CISCO1941/K9 router restarted

Suresh Gurugubilli · ‎05-17-2017

Hi,

1900 series router at site was power rebooted. No issue with power supply as other network devices up for more than a month. below are logs, wondering why it was rebooted.

CIDBOI10-LAMR-RTR-1 uptime is 10 hours, 53 minutes
System returned to ROM by power-on
System restarted at 23:37:28 UTC Tue May 16 2017
System image file is "flash:c1900-universalk9-mz.SPA.155-3.M4a.bin"
Last reload type: Normal Reload
Last reload reason: power-on

CIDBOI10-LAMR-RTR-1#dir
Directory of flash0:/

1 -rw- 16094 Jan 26 2017 22:13:00 +00:00 cfg-01262017-01.txt
2 -rw- 3064 Jul 2 2014 22:51:36 +00:00 cpconfig-19xx.cfg
3 -rw- 720 Aug 26 2015 20:11:36 +00:00 vlan.dat
4 -rw- 13885 Aug 23 2016 01:23:34 +00:00 DMVPN_config_AUG_22
5 -rw- 2464 Jul 2 2014 22:54:12 +00:00 home.shtml
6 -rw- 75608148 Jul 24 2015 16:09:54 +00:00 c1900-universalk9-mz.SPA.154-3.M3.bin
7 -rw- 1195361 Jul 24 2015 16:19:20 +00:00 pp-adv-isrg2-154-3.M2-20-14.0.0.pack
8 -rw- 1202434 Jan 19 2016 15:14:24 +00:00 pp-adv-isrg2-154-3.M2-20-15.0.0.pack
9 -rw- 2566827 Dec 10 2016 21:01:12 +00:00 pp-adv-isrg2-156-3.M-23-26.0.0.pack
10 -rw- 79680096 Dec 10 2016 21:28:04 +00:00 c1900-universalk9-mz.SPA.155-3.M4a.bin
11 -rw- 17994 Feb 27 2017 18:20:06 +00:00 cfg-02272016-01.txt
12 -rw- 17994 Feb 27 2017 18:25:32 +00:00 cfg-02272017-01.txt
13 -rw- 2377766 Feb 27 2017 19:20:40 +00:00 pp-adv-isrg2-155-3.M4a-23-28.0.0.pack
14 -rw- 194868 Mar 1 2017 20:38:28 +00:00 crashinfo_20170301-203829-UTC
15 -rw- 20874 Apr 18 2017 21:58:04 +00:00 cfg-04182017-01.txt

*Jan 2 00:00:02.315: %SMART_LIC-6-AGENT_READY: Smart Agent for Licensing is initialized
*Jan 2 00:00:02.447: %IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL: Module name = c1900 Next reboot level = ipbasek9 and License = ipbasek9
*Jan 2 00:00:02.639: %IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL: Module name = c1900 Next reboot level = securityk9 and License = securityk9
*Jan 2 00:00:02.819: %IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL: Module name = c1900 Next reboot level = datak9 and License = datak9
*May 16 23:24:11.623: c3600_scp_set_dstaddr2_idb(184)add = 80 name is Embedded-Service-Engine0/0
*May 16 23:24:32.939: c3600_scp_set_dstaddr2_idb(184)add = 0 name is NULL
*May 16 23:24:41.615: %VPN_HW-6-INFO_LOC: Crypto engine: onboard 0 State changed to: Initialized
*May 16 23:24:41.619: %VPN_HW-6-INFO_LOC: Crypto engine: onboard 0 State changed to: Enabled
*May 16 23:24:42.595: %VPN_HW-6-INFO_LOC: Crypto engine: slot 0 State changed to: Initialized
*May 16 23:24:48.459: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to down
*May 16 23:24:48.459: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up
*May 16 23:24:48.463: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1/0, changed state to up
*May 16 23:24:48.463: %LINK-3-UPDOWN: Interface GigabitEthernet0/1/0, changed state to up
*May 16 23:24:48.463: %LINEPROTO-5-UPDOWN: Line protocol on Interface ISM VPN Accelerator, changed state to up
*May 16 23:24:49.311: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
*May 16 23:24:49.543: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to down
*May 16 23:24:49.547: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state to up
*May 16 23:24:51.667 UTC: %SYS-5-LOG_CONFIG_CHANGE: Buffer logging: level debugging, xml disabled, filtering disabled, size (120000)
*May 16 23:24:51.671 UTC: %SYS-5-LOG_CONFIG_CHANGE: Console logging disabled
*May 16 23:25:00.463 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel10, changed state to down
*May 16 23:25:00.867 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback10, changed state to up
*May 16 23:25:01.291 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel20, changed state to down
*May 16 23:25:03.851 UTC: %LINK-5-CHANGED: Interface Embedded-Service-Engine0/0, changed state to administratively down
*May 16 23:25:05.235 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Embedded-Service-Engine0/0, changed state to down
*May 16 23:25:11.795 UTC: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 167.191.134.197 port 0 CLI Request Triggered
*May 16 23:25:13.175 UTC: %SYS-5-CONFIG_I: Configured from memory by console
*May 16 23:25:13.675 UTC: %LINK-3-UPDOWN: Interface GigabitEthernet0/1/0, changed state to down
*May 16 23:25:14.719 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1/0, changed state to down
*May 16 23:25:15.943 UTC: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1900 Software (C1900-UNIVERSALK9-M), Version 15.5(3)M4a, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2016 by Cisco Systems, Inc.
Compiled Thu 06-Oct-16 13:56 by prod_rel_team
*May 16 23:25:15.987 UTC: %SNMP-5-COLDSTART: SNMP agent on host CIDBOI10-LAMR-RTR-1 is undergoing a cold start
*May 16 23:25:16.879 UTC: %SSH-5-ENABLED: SSH 2.0 has been enabled
*May 16 23:25:16.883 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0/0, changed state to down
*May 16 23:25:16.883 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0/1, changed state to down
*May 16 23:25:16.883 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0/2, changed state to down
*May 16 23:25:16.883 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0/3, changed state to down
*May 16 23:25:17.099 UTC: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
*May 16 23:25:17.099 UTC: %CRYPTO-6-GDOI_ON_OFF: GDOI is OFF
*May 16 23:25:17.099 UTC: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
*May 16 23:25:17.099 UTC: %CRYPTO-6-GDOI_ON_OFF: GDOI is OFF
*May 16 23:25:17.107 UTC: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is ON
*May 16 23:25:17.607 UTC: %LINK-3-UPDOWN: Interface GigabitEthernet0/1/0, changed state to up
*May 16 23:25:18.735 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1/0, changed state to up
*May 16 23:25:21.239 UTC: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 167.191.134.197 port 514 started - CLI initiated
*May 16 23:25:21.351 UTC: %VPN_HW-6-INFO_LOC: Crypto engine: onboard 0 State changed to: Disabled
*May 16 23:25:21.367 UTC: %VPN_HW-6-INFO_LOC: Crypto engine: slot 0 State changed to: Enabled
*May 16 23:25:21.367 UTC: ISM VPN UP & READY
*May 16 23:25:21.371 UTC: %CRYPTO-6-GDOI_ON_OFF: GDOI is OFF
*May 16 23:25:21.371 UTC: %CRYPTO-6-GDOI_ON_OFF: GDOI is OFF
*May 16 23:25:31.472 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel10, changed state to up
*May 16 23:25:31.596 UTC: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.252.2.1 (Tunnel10) is up: new adjacency
*May 16 23:26:01.472 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel20, changed state to up
*May 16 23:26:11.712 UTC: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.252.4.4 (Tunnel20) is up: new adjacency
*May 16 23:26:11.756 UTC: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.252.4.3 (Tunnel20) is up: new adjacency
May 16 23:41:02.906 UTC: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.252.4.4 (Tunnel20) is down: retry limit exceeded
May 16 23:41:19.686 UTC: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.252.4.4 (Tunnel20) is up: new adjacency
May 16 23:42:39.214 UTC: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.252.4.4 (Tunnel20) is down: retry limit exceeded
May 16 23:42:52.354 UTC: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.252.4.4 (Tunnel20) is up: new adjacency
May 16 23:44:07.114 UTC: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to up
May 16 23:44:08.114 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state to up
May 16 23:44:11.866 UTC: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.252.4.4 (Tunnel20) is down: retry limit exceeded
May 16 23:44:17.502 UTC: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 167.191.21.33 (GigabitEthernet0/0) is up: new adjacency
May 16 23:44:22.746 UTC: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 10.252.4.4 (Tunnel20) is up: new adjacency

marce1000 · ‎05-17-2017

Last reload reason: power-on

Despite your analysis this means what it says; hence there must have been some (other) power problem.

M.

-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

Mark Malone · ‎05-17-2017

yep heres the official word on it , something happened other than the router here

Power-On

If the show version command output shows restarted by reload or System returned to ROM by power-on, you can infer that the router was either power-cycled, or that the power source went down for a few seconds. Verify your power source and troubleshoot the outlet circuit (power to router).

Suresh Gurugubilli · ‎05-18-2017

Thanks for reply, even i suspect this is related to Power Supply.

But, I see 1900 series router experiencing same issue multiple times with multiple devices. Either it's Power-On or Softreload. So just want to check other customers also notice this.

Mark Malone · ‎05-18-2017

Yes here is the doc , this covers most general types of reloads or crashes you might see

http://www.cisco.com/c/en/us/support/docs/ios-nx-os-software/ios-software-releases-121-mainline/7957-crashes-lesscommon.html#anc19

Reload

If the show version command output shows restarted by reload or system returned to ROM by reload, you can infer that a user rebooted the router manually with the reload command. This is not a system crash.