|
|
This chapter describes how to configure the switch router's route processor so it can be accessed by other devices. The information in the following sections applies to both the Catalyst 8540 CSR route processor and the Catalyst 8510 CSR switch route processor, with the exception of CPU redundancy, which is available only in the Catalyst 8540 CSR. 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:
Before starting up the switch router, you should verify the following:
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.
For further details on configuring ports and modems for management access, refer to the Cisco IOS Configuration Fundamentals Configuration Guide and Dial Solutions 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. To configure the management port from the CLI, see Table 3-1.
| Step | Command | Purpose | ||
|---|---|---|---|---|
| Router> enable | Enter privileged EXEC mode. | ||
| Router# enable-password | Set the enable password. See the "About Passwords" section. | ||
| Router# | Verify the installed hardware part numbers and serial numbers. | ||
| Router# | Enter global configuration mode. | ||
| Router(config)# enable secret | Enter an enable secret password. Once set, the enable secret password must be entered to gain access to global configuration mode. | ||
| Router(config)# | Enter interface configuration mode on interface ethernet0, the route processor management port. | ||
| Router(config-if)# | Enter the IP address and IP subnet mask for the management port interface. | ||
| Router(config-if)# | Return to global configuration mode. | ||
| Router(config)# | |||
| Router(config-line)# password password | Enter a password for Telnet sessions. | ||
| Router(config-line)# Ctrl-Z | Return to privileged EXEC mode. | ||
| Router# | Save your configuration changes to NVRAM. |
The switch router should now be operating correctly and transferring data.
You can display the configuration file when you are in privileged EXEC (enable) mode.
Router# show running-configRouter# show startup-configIf you made changes to the configuration, but did not yet write the changes to NVRAM, the results of the show running-config will differ from the results of the show startup-config command.
In addition to the system passwords and enable password, your initial configuration should include the host name to make it easier to configure and troubleshoot the switch router. To configure the host name, follow the steps in Table 3-2.
| Step | Command | Purpose |
| 1 | Router# | Enter global configuration mode. |
| 2 | Router(config)# | Enter a system name. |
| 3 | Router(config)# | Return to privileged EXEC mode. The prompt indicates that the hostname has been set to "8540CSR." |
| 4 | Router# | Copy 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. For information on other optional NTP configurations, see the Cisco IOS Configuration Fundamentals Configuration Guide.
| Step | Command | Purpose | ||
| Router(config)# | Update hardware calendar with NTP time. | ||
| Router(config)# ntp server ip-address | Form a server association with another system. You can specify multiple associations. | ||
| Router(config)# end | Return to privileged EXEC mode. | ||
| Router# | Save your configuration changes to NVRAM. |
To view the current NTP configuration and status, use the show ntp status or the show ntp associations commands.
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.These features and their configuration are described in the following sections:
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:
The former primary route processor then becomes the secondary route processor.
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.
The following conditions can cause a switchover from the primary router processor to the secondary route processor.
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.
You can manually force the secondary route processor to take over as the primary. To do so, use the privileged EXEC command in Table 3-4.
| Command | Purpose |
|---|---|
Force a switchover. |
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 steps in Table 3-5.
| Step | Command | Purpose |
|---|---|---|
| 1 | Router(config)# config-register 0x2102 | Set the config register for autoboot. |
| 2 | Router(config)# end | Return to privileged EXEC mode. |
| 3 | Save the configuration to NVRAM. The new configuration register value takes effect after the next system reload. |
To display the configuration register value, use the privileged EXEC command in Table 3-6.
| Command | Purpose |
|---|---|
Display the configuration register value. |
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.
To immediately synchronize the configurations used by the two route processors, use the privileged EXEC command in Table 3-7 on the primary route processor.
| Command | Purpose |
|---|---|
Router# redundancy manual-sync {startup-config | running-config | both} | Immediately synchronize the configuration. |
To manually synchronize the configurations used by the two route processors during a switchover, perform the steps in Table 3-8 on the primary route processor, beginning in global configuration mode.
| Step | Command | Purpose |
|---|---|---|
| 1 | Entes redundancy configuration mode. | |
| 2 | Enter main-cpu configuration submode. | |
| 3 | Synchronize either or both configurations during switchover or writing the files to NVRAM. | |
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 running-config startup-config
To display the route processor redundancy configuration, use the privileged EXEC command in Table 3-9.
| Command | Purpose |
|---|---|
Display the redundancy configuration. |
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)
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 command described in Table 3-10 from privileged EXEC mode.
| Command | Purpose |
|---|---|
Change the secondary route processor to ROM monitor mode prior to removal. |
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:
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.
To configure which two switch processors will be active and which one will run in standby mode, use the privileged EXEC command in Table 3-11 on the primary switch processor.
| Command | Purpose |
|---|---|
Router# redundancy preferred-switch-card-slots {5 | 6 | 7} {5 | 6 | 7} | Configure the active and standby switch processors. |
In the following example, the preferred switch processors are configured to be in slots 5 and 7 with the slot 6 switch processor running in standby mode:
Router# redundancy preferred-switch-card-slots 5 7 The preferred switch cards selected are already active
To display the preferred switch processor redundancy configuration, use the privileged EXEC command in Table 3-12.
| Command | Purpose |
|---|---|
Display the redundancy configuration. |
The following example whos 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 privileged EXEC command in Table 3-13.
| Command | Purpose |
|---|---|
Display the switch redundancy configuration. |
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 Flash PC Cards to copy system images and make standard configurations. Flash PC Cards are not required for the operation of the switch router.
Flash 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 Flash PC Cards.
A Flash PC Card is blank and must be formatted before use. The formatting procedure erases all information on the Flash PC Card.
Following is the general procedure for formatting a Flash PC Card:
Step 1 If you have files on an existing Flash PC Card that you want to back up, copy them to a TFTP server using the copy flash tftp command.
Step 2 Insert the Flash PC Card you want to format into slot 0 or slot 1.
Step 3 Format the Flash PC Card using the format command.
The following example demonstrates formatting a Flash 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 Flash 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 Flash PC Cards, the system counts backward from 160 to 1.
To copy the startup configuration file from the Flash memory SIMM to a Flash PC Card once the Flash PC Card is formatted and ready to use, use the command shown in Table 3-14.
| Command | Purpose |
|---|---|
Router# copy startup-config flash-device | From privileged EXEC mode, copy the file startup-config to the Flash PC Card in the specified location. |
The following example demonstrates copying the startup configuration file to the Flash PC Card in slot 0; the default filename is used:
Destination filename [startup-config]?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 Flash PC Card, to another Flash memory file system. Copying files to different Flash memory file systems lets you create backup copies of working configurations and duplicate configurations for other devices.
The following example describes how to copy a new image from a Flash PC Card in slot 1 to a Flash 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 Flash PC Cards in both slot 0 and slot 1.
 | Tips Make sure that the new image fits on the Flash 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 print working directory (pwd) command, as shown in the following example:
Router# pwd bootflash
To move between Flash memory media, use the cd [bootflash: | slot0: | slot1:] command, as shown in the following example:
Router# cd slot0: Router# pwd slot0 Router#
To list the directory contents of any Flash memory media, use the dir [bootflash: | slot0: | slot1:] 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) Router#
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. |
The following is an example of the delete and squeeze commands used together. Note that the delete command requires you to specify the filename, while the squeeze command requires that you specify the Flash memory media (for example, slot0:).
Router# delete cat8540c-in-mz.120-1.W5.6a.bin Router# dir Directory of slot0:/ 4 -rw- 2386 May 11 1999 17:25:36 startup-config 16384000 bytes total (9360836 bytes free) Router#
The image file is marked for deletion. Use the squeeze command to complete the operation.
Router# squeeze slot0: All deleted files will be removed, proceed? [confirm] y Squeeze operation may take a while, proceed? [confirm] Y ebESESESESESESESES Router# dir 4 -rw- 2386 May 11 1999 17:25:36 startup-config 12869836 bytes available (1825540 bytes used)
Table 3-15 lists and describes the output that could be generated from a squeeze command.
| Output Letter | Description |
|---|---|
e | This special location was erased (which must be performed before any write operation). |
b | The data about to be written to this special location was temporarily copied. |
E | The sector temporarily occupied by the data was erased. |
S | The data was written to its permanent location in Flash memory. |
Z | This log was erased after the squeeze command was successfully completed. |
Future releases of Cisco IOS system images can be obtained from a network server, a floppy disk, or a Flash PC Card. This section describes how to configure the switch router so that it boots from an image on a Flash PC Card. To enable booting from a Flash PC Card, use the commands in Table 3-16.
.
| Step | Command | Purpose |
|---|---|---|
| 1 | Router# configure terminal | Enter global configuration mode. |
| 2 | Router(config)# no boot system | Disable booting from bootflash. |
| 3 | Router(config)# boot system flash flash-device: image-name | Enable booting from the image name file on the specified Flash memory device. |
| 4 | Router(config)# config-reg 0x2102 | |
| 5 | Router# copy running-config startup-config | Save the configuration to NVRAM. |
| 6 | Router# reload | Reboot the system. |
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 Flash PC Card.
Router(config)# boot system flash slot0: image2
 | Tips 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, use the steps in Table 3-17.
| Step | Command | Purpose | ||
|---|---|---|---|---|
| Router# cd flash-device | From privileged EXEC mode, change the Flash device to the slot that holds the Flash PC Card. | ||
| Router# show flash all | Display the contents of Flash memory, including the names of the images that currently reside there. Note the name of the image file you want to copy. | ||
| Router# copy flash tftp: |
The followi ng example demonstrates copying a specified system image file from the current flash device to the default TFTP server:
Router#copy flash tftp: Source filename []? cat8540c-in-mz.120-1a.W5.6b.binAddress or name of remote host [172.68.16.129]?yDestination filename [cat8540c-in-mz.120-1a.W5.6b.bin]?y
It is a good idea to have a copy of the current system image on a Flash PC Card in case the file in Flash memory becomes corrupted. You can then replace the system software by copying the backup image from the Flash PC Card to the onboard Flash memory. Use the commands in Table 3-18 to copy the system image from the TFTP server to a Flash PC Card.
| Step | Task/Command | Description | ||
|---|---|---|---|---|
| Router# cd flash-device | From privileged EXEC mode, change the Flash device to the slot that holds the Flash PC Card. | ||
| Router# pwd | Verify that you are in the right directory. | ||
| Router# copy tftp flash: | Copy a file from a TFTP server to Flash memory. |
The following examples demonstrates copying a system image file from the default TFTP server to the current Flash PC Card:
Router#copy tftp flash: Source filename []? cat8540c-in-mz.120-1a.W5.6b.binAddress or name of remote host [172.68.16.129]?yDestination filename [cat8540c-in-mz.120-1a.W5.6b.bin]?y5746016 bytes available on device slot0, proceed? [confirm]y
Now that you have configured the route processor, see "Interface Configurations," for instructions on interface configurations for your switch router.
Posted: Wed Dec 22 14:09:19 PST 1999
Copyright 1989-1999©Cisco Systems Inc.