|
|
This chapter consists of these sections:
Table 3-1 shows the default supervisor engine configuration.
| Feature | Default Value |
|---|---|
Administrative connection | Normal mode |
Global switch information |
|
System clock | No value for system clock time |
Passwords | No passwords configured for normal mode or enable mode (press the Return key) |
Switch prompt | |
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 on the Catalyst 6000 and 6500 series switches:
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 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 how to enter the privileged mode:
Cisco Systems Console Tue Nov 24 1998, 14:49:15 Console> enable Enter password: Console> (enable)
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 the in-band (sc0) logical interface.
To set the switch IP address, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Assign an IP address and netmask 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, netmask (the netmask can be entered as the desired number of masking bits), and VLAN to the in-band (sc0) interface and how to verify the interface configuration:
Console> (enable) set interface sc0 10.1.1.1/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.1 netmask 255.0.0.0 broadcast 10.255.255.255
Console> (enable)
The supervisor engine sends IP packets with unresolved destination IP addresses to the default gateway (typically a router).
You can define up to three default IP gateways. 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.
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] |
Step 3 Verify that the default gateways appear correctly in the IP routing table. | show ip route |
The metric parameter is an optional value that indicates the number of hops between the switch and the gateway. The gateway parameter can be either an IP address or, if DNS is configured, a host name.
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[/netmask] gateway [metric] |
Step 2 Verify that the static route appears correctly in the IP routing table. | show ip route |
The netmask can be entered as the desired number of bits. 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.
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 (shown by the arrow):
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 a BOOTP request only if you set the switch IP address to 0.0.0.0. This address is the default for a new switch or a switch whose configuration file has been cleared using the clear config all command.
To configure a workstation as a BOOTP server, you must determine the MAC address of the switch and add that MAC address to the BOOTP configuration file on the server.
To create a BOOTP server on a UNIX workstation, perform this task:
| Task | Command |
|---|---|
Step 1 Make sure you have BOOTP server code installed correctly on the workstation. |
|
Step 2 Obtain the first address in the MAC address range for VLAN 1 in 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 configuration file (usually /usr/etc/bootptab) for each switch. Press Return after each entry to create a blank line between each entry. |
|
Step 4 Set the switch IP address to 0.0.0.0. | set interface sc0 0.0.0.0 |
Step 5 Confirm that the switch 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, 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:
Catalyst 6000> (enable) set password Enter old password: Enter new password: Retype new password: Password changed. Catalyst 6000> (enable) set enablepass Enter old password: Enter new password: Retype new password: Password changed. Catalyst 6000> (enable)
These sections describe how the startup configuration on the Catalyst 6000 and 6500 series supervisor engine works and how to modify the configuration register and BOOT variable:
These sections describe how the boot configuration works on the Catalyst 6000 and 6500 series supervisor engine:
The supervisor engine boot process involves two software images: ROM monitor and supervisor engine software. When the switch is powered up or reset, the ROM-monitor code is executed. Depending on the nonvolatile RAM (NVRAM) configuration, the supervisor engine either stays in ROM-monitor mode or loads the supervisor engine software.
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 "Understanding the BOOT Environment Variable" section.
The ROM monitor executes upon switch power-up, reset, or when a fatal exception occurs. The switch enters ROM-monitor mode if the switch does not find a valid software 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 software image from bootflash, a Flash PC card, or a network server.
You can also 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.
The ROM monitor has these features:
The configuration register determines whether the switch loads a software image and where the software image is stored. The configuration register boot field determines if and how the ROM monitor loads a supervisor engine software image at startup. You can modify the boot field to force the switch to boot a particular software image at startup instead of using the default software 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 file names on various devices from which the switch can boot at startup.
You can add several image names to the BOOT environment variable to provide a fail-safe boot configuration. If the first image 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 try. If there is no valid image to boot, the switch enters ROM-monitor mode where you can manually specify an image to boot.
The switch stores and executes images in the order in which you enter them. 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 redefine the list in the desired order.
Table 3-2 shows the default supervisor engine boot configuration.
| Feature | Default Configuration |
|---|---|
Configuration register value | 0x10f |
Boot method | Switch boots from the image specified in the BOOT environment variable |
ROM monitor console port baud rate | 9600 baud |
ignore-config parameter | Disabled |
Empty |
These sections describe how to modify the configuration register and BOOT environment variable on the supervisor engine:
You can determine the boot method the switch will use at the next startup by setting the boot field in the configuration register. These boot methods are supported:
To set the boot field in the configuration register, 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)
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.
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 switch software to ignore the configuration information in NVRAM the next time the switch is restarted. This command affects the next 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 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 software image to add to the BOOT environment variable. | set boot system flash device:[filename] [prepend] [mod_num] |
This example shows how to add software image names to the BOOT environment variable:
Console> (enable) set boot system flash bootflash:cat6000-sup.5.1-1-5.bin BOOT variable = bootflash:cat6000-sup.5.1-1-5.bin,1; Console> (enable) set boot system flash bootflash:cat6000-sup.5.1-1-4.bin BOOT variable = bootflash:cat6000-sup.5.1-1-5.bin,1;bootflash:cat6000-sup.5.1-1 -4.bin,1; Console> (enable) set boot system flash bootflash:cat6000-sup.5.1-1-6.bin prepend BOOT variable =bootflash:cat6000-sup.5.1-1-6.bin,1;cat6000-sup.5.1-1-5.bin,1;boot flash:cat6000-sup.5.1-1-4.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 =bootflash:cat6000-sup.5.1-1-6.bin,1;cat6000-sup.5.1-1-5.bin,1;boot flash:cat6000-sup.5.1-1-4.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:cat6000-sup.5.1-1-4.bin BOOT variable =bootflash:cat6000-sup.5.1-1-6.bin,1;cat6000-sup.5.1-1-5.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 redundant supervisor engine operation feature allows you to install a second supervisor engine in a Catalyst 6000 or 6500 series switch. The second supervisor engine takes over if the active supervisor engine fails. No software commands are needed to enable this functionality.
This section discusses the following topics:
These sections describe how supervisor engine redundancy works.
When you install two supervisor engines in a Catalyst 6000 or 6500 series switch, the first supervisor engine to come up becomes the active module; the second supervisor engine goes into standby mode. All administrative and network management functions, such as SNMP, CLI console, Telnet, Spanning-Tree Protocol, Cisco Discovery Protocol (CDP), and VLAN Trunk Protocol (VTP) are processed on the active supervisor engine.
At power-up, both supervisor engines run through 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 engine in slot 1 becomes active, and the supervisor engine 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 downloads its software image automatically 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. After the reset supervisor engine comes up, it functions as if a hot swap occurred, and then enters the standby mode.
In the case of a just-inserted supervisor engine, the newly inserted 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 just-inserted supervisor engine. Running diagnostics would disrupt normal traffic. The just-inserted supervisor engine goes immediately into standby mode. At this point, the active supervisor engine downloads software and configuration information to the standby supervisor engine, if necessary.
The supervisor engine uses two software images: the boot image and the runtime image. If either image on the active supervisor engine changes after the switch boots, the synchronization feature ensures that the boot and runtime images on the standby supervisor engine are updated to match the images on the active supervisor. 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. After the switch boots, the runtime image resides in dynamic RAM (DRAM).
In addition to the onboard bootflash, the supervisor engine has a PCMCIA slot for a Flash PC card where you can store other software images and files.
Because the supervisor engine can have two boot devices, it needs to know the name of the boot file image and its location in the Flash file system in order to boot and synchronize properly.
The supervisor engine has a file system implemented in the Flash memory devices and the boot image is read directly into the file system. With the Flash file system devices, you can perform operations on the files stored in Flash memory (such as copy, delete, undelete, and so on), and you can store the boot image of the active supervisor engine in the standby supervisor engine bootflash.
When you power up or reset a Catalyst 6000 or 6500 series switch with redundant supervisor engines, 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 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 switch, 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.
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:
See the "Supervisor Engine Synchronization Examples" section for examples of how the switch synchronizes the supervisor engine Flash images with various configurations.
These conditions and events can cause the synchronization of images between redundant supervisor engines 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 and show test commands:
Console> show module 2
Mod Slot Ports Module-Type Model Status
--- ---- ----- ------------------------- ------------------- --------
2 2 2 1000BaseX Supervisor WS-X6K-SUP1-2GE ok
Mod Module-Name Serial-Num
--- ------------------- -----------
2 SAD02330231
Mod MAC-Address(es) Hw Fw Sw
--- -------------------------------------- ------ ---------- -----------------
2 00-e0-14-0e-f5-6c to 00-e0-14-0e-f5-6d 0.404 4.2(2038) 4.2(0.24)VAI50
00-e0-14-0e-f5-6e to 00-e0-14-0e-f5-6f
00-10-7b-bb-2b-00 to 00-10-7b-bb-2e-ff
Mod Sub-Type Sub-Model Sub-Serial Sub-Hw
--- ------------------- ------------------- ----------- ------
2 L2 Switching Engine WS-F6020 SAD02350211 0.101
Console> (enable) show test 2
Module 2 : 2-port 1000BaseX Supervisor
Network Management Processor (NMP) Status: (. = Pass, F = Fail, U = Unknown)
ROM: . Flash-EEPROM: . Ser-EEPROM: . NVRAM: . EOBC Comm: .
Line Card Status for Module 1 : PASS
Port Status :
Ports 1 2
-----------
. .
Line Card Diag Status for Module 2 (. = Pass, F = Fail, N = N/A)
Module 2
Cafe II Status :
NewLearnTest: .
IndexLearnTest: .
DontForwardTest: .
DontLearnTest: .
ConditionalLearnTest: .
BadBpduTest: .
TrapTest: .
Loopback Status [Reported by Module 2] :
Ports 1 2
-----------
. .
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). | 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 switch sends a standard SNMP warm-start trap to the configured trap receivers.
This example shows how to force a switchover to the standby supervisor engine:
Console> (enable) reset 1 This command will force a switch-over to the standby supervisor module and disconnect your telnet session. Do you want to continue (y/n) [n]? y Connection closed by foreign host. host%
These examples show what happens when the synchronization function encounters certain conditions. 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 engines 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;
f1
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)
Posted: Thu Apr 8 14:22:29 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.