Cisco help.

[AbecX]

I need some help with a 2924XL switch. Anyone around?

Damn thing keeps locking up and I have to reset it, I'm pretty sure its configuration error, but I dont know where to start.

[Lyn]

Wrong forum dude!

[Blue88Coupe]

write
erase
reload

[AbecX]

I don think its supposed to have that many input errors. Any ideas?

switch5>show interface FastEthernet 0/1
FastEthernet0/1 is up, line protocol is up
Hardware is Fast Ethernet, address is 0003.6b93.76c1 (bia 0003.6b93.76c1)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 251/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Full-duplex, 100Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:04, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 30000 bits/sec, 27 packets/sec
5 minute output rate 71000 bits/sec, 32 packets/sec
208378 packets input, 48249628 bytes
Received 10078 broadcasts, 12498 runts, 0 giants, 0 throttles
12583 input errors, 35 CRC, 50 frame, 0 overrun, 1 ignored
0 watchdog, 319 multicast
0 input packets with dribble condition detected
258949 packets output, 57318182 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out

[Stang2be]

how many hosts plugged into this thing? I agree those errors dont look right. Its no help now but I've got a few 2924s on the shelf at the office. Are you doing anything fancy with the switch?

[AbecX]

there is 22 hosts plugged into the switch, one uplink to our core switch. minimal bandwidth is going through it, nothing to come close to maxing anything out.

[DamonH]

Originally posted by AbecX
Received 10078 broadcasts, 12498 runts, 0 giants, 0 throttles
12583 input errors, 35 CRC, 50 frame, 0 overrun, 1 ignored
0 watchdog, 319 multicast
0 input packets with dribble condition detected
258949 packets output, 57318182 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out

You are DEFINITELY not suppose to be seeing that many input errors! I'd check your cabling.

[lowthreeohz]

it's creating like 85 errors in under a minute. like above, check the cabling Cruz. ;)

[Stang2be]

only thing else I could think of besides cabling is checking that one of the nic's is having issues with auto neg or hard coded to 10 half or 100 half or something like that.

[White_lightning]

like everyone said. check cabling.. if that doesnt do it.. try pull up statistics per port ( dont know if the 2924 will do it.. ) or telnet in twice.. reset the error counter. and start shutting down ports till you find the one causing the problems

[AbecX]

I dropped the port speed and duplex to 10/H, still getting errors.

I wouldnt think it was the cabling, we had a switch plugged up last week that worked fine albeit some cheap ass manageable switch.

Thanks for the help so far.

[XL]

Originally posted by AbecX
I dropped the port speed and duplex to 10/H, still getting errors.

I wouldnt think it was the cabling, we had a switch plugged up last week that worked fine albeit some cheap ass manageable switch.

Thanks for the help so far.
The speed and duplex shouldn't be causing the problem. If it is, then the IOS would give you a message saying there is a duplex conflict. I don't know how many of the interfaces on a 2900 are fast ethernet or ethernet. Where is the FastEthernet interface going?

[AbecX]

I'm assuming FastEthernet 0/1 is referring to port 1 on my switch which is the uplink to the core switch.

[XL]

Originally posted by AbecX
I'm assuming FastEthernet 0/1 is referring to port 1 on my switch which is the uplink to the core switch.
I'm pretty sure on switches 0/1 means first port on the row. On their router it is 0/0 which is the first interface. It looks like you are getting a lot of "runts", which are incomplete packets that are discarded. Runts are almost always caused by collisions. But since your collision rate isn't high, it seems like it is from under-runs. Underruns come from a transmitter that is sending faster than the receiver can handle.

Out of all that garbage I just typed, I think underruns are your problem.

Edit: I just looked at your interface statistics and it says it isn't getting any underruns. I'm stumped.

[AbecX]

switch5#sh int Fast 0/1
FastEthernet0/1 is up, line protocol is up
Hardware is Fast Ethernet, address is 0003.6b93.76c1 (bia 0003.6b93.76c1)
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Auto-duplex (Full), 10Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:06, output 00:00:01, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 22000 bits/sec, 22 packets/sec
5 minute output rate 38000 bits/sec, 28 packets/sec
744235 packets input, 134721301 bytes
Received 43067 broadcasts, 32233 runts, 0 giants, 0 throttles
32468 input errors, 115 CRC, 120 frame, 0 overrun, 2 ignored
0 watchdog, 1258 multicast
0 input packets with dribble condition detected
910434 packets output, 205258600 bytes, 0 underruns
0 output errors, 10 collisions, 6 interface resets
0 babbles, 0 late collision, 35 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out

[XL]

Well, look at it, all input errors, no output errors. It has to be coming from the source. Any way of checking the core switch?

Put it back on auto speed, you don't need to hard set that.

[AbecX]

I'd have to go to work and check it out, I dont know what port this switch plugs into on our core switch.

[AbecX]

I'm pretty sure its the core switch causing the problems, switch5 is not having any outgoing connection issues, the core switch seems to just be dropping the connection for some reason. Looking at the cacti graph shows that switch5 is able to send out data, but the core isnt accepting it back in: http://abecx.net/graph.gif When looking at the graph, you can see where data stops coming inbound, but outbound from switch5 is still trying to get out. Looking at the stats on Switch5 also confirms this somewhat as its having all the errors on the inbound interface. Dont know if I'm right but thats my theory with a couple of hours into something I've never done before.

[ScottJ]

I see it as a source issue too. Have you replaced the blade on switch5 to test? Are there any othe ports on FE 0/x having issues?

[XL]

Originally posted by ScottJ
Have you replaced the blade on switch5 to test?
2900's aren't modular.