Catalyst 4500 Series Switch Cisco IOS Software Configuration Guide, 12.2(31)SGA

Configuring Supervisor Engine Redundancy Using RPR and SSO

Catalyst 4500 series switches allow a redundant supervisor engine to take over if the active supervisor engine fails. In software, supervisor engine redundancy is enabled by running the redundant supervisor engine in route processor redundancy (RPR) or stateful switchover (SSO) operating mode.

Note The minimum ROMMON requirement for running SSO is Cisco IOS Release 12.1(20r)EW1 or Cisco IOS Release 12.2(20r)EW1.

This chapter describes how to configure supervisor engine redundancy on the Catalyst 4507R and Catalyst 4510R switches.

Note For information on Cisco nonstop forwarding (NSF) with SSO, see Chapter 9, "Configuring Cisco NSF with SSO Supervisor Engine Redundancy."

This chapter contains these major sections:

•Understanding Supervisor Engine Redundancy

•Understanding Supervisor Engine Redundancy Synchronization

•Supervisor Engine Redundancy Guidelines and Restrictions

•Configuring Supervisor Engine Redundancy

•Performing a Manual Switchover

•Performing a Software Upgrade

•Manipulating Bootflash on the Redundant Supervisor Engine

Note For complete syntax and usage information for the switch commands used in this chapter, refer to the Catalyst 4500 Series Switch Cisco IOS Command Reference and related publications at this location:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124cr/index.htm.

Understanding Supervisor Engine Redundancy

These sections describe supervisor engine redundancy:

•Overview

•RPR Operation

•SSO Operation

•"Understanding Supervisor Engine Redundancy Synchronization" section

Overview

With supervisor engine redundancy enabled, if the active supervisor engine fails or if a manual switchover is performed, the redundant supervisor engine becomes the active supervisor engine. The redundant supervisor engine has been automatically initialized with the startup configuration of the active supervisor engine, shortening the switchover time (30 seconds or longer in RPR mode, depending on the configuration; subsecond in SSO mode).

In addition to the reduced switchover time, supervisor engine redundancy supports the following:

•Online insertion and removal (OIR) of the redundant supervisor engine.

Supervisor engine redundancy allows OIR of the redundant supervisor engine for maintenance. When the redundant supervisor engine is inserted, the active supervisor engine detects its presence, and the redundant supervisor engine boots into a partially-initialized state in RPR mode and a fully-initialized state in SSO mode.

•Software upgrade. (See the "Performing a Software Upgrade" section.)

To minimize down time during software changes on the supervisor engine, load the new image on the redundant supervisor engine, and conduct a switchover.

When power is first applied to a switch, the supervisor engine that boots first becomes the active supervisor engine and remains active until a switchover occurs.

A switchover will occur when one or more of the following events take place:

•The active supervisor engine fails (due to either hardware or software function) or is removed.

•A user forces a switchover.

•A user reloads the active supervisor engine.

Table 8-1 provides information about chassis and supervisor engine support for redundancy.

RPR Operation

RPR is supported in Cisco IOS Release 12.2(12c)EW and later releases. When a redundant supervisor engine runs in RPR mode, it starts up in a partially-initialized state and is synchronized with the persistent configuration of the active supervisor engine.

Note Persistent configuration includes the following components: startup-config, boot variables, config-register, and VLAN database.

The redundant supervisor engine pauses the startup sequence after basic system initialization, and in the event that the active supervisor engine fails, the redundant supervisor engine becomes the new active supervisor engine.

In a supervisor engine switchover, traffic is disrupted because in the RPR mode all of the physical ports restart since there is no state maintained between supervisor engines relating to module types and statuses. When the redundant supervisor engine completes its initialization, it will read hardware information directly from the module.

SSO Operation

SSO is supported in Cisco IOS Release 12.2(20)EWA and later releases. When a redundant supervisor engine runs in SSO mode, the redundant supervisor engine starts up in a fully-initialized state and synchronizes with the persistent configuration and the running configuration of the active supervisor engine. It subsequently maintains the state on the protocols listed below, and all changes in hardware and software states for features that support stateful switchover are kept in sync. Consequently, it offers zero interruption to Layer 2 sessions in a redundant supervisor engine configuration.

Because the redundant supervisor engine recognizes the hardware link status of every link, ports that were active before the switchover will remain active, including the uplink ports. However, because uplink ports are physically on the supervisor engine, they will be disconnected if the supervisor engine is removed.

If the active supervisor engine fails, the redundant supervisor engine become active. This newly active supervisor engine uses existing Layer 2 switching information to continue forwarding traffic. Layer 3 forwarding will be delayed until the routing tables have been repopulated in the newly active supervisor engine.

SSO supports stateful switchover of the following Layer 2 features. The state of these features is preserved between both the active and redundant supervisor engines:

•802.3

•802.3u

•802.3x (Flow Control)

•802.3ab (GE)

•802.3z (Gigabit Ethernet including CWDM)

•802.3ad (LACP)

•802.1p (Layer 2 QoS)

•802.1q

•802.1X (Authentication)

•802.1D (Spanning Tree Protocol)

•802.3af (Inline power)

•PAgP

•VTP

•Dynamic ARP Inspection

•DHCP snooping

•IP source guard

•IGMP snooping (versions 1 and 2)

•DTP (802.1q and ISL)

•MST

•PVST+

•Rapid-PVST

•PortFast/UplinkFast/BackboneFast

•BPDU guard and filtering

•Voice VLAN

•Port security

•Unicast MAC filtering

•ACL (VACLS, PACLS, RACLS)

•QOS (DBL)

•Multicast storm control/broadcast storm control

SSO is compatible with the following list of features. However, the protocol database for these features is not synchronized between the redundant and active supervisor engines:

•802.1Q tunneling with Layer 2 Protocol Tunneling (L2PT)

•Baby giants

•Jumbo frame support

•CDP

•Flood blocking

•UDLD

•SPAN/RSPAN

•NetFlow

The following features are learned on the redundant supervisor engine if the SSO feature is enabled:

•All Layer 3 protocols on Catalyst 4500 series switches (Switch Virtual Interfaces)

Understanding Supervisor Engine Redundancy Synchronization

During normal operation, the persistent configuration (RPR and SSO) and the running configuration (SSO only) are synchronized by default between the two supervisor engines. In a switchover, the new active supervisor engine uses the current configuration.

Note You cannot enter CLI commands on the redundant supervisor engine console.

These sections describe supervisor engine redundancy synchronization:

•RPR Supervisor Engine Configuration Synchronization

•SSO Supervisor Engine Configuration Synchronization

RPR Supervisor Engine Configuration Synchronization

Because the redundant supervisor engine is only partially initialized in RPR mode, it interacts with the active supervisor engine only to receive configuration changes at startup and upon saving the configuration changes.

When a redundant supervisor engine is running in RPR mode, the following events trigger synchronization of the configuration information:

•When the redundant supervisor engine boots, the auto-sync command synchronizes the persistent configuration. This command is enabled by default. For details, refer to "Synchronizing the Supervisor Engine Configurations" section.

•When the active supervisor engine detects the redundant supervisor engine, the configuration information is synchronized from the active supervisor engine to the redundant supervisor engine. This synchronization overwrites any existing startup configuration file on the redundant supervisor engine.

•When you make changes to the configuration, you must use the write command to save and synchronize the startup configuration of the redundant supervisor engine.

SSO Supervisor Engine Configuration Synchronization

When a redundant supervisor engine runs in SSO mode, the following events trigger synchronization of the configuration information:

•When the active supervisor detects the redundant supervisor engine, synchronization of the persistent and running configuration takes place, allowing the redundant supervisor engine to arrive at a fully-initiated state.

•When real-time changes occur, the active supervisor engine synchronizes the running-config and (or) the persistent configuration (if necessary) with the redundant supervisor engine.

•When you change the configuration, you must use the write command to allow the active supervisor engine to save and synchronize the startup configuration of the redundant supervisor engine.

Supervisor Engine Redundancy Guidelines and Restrictions

The following guidelines and restrictions apply to supervisor engine redundancy:

•RPR requires Cisco IOS Release 12.1(12c)EW, Release 12.1(19)E or later releases. SSO requires Cisco IOS Release 12.2(20)EWA or later releases.

•The Catalyst 4507R switch and the 4510R switch are the only Catalyst 4500 series switches that support supervisor engine redundancy.

•The Catalyst 4510R series switch only supports the WS-X4516 and WS-X4516-10GE supervisor engines. The Catalyst 4507R series switch supports supervisor engines WS-X4013+, WS-X4013+10GE, WS-X4515, WS-X4516, and WS-X4516-10GE.

•In Cisco IOS Release 12.2(25)SG and later releases on a Catalyst 4507R series switch, TenGigabit Ethernet and Gigabit Ethernet uplinks are concurrently usable on the Supervisor Engine V-10GE (WS-X4516-10GE) and the Supervisor Engine II+10GE (WS-4013+10GE). In Cisco IOS releases earlier than 12.2(25)SG, you need to use the hw-module uplink select configuration command to select either the TenGigabit Ethernet or Gigabit Ethernet uplinks.

•In Cisco IOS Release 12.2(25)SG and later releases, when using a Supervisor Engine V-10GE (WS-X4516-10GE) on a Catalyst 4510R series switch, you can select to use both the TenGigabit Ethernet and Gigabit Ethernet uplinks concurrently, but only with a WS-X4302-GB in slot 10. If either the 10 Gigabit Ethernet or Gigabit Ethernet uplinks are selected, then any linecard is allowed in slot 10. To select the uplinks, use the hw-module uplink select configuration command. In Cisco IOS releases earlier than 12.2(25)SG, you cannot use the TenGigabit Ethernet and Gigabit Ethernet uplinks concurrently.

•When you select TenGigabit Ethernet uplinks on WS-X4516-10GE and WS-X4013+10GE Supervisor Engines in RPR or SSO mode, only TenGigabitEthernet 1/1 and 2/1 interfaces are available. Similarly, when you select Gigabit Ethernet uplinks, only GigabitEthernet 1/3, 1/4, 2/3, and 2/4 interfaces are available. When you select to use both uplinks concurrently, TenGigabitEthernet 1/1 and 2/1 interfaces and GigabitEthernet 1/3, 1/4, 2/3, and 2/4 interfaces are available.

•Redundancy requires both supervisor engines in the chassis to be of the same supervisor engine model (same model, same memory, NFL daughter card and so on), and to use the same Cisco IOS software image.

•When you use the WS-X4013+ and WS-X4515 supervisor engines in RPR or SSO mode, only the Gig1/1 and Gig2/1 Gigabit Ethernet interfaces are available, but the Gig1/2 and Gig2/2 uplink ports are unavailable.

•When the WS-X4516 active and redundant supervisor engines are installed in the same chassis, the four uplink ports (Gig1/1, Gig2/1, Gig 1/2, and Gig2/2) are available.

•The active and redundant supervisor engines in the chassis must be in slots 1 and 2.

•Each supervisor engine in the chassis must have its own Flash device and console port connections to operate the switch on its own.

•Each supervisor engine must have a unique console connection. Do not connect a Y cable to the console ports.

•Supervisor engine redundancy does not provide supervisor engine load balancing.

•The Cisco Express Forwarding (CEF) table is cleared on a switchover. As a result, routed traffic is interrupted until route tables reconverge. This reconvergence time is minimal because the SSO feature reduces the supervisor engine redundancy switchover time from 30+ seconds to subsecond, so Layer 3 also has a faster failover time if the switch is configured for SSO.

•Static IP routes are maintained across a switchover because they are configured from entries in the configuration file.

•Information about Layer 3 dynamic states that is maintained on the active supervisor engine is not synchronized to the redundant supervisor engine and is lost on switchover.

•Starting with Cisco IOS Release 12.2, if an unsupported condition is detected (such as when the active supervisor engine is running Cisco IOS Release 12.2(20)EW and the redundant supervisor engine is running Cisco IOS Release 12.1(20)EW), the redundant supervisor engine will be reset multiple times and then be placed in ROMMON mode. Therefore, it is important to follow the exact procedures outlined in the "Performing a Software Upgrade" section.

•If you are running (or upgrading to) Cisco IOS Release 12.2(20)EWA or Cisco IOS Release 12.2(25)EW and are using a single supervisor engine in a redundant chassis (Catalyst 4507R or Catalyst 4510R series switch), and you intend to use routed ports, do one of the following:

–Use SVI's instead of routed ports.

–Change the redundancy mode from SSO to RPR.

•Configuration changes made to the redundant supervisor engine through SNMP synchronization and SNMP set operations in SSO mode are not synchronized to the redundant supervisor engine. Even though you can still perform SNMP set operations in SSO mode, you might experience unexpected behaviour.

After you configure the switch through SNMP in SSO mode , copy the running-config file to the startup-config file on the active supervisor engine to trigger synchronization of the startup-config file on the redundant supervisor engine. Then, reload the redundant supervisor engine so that new configuration is applied on the redundant supervisor engine.

•You cannot perform configuration changes during the startup (bulk) synchronization. If you attempt to make configuration changes during this process, the following message is generated:

Config mode locked out till standby initializes

•If configuration changes occur at the same time as a supervisor engine switchover, these configuration changes are lost.

Configuring Supervisor Engine Redundancy

These sections describe how to configure supervisor engine redundancy:

•Configuring Redundancy

•Virtual Console for Standby Supervisor Engine

•Synchronizing the Supervisor Engine Configurations

Configuring Redundancy

To configure redundancy, perform this task:

Switch(config)# redundancy 

Switch(config-red)# mode {sso | rpr}

Switch# show running-config

Switch# show redundancy  
[clients | counters | history | states]

When configuring redundancy, note the following:

•The sso keyword is supported in Cisco IOS Release 12.2(20)EWA and later releases.

•The rpr keyword is supported in Cisco IOS Release 12.1(12c)EW and later releases.

This example shows how to configure the system for SSO and display the redundancy facility information:

Switch> enable 

Switch# configure terminal 

Enter configuration commands, one per line. End with CNTL/Z.

Switch(config)# redundancy 

Switch(config-red)# mode sso 

Switch(config-red)# end 

Switch# show redundancy

Redundant System Information :

------------------------------

       Available system uptime = 2 days, 2 hours, 39 minutes

Switchovers system experienced = 0

              Standby failures = 0

        Last switchover reason = none

                 Hardware Mode = Duplex

    Configured Redundancy Mode = Stateful Switchover

     Operating Redundancy Mode = Stateful Switchover

              Maintenance Mode = Disabled

                Communications = Up

Current Processor Information :

-------------------------------

               Active Location = slot 1

        Current Software state = ACTIVE

       Uptime in current state = 2 days, 2 hours, 39 minutes

                 Image Version = Cisco Internetwork Operating System Software

IOS (tm) Catalyst 4000 L3 Switch Software (cat4000-I5S-M), Version 12.2(20)EWA(3

.92), CISCO INTERNAL USE ONLY ENHANCED PRODUCTION VERSION

Copyright (c) 1986-2004 by cisco Systems, Inc.

Compiled Wed 14-Jul-04 04:42 by esi

                          BOOT = bootflash:cat4000-i5s-mz.122_20_EWA_392,1

        Configuration register = 0x2002

Peer Processor Information :

----------------------------

              Standby Location = slot 2

        Current Software state = STANDBY HOT

       Uptime in current state = 2 days, 2 hours, 39 minutes

                 Image Version = Cisco Internetwork Operating System Software

IOS (tm) Catalyst 4000 L3 Switch Software (cat4000-I5S-M), Version 12.2(20)EWA(3

.92), CISCO INTERNAL USE ONLY ENHANCED PRODUCTION VERSION

Copyright (c) 1986-2004 by cisco Systems, Inc.

Compiled Wed 14-Jul-04 0

                          BOOT = bootflash:cat4000-i5s-mz.122_20_EWA_392,1

        Configuration register = 0x2002

Switch#

This example shows how to display redundancy facility state information:

Switch# show redundancy states

my state = 13 -ACTIVE

     peer state = 8  -STANDBY HOT

           Mode = Duplex

           Unit = Primary

        Unit ID = 2

Redundancy Mode (Operational) = Stateful Switchover

Redundancy Mode (Configured)  = Stateful Switchover

     Split Mode = Disabled

   Manual Swact = Enabled

 Communications = Up

   client count = 21

 client_notification_TMR = 240000 milliseconds

          keep_alive TMR = 9000 milliseconds

        keep_alive count = 0

    keep_alive threshold = 18

           RF debug mask = 0x0

Switch#

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 active 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 back to the original prompt 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 such a case, 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 login to the standby supervisor engine using a virtual console, do the following:

Switch# session module 2

Connecting to standby virtual console

Type "exit" or "quit" to end this session

Switch-standby-console# exit

Switch#

If the standby console is not enabled, the following message appears.

Switch-standby-console#

Standby console disabled.

Valid commands are: exit, logout

Note The standby virtual console provides the standard features that are available from the supervisor console such as command history, command completion, command help and partial command keywords.

The following limitations apply to the standby virtual console:

•All commands on the virtual console run to completion. It does not provide the auto-more feature; it behaves as if the terminal length 0 command has been executed. It is also non-interactive. Therefore, a running command cannot be interrupted or aborted by any key sequence on the active supervisor engine. Therefore if a command produces considerable output, the virtual console displays it on the supervisor screen.

•The virtual console is non-interactive. Because the virtual console does not detect the interactive nature of a command, any command that requires user interaction causes the virtual console to wait until the RPC timer aborts the command.

The virtual console timer is set to 60 seconds. The virtual console returns to its prompt after 60 seconds. During this time, you cannot abort the command from the key board. You must wait for the timer to expire before you continue.

•You cannot use virtual console to view debug and syslog messages that are being displayed on the standby supervisor engine. The virtual console only displays the output of commands that are executed from the virtual console. Other information that is displayed on the real standby console does not appear on the virtual console.

Synchronizing the Supervisor Engine Configurations

To manually synchronize the configurations used by the two supervisor engines, perform this task on the active supervisor engine:

Switch(config)# redundancy

Switch(config-red)# main-cpu

Switch(config-r-mc)# auto-sync {startup-config | 
config-register | bootvar | standard}

Switch(config-r-mc)# end

Switch# copy running-config startup-config

Note Configuration changes made to the active supervisor engine through SNMP are not synchronized to the redundant supervisor engine. For information on how to handle this situation, see the "Supervisor Engine Redundancy Guidelines and Restrictions" section.

Note The auto-sync command controls the synchronization of the config-reg, bootvar, and startup/private configuration files only. The calendar and VLAN database files are always synchronized when they change. In SSO mode, the running-config is always synchronized.

This example shows how to reenable the default automatic synchronization feature using the auto-sync standard command to synchronize the startup-config and config-register configuration of the active supervisor engine with the redundant supervisor engine. Updates for the boot variables are automatic and cannot be disabled.

Switch(config)# redundancy

Switch(config-red)# main-cpu

Switch(config-r-mc)# auto-sync standard

Switch(config-r-mc)# end

Switch# copy running-config startup-config

Note To manually synchronize individual elements of the standard auto-sync configuration, disable the default automatic synchronization feature.

Note When you configure the auto-sync standard, the individual sync options such as no auto-sync startup-config are ignored.

This example shows how to disable default automatic synchronization and allow only automatic synchronization of the config-registers of the active supervisor engine to the redundant supervisor engine, while disallowing synchronization of the startup configuration:

Switch(config)# redundancy

Switch(config-red)# main-cpu

Switch(config-r-mc)# no auto-sync standard

Switch(config-r-mc)# auto-sync config-register

Switch(config-r-mc)# end

Performing a Manual Switchover

This section describes how to perform a manual switchover (from the active supervisor engine to the redundant supervisor engine) for test purposes. We recommend that you perform a manual switchover prior to deploying SSO in your production environment.

Note This discussion assumes that SSO has been configured as the redundant mode.

To perform a manual switchover, perform this task on the active supervisor engine:

Switch# show redundancy

Switch# redundancy force-switchover

Be aware of these usage guidelines:

•To force a switchover, the redundant supervisor engine must be in a standby hot state. You can verify the state with the show redundancy command. If the state is not standby hot, the redundancy force-switchover command will not execute.

•Use the redundancy force-switchover command, rather than the reload command, to initiate a switchover. The redundancy force-switchover command will first check that the redundant supervisor engine is in the correct state. If you issue the reload command and the status is not standby hot, the reload command will reset the current supervisor engine only.

After an initial switchover, there might be occasions when you want to make the supervisor engine in slot 1 of the chassis the active supervisor engine. If the image on supervisor engine 1 is the one you intend to run on both supervisor engines, it is not necessary to re-boot the image on the supervisor engine in slot 1 to make it redundant. Instead, you can force another switchover. However, if you want a newer version of the image to run on both supervisor engines, follow the steps under "Performing a Software Upgrade" on page 13. Use the show module command to see which slot contains the active supervisor engine, and force another switchover if necessary.

Performing a Software Upgrade

The software upgrade procedure supported by supervisor engine redundancy allows you to reload the Cisco IOS software image on the redundant supervisor engine, and once complete, reload the active supervisor engine once.

If the active supervisor engine is running Cisco IOS Release 12.2(x)S, the standby supervisor engine cannot run Cisco IOS Release 12.1(x)E. This would reset the switch immediately after the system boot of the standby supervisor engine. The reverse configuration, where the standby engine is running Cisco IOS Release 12.2(x)S and the active supervisor engine is running Cisco IOS Release 12.1(x)E, is fully supported.

To perform a software upgrade, perform this task:

Switch# copy source_device:source_filename 
slot0:target_filename

Switch# copy source_device:source_filename 
bootflash:target_filename 

Switch# copy source_device:source_filename 
slaveslot0:target_filename

Switch# copy source_device:source_filename 
slavebootflash:target_filename 

Switch# config terminal

Switch(config)# config-register 0x2

Switch(config)# boot system flash 
device:file_name 

Switch(config)# redundancy

Switch(config-red)# main-cpu

Switch(config-r-mc)# auto-syn standard

Switch(config-r-mc)# end

Switch# copy running-config start-config

Switch# redundancy reload peer

Switch# redundancy force-switchover

This example shows how to perform a software upgrade:

Switch# config terminal

Switch(config)# config-register 0x2

Switch(config)# boot system flash slot0:cat4000-i5s-mz.122-20.EWA

Switch(config)# redundancy

Switch(config-red)# main-cpu

Switch(config-r-mc)# auto-syn standard

Switch(config-r-mc)# end

Switch# copy running-config start-config

Switch# redundancy reload peer

Switch# redundancy force-switchover 

Switch#

This example illustrates how to verify that the running configuration on the active supervisor engine has successfully synchronized with the redundant supervisor engine:

Switch# config terminal

Switch(config)# redundancy

Switch(config-red)# main-cpu

Switch(config-r-mc)# auto-sync standard

4d01h: %C4K_REDUNDANCY-5-CONFIGSYNC: The bootvar has been successfully synchronized to the 
standby supervisor

4d01h: %C4K_REDUNDANCY-5-CONFIGSYNC: The config-reg has been successfully synchronized to 
the standby supervisor

4d01h: %C4K_REDUNDANCY-5-CONFIGSYNC: The startup-config has been successfully synchronized 
to the standby supervisor

4d01h: %C4K_REDUNDANCY-5-CONFIGSYNC: The private-config has been successfully synchronized 
to the standby supervisor

The example above shows that the boot variable, the config-register, and the startup configuration from the active supervisor engine have successfully synchronized to the redundant supervisor engine.

Manipulating Bootflash on the Redundant Supervisor Engine

Note The console port on the redundant supervisor engine is not available.

To manipulate the redundant supervisor engine bootflash, perform one or more of the following tasks:

Switch# dir slaveslot0:target_filename 

or: 
Switch# dir slavebootflash:target_filename 

Switch# delete slaveslot0:target_filename

or: 
Switch# delete slave bootflash:target_filename 

Switch# squeeze slaveslot0:target_filename

or: 
Switch# squeeze slavebootflash:target_filename 

Switch# format slaveslot0:target_filename

or: 
Switch# format slavebootflash:target_filename 

Switch# copy source_device:source_filename 
slaveslot0:target_filename

or: 
Switch# copy source_device:source_filename 
slavebootflash:target_filename