|
|
This chapter describes how to perform the following configuration tasks:
For module-specific default configurations, refer to the Catalyst 5000 Series Module Installation Guide. For detailed descriptions and configuration instructions, refer to the Catalyst 5000 Series Software Configuration Guide.
The supervisor engine is brought online as follows:
1 ) If you installed a new supervisor engine, the system uses the factory default configuration. Log in to your console, and enter show config to display the defaults. For a limited list of commands to make minor changes to your default configuration, see the section "Changing the Default Configuration."
2 ) If you reinstalled the original supervisor engine, the system uses the configuration that was last stored in memory before the supervisor engine was removed. All interfaces should function as they did before removal. Log in to your console, and enter the show config command to verify the configuration.
3 ) If you installed a supervisor engine from another switch, the supervisor engine is configured for the other interfaces, and its configuration is probably not compatible with the current switch. Log in to your console, and enter show config to verify the configuration. If the configuration is compatible with this switch, you need not reconfigure the system. If the configuration is not compatible, run the clear config command to return the supervisor engine to its factory defaults, and then customize the configuration to your requirements.
You can use a configuration register for configuring the ROM monitor in addition to a boot environment variable that you set to specify the location and filename of images to boot. Both these configuration tools are described in the following sections.
You can modify the configuration register boot field to specify the method that the switch uses to load a system image upon startup. Instead of using the default system image to start up, you can specify a particular system image for the switch to use.
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):
Other bits in the configuration register are as follows:
Caution If bit 6 (0x0040) is set, the system software erases the configuration stored in NVRAM.
The ROM monitor is a ROM-based program that executes upon platform power-up, reset, or when a fatal exception occurs. The following functionality is built into the ROM monitor:
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.
For connection through a terminal server, you can escape to the Telnet prompt and enter the send break command to break back to ROM monitor mode.
The manual boot command has the following syntax:
The ROM monitor commands are listed below and described in the following paragraphs. You can obtain additional information about a command by typing the command name with a -? option. Command descriptions are in the order displayed.
rommon 1 > help alias set and display aliases command boot boot up an external process confreg configuration register utility dev list the device table dir list files in file system help monitor builtin command help history monitor command history meminfo main memory information repeat repeat a monitor command reset system reset set set a monitor variable sync write monitor environment to NVRAM unalias unset an alias unset unset a monitor variable
Creates an alias (value) for a name. If the value contains a space or other special (shell) characters, you must place it in quotes. If the value has a space as its last character, the next command line word is also checked for an alias (normally only the first word on a command line is checked). Without an argument, this command prints a list of all aliased names and their values. An example follows:
rommon 1 > alias r=repeat h=history ?=help b=boot ls=dir
Boots an image. Without an argument, the first image in Flash is booted. You can specify an image by typing its name. Specify the device by typing the device id. If the device is partitioned and the image is not in the first partition, you must specify the partition number. If no device is given with an imagename, the image is net booted. If a device name is not recognized by the ROM monitor, it assumes netbooting and passes the device id to the boot helper image. Options to the boot command are -x, load image but do not execute and -v, verbose.
When executed with the argument hexnum, the configuration register is changed to match the hexadecimal number specified. Without the hexnum argument, confreg displays the contents of the configuration register in plain English and allows you to alter the contents. You are prompted to change or keep the information held in each bit of the configuration register. In either case the new configuration register value is written into NVRAM and takes effect after you reset the switch. An example follows:
rommon 1 > confreg
Configuration Summary
enabled are:
console baud: 9600
boot: the ROM Monitor
do you wish to change the configuration? y/n [n]: y
enable "diagnostic mode"? y/n [n]: y
enable "use net in IP bcast address"? y/n [n]:
enable "load rom after netboot fails"? y/n [n]:
enable "use all zero broadcast"? y/n [n]:
enable "break/abort has effect"? y/n [n]:
enable "ignore system config info"? y/n [n]:
change console baud rate? y/n [n]: y
enter rate: 0 = 9600, 1 = 4800, 2 = 1200, 3 = 2400
4 = 19200, 5 = 38400, 6 = 57600, 7 = 115200 [0]: 0
change the boot characteristics? y/n [n]: y
enter to boot:
0 = ROM Monitor
1 = the boot helper image
2-15 = boot system
[0]: 0
Configuration Summary
enabled are:
diagnostic mode
console baud: 9600
boot: the ROM Monitor
do you wish to change the configuration? y/n [n]:
You must reset or power cycle for new config to take effect
Lists the device IDs available on the switch. An example follows:
rommon 1 > dev
Devices in device table:
id name
flash: flash
slot0: PCMCIA slot 0
slot1: PCMCIA slot 1
eprom: eprom
Lists the files on a partition of the named device. If you do not specify a partition, it defaults to the first partition. An example follows:
rommon 1 > dir flash:
File size Checksum File name
65 bytes (0x41) 0xb49d clev/oddfile65
2229799 bytes (0x220627) 0x469e clev/sierra-k.Z
rommon 12 > dir flash:2:
File size Checksum File name
2229799 bytes (0x220627) 0x469e mars-image
Displays the command history, the last 16 commands executed in the ROM monitor environment. For convenience, this command is aliased to the letter "h" by the ROM monitor.
Provides information about the main memory, packet memory, and NVRAM. Enter the -l option to display the supported DRAM configurations.
rommon 1 > meminfo Main memory size: 16 MB in 32 bit mode. Available main memory starts at 0xa000e000, size 16328KB IO (packet) memory size: 25 percent of main memory. NVRAM size: 32KB
Repeats commands. Without an argument, the last command is repeated. The optional command number (from the history list) or match string specifies which command to repeat. In the case of the match string, the most recent command to begin with the specified string is reexecuted. If the string contains white space, it must be quoted. This command is usually aliased to the letter "r."
Resets the switch.
Displays the monitor variable names with their values.
Writes the working in-core copy of environment variables and aliases out to NVRAM so they are read on the next reset. Analogous to the system write memory command, but for ROM monitor configurations only.
Removes an alias name and its associated value from the alias list.
Removes a variable name from the variable list. Note that this command is different from the command VARNAME= that sets the variable to a NULL string.
Sets the ROM monitor variable VARNAME to varvalue. Do not insert a space before or after the equal (=) sign. If there are spaces, you must place the varvalue in quotes. Spell variable names in all caps to make them conspicuous.
Software release 4.1 provides several commands that you can enter 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.
Enter the following commands to set the BOOT environment variable that specifies a list of images the switch loads at startup. If you do not specify a filename, the file to boot is the first valid file in the device. You can enter several boot system commands to provide a fail-safe method for booting the switch. The system stores and executes the boot system commands in the order in which you enter them.
The set boot system flash device:[filename] [prepend] [mod_num] 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, enter this 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, enter 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 system stores and executes the boot system commands in the order in which you enter them. The clear boot system all command clears the entire BOOT environment variable. If you want to rearrange the booting order, you need to clear them all first, and then redefine the list. An example follows:
Console> (enable) clear boot system all [mod_num] Console> (enable) set boot system flash slot0:cat5k_r47_1.cbi BOOT variable = slot0:cat5k_r47_1.cbi; Console> (enable) set boot system flash slot0:cat5k_r47_2.cbi BOOT variable = slot0:cat5k_r47_1.cbi;slot0:cat5k_r47_2.cbi;
Clear an individual image as follows:
Console> (enable) clear boot system flash device:[filename] [mod_num]
The configuration register is a 16-bit value that specifies how the Supervisor Engine III module boots the next time the switch is restarted. The default value is 0x10F, which causes the switch to boot from what is specified by the BOOT environment variable. The choices are stay in ROM monitor, boot from onboard Flash, or use the image specified by the set boot system command. Enter the following commands to set the configuration register value:
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.
This section describes commands used to manage the Flash file system.
Sets the default Flash device. If you do not specify a device, the system defaults to slot0. The colon (:) is required and the valid devices are bootflash, slot0, and slot1. When you enter a command where device is an option, if you do not specify a device, the device used is that set by the cd command. In the example, bootflash is set as the default Flash device.
Console> cd bootflash: Default flash device set to bootflash.
Shows the current setting of the cd command. Note that when the cd command is used without specifying a device, the system defaults to slot0.
Console> pwd bootflash Console> cd Default flash device set to slot0. Console> pwd slot0
Displays the files on a Flash memory device, as follows:
Examples of the dir command follow:
Console> dir -#- -length- -----date/time------ name 2 1052608 Apr 15 1998 15:43:50 cat5k_r47_1.cbi 6283877 bytes available (2104731 bytes used) Console> dir long -#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name 2 .. 2 43B312DF 201ed8 15 1052608 Apr 15 1998 15:43:50 cat5k_r47_1.cbi 6283877 bytes available (2104731 bytes used) Console> dir all -#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name 1 .D 2 2D6B310A 100fc0 15 1052123 Apr 15 1998 15:43:50 cat5k_r47_1.cbi 2 .. 2 43B312DF 201ed8 15 1052608 Apr 16 1998 10:23:30 cat5k_r47_1.cbi 6283877 bytes available (2104731 bytes used) Console>
Deletes a file or recovers a deleted 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 deleted file can be recovered by using the undelete command followed by the file index number (#). Enter the dir command to get the index number of the file you want to be undeleted.
A file cannot be undeleted if a valid file with the same name exists. The existing file must be deleted first and then you can undelete the target file. A file can be deleted or undeleted up to 15 times. To permanently delete all deleted files on a device, enter the squeeze command. Examples of the undelete and delete commands follow:
Console> (enable) undelete 1 File undelete error (file not unique) Console> (enable) delete slot1:some-other-image slot1:some-other-image has been deleted. Console> (enable) undelete 1 slot1 slot1:some-other-image has been recovered.
Permanently deletes Flash files as follows:
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)
Before you can use a new Flash card, you must format it. The format command syntax follows:
format [spare spare-number] [m/]device1: [[device2:][monlib-filename]]
You can reserve up to 16 (default 0) spare sectors for use when other sectors fail. If you do not reserve a spare sector and some sectors fail, you must reformat the whole Flash memory, which erases all existing data.
The monlib-filename 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. device1 is the device to format and device2 contains the monlib filename to use. When you omit the [[device2:][monlib-filename]] argument, the system formats device1 using the ROM monitor library file that is bundled with the system software. When 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. When you omit monlib-filename from the [[device2:][monlib-filename]] argument, the system formats device1 using device2's ROM monitor library file. When you specify the entire [[device2:][monlib-filename]] argument, the system formats device1 using the specified ROM monitor library file from the specified device. You can specify device1's own ROM monitor library file in this argument. When the system cannot find a file, the system terminates the formatting process. An example of the format command follows:
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.
Verifies the checksum of a file on a Flash device, as follows:
Console> (enable) verify cat5k_r47_1.cbi CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC File cat5k_r47_1.cbi verified OK.
The following commands are used to copy files:
The file-id argument has the format of m/device: filename. The general rule for the default is that if the source or destination device is not given, use the one 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, FDDI, and ATM. For FDDI and ATM, the only combination of file-id is m/bootflash: without filename. The flash keyword is based on the current implementation and is provided to support multiple module downloads. Based on the file type derived, a prompt is given for all modules of the same type. Different prompts are given depending on the command argument and reply. Some examples follow:
Console> (enable) pwd slot0 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) show flash slot1: -#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name 1 .. 2 43B312DF 201ed8 15 1052608 Apr 15 1998 11:12:30 cat5k_r47_1.cbi 6942656 bytes available (1052736 bytes used) Console> (enable) copy cat5k_r47_1.cbi slot1: 6942528 bytes available on device 1/slot1, proceed (y/n) [n]?y CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCcccccccccccccccccccccccccccccccccccccccccccccccccccc ccccccccccccccccCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC File has been copied successfully. Console> (enable) show flash slot1: -#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name 1 .D 2 43B312DF 201ed8 15 1052608 Apr 15 1998 11:12:30 cat5k_r47_1.cbi 1 .. 2 43B312DF 201ed8 15 1052608 Apr 15 1998 11:18:25 cat5k_r47_1.cbi 5889920 bytes available (2105472 bytes used) Console> (enable) < after copy 5 more times >
When there is not enough space to copy the new file (as shown in the following example), you need to either squeeze or format the device:
Console> (enable) copy cat5k_r47_1.cbi slot1: 626112 bytes available on device 1/slot1, proceed (y/n) [n]?y CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCcccccccccccc Not enough space left on device 1/slot1 Console> (enable)
These examples show how to download an image from TFTP to a Flash device and from a Flash device to ATM and FDDI modules:
Console> (enable) copy tftp slot0: Address or name of remote host [172.20.22.7]? Enter source file name [cat5k_r47_1.cbi]? Enter destination file name [cat5k_r47_1.cbi]? 6942528 bytes available on device slot0, proceed (y/n) [n]?y CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCcccccccccccccccccccccccccccccccccccccccccccccccccccc ccccccccccccccccCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC File has been copied successfully. Console> (enable) copy slot0:fddi_image 5/bootflash: Download slot0:fddi_image to Module 5 FLASH (y/n) [n]?
This example shows a module download for supervisor engine modules:
Console> (enable) copy tftp flash Address or name of remote host [172.20.22.7]? Enter source file name [cat5k_r47_1.cbi]? Flash device [slot0]? Enter destination file name [cat5k_r47_1.cbi]? 6942528 bytes available on device slot0, proceed (y/n) [n]?y CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCcccccccccccccccccccccccccccccccccccccccccccccccccccc ccccccccccccccccCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC File has been copied successfully.
This example shows a multiple module download for FDDI modules:
Console> (enable) copy tftp flash Address or name of remote host [172.20.22.7]? Enter source file name [cat5k_r47_1.cbi]? fddi_image Download image fddi_image to Module 5 FLASH (y/n) [n]? y Download image fddi_image to Module 7 FLASH (y/n) [n]? n Download image fddi_image to Module 8 FLASH (y/n) [n]? y
Displays the names of the supported Flash devices, as follows:
Console> show flash devices bootflash, slot0, slot1, tftp.
The show flash command without any option is like the dir command with the all option (lists deleted files, undeleted files, and files with errors). The chips option shows information about the chip, including which bank the chip is in and its code. The filesys option shows the Device Info Block, Status Info, and Usage Info. Examples of show flash and its options follow:
Console> show flash
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .D 2 2D6B310A 100fc0 15 1052123 Apr 15 1998 15:43:50 cat5k_r47_1.cbi
2 .. 2 43B312DF 201ed8 15 1052608 Apr 15 1998 10:23:30 cat5k_r47_1.cbi
6283877 bytes available (2104731 bytes used)
Console> show flash chips
******** Intel Series 2+ Status/Register Dump ********
ATTRIBUTE MEMORY REGISTERS:
Config Option Reg (4000): 2
Config Status Reg (4002): 0
Card Status Reg (4100): 1
Write Protect Reg (4104): 4
Voltage Cntrl Reg (410C): 0
Rdy/Busy Mode Reg (4140): 2
COMMON MEMORY REGISTERS: Bank 0
Intelligent ID Code : 8989A0A0
Compatible Status Reg: 8080
Global Status Reg: B0B0
Block Status Regs:
0 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
8 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
16 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
24 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
COMMON MEMORY REGISTERS: Bank 1
Intelligent ID Code : 8989A0A0
Compatible Status Reg: 8080
Global Status Reg: B0B0
Block Status Regs:
0 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
8 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
16 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
24 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
COMMON MEMORY REGISTERS: Bank 2
Intelligent ID Code : FF00FF
IID Not Intel -- assuming bank not populated
COMMON MEMORY REGISTERS: Bank 3
Intelligent ID Code : FF00FF
IID Not Intel -- assuming bank not populated
COMMON MEMORY REGISTERS: Bank 4
Intelligent ID Code : FF00FF
IID Not Intel -- assuming bank not populated
Console> show flash filesys
-------- F I L E S Y S T E M S T A T U S --------
Device Number = 0
DEVICE INFO BLOCK:
Magic Number = 6887635 File System Vers = 10000 (1.0)
Length = 800000 Sector Size = 20000
Programming Algorithm = 4 Erased State = FFFFFFFF
File System Offset = 20000 Length = 7A0000
MONLIB Offset = 100 Length = C730
Bad Sector Map Offset = 1FFF8 Length = 8
Squeeze Log Offset = 7C0000 Length = 20000
Squeeze Buffer Offset = 7E0000 Length = 20000
Num Spare Sectors = 0
Spares:
STATUS INFO:
Writable
NO File Open for Write
Complete Stats
No Unrecovered Errors
USAGE INFO:
Bytes Used = 201D9B Bytes Available = 5FE265
Bad Sectors = 0 Spared Sectors = 0
OK Files = 1 Bytes = 100FC0
Deleted Files = 1 Bytes = 100DDB
Files w/Errors = 0 Bytes = 0
Console> show flash all
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .D 2 2D6B310A 100fc0 15 1052123 Apr 15 1998 15:43:50 cat5k_r47_1.cbi
2 .. 2 43B312DF 201ed8 15 1052608 Apr 15 1998 10:23:30 cat5k_r47_1.cbi
6283877 bytes available (2104731 bytes used)
-------- F I L E S Y S T E M S T A T U S --------
Device Number = 0
DEVICE INFO BLOCK:
Magic Number = 6887635 File System Vers = 10000 (1.0)
Length = 800000 Sector Size = 20000
Programming Algorithm = 4 Erased State = FFFFFFFF
File System Offset = 20000 Length = 7A0000
MONLIB Offset = 100 Length = C730
Bad Sector Map Offset = 1FFF8 Length = 8
Squeeze Log Offset = 7C0000 Length = 20000
Squeeze Buffer Offset = 7E0000 Length = 20000
Num Spare Sectors = 0
Spares:
STATUS INFO:
Writable
NO File Open for Write
Complete Stats
No Unrecovered Errors
USAGE INFO:
Bytes Used = 201D9B Bytes Available = 5FE265
Bad Sectors = 0 Spared Sectors = 0
OK Files = 1 Bytes = 100FC0
Deleted Files = 1 Bytes = 100DDB
Files w/Errors = 0 Bytes = 0
******** Intel Series 2+ Status/Register Dump ********
ATTRIBUTE MEMORY REGISTERS:
Config Option Reg (4000): 2
Config Status Reg (4002): 0
Card Status Reg (4100): 1
Write Protect Reg (4104): 4
Voltage Cntrl Reg (410C): 0
Rdy/Busy Mode Reg (4140): 2
COMMON MEMORY REGISTERS: Bank 0
Intelligent ID Code : 8989A0A0
Compatible Status Reg: 8080
Global Status Reg: B0B0
Block Status Regs:
0 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
8 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
16 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
24 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
COMMON MEMORY REGISTERS: Bank 1
Intelligent ID Code : 8989A0A0
Compatible Status Reg: 8080
Global Status Reg: B0B0
Block Status Regs:
0 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
8 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
16 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
24 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
COMMON MEMORY REGISTERS: Bank 2
Intelligent ID Code : FF00FF
IID Not Intel -- assuming bank not populated
COMMON MEMORY REGISTERS: Bank 3
Intelligent ID Code : FF00FF
IID Not Intel -- assuming bank not populated
COMMON MEMORY REGISTERS: Bank 4
Intelligent ID Code : FF00FF
IID Not Intel -- assuming bank not populated
bootflash, slot0, slot1, tftp
The show microcode command without an option shows all the files in every Flash device along with the device:filename header for each file, as follows:
Console> (enable) show microcode Bundled Images Version Size(bytes) Built --------------- ---------- ------------ ----------------- LCP51-32 4.1(0.47) 25587 04/01/98 05:45:12 LCP51-64 4.1(0.57) 52917 04/14/98 05:53:33 MCP360 4.1(0.57) 172144 04/14/98 06:09:07 LCP360 4.1(0.57) 125588 04/14/98 06:06:04 TOKEN-RING 4.1(0.57) 29473 04/14/98 05:49:50 ATM/FDDI LCP 4.1(0.57) 25054 04/14/98 05:45:52 C5IP 4.1(0.57) 24394 04/14/98 05:53:37 Console> (enable)
This section provides procedures for managing the Supervisor Engine III module.
To set the BOOT environment variable, enter this command:
| Task | Command |
|---|---|
| Set the BOOT environment variable. | set boot system flash device:[filename] [prepend] [mod_num] |
After entering these commands, you see this 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, enter this command:
| Task | Command |
|---|---|
| Display the contents of the BOOT environment variable. | show boot [mod_num] |
After entering this command, you see this 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, enter these commands:
| 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 entering these commands, you see these displays:
Console> show flash -#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name 1 .. 2 43B312DF 100fc0 15 1052608 Apr 15 1998 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 these 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 entering these commands, you see these displays:
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 these 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} |
These examples include the show flash command, which you can enter 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 Apr 15 1998 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 Apr 15 1998 11:12:30 cat5k_r47_1.cbi 1 .. 2 43B312DF 201ed8 15 1052608 Apr 15 1998 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 these 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 these displays:
Console> (enable) verify cat5k_r47_1.cbi CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC File cat5k_r47_1.cbi verified OK. Console> (enable) Console> (enable) dir -#- -length- -----date/time------ name 2 1052608 Apr 16 1998 15:43:50 cat5k_r47_1.cbi Console> (enable) Console> (enable) show flash -#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name 1 .D 2 2D6B310A 100fc0 15 1052123 Apr 15 1998 15:43:50 cat5k_r47_1.cbi 2 .. 2 43B312DF 201ed8 15 1052608 Apr 16 1998 10:23:30 cat5k_r47_1.cbi 6283877 bytes available (2104731 bytes used) Console> (enable)
To format a Flash memory device, enter this command:
| Task | Command |
|---|---|
| Format a Flash memory device | format [spare spare-number] [m/]device1: [[device2:] [monlib-filename]] |
After entering this command, you see this 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, enter this command:
| Task | Command |
|---|---|
| Set the configuration register. | set boot config-register 0xvalue [mod_num] |
This 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, enter this command:
| Task | Command |
|---|---|
| Change the ROM monitor baud rate in the configuration register. | set boot config-register baud {1200 | 2400 | 4800 | 9600} [mod_num] |
This 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, enter this command:
| Task | Command |
|---|---|
| Enable the ignore-config option in the configuration register. | set boot config-register ignore-config enable |
After entering this command, you see this 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, enter this command:
| 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] |
This 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)
The Catalyst 5000 series switch has features that you can customize, but the default values might suit your environment. The default values of these features are set as follows:
The commands listed in Table 5-1 are used to change the default configuration. Additional configuration commands are listed in Table 5-2.
| Task | Command |
|---|---|
| Uploading/downloading system information | upload or download |
Establishing the console port connection
|
enable |
Setting the system information
|
set system contact contact_string set system location location_string set system name name_string set time day_of_week mm/dd/yy hh:mm:ss set prompt prompt_string set password set enablepass |
Setting the interface type
|
set interface sc ip_address [netmask[broadcast]] set ip route default gateway [metric] |
Configuring SLIP1 on the console port
|
set interface slip_address_dest_address |
| Configuring SNMP management | set snmp community read-only | read_write | read_write_all community string set snmp trap rcvr_address rcvr_community set snmp trap enable |
| Configuring MLS | Refer to the Catalyst 5000 Series Multilayer Switching User Guide for configuration details |
| Setting an Ethernet or Fast Ethernet port name
| set port name mod_num/port_num [name_string] |
| Setting an Ethernet or Fast Ethernet port priority level | set port level mod_num/port_num normal | high |
| Setting 10/100Base TX port speed | set port speed mod_num/port_num [10 | 100 | auto] |
| Setting the Ethernet or Fast Ethernet port transmission type | set port duplex mod_num/port_num half | full |
| Setting an FDDI/CDDI2 port name | set port name mod_num/port_num [name_string] |
| Setting an FDDI/CDDI port priority level | set port level mod_num/port_num normal | high |
| Task | Command |
| Send ICMP1 echo request packets to another node on the network. | ping |
| Show the system configuration. | show configuration |
| Show the module information. | show module |
| Show the port information. | show port |
| Show the system information. | show system |
| Start a Telnet connection to a remote system. | telnet |
All module default configuration information is in the Catalyst 5000 Series Module Installation Guide shipped with the switch. For information on other configurations, refer to the Catalyst 5000 Series Software Configuration Guide.
Periodically, there will be new software to implement features and enhancements or maintenance releases. You can use the following two methods to update the software on the Catalyst 5000 series switch:
Use the procedures in the following sections to verify your current software version and then, if necessary, download new software to the supervisor engine.
When you start the system, the system loads the system image from Flash memory. You can enter the show flash or show version commands to display the current system image version.
The show version and show flash commands show the current Flashcode version on the first line of the supervisor engine display.
If the display shows that the system image loading from Flash memory is not the correct version, enter the download command to load the new system image to the supervisor engine module (see the next section "Downloading a New System Image" for a TFTP download procedure).
To download a new image into Flash memory, perform the following steps from a console, using TFTP:
Step 1 Ensure that the workstation acting as the download server has the TFTP daemon.
Step 2 On Sun workstations, make sure the /etc/inetd.conf file contains this line:
Make sure the /etc/services file contains this line:
Step 3 Copy the new software from the floppy disks to the home directory specified for the TFTP daemon on the workstation (usually /tftpboot). If this directory does not exist, create it before continuing. The file you copy is c5009_xx.bin, where xx is the software revision number.
Step 4 Log in to the switch through the command line or through a Telnet session.
Step 5 Enter the download host file command. Specify the IP address or host name of the workstation acting as the download server. Also specify the file to download. If you are downloading a software file for an FDDI or ATM module, you must also specify the module number. The following is the command syntax:
In the following example, when no module number is given, the file downloads by default to module 1:
Console> (enable) download 190.180.122.40 c5009_11xx.binStep 6 When the following prompt appears, press y:
The switch erases the Flashcode and reprograms modules on the supervisor card with the downloaded Flashcode:
Step 7 Reset the switch.
Step 8 Perform the following steps to verify that the new Flashcode version is loaded:
(a) Look at the module status LEDs and verify that the interfaces return to the same state they were in prior to the download (some might have been shut down). If a status LED fails to go on after a second installation attempt, or if any of the interfaces fail to return to their previous states, see Chapter 6, "Troubleshooting the Installation."
(b) Enter the show module command to display the interfaces for all switching module types.
If the new Flashcode version is displayed, your installation is complete.
If a different (older) version is displayed, the old Flashcode is still loading from Flash memory. If the older version is displayed after a second installation attempt, see Chapter 6, "Troubleshooting the Installation."
|
|