|
|
This document describes the Route Switch Processor (RSP8), an optional system processor for the Cisco 7507, Cisco 7507-MX, Cisco 7513, Cisco 7513-MX and Cisco 7576 routers. The RSP8 significantly increases the performance for most protocols and services over the RSP2 and RSP4/RSP4+.
The RSP8 supports the high system availability (HSA) feature, which allows two RSP8s (or an RSP8 and an RSP16) to be used in a Cisco 7507, Cisco 7507-MX, Cisco 7513, or Cisco 7513-MX router. See the "Configuring High System Availability" section for more information on HSA.
The RSP8 also supports high availability (HA), a series of features that operates similarly to HSA, but which further minimizes system downtime. (HSA is the system default.) For more information on HA, see the "Enabling High Availability Features" section.
This document contains the following sections:
All of the documentation mentioned below is available online, on the Documentation CD-ROM, or as printed documents. For a complete list of documentation, refer to the Cisco 7500 Series Router Documentation flyer (part number DOC-7812955) that shipped with your RSP, or online at http://www.cisco.com/univercd/cc/td/doc/product/core/cis7505/12955fly.ht m.
Your router and the Cisco IOS software running on it contain extensive features and functionality, which are documented in the following resources:
For configuration information and support, refer to the Cisco IOS software configuration documentation set that corresponds to the software release installed on your Cisco hardware.
 |
Note You can access Cisco IOS software configuration and hardware installation and maintenance documentation on the World Wide Web at http://www.cisco.com. Translated documentation is available at the following URL: http://www.cisco.com/public/countries_languages.shtml . |
For hardware installation and maintenance information, refer to the Quick Start Guide for your router, or refer to the Cisco 7500 Installation and Configuration Guide online at http://www.cisco.com/univercd/cc/td/doc/product/core/cis7505/cicg7500/index.htm.
For Flash Disk information with the RSP8, refer to Using the Flash Disk available online at http://www.cisco.com/univercd/cc/td/doc/product/core/7200vx/72vxfru/5819fdsk.htm .
For Flash memory card information, refer to Flash Memory Card Installation Instructions available online at http://www.cisco.com/univercd/cc/td/doc/product/core/cis7505/frus/2083flmc.htm .
The topics discussed in this section are:
The RSP8 supports the VIP2, VIP4 and the VIP6-80 in the Cisco 7505, Cisco 7507, Cisco 7507-MX, Cisco 7513, Cisco 7513-MX, and Cisco 7576 routers. (See Figure 1 and Figure 2.) The RSP8 is available as an upgrade to an existing RSP4, RSP2, or RSP1. The RSP8 contains the central processing unit (CPU) and most of the memory components for the router. The Cisco IOS software images reside in Flash memory, located on the RSP8:
|
Note For the Cisco IOS releases that are supported on the RSP8, refer to the "System Software" section and to the Software Advisor at http://www.cisco.com/cgi-bin/Support/CompNav/Index.pl . |
Storing the IOS software images in Flash memory enables you to download and boot from upgraded Cisco IOS software images remotely or from software images resident in the RSP8 Flash memory, without having to remove and replace read-only memory (ROM) devices.
In addition to running the system software from DRAM, the RSP8 contains and executes the following management functions that control the system:
The high-speed switching section of the RSP8 communicates with and controls the interface processors on the high-speed CyBus. This switching section of the RSP8 decides the destination of a packet and switches it based on that decision.
|
Note The Standby/Active button manually transitions the RSP from active to standby status, and from standby to active status when the router is configured for HSA or HA. The Reset button reboots the system. |
The CPU used in the RSP8 is a 250-MHz R7000 with 256-KB Layer 2 cache.
Table 1 shows the memory components on the RSP8.
Table 1 RSP8 Memory Components
|
|
1 64 MB of DRAM is the default DRAM configuration for the RSP8. The RSP8 is preconfigured with either two 32-MB DIMM or one 64-MB DIMM. 2 Do not mix memory sizes. If installing 2 DIMMs, both DIMMs must be the same size. If your router includes redundant RSPs, the RSPs should have the same memory size. 3 SRAM is not user-configurable or field-upgradable. 4 A system configuration file is contained in NVRAM, which allows the Cisco IOS software to control several system variables. 5 A 20-MB Flash memory card is the default shipping configuration for the RSP8 products. 6 The Flash Disk is offered as an option under the RSP8. You can use a Flash Disk side-by-side with a Flash memory card. |
DRAM stores routing tables, protocols, and network accounting applications and runs the Cisco IOS software. The standard (default) RSP8 configuration is 64 MB (preconfigured with either two 32-MB DIMMs or one 64-MB DIMM) of DRAM, with up to 256 MB available through DIMM upgrades. DRAM is contained in up to two DIMM sockets: U12 (also called bank 0) and U15 (also called bank 1). When upgrading DRAM, you must use DIMMs from Cisco. (Also see the "Compatibility Requirements" section.)
 |
Caution To prevent memory problems, DRAM DIMMS must be 3.3-volt (V) devices. Do not attempt to install higher-voltage devices in the RSP8 DIMM sockets. |
SRAM provides packet buffering and CPU cache memory functions. The standard RSP8 configuration is 8 MB of SRAM for packet buffering and 2 MB of tertiary (L3) CPU cache memory.
|
Note SRAM is fixed and is not field-upgradable. |
The system configuration, software configuration register settings, and environmental monitoring logs are contained in the 2-MB NVRAM, which is backed up with built-in lithium batteries that retain the contents for a minimum of 5 years. When replacing an RSP8, be sure to back up your configuration to a remote server so you can retrieve it later.
|
Caution Before you replace an RSP8 in a system with one RSP8, back up the running configuration to a Trivial File Transfer Protocol (TFTP) file server or to Flash memory so you can retrieve it later. If the configuration is not saved, the entire configuration will be lost—inside the NVRAM on the removed RSP8—and you will have to reenter the entire configuration manually. For instructions on how to save the configuration file, see the "Saving and Retrieving a Configuration File" section. This procedure is not necessary if you are temporarily removing an RSP8; lithium batteries retain the configuration in memory until you replace the RSP8 in the system. |
Flash memory cards (formerly called PCMCIA cards) and Flash Disks allow you to remotely load and store multiple Cisco IOS software and microcode images. You can download a new image over the network or from a local server and then add the new image to Flash memory or replace the existing files. You can then boot routers either manually or automatically from any of the images stored in Flash memory. Flash memory also functions as a TFTP server to allow other servers to boot remotely from stored images or to copy them into their own Flash memory.
Flash memory cards are available in 16-, 20-, or 32-MB sizes. Flash memory cards can be used in the RSP8 second PC Card slot for additional space, or as a backup to the main Flash memory.
Flash Disks are an alternative to the Flash memory cards, with more storage capacity. Flash Disks are available in 48-MB, 64-MB or 128-MB sizes, and can be used in slot 0, slot 1, or slots 0 and 1. You can use the Flash Disk side-by-side with the Flash memory cards.
|
Caution In order for a Flash memory card or Flash Disk that was formatted on an RSP1, RSP2, RSP4, or RSP7000 to be compatible in an RSP8, the Flash memory card or Flash Disk must be formatted with a boot image or Cisco IOS software image that is compatible with the RSP8. |
For a list of compatible software releases for the Flash memory card and Flash Disk, refer to the Software Advisor at http://www.cisco.com/cgi-bin/Support/CompNav/Index.pl.
There are no user-configurable jumpers on the RSP8.
Table 2 describes the operation of the LEDs found on the RSP8:
|
| 1 The RSP8 controls these LEDs and turns them on in parallel to indicate that the system is operational. |
The RSP8 has two PC Card slots available. Either slot can support a Flash memory card or a Flash Disk. Type I and Type II PC Cards can be used in PC Card slot 0 and slot 1. Type III PC Cards can be used in slot 1. Not all Flash memory cards or Flash Disks that are commercially available are supported.
|
Note Other Flash memory card or Flash Disk limitations might apply. For additional information, refer to the "Related Documentation" section 2. |
Two asynchronous serial ports on the RSP8, labeled Console and Auxiliary, allow you to connect external terminal devices to monitor and manage the system. The console port is an Electronics Industries Association/Telecommunications Industry Association (EIA/TIA)-232 receptacle (female) that provides a data circuit-terminating equipment (DCE) interface for connecting a console terminal.
|
Note EIA/TIA-232 was known as recommended standard RS-232 before its acceptance as a standard by the Electronic Industries Association (EIA) and Telecommunications Industry Association (TIA). |
The auxiliary port is an EIA/TIA-232 plug (male) that provides a data terminal equipment (DTE) interface; the auxiliary port supports flow control and is often used to connect a modem, a channel service unit (CSU), or other optional equipment for Telnet management.
Table 3 lists the physical specifications for the RSP8:
|
The Cisco 7507, Cisco 7507-MX, Cisco 7513, and Cisco 7513-MX routers support downloadable system software and microcode for most Cisco IOS and microcode upgrades. This enables you to remotely download, store, and boot from a new image. The publication Upgrading Software and Microcode in Cisco 7000 Series and Cisco 7500 Series Routers (DOC-781144=) provides instructions for upgrading over the network or from floppy disks. Flash memory contains the default system software image and bundled microcode images. Flash memory cards and Flash Disks are supported.
For the latest software release information, refer to the Software Advisor at http://www.cisco.com/cgi-bin/Support/CompNav/Index.pl .
At system startup, an internal system utility scans for compatibility problems between the installed interface processor types and the bundled microcode images. The utility then decompresses the images into running dynamic random-access memory (DRAM). The bundled microcode images then function the same as the EPROM images.
The Cisco IOS software images reside in Flash memory, which is located on the RSP8 in the form of a single in-line memory module (SIMM), on Flash memory cards, or on Flash Disks that insert in the two PC Card slots (slot 0 and slot 1) on the front of the RSP8. (See Figure 2.) Storing the Cisco IOS images in Flash memory enables you to download and boot from upgraded Cisco IOS images remotely or from software images resident in the RSP8 Flash memory.
Although no monitoring of voltage or temperature is done by the RSP8, a comparator device ensures that voltage is within the normal operating ranges, and three temperature sensors on the RSP8 send temperature information to the chassis interface (CI) card. The CI card reports all voltage and temperature readings, and these readings are available through standard software commands for environmental monitoring. The RSP8 uses a software-controlled configuration register, so you do not have to remove the RSP8 to configure jumpers. There are no user-configurable jumpers on the RSP8.
Before beginning the installation procedures, review the following sections to ensure awareness of the appropriate regulatory and safety requirements, and to ensure that your RSP8 hardware functions properly with compatible components:
|
Note If you are replacing an existing RSP8, back up your current configuration file to a remote server before you remove the RSP8 to avoid having to reenter all your current configuration information manually. To back up the file, you need access to a remote TFTP server. See the "Saving and Retrieving a Configuration File" section for instructions for uploading the file to a TFTP server or saving it to Flash memory, and then retrieving it after the new RSP8 is installed. |
Following are safety guidelines that you should follow when working with any equipment that connects to electrical power or telephone wiring.
 |
Warning Only trained and qualified personnel should be allowed to install or replace this equipment. |
Follow these basic guidelines when working with any electrical equipment:
Use the following guidelines when working with any equipment that is connected to telephone wiring or to other network cabling:
Electrostatic discharge (ESD) damage, which can occur when electronic cards or components are improperly handled, can result in complete or intermittent failures. Each processor module contains a printed circuit card that is fixed in a metal carrier.
Electromagnetic interference (EMI) shielding, connectors, and a handle are integral components of the carrier. Although the metal carrier helps to protect the board from ESD, use an ESD-preventive wrist or ankle strap whenever you handle any electronic system component.
Following are guidelines for preventing ESD damage:
|
Caution For safety, periodically check the resistance value of the antistatic strap. The measurement should be between 1 and 10 megohms (Mohms). |
This section describes compatibility requirements for the RSP8.
Following are chassis slot and DRAM requirements for ensuring RSP8 compatibility.
Flash memory cards, Flash Disks, and DRAM DIMMs must meet the following requirements:
|
Note You can reboot from a Flash memory card or Flash Disk in the RSP8 that was previously formatted on an RSP4+. |
The minimum supported Cisco IOS release compatible with the RSP8 is release 12.0(5)T or a later release of Cisco IOS release 12.0 T. For the latest compatible software releases, refer to the Software Advisor at http://www.cisco.com/cgi-bin/Support/CompNav/Index.pl.
|
Note The 32-MB Flash memory card is compatible with Cisco IOS Release 12.1(5)T1 or a later release of 12.1 T. |
Use the show version and show hardware commands to display the router's current hardware and software configurations. The show microcode command lists the bundled microcode (and target hardware) version for each processor type. The show controller cbus command shows the microcode version you are running. The show diagbus command shows the RSP8 board's hardware version and revision.
For additional descriptions of show commands, refer to the Configuration Fundamentals Configuration Guide and Configuration Fundamentals Command Reference publications, which are available online, on the Documentation CD-ROM, or as printed documents.
|
Note If the required system software and microcode are not available in your system, contact a customer service representative for upgrade information. (To obtain assistance, see the "Technical Assistance Center" section on page 90.) |
Your router's configuration, protocols and features might require more than the 64 MB of DRAM that is shipped with the RSP8. To upgrade DRAM, see the "Replacing and Upgrading DRAM DIMMs" section.
To ensure proper operation of a system configured for HSA or HA, note the guidelines below:
|
Caution Before using a Flash memory card previously formatted and used in an RSP, RSP7000, RSP1, RSP2, or RSP4, you must reformat the Flash memory card. Flash memory cards formatted on any of these processors do not work properly in an RSP8. You must first reformat it on your RSP8 system. Refer to Flash Memory Card Installation Instructions (part number DOC-782083=) for instructions on reformatting Flash memory. |
Microcode is a set of processor-specific software instructions that enables and manages the features and functions of a specific processor type. At system startup or reload, the system loads the microcode for each processor type present in the system. The latest available microcode image for each processor type is bundled and distributed with the system software image.
|
Note Overriding the bundle can result in incompatibility among the various interface processors in the system. We recommend that you use only the microcode image that is bundled. |
You need some or all of the following parts and tools to install, remove, and replace an RSP8 or to upgrade DRAM. If you need additional equipment, contact a customer service representative for ordering information.
|
Caution To prevent memory problems, DRAM DIMMS must be 3.3-volt (V) devices. Do not attempt to install higher-voltage devices in the RSP8 DIMM sockets. |
Before you begin, be sure that your system meets the minimum software, hardware, and microcode requirements described in the "Compatibility Requirements" section.
This section includes the following procedures for installing or replacing an RSP8:
After the new RSP8 is secure, follow the procedures in the "Troubleshooting the Installation" section to verify that it is installed and functioning properly.
|
Caution Removing the only installed RSP8 from a system while the system is operating will cause the system to crash. Consider this before removing an RSP8 while the system is operating. To ensure that the standby RSP8 operates properly with the full system configuration should the active RSP8 ever fail, the standby RSP8 must have the same (or higher) DRAM and Flash memory capacity as the active RSP8. See the "Memory Components" section for RSP8 memory component requirements. |
|
Note The carriers on processor modules have electromagnetic interference (EMI) fences for EMI shielding; therefore, they fit very tightly in the chassis slots. To ensure that you can properly remove or install an RSP8 in RSP slot 7 from the Cisco 7513 router, we recommend that you proceed as follows: first remove an interface processor installed in slot 8, remove or install the RSP8 in RSP slot 7 (and fasten its captive installation screws as appropriate), and then reinstall the interface processor in slot 8. |
When you remove or install the RSP8, be sure to use the ejector levers, which help to ensure that the RSP8 is fully inserted in the backplane or fully dislodged from it. An RSP8 that is only partially connected to the backplane can halt the system unless a second RSP8 is installed.
Figure 3 shows the ejector lever mechanism. When you simultaneously push the ejector levers inward (toward the carrier handle), the levers push the RSP8 into the slot and ensure that the board connectors are fully seated in the backplane.
To remove the RSP8, complete the following steps:
Step 2 Attach an antistatic strap to yourself and then connect the equipment end of the strap to a captive installation screw on an installed interface processor, or to any unfinished chassis surface.
Step 3 If you are replacing the RSP8, disconnect any devices that are attached to the console or auxiliary ports. If you are removing the RSP8 for maintenance and will reinstall the same one, you can leave the devices attached provided that doing so will not strain the cables.
Step 4 Use a screwdriver to loosen the two captive installation screws. (See Figure 3.)
Step 5 Place your thumbs on the ends of each of the ejector levers and simultaneously pull them both outward, away from the carrier handle (as shown in the illustration at the bottom of Figure 3c) to release the carrier from the slot and to dislodge the RSP8 from the backplane.
Step 6 Grasp the handle of the RSP8 with one hand and pull the RSP8 straight out of the slot, keeping your other hand under the carrier to guide it. (See Figure 4.) Keep the carrier parallel to the backplane. Avoid touching the board or any connector pins.
Step 7 Place the removed RSP8 on an antistatic mat or foam. If you plan to return the RSP8 to the factory, immediately place it in an antistatic bag to prevent ESD damage.
Step 8 Attach the equipment end of the ESD-preventive strap to the RSP8 before performing any maintenance on the RSP8 that might create an ESD hazard.
This completes the removal procedure. If you removed the RSP8 to replace DIMMs, proceed to the "Replacing and Upgrading DRAM DIMMs" section. If you are replacing the RSP8, proceed to the next section to install the new RSP8.
|
Caution Removing the only installed RSP8 from a system while the system is operating will cause the system to crash. Consider this before removing an RSP8 while the system is operating. To ensure that the standby RSP8 operates properly with the full system configuration should the active RSP8 ever fail, the standby RSP8 must have the same (or higher) DRAM and Flash memory capacity as the active RSP8. See the "Memory Components" section for RSP8 memory component requirements. |
|
Note The carriers on processor modules have electromagnetic interference (EMI) fences for EMI shielding; therefore, they fit very tightly in the chassis slots. To ensure that you can properly remove or install an RSP8 in RSP slot 7 from the Cisco 7513 router, we recommend that you proceed as follows: first remove an interface processor installed in slot 8, remove or install the RSP8 in RSP slot 7 (and fasten its captive installation screws as appropriate), and then reinstall the interface processor in slot 8. |
The RSP8 is keyed for installation only in an RSP slot. By default, the active RSP is the one that occupies the first RSP slot in the router: slot 2 in the Cisco 7507 and Cisco 7507-MX, and slot 6 in the Cisco 7513 and Cisco 7513-MX.
To install an RSP8, complete the following steps:
Step 2 Place the back of the RSP8 in the appropriate RSP slot and align the notches along the edge of the carrier with the grooves in the slot. (See Figure 3a.)
|
Caution To prevent damage to the backplane, you must install the RSP8 in one of the two RSP slots on the router. The slots are keyed for correct installation. Forcing the RSP8 into a different slot can damage the backplane and the RSP8. |
Step 3 While keeping the RSP8 parallel to the backplane, carefully slide the carrier into the slot until the RSP8 faceplate makes contact with the ejector levers, and then stop. (See Figure 3b.)
Step 4 Using the thumb and forefinger of each hand to pinch each ejector lever, simultaneously push both ejector levers inward (toward the handle) until they are parallel to the faceplate. (See Figure 3c.)
Step 5 Use a screwdriver to tighten the captive installation screws on the ends of the RSP8. (See Figure 3a)
Step 6 Use a screwdriver to tighten the two captive installation screws on the RSP8 faceplate to prevent the RSP8 from becoming partially dislodged from the backplane and to ensure proper EMI shielding. (These screws must be tightened to meet EMI specifications.)
Step 7 If you disconnected the console terminal to remove the RSP8, or if you are installing a new RSP8, connect the console terminal to the console port. (See the "Connecting a Console Terminal" section.)
Step 8 Ensure that a console terminal is connected (see the "Connecting a Console Terminal" section) and that it is turned on.
Step 9 Turn the system power back on, and proceed to the "Restarting the System" section to check the installation.
This completes the procedure for replacing the RSP8.
The system console port on the RSP8 is a DB-25 receptacle DCE port for connecting a console terminal, which you need to configure in order to communicate with your system. The console port is located on the RSP8 just below the auxiliary port, as shown in Figure 5, and is labeled Console.
Before connecting the console port, check the documentation for your terminal to determine the baud rate of the terminal you are using. The baud rate of the terminal must match the default baud rate (9600 baud). Set up the terminal as follows: 9600 baud, 8 data bits, no parity, and 2 stop bits (9600,8N2).
Use the console cable provided to connect the terminal to the console port on the RSP8, and then follow the steps in the "Restarting the System" section.
|
Note The console and auxiliary ports are asynchronous serial ports; any devices connected to these ports must be capable of asynchronous transmission. (Asynchronous is the most common type of serial device; for example, most modems are asynchronous devices.) |
The auxiliary port on the RSP8 is a DB-25 plug DTE port for connecting a modem or other DCE device (such as a channel service unit [CSU], data service unit [DSU], or other router) to the router. The port is located next to the console port on the RSP8 and is labeled AUX. An example of a modem connection is shown in Figure 5.
For systems with two RSP8s installed and the HSA or the HA feature enabled, you can connect to either the console or auxiliary ports simultaneously on both RSPs using a special, optional Y-cable. If only one RSP8 is installed, it is the system active by default.
|
Note The Y-cables are not required; two individual console cables and two individual auxiliary cables can be used instead. |
Figure 6 shows the console Y-cable and Figure 7 shows the auxiliary Y-cable.
When you turn the system power back on, verify that the system boots and resumes normal operation. If you are restarting the system after upgrading the DRAM, expect that it will take the system longer to complete the memory initialization portion of the boot sequence with more DRAM. (See the "Verifying System Startup Sequence" section.)
Follow these steps to verify that the RSP8 is installed and functioning properly:
Step 2 Observe the RSP8 LEDs. While the system initializes, the CPU halt LED on the RSP8 stays on. It goes off when the boot process is complete. As the RSP8 initializes each interface processor, the status LEDs on each interface processor go on and off in irregular sequence.
Step 3 For a Cisco 7507, Cisco 7507-MX, Cisco 7513, or Cisco 7513-MX with HSA or HA configured, verify that the console terminal displays the system banner and startup screen as the system restarts.
Step 4 With a single RSP8 (non-HSA or non-HA), verify that the console terminal displays the system banner and startup screen as the system restarts. The display should look similar to the following:
Step 5 After the system boots the software and initializes the interface processors, verify that the RSP8 LEDs are in the following states:
Step 6 Verify that all the enabled LEDs (on the interface processors) are on.
Step 7 In systems with a second RSP8 installed (and HSA or HA configured), use the show version command to verify that the standby RSP8 is recognized by the system. Following is a sample from a Cisco 7513:
(Note that this could also be "slot 6" depending on which RSP is configured as the standby or the recent crash history of your router.)
When you have verified all the conditions in Step 2 through Step 6 (or Step 7 if you have a second RSP8 installed and want to use the HSA or HA features), the installation is complete. If you replaced the RSP8 and saved your configuration file to a remote server before doing so, see the "Retrieving the Configuration File" section. If you replaced the RSP8 and did not save the configuration, use the configure command or the setup facility to reenter the configuration information.
An error condition exists if no LEDs go on at power up or after initialization, or if the CPU halt LED go on and remain on. If this happens, proceed to the "Troubleshooting the Installation" section to try to isolate the problem.
For more complete configuration information, refer to the Configuration Fundamentals Configuration Guide and the Configuration Fundamentals Command Reference publications, which are available online, on the Documentation CD-ROM, or as printed documents.
If you have a second RSP8 installed, you must configure the HSA (or HA, if you prefer) features for your Cisco 7507, Cisco 7507-MX, Cisco 7513, or Cisco 7513-MX router. Read the following caution, and then proceed to the "Configuring High System Availability" section, or the "Enabling High Availability Features" section.
|
Caution When you install a second RSP8 card for the first time and plan to enable the HSA or HA features, you must immediately configure it correctly. See the "Configuring High System Availability" section, or the "Enabling High Availability Features" section. This ensures that the new standby is configured consistently with the active. Failure to do so might result in an unconfigured standby RSP8 (or RSP16) taking over control of the router when the active fails, rendering the network inoperable. |
This completes the procedure for restarting the system.
If you have a single RSP8, you can configure your system according to the Cisco IOS release appropriate for your router. See the Cisco IOS software configuration documentation set that corresponds to the software release installed on your Cisco hardware at http://www.cisco.com/univercd/cc/td/doc/product/software/index.htm .
If you have more than one RSP8 (or an RSP8 and an RSP16), and you are using a Cisco 7507 or a Cisco 7507-MX router or a Cisco 7513 or a Cisco 7513-MX router, you must configure your router for either high system availability (HSA), the default (see the "Configuring High System Availability" section), or high availability (HA) (see the "Enabling High Availability Features" section).
Before you configure your system using the EXEC-level commands, you must enter the privileged level of the EXEC command interpreter using the enable command. The system prompts you for a password if one has been set. The system prompt for the privileged EXEC level ends with a pound sign (#) instead of an angle bracket (>).
At the console terminal, enter the privileged EXEC level as follows:
Step 2 Type the password (the password is case sensitive). For security purposes, the password is not displayed.
Step 3 When you specify the correct password, the system displays the privileged-level system prompt (#) as follows:
The pound sign (#) at the system prompt indicates the privileged level of the EXEC command interpreter, from which you can execute EXEC-level commands.
This completes the procedure for using the EXEC command interpreter.
For configuration information and support, refer to the Cisco IOS software configuration documentation set that corresponds to the software release installed on your Cisco hardware.
|
Note You can access Cisco IOS software configuration information at http://www.cisco.com. Refer to the Software Advisor at http://www.cisco.com/cgi-bin/Support/CompNav/Index.pl for additional information. |
For troubleshooting information, refer to the "Troubleshooting the Installation" section.
This section describes high system availability (HSA), a feature that enables a router to continue processing and forwarding packets after a planned or unplanned outage.
It includes the following topics:
HSA is the system default when two RSP8s, or an RSP8 and an RSP16 (one designated as the "active" and the other as the "standby") are installed in a router and the active RSP8 fails. The standby RSP8 takes over in this situation, known as a "cold standby." The router restarts without manual intervention (for example, without inserting a new RSP) by rebooting with the standby RSP. The standby has its own image and configuration file and acts as a single processor.
|
Caution To ensure proper functioning of the standby RSP8 in the event of an active RSP8 failure, the standby RSP8 should have the same boot image, the same ROM monitor, and the same DRAM configuration as the active RSP8. |
|
Note An RSP8 can interoperate with another RSP8, or with an RSP16. It cannot interoperate with an RSP1, an RSP2, or an RSP4/4+. In the following text, you can substitute references to two RSP8s with an RSP8 and an RSP16. |
When two new RSP8s (or an RSP8 and an RSP16) are installed at the same time, the RSP that occupies the first even RSP slot on the router is the active (normally the RSP16 if the RSP8 is used in conjunction with the RSP16), and the RSP that occupies the odd RSP slot is the standby. If a crash has occurred, the RSP in the odd slot becomes the active and the RSP in the even slot becomes the standby.
HSA is supported on the following routers: Cisco 7507, Cisco 7507-MX, Cisco 7513, and Cisco 7513-MX. HSA is not supported on the Cisco 7505 or the Cisco 7576 routers.
The cold standby procedure, from initial failure to first packet transmission, currently takes approximately eight to ten minutes.
For more complete HSA configuration information, refer to the Cisco IOS Configuration Fundamentals Configuration Guide and the Cisco IOS Configuration Fundamentals Command Reference publications, which are available online, on the Cisco Documentation CD-ROM, or as printed copies.
During HSA operation, the active RSP8 card functions as if it were a single processor, controlling all functions of the router. The standby RSP8 card does nothing but actively monitor the active RSP8 for failure.
When the standby RSP8 detects a nonfunctional active RSP8, the standby resets itself and takes part in active-standby arbitration. Active-standby arbitration is a ROM monitor process that determines which RSP8 card is the active and which is the standby upon startup (or reboot).
If a system crash causes the active RSP8 to fail, the standby RSP8 becomes the new active RSP8 and uses its own system image and configuration file to reboot the router. The failed RSP8 card (now the standby) remains inactive until you perform diagnostics, correct the problem, and then issue the standby reload command.
With HSA operation, use the following guidelines:
|
Caution Removing the active RSP8 while the system is operating might cause the system to crash; however, the system reloads with the standby RSP8 as the new active. To prevent any system problems, do not remove the active RSP8 while the system is operating. |
The two common ways to use HSA are as follows:
You can also use HSA for advanced implementations. For example, you can configure the RSP8 cards with the following:
|
Note Other, more complex uses of HSA are also possible, but are not addressed in this document. For more
information, contact your Cisco service representative. The following HSA configuration information specifically refers to a Cisco 7513 and Cisco 7513-MX. The primary difference between the Cisco 7507 and Cisco 7507-MX and the Cisco 7513 and Cisco 7513-MX, with respect to HSA configuration, is that the RSP active and standby slots in the Cisco 7507 and Cisco 7507-MX are slot 2 and slot 3, respectively. |
To configure HSA operation with the RSP8, you must have:
|
Caution The HSA feature works with two RSP8 cards, or with one RSP8 and one RSP16. The RSP8 cannot be used in combination with the RSP1, RSP2 or RSP4/4+ when utilizing the HSA feature. |
Before you configure HSA, decide how you intend to use HSA, as described in the "HSA Implementation Methods" section. Do you want it for simple hardware backup or for software error protection? If you are using new or experimental Cisco IOS software, consider using the software error protection method; otherwise, use the simple hardware backup method.
Once you have decided which method to use, complete the tasks in the following sections. The first two and last two tasks are required for both implementations. The third and fourth tasks relate to simple hardware backup. The fifth task relates to software error protection only.
|
Note The following HSA configuration examples refer to a Cisco 7513. If you have a Cisco 7507, the primary difference is that the active and the standby RSPs are located in slots 2 and 3, respectively. |
Your view of the environment is always from the active RSP8 perspective, and you must define a default standby RSP8. The router uses the default standby information when booting.
To define the default standby RSP8, use the following commands beginning in privileged EXEC configuration mode:
|
Upon the next system reboot, the above changes take effect (if both RSP8 cards are operational). Thus, the specified default standby becomes the standby RSP8 card. The other RSP8 card takes over control of the system and controls all functions of the router.
If you do not specifically define the default standby RSP8, the RSP8 card located in the higher number processor slot is the default standby. On the Cisco 7507 and Cisco 7507-MX, processor slot 3 contains the default standby RSP. On the Cisco 7513 and Cisco 7513-MX, processor slot 7 contains the default standby RSP.
The following example sets the default standby RSP8 to processor slot 2 on a Cisco 7507 or Cisco 7507-MX:
With the simple hardware backup and software error protection implementation methods, you always want your active and standby configuration files to match. To ensure that they match, turn on automatic synchronization. In automatic synchronization mode, the active copies its startup configuration to the standby's startup configuration when you issue a copy command that specifies the active's startup configuration (nvram:startup-config) as the target.
Automatic synchronization mode is on by default; however, to turn it on manually, use the following commands beginning in privileged EXEC configuration mode:
|
The following example turns on automatic configuration file synchronization:
For simple hardware backup, ensure that both RSP cards have the same system image.
To ensure that both RSPs have the same system image, use the following commands beginning in privileged EXEC configuration mode:
|
|
Note Standard 16-, 20-, or 32-MB Flash memory cards are supported with the RSP8. (The 20-MB Flash
memory card is currently the default.) See
Flash Memory Card Installation Instructions for detailed information. You should specify slot0
or slot1 in your command, depending on which slot you are using. Standard 48-MB, 64-MB, and 128-MB Flash Disks are supported with the RSP8. See Using the Flash Disk for additional information. You should specify slot0 or slot1 in your command, depending on which slot your are using. |
The following example ensures that both RSPs have the same system image. Note that because no environment variables are set, the default environment variables are in effect for both the active and the standby RSP.
To ensure that both RSPs have the same microcode images, use the following commands beginning in privileged EXEC configuration mode:
|
The following example ensures that both RSPs have the same microcode image. Notice that slots 0, 1, 4, 9, and 10 load microcode from the bundled software, as noted by the statement "software loaded from system." The Channel Interface Processor (CIP2) in slot 11 does not use the microcode bundled with the system. Instead, it loads the microcode from slot0:pond/bath/rsp_fsip20-1. Thus, you must ensure that the standby RSP8 has a copy of the same FSIP microcode in the same location.
For software error protection, the RSPs should have different system images.
When the factory sends you a new router with two RSP8s, you receive the same system image on both RSPs. To configure the HSA feature for software error protection, you need two separate software images on the RSPs. You copy a desired image to the active RSP card and modify the boot system commands to reflect booting under two separate system images. Each RSP uses its own image to boot the router when it becomes the active RSP.
To specify different startup images for the active and the standby RSPs, use the following commands in beginning in privileged EXEC configuration mode:
|
| 1 See the "Software Configuration Register Settings" section for more information on systems that can use this command to modify the software configuration register. |
|
Note The following examples show systems with two RSP8s. |
The following example describes an upgrade scenario under the following conditions:
Figure 8 illustrates the software error protection configuration for this sample scenario. The commands to set up this configuration follow the figure.
Step 2 Now view the standby software image location and version:
Step 3 To upgrade to the Cisco IOS Release 12.0(22.3)S1 system image on the active RSP, copy the Cisco IOS Release 12.0(22.3)S1 system image from a TFTP server to slot 0 on the active RSP:
Step 4 Enter global configuration mode and configure the system to boot first from a Cisco IOS Release 12.0(22.3)S1 system image and then from a Cisco IOS Release 12.0(23)S system image.
With this configuration, when the slot 6 RSP is active, it looks first in its PC Card slot 0 for the system image file rsp-pv-mz.120-22.3.S1 to boot. Finding this file, the router boots from that system image. When the slot 7 RSP is active, it also looks first in its slot 0 for the system image file rsp-pv-mz.120-22.3.S1 to boot. Because that image does not exist in that location, the slot 7 RSP looks for the system image file rsp-pv-mz.120-23.S in slot 0 to boot. Finding this file in its PC Card slot 0, the router boots from that system image. In this way, each RSP can reboot the system using its own system image when it becomes the active RSP.
Step 5 Configure the system further with a fault-tolerant booting strategy:
Step 6 Set the configuration register to enable loading of the system image from a network server or from Flash memory and save the changes to the active and the standby startup configuration file:
Step 7 Reload the system so that the active RSP uses the new Cisco IOS Release 12.0(22.3)S1 system image:
This completes the sample procedure for upgrading to a new software version.
The following example describes a backup scenario under the following conditions:
In this scenario, we begin with the configuration shown in Figure 9.
Next, we copy the rsp-pv-mz.120-23.S image to the active and the standby RSPs, as shown in Figure 10.
Last, we delete the rsp-pv-mz.120-22.3.S1 image from the standby RSP4/4+ card, as shown in Figure 11:
Complete the following steps to configure software error protection for this sample scenario:
Step 2 Copy the Cisco IOS Release 12.0(23)S system image from a TFTP server to PC Card slot 0 on the active and standby RSPs:
Step 3 Delete the rsp-pv-mz.120-22.3.S1 image from the standby RSP:
Step 4 Configure the system to boot first from a Cisco IOS Release 12.0(22.3)S1 system image and then from a Cisco IOS Release 12.0(23)S system image:
Step 5 Configure the system further with a fault-tolerant booting strategy:
Step 6 Set the configuration register to enable loading of the system image from a network server or from Flash memory and save the changes to the active and the standby startup configuration file:
|
Note You do not need to reload the router in this example, because the router is currently running the Cisco IOS Release 12.0(22.3)S1 image. |
This completes the sample procedure for backing up with an older software version.
You can optionally set environment variables on both RSPs in a Cisco 7507, Cisco 7507-MX, Cisco 7513, or Cisco 7513-MX router.
|
Note When you configure the HSA operation, we recommend that you use the default environment variables. If you do change the variables, we recommend that you set the same device for equivalent environment variables on each RSP. For example, if you set one RSP CONFIG_FILE environment variable to NVRAM, then set the other RSP CONFIG_FILE environment variable to NVRAM also. |
You set environment variables on the active RSP just as you would if it were the only RSP in the system. You can set the same environment variables on the standby RSP manually or automatically.
The following sections describe these two methods:
For more complete configuration information on how to set environment variables, refer to the Cisco IOS Configuration Fundamentals Configuration Guide and the Cisco IOS Configuration Fundamentals Command Reference publications, which are available online on Cisco.com, on the Documentation CD-ROM, or as printed documents.
Once you set the active RSP environment variables, you can manually set the same environment variables on the standby RSP using the slave sync config command.
However, automatic synchronization is enabled by default on the RSP. Therefore, unless you have disabled automatic synchronization, or this is the first time you are installing a second RSP, a manual update is not required. For more information about automatic synchronization, see the "Ensuring that Both RSPs Contain the Same Configuration Files" section.
|
Caution When you install a second RSP for the first time, you must immediately configure it using the slave sync config command. This ensures that the new standby RSP is configured consistently with the active RSP. Failure to do so might result in an unconfigured standby RSP taking control of the router when the active RSP fails, rendering the network inoperable. |
For additional information about using the slave sync config command, see the "Monitoring and Maintaining HSA Operation" section. For more complete HSA configuration information, refer to the Cisco IOS Configuration Fundamentals Configuration Guide and the Cisco IOS Configuration Fundamentals Command Reference publications.
To manually set environment variables on the standby RSP, use the following commands beginning in global configuration mode:
|
With automatic synchronization turned on, when you set the active RSP environment variables and save them, the system automatically saves the same environment variables to the standby's startup configuration.
You do not need to use the slave sync config command when automatic synchronization is enabled, unless this is the first time you are installing a second RSP. For more information about this use of the slave sync config command, see the "Monitoring and Maintaining HSA Operation" section.
|
Note Automatic synchronization mode is on by default. Therefore, unless you have disabled automatic synchronization a manual update is not required. For more information about automatic synchronization, see the "Ensuring that Both RSPs Contain the Same Configuration Files" section. |
To set environment variables on the standby RSP when automatic synchronization is on, use the following commands on the active RSP beginning in global configuration mode:
|
To monitor and maintain HSA operation, you can override the standby image that is bundled with the active image by using the following command in global configuration mode:
|
Note The slave image system command, previously used to determine which image the standby runs, is not valid with newer images containing HA features. |
You can manually synchronize configuration files and ROM monitor environment variables on the active and the standby RSPs using the following command in privileged EXEC configuration mode:
|
Caution When you install a second RSP for the first time, you must immediately configure it using the slave sync config command. This ensures that the new standby RSP is configured consistently with the active RSP. Failure to do so might result in an unconfigured standby RSP taking control of the router when the active RSP fails, rendering the network inoperable. |
The slave sync config command is also a useful tool for more advanced implementation methods not discussed in this document. Refer to the Cisco IOS Configuration Fundamentals Configuration Guide and the Cisco IOS Configuration Fundamentals Command Reference publications, which are available on the Documentation CD-ROM, online at Cisco.com, or as printed documents.
This section discusses the following topics:
High availability (HA), an alternative to the default high system availability (HSA) feature, is a series of features that minimizes system downtime through a "warm standby." Warm standby allows the system to switch over to a standby RSP preloaded with a Cisco IOS image in 30 seconds to 5 minutes, depending on the feature. For more information on high service availability (HSA), the system default program, refer to the "Configuring High System Availability" section. Like HSA, HA is supported on the Cisco 7507, Cisco 7507-MX, Cisco 7513, and Cisco 7513-MX routers with two RSP8s, or with one RSP8 and one RSP16.
A router configured for HA has two RSPs, an active RSP and a standby RSP. The active RSP controls all functions of the router, and the standby RSP monitors the active for failure.
SLCR is disabled by default and needs to be manually configured. When SLCR is enabled, and more than two linecards crash simultaneously, all line cards will be reset.
For more information on how to configure SLCR, refer to the Cisco 7500 Single Line Card Reload feature module at http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s13 /slcr.htm.
RPR is disabled by default, and needs to be manually configured. For more information on RPR, refer to the Route Processor Redundancy and Fast Software Upgrade on Cisco 7500 Series Routers feature module available online at http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st 16/st_rpr7x.htm.
Online removal of the active RSP causes all line cards to reset and reload, which is equivalent to an RPR switchover, and results in a longer switchover time. When it is necessary to remove the active RSP from the system, first issue a switchover command to switch from the active RSP to the standby RSP.
RPR+ is disabled by default, and needs to be manually configured. RPR+ does not support the Legacy interface processor card. The system will default to RPR if the router includes an Legacy interface processor card. For more information on how to configure RPR+, refer to the RPR+ on Cisco 7500 Series Routers feature module, available online at http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st19/st _rpr2.htm.
For more information on FSU, refer to the Route Processor Redundancy and Fast Software Upgrade on Cisco 7500 Series Routers feature module available online at http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120st/120st 16/st_rpr7x.htm.
SSO is disabled by default, and needs to be manually configured. SSO does not support the Legacy interface processor cards. For more information on how to configure SSO, refer to the Stateful Switchover feature module available online at http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22/sso 120s.htm.
Cisco NSF is supported by the BGP, OSPF, and IS-IS protocols for routing and by Cisco Express Forwarding (CEF) for forwarding. For more information on how to configure NSF, see the Cisco Nonstop Forwarding feature module available online at http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s22 /nsf120s.htm.
The RPR and FSU features are available on the Cisco 7507, Cisco 7507-MX, Cisco 7513, and Cisco 7513-MX routers, which are loaded with two route switch processors (RSPs). The router is loaded with two route switch processors (RSPs), which can be two RSP8s, or an RSP16 and an RSP8.
The following HA features became available on the following minimum software releases:
|
Note For current hardware and softwarecompatibility information, refer to the Software Advisor tool at http://www.cisco.com/cgi-bin/Support/CompNav/Index.pl . |
See the following sections for the configuration tasks required to run the RPR/RPR+, SSO with NSF, FSU, and SLCR features.
To enter privileged EXEC configuration mode, enable the router using the following steps:
Step 2 Type the password (the password is case sensitive). For security purposes, the password is not displayed.
When you specify the correct password, the system displays the privileged-level system prompt (#):
This completes the procedure to enable the router.
You can use TFTP to copy a high availability Cisco IOS software image onto the active and standby RSPs.
|
Note Before you begin to copy a file to Flash memory, be sure that there is enough space available in Flash memory. To verify the amount of Flash memory available, you can use the show flash: command. Compare the size of the file you are copying to the amount of available Flash memory shown. If the space available is less than the space required by the file you will copy, the copy process will continue, but the entire file will not be copied into Flash memory. |
To copy a Cisco IOS software image from a TFTP server to a Flash memory card or Flash Disk on the active RSP, use the following commands beginning in privileged EXEC configuration mode:
|
| 1 Before you copy a file to Flash memory, be sure there is ample space available in Flash memory. Compare the size of the file you are copying to the amount of available Flash memory shown. If the space available is less than the space required by the file you will copy, the copy process will continue, but the entire file will not be copied into Flash memory. |
Though it is not required, we recommend that you modify the software configuration register boot field so that the system boots the same image that the hw-module slot slot-number image file-spec command specifies in the "Configuring RPR and RPR+" section.
|
|
Note Online removal of the active RSP causes all line cards to reset and reload, which is the equivalent to an RPR switchover, and results in a longer switchover time. When it is necessary to remove the active RSP from the system, first issue a switchover command to switch from the active RSP to the standby RSP. |
To configure RPR and RPR+, use the following commands beginning in privileged EXEC configuration mode:
|
Use the show redundancy command to verify that RPR or RPR+ is enabled:
In the following example, the active RSP is in slot 2 and the standby RSP is installed in slot 3 of a Cisco 7507 router.
To configure SSO, use the following commands beginning in privileged EXEC configuration mode:
|
The autosynchronization procedure is only for devices supporting Frame Relay and is optional. To configure Frame Relay SSO to synchronize LMI sequence numbers between the active and standby RSPs, use the following command in global configuration mode.
|
To verify that SSO is configured on the networking device, use the show redundancy command. To verify that the device is running in SSO mode, use the show redundancy states command. The show redundancy states command specifies whether the unit is running in SSO mode, which is indicated by STANDBY HOT.
|
Note The output of these commands will vary based on your device configuration and system site requirements. |
Step 2 Run the show redundancy states command to verify that SSO is operating on the device.
Step 3 Use the show redundancy client command to display the list of applications and protocols that have registered as SSO protocols or applications. Verify the list of supported line protocols.
Cisco Nonstop Forwarding (NSF) always runs together with SSO. If you have not already configured SSO, refer to the "Configuring a Stateful Switchover (SSO)" section. Cisco NSF is supported by the BGP, OSPF, and IS-IS protocols for routing and by Cisco Express Forwarding (CEF) for forwarding. Of the routing protocols, BGP, OSPF, and IS-IS have been enhanced with NSF-capability and awareness, which means that routers running these protocols can detect a switchover and take the necessary actions to continue forwarding network traffic and to recover route information from the peer devices. The IS-IS protocol can be configured to use state information that has been synchronized between the active and the standby RSP to recover route information following a switchover instead of information received from peer devices.
A device is said to be NSF-capable if it has been configured to support NSF; therefore, it would rebuild routing information from NSF-aware or NSF-capable neighbors.
Each protocol depends on CEF to continue forwarding packets during switchover while the routing protocols rebuild the Routing Information Base (RIB) tables. Once the routing protocols have converged, CEF updates the FIB table and removes stale route entries. CEF, in turn, updates the line cards with the new FIB information.
See the following sections for the NSF feature. Each task in the list is identified as either required or optional.
The CEF NSF feature operates by default while the networking device is running in SSO mode. No configuration is necessary.
|
Note You must configure BGP graceful restart on all peer devices participating in BGP NSF. |
To configure BGP for NSF, use the following commands beginning in privileged EXEC configuration mode, and repeat this procedure on each of the BGP NSF peer devices:
|
|
Note All peer devices participating in OSPF NSF must be made OSPF NSF-aware, which happens automatically once you install an NSF software image on the device. |
To configure NSF for OSPF, use the following commands beginning in privileged EXEC configuration mode:
|
To configure NSF for IS-IS, use the following commands beginning in privileged EXEC configuration mode:
|
To verify that CEF is NSF-capable, use the show cef state command:
To verify NSF for BGP, you must check that the graceful restart function is configured on the SSO-enabled networking device and on the neighbor devices. Perform the following steps:
Step 2 Repeat Step 1 on each of the BGP neighbors.
Step 3 On the SSO device and the neighbor device, verify that the graceful restart function is shown as both advertised and received, and confirm the address families that have the graceful restart capability. If no address families are listed, then BGP NSF also will not occur:
To verify NSF for OSPF, you must check that the NSF function is configured on the SSO-enabled networking device. Perform the following steps:
Step 2 Use the show ip ospf command to verify that NSF is enabled on the device:
To verify NSF for IS-IS, you must check that the NSF function is configured on the SSO-enabled networking device. Perform the following steps:
Step 2 If the NSF configuration is set to cisco, use the show isis nsf command to verify that NSF is enabled on the device. Using the Cisco configuration, the display output will be different on the active and standby RSPs. The following display shows sample output for the Cisco configuration on the active RSP.
In this example, note the presence of "NSF restart enabled":
The following display shows sample output for the Cisco configuration on the standby RSP. In this example, note the presence of "NSF restart enabled":
Step 3 If the NSF configuration is set to ietf, use the show isis nsf command to verify that NSF is enabled on the device. The following display shows sample output for the IETF IS-IS configuration on the networking device:
To troubleshoot the NSF feature, use the following commands in privileged EXEC configuration mode, as needed:
|
For the following troubleshooting situations, try the corresponding recommended action to resolve the problem.
Symptom The system displays FIB errors.
Recommended Action Use the show cef state command to verify that distributed CEF switching is enabled on your platform. To enable distributed CEF, use the ip cef distributed command in global configuration mode on the active RSP.
Symptom Cannot determine if an OSPF neighbor is NSF-aware.
Recommended Action To verify whether an OSPF neighbor device is NSF-aware and if NSF is operating between them, use the show ip ospf neighbor detail command.
Symptom The system loses, or appears to lose, adjacencies with network peers following a stateful switchover.
Recommended Action Use the show clns neighbors detail command to find any neighbors that do not have "NSF capable" and make sure that they are running NSF-aware images. Additionally, for ISIS, the standby RSP must be stable for 5 minutes (default) before another restart can be initiated. Use the nsf interval command to reset the restart period.
The following example configures BGP NSF on a networking device:
The following example configures BGP NSF on a neighbor router. All devices supporting BGP NSF must be NSF-aware, meaning that these devices recognize and advertise graceful restart capability.
The following example configures OSPF NSF on a networking device:
The following example configures Cisco proprietary IS-IS NSF operation on a networking device:
The following example configures IS-IS NSF for IETF operation on a networking device:
To perform a Fast Software Upgrade (FSU), use the following commands beginning in privileged EXEC configuration mode:
|
| 1 Before you copy a file to Flash memory, be sure there is ample space available in Flash memory. Compare the size of the file you are copying to the amount of available Flash memory shown. If the space available is less than the space required by the file you will copy, the copy process will continue, but the entire file will not be copied into Flash memory. |
The following example show a Fast Software Upgrade performed on a Cisco 7507 router with an active RSP in slot 2 and a standby RSP installed in slot 3.
The Cisco 7500 SLCR feature is disabled by default. Therefore, the process for disabling this feature is only necessary if the Cisco 7500 SLCR feature has been enabled by the user on the Cisco 7500 series router.
To enable the Cisco 7500 Single Line Card Reload (SLCR) feature, use the service single-slot-reload-enable global configuration command on the Cisco 7500 series router.
|
To disable the Cisco 7500 Single Line Card Reload feature, use the no service single-slot-reload-enable global configuration command on the Cisco 7500 series router.
|
Use the show running-config command to verify that single line card reloading has been successfully enabled on the Cisco 7500 series router. If the service single-slot-reload-enable line appears in the command output, Cisco 7500 SLCR is enabled. If this line does not appear in the command output, Cisco 7500 SLCR is disabled.
In the following example, SLCR is enabled for all lines cards in the Cisco 7500 series router:
In the following example, SLCR is disabled for all line cards in the Cisco 7500 series router:
The debug oir command is used to debug the online insertion and removal (OIR) feature (which is also known as hot-swapping or power-on servicing). The debug oir command is often useful in debugging problems related to OIR, including single line card reloading.
Use the commands in the table below to troubleshoot the RPR, RPR+, SSO, and FSU features on Cisco 7500 series routers:
|
To display information about the active and the standby RSPs, use any of the following commands beginning in privileged EXEC configuration mode:
|
This section contains procedures to follow if your system does not restart as expected. Review the descriptions that follow so you can anticipate the expected system startup sequence. Then restart the system and try to isolate the problem by observing the LEDs as the system attempts to boot the software and initialize the RSPs and each interface processor.
This section includes the following topics:
Following are functional descriptions of the LEDs on the power supplies and processor modules, and the behavior you should observe at system startup.
On the router, the AC (or DC) OK LED is located on each power supply. If this LED does not go on and stay on, there is most likely a problem with the input power or one of the internal DC lines.
The AC (or DC) OK LED will not go on or will go off if the power supply reaches an out-of-tolerance temperature or voltage condition. It is unlikely that the power supply will shut down during startup because of an over-temperature condition; however, it can shut down if it detects an over- or undervoltage condition during startup. For descriptions of environmental monitoring functions, refer to the Cisco 7500 Series Installation and Configuration Guide, which is available online, on the Documentation CD-ROM, or in print.
Figure 12 shows the LEDs on the RSP8 faceplate. The LEDs on the RSP8 indicate the system and RSP8 status and which PC Card slot is active. The CPU halt LED, which goes on only if the system detects a processor hardware failure, should remain off. A successful boot is indicated when the normal LED goes on; however, this does not necessarily mean that the system has reached normal operation. During normal operation, the CPU halt LED should be off, and the normal LED should be on, indicating that the RSP8 is receiving +5V. The slot 0 and slot 1 LEDs indicate which PC Card slot is in use, and each LED blinks when the card is accessed by the system. The active and the standby LEDs provide a visual indication of whether the RSP8 is designated an active or a standby device.
|
Caution The reset switch (see Figure 12) resets the RSP8 and the entire system. To prevent system errors and problems, use it only at the direction of your Cisco-certified service representative. |
By checking the state of the LEDs, you can determine when and where the system failed in the startup sequence. Because you turn on the system power with the on/off switches on each power supply, it is easiest to observe the startup behavior from the rear of the router. Use the following descriptions of the normal startup sequence to isolate the problem, and then use the troubleshooting procedures wherever the system fails to operate as expected. If you are able to isolate the problem to a faulty hardware component, or if you are unable to successfully restart the system, see the "Technical Assistance Center" section for instructions on contacting a service representative.
|
Note The time required for the system to initialize (boot) might vary with different router configurations and the amount of memory that must be initialized. During the system startup sequence, the time required to initialize the memory (not necessarily the entire boot sequence) in a system that contains 256 MB of DRAM might be longer than in a system that contains less DRAM. |
During the boot sequence, the system banner display pauses while it initializes the memory. Because your RSP8 has more than 32 MB of DRAM, you might notice an increase in the amount of time required to initialize the memory. The pause in the banner display occurs after the copyright line and before the system displays the list of installed hardware, as shown in the following display:
|
Note The procedures in this section are based on the assumption that your system was operating correctly until you removed (or replaced) the RSP8. If the following sequence uncovers a new problem with the power subsystem or one of the interface processors, refer to the Cisco 7500 Series Installation and Configuration Guide for system startup troubleshooting procedures. |
Use the following startup sequences and troubleshooting procedures to isolate system problems:
If the system power LED still fails to go on as expected, a power supply or input power failure could be the problem. Before contacting a service representative, refer to the Cisco 7500 Series Installation and Configuration Guide for power subsystem troubleshooting procedures.
When the system power LED indicates normal operation, proceed to the next step.
Step 2 Listen for the system blower and observe the fan OK LED. You should hear the system blower start operating immediately after you turn on the system power. If you determine that the power supply is functioning normally and that an internal fan (or the system blower) is faulty, contact a service representative. If the blower or a power supply fan does not function properly at initial startup, you cannot make any installation adjustments.
Step 3 When you have verified that the power supply is functioning properly, observe the LEDs on the RSP8. The CPU halt LED always turns on during initial power-up of an RSP8 and remains on for approximately one-half second, then turns off. If it remains on during the startup sequence, the system has encountered a processor hardware error.
Step 4 During the boot process, the LEDs on most of the interfaces light in irregular sequence; this does not indicate either correct system startup or failure.
Step 5 When the system boot is complete, the RSP8 begins to initialize the interface processors. During this initialization, the LEDs on each interface processor behave differently (most flash on and off). The enabled LED on each interface processor goes on when initialization has been completed.
Step 6 When the system boot is complete and all interface processors have been initialized, the active RSP8's console screen displays a script and a system banner similar to the following:
If the system still fails to start up or operate properly, or if you isolate the cause of the problem to a failed component, contact a service representative for further assistance.
This completes the procedure for verifying system startup.
The Cisco 7500 series routers require that the first file on bootflash be a boot image. If it is not, the bootstrap software attempts to boot whatever file is first. While attempting to boot a non-image file, the system either crashes or hangs. The symptom for the RSP might be a series of Cs (CCCCC) displayed on the console. To troubleshoot, install a Flash Disk with a bootable first image in slot 0 of the RSP to allow the router to boot the Cisco IOS image. Verify the system boot settings using the show bootvar command.
|
Note If the configuration register is set incorrectly, this could lead to a boot failure. Refer to the "Software Configuration Register Settings" section for instructions on setting your configuration register. Setting the config-register to 0x0 sets the boot variable to boot to ROMmon. |
If your router continues to experiences this problem, open a case with TAC. See the "Technical Assistance Center" section for more information.
This section describes actions that you can take to correct or obtain information when an RSP fails. It includes the following topics:
If you have a Cisco 7507 or a Cisco 7513 with an RSP8 configured as the system standby, we strongly recommend that you use the following procedure to remove and replace an interface processor:
Step 2 Wait 15 seconds.
Step 3 Remove and replace the interface processor, using the procedures in the configuration note that shipped with your interface processor or in the Cisco 7500 Series Installation and Configuration Guide.
Step 4 Wait 15 seconds.
Step 5 Reinsert the standby RSP8.
This completes the procedure to remove and replace an interface processor.
When a new active RSP takes over ownership of the router, it automatically reboots the failed RSP as the standby RSP. You can also manually reload the failed RSP.
To manually reload a failed RSP from the active console, use the following command in privileged EXEC configuration mode:
To access the state of the failed RSP in the form of a stack trace from the active console, use the following command in privileged EXEC configuration mode:
|
| 1 This command is documented in the "System Management Commands" chapter of the Cisco IOS Configuration Fundamentals Command Reference publication. |
For information about other commands that you can use to display information about the RSPs, see the "Monitoring and Maintaining the Active and Standby RSPs" section.
This section includes the following RSP8 maintenance procedures:
This section describes the procedures for saving and retrieving a system configuration file using a TFTP server.
Configuration information resides in two places when the router is operating: the startup default (permanent) configuration in NVRAM, and the running (temporary) memory in RAM. The default startup configuration always remains available; NVRAM retains the information even when the power is shut down. The current information is lost if the system power is shut down. The current configuration contains all nondefault configuration information that you added with the configure command, the setup facility, or editing of the configuration file.
The configure command adds the current configuration to the default configuration in NVRAM so that it is also saved when power is shut down. Whenever you make changes to the system configuration, use the copy running-config startup-config command to ensure that the new configuration is saved.
If you replace the RSP8 in a system with only one RSP8, you also replace the entire configuration, which resides in NVRAM on the RSP8. If you copy the configuration file to a remote server before removing the RSP8, you can retrieve it later and write it into NVRAM on the new RSP8. You can also use the copy running-config slot0:config-file command to save the configuration file to Flash memory, and then use the copy slot0:config-file nvram:startup-config command to restore it.
If you do not copy the configuration file, you must use the configure command or the setup command facility to re-enter the configuration information after you install the new RSP8. For complete descriptions of these two commands, and instructions for using them, refer to the Cisco IOS software documentation.
If you are temporarily removing an RSP8, it is not necessary to copy the configuration file to a remote server; the lithium batteries retain the configuration file in memory until you replace the RSP8 in the system. This procedure requires privileged-level access to the EXEC command interpreter, which usually requires a password. See the "Using the EXEC Command Interpreter" section and contact your system administrator to obtain access, if necessary.
For configuration information and support, refer to the Cisco IOS software configuration documentation set that corresponds to the software release installed on your Cisco hardware.
Before you attempt to copy or retrieve a file from a remote host, ensure that the connection is good between the router and the remote server by using the packet internet groper (ping) program. The ping program sends a series of echo request packets to the remote device and waits for a reply. If the connection is good, the remote device echoes them back to the local device.
The console terminal displays the results of each message sent: an exclamation point (!) indicates that the local device received an echo, and a period (.) indicates that the server timed out while awaiting the reply. If the connection between the two devices is good, the system displays a series of exclamation points (! ! !) or [ok]. If the connection fails, the system displays a series of periods (. . .) or [timed out] or [failed].
To verify the connection between the router and a remote host, use the ping command followed by the name or Internet Protocol (IP) address of the remote server; then press Return. Although the ping command supports configurable options, the defaults, including IP as the protocol, are enabled when you enter a host name or address on the same line as the ping command. For a description of the configurable options, refer to the appropriate software documentation.
The following example shows a successful ping operation:
The following example shows the results of a failed ping operation:
If the connection fails, check the physical connection to the remote file server and verify that you are using the correct address or name, and then ping the server again. If you are unable to establish a good connection, contact your network administrator or see the "Technical Assistance Center" section for instructions on contacting technical assistance.
Before you copy (save) the running configuration to a TFTP file server, ensure the following:
To store information on a remote host, use the copy startup-config tftp privileged EXEC command. The command prompts you for the destination host's address and a filename, and then displays the instructions for confirmation. When you confirm the instructions, the router sends a copy of the currently running configuration to the remote host. The system default is to store the configuration in a file called by the name of the router with -confg appended. You can either accept the default filename by pressing Return at the prompt, or enter a different name before pressing Return.
To copy the currently running configuration to a remote host, perform the following steps:
Step 2 Use the ping command to check the connection between the router and the remote host. (See the previous section, "Using the ping Command to Ensure Connectivity.")
Step 3 Use the show running-config command to display the currently running configuration on the terminal and ensure that the configuration information is complete and correct.
Step 4 If it is not, use the configure command to add or modify the existing configuration. (Refer to the appropriate software documentation for descriptions of the configuration options available for the system and individual interfaces, and for specific configuration instructions.)
|
Note Before you can save (copy) a file to a TFTP server, a file must first exist on the TFTP server. Use the appropriate server commands to create this file and ensure that the filename matches the filename you will copy from the router. Also, ensure that the appropriate server permissions are set so the router can copy to this file. |
Step 5 Create a file on the TFTP server.
Step 6 Use the copy startup-config tftp command. The EXEC command interpreter prompts you for the name or interface processor address of the remote host that is to receive the configuration file. (The prompt might include the name or address of a default file server.)
Step 7 Type the name or interface processor address of the remote host. In the following example, the name of the remote server is servername:
Step 8 The EXEC command interpreter prompts you for the name of the file that will contain the configuration. By default, the system appends -confg to the router's name to create the new filename. Press Return to accept the default filename, or enter a different name for the file before pressing Return. In the following example, the default is accepted:
Step 9 Before the router executes the copy process, it displays the instructions you entered for confirmation. If the instructions are not correct, type n (no) and then press Return to end the process. To accept the instructions, press Return, or press y and then press Return, and the system begins the copy process. In the following example, the default is accepted:
While the router copies the configuration to the remote host, it displays a series of exclamation points (! ! !) or periods (. . .). The !!!! and [ok] indicate that the operation is successful. A series of periods (...) and [timed out] or [failed] indicates a failure, which would probably be due to a network fault or the lack of a writable, readable file on the remote file server.
Step 10 If the display indicates that the process was successful (with the series of exclamation points [! ! !] and [ok]), the copy process is complete. The configuration is safely stored in the temporary file on the remote file server.
If the display indicates that the process failed (with the series of periods [. . .] as shown in the following example:
your configuration was not saved. Repeat the preceding steps, or select a different remote file server and repeat the preceding steps.
Step 11 To further ensure that the configuration file was copied correctly, use the show startup-config command and look at the first line for the configuration file's size. Compare it with the file you copied to the TFTP server. Following is an example. (Take special note of the line preceded by >>.)
After you upload the configuration file, you are prepared to replace the RSP. For more information see the "Removing the RSP8" section. If you are unable to copy the configuration to a remote host successfully, contact your network administrator or see the "Obtaining Technical Assistance" section for instructions on contacting Cisco Systems for technical support.
This completes the procedure for copying the configuration file.
This section describes how to retrieve the saved configuration and copy it to NVRAM. Enter privileged EXEC configuration mode and specify that you will configure the router from the network. The system prompts you for a host name and address, the name of the configuration file stored on the host, and confirmation to reboot using the remote file.
You can access the router through a console terminal attached to the RSP8 console port, or you can Telnet to the router from a remote terminal.
To retrieve the currently running configuration from a remote host, perform the following steps:
|
Note Until you retrieve the previous configuration, the router runs from the default configuration in NVRAM. Therefore, any passwords that were configured on the previous system are not valid until you retrieve the configuration. |
Step 2 Configure an interface port on the router for a connection to a remote host (TFTP server).
Step 3 Use the ping command to verify the connection between the router and the remote host. (See the "Using the ping Command to Ensure Connectivity" section.)
Step 4 At the system prompt, use the copy tftp startup-config command and press Return to enter the configuration mode and specify that you will configure the system from a network device (instead of from the console terminal, which is the default).
Step 5 The system prompts you for the IP address of the host. Type the IP address or name of the remote host (the remote TFTP server to which you originally saved the configuration file).
Step 6 The system prompts you to select a host or network configuration file. The default is host; press Return to accept the default.
Step 7 The system prompts you for the name of the configuration file. The default is to use the name of the router with the suffix -confg (router-confg in the following example). If you specified a different filename when you copied the configuration, type the filename; otherwise, press Return to accept the default.
Step 8 Before the system reloads the new configuration file in NVRAM, it displays the instructions you entered for confirmation. If the instructions are not correct, type n (no), and then press Return to cancel the process. To accept the instructions, press Return, or press y and then press Return. Output similar to the following appears:
While the router retrieves and reloads the configuration file from the remote host, the console display indicates whether or not the operation is successful. A series of exclamation points (!!!!) and [OK] (as shown in the preceding example) indicates that the operation was successful. A series of periods (...) and [timed out] or [failed] indicate a failure (which would probably be due to a network fault or an incorrect server name, address, or filename).
The following is an example of a failed attempt to boot from a remote server:
Step 9 If the display indicates that the process was successful, as shown in Step 8, proceed to the Step 10.
If the display indicates that the process failed, verify the name or address of the remote server and the filename, and repeat the preceding steps. If you are unable to retrieve the configuration file, contact your network administrator or see the "Technical Assistance Center" section for instructions on contacting technical assistance.
Step 10 To ensure that the configuration file was retrieved correctly, use the show startup-config command and look at the first line for the configuration file size. Compare it with the file you retrieved from the TFTP server to confirm that it is correct. Following is an example:
Step 11 To ensure that the startup configuration file stored in NVRAM is the default running configuration file used by the system, use the copy running-config startup-config command as follows:
This completes the procedure for retrieving the saved configuration file.
This section describes how to remove and replace RSP8 DRAM DIMMs.
The default DRAM configuration is 64 MB, residing on up to two DIMMs. The DRAM DIMM sockets are U12 (bank 0) and U15 (bank 1). (See Figure 2 and Table 4.)
|
Caution To prevent system problems, do not use DRAM single in-line memory modules (SIMMs) from an RSP2 in an RSP8. The RSP8 requires DRAM dual in-line memory modules (DIMMs). |
|
Note Do not mix memory sizes. If installing two DIMMs, both DIMMs must be the same size. If your router includes redundant RSPs, the RSPs should have the same memory size. |
|
Note The total number of memory devices per DIMM differs for each manufacturer. The DIMMs in Figure 2 are generic representations of the actual DRAM DIMMs for your RSP. |
Table 4 lists the various configurations of DRAM DIMMs that are available, the number of DIMMs for each configuration, and the DRAM banks they occupy. Note which banks are used, given the combinations of available DIMM sizes and the maximum DRAM you require.
Table 4 RSP8 DRAM DIMM Configurations1
|
|
1 Do not mix memory sizes. If installing two DIMMs, both DIMMs must be the same size. 2 The RSP8 default DRAM configuration is 64 MB. The RSP8 ships with either two 32-MB DIMMS or one 64-MB DIMM. |
|
Caution To prevent system and memory problems when you install DRAM, the RSP8 DRAM DIMMS must be 3.3V devices. Do not attempt to install higher-voltage devices in the RSP8 DIMM sockets. Handle the DIMM by the card edges only, and avoid touching the memory module, pins, or traces (the metal fingers along the connector edge of the DIMM). (See Figure 13.) |
|
Note Use only SDRAM DIMMs from Cisco Systems. A Cisco manufacturing part number appears on each SDRAM DIMM. |
This section discusses the procedure for removing DIMMs from your RSP8.
Use this procedure to remove the existing DIMMs:
Step 2 Place the RSP8 on an antistatic mat or pad and ensure that you are wearing an antistatic device, such as a wrist strap.
Step 3 Position the RSP8 so that the faceplate is toward you and the bus connectors are away from you—this position is shown in Figure 2.
Step 4 Locate the DRAM DIMMs on the RSP8. The DIMMs occupy U12 (bank 0) and U15 (bank 1). (See Figure 2.)
Step 5 Open the DIMM socket release levers on the DIMM to release the DIMM from the socket. (See Figure 14.) The DIMM is under tension in the socket; therefore, the DIMM might be released from the socket with some force.
Step 6 With the DIMM socket tabs open, grasp the ends of the DIMM between your thumbs and forefingers and pull the DIMM completely out of the socket. (See Figure 15.)
Step 7 Place the removed DIMM on an antistatic mat, and store it in an antistatic container to protect it from ESD damage.
Step 8 Repeat Step 4 through Step 7 for the remaining DIMM, if required for your upgrade.
This completes the DIMM removal procedure. Proceed to the next section to install the new DIMMs.
This section discusses the procedure for installing DIMMs on your RSP.
Use this procedure to install new DIMMs.
|
Note Do not mix memory sizes. If installing two DIMMs, both DIMMs must be the same size. |
Step 2 Hold the DIMM between your thumbs and forefingers. (See Figure 13.)
Step 3 Insert the connector edge of the DIMM straight into the socket.
|
Caution When inserting the DIMM, use firm but not excessive pressure. If you damage a socket, you will have to return the RSP to the factory for repair. |
Step 4 Gently push the DIMM into the socket until the socket release levers close over the ends of the DIMM. (See Figure 16.) If necessary, rock the DIMM gently back and forth to seat it properly.
Step 5 Check to see if the DIMM is seated properly. If the DIMM appears misaligned, carefully remove it and reseat it in the socket. Push the DIMM firmly back into the socket until first one and then the other socket release lever moves into place.
Step 6 Repeat Step 1 through Step 5 above if you are replacing more than one DIMM.
This completes the procedure for installing DRAM DIMMs. Proceed to the following section to check the installation.
This section describes how you would verify the memory upgrade.
If after several attempts the system fails to restart properly, contact TAC (see the "Technical Assistance Center" section), or a service representative for assistance. Before you call, make note of any error messages, unusual LED states, or any other indications that might help solve the problem. The time required for the system to initialize might vary with different router configurations and DRAM configurations. Routers with 256 MB of DRAM might take longer to boot than those with less DRAM.
This completes the RSP memory upgrade verification.
An overview of the procedure for recovering a lost password follows:
|
Note A key to recovering a lost password is to set the configuration register so that the contents of NVRAM are ignored (0x0040), allowing you to see your password. |
To recover a lost password, follow these steps:
Step 2 Configure the terminal to operate at 9600 baud, 8 data bits, no parity, 2 stop bits (or to whatever settings the router is set).
Step 3 Use the show version command to display the existing configuration register value. Note this value for later use in Step 13.
Step 4 If the Break function is disabled, power cycle the router. (To power cycle, turn off the router, wait 5 seconds, and then turn it on again.) If the Break function is enabled on the router, press Break or send a break (^[) and then proceed to Step 5.
Step 5 Within 5 seconds of turning on the router, press Break. This action causes the terminal to display the bootstrap program prompt:
Step 6 Set the configuration register to ignore the configuration file information as follows:
Step 7 Initialize the router using the i command as follows:
The router power cycles, the configuration register is set to ignore the configuration file, and the router boots the boot system image and prompts you with the system configuration dialog as follows:
Step 8 Type no in response to the system configuration dialog prompts until the following system message is displayed:
Step 9 Press Return. After some interface information, the prompt appears as follows:
Step 10 Use the enable command to enter privileged EXEC configuration mode. The prompt changes to the following:
Step 11 Use the show configuration privileged EXEC command to display the enable password in the configuration file.
Step 12 At the privileged EXEC prompt, use the configure terminal command to enter global configuration mode. You are prompted as follows:
Step 13 Using the config-register 0xvalue command, change the configuration register value back to its original value (noted in Step 3) or change it to a value of 0x0102 (factory default).
Step 14 Exit global configuration mode using Ctrl-Z or by typing end.
Step 15 Reboot the router and enable it using the recovered password.
This completes the procedure for recovering a lost password.
The following sections include important reference information:
The console port on the RSP8 is an EIA/TIA-232, DCE, DB-25 receptacle. Both Data Set Ready (DSR) and Data Carrier Detect (DCD) are active when the system is running. The Request To Send (RTS) signal tracks the state of the Clear To Send (CTS) input. The console port does not support modem control or hardware flow control. The console port requires a straight-through EIA/TIA-232 cable. Table 5 lists the signals used on this port.
The auxiliary port on the RSP8 is an EIA/TIA-232, DTE, DB-25 plug to which you can attach a CSU or DSU or other equipment in order to access the router from the network. The asynchronous auxiliary port supports hardware flow control and modem control. Table 6 lists the signals used on this port.
The console and auxiliary Y-cables allow you to simultaneously connect the console ports or auxiliary ports on two RSPs (configured as system active and slave in RSP slots 2 and 3 in the Cisco 7507 and Cisco 7507-MX, and RSP slots 6 and 7 in the Cisco 7513 and Cisco 7513-MX) to one console terminal or external auxiliary device (such as a modem).
The two Y-cables (Product Number CAB-RSP8CON=, shown in Figure 6, and Product Number CAB-RSP8AUX=, shown in Figure 7) ship with the router and are available as spare parts. The console Y-cable pinout is listed in Table 7, and the auxiliary Y-cable pinout is listed in Table 8.
Table 7 Console Y-Cable Signals (Product Number CAB-RSP8CON=)
|
Table 8 Auxiliary Y-Cable Signals (Product Number CAB-RSP8AUX=)
|
Settings for the 16-bit software configuration register are written into the NVRAM. Following are some reasons for changing the software configuration register settings:
|
Note The Break function (software configuration register bit 8) when enabled allows you to send a Break signal to the router during a system (re)boot. This stops the boot process and places the router into ROM monitor mode. You can activate the Break function by using a dedicated Break key function on the keyboard, or by entering the Ctrl-[ (left square bracket) key combination. |
If the router finds no boot system commands, it uses the configuration register value to form a filename from which to boot a default system image stored on a network server. (See Table 11.)
Table 9 lists the meaning of each of the software configuration memory bits, and Table 10 defines the boot field.
|
Caution To avoid confusion and possibly halting the router, remember that valid configuration register settings might be combinations of settings and not just the individual settings listed in Table 9. For example, the factory default value of 0x0102 is a combination of settings. |
Table 9 Software Configuration Register Bit Meanings
|
|
1 The factory default value for the configuration register is 0x0102. This value is a combination of the following: bit 8 = 0x0100 and bits 00 through 03 = 0x0001 (see Table 11). 2 OEM = original equipment manufacturer |
Table 10 Explanation of Boot Field (Software Configuration Register Bits 00 to 0F)
|
To change the configuration register while running the system software, follow these steps:
Step 2 To enter global configuration mode, use the configure terminal command. You are prompted for further commands, as shown in the following example:
Step 3 To set the contents of the configuration register, use the config-register 0xvalue configuration command, where value is a hexadecimal number preceded by 0x (see Table 10), as shown in the following example:
Step 4 Exit global configuration mode using Ctrl-Z or by typing end.The new configuration register settings are saved to memory; however, the new settings do not take effect until the system software is reloaded when you reboot the router.
Step 5 To display the configuration register value currently in effect and the value that will be used at the next reload, enter the show version privileged EXEC command. The value is displayed on the last line of the screen display, as in the following example:
Step 6 Reboot the router. The new value takes effect. Configuration register changes take effect only when the system reloads, such as when you issue a reload command from the console.
This completes the procedure to change the configuration register while running the system software.
The lowest four bits of the software configuration register (bits 3, 2, 1, and 0) form the boot field. (See Table 10.) The boot field specifies a number in binary form. If you set the boot field value to 0, you must boot the operating system manually by entering the b command at the bootstrap prompt (>), as follows:
Definitions of the various b command options follow:
If you set the boot field value to 0x2 through 0xF and there is a valid boot system command stored in the configuration file, then the router boots the system software as directed by that value. If there is no boot system command, the router forms a default boot filename for booting from a network server. (See Table 11 for the format of these default filenames.)
In the following example, the software configuration register is set to boot the router from onboard Flash memory and to ignore the Break function at the next reboot of the router:
The server creates a default boot filename as part of the automatic configuration processes. To form the boot filename, the server starts with the name cisco and adds the octal equivalent of the boot field number, a hyphen, and the processor-type name.
Table 11 lists the default boot filenames or actions for the processor.
|
Note A boot system configuration command in the router configuration in NVRAM overrides the default netboot filename. |
Bit 8 controls the console Break key. Setting bit 8 (the factory default) causes the processor to ignore the console Break key. Clearing bit 8 causes the processor to interpret the Break key as a command to force the system into the bootstrap monitor, thereby halting normal operation. Regardless of the setting of the break enable bit, a break causes a return to the ROM monitor during the first few seconds (approximately 5 seconds) of booting.
Bit 9 is unused. Bit 10 controls the host portion of the IP broadcast address. Setting bit 10 causes the processor to use all zeros; clearing bit 10 (the factory default) causes the processor to use all ones. Bit 10 interacts with bit 14, which controls the network and subnet portions of the broadcast address. Table 12 shows the combined effect of bits 10 and 14.
Table 12 Configuration Register Settings for Broadcast Address Destination
|
Bits 11 and 12 in the configuration register determine the baud rate of the console terminal. Table 13 shows the bit settings for the four available baud rates. (The factory-set default baud rate is 9600.)
Bit 13 determines the server response to a bootload failure. Setting bit 13 causes the server to load operating software from Flash memory after five unsuccessful attempts to load a boot file from the network. Clearing bit 13 causes the server to continue attempting to load a boot file from the network indefinitely. By factory default, bit 13 is cleared to 0.
To enable a boot from Flash memory, set configuration register bits 3, 2, 1, and 0 to a value between 2 and 15 in conjunction with the boot system flash device:filename configuration command, where device is bootflash:, slot0:, or slot1:, and filename is the name of the file from which you want to boot the system.
To enter global configuration mode while in the system software image and specify a Flash memory filename from which to boot, use the configure terminal privileged EXEC configuration command at the enable prompt, as follows:
To disable the Break function and enable the boot system flash device:filename command, use the config-register command with the value shown in the following example:
To enable a boot from the Flash Disk, set configuration register bits 3, 2, 1, and 0 to a value between 2 and 15 in conjunction with the boot system [disk0: | disk1:]filename configuration command. This section includes only descriptions of boot commands specific to the Flash Disk. (You can use either the slotn: argument or the diskn: argument for boot commands.)
Following are definitions of the various Flash Disk-related boot commands:
boot system flash disk0:—Boots the first file in the Flash Disk in slot 0.
boot system flash disk1:—Boots the first file in the Flash Disk in slot 1.
boot system flash disk0:herfile—Boots the file named herfile from the Flash Disk in slot 0.
boot system flash disk1:hisfile—Boots the file named hisfile from the Flash Disk in slot 1.
|
Note As you use boot commands, pay attention to how you use the Spacebar, which influences the way your system interprets the commands. Also, be sure that you define the entire path to a file as you type the boot commands; otherwise, the system might not be able to find the file. |
For example, notice the difference in the following correct and incorrect commands:
Based on the preceding correct command, the system boots the file specified (myfile).
Based on the preceding incorrect command, the system finds the filename field blank because there is a space after disk0:. In this case, the system ignores the filename argument and boots the first file on the Flash Disk, which might not be the file called myfile.
Use the following procedure to enable booting the file myfile from a Flash Disk:
Step 2 Enable the boot system flash disk0:myfile command using the config-register command with the hexadecimal value shown in the following example:
The config-reg 0x2102 command, with the hexadecimal value 0x2102, results in the following:
Step 3 Press Ctrl-Z or type end to exit global configuration mode:
Step 4 Save the new configuration to NVRAM by using the copy running-config startup-config command as follows:
The Flash memory (PC Card) slots on the front panel of the RSP8 support PC Card-based Flash memory media for your system. You can use this Flash memory to store and run IOS software images, or as a file server for other routers to access as clients. The Flash memory media is either Flash memory cards or Flash Disks.
|
Note A complete discussion of PC Card-based Flash memory is beyond the scope of this publication. For detailed information on Flash memory cards, refer to Flash Memory Card Installation Instructions (Part Number: DOC-782083=). Or, for detailed information on Flash Disk, refer to Using the Flash Disk (Part Number DOC-785819=). |
These sections explain how to obtain documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at this URL:
Translated documentation is available at this URL:
http://www.cisco.com/public/countries_languages.shtml
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
You can order Cisco documentation in these ways:
http://www.cisco.com/cgi-bin/order/order_root.pl
http://www.cisco.com/go/subscription
You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.
You can e-mail your comments to bug-doc@cisco.com.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you with these tasks:
If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:
The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Cisco TAC inquiries are categorized according to the urgency of the issue:
The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
http://www.cisco.com/register/
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
This document is to be used in conjunction with the appropriate Quick Start Guide that shipped with your router and the documents listed in the "Related Documentation" section.
Copyright © 2003 Cisco Systems, Inc. All rights reserved.
Posted: Thu Jul 31 07:28:31 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
