6506 chassis module issue

[waqas.ahmed.1987]

Hi everyone,

I have single 6506 chassis with two supervisor engineers (WS-X6K-SUP2-2GE ). Post power shutdown one of  the engine is not appearing in inventory.

Below is the console output

CoreSwitch> (enable) session 15
Module 15 is not installed.
CoreSwitch> (enable)

Question:

What is the command to reload the whole chassis?

Can we reseat the module without shutting the chassis? Is it hot swappable

Any suggestions is appreciated.

[Reza Sharifi]

Hi,

Can you post the output of "sh redundancy"

Module 15 is not installed.

If this is a 6506, there is no module 15. You only have 6 blades.

HTH

[waqas.ahmed.1987]

RSM2#sho redundancy
Designated Router: 2 Non-designated Router: 0

Redundancy Status: designated

Config Sync AdminStatus : disabled

Config Sync RuntimeStatus: disabled

Single Router Mode AdminStatus : disabled

Single Router Mode RuntimeStatus: disabled

Single Router Mode transition timer : 120 seconds

[Leo Laohoo]

Sup2 is CatOS.  

The command to reboot the entire chassis is "reload".

[Giuseppe Larosa]

Hello @waqas.ahmed.1987 ,

you have sup2 with MSFC2 that is in hybrid mode CatOS on SUp2 and IOS on MSFC2

the session 15 is used to access the MSFC.

as suggested you should reload the chassis from supervisor prompt.

If even this does not work you need to make the other Sup2 the master in the hope that its MSFC2 is working.

I am not sure but the MSFC on the standby supervisor can be reached using session 16 if I correctly remember

>> Single Router Mode RuntimeStatus: disabled

This means each MSFC has its own addresses on each of the SVIs so the system may be able to work using MSFC on standby supervisor if it is alive and working.

Edit:

in CatOS use

show module

check the state of the submodules in the last part of the output it should list the MSFC2

Hope to help

Giuseppe

[waqas.ahmed.1987]

not showing 15 .

.

output

CoreSwitch> (enable) sho module
Mod Slot Ports Module-Type Model Sub Status
--- ---- ----- ------------------------- ------------------- --- --------
1 1 2 1000BaseX Supervisor WS-X6K-SUP2-2GE yes ok
2 2 2 1000BaseX Supervisor WS-X6K-SUP2-2GE yes standby
16 2 1 Multilayer Switch Feature WS-F6K-MSFC2 no ok
3 3 8 1000BaseX Ethernet WS-X6408A-GBIC no ok
4 4 8 1000BaseX Ethernet WS-X6408A-GBIC no ok

Mod Module-Name Serial-Num
--- -------------------- -----------
1 SAL062722DD
2 SAL062722CB
16 SAL062723XL
3 SAL06251CX2
4 SAL062410PF

Mod MAC-Address(es) Hw Fw Sw
--- -------------------------------------- ------ ---------- -----------------
1 00-09-12-43-c6-7a to 00-09-12-43-c6-7b 3.7 7.1(1) 7.2(2)
00-09-12-43-c6-78 to 00-09-12-43-c6-79
00-0a-42-3e-82-40 to 00-0a-42-3e-86-3f
2 00-05-74-86-0f-16 to 00-05-74-86-0f-17 3.7 7.1(1) 7.2(2)
00-05-74-86-0f-14 to 00-05-74-86-0f-15
16 00-06-52-60-cb-40 to 00-06-52-60-cb-7f 2.3 12.1(11b)E 12.1(11b)E
3 00-09-12-7a-29-e8 to 00-09-12-7a-29-ef 2.1 5.4(2) 7.2(2)
4 00-09-e8-f8-3c-00 to 00-09-e8-f8-3c-07 2.1 5.4(2) 7.2(2)

Mod Sub-Type Sub-Model Sub-Serial Sub-Hw
--- ----------------------- ------------------- ----------- ------
1 L3 Switching Engine II WS-F6K-PFC2 SAL062722MV 3.2
2 L3 Switching Engine II WS-F6K-PFC2 SAL062722MA 3.2

[Giuseppe Larosa]

Hello @waqas.ahmed.1987 ,

ok the show module tells us that both the MSFC2 daughter cards are present

Try to use session 16 to see if you are able to connect to the MSFC installed on the standby supervisor.

>> 16 2 1 Multilayer Switch Feature WS-F6K-MSFC2 no ok

this is alive

Likely the MSFC on primary supervisor is stucked in ROMMON and did not complete the boot process.

Hope to help

Giuseppe

[waqas.ahmed.1987]

yes i can connect to session 16, on Sup2 . So now we will switchover from Sup Engine2 to active then we can restart Supervisor engine1

Just to confirm does this requires any maintenance window or downtime?

[Giuseppe Larosa]

Hello @waqas.ahmed.1987 ,

>> Just to confirm does this requires any maintenance window or downtime?

It is better to schedule a maintenance window if this device is in production network.

MSFC2 on "slot" 16 should be doing its job allowing for inter Vlan routing to happen if configured for doing so.

Hope to help

Giuseppe