|
|
This chapter describes how to configure the supervisor engine software, including IP address and subnet mask assignment, default gateway configuration, and redundant supervisor engine operation.
This chapter consists of these sections:
The Catalyst 5000, 2926G, and 2926 series switches have two configurable IP management interfaces, the in-band (sc0) interface and the SLIP (sl0) interface. The Catalyst 4000 and 2948G series switches have an additional interface, the management Ethernet (me1) interface.
The in-band (sc0) management interface is connected to the switching fabric and therefore participates in all of the functions of a normal switch port, such as spanning tree, Cisco Discovery Protocol (CDP), virtual LAN (VLAN) membership, and so forth. The out-of-band management interfaces (sl0 and me1) are not connected to the switching fabric and do not participate in any of these functions.
When you configure the IP address, subnet mask, and broadcast address (and, on the sc0 interface, VLAN membership) of the sc0 or me1 interface, you can access the switch through Telnet or SNMP. When you configure the SLIP (sl0) interface, you can open a point-to-point connection to the switch through the console port from a workstation.
Because sc0 and me1 are two distinct interfaces, they potentially can have duplicate IP addresses or overlapping subnets. Therefore, when you enter a command that causes sc0 and me1 to have the same IP address or occupy the same subnet, the switch software brings one of the interfaces down.
In most cases, the switch software brings down the sc0 interface after you confirm the change. However, when the switch boots with the IP address 0.0.0.0 configured on both the sc0 and me1 interfaces, the me1 interface is brought down to allow BOOTP and RARP requests to broadcast out the sc0 interface.
Duplicate IP addresses and equal subnets are allowed on the sc0 and me1 interfaces provided that one of the interfaces is configured down. Non-equal subnets are not allowed (for example, sc0 with IP address 10.1.1.1 and subnet mask 255.0.0.0 and me1 with IP address 10.1.1.2 and subnet mask 255.255.255.0).
Table 3-1 shows the default supervisor engine configuration. For information on the default configuration for supervisor engine Fast Ethernet and Gigabit Ethernet uplinks, refer to "Configuring Ethernet, Fast Ethernet, and Gigabit Ethernet Switching."
| Feature | Default Value |
|---|---|
Administrative connection | Normal mode |
Global system information |
|
System clock | No value for system clock time |
Passwords | No passwords configured for normal mode or enable mode (press Return key) |
System prompt | |
Management Ethernet (me1) interface (Catalyst 4000 and 2948G series switches only) | IP address, subnet mask, and broadcast address set to 0.0.0.0 |
In-band (sc0) interface |
|
Default gateway address | Set to 0.0.0.0 with a metric of 0 |
SLIP2 (sl0) interface |
|
| 1VLAN=virtual LAN 2SLIP=Serial Line Internet Protocol |
These sections describe how to configure the supervisor engine software:
You can configure the switch using the set, show, and clear commands. Enter set commands to change switch parameters. Enter show commands to verify the configuration. Use clear commands (or, in some cases, set commands) to overwrite or erase configuration parameters.
Before you configure the supervisor engine software, obtain the following information:
Make sure the terminal is connected to the switch and that the switch and terminal are on. Perform this task to establish a console port connection to the switch.
| Task | Command |
|---|---|
Step 1 Access the switch command-line interface (CLI) using the appropriate commands or application on the terminal (for example, using the tip command on a UNIX system). |
|
Step 2 At the Enter password: prompt, press Return. |
|
Step 3 Enter privileged mode. | enable |
Step 4 At the Enter password: prompt, press Return. |
|
This example shows the bootup display of a Catalyst 5000 series switch with a Supervisor Engine II (the display on your switch might be different depending on the switch model and supervisor engine version):
ATE0 ATS0=1 Catalyst 5000 Power Up Diagnostics Init NVRAM Log LED Test ROM CHKSUM DUAL PORT RAM r/w RAM r/w RAM address test Byte/Word Enable test RAM r/w 55aa RAM r/w aa55 EARL test BOOTROM Version 2.1, Dated Apr 6 1998 16:49:40 BOOT date: 00/00/00 BOOT time: 03:18:57 SIMM RAM address test SIMM Ram r/w 55aa SIMM Ram r/w aa55 Start to Uncompress Image ... IP address for Catalyst not configured BOOTP will commence after the ports are online Ports are coming online ... Cisco Systems Console Enter password: Mon Apr 06 1998 03:20:41 Module 1 is online Enter Password: Mon Apr 06 1998 03:20:41 Module 2 is online Enter Password: Sending RARP request with address 00:40:0b:6c:2b:ff Sending bootp request with address: 00:40:0b:6c:2b:ff Sending RARP request with address 00:40:0b:6c:2b:ff Sending bootp request with address: 00:40:0b:6c:2b:ff Sending RARP request with address 00:40:0b:6c:2b:ff Sending bootp request with address: 00:40:0b:6c:2b:ff Sending RARP request with address 00:40:0b:6c:2b:ff Sending bootp request with address: 00:40:0b:6c:2b:ff Sending RARP request with address 00:40:0b:6c:2b:ff Sending bootp request with address: 00:40:0b:6c:2b:ff Sending RARP request with address 00:40:0b:6c:2b:ff Sending bootp request with address: 00:40:0b:6c:2b:ff Sending RARP request with address 00:40:0b:6c:2b:ff Sending bootp request with address: 00:40:0b:6c:2b:ff Sending RARP request with address 00:40:0b:6c:2b:ff Sending bootp request with address: 00:40:0b:6c:2b:ff Sending RARP request with address 00:40:0b:6c:2b:ff Sending bootp request with address: 00:40:0b:6c:2b:ff Sending RARP request with address 00:40:0b:6c:2b:ff Sending bootp request with address: 00:40:0b:6c:2b:ff Console> enable Enter password: Console> (enable)
This example shows the bootup display of a Catalyst 5000 series switch with a Supervisor Engine III. (The Supervisor Engine III FSX and FLX bootup display is similar; the display on your switch might be different depending on the switch model and supervisor engine version):
System Power On Diagnostics NVRAM Size..............................128KB LED Test................................Done 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.................16MB DRAM Data 0x55 Test.....................Passed DRAM Data 0xaa Test.....................Passed DRAM Address Test.......................Passed Clearing DRAM...........................Done EARL++..................................Present EARL RAM Test...........................Passed EARL Serial Prom Test...................Passed Level2 Cache............................Present Level2 Cache test.......................Passed
Before you can Telnet to the switch or use Simple Network Management Protocol (SNMP) to manage the switch, you must assign an IP address to either the in-band (sc0) logical interface or the management Ethernet (me1) interface. For information on obtaining an IP address from a BOOTP or RARP server, see the "Using BOOTP or RARP to Obtain an IP Address" section. For information on configuring the me1 interface, see the "Setting the Management Ethernet (me1) Interface IP Address" section.
To set the IP address and VLAN membership of the in-band (sc0) management interface, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Assign an IP address, subnet mask, and (optional) broadcast address to the in-band (sc0) interface. | set interface sc0 [ip_addr [netmask] [broadcast]] |
Step 2 Assign the in-band interface to the proper VLAN (make sure the VLAN is associated with the network to which the IP address belongs). | set interface sc0 [vlan] |
Step 3 If necessary, bring the interface up. | set interface sc0 up |
Step 4 Verify the interface configuration. | show interface |
This example shows how to assign an IP address, subnet mask, and VLAN to the in-band (sc0) interface and how to verify the interface configuration:
Console> (enable) set interface sc0 10.1.1.100 255.0.0.0
Interface sc0 IP address and netmask set.
Console> (enable) set interface sc0 10
Interface sc0 vlan set.
Console> (enable) show interface
sl0: flags=51<UP,POINTOPOINT,RUNNING>
slip 0.0.0.0 dest 128.96.3.240
sc0: flags=63<UP,BROADCAST,RUNNING>
vlan 10 inet 10.1.1.100 netmask 255.0.0.0 broadcast 10.255.255.255
Console> (enable)
Before you can Telnet to the switch or use SNMP to manage the switch, you must assign an IP address to either the in-band (sc0) logical interface or the management Ethernet (me1) interface. The me1 interface is only present on the Catalyst 4000 and 2948G series switches. For information on configuring the sc0 interface, see the "Setting the In-Band (sc0) Interface IP Address" section.
To set the management Ethernet (me1) interface IP address, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Assign an IP address and subnet mask to the management Ethernet (me1) interface. | set interface me1 [ip_addr [netmask]] |
Step 2 If necessary, bring the interface up. | set interface me1 up |
Step 3 Verify the interface configuration. | show interface |
This example shows how to assign an IP address and subnet mask to the management Ethernet (me1) interface and how to verify the interface configuration:
Console> (enable) set interface me1 172.20.52.12 255.255.255.224
Interface me1 IP address and netmask set.
Console> (enable) show interface
sl0: flags=51<UP,POINTOPOINT,RUNNING>
slip 0.0.0.0 dest 0.0.0.0
sc0: flags=63<UP,BROADCAST,RUNNING>
vlan 1 inet 0.0.0.0 netmask 0.0.0.0 broadcast 0.0.0.0
me1: flags=63<UP,BROADCAST,RUNNING>
inet 172.20.52.12 netmask 255.255.255.224 broadcast 172.20.52.31
Console> (enable)
The supervisor engine sends IP packets with unresolved destination IP addresses to the default gateway (typically a router).
On the Catalyst 5000, 2926G, and 2926 series switches, you can define up to three default IP gateways in software release 4.1 and later. Use the primary keyword to give a default IP gateway higher priority than other default gateways. If no primary default gateway is specified, the first gateway configured is the primary gateway. If more than one gateway is designated as primary, the last primary gateway configured is the primary default gateway.
Defining multiple default gateways provides redundancy; if the primary default gateway fails, the switch uses the secondary default gateways in the order in which they were configured.
On the Catalyst 4000 and 2948G series switches, you can define only a single default gateway. When you configure a default gateway when both the in-band (sc0) and management Ethernet (me1) interfaces are configured, the switch software automatically determines through which interface the default gateway can be reached.
To specify one or more default gateways, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Configure a default IP gateway address for the switch. | set ip route default gateway [metric] [primary] |
Step 2 (Optional) Configure additional default gateways for the switch. | set ip route default gateway [metric] [primary] |
Step 3 Verify that the default gateways appear correctly in the IP routing table. | show ip route |
This example shows how to configure three default gateways on the switch and how to verify the default gateway configuration:
Console> (enable) set ip route default 10.1.1.1 primary Route added. Console> (enable) set ip route default 10.1.1.10 Route added. Console> (enable) set ip route default 10.1.1.20 Route added. Console> (enable) show ip route Fragmentation Redirect Unreachable ------------- -------- ----------- enabled enabled enabled The primary gateway: 10.1.1.1 Destination Gateway Flags Use Interface ----------------------- ----------------------- ------ ---------- --------- default 10.1.1.20 G 0 sc0 default 10.1.1.10 G 0 sc0 default 10.1.1.1 UG 12 sc0 10.0.0.0 10.1.1.100 U 0 sc0 default default UH 0 sl0 Console> (enable)
If your Telnet station or SNMP network management workstation is on a different network from the switch and there is no router available, you might need to add a static routing table entry for the network where your end station is located.
To configure a static route, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Configure a static route to the remote network. | set ip route destination gateway [metric] |
Step 2 Verify that the static route appears correctly in the IP routing table. | show ip route |
This example shows how to configure a static route on the switch and how to verify that the route is configured properly in the routing table:
Console> (enable) set ip route 172.16.0.0 10.1.1.20 Route added. Console> (enable) show ip route Fragmentation Redirect Unreachable ------------- -------- ----------- enabled enabled enabled The primary gateway: 10.1.1.1 Destination Gateway Flags Use Interface ----------------------- ----------------------- ------ ---------- --------- 172.16.0.0 10.1.1.20 UG 0 sc0 default 10.1.1.1 UG 18 sc0 10.0.0.0 10.1.1.100 U 0 sc0 default default UH 0 sl0 Console> (enable)
Use the SLIP (sl0) interface for point-to-point SLIP connections between the switch and an IP host.
| Caution You must use the console port for the SLIP connection. When the SLIP connection is enabled and SLIP is attached on the console port, an EIA/TIA-232 terminal cannot connect via the console port. If you are connected to the switch CLI through the console port and you enter the slip attach command, you will lose the console port connection. Use Telnet to access the switch, enter privileged mode, and enter the slip detach command to restore the console port connection. |
To enable and attach SLIP on the console port, perform this task:
| Task | Command |
|---|---|
Step 1 Access the switch from a remote host with Telnet. | telnet {host_name | ip_addr} |
Step 2 Enter privileged mode on the switch. | enable |
Step 3 Set the console port SLIP address and the destination address of the attached host. | set interface sl0 slip_addr dest_addr |
Step 4 Enable SLIP for the console port. | slip attach |
Step 5 Verify the SLIP interface configuration. | show interface |
This example shows how to configure SLIP on the console port and verify the configuration:
sparc20% telnet 172.20.52.71
Trying 172.20.52.71 ...
Connected to 172.20.52.71.
Escape character is '^]'.
Cisco Systems Console
Enter password:
Console> enable
Enter password:
Console> (enable) set interface sl0 10.1.1.1 10.1.1.2
Interface sl0 slip and destination address set.
Console> (enable) slip attach
Console Port now running SLIP.
Console> (enable) show interface
sl0: flags=51<UP,POINTOPOINT,RUNNING>
slip 10.1.1.1 dest 10.1.1.2
sc0: flags=63<UP,BROADCAST,RUNNING>
vlan 523 inet 172.20.52.71 netmask 255.255.255.224 broadcast 172.20.52.95
Console> (enable)
The switch makes BOOTP and RARP requests only if the sc0 interface IP address is set to 0.0.0.0 when the switch boots up. This address is the default for a new switch or a switch whose configuration file has been cleared using the clear config all command. BOOTP and RARP requests are only broadcast out the sc0 interface.
The me1 interface does not participate in BOOTP or RARP. If both the sc0 and me1 interfaces are unconfigured (IP address 0.0.0.0), the me1 interface is brought down to allow the switch to broadcast BOOTP or RARP requests on the sc0 interface. If the me1 interface is configured and the sc0 interface is not, BOOTP and RARP requests are not sent. Similarly, if the sc0 interface is not configured but the interface is configured down, BOOTP and RARP requests are not sent.
To use BOOTP or RARP to obtain an IP address for the switch, perform this task:
| Task | Command |
|---|---|
Step 1 Make sure you have BOOTP or RARP server code installed correctly on the workstation. |
|
Step 2 Obtain the first address in the MAC address range for module 1 (the supervisor engine). Choose the last address in the range on the first line under the MAC-Address(es) heading. | show module |
Step 3 Add an entry in the BOOTP or RARP configuration file for each switch. Press Return after each entry to create a blank line between each entry. |
|
Step 4 Set the sc0 interface IP address to 0.0.0.0. | set interface sc0 0.0.0.0 |
Step 5 Reset the switch. The switch broadcasts BOOTP and RARP requests only when the switch boots up. | reset system |
Step 6 When the switch reboots, confirm that the sc0 interface IP address is set correctly. | show interface |
To set the user mode and privileged mode passwords, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Set the password for normal mode. Enter your old password (press Return on a switch with no password configured), enter your new password, and reenter your new password. | set password |
Step 2 Set the password for privileged mode. Enter your old password, enter your new password, and reenter your new password. | set enablepass |
This example shows how to set the passwords on the switch:
Console> (enable) set password Enter old password: Enter new password: Retype new password: Password changed. Console> (enable) set enablepass Enter old password: Enter new password: Retype new password: Password changed. Console> (enable)
These sections describe how the boot configuration works on the Catalyst 5000 series Supervisor Engine III (including the Supervisor Engine III FSX and FLX models) and on the Catalyst 4000, 2948G, and 2926G series switches, and how to modify the configuration register and BOOT variable:
These sections describe how the boot configuration works on the Catalyst 5000 series Supervisor Engine III and Catalyst 4000 and 2948G series switches:
The boot process on the Catalyst 5000 series Supervisor Engine III and the Catalyst 4000, 2948G, and 2926G series switches involves two software images: ROM monitor and supervisor engine system code. When the switch is powered up or reset, the ROM-monitor code is executed. Depending on the nonvolatile RAM (NVRAM) configuration, the switch either stays in ROM-monitor mode or loads the supervisor engine system code.
Two user-configurable parameters determine how the switch boots: the configuration register and the BOOT environment variable. The configuration register is described in the "Understanding the Configuration Register" section. The BOOT environment variable is described in the "Understanding the BOOT Environment Variable" section.
The ROM monitor code executes upon switch power-up, reset, or when a fatal exception occurs. The system enters ROM-monitor mode if the switch does not find a valid system image, if the NVRAM configuration is corrupted, or if the configuration register is set to enter ROM-monitor mode. From ROM-monitor mode, you can manually load a system image from Flash memory, from a network server file, or from bootflash.
On the Catalyst 5000 and 2926G series switches, you can enter ROM-monitor mode by restarting the switch and then pressing the Break key during the first 60 seconds of startup. If you are connected through a terminal server, you can escape to the Telnet prompt and enter the send break command to enter ROM-monitor mode.
On the Catalyst 4000 and 2948G series switches, you can enter ROM-monitor mode by restarting the switch and then pressing Control-C during the first five seconds of startup. If you are connected through a terminal server, you can escape to the Telnet prompt and press Control-C to enter ROM-monitor mode.
The following functionality is built into the ROM monitor:
The configuration register determines whether the switch loads an operating system image and where the system image is stored. The configuration register boot field determines if and how the ROM monitor loads a supervisor engine system image at startup. You can modify the boot field to force the switch to boot a particular system image at startup instead of using the default system image.
The lowest four bits (bits 3, 2, 1, and 0) of the 16-bit configuration register form the boot field. The default boot field value is 0x10F. The possible configuration register boot field settings are as follows:
The function of other bits in the configuration register are as follows:
The BOOT environment variable specifies a list of image files on various devices from which the switch can boot at startup.
You can add several images to the BOOT environment variable to provide a fail-safe boot configuration. If the first file fails to boot the switch, subsequent images specified in the BOOT variable are tried until the switch boots or there are no additional images to attempt to boot. If there is no valid image to boot, the system enters ROM-monitor mode where you can manually specify an image to boot.
The system stores and executes images in the order in which you added them to the BOOT variable. If you want to change the order in which images are tried at startup, you can either prepend and clear images from the BOOT variable to attain the desired order or you can clear the entire BOOT environment variable and then redefine the list in the desired order.
Table 3-2 shows the default switch boot configuration.
| Feature | Default Configuration |
|---|---|
Configuration register value | 0x10f |
Boot method | System boots from the image specified in the BOOT environment variable |
ROM monitor console port baud rate | 9600 baud1 |
ignore-config parameter | Disabled |
BOOT environment variable | Empty |
| 1On the Catalyst 4000 and 2948G series switches, the ROM monitor console port baud rate is always 9600 baud. |
The following sections describe how to modify the configuration register and BOOT environment variable on the Catalyst 5000 series Supervisor Engine III and Catalyst 4000, 2948G, and 2926G series switches:
You can determine the boot method the switch will use at the next startup by setting the boot field in the configuration register. This command affects only the configuration register bits that control the boot field and leaves the remaining bits unaltered. The following boot methods are supported:
To set the configuration register boot field, perform this task in privileged mode:
| Task | Command |
|---|---|
Specify the boot field in the configuration register. | set boot config-register boot {rommon | bootflash | system} [mod_num] |
This example shows how to force the switch to enter ROM-monitor mode at the next startup:
Console> (enable) set boot config-register boot rommon Configuration register is 0x140 ignore-config: enabled console baud: 9600 boot: the ROM monitor Console> (enable)
On the Catalyst 5000 and 2926G series switches, you can change the console port baud rate used by the ROM monitor. The new baud rate is used the next time the switch is restarted. This command affects only the configuration register bits that control the baud rate and leaves the remaining bits unaltered.
On the Catalyst 4000 and 2948G series switches, you cannot change the ROM monitor console port baud rate; it is always set to 9600 baud.
To change the ROM-monitor console port baud rate in the configuration register, perform this task in privileged mode:
| Task | Command |
|---|---|
Change the ROM-monitor console port baud rate in the configuration register. | set boot config-register baud {1200 | 2400 | 4800 | 9600} [mod_num] |
This example shows how to change the ROM-monitor console port baud rate in the configuration register to 2400:
Console> (enable) set boot config-register baud 2400 Configuration register is 0x190f ignore-config: disabled console baud: 2400 boot: image specified by the boot system commands Console> (enable)
You can cause the system software to ignore the configuration information stored in NVRAM the next time the switch is restarted. This command affects only the configuration register bits that control whether the switch ignores the NVRAM configuration and leaves the remaining bits unaltered. This command affects the next system restart only.
| Caution Enabling the ignore-config parameter is the same as entering the clear config all command; that is, it clears the entire configuration stored in NVRAM the next time the switch is restarted. |
To set the switch to ignore the NVRAM configuration at the next startup, perform this task in privileged mode:
| Task | Command |
|---|---|
Set the switch to ignore the contents of NVRAM at startup. | set boot config-register ignore-config enable |
This example shows how to set the switch to ignore the NVRAM configuration at the next startup:
Console> (enable) set boot config-register ignore-config enable Configuration register is 0x14f ignore-config: enabled console baud: 9600 boot: image specified by the boot system commands Console> (enable)
To set the entire configuration register value, perform this task in privileged mode:
| Task | Command |
|---|---|
Set the configuration register. | set boot config-register 0xvalue [mod_num] |
This example shows how to set the configuration register value to 0x90f:
Console> (enable) set boot config-register 0x90f Configuration register is 0x90f ignore-config: disabled console baud: 4800 boot: image specified by the boot system commands Console> (enable)
To set the BOOT environment variable, perform this task in privileged mode:
| Task | Command |
|---|---|
Specify a system image to add to the BOOT environment variable. | set boot system flash device:[filename] [prepend] [mod_num] |
This example shows how to add system images to the BOOT environment variable:
Console> (enable) set boot system flash bootflash:cat5000-sup3.3-2-1b.bin BOOT variable = bootflash:cat5000-sup3.3-2-1b.bin,1; Console> (enable) set boot system flash bootflash:cat5000-sup3.4-1-2.bin BOOT variable = bootflash:cat5000-sup3.3-2-1b.bin,1;bootflash:cat5000-sup3.4-1 -2.bin,1; Console> (enable) set boot system flash slot0:cat5000-sup3.4-2-1.bin prepend BOOT variable = slot0:cat5000-sup3.4-2-1.bin,1;bootflash:cat5000-sup3.3-2-1b. bin,1;bootflash:cat5000-sup3.4-1-2.bin,1; Console> (enable)
To display the current configuration register and BOOT environment variable settings, perform this task:
| Task | Command |
|---|---|
Display the current configuration register and BOOT environment variable settings. | show boot [mod_num] |
This example shows how to display the current configuration register and BOOT environment variable settings:
Console> (enable) show boot BOOT variable = slot0:cat5000-sup3.4-2-1.bin,1;bootflash:cat5000-sup3.3-2-1b. bin,1;bootflash:cat5000-sup3.4-1-2.bin,1; Configuration register is 0x10f ignore-config: disabled console baud: 9600 boot: image specified by the boot system commands Console> (enable)
To clear entries from the BOOT environment variable, perform one of these tasks in privileged mode:
| Task | Command |
|---|---|
| clear boot system flash device:[filename] [mod_num] |
| clear boot system all [mod_num] |
This example shows how to clear a specific entry from the BOOT environment variable:
Console> (enable) clear boot system flash bootflash:cat5000-sup3.3-2-1b.bin BOOT variable = slot0:cat5000-sup3.4-2-1.bin,1;bootflash:cat5000-sup3.4-1-2.bin,1; Console> (enable)
This example shows how to clear the entire BOOT environment variable:
Console> (enable) clear boot system all BOOT variable = Console> (enable)
The Catalyst 5505, 5509, and 5500 switches support an optional redundant supervisor engine. The second supervisor engine takes over if the active supervisor engine fails. No software commands are needed to enable this functionality.
These sections describe how to use redundant supervisor engines on the Catalyst 5000 series switches:
When you install two supervisor engine modules in the Catalyst 5505, 5509, or 5500 switch, the first supervisor engine module to come online becomes the active module; the second supervisor engine module goes into standby mode. All administrative and network management functions, such as SNMP, CLI console, Telnet, Spanning-Tree Protocol (STP), Cisco Discovery Protocol (CDP), and VLAN Trunk Protocol (VTP) are processed on the active supervisor engine module.
At power-up, both supervisor engine modules run initial module-level diagnostics. Assuming both modules pass this level of diagnostics, the two modules communicate over the backplane, allowing them to cooperate during switching-bus diagnostics. The supervisor in slot 1 becomes active, and the supervisor in slot 2 enters standby mode. At this point, if the software versions of the two supervisors are different, or if the NVRAM configuration of the two supervisors is different, the active supervisor engine automatically downloads its software image and configuration to the standby supervisor engine.
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.
If you hot-insert a second supervisor engine module, the second module communicates with the active supervisor engine after completing its initial module-level diagnostics. Because the active supervisor engine is already switching traffic on the backplane, no switching-bus diagnostics are run for the second supervisor engine because running diagnostics can disrupt normal traffic. The second supervisor engine immediately enters standby mode. The active supervisor engine downloads the software image and configuration to the standby supervisor engine, if necessary.
The Supervisor Engine III modules use two Flash images: the boot image and the runtime image. The boot image filename is specified in the BOOT environment variable, which is stored in NVRAM. The runtime image is the boot image that the ROM monitor uses to boot the Supervisor Engine III module. After the system boots, the runtime image resides in dynamic RAM (DRAM).
When you power up or reset a Catalyst 5000 series switch with redundant Supervisor Engine III modules, synchronization occurs to ensure that the runtime and boot images on the standby supervisor engine are the same as the images on the active supervisor engine.
The Supervisor Engine III modules can have different runtime and boot images. If the boot image and the runtime image are the same, and you change the BOOT environment variable or overwrite or destroy the current boot image on the Flash device that was used to boot the system, the runtime and boot images will differ. Whenever you reconfigure the boot image, the active supervisor engine synchronizes its current boot image with the standby supervisor engine.
Supervisor Engine II modules use 8-MB onboard Flash memory to store a single boot image, and only one boot image can be stored at a time. The Supervisor Engine III, III FSX, and III FLX modules do not have memory dedicated to storing the boot image. Instead, a Flash file system is implemented and the boot image is read directly into the file system. You can perform operations (such as copy, delete, undelete, and so on) on files stored on Flash memory devices, and you can store the boot image of the active supervisor engine in the standby supervisor engine boot Flash. For more information about using the Flash file system, see the "Using the Flash File System" section.
The Supervisor Engine III FSX and FLX models have only the onboard Flash memory (bootflash:). The Supervisor Engine III module has two Flash PC card (PCMCIA) slots (slot0: and slot1:) in addition to the onboard Flash memory; these slots can hold Flash PC cards that can store additional boot images.
Since you can store multiple boot images on the Supervisor Engine III, III FSX, and III FLX modules, you must specify the name of the boot file image and the location of the image file in the Flash file system in order to boot and synchronize properly. For information about how to specify the name and location of the boot image, see the "Modifying the Switch Boot Configuration" section.
In the synchronization process, the active supervisor engine checks the standby supervisor engine runtime image to make sure it matches its own runtime image. The active supervisor engine checks three conditions:
The following section describes the conditions that can initiate Flash synchronization. For examples of how the system synchronizes the Supervisor Engine III (including the FSX and FLX models) Flash images with various configurations, see the "Supervisor Engine III Synchronization Examples" section.
These conditions initiate the synchronization of the runtime and boot images on the active and standby Supervisor Engine III modules:
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 ASP/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 module 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 module (where mod_num is the number of the active supervisor). | reset mod_num |
You can also switch to the standby supervisor engine module by setting the CISCO-STACK-MIB moduleAction variable to reset(2) on the active supervisor engine module.When the switchover occurs, the system sends a standard SNMP warm-start trap to the configured trap receivers.
This example shows an example of the console output on the active supervisor 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 an example of the console output on the standby supervisor 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)
The following examples show what happens when the synchronization function encounters certain conditions. These examples apply to the Supervisor Engine III, III FSX, and III FLX models, 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 example 1 is as follows:
bootflash:f1
bootflash:f1,1
f1
The configuration for example 2 is as follows:
bootflash:f1
bootflash:f1,1
f1
bootflash:f2
bootflash:f2,1
f2
The configuration for example 3 is as follows:
bootflash:f1
bootflash:f1,1
f1
bootflash:f2
bootflash:f2,1
f1,f2
The configuration for example 4 is as follows:
bootflash:f1
bootflash:f1,1
f1
bootflash:f2
bootflash:f2,1;
f2, f3, f4 (less than 1 MB left on device)
This section contains four examples in which the bootstrings on the active and standby Supervisor Engine III modules are synchronized.
The configuration for this example is as follows:
bootflash:f1
bootflash:f1,1;
f1
bootflash:f1
bootflash:f1,1;
f1
The configuration for this example is as follows:
bootflash:f1
bootflash:f1,1;
f1,f2
bootflash:f1
bootflash:f1,1;
The configuration for this example is as follows:
bootflash:f1
bootflash:f1,1;
f1,f2
bootflash:f1
bootflash:f1,1;
f1,f2
The configuration for this example is as follows:
bootflash:f1
bootflash:f1,1;
f1,f2
bootflash:f1
bootflash:f1,1;
f0,f1,f3 (less than 1 MB left on device)
|
|