|
|
This chapter consists of these sections:
These sections describe how supervisor engine redundancy works:
Catalyst 5500 series switches support supervisor engine redundancy with Supervisor Engine II, II G, III, III F, or III G. You must install the redundant supervisor engines in slots 1 and 2 of the chassis.
Redundant supervisor engines must be of the same type. Supervisor Engine III and III F modules are interchangeable in a redundant configuration provided the feature card is the same on both supervisor engines (both EARL1+, both NFFC, or both NFFC II).
When you boot a Catalyst 5500 series switch with redundant supervisor engines, the first supervisor engine to come online becomes the active supervisor engine; the second supervisor engine enters standby mode. All administrative and network management functions, such as CLI processing, SNMP, Telnet, Spanning-Tree Protocol (STP), Cisco Discovery Protocol (CDP), and VLAN Trunk Protocol (VTP), are processed on the active supervisor engine.
The Supervisor Engine II, II G, and III G modules store the boot image in onboard Flash memory. Only one boot image can be stored at a time. If you download a new system image to the supervisor engine, the new image replaces the image stored in the onboard Flash.
When you power up or reset the switch, both supervisor engines run initial module-level diagnostics. The supervisor engine in slot 1 becomes active, and the supervisor engine in slot 2 enters standby mode. If the software images on the two supervisor engines are different, or if the NVRAM configuration of the two supervisor engines is different, the active supervisor engine automatically downloads its software image and configuration to the standby supervisor engine.
When you power up or reset the switch, both supervisor engines run initial module-level diagnostics. The supervisor engine in slot 1 becomes active, and the supervisor engine in slot 2 enters standby mode.
The Supervisor Engine III and III F modules use two system images:
In most cases, the boot image and the runtime image are the same. However, if you change the BOOT environment variable or delete the boot image in Flash memory, the runtime and boot images are different. If you change or remove the boot image, the active supervisor engine synchronizes the new boot image with the boot image on the standby supervisor engine.
These conditions initiate the synchronization of the runtime and boot images on the active and standby Supervisor Engine III modules:
If the background diagnostics on the active supervisor engine detect a major problem or an exception occurs, the active supervisor engine resets. The standby supervisor engine detects that the active supervisor engine is no longer running and becomes active. The standby supervisor engine can detect if the active supervisor engine is not functioning and can force a reset, if necessary. If the reset supervisor engine comes online again, it enters standby mode.
In the event of a failure of the active supervisor engine, the standby supervisor engine becomes active. The redundant supervisor engine runs the same system image and configuration as the active supervisor engine and the system continues to operate with the same configuration after switching over to the second supervisor engine.
Whether you can use the uplink ports on the standby supervisor engine depends on the software release running on the switch:
The following conditions and events can cause the synchronization of images between redundant Supervisor Engine III modules to fail or to produce unexpected results:
You can verify the status of the standby supervisor engine using a number of CLI commands.
To verify the status of the standby supervisor engine, perform one or more of these tasks:
| Task | Command |
|---|---|
| show module [mod_num] |
| show port [mod_num[/port_num]] |
| show test [mod_num] |
This example shows how to check the status of the standby supervisor engine using the show module command:
Console> (enable) show module Mod Module-Name Ports Module-Type Model Serial-Num Status --- ------------------- ----- --------------------- --------- --------- ------- 1 4 10/100BaseTX Supervis WS-X5530 009979082 ok 2 2 10/100BaseTX Supervis WS-X5530 007451586 standby 3 48 10BaseT Ethernet WS-X5012A 007879593 ok 4 1 Network Analysis/RMON WS-X5380 008175475 ok 5 1 Route Switch WS-X5302 007460757 ok 6 10BaseT Ethernet Ext 7 48 10BaseT Ethernet WS-X5014 007879658 ok 8 1 MM OC-3 ATM WS-X5155 003414855 ok 9 2 UTP OC-3 Dual-Phy ATM WS-X5156 007646048 ok 13 /SRP Mod MAC-Address(es) Hw Fw Sw --- -------------------------------------- ------ ---------- ----------------- 1 00-e0-4f-ac-b0-00 to 00-e0-4f-ac-b3-ff 1.8 3.1.2 4.3(1a) 2 00-e0-4f-ac-b0-00 to 00-e0-4f-ac-b3-ff 1.3 3.1.2 4.3(1a) 3 00-10-7b-50-1b-00 to 00-10-7b-50-1b-2f 0.202 4.2(108) 4.3(1a) 4 00-e0-14-10-18-00 0.100 4.1.1 4.3(0.31) 5 00-e0-1e-91-d5-14 to 00-e0-1e-91-d5-15 5.0 20.7 11.3(3a)WA4(5) 7 00-10-7b-5d-30-40 to 00-10-7b-5d-30-6f 0.102 4.2(108) 4.3(1a) 8 00-e0-1e-a9-20-b9 1.2 1.3 3.2(7) 9 00-e0-1e-e5-07-27 2.1 1.3 3.2(6) Mod Sub-Type Sub-Model Sub-Serial Sub-Hw --- -------- --------- ---------- ------ 1 NFFC WS-F5521 0008936340 1.0 1 uplink WS-U5537 0007288247 2.0 2 NFFC WS-F5521 0011462777 1.1 2 uplink WS-U5531 0007464204 1.1 Console> (enable)
You can switch over to the standby supervisor engine by resetting the active supervisor engine.
To force a switchover to the standby supervisor engine, perform this task in privileged mode:
| Task | Command |
|---|---|
Reset the active supervisor engine (where mod_num is the number of the active supervisor engine). | reset mod_num |
You can also switch to the standby supervisor engine by setting the CISCO-STACK-MIB moduleAction variable to reset(2) on the active supervisor engine. When the switchover occurs, the system sends a standard SNMP warm-start trap to the configured trap receivers.
This example shows the console output on the active supervisor engine when you force a switchover from the active to the standby supervisor engine:
Console> (enable) reset 1 This command will force a switch-over to the standby Supervisor module. Do you want to continue (y/n) [n]? y Console> (enable) 12/07/1998,17:04:39:SYS-5:Module 1 reset from Console// System Bootstrap, Version 3.1(2) Copyright (c) 1994-1997 by cisco Systems, Inc. System Bootstrap, Version 3.1(2) Copyright (c) 1994-1997 by cisco Systems, Inc. Presto processor with 32768 Kbytes of main memory Autoboot executing command: "boot bootflash:cat5000-sup3.4-3-1a.bin" CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC Uncompressing file: ########################################################### System Power On Diagnostics NVRAM Size .. .................512KB ID Prom Test ..................Passed DPRAM Size ....................16KB DPRAM Data 0x55 Test ..........Passed DPRAM Data 0xaa Test ..........Passed DPRAM Address Test ............Passed Clearing DPRAM ................Done System DRAM Memory Size .......32MB DRAM Data 0x55 Test ...........Passed DRAM Data 0xaa Test ...........Passed DRAM Address Test ............Passed Clearing DRAM .................Done EARLII ........................Present EARLII RAM Test ...............Passed EARL Serial Prom Test .........Passed Level2 Cache ..................Present Level2 Cache test..............Passed Boot image: bootflash:cat5000-sup3.4-3-1a.bin Downloading epld sram device please wait ... Programming successful for Altera 10K50 SRAM EPLD This module is now in standby mode. Console is disabled for standby supervisor
This example shows the console output on the standby supervisor engine when you force a switchover from the active to the standby supervisor engine:
Cisco Systems Console Enter password: 12/07/1998,17:04:43:MLS-5:Multilayer switching is enabled 12/07/1998,17:04:43:MLS-5:Netflow Data Export disabled 12/07/1998,17:04:44:SYS-5:Module 2 is online 12/07/1998,17:04:45:SYS-5:Module 5 is online 12/07/1998,17:04:45:SYS-5:Module 7 is online 12/07/1998,17:04:45:SYS-5:Module 3 is online 12/07/1998,17:04:52:MLS-5:Route Processor 172.20.52.6 added 12/07/1998,17:05:10:SYS-5:Module 8 is online 12/07/1998,17:05:14:SYS-5:Module 9 is online 12/07/1998,17:05:22:SYS-5:Module 4 is online 12/07/1998,17:06:13:SYS-5:Module 1 is in standby mode Supervisor image synchronization process will start in 10 seconds 12/07/1998,17:06:37:SYS-5:Ports on standby supervisor(Module 1) are UP 12/07/1998,17:06:41:SYS-5:Active supervisor is synchronizing the NMP image. 12/07/1998,17:06:44:SYS-5:The active supervisor has synchronized the NMP image. Console>
In software release 4.3 and later, you can configure the uplink ports on the standby supervisor engine as active or inactive. This configuration is independent of other configuration commands such as set port enable and set port disable. The default configuration is the uplinks are inactive.
To configure the uplink ports on the standby supervisor engine as active, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Set the uplink ports on the standby supervisor engine to active. | set standbyports enable |
Step 2 Verify the configuration. | show standbyports |
This example shows how to set the uplink ports on the standby supervisor engine to active:
Console> (enable) set standbyports enable Standby ports feature enabled. Please wait while the standby ports are coming up.. Console> (enable) 12/07/1998,16:45:15:SYS-5:Ports on standby supervisor(Module 2) are UP Console> (enable)
To configure the uplink ports on the standby supervisor engine as inactive, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Set the uplink ports on the standby supervisor engine to inactive. | set standbyports disable |
Step 2 Verify the configuration. | show standbyports |
This example shows how to set the uplink ports on the standby supervisor engine to inactive:
Console> (enable) set standbyports disable Standby ports feature disabled. Console> (enable)
In software release 5.2 and later, you can perform a minimal downtime software upgrade in a switch with redundant supervisor engines. In most cases, the minimal downtime software upgrade reduces switch downtime to approximately 30-45 seconds from the average 4-5 minutes previously required.
 | Caution The minimal downtime software upgrade is most effective when the uplink ports on both supervisor engines are connected to the same network. If the uplink ports on the active and standby supervisor engines are connected to different networks, connectivity to each network is disrupted for approximately 4-5 minutes as each supervisor engine resets. |
In software release 5.2 and later on the Supervisor Engine III and III F, the download command performs the following actions:
The minimal downtime software upgrade process is as follows:
1. Use the download command to copy the new software image to the bootflash of the active supervisor engine. On the Supervisor Engine III and III F, the download command automatically deletes the oldest files in bootflash: if necessary to make room for the new image file, and prepends the new filename to the BOOT variable.
2. The active supervisor engine copies the new software image to the standby supervisor engine bootflash.
3. Use the reset mindown command to reset the switch. The standby supervisor engine resets and reboots using the new software image.
| Caution If you make configuration changes after entering the reset mindown command but before the active supervisor engine resets (see step 4), the changes are not saved. Input from the CLI is still accepted by the switch while the standby supervisor engine is reset, but any changes you make to the configuration between the time when you enter the reset mindown command and the time when the supervisor engine comes online running the new software image are not saved or synchronized with the standby supervisor engine. |
4. When the standby supervisor engine comes online, the active supervisor engine resets, causing a fast switchover to the standby supervisor engine.
5. The new active supervisor engine comes online running the new software image. The active supervisor engine resets all of the switching modules. Modules come online in approximately 30 seconds.
6. The previously active supervisor engine comes online running the new software image and enters standby mode.
To perform a minimal downtime software upgrade, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Download the new software image to the active supervisor engine. | download tftp_server filename |
Step 2 Reset the switch using the mindown keyword. | reset mindown |
This example shows how to perform a minimal downtime software upgrade on a switch with redundant Supervisor Engine III modules and includes output from both the active and standby supervisor engines.
This output is from the active supervisor engine in slot 1:
Console> (enable) download 172.20.52.3 cat5000-sup3.5-2-1.bin Download image cat5000-sup3.5-2-1.bin from 172.20.52.3 to Module 1 FLASH (y/n) [n]? y Squeeze bootflash in progress.... Erasing squeeze logCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC File has been copied successfully. Supervisor image synchronization process will start in 10 seconds Console> (enable) %SYS-5-SUP_IMGSYNCSTART:Active supervisor is synchronizing the NMP image %SYS-5-SUP_IMGSYNCFINISH:Active supervisor has synchronized the NMP image Console> (enable) reset mindown This command will upgrade standby Supervisor first, and switchover when standby Supervisor comes online. Do you want to continue (y/n) [n]? y Console> (enable) %SYS-3-SUP_WAITSBYSUPONLINE:Wait for standby supervisor to come online %SYS-5-SUP_MODSBY:Module 2 is in standby mode %MGMT-5-NVRAM_MINDOWN:Reset mindown in progress. Configuration changes are not set to nvram %SYS-3-SUP_THISSUPRESET:Resetting this supervisor .. standby supervisor will take over This command will force a switch-over to the standby Supervisor module. %SYS-5-MOD_RESET:Module 1 reset from SNMP_reset_mind// System Bootstrap, Version 3.1(2) Copyright (c) 1994-1997 by cisco Systems, Inc. System Bootstrap, Version 3.1(2) Copyright (c) 1994-1997 by cisco Systems, Inc. Presto processor with 32768 Kbytes of main memory Autoboot executing command: "boot bootflash:cat5000-sup3.5-2-1.bin" CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC Uncompressing file: ########################################################### ################################################################################ ################################################################################ ################################################################################ ################################################################################ ################################################################################ ################################################################################ ################################################################################ ################################################################################ ################################################################################ ################################################################################ ################################################################################ ################################################################################ ################### System Power On Diagnostics NVRAM Size ....................512 KB ID Prom Test ..................Passed DPRAM Size ....................16KB DPRAM Data 0x55 Test ..........Passed DPRAM Data 0xaa Test ..........Passed DPRAM Address Test ............Passed Clearing DPRAM ................Done System DRAM Memory Size .......32MB DRAM Data 0x55 Test ...........Passed DRAM Data 0xaa Test ...........Passed DRAM Address Test ............Passed Clearing DRAM .................Done EARLII ........................Present EARLII RAM Test ...............Passed EARL Serial Prom Test .........Passed Level2 Cache ..................Present Level2 Cache test..............Passed Boot image: bootflash:cat5000-sup3.5-2-1.bin Downloading epld sram device please wait ... Programming successful for Altera 10K50 SRAM EPLD This module is now in standby mode. Console is disabled for standby supervisor
This output is from the standby supervisor engine in slot2:
Squeeze bootflash in progress.... Erasing squeeze log System Bootstrap, Version 3.1(2) Copyright (c) 1994-1997 by cisco Systems, Inc. Presto processor with 32768 Kbytes of main memory Autoboot executing command: "boot bootflash:BTSYNC_cat5000-sup3.5-2-1.bin " CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC Uncompressing file: ########################################################### ################################################################################ ################################################################################ ################################################################################ ################################################################################ ################################################################################ ################################################################################ ################################################################################ ################################################################################ ################################################################################ ################################################################################ ################################################################################ ################################################################################ ################### System Power On Diagnostics NVRAM Size ....................512 KB ID Prom Test ..................Passed DPRAM Size ....................16KB DPRAM Data 0x55 Test ..........Passed DPRAM Data 0xaa Test ..........Passed DPRAM Address Test ............Passed Clearing DPRAM ................Done System DRAM Memory Size .......32MB DRAM Data 0x55 Test ...........Passed DRAM Data 0xaa Test ...........Passed DRAM Address Test ............Passed Clearing DRAM .................Done EARLII ........................Present EARLII RAM Test ...............Passed EARL Serial Prom Test .........Passed Level2 Cache ..................Present Level2 Cache test..............Passed Boot image: bootflash:BTSYNC_cat5000-sup3.5-2-1.bin This module is now in standby mode. Console is disabled for standby supervisor Cisco Systems Console Enter password: %MLS-5-NDEDISABLED:Netflow Data Export disabled %SYS-5-MOD_OK:Module 2 is online %SYS-5-MOD_OK:Module 8 is online %SYS-5-MOD_OK:Module 3 is online %SYS-5-SUP_MODSBY:Module 1 is in standby mode Supervisor image synchronization process will start in 10 seconds %SYS-5-SUP_IMGSYNCSTART:Active supervisor is synchronizing the NMP image %SYS-5-SUP_IMGSYNCFINISH:Active supervisor has synchronized the NMP image %SYS-5-MOD_OK:Module 10 is online Console>
The following examples show what happens when the synchronization function encounters certain conditions. These examples apply to the Supervisor Engine III and III F unless otherwise noted. These examples are not intended to cover every possible condition.
This section contains four examples in which the active supervisor engine runtime image is synchronized with the standby supervisor engine.
The configuration for this example is as follows:
| Active Supervisor Engine | Standby Supervisor Engine |
|---|---|
Runtime image: | Runtime image: |
BOOT variable: | BOOT variable: |
Bootflash: | Bootflash: |
The result is as follows:
The configuration for this example is as follows:
| Active Supervisor Engine | Standby Supervisor Engine |
|---|---|
Runtime image: | Runtime image: |
BOOT variable: | BOOT variable: |
Bootflash: | Bootflash: |
The result is as follows:
The configuration for this example is as follows:
| Active Supervisor Engine | Standby Supervisor Engine |
|---|---|
Runtime image: | Runtime image: |
BOOT variable: | BOOT variable: |
Bootflash: | Bootflash: |
The result is as follows:
The configuration for this example is as follows:
| Active Supervisor Engine | Standby Supervisor Engine |
|---|---|
Runtime image: | Runtime image: |
BOOT variable: | BOOT variable: |
Bootflash: | Bootflash: |
There is less than 1 MB of space left on the bootflash: device. Timestamp 2 is older than timestamp 3, and the timestamp 3 is older than timestamp 4.
The result is as follows:
This section contains four examples in which the BOOT variable on the active and standby Supervisor Engine III modules are synchronized.
The configuration for this example is as follows:
| Active Supervisor Engine | Standby Supervisor Engine |
|---|---|
Runtime image: | Runtime image: |
BOOT variable: | BOOT variable: |
Bootflash: | Bootflash: |
The result is as follows:
The configuration for this example is as follows:
| Active Supervisor Engine | Standby Supervisor Engine |
|---|---|
Runtime image: | Runtime image: |
BOOT variable: | BOOT variable: |
Bootflash: | Bootflash: |
The result is as follows:
The configuration for this example is as follows:
| Active Supervisor Engine | Standby Supervisor Engine |
|---|---|
Runtime image: | Runtime image: |
BOOT variable: | BOOT variable: |
Bootflash: | Bootflash: |
There is less than 1 MB of space left on the bootflash: device. The timestamp for image_file0 is older than image_file1, and the timestamp for image_file1 is older than the timestamp for image_file3.
The result is as follows:
Posted: Fri Oct 1 13:10:05 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.