01-16-2013 08:22 PM - edited 03-04-2019 06:44 PM
Hi All,
We are having Cisco 7200 Router running with code 15.1(4)M4 along with NPEg2.
After connecting Router in network, we are getting below error messages and after that Router reloaded.
One more thing need to add is that we have recently upgrade the IOS and replece the NPEg2 as well.
The Error messages are:
-Traceback= 2160AB0z 2160E34z 386620Cz 3874930z 1B13DD8z 1B13F48z 3523D20z 352268Cz 3522C44z 352C4A8z 3534FA8z 35270ECz 2A23DE4z 2A420B8z 2A218F4z 2A219C4z
Jan 16 19:37:18.100 ist: %SYS-2-LINKED: Bad enqueue of 38B248D8 in queue 711D774 -Process= "IP Input", ipl= 4, pid= 111
-Traceback= 2160AB0z 2160E34z 386620Cz 3874930z 1B13DD8z 1B13F48z 3523D20z 352268Cz 3522C44z 352C4A8z 3534FA8z 35270ECz 2A23DE4z 2A420B8z 2A218F4z 2A219C4z
Jan 16 19:37:18.904 ist: %SYS-2-LINKED: Bad enqueue of 38B2A558 in queue 711D774 -Process= "IP Input", ipl= 4, pid= 111
-Traceback= 2160AB0z 2160E34z 386620Cz 3874930z 1B13DD8z 1B13F48z 3523D20z 352268Cz 3522C44z 352C4A8z 3534FA8z 35270ECz 2A23DE4z 2A420B8z 2A218F4z 2A219C4z
Jan 16 19:37:18.904 ist: %SYS-2-LINKED: Bad enqueue of 38B2B7D8 in queue 711D774 -Process= "IP Input", ipl= 4, pid= 111
-Traceback= 2160AB0z 2160E34z 386620Cz 3874930z 1B13DD8z 1B13F48z 3523D20z 352268Cz 3522C44z 352C4A8z 3534FA8z 35270ECz 2A23DE4z 2A420B8z 2A218F4z 2A219C4z
Jan 16 19:37:19.712 ist: %SYS-2-LINKED: Bad enqueue of 38B31458 in queue 711D774 -Process= "IP Input", ipl= 4, pid= 111
-Traceback= 2160AB0z 2160E34z 386620Cz 3874930z 1B13DD8z 1B13F48z 3523D20z 352268Cz 3522C44z 352C4A8z 3534FA8z 35270ECz 2A23DE4z 2A420B8z 2A218F4z 2A219C4z
Jan 16 19:37:19.712 ist: %SYS-2-LINKED: Bad enqueue of 38B326D8 in queue 711D774 -Process= "IP Input", ipl= 4, pid= 111
-Traceback= 2160AB0z 2160E34z 386620Cz 3874930z 1B13DD8z 1B13F48z 3523D20z 352268Cz 3522C44z 352C4A8z 3534FA8z 35270ECz 2A23DE4z 2A420B8z 2A218F4z 2A219C4z
Jan 16 19:37:20.520 ist: %SYS-2-LINKED: Bad enqueue of 38B3A858 in queue 711D774 -Process= "IP Input", ipl= 4, pid= 111
-Traceback= 2160AB0z 2160E34z 386620Cz 3874930z 1B13DD8z 1B13F48z 3523D20z 352268Cz 3522C44z 352C4A8z 3534FA8z 35270ECz 2A23DE4z 2A420B8z 2A218F4z 2A219C4z
Jan 16 19:37:20.520 ist: %SYS-2-LINKED: Bad enqueue of 38B3BAD8 in queue 711D774 -Process= "IP Input", ipl= 4, pid= 111
-Traceback= 2160AB0z 2160E34z 386620Cz 3874930z 1B13DD8z 1B13F48z 3523D20z 352268Cz 3522C44z 352C4A8z 3534FA8z 35270ECz 2A23DE4z 2A420B8z 2A218F4z 2A219C4z
Jan 16 19:37:22.517 ist: %TRACKING-5-STATE: 2 interface Gi0/1 line-protocol Up->Down
Jan 16 19:37:23.437 ist: %HSRP-5-STATECHANGE: GigabitEthernet0/3 Grp 1 state Active -> Speak
Jan 16 19:37:23.621 ist: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
Jan 16 19:37:23.641 ist: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 172.16.20.3 (GigabitEthernet0/1) is down: interface down
Jan 16 19:37:23.645 ist: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 172.16.20.5 (GigabitEthernet0/1) is down: interface down
Jan 16 19:37:24.621 ist: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
Jan 16 19:37:34.209 ist: %HSRP-5-STATECHANGE: GigabitEthernet0/3 Grp 1 state Speak -> Standby
Jan 16 19:37:46.518 ist: %TRACKING-5-STATE: 1 interface Gi0/3 line-protocol Up->Down
Jan 16 19:37:48.442 ist: %LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to down
Jan 16 19:37:48.442 ist: %ENTITY_ALARM-6-INFO: ASSERT CRITICAL Gi0/3 Physical Port Link Down
.Jan 16 19:37:48.442 ist: %HSRP-5-STATECHANGE: GigabitEthernet0/3 Grp 1 state Standby -> Init
.Jan 16 19:37:48.442 ist: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 172.16.1.5 (GigabitEthernet0/3) is down: interface down
.Jan 16 19:37:48.454 ist: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 172.16.1.200 (GigabitEthernet0/3) is down: interface down
.Jan 16 19:37:48.458 ist: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 172.16.1.10 (GigabitEthernet0/3) is down: interface down
Jan 16 19:37:49.442 ist: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/3, changed state to down
Jan 16 19:37:53.595 ist: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 172.16.12.32 port 514 started - reconnection
Jan 16 19:37:58.595 ist: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 172.16.11.32 port 514 started - reconnection
Jan 16 19:38:05.239 ist: %RF-5-RF_RELOAD: Shelf reload. Reason: Active down, Standby not ready to take Active role
Jan 16 19:38:05.239 ist: %RF_INTERDEV-4-RELOAD: % RF induced self-reload. my state = DISABLED peer state = DISABLED
System Bootstrap, Version 12.4(12.2r)T, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2006 by cisco Systems, Inc.
Socket jumper: not present Failsafe jumper: present = normal
FPGA revision 0x00000026
C7200 platform with 1046528 Kbytes of main memory
Readonly ROMMON initialized
Any clue, is it poiting towards Hardware or Software?
Regards,
YSR.
01-16-2013 08:51 PM
Hi
This should be a software bug
Thanks
Raju
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide