This chapter describes the initial configuration of the Catalyst 5000 series switches and explains how to configure such functions as Internet Protocol (IP) addressing and Simple Network Management Protocol (SNMP).
Before you can use Telnet to connect to the switch or SNMP to manage your network, you must assign an IP address. Up to eight simultaneous Telnet sessions are possible. If your Telnet station or SNMP network management workstation is on a different network from the switch, you must add a static routing table entry to the routing table by entering the set ip route command.
The configurable Catalyst 5000 series features have default values that will most likely suit your environment, and you might not need to change them. For definitions of all commands discussed in this chapter, refer to the Catalyst 5000 Series Command Reference publication.
Note The Supervisor Engine III is managed differently than the Supervisor Engines I and II. Refer to "
Managing the Supervisor Engine III" for the additional information needed for the Supervisor Engine III.
The default values of the features for the Catalyst 5000 series switch follow:
- The administrative connection is set to normal mode.
- The system information defaults are set as follows:
- There are no defaults for the system contact, location string, system name, system clock time, and passwords for entering the command-line interfaces (CLI) for normal mode or privileged mode.
- The system prompt is set to Console>.
- The interface type defaults are set as follows:
- The sc0, sl, IP address, netmask, and broadcast are set to 0.0.0.0.
- The destination address for sl0 is 0.0.0.0.
- The sc0 interface is assigned to VLAN 1.
- The default gateway is 0.0.0.0 with a metric of 0.
- The Serial Line Interface Protocol (SLIP) for the console port is set to detach and is not active.
- Remote Monitoring (RMON) support is disabled.
- SNMP defaults are as follows:
- The SNMP community defaults are set:
- Read-Only: Public
- Read-Write: Private
- Read-Write-all: Secret
- No SNMP traps are enabled.
- The VLAN Trunking Protocol (VTP) interval is five minutes. No domain name is specified. The mode of operation is server. There is no VTP password. VTP is disabled by default.
- All VLANs are allowed for trunking. Trunking is set to auto mode for Fast Ethernet ports and non-trunking for Fiber Distributed Data Interface (FDDI) ports. All ports are nontrunk ports by default.
- No Ethernet-FDDI mapping is provided; no trunk traffic is forwarded.
- The native VLAN (internal Ethernet VLAN that translates to native FDDI packets) is 1.
- The trunk configuration, Ethernet-FDDI VLAN mapping, and the native VLAN are stored in the supervisor engine module nonvolatile RAM (NVRAM) and sent to the FDDI module after a module reset for configuration.
You can configure the switch through the CLI using three types of commands: set, show, and clear. Enter the set commands to establish switch parameters. After each set command, enter the show command to verify that you have entered the correct values and configured the switch correctly. If you make errors, enter the set or clear command to overwrite or erase the parameter.
For a list of available commands, enter set help, show help, or clear help. To display the command usage, enter the command and the word help, as the following example shows:
Console> (enable) set spantree hello help
Usage: set spantree hello [vlan]
(interval = 1..10, vlan = 1..1000)
Before you begin to configure your supervisor software, obtain the following information:
Note After SLIP is enabled and attached on the console port, an EIA/TIA-232 terminal cannot access the Catalyst 5000 series switch through this port.
Note The Supervisor Engine III has an auxiliary (AUX) port to which you can connect a modem for remote access to the switch.
After installing and connecting the switch, perform these steps to start up and access the switch. Refer to the Catalyst 5000 Series Installation Guide for details about how to install and connect the Catalyst 5000 series switch to a terminal.
| Task
| Command
|
|---|
| Step 1 Turn ON the power to the switch and the console terminal.
| None
|
| Step 2 Access the console port using the console terminal.
| None
|
| Step 3 At the Enter password: prompt, press Return.
| None
|
| Step 4 Enter privileged mode.
| enable-Switch Command
|
| Step 5 At the Enter password: prompt, press Return.
| None
|
After turning on the power to the switch and console terminal on systems with Supervisor Engines I and II, you see this initial bootup display:
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 Dec 5 1996 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:
Thu Mar 21 1996 03:20:41 Module 1 is online
Enter Password:
Thu Mar 21 1996 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>
Console> enable
Enter password:
Console> (enable)
Note The system only initiates a BOOTP or Reverse Address Resolution Protocol (RARP) request when the sc0 interface is set to
0.0.0.0 or when you enter the command
clear config all.
After turning on the power to the switch and console terminal on systems with Supervisor Engine III, you see this initial bootup display:
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
We recommend that you set several optional system parameters as part of the initial system setup. To set the system parameters, perform the following steps in privileged mode:
| Task
| Command
|
|---|
| Step 1 Set the system contact.
| set system contact contact_string
|
| Step 2 Set the system location string.
| set system location location_string
|
| Step 3 Set the system name.
| set system name name_string
|
| Step 4 Set the system clock.
| set time day_of_week mm/dd/yy hh:mm:ss
|
| Step 5 Set the system prompt.
| set prompt prompt_string
|
| Step 6 Set password protection for entering the command line in normal mode.
| set password
|
| Step 7 Set password protection for entering the command line in privileged mode.
| set enablepass
|
To set the interface type, perform these steps in privileged mode:
| Task
| Command
|
|---|
| Step 1 If you are using a local network connection to the console port, set the logical port sc0. Assign the Catalyst 5000 IP address to a VLAN.
| set interface sc0 up
set interface sc0 ip_address [netmask [broadcast]]
set interface sc0 vlan_num ip_address
|
| Step 2 If you are using a SLIP connection to the console port, set the slip port sl0.
| set interface sl0 up
set interface slip_address dest_address
|
| Step 3 Configure static routes.
| set ip route destination gateway [metric]
|
| Step 4 Configure a default route, if desired.
| set ip route destination gateway metric
|
| Step 5 Check the configuration status of the switch.
| show interface
|
| Step 6 Display the route table entries of the configuration.
| show ip route
|
You need to configure static routes entering the set ip route command if your Telnet station or SNMP network management workstation is on a different network from the switch.
After entering the show interface command, you see this display:
Console> (enable) show interface
sl0: flags=10
vlan 1 inet 0.0.0.0 netmask 0.0.0.0 broadcast 0.0.0.0
sc0: flags=863
inet 0.0.0.0 netmask 0.0.0.0 broadcast 0.0.0.0
Console> (enable)
After entering the set interface sc0 up command and the set ip route command, you see this display:
Console> (enable) set interface sc0 up
Interface sc0 administratively up.
Console> (enable) set interface sc0 192.200.11.44 255.255.255.0 192.200.11.255
Interface sc0 IP address and netmask set.
Console> (enable) set interface sl0 up
Interface sl0 administratively up.
Console> (enable) set interface sl0 192.200.10.45 192.200.10.103
Interface sl0 SLIP and destination address set.
Console> (enable) set interface sc0 5
Interface sc0 vlan set.
Console> (enable) set ip route default 192.122.173.42
Route added.
After the set interface command has been executed, the show interface command shows this configuration:
Console> (enable) show interface
sl0: flags=10
inet 192.200.10.45 netmask 192.200.10.45 broadcast 192.200.10.103
sc0: flags=863
vlan 1 inet 192.200.11.44 netmask 255.255.255.0 broadcast 192.200.11.255
Console> (enable)
After entering the show ip route command, you see this display:
Console> (enable) show ip route
Redirect
--------
enabled
Destination Gateway Flags Use Interface
--------------- --------------- ------ ---------- ---------
default 192.122.173.42 UG 59444 sc0
192.22.74.0 192.22.74.223 U 5 sc0
Console> (enable)
To configure the console port for SLIP, perform these steps:
| Task
| Command
|
|---|
| Step 1 Access the switch from a remote host with Telnet.
| None
|
| Step 2 Set the IP address of the console port.
| set interface slip_address dest_address
|
| Step 3 Enable the serial line interface protocol for the console port.
| slip attach
|
| Caution The SLIP connection must use the console port. While this connection is active, you lose your console port connection. If you are connected to the command line through the serial port and you enter the slip attach command, you will lose the console port connection. In that case, use Telnet to access the command line, enter privileged mode, and type slip detach to restore the console port or reset the switch.
|
Note The command line is not accessible from a direct local terminal. You must use SLIP to access it.
IP address information can be set using the Bootstrap Protocol (BOOTP). You can configure a BOOTP server with the Media Access Control (MAC) and IP addresses of the switch. When the switch boots, it automatically retrieves the IP address from the BOOTP server.
The switch performs a BOOTP request only if you set the current IP address to 0.0.0.0. This 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 Sun workstation, perform these steps:
| Task
| Command
|
|---|
| Step 1 Install the BOOTP server code on the workstation, if it is not already installed.
| None
|
| Step 2 Obtain the first address in the MAC address range for VLAN 1 in module 1 (the supervisor module). Choose the last address in the range on line 1 under the MAC-Address(es) heading.
| show module
|
| Step 3 Add an entry in the BOOTP configuration file (usually /usr/etc/bootptab) for each Catalyst 5000 series switch. Press Return after each entry to create a blank line between each entry.
| None
|
After you configure the IP address(es), test the connection between the switch and a host. The host can reside anywhere in your network. To test for connectivity, perform these steps:
| Task
| Command
|
|---|
| Step 1 Enter the ping command to send an echo request to the host specified in the command line.
| ping host
|
| Step 2 If necessary, reset the configuration to its default values, and reenter the configuration information.
| clear config
|
Note You must connect the host to a port with an address on the same IP network, or configure a static route entry to reach the host network. Refer to the
set ip route command in the
Catalyst 5000 Series Command Reference publication.
To test connectivity from the switch to a workstation with an IP address of 192.34.56.5, enter the command ping 192.34.56.5. If the switch receives a response, you see the following message:
192.34.56.5 is alive
Note Parameters set through the administrative interface remain set even if you disconnect power to the switch. The
clear config all command returns all parameters to their default values.
The Supervisor Engine III requires additional configuration that is not needed by the other supervisor engine modules. This section describes how to manage the Supervisor Engine III.
| Caution Some Catalyst 5000 supervisor engine software releases update the Supervisor Engine III erasable programmable logic devices (EPLDs). There is a finite number of times that the EPLDs can be updated. As a result, you should avoid loading a new software release and then backing out unnecessarily. Catalyst 5000 series release notes indicate which software releases have code that updates the EPLDs.
|
The Supervisor Engine III Flash memory contains a file system. You can use a variety of commands to manage the file system (such as cd, pwd, dir, delete, and copy). The file system includes the following devices:
For information on updating the software on a Supervisor Engine III, refer to Appendix A, "Downloading Files."
The Supervisor Engine III boot process involves two images: ROM monitor (a new image for Catalyst 5000 series supervisor engines) and Network Management Processor (NMP) code. The ROM monitor is the first software to run when the switch is powered up or reset. The NVRAM configuration specifies whether the Supervisor Engine III stays in ROM monitor mode or loads NMP code.
The configuration register boot field determines whether the switch loads an operating system image, and if so, where it obtains this system image. In addition to the configuration register, a boot environment variable is also used to specify the location and filename of images to boot. The BOOT environment variable specifies a list of bootable images on various devices. The set boot system flash commands set the BOOT environment variable.
You can modify the configuration register boot field to tell the switch if and how to load a system image upon startup. Also, instead of using the default system image to start up, you can specify a particular system image for the switch to use for start up.
The lowest four bits of the 16-bit configuration register (bits 3, 2, 1, and 0) form the boot field. Configuration register settings are as follows (the default value is 0x10F):
- When the entire boot field equals 0000, it does not load a system image. Instead, it enters ROM monitor mode from which you can enter ROM monitor commands to manually load a system image.
- When the entire boot field equals 0001, it loads the system image found in onboard Flash memory.
- When the entire boot field equals a value between 0010 and 1111, it loads the system image specified by boot system commands in the NVRAM configuration. It tries to boot the image in the order in which you enter the boot system commands. If it cannot boot any image in the BOOT environment variable list, it stays in ROM monitor mode. The exact booting sequence is defined by the ROM monitor.
Other bits in the configuration register are as follows:
- Bit 6 (0x0040): Causes system software to clear NVRAM contents
- Bit 7 (0x0080): OEM bit enabled (not used)
- Bit 8 (0x0100): Break disabled (scheduled for Supervisor Engine III release 2)
- Bit 9 (0x0200): Use secondary bootstrap (not used by the ROM monitor)
- Bit 10 (0x0400): IP broadcast with all zeros (not used)
- Bit 11/12 (0x0800/0x1000): Console line speed: 0/0=9600, 0/1=1200, 1/0=4800, 1/1=2400. (Default is 9600)
- Bit 13 (0x2000): Boot default Flash software if network boot fails (not used)
- Bit 14 (0x4000): IP broadcasts do not have network numbers (not used)
- Bit 15 (0x8000): Enable diagnostic messages and ignore NVRAM contents (not used)
The ROM monitor is a ROM-based program that is executed upon platform power-up, reset, or when a fatal exception occurs. The following functionality is built into the ROM monitor:
- Power-on confidence test
- Hardware initialization
- Boot capability (allows manual boot and autoboot)
- Debug utility and crash analysis
- Monitor call interface (EMT calls--the ROM monitor provides information and some functionality to the running system images via EMT calls)
- File system (the ROM monitor knows the simple file system and supports the newly developed file system through the dynamic linked file system library [MONLIB])
- Exception handling
Entering ROM Monitor Mode
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 the ROM monitor mode, you can manually load a system image from Flash memory, from a network server file, or from bootflash.
You can also enter ROM monitor mode by restarting the switch and then pressing the Break key during the first 60 seconds of startup.
Note Break is always enabled for 60 seconds after rebooting the system, regardless of whether Break is configured to be off by configuration-register settings.
For connection through a terminal server, you can escape to the Telnet prompt and type the send break command to enter ROM monitor mode.
ROM Monitor Commands
You can use the following commands with the ROM monitor.
- This command sets the default flash device for the system. If a device is not specified, the system defaults to slot0. The colon (:) is required and the valid devices for this command could be bootflash, slot0, or slot1. For those commands where device is an option, default device by cd will be used if device is not specified.
Console> cd bootflash:
Default flash device set to bootflash.
- This command shows the current setting of the cd command.
Console> pwd
bootflash
Console> cd
Default flash device set to slot0.
Console> pwd
slot0
- dir [[m/]device:] [filename] [all | deleted | long]
- The dir command displays a list of the files in Flash memory. The m/ device: variable is the name of the device on which the files reside, and the filename variable allows you to specify a particular file on the named device. If the device is not specified, the command defaults to the first device found.
- The all, deleted, and long keywords allow you to specify how the information is displayed.
- The boot command boots the switch manually. Entering the boot command with no options tells the system to boot from the first valid image found in bootflash. The device: variable tells the system to boot from the Flash device. The Flash device can be bootflash, slot0, or slot1. The filename variable specifies a specific file from which to boot. If filename is not specified, the command defaults to the first valid file found in the device. The filename variable is case sensitive.
- copy file-id {tftp | flash | file-id}
- copy tftp {flash | file-id}
- copy flash {tftp | file-id}
- The file-id argument has the format of m/device: filename. If the source or destination device is not specified, the command uses the ones specified by the cd command. If the destination filename is omitted, the software uses the source filename. The m/ option gives access to different modules, such as the standby supervisor engine, an FDDI module, and an ATM module. If copying to an FDDI or ATM module, you must specify the file-id as m/bootflash: without the filename. The flash keyword supports multiple module downloads. Based on the image file type, the system displays a prompt for all modules of the same type as the image file. A different prompt is given depending on the command argument and reply.
- The confreg global configuration command changes the configuration register settings. The value variable is a hexadecimal or decimal value that represents the 16-bit configuration register value that will be used the next time the switch is restarted.
| Caution If bit 6 (0x0040) in the configuration register is set, the system software will erase the configuration stored in NVRAM.
|
See the "Procedures" section later in this chapter for examples of using the ROM monitor commands.
Software release 3.1 provides several commands used to configure the boot parameters for the Supervisor Engine III module. These commands allow you to specify the image file(s) from which the system will boot and the configuration register value.
Specifying Boot Image Files
The BOOT environment variable specifies a list of image files from which the switch boots at startup.
- The set boot system flash command sets the BOOT environment variable. The arguments to the set boot system flash command are described as follows:
|
device:
| Tells the system to boot from the Flash device. The Flash device can be bootflash, slot0, or slot1.
|
| filename
| (Optional) Specifies a specific file from which to boot. If filename is not specified, the command defaults to the first valid file found in the device. The filename variable is case sensitive.
|
| prepend
| (Optional) Allows you to add new information to the beginning of the boot string, rather than at the end of the boot string, which is the default action. For example, if the current boot string is slot0:a;slot1:b and you want to add bootflash:c to the end of the boot string, you would issue the following command:
Console> (enable) set boot system flash bootflash:c
The boot string is now slot0:a;slot1:b:bootflash:c.
However, if you want to add bootflash:c to the beginning of the boot string, you would issue the same command and add the prepend option, as follows:
Console> (enable) set boot system flash bootflash:c prepend
The boot string is now bootflash:c;slot0:a;slot1:b.
|
| mod_num
| (Optional) Specifies which Supervisor Engine III module in a redundant configuration is affected. Unlike other configuration commands, boot commands issued to one supervisor engine are not copied automatically to the second supervisor engine.
|
- The clear boot system flash device:[filename] [mod_num] command clears the BOOT environment variable on the specified device.
- clear boot system all [mod_num]
- The clear boot system all [mod_num] command clears the entire BOOT environment variable. To rearrange the booting order, you must clear the entire BOOT environment variable first, and then redefine the list.
Note You can enter several set boot system flash commands to provide backup image files in case the first file fails to boot the switch. Because the system stores and executes the set boot system flash commands in the order in which they are entered, you must clear old entries before building a new image.
Setting the Configuration Register
The configuration register is a 16-bit value that specifies how the Supervisor Engine III module boots the next time the switch is restarted. Use the following commands to set the configuration register value:
Note In the following commands, the optional
mod argument specifies which Supervisor Engine III module in a redundant configuration is affected. Unlike other configuration commands,
set boot commands issued to one supervisor engine are not copied automatically to the second supervisor engine.
- This command sets the entire 16-bit configuration register value. The default value is 0x10F, which specifies the following settings:
- The boot device is the value specified by the BOOT environment variable
- The baud rate used by the ROM monitor is set to 9600
- The ignore-config parameter is disabled
- set boot config-register baud {1200 | 2400 | 4800 | 9600} [mod_num]
- This command sets the console baud rate to be 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. The default console baud rate used by the ROM monitor is 9600.
Note The baud rate specified in the configuration register is used by the ROM monitor only and is different from the baud rate specified by the set system baud command.
- set boot config-register ignore-config {enable | disable} [mod_num]
- This command allows you to enable and disable the ignore-config parameter. The ignore-config parameter, when enabled, causes system software to ignore the configuration information stored in NVRAM the next time the switch is restarted.
| Caution Enabling the ignore-config parameter is the same as issuing the clear config all command; that is, it will clear the entire configuration stored in NVRAM the next time the switch is restarted.
|
- This command effects the next system restart only. The ignore-config parameter is disabled by default.
- set boot config-register boot {rommon | bootflash | system} [mod_num]
- This command specifies the boot image to use on the next restart. Use the rommon keyword to stay in the ROM monitor, the bootflash keyword to boot from onboard Flash, or the system keyword to boot from the image specified by the set boot system command. By default, the system boots from the image specified by set boot system command.
Note We recommend that you use only the rommon and system options to the set boot config-register boot command.
Note Each time you enter one of the
set boot config-register commands, the system displays all current configuration-register information (the equivalent of entering the
show boot command).
Flash File System Commands
The following commands are used to configure the files in the Flash file system.
- The delete command deletes any file on a Flash memory device. When you delete a file, the system software marks the file as deleted, but does not erase the file.
- The undelete command recovers a file deleted from a Flash memory device. Because there could be multiple deleted files with the same name, you can specify the index variable to identify a specific file. Use the dir command to learn the file's index number.
- A file cannot be undeleted if a valid one with the same name exists. Instead, you must delete the existing file first and then undelete the target file. A file can be deleted/undeleted up to 15 times.
- The squeeze command permanently deletes a file from a Flash memory device.
- Before a new Flash device can be used, it must first be formatted. Up to 16 (default 0) spare sectors can be reserved for use when other sectors fail. If no spare sector is reserved and later some sectors fail, the entire Flash memory must be reformatted, erasing all existing data.
- The monlib file is the ROM monitor library used by the ROM monitor to access files in the Flash file system. It is also compiled into the system image. In the command syntax, device1 is the device to format and device2 contains the monlib file to use. If you omit the [[device2:][monlib-filename]] argument, the system formats device1 using the monlib that is bundled with the system software. If you omit device2 from the [[device2:][monlib-filename]] argument, the system formats device1 using the named monlib file from the device specified by the cd command. If you omit monlib-filename from the [[device2:][monlib-filename]] argument, the system formats device1 using the monlib file from device2. When you specify the whole [[device2:][monlib-filename]] argument, the system formats device1 using the specified monlib file from the specified device.
Note You can specify device1's own monlib file in this argument. When the system cannot find a monlib file, it terminates the formatting process.
- verify [[m/]device:] filename
- The verify command verifies the checksum of a file on a Flash memory device.
See the "Procedures" section later in this chapter for examples of using the boot commands.
For a complete list of Flash system commands, refer to the Catalyst 5000 Series Command Reference publication.
This section provides procedures for managing the Supervisor Engine III module.
To set the BOOT environment variable, perform this task:
| Task
| Command
|
|---|
| Set the BOOT environment variable.
| set boot system flash device:[filename] [prepend] [mod_num]
|
After issuing these commands, you see the following display:
Console> (enable) set boot system flash slot0:cat5k_r47_1.cbi
BOOT variable = slot0:cat5k_r47_1.cbi;
Console> (enable)
This command appends the filename as cat5k_r47_2.cbi on device slot0 to the BOOT environment variable:
Console> (enable) set boot system flash slot0:cat5k_r47_2.cbi
BOOT variable = slot0:cat5k_r47_1.cbi;slot0:cat5k_r47_2.cbi;
Console> (enable)
This command prepends bootflash:c to the beginning of the boot string:
Console> (enable) set boot system flash bootflash:c prepend
Console> (enable)
To display the contents of the BOOT environment settings, perform this task:
| Task
| Command
|
|---|
| Display the contents of the BOOT environment variable.
| show boot [mod_num]
|
After issuing these commands, you see the following display:
Console> show boot
BOOT variable = slot0:cat5k_r47_1.cbi;slot0:cat5k_r47_2.cbi;
Configuration register is 0x10f
ignore-config: disabled
console baud: 9600
boot: image specified by the boot system commands
Console>
To set the default Flash device for the system, perform the following tasks:
| Task
| Command
|
|---|
| Step 1 Identify the supported Flash devices on the system.
| show flash devices
|
| Step 2 Set the default Flash device for the system.
| cd [[m/][bootflash: | slot0: | slot1:]]
|
| Step 3 Verify the default Flash device for the system.
| pwd [mod_num]
|
After issuing these commands, you see the following display:
Console> show flash
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. 2 43B312DF 100fc0 15 1052608 Nov 27 1996 10:23:30 cat5k_r47_1.cbi
7336000 bytes available (1052608 bytes used)
Console>
Console> cd bootflash:
Default flash device set to bootflash.
Console>
Console> pwd
bootflash
Console>
To delete or restore files on a Flash device, enter the following commands:
| Task
| Command
|
|---|
| Delete a file on a Flash device.
| delete [[m/]device:]filename
|
| Undelete a file on a Flash device.
| undelete index [[m/]device:]
|
| Permanently delete a file on a Flash device.
| squeeze [m/]device:
|
After issuing these commands, you see the following display:
Console> (enable) delete slot1:some-other-image
slot1:some-other-image has been deleted.
Console> (enable)
Console> (enable) undelete 1 slot1
slot1:some-other-image has been recovered.
Console> (enable)
Console> (enable) squeeze slot0:
All deleted files will be removed, proceed (y/n) [n]?y
Squeeze operation may take a while, proceed (y/n) [n]?y
Erasing squeeze log
Console> (enable)
To copy files on a Flash device, enter the following commands:
| Task
| Command
|
|---|
| Copy a Flash file to a TFTP server, Flash memory, or another Flash device.
| copy m/device:filename {tftp | flash | m/device:filename}
|
| Copy a file from a TFTP server to Flash memory or to a Flash device.
| copy tftp {flash | m/device:filename}
|
| Copy a file from Flash memory to a TFTP server or to a Flash device.
| copy flash {tftp | m/device:filename}
|
The following examples include the show flash command, which you can use to display the contents of the Flash device after each copy command is entered:
Console> (enable) copy cat5k_r47_1.cbi slot1:
7995264 bytes available on device 1/slot1, proceed (y/n) [n]?y
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
File has been copied successfully.
Console> (enable)
Console> (enable) show flash slot1:
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. 2 43B312DF 201ed8 15 1052608 Nov 30 1996 11:12:30 cat5k_r47_1.cbi
6942656 bytes available (1052736 bytes used)
Console> (enable)
Console> (enable) copy cat5k_r47_1.cbi slot1:
6942528 bytes available on device 1/slot1, proceed (y/n) [n]?y
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
File has been copied successfully.
Console> (enable)
Console> (enable) show flash slot1:
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .D 2 43B312DF 201ed8 15 1052608 Nov 30 1996 11:12:30 cat5k_r47_1.cbi
1 .. 2 43B312DF 201ed8 15 1052608 Nov 30 1996 11:18:25 cat5k_r47_1.cbi
5889920 bytes available (2105472 bytes used)
Console> (enable)
To display information on Flash memory and the Flash files, enter the following commands:
| Task
| Command
|
|---|
| Verify the checksum of a file on a Flash device.
| verify [[m/]device:] filename
|
| Display a list of files on a Flash device.
| dir [[m/]device:][filename] [all | deleted | long]
|
| Display information about the Flash memory.
| show flash [[m/]device:] [all | chips | filesys]
|
After entering these commands, you see the following display:
Console> (enable) verify cat5k_r47_1.cbi
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
File cat5k_r47_1.cbi verified OK.
Console> (enable)
Console> dir
-#- -length- -----date/time------ name
2 1052608 Jun 26 1995 15:43:50 cat5k_r47_1.cbi
Console>
Console> show flash
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .D 2 2D6B310A 100fc0 15 1052123 Nov 26 1996 15:43:50 cat5k_r47_1.cbi
2 .. 2 43B312DF 201ed8 15 1052608 Nov 27 1996 10:23:30 cat5k_r47_1.cbi
6283877 bytes available (2104731 bytes used)
Console>
To format a Flash memory device, perform the following task:
| Task
| Command
|
|---|
| Format a Flash memory device.
| format [spare spare-number] [m/]device1: [[device2:] [monlib-filename]]
|
After entering this command, you see the following display:
Console> (enable) format slot1:
All sectors will be erased, proceed (y/n) [n]?y
Enter volume id (up to 31 characters):
Formatting sector 1
Format device slot1 completed.
Console> (enable)
To set the configuration register, perform the following task:
| Task
| Command
|
|---|
| Set the configuration register.
| set boot config-register 0xvalue [mod_num]
|
The following command sets the configuration register value to 0x10f (the default):
Console> (enable) set boot config-register 0x10f
Configuration register is 0x10f
ignore-config: disabled
console baud: 9600
boot: image specified by the boot system commands
To change the ROM monitor baud rate in the configuration register, perform this task:
| Task
| Command
|
|---|
| Change the ROM monitor baud rate in the configuration register.
| set boot config-register baud {1200 | 2400 | 4800 | 9600} [mod_num]
|
The following command changes the ROM monitor baud rate in the configuration register to 4800:
Console> (enable) set boot config-register baud 4800
Configuration register is 0x90f
ignore-config: disabled
console baud: 4800
boot: image specified by the boot system commands
To enable the ignore-config option in the configuration register, perform this task:
| Task
| Command
|
|---|
| Enable the ignore-config option in the configuration register.
| set boot config-register ignore-config enable
|
After entering this command, you see the following display:
Console> (enable) set boot config-register ignore-config enable
Configuration register is 0x94f
ignore-config: enabled
console baud: 4800
boot: image specified by the boot system commands
Console> (enable)
To specify the boot image to use on the next restart in the configuration register, perform this task:
| Task
| Command
|
|---|
| Specify the boot image to use on the next restart in the configuration register.
| set boot config-register boot {rommon | bootflash | system} [mod_num]
|
The following command specifies rommon as the boot image to use on the next restart:
Console> (enable) set boot config-register boot rommon
Configuration register is 0x100
ignore-config: disabled
console baud: 9600
boot: the ROM monitor
Console> (enable)
Note We recommend using the
rommon and
system options of the
set boot config-register boot command only.
