Cisco 2821 Drops LAN Connection

Answered Question

I have a Cisco 2821 with a Etherswitch WIC connected to an ISP router and a network switch and for a couple of days now the WIC dropped it's connection to the LAN.  Reloading the router solves the issue until the next day.  I checked the logging on the router and nothing.  I was able to ping the virtual interface on the router while directly connected via the console.  All virtual and physical interfaces were up.  However, I wasn't able to ping anything on the local network.  There were no crash logs on the server.  How can I troubleshoot this issue?


The only explanation I had is that I had the WIC interface connected to a gigabit port.  Would that cause problems--connecting a 10/100 WIC to a Gigabit port on another switch???

Correct Answer by burleyman about 7 years 2 weeks ago

On the interface in question, it is running half duplex which is why you are seeing the collisions you will need to correct this and you collisions should go away. make sure both ends are setup the same way as this could also be a duplex mismatch.



Mike

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.

Here's the show interfaces.  What concerns me are the collisions and interface resets.


ABT_OPS#show interfaces
FastEthernet0/3/0 is up, line protocol is up
  Hardware is Fast Ethernet, address is 001b.54f0.4d29 (bia 001b.54f0.4d29)
  Description: TRUNK_PORT
  MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
     reliability 252/255, txload 3/255, rxload 4/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Half-duplex, 100Mb/s
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output never, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 1926000 bits/sec, 426 packets/sec
  5 minute output rate 1244000 bits/sec, 424 packets/sec
     1155584 packets input, 586968670 bytes, 0 no buffer
     Received 44 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 input packets with dribble condition detected
     1181325 packets output, 412154404 bytes, 0 underruns
     34516 output errors, 45158 collisions, 2 interface resets
     0 unknown protocol drops
     0 babbles, 13640 late collision, 15048 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out
FastEthernet0/3/1 is up, line protocol is up
  Hardware is Fast Ethernet, address is 001b.54f0.4d2a (bia 001b.54f0.4d2a)
  Description: TO_FIREWALL_UNTRUSTED
  MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
     reliability 255/255, txload 2/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 100Mb/s
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input never, output never, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 432000 bits/sec, 155 packets/sec
  5 minute output rate 1069000 bits/sec, 155 packets/sec
     393156 packets input, 135668499 bytes, 0 no buffer
     Received 68 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 input packets with dribble condition detected
     368804 packets output, 271710924 bytes, 0 underruns
     0 output errors, 0 collisions, 2 interface resets
     0 unknown protocol drops
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out
FastEthernet0/3/2 is up, line protocol is up
  Hardware is Fast Ethernet, address is 001b.54f0.4d2b (bia 001b.54f0.4d2b)
  Description: TO_LAN_TRUSTED
  MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
     reliability 255/255, txload 2/255, rxload 2/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 100Mb/s
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output never, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 883000 bits/sec, 291 packets/sec
  5 minute output rate 868000 bits/sec, 295 packets/sec
     834454 packets input, 292393570 bytes, 0 no buffer
     Received 1355 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 input packets with dribble condition detected
     823484 packets output, 320229130 bytes, 0 underruns
     0 output errors, 0 collisions, 2 interface resets
     0 unknown protocol drops
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out

Correct Answer
burleyman Thu, 05/13/2010 - 12:42
User Badges:
  • Blue, 1500 points or more

On the interface in question, it is running half duplex which is why you are seeing the collisions you will need to correct this and you collisions should go away. make sure both ends are setup the same way as this could also be a duplex mismatch.



Mike

burleyman Thu, 05/13/2010 - 12:53
User Badges:
  • Blue, 1500 points or more

What is the confiruration of the interface on your side?


Auto/Auto

or

Hard set speed and duplex?



Mike

burleyman Thu, 05/13/2010 - 13:08
User Badges:
  • Blue, 1500 points or more

My guess is that is your side is set to Auto is that thier side is set to 100/full which will cause a duplex mismatch.




Mike

francisco_1 Thu, 05/13/2010 - 13:08
User Badges:
  • Gold, 750 points or more

Is the affected interface FastEthernet0/3/0? It's using half duplex with output errors & collision!!!



FastEthernet0/3/0 is up, line protocol is up
    Description: TRUNK_PORT
  MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
     reliability 252/255, txload 3/255, rxload 4/255
    Half-duplex, 100Mb/s
       34516 output errors, 45158 collisions, 2 interface resets
     0 unknown protocol drops
     0 babbles, 13640 late collision, 15048 deferred
   


Francisco

francisco_1 Thu, 05/13/2010 - 13:09
User Badges:
  • Gold, 750 points or more

Have you tried hard coding duplex on both sides?

amychen2008 Thu, 05/13/2010 - 13:15
User Badges:

Actually this is 10g port, cannot change speed/duplex.  I don't see input errors.


#show arp 
Protocol  Address          Age (min)  Hardware Addr   Type        Interface
Internet  1.1.1.1                 -   0005.dd32.6000  ARPA        GigabitEthernet0/0
Internet  1.1.1.2                45   0005.5f1e.68cc  ARPA        GigabitEthernet0/0


#show cdp nei
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater

Device ID            Local Intrfce         Holdtme   Capability    Platform   Port ID
xxxxxx                    Gig 0/0               147            R        12410/PRP Gig 2/0


#show int g0/0
GigabitEthernet0/0 is up, line protocol is up
  Hardware is GigMac 1 Port 10 GigabitEthernet Plus, address is 0005.dd32.6000 (bia 0005.dd32.6000)
  Internet address is 1.1.1.1/30
  MTU 4470 bytes, BW 10000000 Kbit, DLY 10 usec, rely 255/255, load 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full Duplex, 10000Mbps, link type is force-up, media type is LR 1310nm
  ......
  30 second input rate 0 bits/sec, 0 packets/sec
  30 second output rate 0 bits/sec, 0 packets/sec
     29 packets input, 11339 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 29 multicast, 0 pause input
     233 packets output, 34595 bytes, 0 underruns
     Transmitted 0 broadcasts
     0 output errors, 0 collisions, 0 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 pause output
     0 output buffer failures, 0 output buffers swapped out

Actions

This Discussion