Cisco 7500 Series Routers

Table of Contents

Route Switch Processor (RSP2)
Installation and Configuration Guide

Product Numbers: RSP2, RSP=, ROMMON-RSP2, MEM-RSP-8M=, MEM-RSP-16M=, MEM-RSP-24M=, MEM-RSP-32M=, MEM-RSP-64M=, MEM-RSP-128M=, MEM-RSP-FLC8M=, MEM-RSP-FLC16M=, MEM-RSP-FLC20M=, MEM-RSP-FLC32M=

Customer Order Number: DOC-782026=

This document describes the Route Switch Processor (RSP2), the default system processor for the Cisco 7505, Cisco 7507 and Cisco 7513 routers.

Caution   We strongly recommend that you do not use the RSP2 in the Cisco 7507-MX, and Cisco 7513-MX routers. The Cisco 7507-MX and Cisco 7513-MX routers ship by default with an RSP8.

The RSP2 supports the high system availability (HSA) feature, which allows two RSP2s, or an RSP4/4+ and an RSP2, to be used in a Cisco 7507 and Cisco 7513 routers. See the "Configuring High System Availability" section for more information on HSA.

The RSP2 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.

With HA or HSA enabled, the RSP2 supports online insertion and removal (OIR).

Document Contents

This document contains the following sections:

Related Documentation

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

Product Description

This section discusses the following topics:

The RSP2 supports the VIP2 and the VIP4 in the Cisco 7505, Cisco 7507, and the Cisco 7513. (See Figure 1 and Figure 2.)

The RSP2 supports the VIP2 and VIP4 in the Cisco 7000 series routers, and the VIP2, VIP4, and the VIP6-80 in the Cisco 7505, Cisco 7507, and the Cisco 7513 routers. The RSP2 is not supported on the Cisco 7507-MX or the Cisco 7513-MX routers. The RSP2 is not available as an upgrade from an RSP700, or an RSP1. You cannot upgrade to an RSP4/4+, RSP8, or RSP16 from the RSP2.

The RSP2 contains the central processing unit (CPU) and most of the memory components for the router. The Cisco IOS software images reside in Flash memory, which is located on the RSP2:

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 RSP2 Flash memory, without having to remove and replace read-only memory (ROM) devices.

The RSP2 also contains:

In addition to running the system software from DRAM, the RSP2 contains and executes the following management functions that control the system:

The high-speed switching section of the RSP2 communicates with and controls the interface processors on the high-speed CyBus. This switching section decides the destination of a packet and switches it based on that decision. The RSP2 uses a 16-million-instructions-per-second (mips) processor to provide high-speed, autonomous switching and routing.

The RSP2 installs in the following slots on your Cisco 7000 or Cisco 7500 series router:

Figure 1   RSP2 (Front-Panel View)

Note   A bank of hardware (Media Access Control [MAC]-layer) addresses for the interface ports is contained in an NVRAM device on the router backplane.

CPU

The CPU used in the RSP2 is a Mips R4600 Reduced Instruction Set Computing (RISC) processor with an external clock speed of 50 MHz, and an internal clock speed of 100 MHz.

Memory Components

Table 1 shows the memory components on the RSP2.

DRAM

DRAM stores routing tables, protocols, and network accounting applications and runs the Cisco IOS software. The standard (default) RSP2 configuration is 32 MB of DRAM, with up to 128 MB available through SIMM upgrades. DRAM is contained in up to four SIMM sockets: U21 and U33 (also called bank 0) and U12 and U4 (also called bank 1). When upgrading DRAM, you must use SIMMs from Cisco. (Also see the "Compatibility Requirements" section.)

Caution   To prevent memory problems, DRAM SIMMS must be 3.3-volt (V) devices. Do not attempt to install higher-voltage devices in the RSP2 SIMM sockets.

For RSP2 DRAM upgrade procedures, refer to the "Replacing and Upgrading DRAM SIMMs" section.

NVRAM

The system configuration, software configuration register settings, and environmental monitoring logs are contained in the 128-KB NVRAM, which is backed up with built-in lithium batteries that retain the contents for a minimum of 5 years. When replacing an RSP2, be sure to back up your configuration to a remote server so you can retrieve it later.

Caution   Before you replace an RSP2 in a system with one RSP2, back up the running configuration to a 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 RSP2—and you will have to reenter the entire configuration manually. For instructions on how to save the configuration file, see the "Saving and Retrieving the Configuration File" section. This procedure is not necessary if you are temporarily removing an RSP2; lithium batteries retain the configuration in memory until you replace the RSP2 in the system.

Flash Memory

The Flash memory card for the RSP2 is an 16- or 20- Flash memory card, which conforms with the PC Card normally Personal Computer Memory Card International Association (PCMCIA) format.

Both the onboard 8-MB and the 16- or 20-MB Flash memory card (PCMCIA cards) 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 stored images. 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.

Caution   To prevent system problems, use Flash memory cards in the RSP2 that were formatted on an RP, RSP1, or RSP7000 running Cisco IOS Release 11.1(8)CA1 or a later release of 11.1 CA1. You cannot use Flash memory cards on the RSP2 (as storage or boot devices) that were formatted on an RP, RSP1, or RSP7000 using a Cisco IOS boot image earlier than Cisco IOS Release 11.1(8)CA1.

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/pcgi-bin/Support/CompNav/Index.pl.

LEDs

Table 2 describes the operation of the LEDs found on the RSP2:

The Active/Standby switch has been deactivated in software. The reset button boots the system.

PC Card Slots

The RSP2 has two PC Card slots available. Either slot can support a Flash memory card or an input/output (I/O) device. 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 that are commercially available are supported, and not all I/O devices are supported.

Note   Other Flash memory card limitations might apply. For additional Flash memory information, refer to the Flash memory configuration notes listed in the "Related Documentation" section.

Serial Ports

Two asynchronous serial ports on the RSP2, 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.

Specifications

Table 3 lists the physical specifications for the RSP2:

System Software

The Cisco 7505, Cisco 7507, and Cisco 7513 routers support downloadable system software and microcode for most Cisco IOS software 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. An erasable programmable read-only memory (EPROM) device contains the latest microcode version, in compressed form, for each interface processor.

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 RSP2 in the form of a single in-line memory module (SIMM), on Flash memory cards that insert in the two PC Card slots (slot 0 and slot 1) on the front of the RSP2. (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 RSP2 Flash memory.

Although no monitoring of voltage or temperature is done by the RSP2, a comparator device ensures that voltage is within the normal operating ranges, and three temperature sensors on the RSP2 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 RSP2 uses a software-controlled configuration register, so you do not have to remove the RSP2 to configure jumpers. There are no user-configurable jumpers on the RSP2.

Note   The exception to this is CIP microcode, which, as of Cisco IOS Release 11.1(1), is unbundled from the Cisco IOS software image bundle, and is available in a separate bundle on floppy disks, a TFTP server, Cisco.com, or PC Card-based Flash memory media.

For the latest software release information, refer to the hardware/software compatibility matrix at http://www.cisco.com/pcgi-bin/front.x/Support/HWSWmatrix/hwswmatrix.cgi.

Installation Prerequisites

Before beginning the installation procedures, review the following sections to ensure awareness of the appropriate regulatory and safety requirements, and to ensure that your RSP2 hardware functions properly with compatible components:

Safety Guidelines

This section lists safety guidelines 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.

Safety Guidelines

Following are safety guidelines that you should follow when working with any equipment that connects to electrical power or telephone wiring.

Safety Warnings

Warning This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. To see translations of the warnings that appear in this publication, refer to the Regulatory Compliance and Safety Information document that accompanied this device. Waarschuwing Dit waarschuwingssymbool betekent gevaar. U verkeert in een situatie die lichamelijk letsel kan veroorzaken. Voordat u aan enige apparatuur gaat werken, dient u zich bewust te zijn van de bij elektrische schakelingen betrokken risico's en dient u op de hoogte te zijn van standaard maatregelen om ongelukken te voorkomen. Voor vertalingen van de waarschuwingen die in deze publicatie verschijnen, kunt u het document Regulatory Compliance and Safety Information (Informatie over naleving van veiligheids- en andere voorschriften) raadplegen dat bij dit toestel is ingesloten. Varoitus Tämä varoitusmerkki merkitsee vaaraa. Olet tilanteessa, joka voi johtaa ruumiinvammaan. Ennen kuin työskentelet minkään laitteiston parissa, ota selvää sähkökytkentöihin liittyvistä vaaroista ja tavanomaisista onnettomuuksien ehkäisykeinoista. Tässä julkaisussa esiintyvien varoitusten käännökset löydät laitteen mukana olevasta Regulatory Compliance and Safety Information -kirjasesta (määräysten noudattaminen ja tietoa turvallisuudesta). Attention Ce symbole d'avertissement indique un danger. Vous vous trouvez dans une situation pouvant causer des blessures ou des dommages corporels. Avant de travailler sur un équipement, soyez conscient des dangers posés par les circuits électriques et familiarisez-vous avec les procédures couramment utilisées pour éviter les accidents. Pour prendre connaissance des traductions d'avertissements figurant dans cette publication, consultez le document Regulatory Compliance and Safety Information (Conformité aux règlements et consignes de sécurité) qui accompagne cet appareil. Warnung Dieses Warnsymbol bedeutet Gefahr. Sie befinden sich in einer Situation, die zu einer Körperverletzung führen könnte. Bevor Sie mit der Arbeit an irgendeinem Gerät beginnen, seien Sie sich der mit elektrischen Stromkreisen verbundenen Gefahren und der Standardpraktiken zur Vermeidung von Unfällen bewußt. Übersetzungen der in dieser Veröffentlichung enthaltenen Warnhinweise finden Sie im Dokument Regulatory Compliance and Safety Information (Informationen zu behördlichen Vorschriften und Sicherheit), das zusammen mit diesem Gerät geliefert wurde. Avvertenza Questo simbolo di avvertenza indica un pericolo. La situazione potrebbe causare infortuni alle persone. Prima di lavorare su qualsiasi apparecchiatura, occorre conoscere i pericoli relativi ai circuiti elettrici ed essere al corrente delle pratiche standard per la prevenzione di incidenti. La traduzione delle avvertenze riportate in questa pubblicazione si trova nel documento Regulatory Compliance and Safety Information (Conformità alle norme e informazioni sulla sicurezza) che accompagna questo dispositivo. Advarsel Dette varselsymbolet betyr fare. Du befinner deg i en situasjon som kan føre til personskade. Før du utfører arbeid på utstyr, må du vare oppmerksom på de faremomentene som elektriske kretser innebærer, samt gjøre deg kjent med vanlig praksis når det gjelder å unngå ulykker. Hvis du vil se oversettelser av de advarslene som finnes i denne publikasjonen, kan du se i dokumentet Regulatory Compliance and Safety Information (Overholdelse av forskrifter og sikkerhetsinformasjon) som ble levert med denne enheten. Aviso Este símbolo de aviso indica perigo. Encontra-se numa situação que lhe poderá causar danos físicos. Antes de começar a trabalhar com qualquer equipamento, familiarize-se com os perigos relacionados com circuitos eléctricos, e com quaisquer práticas comuns que possam prevenir possíveis acidentes. Para ver as traduções dos avisos que constam desta publicação, consulte o documento Regulatory Compliance and Safety Information (Informação de Segurança e Disposições Reguladoras) que acompanha este dispositivo. ¡Advertencia! Este símbolo de aviso significa peligro. Existe riesgo para su integridad física. Antes de manipular cualquier equipo, considerar los riesgos que entraña la corriente eléctrica y familiarizarse con los procedimientos estándar de prevención de accidentes. Para ver una traducción de las advertencias que aparecen en esta publicación, consultar el documento titulado Regulatory Compliance and Safety Information (Información sobre seguridad y conformidad con las disposiciones reglamentarias) que se acompaña con este dispositivo. Varning! Denna varningssymbol signalerar fara. Du befinner dig i en situation som kan leda till personskada. Innan du utför arbete på någon utrustning måste du vara medveten om farorna med elkretsar och känna till vanligt förfarande för att förebygga skador. Se förklaringar av de varningar som förkommer i denna publikation i dokumentet Regulatory Compliance and Safety Information (Efterrättelse av föreskrifter och säkerhetsinformation), vilket medföljer denna anordning.

Electrical Equipment Guidelines

Follow these basic guidelines when working with any electrical equipment:

Telephone Wiring Guidelines

Use the following guidelines when working with any equipment that is connected to telephone wiring or to other network cabling:

Preventing Electrostatic Discharge Damage

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

Compatibility Requirements

This section describes important compatibility requirements for the RSP2.

Chassis Slot and DRAM Requirements

Following are chassis slot and DRAM requirements for ensuring RSP2 compatibility.

Memory Requirements

Flash memory cards and DRAM SIMMs must meet the following requirements:

To check the boot ROM (also called the system bootstrap) version currently running on your RSP2, use the show version command and check the boot ROM version number as follows:

Software Prerequisites

The minimum supported Cisco IOS release compatible with the RSP2 is 10.3(6) or a later release of Cisco IOS release 10.3. For the latest compatible software releases, refer to the software advisor at http://www.cisco.com/pcgi-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 Cisco IOS Release 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 RSP2 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 "Obtaining Technical Assistance" section on page 86.)

Hardware Prerequisites

Your router configuration, protocols and features might require more than the 32 MB of DRAM that is shipped with the RSP2. To upgrade DRAM, see the "Software Configuration Register Settings" 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, or RSP1, you must reformat the Flash memory card. Flash memory cards formatted on any of these processors do not work properly in an RSP2. You must first reformat it on your RSP2 system. Refer to Flash Memory Card Installation Instructions (part number DOC-782083=) for instructions on reformatting Flash memory.

Microcode Requirements

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. The exception to this is CIP microcode, which as of Cisco IOS Release 11.1(1), is unbundled from the IOS software image bundle, and is available in a separate bundle on floppy disks, a TFTP server, CCO, or Flash memory cards.

Installing the RSP2

The following sections describe the procedures for installing or replacing an RSP2. Ensure that your system meets the minimum software, hardware, and microcode requirements described in the following: "Software Prerequisites" section, "Hardware Prerequisites" section, and "Microcode Requirements" section. Proceed to the "Removing the RSP2" section for instructions on removing the RSP2, and then to the "Replacing the RSP2" section for installation instructions. After the new RSP2 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 RSP2 from a system while the system is operating will cause the system to crash. Consider this before removing an RSP2 while the system is operating. To ensure that the standby RSP2 operates properly with the full system configuration should the active RSP2 ever fail, the standby RSP2 must have the same DRAM and the same (or higher) Flash memory capacity as the active RSP2. See the "Memory Components" section for RSP2 memory component requirements.

Note   The carriers on processor modules have EMI fences for EMI shielding; therefore, they fit very tightly in the chassis slots. To ensure that you can properly remove or install an RSP2 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 RSP2 in RSP slot 7 (and fasten its captive installation screws as appropriate), and then reinstall the interface processor in slot 8.

List of Parts and Tools

You need some or all of the following parts and tools to remove and replace an RSP2 or to upgrade DRAM. If you need additional equipment, contact a customer service representative for ordering information.

Caution   To prevent memory problems, DRAM SIMMs must be 3.3-volt (V) devices. Do not attempt to install higher-voltage devices in the RSP2 SIMM sockets.

Removing the RSP2

When you remove or install the RSP2, be sure to use the ejector levers, which help to ensure that the RSP2 is fully inserted in the backplane or fully dislodged from it. An RSP2 that is only partially connected to the backplane can halt the system unless a second RSP2 is installed.

Figure 3 shows a detail of the ejector lever mechanism that is appropriate for the router. When you simultaneously push the ejector levers inward (toward the carrier handle), the levers push the RSP2 into the slot and ensure that the board connectors are fully seated in the backplane. Follow these steps to remove the RSP2:

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 RSP2, disconnect any devices that are attached to the console or auxiliary ports. If you are removing the RSP2 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 ejectors and simultaneously pull them both outward, away from the carrier handle (in the opposite direction from that shown in Figure 3c) to release the carrier from the slot and to dislodge the RSP2 from the backplane.

Step 6   Grasp the handle of the RSP2 with one hand and pull the RSP2 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 RSP2 on an antistatic mat or foam. If you plan to return the RSP2 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 RSP2 before performing any maintenance on the RSP2 that might create an ESD hazard.

This completes the removal procedure. If you removed the RSP2 to replace SIMMs, proceed to the "Software Configuration Register Settings" section. If you are replacing the RSP2, proceed to the next section to install the new RSP2.

Replacing the RSP2

The RSP2 is keyed for installation only in an RSP slot. By default, the system active is the RSP that occupies the first RSP slot in the router: slot 2 in the Cisco 7507, and slot 6 in the Cisco 7513. Follow these steps to install an RSP2:

Step 2   Place the back of the RSP2 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 RSP2 in one of the two RSP slots on the router. The slots are keyed for correct installation. Forcing the RSP2 into a different slot can damage the backplane and the RSP2.

Step 3   While keeping the RSP2 parallel to the backplane, carefully slide the carrier into the slot until the RSP2 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 RSP2. (See Figure 3a.)

Step 6   Use a screwdriver to tighten the two captive installation screws on the RSP2 faceplate to prevent the RSP2 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 RSP2, or if you are installing a new RSP2, connect the console terminal to the console port. (See the "Connecting the Console Terminal" section.)

Step 8   Ensure that a console terminal is connected (see the "Connecting the 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 RSP2.

Connecting the Console Terminal

The system console port on the RSP2 is a DCE DB-25 receptacle for connecting a console terminal, which you need to configure in order to communicate with your system. The console port is located on the RSP2 to the right of 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 RSP2, 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.)

Connecting to the Auxiliary Port

The auxiliary port on the RSP2 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 above the console port on the RSP2 and is labeled AUX. An example of a modem connection is shown in Figure 5.

Using the Y-Cables for Console and Auxiliary Connections

For systems with two RSP2s installed and the HSA or 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 RSP2 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.

Restarting the System

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 RSP2 is installed and functioning properly:

Step 2   Observe the RSP2 LEDs. While the system initializes, the CPU halt LED on the RSP2 stays on. It goes off when the boot process is complete. As the RSP2 initializes each interface processor, the status LEDs on each interface processor go on and off in irregular sequence.

Step 3   For a Cisco 7507 or Cisco 7513 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 RSP2 (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 RSP2 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 RSP2 installed (and HSA or HA configured), use the show version command to verify that the standby RSP2 is recognized by the system. Following is a sample from a Cisco 7513:

(Note that this could also be "slot 6" depending on which RSP2 is configured as the slave 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 RSP2 installed and want to use the HSA or the HA features), the installation is complete. If you replaced the RSP2 and saved your configuration file to a remote server before doing so, see the "Retrieving the Configuration File" section. If you replaced the RSP2 and did not save the configuration, use the configure command or the setup command 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 goes on and remains 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 on the Documentation CD-ROM or as printed documents.

If you have a second RSP2 installed, you must configure the HSA (or HA, if you prefer) features for your Cisco 7507 or Cisco 7513 router. Read the following caution, and then proceed to the following section, "Configuring High System Availability" section.

Caution   When you install a second RSP2 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 may result in an unconfigured standby RSP2 (or RSP4/4+) taking over the router when the active fails, rendering the network inoperable.

This completes the procedure for restarting the system.

Configuring the Router for a Single RSP2

If you have a single RSP2, 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 RSP2 (or an RSP2 and an RSP4/4+), and you are using a Cisco 7507 router or a Cisco 7513 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).

Using the EXEC Command Interpreter

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 level ends with a pound sign (#) instead of an angle bracket (>).

At the console terminal, enter the privileged level as follows:

Step 2   Enter the password (the password is case sensitive). For security purposes, the password is not displayed.

Step 3   When you enter 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 at http://www.cisco.com. Refer to the Software Advisor at http://www.cisco.com/pcgi-bin/Support/CompNav/Index.pl for additional information.

For troubleshooting information, refer to the "Troubleshooting the Installation" section.

Configuring High System Availability

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 RSP2s, or an RSP2 and an RSP4/4+ (one designated as the "active" or "master" and the other as the "standby" or "slave") are installed in a router and the active RSP2 fails. The standby RSP2 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 RSP2 in the event of an active RSP2 failure, the standby RSP2 should have the same boot image, the same ROM monitor, and the same DRAM configuration as the active RSP2.

Note   An RSP2 can interoperate with another RSP2, or with an RSP4/4+. It cannot interoperate with an RSP1, an RSP8, or an RSP16. In the following text, you can substitute references to two RSP2s with an RSP2 and an RSP4/4+.

When two new RSP2s (or an RSP2 and an RSP4/4+) are installed at the same time, the RSP that occupies the first even RSP slot on the router is the active (normally the RSP4/4+ if the RSP2 is used in conjunction with the RSP4/4+), 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 with RSP2 on the following routers: Cisco 7507, and Cisco 7513. 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 Configuration Fundamentals Configuration Guide and the Configuration Fundamentals Command Reference publications, which are available online, on the Cisco Documentation CD-ROM, or as printed copies.

HSA Active and Standby Operation

During HSA operation, the active RSP2 card functions as if it were a single processor, controlling all functions of the router. The standby RSP2 card does nothing but actively monitor the active RSP2 for failure.

When the standby RSP2 detects a nonfunctional active RSP2, the standby resets itself and takes part in active-standby arbitration. Active-standby arbitration is a ROM monitor process that determines which RSP2 card is the active and which is the standby upon startup (or reboot).

If a system crash causes the active RSP2 to fail, the standby RSP2 becomes the new active RSP2 and uses its own system image and configuration file to reboot the router. The failed RSP2 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 RSP2 while the system is operating might cause the system to crash; however, the system reloads with the standby RSP2 as the new active. To prevent any system problems, do not remove the active RSP2 while the system is operating.

HSA Implementation Methods

Common HSA uses are as follows:

You can also use HSA for advanced implementations. For example, you can configure the RSP2 cards with the following:

HSA System Requirements

To configure HSA operation with the RSP2, you must have:

Caution   The HSA feature works with two RSP2s, or with one RSP2 and one RSP4/4+. The RSP2 cannot be used in combination with the RSP1, RSP8 or RSP16 when utilizing the HSA feature.

Configuring HSA Operation Task List

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.

After determining how you intend to use HSA, 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.

Specifying the Default Standby RSP2

Your view of the environment is always from the active RSP2 perspective, you must define a default standby RSP2. The router uses the default standby information when booting.

To define the default standby RSP2, use the following commands in Table 4 in privileged EXEC mode:

Upon the next system reboot, the above changes take effect (if both RSP2 cards are operational). Thus, the specified default standby becomes the standby RSP2 card. The other RSP2 card takes over control of the system and controls all functions of the router.

If you do not specifically define the default standby RSP2, the RSP2 card located in the higher number processor slot is the default standby. On the Cisco 7507, processor slot 3 contains the default standby RSP. On the Cisco 7513, processor slot 7 contains the default standby RSP.

The following example sets the default standby RSP2 to processor slot 2 on a Cisco 7507:

Ensuring That Both RSPs Contain the Same Configuration File

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 in Table 5, in privileged EXEC mode:

Table 5   Ensuring that Both RSPs Have the Same Configuration File

The following example turns on automatic configuration file synchronization:

Ensuring that Both RSPs Contain the Same System Image

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 in Table 6 in privileged EXEC mode:

Note   Standard 16-, and 20-MB Flash memory cards are supported with the RSP2 (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- and 128-MB Flash Disks are supported with the RSP2. 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.

Ensuring that Both RSPs Contain the Same Microcode Image

To ensure that both RSPs have the same microcode images, use the following commands in Table 7 in privileged EXEC 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 RSP2 has a copy of the same FSIP microcode in the same location.

Specifying Different Startup Images for the Active and the Standby RSPs

For software error protection, the RSPs should have different system images.

When the factory sends you a new router with two RSP2s, 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 two separate system images. Each RSP uses its own image to boot the router when it becomes the active.

To specify different startup images for the active and the standby RSPs, use the following commands in Table 8 in privileged EXEC mode:

Upgrading to a New Software Version Example

Note   The following examples show systems with two RSP2s.

In the following example, assume the following:

Figure 8 illustrates the software error protection configuration for this sample scenario. The configuration commands for this configuration follow the figure.

Step 2   Now view the standby software image location and version:

Step 3   Because you want to run the Cisco IOS Release 12.1(12)E system image on one RSP and the Cisco IOS Release 12.1(13)E system image on the other RSP, copy the Cisco IOS Release 12.1(13)E system image to the active's slot 0:

Step 4   Enter global configuration mode and configure the system to boot first from a Cisco IOS Release 12.1(13)E system image and then from a Cisco IOS Release 12.1(12)E 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-k-mx11.2 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-k-mx11.2 to boot. Because that image does not exist in that location, the slot 7 RSP looks for the system image file rsp-k-mx11.1 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 Release 12.1(12)S system image:

This completes the sample procedure for upgrading to a new software version.

Backing Up with an Older Software Version Example

In the following sample scenario, assume the following:

In this scenario, you begin with the configuration shown in Figure 9.

Next, you copy the rsp-k-mx11.1 image to the active and the standby RSPs, as shown in Figure 10.

Last, delete the rsp-k-mx11.2 image from the standby RSP, as shown in Figure 11:

The following commands configure software error protection for this sample scenario:

Step 2   Copy the Release 12.1(12)E system image to the active and the standby PC Card slot 0:

Step 3   Delete the rsp-k-mx11.2 image from the standby RSP:

Step 4   Configure the system to boot first from a Release 12.1(13)E system image and then from a Release 12.1(12)E 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 Release 12.1(13)E image.

This completes the sample procedure for backing up with an older software version.

Setting Environment Variables on the Active and the Standby RSPs

You can optionally set environment variables on both RSPs in a Cisco 7507 and Cisco 7513.

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 Configuration Fundamentals Configuration Guide and the Configuration Fundamentals Command Reference publications, which are available online, on the Documentation CD-ROM, or as printed documents.

Manually Setting Environment Variables on the Standby RSP

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.

To manually set environment variables on the standby RSP, use the following commands in Table 9 in privileged EXEC mode:

Automatically Setting Environment Variables on the Standby RSP

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.

Note   Automatic synchronization mode is on by default.

To set environment variables on the standby RSP when automatic synchronization is on, use the following commands in Table 10 in privileged EXEC mode:

Monitoring and Maintaining HSA Operation

To monitor and maintain HSA operation, you can override the standby image that is bundled with the active image. To do so, perform the following task in global configuration mode:

Note   The slave image system command, previously used to determine which image the standby runs, is not valid with newer HA images.

You can manually synchronize configuration files and ROM monitor environment variables on the active and the standby RSPs. To do so, perform the following task in privileged EXEC 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 is configured consistently with the active. Failure to do so might result in an unconfigured standby RSP taking control of the router when the active 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 Configuration Fundamentals Configuration Guide and the Configuration Fundamentals Command Reference publications, which are available on the Documentation CD-ROM, online, or as printed documents.

Enabling High Availability Features

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 and the Cisco 7513 routers with two RSP2s, or with one RSP2 and one RSP4/4+.

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.

High Availability Features

HA features include:

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.

Hardware and Software Prerequisites

The RPR and FSU features are available on the Cisco 7507 and Cisco 7513 routers, which are loaded with two route switch processors (RSPs). The router is loaded with two route switch processors (RSPs), which can be two RSP2s, or an RSP2 and an RSP4/4+.

Installation Procedures

See the following sections for the configuration tasks required to run the RPR/RPR+, SSO with NSF, FSU, and SLCR features.

Enabling the Router

Step 2   Enter the password (the password is case sensitive). For security purposes, the password is not displayed.

When you enter the correct password, the system displays the privileged-level system prompt (#):

The completes the enabling the router procedure.

Copying an Image onto an RSP

Use TFTP to copy a high availability Cisco IOS image onto the active and standby RSPs:

Setting the Config-Register Boot Variable

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.

Configuring RPR and RPR+

Each task in the list is identified as either required or optional.

To configure RPR and RPR+, enter the commands as shown below:

Verifying RPR and RPR+

Use the show redundancy command to verify that RPR or RPR+ is enabled:

Configuring RPR and RPR+ Example

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.

Configuring a Stateful Switchover (SSO)

Each task in the list is identified as either required or optional.

To configure SSO, use the following commands beginning in privileged EXEC mode:

Configuring Frame Relay Autosynchronization LMI Sequence Numbers

To configure Frame Relay SSO to synchronize LMI sequence numbers between the active and standby RSPs, use the following command in global configuration mode. This procedure is only for devices supporting Frame Relay and is optional.

Verifying SSO

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

Configuring NonStop Forwarding (NSF)

Cisco NonStop Forwarding (NSF) always runs together with SSO. If you have not already configured SSO, refer to "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.

Configuring CEF NSF

The CEF NSF feature operates by default while the networking device is running in SSO mode. No configuration is necessary.

Configuring BGP NSF

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 mode, and repeat this procedure on each of the BGP NSF peer devices:

Configuring OSPF NSF

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 mode:

Configuring IS-IS NSF

To configure NSF for IS-IS, use the following commands beginning in privileged EXEC mode:

Verifying CEF NSF

To verify that CEF is NSF-capable, use the show cef state command:

Verifying BGP NSF

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:

Verifying OSPF NSF

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:

Verifying IS-IS NSF

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, enter 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:

Troubleshooting NSF Features

To troubleshoot the NSF feature, use the following commands in privileged EXEC mode, as needed:

The following tips may help you to troubleshoot the device.

The system displays FIB errors.

Use the show cef state command to verify that distributed CEF switching is enabled on your platform. To enable distributed CEF, enter the ip cef distributed command in global configuration mode on the active RSP.

Cannot determine if an OSPF neighbor is NSF-aware.

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.

The system loses, or appears to lose, adjacencies with network peers following a stateful switchover.

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.

Configuring BGP NSF Example

The following example configures BGP NSF on a networking device:

Configuring BGP NSF Neighbor Device Example

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.

Configuring OSPF NSF Example

The following example configures OSPF NSF on a networking device:

Configuring IS-IS NSF Example

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:

Performing a Fast Software Upgrade

Each task in the list is identified as either required or optional.

To perform a Fast Software Upgrade (FSU), follow the steps below:

Performing a Fast Software Upgrade Example

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.

RPR, RPR+, SSO, and FSU Troubleshooting Tips

Use the commands in the table below to troubleshoot the RPR, RPR+, and FSU features on Cisco 7500 series routers:

Configuring SLCR

Each task in the list is identified as either required or optional.

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, enter the service single-slot-reload-enable configuration command on the Cisco 7500 series router.

To disable the Cisco 7500 Single Line Card Reload feature, enter the no service single-slot-reload-enable configuration command on the Cisco 7500 series router.

Verifying Cisco 7500 SLCR

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.

SLCR Configuration Example

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:

SLCR Troubleshooting Tips

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.

Miscellaneous HSA and HA Commands

This section describes miscellaneous HSA and HA commands, and how to perform an OIR of an interface processor.

Listed below are commands to display information about failed and active RSPs.

When a new active RSP takes over ownership of the router, it automatically reboots the failed RSP as the standby RSP. You can access the state of the failed RSP in the form of a stack trace from the active console. To do so, perform the following task from EXEC mode:

You can manually reload a failed RSP from the active console. To do so, perform the following task from EXEC mode:

You can display information about the active and the standby RSPs. To do so, perform any of the following tasks from privileged EXEC mode:

Troubleshooting the Installation

This section contains procedures to follow if your system does not restart and boot up 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 RSP2s and each interface processor.

Verifying LEDs

Following are functional descriptions of the LEDs on the power supplies and processor modules, and the behavior you should observe at system startup.

System Power LEDs

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.

RSP2 LEDs

Figure 12 shows the LEDs on the RSP2 faceplate. The LEDs on the RSP2 indicate the system and RSP2 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 RSP2 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 RSP2 is designated an active or a standby device.

---

Note    The Active/Standby switch has been deactivated in software. The reset button boots the system.

---

Caution   The reset switch (see Figure 12) resets the RSP2 and the entire system. To prevent system errors and problems, use it only at the direction of your Cisco-certified service representative.

Verifying System Startup Sequence

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 norm