Table of Contents

Configuring the Route Processor

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:

• Starting Up the Switch Router
  
  
• Using the Console Port or Management Port
  
  
• About Passwords
  
  
• Configuring the Management Port (Ethernet0)
  
  
• Configuring the Host Name
  
  
• About Network Time Protocol
  
  
• Configuring Redundancy and Enhanced High System Availability (Catalyst 8540)
  
  
• Using PC Cards
  
  
• Updating the System Image
  
  

---

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.

---

Starting Up the Switch Router

Before starting up the switch router, you should verify the following:

Step 1   The switch router is set for the correct AC (or DC) power voltages.

Refer to the following for correct power voltages:

• Quick Reference Catalyst 8540 CSR and MSR Hardware Information
  
  
• Quick Reference Catalyst 8510 and LightStream 1010 Hardware Information
  
  

Step 2   The cables are connected to the router.

Step 3   A console terminal is connected to the router.

For instructions, refer to the following:

• Catalyst 8540 CSR Route Processor and Interface Module Installation Guide
  
  
• Catalyst 8510 CSR Route Processor and Interface Module Installation Guide
  
  

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.

Using the Console Port or Management Port

You can configure the switch router from a direct console connection to the console port or remotely through its management port.

• If you are using a direct console connection, configure your terminal emulation program for 9600 baud, 8 data bits, no parity, and 1 stop bit.
  
  
• If you are using the management port interface, you must assign an IP address to the interface (Ethernet0).
  
  

For interface configuration instructions, see the "Configuring the Management Port (Ethernet0)" section.

For further details on configuring ports and lines for management access, refer to the Cisco IOS Configuration Fundamentals Configuration Guide.

Modem Support

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:

• Enable auto answer mode
  
  
• Suppress result codes
  
  

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 Solutions Configuration Guide .

About Passwords

You can configure both an enable password and an enable secret password. For maximum security, the enable password should be different from the enable secret password.

Enable Password

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.

Enable Secret Password

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)."

Configuring the Management Port (Ethernet0)

The Ethernet port on the route processor, named ethernet0, is a management port that allows multiple simultaneous Telnet or SNMP network management sessions.

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:

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.

• To see the current operating configuration, enter the following command at the enable prompt:
  
  

Router# more system:running-config

 

• To see the configuration in NVRAM, enter the following command:
  
  

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.

Configuring the Host Name

In addition to passwords and IP address, your initial configuration should include the host name to make it easier to configure and troubleshoot the switch router. To configure the host name, perform these steps:

About Network Time Protocol

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:

• NTP never synchronizes to a machine that is not synchronized itself.
  
  
• NTP compares the time reported by several machines and does not synchronize to a machine whose time is significantly different from the others, even if its stratum is lower.
  
  

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.

Configuring NTP

NTP services are enabled on all interfaces by default. You can configure your switch router in either of the following NTP associations:

• Peer association—this system either synchronizes to the other system or allows the other system to synchronize to it.
  
  
• Server association—this system synchronizes to the other system, and not the other way around.
  
  

From global configuration mode, use the following procedure to configure NTP in a server association that transmits broadcast packets and periodically updates the calendar:

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.

Configuring Redundancy and Enhanced High System Availability (Catalyst 8540)

The Catalyst 8540 CSR supports redundant CPU operation with dual route processors. In addition, enhanced high system availability (EHSA) is provided in the switching fabric when three switch processors are installed in the chassis. This section describes how to configure redundancy for your CPU with dual route processors. It also describes how to configure EHSA for the switch fabric.

Route Processor Redundant Operation

The Catalyst 8540 CSR supports fault tolerance by allowing a secondary route processor to take over if the primary fails. This secondary, or redundant, route processor runs in standby mode. In standby mode, the secondary route processor is partially booted with the Cisco IOS software, however, no configuration is loaded.

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:

• If the running configurations between the primary and secondary route processors match, the new primary route processor uses the running configuration file.
  
  
• If the running configurations between the primary and secondary route processors do not match, the new primary route processor uses the last saved configuration file in its NVRAM (not the NVRAM of the former primary).
  
  

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:

• A newly inserted route processor card always comes up as the secondary, except in cases where the newly inserted card is the only one present.
  
  
• If the configuration is corrupted, one of the route processors comes up as primary, allowing you to correct the situation manually.
  
  
• The route processor that is the primary when the switch router is powered off becomes the primary route processor when it is powered on again.
  
  
• If none of the above conditions is true, the route processor in slot 4 becomes the primary route processor.
  
  

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.

Conditions that Cause a Switchover from the Primary Route Processor

The following conditions can cause a switchover from the primary route processor to the secondary route processor:

• The primary route processor is removed or swapped. When the route processor functioning as the primary is removed, the secondary takes over. The Catalyst 8540 CSR is now nonredundant until a second route processor is inserted.
  
  
• The primary route processor is rebooted. When a route processor functioning as the primary is rebooted, the secondary takes over.
  
  
• The primary route processor fails. The secondary route processor takes over as the primary, using the last saved configuration (or the current running configuration if they were synchronized with the sync config command).
  
  
• A switchover is manually forced with the redundancy force-failover main-cpu command.
  
  

When a switchover occurs, address states are lost, and then restored after they are dynamically redetermined.

Configuring Route Processor Redundancy

For redundant operation, the following requirements must be met:

• Two route processors and three switch cards are required.
  
  
• The route processors must have identical hardware configurations. This includes variables such as DRAM size, presence or absence of network clock modules, and so on.
  
  
• Both route processors must have the same functional image.
  
  
• Both route processors must be running the same system image.
  
  
• Both route processors must be set to autoboot (a default setting).
  
  

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.

Forcing a Switchover

You can manually force the secondary route processor to take over as the primary. To do so, use the following privileged EXEC command:

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.

If you have changed the default configuration register value from autoboot, you can change it back by performing the following steps:

Note   If the secondary route processor remains in ROM monitor mode, you can manually boot the processor either from bootflash or a PC Card.

Displaying the Configuration Register Value

To display the configuration register value, use the following privileged EXEC command:

Synchronizing the Configurations

During normal operation, the startup and running configurations are synchronized by default between the two route processors. In the event of a switchover, the new primary uses the current configuration. Configurations are synchronized either immediately from the command line or during route processor switchover.

Immediately Synchronizing Route Processor Configurations

To immediately synchronize the configurations used by the two route processors, use the following privileged EXEC command on the primary route processor:

Synchronizing the Configurations During Switchover

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:

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.

Displaying the Route Processor Redundancy Configuration

To display the route processor redundancy configuration, use the following privileged EXEC command:

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) 

Preparing a Route Processor for Removal

Before removing a route processor that is running Cisco IOS in secondary mode, change to ROM monitor mode. You could use the reload command to force the route processor to ROM monitor mode but the automatic reboot would occur and interrupt traffic.

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:

Configuring Switch Fabric EHSA Operation

Slots 5, 6, and 7 in the Catalyst 8540 CSR chassis can accommodate either two or three switch processor cards, with a switching capacity of 10 Gbps each. The possible configurations are as follows:

• Two route processors—20 Gbps non-EHSA switching fabric (no spare)
  
  
• Three route processors—20 Gbps EHSA switching fabric (one spare)
  
  

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:

• A switch processor card is removed or swapped.
  
  
• A switchover is forced manually with the redundancy preferred-switch-card-slots command.
  
  

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.

Configuring the Preferred Switch Processor

To configure which two switch processors will be active and which one will run in standby mode, use the following privileged EXEC command on the primary switch processor:

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.

Displaying the Preferred Switch Processor Redundancy Configuration

To display the preferred switch processor redundancy configuration, use the following privileged EXEC command:

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

Displaying the Switch Processor EHSA Configuration

To display the switch processor EHSA configuration, use the following privileged EXEC command:

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

Using PC Cards

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.

• Formatting a PC Card
  
  
• Copying the Startup Configuration File to the PC Card
  
  
• Copying Files from One PC Card to Another
  
  
• Viewing the Contents of Flash Memory
  
  
• Deleting Files from Flash Memory
  
  
• Booting from a PC Card
  
  
• Backing Up a System Image to a TFTP Server
  
  
• Copying a System Image from a TFTP Server to a PC Card
  
  

Formatting a PC Card

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 1   Back up any files that you have on an existing PC Card by copying them to a TFTP server using the copy command.

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.

Copying the Startup Configuration File to the PC Card

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:

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]? y

386 bytes copied in 0.268 secs

Router#

Copying Files from One PC Card to Another

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.

Tip Make sure that the new image fits on the PC Card in slot 0 along with the old image.

To copy the new image from the new PC Card in slot 1 to the PC Card in slot 0 that contains the old image, enter this command from privileged EXEC mode:

Router# copy slot1:image.new slot0:image.new

Viewing the Contents of Flash Memory

This section describes commands you can use with the onboard Flash memory SIMM (bootflash) and PC Cards.

Determining the Current File System Device

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

Moving Between Flash Memory Media

To move between Flash memory media, use the cd command, as shown in the following example:

Router# cd slot0:

Router# pwd

slot0

Listing the Flash Memory Directory Contents

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)

Deleting Files from Flash Memory

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.

The squeeze command permanently removes files marked for deletion, and pushes all the other undeleted files together to eliminate spaces between them. To prevent data loss due to sudden power loss, the "squeezed" data is temporarily saved to another location in Flash memory. The squeeze command keeps a log of the functions performed so that if a power failure occurs, the system continues the process when the power resumes.

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.

Booting from a PC Card

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:

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

Backing Up a System Image to a TFTP Server

To create a backup copy of your system image, or to verify that the copy in Flash memory is the same as the original file on disk, you can copy system images from Flash memory to a Trivial File Transfer Protocol (TFTP) server.

In some implementations of TFTP, you must create a dummy file on the TFTP server and give it read, write, and execute permissions before copying the file over it. Refer to your TFTP documentation for more information.

Before you copy software between the network server and Flash memory in the router, do the following:

• Make sure you have access to the network server, and obtain its IP address and name.
  
  
• Verify that the server has sufficient room to accommodate the Cisco IOS software image.
  
  
• Check the filename requirements and file space of the network server.
  
  
• Create a dummy file on the server with read-write-execute permission. This is the file you copy to.
  
  

To create a backup of the system software on a TFTP server, perform the following steps:

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.bin

Destination filename [cat8540c-in-mz.120-1a.W5.6b.bin]? y

Copying a System Image from a TFTP Server to a PC Card

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.bin

Destination filename [cat8540c-in-mz.120-1a.W5.6b.bin]? y

5746016 bytes available on device slot0, proceed? [confirm] y

Updating the System Image

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 1   Download the system image from CCO.

Step 2   Copy the system image to the switch router.

Step 3   Reload the switch router with the new image.

Downloading System Images from CCO

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.

Copying the System Image to the Switch Router

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:

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.

Reloading the Switch Router

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:

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

Updating Images on Dual Route Processors (Catalyst 8540)

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 1   Copy the system image from the TFTP server to the Flash memory device on both route processors. For example, if you are using a PC Card in slot 0 of both route processors, you would copy the image to slot0: and to sec-slot0:.

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.