cisco 2911 router interface hangs

[joseph hatem]

dears,

Please note that the LAN interface (GigabitEthernet0/2) on our 2911 router is hanging. the interface stays up/up but is not reachable and stops passing traffic. the issue is temporary resolved after putting the interface in default configuration and reapplying back the configuration.

shut/no shut and router reload does not resolve the issue.

interface GigabitEthernet0/2
 description connected to LAN
 ip address 10.1.184.2 255.255.255.0
 ip nat inside
 ip inspect mea in
 ip virtual-reassembly in
 standby 1 ip 10.1.184.1
 standby 1 priority 110
 standby 1 preempt
 standby 1 track 100 decrement 50
 load-interval 30
 duplex auto
 speed auto

IOS used: c2900-universalk9-mz.SPA.151-4.M8.bin

Please advise.

thank you in advance.

[David Vicente Martinez]

Hi!

I have the same problem with 2911 routers,version c2900-universalk9-mz.SPA.152-1.T4.bin

David.

[joseph hatem]

hi David,

we already changed the cable and the port connected on the switch (from router and switch side) but nothing changed.

regards,

[paul driver]

Hello

Do you get any syslog messages, port status ext.

Have/can you change the port its connected to and also the cabling.

res

Paul

[David Vicente Martinez]

Hi Paul.

In my case the problem is in four routers:

sh logging

Dec  3 07:07:20.131: %ESWMRVL_FLTMG-5-NOTICE: Notice: FPGA Rev 0x71

Dec  3 07:07:24.523: %LINK-5-CHANGED: Interface GigabitEthernet0/0, changed state to reset
Dec  3 07:07:24.523: %LINK-5-CHANGED: Interface GigabitEthernet0/1, changed state to reset
Dec  3 07:07:24.523: %LINK-5-CHANGED: Interface GigabitEthernet0/2, changed state to reset
Dec  3 07:07:25.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Dec  3 07:07:25.719: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to up
Dec  3 07:07:25.719: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
Dec  3 07:07:25.719: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to down
Dec  3 07:07:26.691: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to up
Dec  3 07:07:26.691: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
Dec  3 07:07:26.691: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to down
Dec  3 08:07:26.735 MET: %SYS-6-CLOCKUPDATE: System clock has been updated from 07:07:26 UTC Wed Dec 3 2014 to 08:07:26 MET Wed Dec 3 2014, configured from console by console.
Dec  3 08:07:26.735 MET: %SYS-6-CLOCKUPDATE: System clock has been updated from 08:07:26 MET Wed Dec 3 2014 to 08:07:26 MET Wed Dec 3 2014, configured from console by console.
Dec  3 08:07:28.091 MET: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan2, changed state to down
Dec  3 08:07:28.411 MET: %SYS-5-CONFIG_I: Configured from memory by console
Dec  3 08:07:28.947 MET: %LINK-5-CHANGED: Interface Embedded-Service-Engine0/0, changed state to administratively down
Dec  3 08:07:28.947 MET: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to down
Dec  3 08:07:28.947 MET: %LINK-5-CHANGED: Interface GigabitEthernet0/1, changed state to administratively down
Dec  3 08:07:28.947 MET: %LINK-5-CHANGED: Interface GigabitEthernet0/2, changed state to administratively down
Dec  3 08:07:29.999 MET: %LINEPROTO-5-UPDOWN: Line protocol on Interface Embedded-Service-Engine0/0, changed state to down
Dec  3 08:07:29.999 MET: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to down
Dec  3 08:07:30.551 MET: %LINK-3-UPDOWN: Interface FastEthernet0/0/1, changed state to up
Dec  3 08:07:31.447 MET: %SYS-5-RESTART: System restarted --

[Richard Burts]

David

These log messages are generated as the router boots. It indicates that two of the Gig Ethernet interfaces are admin down (shutdown), one Gig Ethernet is down and the FastEthernet0/0/1 is up after the boot. Is that the situation as you see it? The original post seems to describe an interface that was working and then stops working. Your log messages indicate three interfaces that will not process anything and one interface that probably is working. Are you saying your situation is the same as the original or is different?

As for Gig0/0 being down can you tell us what you think its state should be? Can you tell us what is connected to that interface, how it is connected (including what kind of cable), and whether the device connected to Gig0/0 is up and running?

The original post described a situation where the interface stopped processing and would only start processing when the configuration was removed and then re-applied. Is that your situation also?

HTH

Rick

[David Vicente Martinez]

Hi Richard.

Normal interface state.

Gi 0/0 UP

GI 0/1 Admin Down

Gi 0/2 Admin Down

Fast 0/0/0 Up

Fast 0/0/1 Up

The routers works normally , lines ok, and devices attached ok, without any reason, no problems in lines  PtP  , no power problems, lost the connectivity, the only way to restore the connectivity is with a router reset.

The Gi 0/0 connect to the LAN local:

GigabitEthernet0/0 is up, line protocol is up
  Hardware is CN Gigabit Ethernet, address is 4c00.827f.3de0 (bia 4c00.827f.3de0)
  Description: "LAN LOCAL"
  Internet address is 
  MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full Duplex, 100Mbps, media type is RJ45
  output flow-control is unsupported, input flow-control is unsupported
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:00, output 00:00:00, 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 564000 bits/sec, 98 packets/sec
  5 minute output rate 303000 bits/sec, 75 packets/sec
     2120530 packets input, 802569322 bytes, 0 no buffer
     Received 19268 broadcasts (0 IP multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 1277 multicast, 0 pause input
     2304826 packets output, 1883365124 bytes, 0 underruns
     0 output errors, 0 collisions, 2 interface resets
     845 unknown protocol drops
     0 babbles, 0 late collision, 0 deferred
     1 lost carrier, 0 no carrier, 0 pause output
     0 output buffer failures, 0 output buffers swapped out

And the device conected to this interface is a WS-C3750X-24P (with this example, i have the problem in four routers), with a cat5e wired, no problems was reported in the ws-C3750X-24P.

 In my case when the router is reset, recovered the normal operation

More input:

Cisco CISCO2911/K9 (revision 1.0) with 483328K/40960K bytes of memory.
Processor board ID FCZ17397055
4 FastEthernet interfaces
3 Gigabit Ethernet interfaces
1 terminal line
DRAM configuration is 64 bits wide with parity enabled.
255K bytes of non-volatile configuration memory.
250880K bytes of ATA System CompactFlash 0 (Read/Write)

System image file is "flash0:c2900-universalk9-mz.SPA.152-1.T4.bin"

Thanks in advance.

David.

[Richard Burts]

David

The original post seems to describe a problem that affects only a single interface on the router. I am not clear in your situation whether it is just a single interface that is affected or whether all interfaces are affected. Can you clarify?

The symptoms you describe could be caused by a memory leak. It would be helpful to know what is in syslog at the time of the problem. When the problem happens are you still able to access the router? (telnet/SSH or console?) If so that when the problem happens access the router and look at the log files (it would be good if the logging level were information and even better if the logging level were debug.) If you can not access the router when the problem has happened then it would be good to try to catch the logs as the router runs so that you can see the log messages when the problem happens. Perhaps you could connect a PC to the console (and enable logging console) or perhaps you could telnet/SSH to the router, do term mon (and be sure that logging monitor is enabled at a good level).

HTH

Rick