Cisco Catalyst 4500 Series, Software Configuration Manual

Page: 527 / 2086

12-9
Catalyst 4500 Series Switch, Cisco IOS Software Configuration Guide - Cisco IOS XE 3.9.xE and IOS 15.2(5)Ex
Chapter 12 Configuring Supervisor Engine Redundancy Using RPR and SSO on Supervisor Engine 7-E, Supervisor
Configuring Supervisor Engine Redundancy
RF debug mask = 0
This example shows how to change the system configuration from RPR to SSO mode:
Switch(config)# redundancy
Switch(config-red)# mode
Switch(config-red)#
mode sso
Changing to sso mode will reset the standby. Do you want to continue?[confirm]
Switch(config-red)# end
Switch#
*Aug 1 13:11:16: %C4K_REDUNDANCY-3-COMMUNICATION: Communication with the peer Supervisor
has been lost
*Aug 1 13:11:16: %C4K_REDUNDANCY-3-SIMPLEX_MODE: The peer Supervisor has been lost
This example shows how to change the system configuration from SSO to RPR mode:
Switch(config)# redundancy
Switch(config-red)# mode rpr
Changing to rpr mode will reset the standby. Do you want to continue?[confirm]
Switch(config-red)# end
*Aug 1 13:11:16: %C4K_REDUNDANCY-3-COMMUNICATION: Communication with the peer Supervisor
has been lost
*Aug 1 13:11:16: %C4K_REDUNDANCY-3-SIMPLEX_MODE: The peer Supervisor has been lost
Virtual Console for Standby Supervisor Engine
Catalyst 4500 series switches can be configured with 2 supervisor engines to provide redundancy. When
the switch is powered, one of the supervisor engines becomes active and remains active until a
switchover occurs. The other supervisor engine remains in standby mode.
Each supervisor engine has its own console port. Access to the standby supervisor engine is possible
only through the console port of the standby supervisor engine. Therefore, you must connect to the
standby console to access, monitor or debug the standby supervisor.
Virtual Console for Standby Supervisor Engine enables you to access the standby console from the active
supervisor engine without requiring a physical connection to the standby console. It uses IPC over
EOBC to communicate with the standby supervisor engine and thus emulate the standby console on the
active supervisor engine. Only one standby console session is active at any time.
The Virtual Console for Standby Supervisor Engine allows users who are logged onto the active
supervisor engine to remotely execute
show commands on the standby supervisor engine and view the
results on the active supervisor engine. Virtual Console is available only from the active supervisor
engine.
You can access the standby virtual console from the active supervisor engine with the attach module ,
session module , or remote login commands on the active supervisor engine. You must be in privilege
EXEC mode (level 15) to run these commands to access the standby console.
Once you enter the standby virtual console, the terminal prompt automatically changes to
hostname -standby-console where hostname is the configured name of the switch. The prompt is restored
to the original setting when you exit the virtual console.
You exit the virtual console with the exit or quit commands. When the inactivity period of the terminal
on the active supervisor engine where you logged in exceeds the configured idle time, you are
automatically logged out of the terminal on the active supervisor engine. In this instance, the virtual
console session is also terminated. Virtual console session is also automatically terminated when the
standby is rebooted. After the standby boots up, you need to create another virtual console session.
To log in to the standby supervisor engine using a virtual console, do the following:
Switch#
session module 4