Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

computer's problem

Catalyst 3550-48 SWITCH,a computer connected to the f0/40,and vlan id is 301,as the begining,the computer can ping the default-gateway,but after some time (perhaps several days),the computer can't ping the default-gateway.let the computer connected to the f0/42,and the same vlan,can ping the gateway for a while,after some time,the problem is the same as above!

we make the vlans in 6006,and the 3550-48 is the client of the 6006's domain!the other computers have not the problem

8 REPLIES
New Member

Re: computer's problem

Hi Vanguard,

I believe that you have to identify your problem occur at the computer side or switch side first. Please find out the answer of following question:

1. Is there any other host connect to the same switch and same VLAN (301) experience the same problem?

2. If connect any other host to that 3550-48 f0/40 wiht VLAN 301, will the same problem occur?

3. If connect that host to other switch (such as 6006) with same VLAN, will the problem disappear?

If all the answers of above questions are "no", I believe the problem should be at the computer side.

if all the answer of above question are "yes", I believe the problem should be at the switch side.

Please update me when you finish the testing.

/Michael

New Member

Re: computer's problem

1,the other hosts connected to the same switch and vlan 301 don't experience the problem

2,when other host connected to f0/40,the problem appear

3,i need to test !

thanks

New Member

Re: computer's problem

Hi Vanguard,

If another host which connect to F0/40 experience the same problem, is there any non-default configuration on that interface? Please post your configuration.

/Michael

New Member

Re: computer's problem

no

thanks Michael

New Member

Re: computer's problem

Hi Vanguard,

When the problem occur, how did you fix it? Reboot the computer? Or just unplug the cable and replug it?

Is there any log message in the switch indicate this problem?

Please post your configuration.

/Michael

New Member

Re: computer's problem

Hi Guys,

I also encounter a similar problem here, I have yet need to find out the solution for my problem but I'd like to list it here as it may have something in common:

I used 1 x Cisco 3750 as LAN switch to route different network, each physical interface represent one Class C network and I use "no switchport" command to set up L3 routing between each segment. As far as the configuration concern, no problem with routing.

The problem is: occasionally, users report problem saying it cannot connect to the network. What I found is that the host can ping up to the local default gateway and any interfaces on Cisco 3750, but it cannot reach anything beyond 3750 (i.e. ping hosts on other network will fail) This problem occurs:

1. Randomly, so that it is not the switching problem.

2. Happens on all subnetworks, so that it looks like to be a 3750 problem

All I can do was:

1. Clear 3750 arp cache

2. Change the host's MAC address (from NIC utilities).

3. Wait a while and change MAC address back

then the host is OK again.

It looks like to be a MAC/ARP problem with the 3750 switch, but I cannot find out any related articles describing this problem. Has anyone met this sort of situation before?

Cheers

New Member

Re: computer's problem

I highly suggest to load the latest code on this platform. If this does not help, open a case with TAC cause' more detailed T/S will be required.

New Member

Re: computer's problem

Hi, I've some problems in that way:

2*3750 in stack, release 12.1.19-EA1a, acts as a backbone. It performs Inter Vlan routing.

8*2950, release 12.1.19-EA1a, connected to the 3750 by 802.1q trunks. All switches are running MSTP

Sometimes, some hosts (which are plugged on 2950s) are loosing connectivity toward part of the network, and even though the arp entries are correct, after a clear arp-cache on the stack, it is ok.

Stranger again for a host, after a while, it only "accepts" to communicate with segments which are directly attached to the member 2 of the stack!

According to me, like its predecessor, the release release 12.1.19-EA1a is gonna be a DF...

125
Views
0
Helpful
8
Replies
CreatePlease to create content