cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3002
Views
0
Helpful
1
Replies

9800 Redundancy Peer State Disabled

aklingaman
Level 1
Level 1

Catalyst 9800-L-F Ver. 17.03.03 - Installation Mode: BUNDLE

 

I was able to finally connect the two controllers. As soon as I did, #2 became untouchable, for lack of better words. Cannot console or ping the device's management port any longer.

 

Reloading #1 showed this message during startup:

Chassis number is 1
All chassis in the stack have been discovered. Accelerating discovery
Nov 17 13:54:44.739: %PMAN-3-PROC_EMPTY_EXEC_FILE: R0/0: pvp: Empty executable used for process bt_logger
Nov 17 13:54:46.293: %PMAN-3-PROC_EMPTY_EXEC_FILE: R0/0: pvp: Empty executable used for process bt_logger
Nov 17 13:54:47.052: %PMAN-3-PROC_EMPTY_EXEC_FILE: R0/0: pvp: Empty executable used for process bt_logger
Nov 17 13:54:47.843: %BOOT-3-BOOTTIME_INCOMPATIBLE_SW_DETECTED: R0/0: issu_stack: Incompatible software detected. Details: Active's super boot mode does not match with member's subpackage boot mode. Please boot switch 2 in super mode.

 

In the WebUI, Monitoring>General>System>Redundancy shows that the Peer State is Disabled due to "Simplex Mode."

 

Both controllers should be on ver 17.03.03. Is there a way to configure #2 through #1 CLI that I'm missing? Should I disconnect their RP ports and hard reboot #2 to get back into it? They're paired in an RMI+RP type.

 

Any help appreciated.

 

1 Reply 1

Scott Fella
Hall of Fame
Hall of Fame
Your best bet is to revert back by breaking SSO. Then make sure you have both in install mode (preferred) over bundled mode. Once you make that change and both are using the same mode, then enable SSO again.
-Scott
*** Please rate helpful posts ***
Review Cisco Networking for a $25 gift card