03-10-2007 12:47 PM - edited 03-05-2019 02:49 PM
Hi,
I had install sup720 on 6509 switch, when i issued sh module i get the following:
1 24 CEF720 24 port 1000mb SFP WS-X6724-SFP SAL08342PZG
2 24 CEF720 24 port 1000mb SFP WS-X6724-SFP SAL104040MR
3 48 SFM-capable 48 port 10/100/1000mb RJ45 WS-X6548-GE-45AF SAL104145VF
4 48 SFM-capable 48 port 10/100/1000mb RJ45 WS-X6548-GE-45AF SAL10414T7Q
5 2 Supervisor Engine 720 (Active) WS-SUP720-BASE SAD08320829
6 0 Supervisor-Other Unknown Unknown
the show version is like :
IOS (tm) s72033_rp Software (s72033_rp-PS-M), Version 12.2(17d)SXB1, RELEASE SO
shutdown
FTWARE (fc2)
Cat6500 uptime is 26 minutes
Time since Cat6500 switched to active is 25 minutes
System returned to ROM by unknown reload cause - suspect boot_data[BOOT_COUNT] 0
x0, BOOT_COUNT 0, BOOTDATA 19 (SP by power-on)
System image file is "sup-bootflash:s72033-ps-mz.122-17d.SXB1.bin"
cisco WS-C6509 (R7000) processor (revision 3.0) with 458752K/65536K bytes of mem
ory.
Processor board ID SMG0834A73P
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from power-on
X.25 software, Version 3.0.0.
Bridging software.
4 Virtual Ethernet/IEEE 802.3 interface(s)
148 Gigabit Ethernet/IEEE 802.3 interface(s)
1917K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.
65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102
what iam missing.....?
Thanx
03-10-2007 10:34 PM
Hi,
Do you have some crashinfo files with you? The unknown status usually is something to do with a failure of the module, or the module is stuck up in rommon mode. Have u collected console logs from the supervisor, would be useful if you could post the logs you might have collected through the console of the faulty supervisor.
HTH
Hoogen
03-11-2007 12:39 PM
hi,
i'm don't had the crashinfo file now but i will get it soon, anyway i just did some trouble shooting, so when i install each sup72 module alone it do works fine in any solt 5 or 6. but when both sup72 is install the standby module is stuck in rommon by issuing boot in the stucked sup72 i get the following:
rommon 1 > boot
Loading image, please wait ...
Self decompressing the image :
################# [OK]
Restricted Rights Legend
cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
Cisco Internetwork Operating System Software
IOS (tm) s72033_sp Software (s72033_sp-SPV-M), Version 12.2(17d)SXB11a, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2006 by cisco Systems, Inc.
Compiled Thu 13-Apr-06 04:53 by kehsiao
Image text-base: 0x40020FBC, data-base: 0x40DD8000
00:00:03: %PFREDUN-6-STANDBY: Initializing as STANDBY processor
Firmware compiled 17-Mar-06 14:54 by integ Build [100]
00:00:04: %OIR-SP-STDBY-6-CONSOLE: Changing console ownership to route processor
System Bootstrap, Version 12.2(17r)S4, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2005 by cisco Systems, Inc.
Cat6k-Sup720/RP platform with 524288 Kbytes of main memory
Download Start
!!!!!!!!!
Download Completed! Booting the image.
Self decompressing the image :
...##### [OK]
Restricted Rights Legend
cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
Cisco Internetwork Operating System Software
IOS (tm) s72033_rp Software (s72033_rp-PK9SV-M), Version 12.2(17d)SXB11a, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2006 by cisco Systems, Inc.
Compiled Thu 13-Apr-06 04:50 by kehsiao
Image text-base: 0x40020FBC, data-base: 0x41F18000
%Software-forced reload
Unexpected exception, CPU signal 23, PC = 0x402EF6BC
-Traceback= 402EF6BC 402ED584 403D7E14 403D7E40 40470650 403C5C84 403C5CDC 40394D40 40395ADC 4034497C 40342008 40342254 402F3BB4
$0 : 00000000, AT : 420D0000, v0 : 42640000, v1 : 421D0000
a0 : 4261ADA4, a1 : 0000F100, a2 : 00000000, a3 : 41F50000
t0 : 402F4178, t1 : 3401F101, t2 : 402F4188, t3 : FFFF00FF
t4 : 402F4178, t5 : 20657863, t6 : 6F6E202C, t7 : 65747469
s0 : 00000000, s1 : 00000000, s2 : 41F70000, s3 : 5048191C
s4 : 00000040, s5 : 42660000, s6 : 0000005A, s7 : 5048191C
t8 : 00000000, t9 : 00000004, k0 : 00000000, k1 : 00000000
gp : 420D4A60, sp : 50006CA0, s8 : 00000000, ra : 402ED584
EPC : 402EF6BC, ErrorEPC : BFC1A370, SREG : 3401F103
MDLO : 00000000, MDHI : 00000006, BadVaddr : 00000000
Cause 00000024 (Code 0x9): Breakpoint exception
Writing crashinfo to bootflash:crashinfo_20070311-092900
=== Flushing messages (09:29:01 UTC Sun Mar 11 2007) ===
Buffered messages:
Queued messages:
00:00:44: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.
00:00:44: %CPU_MONITOR-3-PEER_EXCEPTION: CPU_MONITOR peer has failed due to exception , resetting [6/0]
*** System received a Software forced crash ***
signal= 0x17, code= 0x24, context= 0x426475c4
PC = 0x402f4228, SP = 0x41f6d390, RA = 0x402dbe30
Cause Reg = 0x00003820, Status Reg = 0x34018002
ch
00:00:45: %SYS-SP-STDBY-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output.
00:00:45: %OIR-SP-STDBY-6-CONSOLE: Changing console ownership to switch processor
*** System received a Software forced crash ***
signal= 0x17, code= 0x24, context= 0x43bf84e4
PC = 0x40143d40, Cause = 0x1820, Status Reg = 0x34008002
rommon 2 >
System Bootstrap, Version 8.4(2) Release
Copyright (c) 1994-2005 by cisco Systems, Inc.
Cat6k-Sup720/SP processor with 524288 Kbytes of main memory
rommon 1 >
regards
03-11-2007 02:00 PM
I can see that you are running different ios releases on the Sup720 modules. This is known to cause problems.
Please try loading the same software on both modules and see what happens.
03-10-2007 11:41 PM
Check this document for info on the error:
http://www.cisco.com/en/US/products/hw/switches/ps700/products_tech_note09186a00801751d7.shtml
03-10-2007 11:42 PM
It seems like your Sup engine is not booted properly. There is some issue with the Sup engine. Please connect a console to it and see if it is at rommon status. Please check the link below for recovering it:
HTH,
-amit singh
02-05-2010 03:18 AM
Any Solution to this problem .. ???
02-05-2010 04:48 AM
As mentioned above, the second Supervisor Engine fails to come on line because the redundancy mode is enhanced high system availability (EHSA), by default. The standby Supervisor Engine fails to negotiate with the active Supervisor Engine.because they are not using same Software level.
http://www.cisco.com/en/US/products/hw/switches/ps700/products_tech_note09186a00801751d7.shtml
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