Solved: Router 2911 Interface status gone to reset

zeeshanzahid510 · ‎09-11-2020

Router 2911

When i enter "show ip int brief" command i found following result for one of my gigabit interface,

Interface IP-Address OK? Method Status Prot

GigabitEthernet0/0 unassigned YES unset reset down

My problem is why the status in gone to reset and it is not going to up after shut and no shut commands

Leo Laohoo · ‎09-14-2020

Gi0/0 is fixed and cannot be removed.

If you do not need Gi0/0 then other ports will do, HOWEVER, this does not guarantee the other ports will not start to fail.

Remember, the motherboard of the router is failing. RMA is the only way to fix the issue.

View solution in original post

Leo Laohoo · ‎09-11-2020

Post the complete output to the following commands:

sh version
sh interface Gi 0/0
sh logs

zeeshanzahid510 · ‎09-11-2020

Router#show version
Cisco IOS Software, C2900 Software (C2900-UNIVERSALK9-M), Version 15.1(4)M2, REL EASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Mon 26-Sep-11 17:37 by prod_rel_team

ROM: System Bootstrap, Version 15.0(1r)M12, RELEASE SOFTWARE (fc1)

Router uptime is 17 hours, 55 minutes
System returned to ROM by power-on
System restarted at 11:36:22 UTC Fri Sep 11 2020
System image file is "flash0:c2900-universalk9-mz.SPA.151-4.M2.bin"
Last reload type: Normal Reload

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

Cisco CISCO2911/K9 (revision 1.0) with 487424K/36864K bytes of memory.
Processor board ID FGL1548126S
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)

License Info:

License UDI:

-------------------------------------------------
Device# PID SN
-------------------------------------------------
*0 CISCO2911/K9 FGL1548126S

Technology Package License Information for Module:'c2900'

-----------------------------------------------------------------
Technology Technology-package Technology-package
Current Type Next reboot
------------------------------------------------------------------
ipbase ipbasek9 Permanent ipbasek9
security None None None
uc None None None
data None None None

Configuration register is 0x2102

Georg Pauwen · ‎09-11-2020

Hello,

what is the output of:

Router#test interfaces GigabitEthernet0/0

?

Also, does the interface come up when you configure 'no keepalive' ?

Router#conf t

Router(config)#interface GigabitEthernet0/0

Router(config-if)#no keepalive

zeeshanzahid510 · ‎09-12-2020

Router#test interfaces gigabitEthernet 0/0
No IP address for GigabitEthernet0/0.
Skipping...
1 interfaces: 0 passed, 0 failed, 0 skipped, 1 untestable

still same status when i am configuring no keepalive

zeeshanzahid510 · ‎09-11-2020

Router#show interfaces gi
Router#show interfaces gigabitEthernet 0/0
GigabitEthernet0/0 is reset, line protocol is down
Hardware is CN Gigabit Ethernet, address is 2894.0f35.6158 (bia 2894.0f35.6158 )
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Unknown, Unknown, media type is RJ45
output flow-control is XON, input flow-control is XON
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 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 packets output, 0 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 pause output
0 output buffer failures, 0 output buffers swapped out

zeeshanzahid510 · ‎09-11-2020

sh version
sh interface Gi 0/0

result has been posted but there is no such command of show logs

zeeshanzahid510 · ‎09-11-2020

Router is cisco 291. It was in working condition but from last few days this interface is not working also reset the switch but still same response

Leo Laohoo · ‎09-11-2020

@zeeshanzahid510 wrote:

Unknown, Unknown, media type is RJ45

Uhhhh ... WTF.

Console into the router and reboot the router. Post the entire boot-up process.

zeeshanzahid510 · ‎09-12-2020

Here is the boot-up process

Router#reload

System configuration has been modified. Save? [yes/no]: n
Proceed with reload? [confirm]

Sep 12 08:42:45.022: %SYS-5-RELOAD: Reload requested by console. Reload Reason: Reload Command.
System Bootstrap, Version 15.0(1r)M12, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2011 by cisco Systems, Inc.

Total memory size = 512 MB - On-board = 512 MB, DIMM0 = 0 MB
CISCO2911/K9 platform with 524288 Kbytes of main memory
Main memory is configured to 72/-1(On-board/DIMM0) bit mode with ECC enabled

Readonly ROMMON initialized
program load complete, entry point: 0x80803000, size: 0x1b340
program load complete, entry point: 0x80803000, size: 0x1b340

IOS Image Load Test
___________________
Digitally Signed Release Software
program load complete, entry point: 0x81000000, size: 0x475d59c
Self decompressing the image : ############################################################################################################################################################################################################################################################################################################################################################################################################################################################### [OK]

Smart Init is enabled
smart init is sizing iomem
TYPE MEMORY_REQ
Onboard devices &
buffer pools 0x022F6000
-----------------------------------------------
TOTAL: 0x022F6000

Rounded IOMEM up to: 36Mb.
Using 7 percent iomem. [36Mb/512Mb]

Restricted Rights Legend

Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.

cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706

Cisco IOS Software, C2900 Software (C2900-UNIVERSALK9-M), Version 15.1(4)M2, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Mon 26-Sep-11 17:37 by prod_rel_team

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

Cisco CISCO2911/K9 (revision 1.0) with 487424K/36864K bytes of memory.
Processor board ID FGL1548126S
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)

%Error opening tftp://255.255.255.255/network-confg (Timed out)
%Error opening tftp://255.255.255.255/cisconet.cfg (Timed out)
%Error opening tftp://255.255.255.255/router-confg (Timed out)
%Error opening tftp://255.255.255.255/network-confg (Timed out)
%Error opening tftp://255.255.255.255/ciscortr.cfg (Timed out)

Press RETURN to get started!

Jan 2 12:00:04.251: %IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL: Module name = c2900 Next reboot level = ipbasek9 and License = ipbasek9
Jan 2 12:00:04.771: %MAINBOARD-3-I2CRW_ERROR: Write failure - Device @ 0xA8, offset 0x00000000 on I2C bus 1
Jan 2 12:00:04.771: %MAINBOARD-3-I2CRW_ERROR: Read failure - Device @ 0xA8, offset 0x00000000 on I2C bus 1
Jan 2 12:00:04.771: %MAINBOARD-3-I2CRW_ERROR: Write failure - Device @ 0xA8, offset 0x00000001 on I2C bus 1
Jan 2 12:00:04.775: %MAINBOARD-3-I2CR
Router>W_ERROR: Read failure - Device @ 0xA8, offset 0x00000001 on I2C bus 1
Jan 2 12:00:04.775: %MAINBOARD-3-I2CRW_ERROR: Write failure - Device @ 0xA8, offset 0x00000002 on I2C bus 1
Jan 2 12:00:04.775: %MAINBOARD-3-I2CRW_ERROR: Read failure - Device @ 0xA8, offset 0x00000002 on I2C bus 1
Jan 2 12:00:04.775: %MAINBOARD-3-I2CRW_ERROR: Write failure - Device @ 0xA8, offset 0x00000003 on I2C bus 1
Jan 2 12:00:04.775: %MAINBOARD-3-I2CRW_ERROR: Read failure - Device @ 0xA8, offset 0x00000003 on I2C bus 1
Jan 2 12:00:04.775: %MAINBOARD-3-I2CRW_ERROR: Write failure - Device @ 0xA8, offset 0x00000004 on I2C bus 1
Jan 2 12:00:04.775: %MAINBOARD-3-I2CRW_ERROR: Read failure - Device @ 0xA8, offset 0x00000004 on I2C bus 1
Jan 2 12:00:04.779: %MAINBOARD-3-I2CRW_ERROR: Write failure - Device @ 0xA8, offset 0x00000005 on I2C bus 1
Jan 2 12:00:04.779: %MAINBOARD-3-I2CRW_ERROR: Read failure - Device @ 0xA8, offset 0x00000005 on I2C bus 1
Jan 2 12:00:04.779: %MAINBOARD-3-I2CRW_ERROR: Write failure - Device @ 0xA8, offset 0x00000006 on I2C bus 1
Jan 2 12:00:04.779: %MAINBOARD-3-I2CRW_ERROR: Read failure - Device @ 0xA8, offset 0x00000006 on I2C bus 1
Jan 2 12:00:04.779: %MAINBOARD-3-I2CRW_ERROR: Write failure - Device @ 0xA8, offset 0x00000007 on I2C bus 1
Jan 2 12:00:04.779: %MAINBOARD-3-I2CRW_ERROR: Read failure - Device @ 0xA8, offset 0x00000007 on I2C bus 1
Jan 2 12:00:04.779: %MAINBOARD-3-I2CRW_ERROR: Write failure - Device @ 0xA8, offset 0x00000008 on I2C bus 1
Jan 2 12:00:04.783: %MAINBOARD-3-I2CRW_ERROR: Read failure - Device @ 0xA8, offset 0x00000008 on I2C bus 1
Jan 2 12:00:04.783: %MAINBOARD-3-I2CRW_ERROR: Write failure - Device @ 0xA8, offset 0x00000009 on I2C bus 1
Jan 2 12:00:04.783: %MAINBOARD-3-I2CRW_ERROR: Read failure - Device @ 0xA8, offset 0x00000009 on I2C bus 1
Jan 2 12:00:04.783: %MAINBOARD-3-I2CRW_ERROR: Write failure - Device @ 0xA8, offset 0x0000000A on I2C bus 1
Jan 2 12:00:04.783: %MAINBOARD-3-I2CRW_ERROR: Read failure - Device @ 0xA8, offset 0x0000000A on I2C bus 1
Jan 2 12:00:04.783: %MAINBOARD-3-I2CRW_ERROR: Write failure - Device @ 0xA8, offset 0x0000000B on I2C bus 1
Jan 2 12:00:04.783: %MAINBOARD-3-I2CRW_ERROR: Read failure - Device @ 0xA8, offset 0x0000000B on I2C bus 1
Jan 2 12:00:04.787: %MAINBOARD-3-I2CRW_ERROR: Write failure - Device @ 0xA8, offset 0x0000000C on I2C bus 1
Jan 2 12:00:04.787: %MAINBOARD-3-I2CRW_ERROR: Read failure - Device @ 0xA8, offset 0x0000000C on I2C bus 1
Jan 2 12:00:04.787: %MAINBOARD-3-I2CRW_ERROR: Write failure - Device @ 0xA8, offset 0x0000000D on I2C bus 1
Jan 2 12:00:04.787: %MAINBOARD-3-I2CRW_ERROR: Read failure - Device @ 0xA8, offset 0x0000000D on I2C bus 1
Jan 2 12:00:04.787: %MAINBOARD-3-I2CRW_ERROR: Write failure - Device @ 0xA8, offset 0x0000000E on I2C bus 1
Jan 2 12:00:04.787: %MAINBOARD-3-I2CRW_ERROR: Read failure - Device @ 0xA8, offset 0x0000000E on I2C bus 1
Jan 2 12:00:04.787: %MAINBOARD-3-I2CRW_ERROR: Write failure - Device @ 0xA8, offset 0x0000000F on I2C bus 1
Jan 2 12:00:04.791: %MAINBOARD-3-I2CRW_ERROR: Read failure - Device @ 0xA8, offset 0x0000000F on I2C bus 1
Jan 2 12:00:04.791: %MAINBOARD-3-I2CRW_ERROR: Write failure - Device @ 0xA8, offset 0x00000010 on I2C bus 1
Jan 2 12:00:04.791: %MAINBOARD-3-I2CRW_ERROR: Read failure - Device @ 0xA8, offset 0x00000010 on I2C bus 1
Jan 2 12:00:04.791: %MAINBOARD-3-I2CRW_ERROR: Write failure - Device @ 0xA8, offset 0x00000011 on I2C bus 1
Jan 2 12:00:04.791: %MAINBOARD-3-I2CRW_ERROR: Read failure - Device @ 0xA8, offset 0x00000011 on I2C bus 1
Jan 2 12:00:04.791: %ENVMON-3-POWER_ERROR: : Wrong RPS is connected.
Sep 12 08:44:33.187: %LINK-5-CHANGED: Interface GigabitEthernet0/0, changed state to reset
Sep 12 08:44:33.187: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to down
Sep 12 08:44:33.187: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to down
Sep 12 08:44:34.391: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to down
Sep 12 08:44:34.391: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to down
Sep 12 08:44:34.391: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to down
Sep 12 08:44:35.343: %SYS-5-CONFIG_I: Configured from memory by console
Sep 12 08:44:37.363: %LINK-5-CHANGED: Interface Embedded-Service-Engine0/0, changed state to administratively down
Sep 12 08:44:37.363: %LINK-5-CHANGED: Interface GigabitEthernet0/0, changed state to administratively down
Sep 12 08:44:37.363: %LINK-5-CHANGED: Interface GigabitEthernet0/1, changed state to administratively down
Sep 12 08:44:38.363: %LINEPROTO-5-UPDOWN: Line protocol on Interface Embedded-Service-Engine0/0, changed state to down
Sep 12 08:45:18.927: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/network-confg) failed
Sep 12 08:45:59.927: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/cisconet.cfg) failed
Sep 12 08:46:40.927: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/router-confg) failed
Sep 12 08:47:10.927: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/network-confg) failed
Sep 12 08:47:21.927: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/ciscortr.cfg) failed
Sep 12 08:47:21.927: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C2900 Software (C2900-UNIVERSALK9-M), Version 15.1(4)M2, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Mon 26-Sep-11 17:37 by prod_rel_team
Sep 12 08:47:22.087: %SNMP-5-COLDSTART: SNMP agent on host Router is undergoing a cold start
Sep 12 08:47:22.703: %SYS-6-BOOTTIME: Time taken to reboot after reload = 278 seconds
%Error opening tftp://255.255.255.255/cisconet.cfg (Timed out)
Sep 12 08:47:52.363: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/cisconet.cfg) failed
%Error opening tftp://255.255.255.255/router-confg (Timed out)
Sep 12 08:48:34.315: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/router-confg) failed
%Error opening tftp://255.255.255.255/ciscortr.cfg (Timed out)
Sep 12 08:49:15.315: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/ciscortr.cfg) failed
%Error opening tftp://255.255.255.255/network-confg (Timed out)
Sep 12 08:49:33.363: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/network-confg) failed
%Error opening tftp://255.255.255.255/cisconet.cfg (Timed out)
Sep 12 08:50:14.363: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/cisconet.cfg) failed
%Error opening tftp://255.255.255.255/router-confg (Timed out)
Sep 12 08:50:56.315: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/router-confg) failed
%Error opening tftp://255.255.255.255/ciscortr.cfg (Timed out)
Sep 12 08:51:37.315: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/ciscortr.cfg) failed
%Error opening tftp://255.255.255.255/network-confg (Timed out)
Sep 12 08:52:25.363: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/network-confg) failed
%Error opening tftp://255.255.255.255/cisconet.cfg (Timed out)
Sep 12 08:53:06.363: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/cisconet.cfg) failed
%Error opening tftp://255.255.255.255/router-confg (Timed out)
Sep 12 08:53:48.315: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/router-confg) failed
%Error opening tftp://255.255.255.255/ciscortr.cfg (Timed out)
Sep 12 08:54:29.315: %SYS-4-CONFIG_RESOLVE_FAILURE: System config parse from (tftp://255.255.255.255/ciscortr.cfg) failed

Leo Laohoo · ‎09-12-2020

@zeeshanzahid510 wrote:

%MAINBOARD-3-I2CRW_ERROR: Read failure - Device @ 0xA8, offset 0x00000011 on I2C bus 1

The router is dead.

The error message above means a section of the router's motherboard has failed.

zeeshanzahid510 · ‎09-12-2020

Only giga 0/0 is not getting up, remaining other ports are working fine

zeeshanzahid510 · ‎09-13-2020

Can you please suggest that if we change the module of giga 0/0 than it will work for us? Bcoz only giga 0/0 is not getting up remaining ports are working fine.

Leo Laohoo · ‎09-14-2020

Gi0/0 is fixed and cannot be removed.

If you do not need Gi0/0 then other ports will do, HOWEVER, this does not guarantee the other ports will not start to fail.

Remember, the motherboard of the router is failing. RMA is the only way to fix the issue.