Cisco C6807-XL rommon mode

[jeremy21t]

I am configuring two Cisco 6808-XL core switch in VSS mode. The secondary switch enters into rommon mode.

I have tried changing the reg-no 0x2102 but it didn't help. Any help Please. 

[Reza Sharifi]

Does the second switch have the same exact IOS as the primary? Can you console to it and verify the IOS exist?

HTH

[VHACHY442]

If you issue the remote command to verify the config-register what does it show for the standby chassis?

[balaji.bandi]

Couple of questions :

before joining them VSS they were able to boot and working.

both are same version of code of IOS

is this live environment ?

[Leo Laohoo]

Maybe the secondary unit has the wrong IOS version?
Console into this unit and reboot. Post the entire boot-up process.

[jeremy21t]

Hi all 

Thank you for your quick reply. Sorry for the late response, I couldn't get access to the Switch. Below are information's as you requested.    

• The Two switch have the same IOS version
• The config-register is changed back to 0x2100 after i changed to 0x2102
• Below is the entire boot up process

rommon 1 >
rommon 1 >
rommon 1 >
rommon 1 >
rommon 1 >
rommon 1 >
rommon 1 > boot

bootdisk:%s72044-atafslib-m: Digitally Signed Release Software with key version A

Initializing ATA monitor library...
string is bootdisk:s2t54-ipbasek9_npe-mz.SPA.155-1.SY.bin

bootdisk:%s72044-atafslib-m: Digitally Signed Release Software with key version A

Initializing ATA monitor library...

bootdisk:s2t54-ipbasek9_npe-mz.SPA.155-1.SY.bin: Digitally Signed Release Software with key version A

Self extracting the image... [OK]
Self decompressing the image : #################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################### [OK]
*** No sreloc section
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, s2t54 Software (s2t54-IPBASEK9_NPE-M), Version 15.5(1)SY, RELEASE SOFTWARE (fc6)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2017 by Cisco Systems, Inc.
Compiled Sun 30-Apr-17 01:23 by prod_rel_team

fw_board_init : Firmware init 1 calling now
fw_board_init : Firmware init 1 completed
This is a VSS capable switch.
VSL ports can be configured in slot: 3

fw_board_init : Firmware init 2 calling now
fw_board_init : Firmware init 2 completed

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use.----------------I removed legal Contents -----------

cisco C6807-XL (M8572) processor (revision ) with 1785856K/262144K bytes of memory.
Processor board ID FGE21071MKW
CPU: MPC8572_E, Version: 2.2, (0x80E80022)
CORE: E500, Version: 3.0, (0x80210030)
CPU:1500MHz, CCB:600MHz, DDR:600MHz
L1: D-cache 32 kB enabled
I-cache 32 kB enabled

Last reset from s/w reset
1 Virtual Ethernet interface
3 Gigabit Ethernet interfaces
34 Ten Gigabit Ethernet interfaces
2543K bytes of non-volatile configuration memory.

Press RETURN to get started!

Firmware compiled 30-Apr-17 01:23 by sabind Build [26112]

*Oct 11 07:42:22.851: %PFREDUN-6-ACTIVE: Initializing as ACTIVE processor for this switch

*Oct 11 07:42:42.423: SP: Currently running ROMMON from S (Gold) region
*Oct 11 07:42:46.431: %SYS-5-CONFIG_I: Configured from memory by console
*Oct 11 07:42:47.939: %OIR-6-INSPS: Power supply inserted in slot 1
*Oct 11 07:42:47.971: %C6KPWR-4-PSOK: power supply 1 turned on.
*Oct 11 07:42:48.399: %OIR-6-INSPS: Power supply inserted in slot 2
*Oct 11 07:42:48.431: %C6KPWR-4-PSOK: power supply 2 turned on.
*Oct 11 07:42:48.591: %SYS-5-RESTART: System restarted --

Cisco IOS Software, s2t54 Software (s2t54-IPBASEK9_NPE-M), Version 15.5(1)SY, RELEASE SOFTWARE (fc6)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2017 by Cisco Systems, Inc.
Compiled Sun 30-Apr-17 01:23 by prod_rel_team
*Oct 11 07:42:50.751: %SYS-6-BOOTTIME: Time taken to reboot after reload = 609 seconds
*Oct 11 07:42:51.075: %OIR-6-INSPC: Power converter inserted in slot 1
*Oct 11 07:42:52.119: %OIR-6-INSPC: Power converter inserted in slot 2
*Oct 11 07:42:52.299: %C6KENV-4-FANHPMODE: Fan-tray 1 is operating in high power mode
*Oct 11 07:43:00.479: %FABRIC-5-FABRIC_MODULE_ACTIVE: The Switch Fabric Module in slot 3 became active.
*Oct 11 07:43:05.307: %DIAG-6-RUN_MINIMUM: Module 3: Running Minimal Diagnostics...
Router>
Router>
Router>
Router>
Router>
Router>

Router> ----------- //----After a few minutes it enters into rommon mode automaticaly-------

 
*Oct 11 07:44:13.839: Dumping show ibc output to bootflash/bootdisk

%Software-forced reload

*Oct 11 07:44:37.935: %DIAG-3-MAJOR: Module 3: Online Diagnostics detected a Major Error. Please use 'show diagnostic result <target>' to see test results.
*Oct 11 07:44:37.935: %CONST_DIAG-3-BOOTUP_TEST_FAIL: Module 3: TestLoopback failed on port(s) 1-5
*Oct 11 07:44:37.935: %CONST_DIAG-3-BOOTUP_TEST_FAIL: Module 3: TestL2CTSLoopback failed on port(s) 1-5
*Oct 11 07:44:37.935: %CONST_DIAG-3-BOOTUP_TEST_FAIL: Module 3: TestNewIndexLearn failed
*Oct 11 07:44:37.935: %CONST_DIAG-3-BOOTUP_TEST_FAIL: Module 3: TestDontConditionalLearn failed
*Oct 11 07:44:37.935: %CONST_DIAG-3-BOOTUP_TEST_FAIL: Module 3: TestIPv4FibShortcut failed
*Oct 11 07:44:37.935: %CONST_DIAG-3-BOOTUP_TEST_FAIL: Module 3: TestL3Capture2 failed
*Oct 11 07:44:37.935: %CONST_DIAG-3-BOOTUP_TEST_FAIL: Module 3: TestMPLSFibShortcut failed
*Oct 11

07:44:39 UTC Thu Oct 11 2018: Unexpected exception to CPU: vector 1500, PC = 0x53003D4 , LR = 0x530036C
-Traceback= 0x53003D4z 0x8E0A8A4z 0x8C0E9CCz 0x8C11114z 0x504B3ECz 0x5F87024z 0x5F89A24z 0x4E9D1C4z 0x5F9AC50z 0x53019A4z 0x52FBD74z
Traceback sent to CMP
CPU Register Context:
MSR = 0x00029200 CR = 0x24020022 CTR = 0x078A3CAC XER = 0x20000000
R0 = 0x0530036C R1 = 0x572D7A68 R2 = 0xFFF7FFF7 R3 = 0x529689F4
R4 = 0x00000007 R5 = 0x0000000A R6 = 0x00000027 R7 = 0x00000007
R8 = 0x0000002C R9 = 0x00000000 R10 = 0x00000A50 R11 = 0x078A3CAC
R12 = 0x000000E0 R13 = 0x0121F000 R14 = 0x00000000 R15 = 0x00000000
R16 = 0x00000000 R17 = 0x10B67DE8 R18 = 0x57217490 R19 = 0x00000001
R20 = 0x09D54830 R21 = 0x10B70000 R22 = 0xFFFFFFFF R23 = 0x1469E4FC
R24 = 0x00000003 R25 = 0x572D7CF4 R26 = 0x00000000 R27 = 0x57215A24
R28 = 0x09D55764 R29 = 0x0C275080 R30 = 0x572D7A88 R31 = 0x00000000

TEXT_START : 0x04100200
DATA_START : 0x0C000000File bootdisk:crashinfo_20181011-074439-UTC open failed (-1): Directory entries are corrupted, please format the disk
File bootdisk:crashinfo_20181011-074439-UTC open failed (-1): Directory entries are corrupted, please format the disk
File disk0:crashinfo_20181011-074439-UTC Device Error :No such device
File bootdisk:crashinfo_20181011-074439-UTC open failed (-1): Directory entries are corrupted, please format the disk
File disk0:crashinfo_20181011-074439-UTC Device Error :No such device
07:44:37.935: %CONST_DIAG-3-BOOTUP_TEST_FAIL: Module 3: TestNATFibShortcut failed
*Oct 11 07:44:37.935: %CONST_DIAG-3-BOOTUP_TEST_FAIL: Module 3: TestAclPermit failed
*Oct 11 07:44:37.935: %CONST_DIAG-3-BOOTUP_TEST_FAIL: Module 3: TestAclRedirect failed
*Oct 11 07:44:37.935: %CONST_DIAG-3-BOOTUP_TEST_FAIL: Module 3: TestRBAcl failed
*Oct 11 07:44:37.935: %CONST_DIAG-3-BOOTUP_TEST_FAIL: Module 3: TestQos failed
*Oct 11 07:44:37.935: %CONST_DIAG-3-BOOTUP_TEST_FAIL: Module 3: TestEgressSpan failed
*Oct 11 07:44:37.935: %CONST_DIAG-3-BOOTUP_TEST_FAIL: Module 3: TestNetflowShortcut failed
*Oct 11 07:44:37.935: %CONST_DIAG-3-BOOTUP_TEST_FAIL: Module 3: TestInbandEdit failed
*Oct 11 07:44:37.935: %CONST_DIAG-3-BOOTUP_TEST_FAIL: Module 3: TestFabricExternalSnake failed
*Oct 11 07:44:37.935: %CONST_DIAG-3-BOOTUP_TEST_FAIL: Module 3: TestFabricVlanLoopback failed
*Oct 11 07:44:38.247: %HA_EM-6-LOG: Mandatory.go_bootup.tcl: GOLD EEM TCL policy for boot up diagnostic
*Oct 11 07:44:38.263: %C6KENV-4-ADJACENT_SL
*** System received a Software Forced Crash ***
signal= 0x17, code= 0x1500, context= 0xe07ba34
PC = 0x53003d4, Vector = 0x1500, SP = 0x572d7a68
rommon 2 >
rommon 2 >
rommon 2 >
rommon 2 >
rommon 2 >
rommon 2 >

[VHACHY442]

I see the following in the text info:
DATA_START : 0x0C000000File bootdisk:crashinfo_20181011-074439-UTC open failed (-1): Directory entries are corrupted, please format the disk
File bootdisk:crashinfo_20181011-074439-UTC open failed (-1): Directory entries are corrupted, please format the disk
File disk0:crashinfo_20181011-074439-UTC Device Error :No such device
File bootdisk:crashinfo_20181011-074439-UTC open failed (-1): Directory entries are corrupted, please format the disk
File disk0:crashinfo_20181011-074439-UTC Device Error :No such device

It looks like you will need to format the bootdisk and re-install the image. Are you able to issue dir slavebootdisk: and see the directory? Verify the same image is present on the slavebootdisk. If so then you should be able to format the bootdisk: and then copy the image from the slavebootdisk: back to the bootdisk:

[Reza Sharifi]

Usually, tracebacks are a sign of software bugs.  You may want to load a different version in both sups and test again.

Also, you may want to open a TAC case as they might be familiar with the issue.

HTH

[Leo Laohoo]

Look at the "choice" of IOS being used, it is 15.5(1)SY. Look at the last two letters: SY. There is no number after the last letter. This means a version "0", which is synonymous to "a very buggy first release".
Recommendation is, as what Reza said, raise a TAC Case or upgrade the IOS.

[jeremy21t]

Thank you all v. much for your help.

I will do as you suggested and get back to you with the result. I have selected IOS version 15.5.1SY1(ED)

I think CSCur78068 is the bug code for the same problem.

[balaji.bandi]

If you are not very particular about 15.5.1SY1(ED)

why not try below version : 15.4(1)SY

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/15-4SY/release_notes/release_notes_15_4_SY.html

[jeremy21t]

Thanks balaji.bandi 

No special reason. I choose 15.5.1SY(ED) because i saw on Cisco software download page this version got a star and i thought it is recommended.  Does it have a problem. Isn't it stable?. 

https://software.cisco.com/download/home/283933147/type/280805680/release/15.2.1-SY6

[Leo Laohoo]

I never (recommend anyone) pick an IOS version just because it has a "gold star".

[jeremy21t]

Hi LEO

The switch came with IOS 15.5.1(SY) and it has bug. I read the release note for 15.5.1(SY)1 it states as it has fixed the bugs. Kindly suggest me a stable IOS version ?

[balaji.bandi]

I would choose the version of IOS which is compatible and feature looking to deploy in the environment.

As long the features supported and  no bugs reported, any IOS stable is good to go to Live.

Suggest to read release notes before deploying in Live environment.