|
|
This chapter describes how to configure the switch router's route processor so it can be accessed by other devices. Unless otherwise noted, the information in this chapter applies to the Catalyst 8540 CSR, Catalyst 8510 CSR, and Catalyst 8540 MSR with Layer 3 functionality. For further information about the commands used in this chapter, refer to the command reference publications in the Cisco IOS documentation set and to "Command Reference."
This chapter includes the following sections:
 |
Note You are at Step 2 in the suggested process for configuring your switch router (see "Suggested Procedure for Configuring Your Switch Router" section). You should have already set up the hardware and now be ready to proceed with configuring the route processor. |
Before starting up the switch router, you should verify the following:
Step 2 The cables are connected to the router.
Step 3 A console terminal is connected to the router.
When you start up the router, the CLI prompts you whether to enter the initial configuration dialog. Answer no to this prompt:
Would you like to enter the initial dialog? [yes]: no
You see the following user EXEC prompt:
Router>
You can now begin configuring the route processor.
You can configure the switch router from a direct console connection to the console port or remotely through its management port.
For further details on configuring ports and lines for management access, refer to the Cisco IOS Configuration Fundamentals Configuration Guide.
You can connect a modem to the console port on the Catalyst 8540 or to the auxiliary port on the Catalyst 8510 CSR. The following settings on the modem are required:
You can configure your modem by setting the DIP switches on the modem or by connecting the modem to terminal equipment. Refer to the user manual provided with your modem for the correct configuration information.
|
Note Because there are no hardware flow control signals available on the console port, the console port terminal characteristics should match the modem settings. |
For further details on configuring ports and modems for management access, refer to the Cisco IOS Configuration Fundamentals Configuration Guide and Cisco IOS Dial Services Configuration Guide .
The enable password is a nonencrypted password. It can contain any number of uppercase and lowercase alphanumeric characters. Give the enable password only to users permitted to make configuration changes to the switch router.
The enable secret password is a secure, encrypted password. By setting an encrypted password, you can prevent unauthorized configuration changes. On systems running Cisco IOS, you must type in the enable secret password before you can access global configuration mode.You must type in the enable secret password to access boot ROM software.
An enable secret password can contain from 1 to 25 uppercase and lowercase alphanumeric characters. The first character cannot be a number. Spaces are valid password characters. Leading spaces are ignored; trailing spaces are recognized.
You will configure passwords in the next section, "Configuring the Management Port (Ethernet0)."
You can remotely configure the switch router through the Ethernet interface on the management port, but first you must configure an IP address on the management port so that the route processor is reachable. There are two ways to configure the management port interface: manually from the command-line interface (CLI) or copying the configuration from the BOOTP server into NVRAM.
|
Note The Ethernet port interface on the route processor does not route or bridge traffic to other Ethernet ports on the switch router. This Ethernet port is a management port only and should not be configured as a routing port. |
|
Note Before you begin to manually configure the management port interface, obtain its IP address and IP subnet mask. Also make sure the console cable is connected to the console port. |
To configure the management port from the CLI, perform these steps:
| Command | Purpose | |
|---|---|---|
Step 1 | Router> enable Router# | Enters privileged EXEC mode. |
Step 2 | Router# | Verifies the installed hardware part numbers and serial numbers. |
Step 3 | Router# Router(config)# | Enters global configuration mode. |
Step 4 | Router(config)# enable-password | Sets the enable password. See the "About Passwords" section. |
Step 5 | Router(config)# enable secret | Specifies an enable secret password. Once set, the enable secret password must be entered to gain access to global configuration mode. |
Step 6 | Router(config)# Router(config-if)# | Enters interface configuration mode on interface ethernet0, the route processor management port. |
Step 7 | Router(config-if)# | Specifies the IP address and IP subnet mask for the management port interface. |
Step 8 | Router(config-if)# Router(config)# | Returns to global configuration mode. |
Step 9 | Router(config)# Router(config-line)# | |
Step 10 | Router(config-line)# password password | Specifies a password for Telnet sessions. |
Step 11 | Router(config-line)# end Router# | Returns to privileged EXEC mode. |
Step 12 | Router# | Saves your configuration changes to NVRAM. |
The switch router should now be operating correctly and transferring data.
Displaying the Operating Configuration
You can display the configuration file when you are in privileged EXEC (enable) mode.
Router# more system:running-config
Router# more nvram:startup-config
If you made changes to the configuration, but did not yet write the changes to NVRAM, the contents of the running-config file will differ from the contents of the startup-config file.
| Command | Purpose | |
|---|---|---|
Step 1 | Router# Router(config)# | Enters global configuration mode. |
Step 2 | Router(config)# | Specifies a system name, in this case "8540CSR." |
Step 3 | 8540CSR(config)# 8540CSR# | Returns to privileged EXEC mode. The prompt indicates that the hostname has been set to "8540CSR." |
Step 4 | 8540CSR# | Saves your configuration changes to NVRAM. |
Network Time Protocol (NTP) is a utility for synchronizing system clocks over the network, providing a precise time base for networked workstations and servers. In the NTP model, a hierarchy of primary and secondary servers pass timekeeping information by way of the Internet to cross-check clocks and correct errors arising from equipment or propagation failures.
An NTP server must be accessible by the client switch. NTP runs over User Datagram Protocol (UDP), which in turn runs over IP. NTP is documented in RFC 1305. All NTP communication uses Coordinated Universal Time (UTC), which is the same as Greenwich Mean Time. An NTP network usually gets its time from an authoritative time source, such as a radio clock or an atomic clock attached to a time server. NTP distributes this time across the network. NTP is extremely efficient; no more than one packet per minute is necessary to synchronize two machines to within a millisecond of one another.
NTP uses a stratum to describe how many NTP hops away a machine is from an authoritative time source. A stratum 1 time server has a radio or atomic clock directly attached, a stratum 2 time server receives its time from a stratum 1 time server, and so on. A machine running NTP automatically chooses as its time source the machine with the lowest stratum number that it is configured to communicate with through NTP. This strategy effectively builds a self-organizing tree of NTP speakers.
NTP has two ways to avoid synchronizing to a machine whose time might be ambiguous:
The communications between machines running NTP, known as associations, are usually statically configured; each machine is given the IP address of all machines with which it should form associations. Accurate timekeeping is possible by exchanging NTP messages between each pair of machines with an association. However, in a LAN environment, you can configure NTP to use IP broadcast messages. With this alternative, you can configure the machine to send or receive broadcast messages, but the accuracy of timekeeping is marginally reduced because the information flow is one-way only.
The Cisco implementation of NTP does not support stratum 1 service; it is not possible to connect to a radio or atomic clock. We recommend that you obtain the time service for your network from the public NTP servers available in the IP Internet. If the network is isolated from the Internet, the Cisco NTP implementation allows a machine to be configured so that it acts as though it is synchronized using NTP, when in fact it has determined the time using other means. Other machines then synchronize to that machine using NTP.
A number of manufacturers include NTP software for their host systems, and a version for systems running UNIX and its various derivatives is also publicly available. This software allows host systems to be time-synchronized as well.
NTP services are enabled on all interfaces by default. You can configure your switch router in either of the following NTP associations:
From global configuration mode, use the following procedure to configure NTP in a server association that transmits broadcast packets and periodically updates the calendar:
| Command | Purpose | |
|---|---|---|
Step 1 | Router(config)# | Updates hardware calendar with NTP time. |
Step 2 | Router(config)# ntp server ip-address | Forms a server association with another system. You can specify multiple associations. |
Step 3 | Router(config)# end Router# | Returns to privileged EXEC mode. |
Step 4 | Router# | Saves your configuration changes to NVRAM. |
For information on other optional NTP configurations, see the Cisco IOS Configuration Fundamentals Configuration Guide. For a complete configuration example that includes NTP, see the section "Catalyst 8540 CSR with ISL, VLAN, and BVI with GEC" section.
To view the current NTP configuration and status, use the show ntp status or the show ntp associations commands.
At the time of a switchover from the primary route processor, the secondary route processor takes over as primary and loads the configuration as follows:
The former primary route processor then becomes the secondary route processor.
|
Note If the secondary route processor is unavailable, the system reports a major alarm. Use the show facility-alarm command to display the redundancy alarm status. |
When the Catalyst 8540 CSR is powered on, the two route processors go through an arbitration to determine which is the primary route processor and which is the secondary. The following rules apply during arbitration:
During normal operation, the primary route processor is booted completely. The secondary CPU is partially up, meaning it stops short of parsing the configuration. From this point, the primary and secondary processors communicate periodically to synchronize any system configuration changes.
When a switchover occurs, address states are lost, and then restored after they are dynamically redetermined.
For redundant operation, the following requirements must be met:
If these requirements are met, the Catalyst 8540 CSR runs in redundant mode by default. The tasks described in the following sections are optional and used only to change nondefault values.
For a configuration example that includes route processor redundancy, see the section "Catalyst 8540 CSR with ISL, VLAN, and BVI with GEC" section.
Command | Purpose |
|---|---|
|
As long as you have not changed the default configuration register setting from autoboot, the secondary route processor (formerly the primary) completes the boot process from standby mode.
| Command | Purpose | |
|---|---|---|
Step 1 | Router(config)# config-register 0x2102 | Sets the configuration register for autoboot.1 |
Step 2 | Router(config)# boot system filename or Router(config)# boot system flash [flash-fs:][partition-number:][filename] or Router(config)# boot system rom or Router(config)# boot system {mop | rcp | tftp} filename [ip-address] | Sets the BOOT environment variable. This variable specifies the location and name of the system image file to use when automatically booting the switch router. |
Step 3 | Router(config)# end Router# | Returns to privileged EXEC mode. |
Step 4 | Saves the configuration to NVRAM. The new configuration register value takes effect after the next system reload. |
| 1This is the default configuration register setting. For details on using the configuration register to set boot parameters, refer to the Cisco IOS Configuration Fundamentals Configuration Guide . |
|
Note If the secondary route processor remains in ROM monitor mode, you can manually boot the processor either from bootflash or a PC Card. |
To display the configuration register value, use the following privileged EXEC command:
Command | Purpose |
|---|---|
|
To immediately synchronize the configurations used by the two route processors, use the following privileged EXEC command on the primary route processor:
Command | Purpose |
|---|---|
|
|
To manually synchronize the configurations used by the two route processors during a switchover, perform the following steps on the primary route processor, beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step 1 |
Router(config-r)# | Enters redundancy configuration mode. |
Step 2 |
Router(config-r-mc)# | Enters main-cpu configuration submode. |
Step 3 | Synchronizes either or both configurations during switchover or writing the files to NVRAM. |
|
Note Alternatively, you can force an immediate synchronization by entering the redundancy manual-sync command in privileged EXEC mode. |
Example
In the following example, both the startup and running configurations are synchronized:
Router(config)# redundancy Router(config-r)# main-cpu Router(config-r-mc)# sync config both Router(config-r-mc)# end Router# copy system:running-config nvram:startup-config
|
Note The last step in the example above ensures that the running configuration is saved during switchover in the event that the sync config command fails or the startup configuration in NVRAM is older than the running configuration. |
To display the route processor redundancy configuration, use the following privileged EXEC command:
Command | Purpose |
|---|---|
|
Example
In the following example, the route processor redundancy configuration displays:
Router# show redundancy Primary ------- Slot: 4 Uptime: 50 minutes Image: Version XX.X(19980716:020138) 107] Last Running Config. Sync: 50 minutes Last Startup Config. Sync: 50 minutes Last Restart Reason: Normal boot Secondary --------- Slot: 8 Uptime: 50 minutes Image: Version XX.X(19980716:020138)
 |
Caution If you fail to prepare the secondary route processor for removal, the traffic through the switch router could be interrupted. |
To change the secondary route processor to ROM monitor mode and eliminate the automatic reboot, use the following command from privileged EXEC mode:
Command | Purpose |
|---|---|
|
When three switch processors are installed, two are active at any time, while the third runs in standby mode. By default, switch processors 5 and 7 are active and switch processor 6 is the standby. The following situations can cause the standby switch processor to become active:
When a switchover to the standby switch processor occurs, the system resets and all connections are lost. When the system comes up again, all routes are reestablished automatically.
Command | Purpose |
|---|---|
|
|
Example
In the following example, the preferred switch processors are configured to be in slots 5 and 7; the switch processor in slot 6 runs in standby mode:
Router# redundancy preferred-switch-card-slots 5 7 The preferred switch cards selected are already active
|
Note The preferred switch card slot configuration reverts to the default configuration when the switch router is power cycled. |
To display the preferred switch processor redundancy configuration, use the following privileged EXEC command:
Command | Purpose |
|---|---|
|
Example
The following example shows the preferred switch processor redundancy configuration:
Router# show preferred-switch-card-slots The currently preferred switch card slots are slot: 5 and slot: 7 The currently active switch card slots are slot: 5 and slot: 7
To display the switch processor EHSA configuration, use the following privileged EXEC command:
Command | Purpose |
|---|---|
|
Example
The following example shows the primary switch processor EHSA configuration:
Router# show capability primary DRAM Size is :256 MB Pmem Size is :4 MB Nvram Size is :512 KB BootFlash Size is :8 MB ACPM hw version 5.6 ACPM functional version 4.4 Netclk Module present flag :0 NCLK hw version 0.0 NCLK func version 0.0 Printing the parameters for Switch card:0 SWC0 HW version 8.2 SWC0 Functional version 1.4 SWC0 Table memory size:0 MB SWC0 Feat Card Present Flag:1 SWC0 Feat Card HW version 4.0 SWC0 Feat Card Functional version 4.17 Printing the parameters for Switch card:1 SWC1 HW version 8.3 SWC1 Functional version 1.4 SWC1 Table memory size:0 MB SWC1 Feat Card Present Flag:1 SWC1 Feat Card HW version 4.0 SWC1 Feat Card Functional version 4.3 Printing the parameters for Switch card:2 SWC2 HW version 8.2 SWC2 Functional version 1.4 SWC2 Table memory size:0 MB SWC2 Feat Card Present Flag:1 SWC2 Feat Card HW version 4.0 SWC2 Feat Card Functional version 4.17Number of Controller supported in IOS:11 Driver 0 type:2560 super cam Functional Version 1.3 Driver 1 type:2562 OC12 SPAM Functional Version 5.1 Driver 2 type:2564 OC mother board Functional Version 5.1 Driver 3 type:2568 OC mother board Functional Version 5.1 Driver 4 type:258 Switch Card Functional Version 1.0 Driver 5 type:259 Switch Feature Card Functional Version 4.0 Driver 6 type:256 Route Processor Card Functional Version 4.0 Driver 7 type:257 Network Clock Module Functional Version 8.0 Driver 8 type:2570 8 port GigabitEthernet PAM Functional Version 1.72 Driver 9 type:2566 2 port GigabitEthernet PAM Functional Version 2.3 Driver 10 type:2565 16 port 10/100 FastEthernet PAM Functional Version 3.1
This section describes how to use PC Cards to copy system images and make standard configurations. PC Cards are a type of Flash memory that provide expanded file storage for your switch router. PC Cards, unlike the onboard Flash memory SIMM (bootflash), are not required for the operation of the switch router.
|
Note A PC Card must be ordered as a spare part. We recommend that you use a 20-MB PC Card to download and store a copy of the switch router software image. This allows you to store two or more images at the same time. |
PC Cards store a copy of the software image. The following sections describe how to format, delete, configure, and copy files between the onboard Flash memory Single In-Line Memory Module (SIMM), network servers, and PC Cards.
A PC Card is blank and must be formatted before use. The formatting procedure erases all information on the PC Card.
Here is the general procedure for formatting a PC Card:
Step 2 Insert the PC Card you want to format into slot 0 or slot 1.
Step 3 Format the PC Card using the format command.
Example
The following example demonstrates formatting a PC Card in slot 0 and naming it "NewPCcard":
Router# format slot0: Format operation may take a while. Continue? [confirm] y Enter volume ID (up to 30 characters): NewPCcard Formatting sector 1 Format device slot0 completed
In this example, a 16-MB PC Card was used. At the line Formatting sector 1, the system counts the card's sectors backward from 128 to 1 as it formats them. For 20-MB PC Cards, the system counts backward from 160 to 1.
|
Note For more information on inserting a PC Card, refer to the Catalyst 8540 CSR Route Processor and Interface Module Installation Guide or the Catalyst 8510 CSR Route Processor and Interface Module Installation Guide. |
To copy the startup configuration file from NVRAM to a PC Card once the PC Card is formatted and ready to use, use the following command:
Command | Purpose |
|---|---|
|
|
Example
The following example demonstrates copying the startup configuration file to the PC Card in slot 0; the default filename is used:
Router#copy nvram:startup-config slot0:Destination filename [start]?y386 bytes copied in 0.268 secsRouter#
On platforms with multiple Flash memory file systems, you can copy files from one Flash memory file system, such as internal Flash memory or a PC Card, to another Flash memory file system. Copying files to different Flash memory file systems lets you create backup copies of working configurations, duplicate configurations for other devices, and copies of system images.
The following example describes how to copy a new image from a PC Card in slot 1 to a PC Card in slot 0 that contains an old image. This system also has a default boot image on the onboard Flash memory. Before you start, insert PC Cards in both slot 0 and slot 1.
 |
Tips Make sure that the new image fits on the PC Card in slot 0 along with the old image. |
Router# copy slot1:image.new slot0:image.new
To determine which file system device you are accessing, use the pwd (print working directory) command, as shown in the following example:
Router# pwd bootflash
To move between Flash memory media, use the cd command, as shown in the following example:
Router# cd slot0: Router# pwd slot0
To list the directory contents of any Flash memory media, use the dir command, as shown in the following example:
Router# dir Directory of slot0:/ 1 -rw- 3509000 Jan 25 1999 19:46:25 router-in-mz.120-1.W5.6a.bin 3 -rw- 3509004 Feb 5 1999 19:46:25 router-in-mz.120-1a.W5.6b.bin 4 -rw- 2386 Feb 19 1999 17:25:36 startup-config 16384000 bytes total (9360836 bytes free)
When you delete a file from Flash memory, the system marks the file as deleted, allowing you to later recover a deleted file using the undelete command. Erased files cannot be recovered. To permanently erase the configuration file, use the squeeze command.
|
Caution When deleting files from memory, be careful not to delete all the system images. If you delete all existing system images, you can no longer download new images. |
For an example of using the delete and squeeze commands, see the "Copying the System Image to the Switch Router" section.
The switch router can be booted, automatically or manually, from a variety of sources, including a network server or Flash memory device. This section describes how to configure the switch router to boot automatically from an image on a PC Card. For an example of configuring the switch router to boot manually from a PC Card, see the "Updating the System Image" section.
To enable booting from a PC Card, perform the following steps:
| Command | Purpose | |
|---|---|---|
Step 1 | Router# configure terminal Router(config)# | Enters global configuration mode. |
Step 2 | Router(config)# no boot system | Disables booting from bootflash. |
Step 3 | Router(config)# boot system flash [flash-fs:][partition-number:][filename] | Enables booting from the specified system image on the specified Flash file system. |
Step 4 | Router(config)# config-reg 0x2102 | |
Step 5 | Router(config)# end Router# | Exits global configuration mode. |
Step 6 | Router# copy system:running-config nvram:startup-config | Saves the configuration to NVRAM. |
Step 7 | Router# reload | Reboots the system. |
| 1This is the default configuration register setting. For details on using the configuration register to set boot parameters, refer to the Cisco IOS Configuration Fundamentals Configuration Guide . |
When you enter boot commands, be careful not to insert extra spaces because they influence the way the switch router interprets the command. For example, notice the difference in the following commands:
The following command correctly instructs the switch router to boot the image1 file.
Router(config)# boot system flash slot0:image1
The following command incorrectly contains a space between "slot0:" and "image2." The switch router finds the filename field blank and so boots the first file on the PC Card.
Router(config)# boot system flash slot0: image2
Before you copy software between the network server and Flash memory in the router, do the following:
To create a backup of the system software on a TFTP server, perform the following steps:
| Command | Purpose | |
|---|---|---|
Step 1 | Router# show flash-fs: |
Note the name of the image file you want to copy. |
Step 2 | Router# copy flash-fs: tftp: |
Example
The following example demonstrates copying a specified system image file from the current flash device to the default TFTP server:
Router#copy slot0: tftp:Address or name of remote host [172.68.16.129]?y Source filename []? cat8540c-in-mz.120-1a.W5.6b.binDestination filename [cat8540c-in-mz.120-1a.W5.6b.bin]?y
You can copy system image files from a TFTP server to a PC Card for use in booting the switch router or for backup purposes when you boot from internal Flash memory. If the system image on internal Flash memory becomes corrupted, you can replace the system software by copying the backup image from the PC Card to the onboard Flash memory.
|
Note Be sure that you have a properly formatted PC Card in the appropriate slot before beginning this procedure. |
Example
The following example demonstrates copying a system image file from the default TFTP server to the PC Card in slot 0:
Router#copy tftp: slot0:Address or name of remote host [172.68.16.129]?y Source filename []? cat8540c-in-mz.120-1a.W5.6b.binDestination filename [cat8540c-in-mz.120-1a.W5.6b.bin]?y5746016 bytes available on device slot0, proceed? [confirm]y
This section provides minimal instructions for updating the system image on your switch router. This procedure assumes that you are manually booting the switch router from a system image on a PC Card. You can also configure the switch router to boot automatically from a system image specified in the BOOT environment variable. For additional information on booting options and maintaining system images, refer to the Cisco IOS Configuration Fundamentals Configuration Guide.
The following steps give the general procedure for updating the system software:
Step 2 Copy the system image to the switch router.
Step 3 Reload the switch router with the new image.
Cisco IOS system images, along with other software, are available from the Software Center on Cisco Connection Online (CCO) at http://www.cisco.com. You can download system images from CCO using your browser's FTP capability, using conventional FTP, or using CCO's asynchronous dial-up interface.
For instructions on accessing and downloading software from CCO, refer to the document "Software Downloading from CCO via World Wide Web" at the Software Center on CCO.
You copy the system image to the switch router using TFTP, FTP, or RCP. If the system you used to download the image from CCO does not function as a TFTP, FTP, or RCP server, you must first copy the file to an intermediate server that provides those services to your switch router.
|
Note Before copying the system image from the server to the switch router, check the size of the file to make sure you will have enough room for it on the Flash memory device. On UNIX file systems, use the ls -la command from the directory where the file is stored to display the file size. |
To copy the system image from a TFTP server to the PC card, initiate a Telnet session or console connection to the switch and perform the following steps in privileged EXEC mode:
| Command | Purpose | |
|---|---|---|
Step 1 | Router# dir filesystem: | Displays the contents and available space on the Flash device. If there is not enough free space to copy the new system image, perform Steps 2 and 3. Otherwise, proceed to Step 4. |
Step 2 | Router# delete filesystem:filename | Deletes files as needed to free space for the new system image. If you have older system images stored on the file system, it is recommended that you delete the oldest one and leave a newer one in case you need to revert. |
Step 3 | Router# squeeze filesystem: | Permanently deletes files so that the space can be reused. |
Step 4 | Router# copy tftp: filesystem: | Initiates a TFTP session to copy the system image from the TFTP server. The system prompts you for a TFTP server name and filename. |
Step 5 | Router# dir filesystem: | Displays the contents of the file system. This step confirms that the file was copied as expected. |
Example
The following example shows deleting a file from the PC Card in slot 0 on the switch router and copying a new system image to it using TFTP:
Router# dir slot0: Directory of slot0:/ 1 -rw- 7158424 Nov 30 1999 15:46:33 cat8540c-in-mz.120-6.5.W5.15.0.8 2 -rw- 7197444 Jan 02 2000 00:35:33 cat8540c-in-mz.120-6.5.W5.16.0.3 20578304 bytes total (6222180 bytes free) Router# delete slot0:cat8540c-in-mz.120-6.5.W5.15.0.8 Delete filename [cat8540c-in-mz.120-6.5.W5.15.0.8]? Delete slot0:cat8540c-in-mz.120-6.5.W5.15.0.8? [confirm] Router# squeeze slot0: All deleted files will be removed, proceed? [confirm] Squeeze operation may take a while, proceed? [confirm] Erasomg squeeze log . . . . . . . . . . . . . . . Router# copy tftp: slot0: Address or name of remote host [] ? mocha Source filename [] ? joe/cat8540c-in-mz.120-6.5.W5.16.0.8 Destination filename [cat8540c-in-mz.120-6.5.W5.16.0.8] ? Router# dir slot: Directory of slot0:/ 1 -rw- 7197444 Jan 02 2000 00:35:33 cat8540c-in-mz.120-6.5.W5.16.0.3 2 -rw- 7110320 Jan 07 2000 15:25:40 cat8540c-in-mz.120-6.5.W5.16.0.8 20530200 bytes total (6270284 bytes free)
|
Note Be sure that the file size is the same after it was copied as it is on the server. |
When the configuration register is set for manual booting, issuing the reload command causes the system to enter ROM monitor mode, where you enter the boot command and the name of the system image to use. To perform this procedure, you must be connected to the console port, which provides access to the switch router when in ROM monitor mode. For automatic booting you can issue the reload command from an Ethernet connection to the route processor.
|
Note This procedure assumes that you need to change the boot field in the configuration register from its default value so that the system reverts to ROM monitor mode when the reload command is issued. |
To reload the switch router with the new system image on the PC Card, perform the following steps, beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step 1 | Router(config)# config-register 0x0 | Sets the configuration register for manual booting from ROM monitor mode.1 |
Step 2 | Router(config)# end Router# | Returns to privileged EXEC mode. |
Step 3 | Router# | Saves your configuration changes to NVRAM. |
Step 4 | Router# reload | Initiates a reload of the system software. The system prompts you to save the modified configuration before you can proceed. You then enter ROM monitor mode. |
Step 5 | rommon 1> dir filesystem: | Displays the contents of the file system. Perform this optional step to display and copy the name of the system image to the clipboard for use in the next step. |
Step 6 | rommon 1> boot filesystem:filename | Reboots the switch router with the new system image. You can paste the filename from the clipboard if you copied it in the previous step. |
Step 7 | Router> show version | Displays the system software version information. Use this step to confirm that the system is loaded with the expected software version. |
| 1For details on using the configuration register to set boot parameters, refer to the Cisco IOS Configuration Fundamentals Configuration Guide. |
Example
The following example shows setting the configuration register, saving the configuration, and reloading the switch router with the new system image on the PC Card in slot 0:
Router(config)# config-register 0x0
Router(config)# end
Router# copy system:running-config nvram:startup-config
Destination filename [startup-config]?
Building configuration...
[OK]
Router# reload
System configuration has been modified. Save? [yes/no]: yes
Warning: Attempting to overwrite an NVRAM configuration previously written
by a different version of the system image.
Overwrite the previous NVRAM configuration?[confirm]
Building configuration...
[OK]
Proceed with reload? [confirm]
rommon 1> dir slot:
Directory of slot0:/
1 -rw- 7197444 Jan 02 2000 00:35:33 cat8540c-in-mz.120-6.5.W5.16.0.3
2 -rw- 7110320 Jan 07 2000 15:25:40 cat8540c-in-mz.120-6.5.W5.16.0.8
20530200 bytes total (6270284 bytes free)
rommon 2> boot cat8540c-in-mz.120-6.5.W5.15.0.8
<The system boots.>
Router> show version
Cisco Internetwork Operating System Software
IOS (tm) L3 Switch/Router Software (C8540CSR-IN-M), Version 12.0(6.5)W5(16.0.8)
Copyright (c) 1986-2000 by cisco Systems, Inc.
Compiled Fri 07-Jan-2000 15:25 by
Image text-base: 0x60010930, data-base: 0x60882000
When updating the system image on a switch router with dual route processors, you must perform the above procedure for both route processors. The following steps demonstrate the sequence of events that occurs when updating the system image on systems with dual route processors (these steps assume that the route processor in slot 4 is functioning as the primary when you begin):
Step 2 Connect to the console port of the route processor in slot 4 and issue the reload command; a switchover occurs, and the route processor in slot 8 becomes the primary. Then reboot with the new system image; the route processor in slot 4 becomes the secondary.
Step 3 Connect to the console port of the route processor in slot 8 and issue the reload command; a switchover occurs, and the route processor in slot 4 becomes the primary again.Then reboot with the new system image; the route processor in slot 8 becomes the secondary.
Step 4 Use the show redundancy command on the primary to verify that the route processors are loaded and running as expected.
Now that you have configured the route processor, see "Configuring Interfaces," for instructions on interface configurations for your switch router.
Posted: Tue Sep 26 13:26:13 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.