cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
793
Views
15
Helpful
6
Replies

standy supervisor rebooting

sblackman68
Level 1
Level 1

Hi, We have recently encountered the standby supervisor rebooting for no apparent reason WS-C6509-E (Chassis), VS-S720-10G (Module-SUP).  The cat is running software version 12.2(33)SXI7.  Logs are as follows-  

 

s217124-das1.lo4#sh logging
Jan 11 23:04:52.971 GMT: %OIR-SP-3-PWRCYCLE: Card in module 6, is being power-cycled 'Module reset'
Jan 11 23:04:56.895 GMT: %SNMP-5-MODULETRAP: Module 6 [Down] Trap
Jan 11 23:14:18.044 GMT: %FABRIC-SP-5-FABRIC_MODULE_BACKUP: The Switch Fabric Module in slot 6 became standby
Jan 11 23:14:35.680 GMT: %DIAG-SP-6-RUN_MINIMUM: Module 6: Running Minimal Diagnostics...
Jan 11 23:14:37.184 GMT: %DIAG-SP-6-DIAG_OK: Module 6: Passed Online Diagnostics
Jan 11 23:14:39.752 GMT: %SNMP-5-MODULETRAP: Module 6 [Up] Trap
Jan 11 23:14:20.983: %DIAG-SPSTBY-6-RUN_MINIMUM: Module 6: Running Minimal Diagnostics...
Jan 11 23:14:35.532: %DIAG-SPSTBY-6-DIAG_OK: Module 6: Passed Online Diagnostics

 

================================================================================

 

Any help would be great!

 

Cheers,

Scott.

6 Replies 6

Mark Malone
VIP Alumni
VIP Alumni
Hi
is it creating a crash file ? check the flash for it
is there any more to those logs ?

all thats telling you above is it came backonline after reload ,

what does show redundancy say when it went down ?

Hi, Many thanks for your reply, below is the redundancy is as follows:-

 

And this is current uptime of the both the SUP modules:

 

s217124-das1.lo4#show redundancy

Redundant System Information :

------------------------------

       Available system uptime = 3 years, 13 weeks, 3 days, 17 hours, 17 minutes

Switchovers system experienced = 0

              Standby failures = 2

        Last switchover reason = none

 

                 Hardware Mode = Duplex

    Configured Redundancy Mode = sso

     Operating Redundancy Mode = sso

              Maintenance Mode = Disabled

                Communications = Up

 

Current Processor Information :

-------------------------------

               Active Location = slot 5

        Current Software state = ACTIVE

       Uptime in current state = 3 years, 13 weeks, 3 days, 17 hours, 16 minutes

                 Image Version = Cisco IOS Software, s72033_rp Software (s72033_rp-ADVIPSERVICESK9_WAN-M), Version 12.2(33)SXI7, RELEASE SOFTWARE (fc1)

Technical Support: http://www.cisco.com/techsupport

Copyright (c) 1986-2011 by Cisco Systems, Inc.

Compiled Mon 18-Jul-11 05:49 by prod_rel_team

                          BOOT = disk0:s72033-advipservicesk9_wan-mz.122-33.SXI7.bin,1;sup-bootdisk:s72033-advipservicesk9_wan-mz.122-33.SXI7.bin,1;

                   CONFIG_FILE =

                       BOOTLDR =

        Configuration register = 0x2102

 

Peer Processor Information :

----------------------------

              Standby Location = slot 6

        Current Software state = STANDBY HOT

       Uptime in current state = 1 week, 2 days, 16 hours, 3 minutes

                 Image Version = Cisco IOS Software, s72033_rp Software (s72033_rp-ADVIPSERVICESK9_WAN-M), Version 12.2(33)SXI7, RELEASE SOFTWARE (fc1)

Technical Support: http://www.cisco.com/techsupport

Copyright (c) 1986-2011 by Cisco Systems, Inc.

Compiled Mon 18-Jul-11 05:49 by prod_rel_team

                          BOOT = disk0:s72033-advipservicesk9_wan-mz.122-33.SXI7.bin,1;sup-bootdisk:s72033-advipservicesk9_wan-mz.122-33.SXI7.bin,1;

                   CONFIG_FILE =

                       BOOTLDR =

        Configuration register = 0x2102

Did it only reboot once or has it happened several times ?
If its a once off it may not be an issue it can happen from softwrae but if its happening several times you have a bad BUG or else dodgy hardware

That looks good above but we need to see if there's something that will show what happened

I presume after a week the logs are over written on the switch itself , do you have a syslog server setup that the switches send logs too , the logs from that day it rebooted ?

also check the filesystems see if theres any crash file , there usually stored in slave file system but you can see them all by running this command ... dir all-filesystems
Then check if you see anything from the date it happened that says crash file , that file may contain what happened , as it records the issue and dumps it into a crash file for TAC to check

Hi Yes, good point.  I have requested a show tech, which hopefully I can put through the CLI advisor??  Cheers for you help, will let you know. :-)

 

Cheers,

 

Scott.

Cool i have the analyzer setup here too so if you cant get it working just post the tech and ill post what the analyzer gives back when its ran

Thanks Mark, appreciate it.

 

Scott.

 

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card