Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

best practice to determine cisco shutdown ?

Status
Not open for further replies.

matthias7

ISP
Jun 8, 2006
60
MX
Hi

I have an old cisco router 2800 series that is working good but every now and then the router does not respond and gets back up by it self after a while ..

show version command tells me the most of the time:
System returned to ROM by power-on

does it mean restarting because of electrical outages
in the location and nothing else and the timer reseted or could it be something else causing it to reboot ...

Matt
 
That indicates a power failure. If you have a syslog server, setup trap logging to see if there are any events that happen before it boots up.
 
Hi

I read threw the Cisco about traps and well makes me more confused ...

What do i suppose to look for or what should it send to me
when it goes down ...

The Cisco documentation tells me that not always is vise to
use traps since maybe ant an crash it might not be able to send any usefull information and siggest to look for the crashfilñe info in the flash file instead ...

Have you tried that or can i understand it wrong ...

Matt
 
What is the output of "sh enviro all"?

This could be a bad power supply, it could be a bad UPS, etc. It's also possible this could be a software bug or even bad memory.

Do your logs show any "traceback" entries? Could you post the log?

CCNP, CCDP
 
router 1234#show logging
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes, 0 overruns)
Console logging: level debugging, 28 messages logged
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 28 messages logged
Logging Exception size (4096 bytes)
Trap logging: level informational, 32 message lines logged

Log Buffer (20000 bytes):

00:00:14: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up
00:00:15: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to down
00:00:15: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to down
00:00:16: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink2, changed state to down
00:00:16: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel0, changed state to down
00:00:16: %SYS-5-CONFIG_I: Configured from memory by console
00:00:16: %LINK-3-UPDOWN: Interface Serial0/0:0, changed state to down
00:00:16: %LINK-3-UPDOWN: Interface Serial0/1:0, changed state to down
00:00:16: %LINK-3-UPDOWN: Interface Serial0/2:0, changed state to down
00:00:16: %LINK-3-UPDOWN: Interface Serial0/3:0, changed state to down
00:00:17: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0:0, changed state to down
00:00:17: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1:0, changed state to down
00:00:17: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2:0, changed state to down
00:00:17: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/3:0, changed state to down
00:00:18: %SYS-5-RESTART: System restarted --
Cisco Internetwork Operating System Software
IOS (tm) 3600 Software (C3640-JK9O3S-M), Version 12.2(19a), RELEASE SOFTWARE (fc2)
Copyright (c) 1986-2003 by cisco Systems, Inc.
Compiled Mon 29-Sep-03 23:45 by pwade
00:00:18: %SNMP-5-COLDSTART: SNMP agent on host router1234 is undergoing a cold start
00:00:18: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
00:00:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to down
00:00:21: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
00:00:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel0, changed state to up
00:00:29: %CONTROLLER-5-UPDOWN: Controller T1 0/1, changed state to up
00:00:30: %CONTROLLER-5-UPDOWN: Controller T1 0/0, changed state to up
00:00:30: %LINK-3-UPDOWN: Interface Serial0/1:0, changed state to up
00:00:30: %LINK-3-UPDOWN: Interface Multilink1, changed state to up
00:00:30: %LINK-3-UPDOWN: Interface Serial0/0:0, changed state to up
00:00:31: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1:0, changed state to up
00:00:31: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to up
00:00:31: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0:0, changed state to up

This is the logg right now some days after the system restart but i will likely get an chance another day in a not to distant future(1 week more approx).


Question the crashinfo file located on flash file could be of use dont you think ...

matt
 
router1234#show environment all
Power Supply:

Redundant Power System is not present.


Board Temperature:

normal.

matt
 
Loggs from after an crash or reboot todyay oct. 27...


router#show version
Cisco Internetwork Operating System Software
IOS (tm) 3600 Software (C3640-JK9O3S-M), Version 12.2(19a), RELEASE SOFTWARE (fc2)
Copyright (c) 1986-2003 by cisco Systems, Inc.
Compiled Mon 29-Sep-03 23:45 by pwade
Image text-base: 0x60008930, data-base: 0x615DA000

ROM: System Bootstrap, Version 11.1(7)AX [kuong (7)AX], EARLY DEPLOYMENT RELEASE SOFTWARE (fc2)

router uptime is 43 minutes
System returned to ROM by power-on
System restarted at 17:55:22 CDT Wed Oct 27 2010
System image file is "flash:c3640-jk9o3s-mz.122-19a.bin"


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:

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

cisco 3640 (R4700) processor (revision 0x00) with 125952K/5120K bytes of memory.
Processor board ID 05247830
R4700 CPU at 100Mhz, Implementation 33, Rev 1.0
Channelized E1, Version 1.0.
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
Primary Rate ISDN software, Version 1.1.
1 FastEthernet/IEEE 802.3 interface(s)
4 Serial network interface(s)
2 Channelized E1/PRI port(s)
2 Channelized T1/PRI port(s)
DRAM configuration is 64 bits wide with parity disabled.
125K bytes of non-volatile configuration memory.
16384K bytes of processor board System flash (Read/Write)

Configuration register is 0x2102

router#show environment all
Power Supply:

Redundant Power System is not present.


Board Temperature:

normal.


router#show logging
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes, 0 overruns)
Console logging: level debugging, 26 messages logged
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 26 messages logged
Logging Exception size (4096 bytes)
Trap logging: level informational, 30 message lines logged

Log Buffer (20000 bytes):

00:00:14: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up
00:00:15: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, chang ed state to down
00:00:15: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed st ate to down
00:00:16: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink2, changed st ate to down
00:00:16: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel0, changed state to down
00:00:16: %SYS-5-CONFIG_I: Configured from memory by console
00:00:16: %LINK-3-UPDOWN: Interface Serial0/0:0, changed state to down
00:00:16: %LINK-3-UPDOWN: Interface Serial0/1:0, changed state to down
00:00:16: %LINK-3-UPDOWN: Interface Serial0/2:0, changed state to down
00:00:16: %LINK-3-UPDOWN: Interface Serial0/3:0, changed state to down
00:00:17: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0:0, changed s tate to down
00:00:17: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1:0, changed s tate to down
00:00:17: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2:0, changed s tate to down
00:00:18: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/3:0, changed state to down
00:00:18: %SYS-5-RESTART: System restarted --
Cisco Internetwork Operating System Software
IOS (tm) 3600 Software (C3640-JK9O3S-M), Version 12.2(19a), RELEASE SOFTWARE (fc2)
Copyright (c) 1986-2003 by cisco Systems, Inc.
Compiled Mon 29-Sep-03 23:45 by pwade
00:00:18: %SNMP-5-COLDSTART: SNMP agent on host router is undergoing a cold start
00:00:18: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
00:00:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel0, changed state to up
00:00:29: %CONTROLLER-5-UPDOWN: Controller T1 0/1, changed state to up
00:00:30: %CONTROLLER-5-UPDOWN: Controller T1 0/0, changed state to up
00:00:30: %LINK-3-UPDOWN: Interface Serial0/1:0, changed state to up
00:00:30: %LINK-3-UPDOWN: Interface Multilink1, changed state to up
00:00:31: %LINK-3-UPDOWN: Interface Serial0/0:0, changed state to up
00:00:31: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/1:0, changed state to up
00:00:31: %LINEPROTO-5-UPDOWN: Line protocol on Interface Multilink1, changed state to up
00:00:32: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0:0, changed state to up
router#


matt
 
The logs on the router will not tell you happened before the reboot. You need to enable configure a syslog server and check those logs. If it is a trackback or something similar that is causing it you should be able to see that.

Worst case, you could hook up a laptop or such to the serial port and see what the router displays on the screen before the reboot.
 
Hi

Is severity warning good enough and facility is local 7 or how do i know ...

matt
 
Hi

this is the best way to configure sending of data when something happens ...

config terminal
loggin time ... local time
logging trap warning
logging xxx.xxx.xxx.xxx(Server to send loggs to )
logging on
end


matthias
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top