Route Switch Processor (RSP4) Installation and Configuration

Product Numbers:
RSP4+
RSP4
CISCO 7505/4(=)
CISCO 7507/4(=)
CISCO 7513/4(=)
CISCO 7507/4x2(=)
CISCO 7513/4x2(=)
CISCO 7576(=)
MEM-RSP4-32M=¹MEM-RSP4-64M=
MEM-RSP4-128M=
MEM-RSP4-128M-4PK=
MEM-RSP4-256MB=
MEM-RSP4-256-4PK=

¹This memory product is used to upgrade from 32 MB of DRAM to 64 MB of DRAM. (See Table 7).

This configuration note discusses the next-generation Route Switch Processor (RSP4), which is the main system processor available for the Cisco 7505, Cisco 7507, Cisco 7513, and Cisco 7576. The RSP4 combines all of the switched routing and high-speed switching functions required by the Cisco 7500 series. (For more information, see the "Product Description" section.)

In addition, the RSP4 supports the high system availability (HSA) feature, a new feature that allows two RSP4s to be used simultaneously in a Cisco 7507 or Cisco 7513 router with the HSA feature enabled and configured. (To determine which Cisco IOS software release your router is running, see the "Software Prerequisites" section.)

With the HSA feature, one RSP4 operates as the system master and the other RSP4 operates as the system slave, which takes over if the master RSP4 fails. An RSP4 and an RSP2 can also be used simultaneously with the HSA feature. (See the "Hardware Prerequisites" section.)

Note RSP4 functionality in the Cisco 7500 series routers is similar. For convenience, the Cisco 7505, Cisco 7507, Cisco 7513, and Cisco 7576 routers are referred to as the router or as the Cisco 7500 series routers, with specific differences clearly noted.

Document Contents

This publication contains the following sections:

If You Need More Information

Your router and the IOS software running on it contain extensive features and functionality. For information on IOS software and for general installation and maintenance information for your router, use the following resources:

Cisco Documentation CD-ROM package

: Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly; therefore, it might be more up to date than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription.

For IOS software configuration information and support, refer to the modular configuration and modular command reference publications in the IOS software configuration documentation set that corresponds to the software installed on your Cisco hardware. You can also refer to the IOS software release notes for the version of software you are using on your hardware.
For hardware installation and maintenance information on the Cisco 7500 series routers, refer to the Cisco 7500 Series Installation and Configuration Guide that shipped with your Cisco 7500 series router.
For detailed information on the Flash memory cards that you can use in the RSP4, refer to the configuration note Flash Memory Card Installation Instructions (Document Number 78-2083-xx, where xx is the latest version of this document).
For detailed information on the Flash Disks that you can use in the RSP4, refer to the configuration note Using the PCMCIA Flash Disk (Document Number 78-5819-xx, where xx is the latest version of this document).

Note You can access IOS software documentation and hardware installation and maintenance documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

If you are reading Cisco documentation on the World Wide Web, you can submit comments electronically. Click Feedback on the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.

To view Cisco documentation or obtain general information about documentation, refer to the following sources:
- Cisco Connection Online (CCO). (Refer to the "Cisco Connection Online" section.)
- Customer Service at 800 553-6387 or 408 526-7208. Customer Service hours are 5:00 a.m. to 6:00 p.m. Pacific time, Monday through Friday (excluding company holidays). You can also send e-mail to cs-rep@cisco.com.

Installation Prerequisites

This section provides important installation information. Before beginning any of the procedures in this document, review the following sections to ensure that your equipment configuration meets the minimum requirements for the upgrade or replacement you want to perform, and that you have all the parts and tools you need. Also, review safety and ESD-prevention guidelines to help you to avoid injury or damage to the equipment.

Note If you are replacing an existing RSP4, back up your current configuration file to a remote server before you remove the RSP4 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 RSP4 is installed.

Safety Guidelines

This section lists safety guidelines you should follow when working with any equipment that connects to electrical power or telephone wiring.

Safety Warnings

Safety warnings appear throughout this publication in procedures that, if performed incorrectly, might harm you. A warning symbol precedes each warning statement.

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

Use the following basic guidelines when working with any electrical equipment:

Before beginning any procedures requiring access to the router interior, locate the emergency power-off switch for the room in which you are working.
Disconnect all power and external cables before moving a chassis.
Do not work alone when potentially hazardous conditions exist.
Never assume that power has been disconnected from a circuit; always check.
Do not perform any action that creates a potential hazard to people or makes the equipment unsafe.
Carefully examine your work area for possible hazards such as moist floors, ungrounded power extension cables, and missing safety grounds.

Telephone Wiring

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

Never install telephone wiring during a lightning storm.
Never install telephone jacks in wet locations unless the jack is specifically designed for wet locations.
Never touch uninsulated telephone wires or terminals unless the telephone line has been disconnected at the network interface.
Use caution when installing or modifying telephone lines.

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:

Always use an ESD-preventive wrist or ankle strap and ensure that it makes good skin contact.
When you work at the interface processor end of the router, connect the equipment end of the strap to the captive installation screw on an installed interface processor, or to the chassis grounding receptacle that is located next to each power supply.
When you install a processor module, use the ejector levers to properly seat the bus connectors in the backplane, then tighten both captive installation screws. These screws prevent accidental removal, provide proper grounding for the system, and help to ensure that the bus connectors are seated in the backplane.
Handle processor modules by the carrier handles and carrier edges only; never touch the board or any connector pins.
When you remove a processor module, place it card side up on an antistatic surface or in a static shielding bag. Immediately place the module in a static shielding bag if you need to return it to the factory.
Avoid contact between electronic equipment and clothing. Antistatic straps only protect the equipment from ESD voltages on the body; ESD voltages on clothing can still cause damage.

Caution For safety, periodically check the resistance value of the antistatic strap. The measurement should be between 1 and 10 megohms.

Compatibility Requirements

This section describes important compatibility requirements for the RSP4.

Chassis Slot and DRAM Requirements

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

There are no restrictions on installing an RSP4 in a Cisco 7507 provided that you install the RSP4 in slot 2, slot 3 or both. (With the HSA feature enabled, you can use both RSP slots.)

There are no restrictions on installing an RSP4 in a Cisco 7513 provided that you install the RSP4 in slot 6, slot 7, or both. (With the HSA feature enabled, you can use both RSP slots.)

There are no restrictions on installing RSP4s in a Cisco 7576 provided that you install the RSP4s in slot 6 (for router A) and slot 7 (for router B). (The Cisco 7576 does not support the HSA feature.)

The assumption is that if you install two RSP4s in the Cisco 7507 or Cisco 7513, you plan to enable and configure the HSA feature.

Although the Personal Computer Memory Card International Association (PCMCIA) card and DRAM DIMM specifications are defined in the manufacturers' part numbers, they must meet the following requirements:

Intel Series 2+ Flash memory cards and DRAM DIMMs must be obtained from Cisco Systems or an approved vendor.
Maximum DRAM speed is 60 nanoseconds (ns), maximum DIMM height is 1 inch, and maximum DRAM DIMM voltage is 3.3 volts (V).

Flash Memory Card Requirements

Following are Flash memory card requirements for ensuring RSP4 compatibility.

You cannot boot from or use a Flash memory card in the RSP4 that was formatted on another type of RSP-based system (including RSP7000, RSP1 and RSP2) that was running a Cisco IOS software version earlier than the minimum software release requirements listed in Table 1.

Table 1: RSP4 Minimum Software Release Requirements

Cisco IOS Release Version Minimum Cisco IOS Supported Releases

Cisco IOS Release 11.1(8)CA

Cisco IOS Release 11.1(8)CA or later release of Cisco IOS Release 11.1 CA¹

Cisco IOS Release 11.1(17)CC

Cisco IOS Release 11.1(17)CC or later release of Cisco IOS Release 11.1 CC

Cisco IOS Release 11.2(6) P

Cisco IOS Release 11.2(6) P or later release of Cisco IOS Release 11.2 P

Cisco IOS Release 11.3(1)T

Cisco IOS Release 11.3(1)T or later release of Cisco IOS Release 11.3 T

Cisco IOS Release 11.3(1)

Cisco IOS Release 11.3(1) or later release of Cisco IOS Release 11.3

Cisco IOS Release 12.0(1)T

Cisco IOS Release 12.0(1)T or later release of Cisco IOS Release 12.0 T

Cisco IOS Release 12.0(1)

Cisco IOS Release 12.0(1) or later release of Cisco IOS Release 12.0

Cisco IOS Release 12.0(2) XE3

Cisco IOS Release 12.0(2) XE3 or later release of Cisco IOS Release 12.0 XE

Cisco IOS Release 12.0(4)XE1

Cisco IOS Release 12.0(4)XE1 or later release of Cisco IOS Release 12.0 XE1

Cisco IOS Release 12.0(5)S

Cisco IOS Release 12.0(5)S or later release of Cisco IOS Release 12.0 S

Cisco IOS Release 12.1(1)E

Cisco IOS Release 12.1(1)E or later release of Cisco IOS Release 12.1 E

Cisco IOS Release 12.1(1)

Cisco IOS Release 12.1(1) or later release of Cisco IOS Release 12.1

¹Applies to all platforms that support the RSP4 except Cisco 7576, which requires Cisco IOS Release 11.1(22)CC, or a later release of 11.2 CC.

Cisco IOS Release Version	Minimum Cisco IOS Supported Releases
Cisco IOS Release 11.1(8)CA	Cisco IOS Release 11.1(8)CA or later release of Cisco IOS Release 11.1 CA¹
Cisco IOS Release 11.1(17)CC	Cisco IOS Release 11.1(17)CC or later release of Cisco IOS Release 11.1 CC
Cisco IOS Release 11.2(6) P	Cisco IOS Release 11.2(6) P or later release of Cisco IOS Release 11.2 P
Cisco IOS Release 11.3(1)T	Cisco IOS Release 11.3(1)T or later release of Cisco IOS Release 11.3 T
Cisco IOS Release 11.3(1)	Cisco IOS Release 11.3(1) or later release of Cisco IOS Release 11.3
Cisco IOS Release 12.0(1)T	Cisco IOS Release 12.0(1)T or later release of Cisco IOS Release 12.0 T
Cisco IOS Release 12.0(1)	Cisco IOS Release 12.0(1) or later release of Cisco IOS Release 12.0
Cisco IOS Release 12.0(2) XE3	Cisco IOS Release 12.0(2) XE3 or later release of Cisco IOS Release 12.0 XE
Cisco IOS Release 12.0(4)XE1	Cisco IOS Release 12.0(4)XE1 or later release of Cisco IOS Release 12.0 XE1
Cisco IOS Release 12.0(5)S	Cisco IOS Release 12.0(5)S or later release of Cisco IOS Release 12.0 S
Cisco IOS Release 12.1(1)E	Cisco IOS Release 12.1(1)E or later release of Cisco IOS Release 12.1 E
Cisco IOS Release 12.1(1)	Cisco IOS Release 12.1(1) or later release of Cisco IOS Release 12.1

You must first reformat the Flash memory card, formatted on one of these other RSP-based systems, before you can use it as a boot or storage source with the RSP4. (Downloading ROM monitor images directly to the Flash boot ROM device [U5] is not supported with the initial release of the RSP4; this functionality will be available in a future Cisco IOS release.)

Note In order for a Flash memory card that was formatted on an RSP1, RSP2, or RSP7000 to be compatible in an RSP4, the Flash memory card must be formatted with a boot or Cisco IOS software image that is compatible with the RSP4.

Caution To prevent system problems, use Flash memory cards in the RSP4 that were formatted on an RSP1, RSP2, RSP7000, or RSP4 running Cisco IOS Release 11.1(8)CA1 or a later release. (See Table 1 for minimum software release requirements.)

Software Prerequisites

The RSP4 is compatible with the Cisco IOS Releases stated in Table 1. These IOS software releases apply to all systems that support the RSP4, except the Cisco 7576. At a minimum, the Cisco 7576 requires Cisco IOS Release 11.1(22)CC, or a later release of 11.1 CC.

The show version and show hardware commands display the current hardware configuration of the router, including the system software version that is currently loaded and running. 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 RSP4 board's hardware version (Version 1.0 at initial release) and revision (Revision A0 at initial release).

For additional descriptions of show commands, refer to the Configuration Fundamentals Configuration Guide and Configuration Fundamentals Command Reference publications, which are available on the Documentation CD-ROM or as printed copies.

Note If the displays indicate that 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 "Cisco Connection Online" section.)

Hardware Prerequisites

To ensure that the slave RSP4 operates properly with the full system configuration, if the master RSP4 ever fails in a system with the HSA feature configured, the slave RSP4 should have the same DRAM configuration and boot ROM version as the master RSP4.

Caution Removing the system master RSP4 while the system is operating might cause the system to crash; however, the system reloads with the slave RSP4 as the new system master. To prevent any system problems, do not remove the system master RSP4 while the system is operating.

Note With HSA, the RSP4 can interoperate with an RSP2 in a Cisco 7507 or Cisco 7513 router. If you plan to use an RSP4 and an RSP2 in the same router for the HSA feature, refer also to the configuration notes Route Switch Processor (RSP2) Installation and Configuration (Document Number 78-2026-06 or later) and Upgrading the Boot ROM on the RSP2 and Initializing the HSA Feature (Document Number 78-2883-03 or later) to prepare your RSP2 properly. These configuration notes are available on the Documentation CD-ROM, or as printed copies.

Caution Before you can use a Flash memory card that was previously formatted and used in an RP, RSP7000, RSP1, or RSP2), you must reformat the Flash memory card. Flash memory cards formatted on any of these processors do not work properly in an RSP4. To ensure that you can boot a Cisco IOS software image from a Flash memory card that was formatted and used in any of these systems, you must first reformat it on your RSP4 system.

Note Your router's configuration and the protocols and features you are running might require more than 32 MB of DRAM for your RSP4. To upgrade DRAM, see the "Replacing and Upgrading DRAM DIMMs" section.

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 between the various interface processors in the system. We recommend that you use only the microcode image that is bundled.

List of Parts and Tools

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

One of the RSP4-related product numbers listed in the "Product Description" section.
If a DRAM upgrade is required, see the "Replacing and Upgrading DRAM DIMMs" section to determine the DRAM product you need. (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 (such as those designed for the RSP2) in the RSP4's DIMM sockets.

Number 1 Phillips screwdriver and a number 2 Phillips or 3/16-inch flat-blade screwdriver for the captive installation screws that secure the RSP4 in its slot.
ESD-prevention equipment or the disposable ESD-preventive wrist strap included with all spares and upgrade kits.
Antistatic mat, foam pad, or bag for the removed RSP4 (place the removed RSP4 in an antistatic bag if you plan to return it to the factory, or on an antistatic mat or foam if you are replacing components and will reinstall the RSP4).

Saving and Retrieving a Configuration File

This section describes the procedures for saving and retrieving a system configuration file using a Trivial File Transfer Protocol (TFTP) server.

Configuration information resides in two places when the router is operating: the default (permanent) configuration in NVRAM, and the running (temporary) memory in RAM. The default 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 command facility, or by editing the configuration file.

The copy running-config startup-config 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, issue the copy running-config startup-config command to ensure that the new configuration is saved.

If you replace the RSP4 in a system with only one RSP4, you also replace the entire configuration, which resides in NVRAM on the RSP4. If you copy the configuration file to a remote server before removing the RSP4, you can retrieve it later and write it into NVRAM on the new RSP4. 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: command to restore it.

If you do not copy the configuration file, you must use the configure command or the setup command facility to reenter the configuration information after you install the new RSP4. For complete descriptions of these two commands, and instructions for using them, refer to the appropriate software documentation.

If you are temporarily removing an RSP4, 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 RSP4 in the system. This procedure requires privileged-level access to the EXEC command interpreter, which usually requires a password. See the description that follows and contact your system administrator to obtain access, if necessary.

Using the EXEC Command Interpreter

Before you use 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 1 At the EXEC prompt (>), enter the enable command. The EXEC command interpreter prompts you for a privileged-level password, as follows:

Router> enable
 
Password:

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:

Router#

The pound sign (#) at the system prompt indicates the privileged level of the EXEC command interpreter, from which you can execute EXEC-level commands described in the following sections.

This completes the procedure for using the EXEC Command Interpreter.

Using the ping Command to Ensure Connectivity

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

Router# ping 1.1.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/12/12 ms

The following example shows the results of a failed ping operation:

Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Router#

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 end of this document for instructions on contacting technical assistance.

Copying the Configuration File

Before you copy (save) the running configuration to a TFTP file server, ensure the following:

You have a connection to the router either with a console terminal connected to the RSP4 console port or remotely through a Telnet session.
The router is connected to a network supporting a file server (remote host).
The remote host supports the TFTP application.
You have the interface processor address or name of the remote host available.

To store information on a remote host, enter the privileged EXEC command write network. 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.

Follow these steps to copy the currently running configuration to a remote host:

Step 1 The system prompt should display a pound sign (#) to indicate the privileged level of the EXEC command interpreter. If it does not, follow the steps in the "Using the EXEC Command Interpreter" section to enable the privileged level.

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 Issue the show running-config command to display the currently running configuration on the terminal and ensure that the configuration information is complete and correct. 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 4 Create a file on the TFTP server.

Step 5 Issue 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.)

Router# copy startup-config tftp
Remote host []?

Step 6 Enter the name or interface processor address of the remote host. In the following example, the name of the remote server is servername:

Router# copy startup-config tftp
Remote host []? servername
Translating "servername"...domain server (1.1.1.1) [OK]

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

Name of configuration file to write [Router-confg]?
Write file Router-confg on host 1.1.1.1? [confirm]
Writing Router-confg .....

Step 8 Before the router executes the copy process, it displays the instructions you entered for confirmation. If the instructions are not correct, enter n (no) then Return to abort 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:

Write file Router-confg on host 1.1.1.1? [confirm]
Writing Router-confg: !!!! [ok]

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 display of . . . [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 9 If the display indicates that the process was successful (with the series of ! ! ! 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 . . . as shown in the following example):

Writing Router-confg .....

your configuration was not saved. Repeat the preceding steps, or select a different remote file server and repeat the preceding steps.

After you upload the configuration file, proceed to the "Removing the RSP4" section. If you are unable to copy the configuration to a remote host successfully, contact your network administrator or see the end of this document for instructions on contacting technical assistance.

This completes the procedure for copying the configuration file.

Retrieving the Configuration File

After you install the new RSP4, you can retrieve the saved configuration and copy it to NVRAM. To retrieve the configuration, enter 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 directly to the RSP4 console port, or you can configure an interface port and Telnet to the router from a remote terminal.

Follow these steps to retrieve the currently running configuration from a remote host:

Step 1 On the console terminal, the system prompt should display a pound sign (#) to indicate the privileged level of the EXEC command interpreter. If it does not, follow the steps in the "Using the EXEC Command Interpreter" section to enable the privileged level.

Note Until you retrieve the previous configuration, the router is running 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, issue 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).

Router# copy tftp startup-config

Step 5 The system prompts you for the IP address of the host. Enter the IP address or name of the remote host (the remote TFTP server to which you originally saved the configuration file).

Address of remote host [255.255.255.255]? 1.1.1.1

Step 6 The system prompts you for the name of the configuration file. When copying the 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, enter the filename; otherwise, press Return to accept the default.

Name of configuration file [Router-confg]?

Step 7 Before the system reloads the new configuration file in NVRAM, it displays the instructions you entered for confirmation. If the instructions are not correct, enter 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:

Configure using Router-confg from 1.1.1.1? [confirm]
Loading Router-confg from 1.1.1.1: ! ! [OK - 1186/126927 bytes]
Warning: distilled config is not generated
[OK]
%SYS-5-CONFIG_NV: Non-volatile store configured from Router-confg 
by console tftp from 1.1.1.1

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 !!!! and [OK] (as shown in the preceding example) indicates that the operation was successful. A series of . . . 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:

Booting Router-confg ..... [timed out]

Step 8 If the display indicates that the process was successful, as shown in Step 7, proceed to the next step.

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 end of this document for instructions on contacting technical assistance.

Step 9 To ensure that the configuration file was retrieved correctly, issue the show startup-config command and look at the first line for the configuration file's size. Match it with the file you retrieved from the TFTP server. Following is an example:

Router# show startup-config
Using 1186 out of 126968 bytes
!
version 11.1
hostname Router
!
Router#

Step 10 To ensure that the startup configuration file stored in NVRAM is the default running configuration file used by the system, issue the copy startup-config running-config command as follows:

Router# copy startup-config running-config
Router#
%SYS-5-CONFIG_I: Configured from memory by console
Router#

This completes the procedure for retrieving the saved configuration file.

Product Description

The RSP4 is the main system processor module for the Cisco 7500 series routers. (See Figure 1 and Figure 2.)

Figure 1: RSP4 (Horizontal Front-Panel View)

Figure 2: Route Switch Processor (RSP4) (Horizontal Orientation Shown)

The RSP4 is available as follows:

As a spare part, as Product Number RSP4= or RSP4+=
Bundled with and installed in Cisco 7500 series routers, as follows:
- Product Number CISCO7505/4(=), which includes a Cisco 7505 with one installed RSP4
- Product Number CISCO7507/4(=), which includes a Cisco 7507 with one installed RSP4
- Product Number CISCO7513/4(=), which includes a Cisco 7513 with one installed RSP4
- Product Number CISCO7507/4x2(=), which includes a Cisco 7507 with two installed RSP4s
- Product Number CISCO7513/4x2(=), which includes a Cisco 7513 with two installed RSP4s
- Product Number CISCO7576(=), which includes a Cisco 7576 with two installed RSP4s

The RSP4 contains the following components:

IDT R5000 Reduced Instruction Set Computing (RISC) processor, used for the CPU. The CPU runs at an external bus clock speed of 100 MHz and an internal clock speed of 200 MHz.
Up to 256 megabytes (MB) of parity-protected, dynamic random-access memory (DRAM) on two dual in-line memory modules (DIMMs); 32 MB of DRAM is the default shipping configuration for the RSP4; 64MB of DRAM is the default shipping configuration for the RSP4+.
2 MB of parity-protected, static random-access memory (SRAM) for packet buffering, and 512 KB of SRAM for secondary CPU cache memory functions (SRAM is not user-configurable).
Most of the additional memory components used by the system, including onboard Flash memory and up to two PCMCIA-based Flash memory cards.
Air-temperature sensors for environmental monitoring. (All of the logic for the environmental monitoring functions is contained on the router interface card.)

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

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

Sending and receiving routing protocol updates
Managing tables and caches
Monitoring interface and environmental status
Providing Simple Network Management Protocol (SNMP) management and the console/Telnet interface

The high-speed switching section of the RSP4 communicates with and controls the interface processors on the high-speed CyBus. This switching section of the RSP4 decides the destination of a packet and switches it based on that decision.

The RSP4 combines all of the switched routing and high-speed switching functions. The RSP4 supports the HSA feature, which allows two RSP4s to be used in a Cisco 7507 or Cisco 7513 router. By default, the system master is the RSP4 that occupies the first RSP slot in the router: slot 2 in the Cisco 7507, and slot 6 in the Cisco 7513.

Note The Cisco 7505 has only one RSP slot; therefore, it does not support the HSA feature.

System Software

The Cisco 7507 and Cisco 7513 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 (Document Number 78-1144-xx), which accompanies all Cisco IOS upgrade kits, provides instructions for upgrading over the network or from floppy disks. Flash memory contains the default system software image and bundled microcode images. Both PCMCIA-based and SIMM-based Flash memory are supported.

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 either on the RSP4, in the form of a single in-line memory module (SIMM), or on up to PCMCIA-based Flash memory cards that insert in the two PCMCIA slots (slot 0 and slot 1) on the front of the RSP4. (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 RSP4 Flash memory.

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

Memory Components

Figure 2 shows the various types of memory components on the RSP4, and lists the functions of each type.

Table 2: RSP4 Memory Components

Type Size Quantity Description Location

DRAM

32¹ to 256 MB DIMMs

1 or 2

32-, 64-, or 128-MB DIMMs (based on DRAM required) for main Cisco IOS image functions

U10
or U10 and U13

SRAM²

2 MB (fixed)

-

SRAM for packet buffering functions (MEMD)

-

512 KB (fixed)

-

SRAM for secondary CPU cache memory functions

-

NVRAM

128 KB

1

Nonvolatile SRAM for the system configuration file³

-

Flash memory

8-MB SIMM

1

Contains the Cisco IOS images on the RSP4

U1

16⁴ and 20 MB

Up to 2

Contains the Cisco IOS images on up to two PCMCIA-based Flash memory cards⁵

Slot 0 and slot 1

Flash boot ROM

256 KB

1

Flash EPROM for the ROM monitor program image⁶

U5

¹32 MB of DRAM is the default DRAM configuration for the RSP4; 64 MB of DRAM is the default DRAM configuration for the RSP4+.
²SRAM is not user-configurable or field-upgradable.
³A system configuration file is contained in NVRAM, which allows the Cisco IOS software to control several system variables.
⁴A 16-MB Flash memory card is the default shipping configuration for the RSP4 products.
⁵Type 1, Type 2, and Type 3 PCMCIA cards can be used in PCMCIA slot 1, and Type 1 and Type 2 PCMCIA cards can be used in slot 0.
⁶Downloading ROM monitor images to the Flash boot ROM device is not supported with the initial release of the RSP4; this functionality will be available in a future Cisco IOS release.

Type	Size	Quantity	Description	Location
DRAM	32¹ to 256 MB DIMMs	1 or 2	32-, 64-, or 128-MB DIMMs (based on DRAM required) for main Cisco IOS image functions	U10 or U10 and U13
SRAM²	2 MB (fixed)	-	SRAM for packet buffering functions (MEMD)	-
	512 KB (fixed)	-	SRAM for secondary CPU cache memory functions	-
NVRAM	128 KB	1	Nonvolatile SRAM for the system configuration file³	-
Flash memory	8-MB SIMM	1	Contains the Cisco IOS images on the RSP4	U1
	16⁴ and 20 MB	Up to 2	Contains the Cisco IOS images on up to two PCMCIA-based Flash memory cards⁵	Slot 0 and slot 1
Flash boot ROM	256 KB	1	Flash EPROM for the ROM monitor program image⁶	U5

DRAM

DRAM stores routing tables, protocols, and network accounting applications and runs the Cisco IOS software. The standard (default) RSP4 configuration is 32 megabytes (MB) of DRAM, and the standard (default) RSP4+ configuration is 64 megabytes (MB) of DRAM. Both the RSP4 and RSP4+ have up to 256 MB of DRAM available through DIMM upgrades. DRAM is contained in up to two DIMM sockets: U10 (also called bank 0) and U13 (also called bank 1). When upgrading DRAM, you must use DIMMs from an approved vendor. (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 (such as those designed for the RSP2) in the RSP4's DIMM sockets.

SRAM

SRAM provides packet buffering and CPU cache memory functions. The standard RSP4 configuration is 2 MB of DRAM for packet buffering, and 512 kilobytes (KB) of secondary CPU cache memory.

Note SRAM is fixed and is not field-upgradable.

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 RSP4, be sure to back up your configuration to a remote server so you can retrieve it later.

Caution Before you replace an RSP4 in a system with one RSP4, 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 RSP4—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 RSP4; lithium batteries retain the configuration in memory until you replace the RSP4 in the system.

Flash Memory

Both the onboard 8-MB Flash memory and the 16- or 20-MB PCMCIA-card-based Flash memory allow you to remotely load and store multiple Cisco IOS software and microcode images. (The 16-MB Flash memory card is the default Flash memory card that ships with the RSP4.) 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.

Note In order for a Flash memory card that was formatted on an RP, RSP1, RSP2, or RSP7000 to be compatible in an RSP4, the Flash memory card must be reformatted with a boot or Cisco IOS software image that is compatible with the RSP4. Currently the Cisco IOS release required for Flash memory card compatibility is Cisco IOS Release 11.1(8)CA1 or later. Downloading ROM monitor images to the Flash boot ROM device (U5) is not supported with the initial release of the RSP4; this functionality will be available in a future Cisco IOS release.

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

Jumpers

There are no user-configurable jumpers on the RSP4.

LEDs

Several LEDs on the RSP4 indicate the system and RSP4 status. The normal LED is on when the system is operational and indicates that the RSP4 is receiving +5V. During normal operation, the CPU halt LED should be off. The CPU halt LED goes on only if the system detects a processor hardware failure. The RSP4 controls the normal and CPU halt LEDs and turns them on in parallel to indicate that the system is operational.

The master/slave LEDs indicate whether an RSP4 is the master or the slave in a system configured for the high system availability (HSA) feature. The slot 0 and slot 1 PCMCIA LEDs are on when a PCMCIA card is being accessed while inserted in the respective PCMCIA slot.

PCMCIA Slots

The RSP4 has two PCMCIA slots available. Either slot can support a Flash memory card or an input/output (I/O) device. Type 1 and Type 2 PCMCIA cards can be used in PCMCIA slot 0 and 1. Not all Flash memory cards that are commercially available are supported, and not all I/O devices are supported. The RSP4 also supports the use of PCMCIA Flash Disks for storage of Cisco IOS images, microcode images, and configuration files, and as TFTP servers.

Note Other Flash memory card limitations might apply. For additional Flash memory information, refer to the Flash memory configuration notes listed in the "If You Need More Information" section.

Serial Ports

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

Installing the RSP4

The following sections describe the procedures for installing or replacing an RSP4. Ensure that your system meets the minimum software, hardware, and microcode requirements described in the following sections: "Software Prerequisites" section, "Hardware Prerequisites" section, and "Microcode Requirements" section. Proceed to the "Removing the RSP4" section for instructions on removing the RSP4, and then to the section "Replacing the RSP4" for the installation instructions. After the new RSP4 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 RSP4 from a system while the system is operating might cause the system to crash. Consider this before removing an RSP4 while the system is operating. To ensure that the slave RSP4 operates properly with the full system configuration, should the master RSP4 ever fail, the slave RSP4 should have the same boot-ROM and DRAM configuration as the master RSP4.

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/install an RSP4 in RSP slot 7, we recommend that you proceed as follows: first remove an interface processor installed in slot 8, remove or install the RSP4 in RSP slot 7 (and fasten its captive screws as appropriate), then reinstall the interface processor in slot 8.

Removing the RSP4

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

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

Step 1 Optional step: If you are replacing the RSP4 in a system with one RSP4, copy the currently running configuration file to a TFTP server so you can retrieve it later. (See the "Saving and Retrieving a Configuration File" section.)

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 RSP4, disconnect any devices that are attached to the console or auxiliary ports. If you are removing the RSP4 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 4.)

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 4c) to release the carrier from the slot and to dislodge the RSP4 from the backplane.

Step 6 Grasp the handle of the RSP4 with one hand and pull the RSP4 straight out of the slot, keeping your other hand under the carrier to guide it. (See Figure 3.) Keep the carrier parallel to the backplane. Avoid touching the board or any connector pins.

Figure 3: Handling the RSP4 during Removal and Installation

Step 7 Place the removed RSP4 on an antistatic mat or foam. If you plan to return the RSP4 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 RSP4 before performing any maintenance on the RSP4 that might create an ESD hazard.

This completes the removal procedure. If you removed the RSP4 to replace DIMMs, proceed to the appropriate section. If you are replacing the RSP4, proceed to the next section to install the new RSP4.

Replacing the RSP4

The RSP4 is keyed for installation only in an RSP slot. (See Figure 1 and Figure 2.) By default, the system master is the RSP4 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 RSP4:

Step 1 Grasp the RSP4 handle with one hand and place your other hand under the carrier to support and guide it into the slot. (See Figure 3.) Avoid touching the board or any connectors.

Step 2 Place the back of the RSP4 in the appropriate RSP slot and align the notches along the edge of the carrier with the grooves in the slot. (See Figure 4a.)

Figure 4: Ejector Levers and Captive Installation Screw

Caution To prevent damage to the backplane, you must install the RSP4 in one of the two RSP slots on the router. The slots are keyed for correct installation. Forcing the RSP4 into a different slot can damage the backplane and the RSP4.

Step 3 While keeping the RSP4 parallel to the backplane, carefully slide the carrier into the slot until the RSP4 faceplate makes contact with the ejector levers, and then stop. (See Figure 4b.)

Step 4 Using the thumb and forefinger of each hand to pinch each ejector, simultaneously push both ejectors inward (toward the handle) until they are parallel to the faceplate. (See Figure 4c.)

Step 5 Use a screwdriver to tighten the captive installation screws on the ends of the RSP4. (See Figure 4 a.)

Step 6 Use a screwdriver to tighten the two captive screws on the RSP4 faceplate to prevent the RSP4 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 RSP4, or if you are installing a new RSP4, 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 RSP4.

Connecting a Console Terminal

The system console port on the RSP4 is a DB-25 receptacle DCE port for connecting a data terminal, which you will need to configure and communicate with your system. The console port is located on the RSP4 just below the auxiliary port, as shown in Figure 5, and is labeled Console.

Before connecting the console port, check your terminal's documentation 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 RSP4, and then follow the steps in the "Restarting the System" section.

Figure 5: Console and Auxiliary Port Connections

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 RSP4 is a DB-25 plug DTE port for connecting a modem or other DCE device (such as a CSU/DSU or other router) to the router. The port is located next to the console port on the RSP4 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 RSP4s installed (one as master and one as slave in RSP slots 2 and 3 in the Cisco 7507, and slots 6 and 7 in the Cisco 7513, using the HSA feature), you can simultaneously connect to both console or auxiliary ports using a special, optional Y-cable. RSP4 defaults as the system master if only one RSP4 is installed.

Figure 6 shows the console Y-cable and Figure 7 shows the auxiliary Y-cable.

Figure 6: Console Y-Cable (CAB-RSP4CON=)

Figure 7: Auxiliary Y-Cable (CAB-RSP4AUX=)

Note The Y-cables are not required for the RSP4s in your Cisco 7507 or Cisco 7513; two individual console cables and two individual auxiliary cables can be used instead.

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

Step 1 Check the RSP4 connections to make sure they are secure:

The RSP4 is inserted all the way into its slot, and both the captive installation screws are tightened.
The console terminal is turned on and is connected to the console port.

Step 2 Observe the RSP4 LEDs. While the system initializes, the CPU halt LED on the RSP4 stays on. It goes off when the boot process is complete. As the RSP4 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 configured, verify that the console terminal displays the system banner and startup screen as the system restarts. The master console display should look similar to the following for a Cisco 7513 (note the RSP slots indicated):

System Bootstrap, Version 11.1(8)CA1, RELEASED SOFTWARE
Copyright (c) 1986-1996 by cisco Systems, Inc.
SLOT 6 RSP4 is system master
SLOT 7 RSP4 is system slave
RSP4 processor with 32 Mbytes of main memory
 
[additional displayed text omitted from this example]
 
Cisco Internetwork Operating System Software
IOS (tm) GS Software (RSP-K-M), Version 11.1(8)CA1 [biff 51096]
Copyright (c) 1986-1996 by cisco Systems, Inc.
Compiled Mon 22-Jan-96 21:15 by biff
Image text-base: 0x600108A0, data-base: 0x607B8000
 
cisco RSP4 (R5000) processor with 32 Mbytes of memory.
R5000 processor, Implementation 35, Revision 1.0
 
[additional displayed text omitted from this example]
 
8192K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).
8192K bytes of Flash internal SIMM (Sector size 256K).
Slave in slot 7 is halted.
 
[additional displayed text omitted from this example]

The master console display should look similar to the following for a Cisco 7507 (note the RSP slots indicated):

System Bootstrap, Version 11.1(8)CA1, RELEASED SOFTWARE
Copyright (c) 1986-1996 by cisco Systems, Inc.
SLOT 2 RSP4 is system master
SLOT 3 RSP4 is system slave
RSP4 processor with 32 Mbytes of main memory
 
[additional displayed text omitted from this example]
 
Cisco Internetwork Operating System Software
IOS (tm) GS Software (RSP-K-M), Version 11.1(8)CA1 [biff 51096]
Copyright (c) 1986-1996 by cisco Systems, Inc.
Compiled Mon 22-Jan-96 21:15 by biff
Image text-base: 0x600108A0, data-base: 0x607B8000
 
cisco RSP4 (R5000) processor with 32 Mbytes of memory.
R5000 processor, Implementation 35, Revision 1.0
 
[additional displayed text omitted from this example]
 
8192K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).
8192K bytes of Flash internal SIMM (Sector size 256K).
Slave in slot 3 is halted.
[additional displayed text omitted from this example]

Step 4 With a single RSP4 (non-HSA), verify that the console terminal displays the system banner and startup screen as the system restarts. The display should look similar to the following:

System Bootstrap, Version 11.1(8)CA1 [biff 51096], RELEASED SOFTWARE
Copyright (c) 1994-1996 by cisco Systems, Inc.
SLOT 6 RSP4 is system master
RSP4 processor with 32 Mbytes of main memory
 
[additional displayed text omitted from this example]
 
Cisco Internetwork Operating System Software
IOS (tm) GS Software (RSP-K-M), Version 11.1(8)CA1 [biff 51096]
Copyright (c) 1986-1996 by cisco Systems, Inc.
Compiled Mon 22-Jan-96 21:15 by biff
Image text-base: 0x600108A0, data-base: 0x607B8000
 
cisco RSP4 (R5000) processor with 32 Mbytes of memory.
R5000 processor, Implementation 35, Revision 1.0
 
[additional displayed text omitted from this example]

Step 5 After the system boots the software and initializes the interface processors, verify that the RSP4 LEDs are in the following states:

RSP4 normal LED is on (for each RSP4 installed)
CPU halt LED is off (for each RSP4 installed)
Master RSP4's master LED is on (if HSA is configured)
Slave RSP4's slave LED is on (if HSA is configured)

Note Boot time is approximately 1 minute for systems with one RSP4 and approximately 1.5 minutes for systems with two RSP4s.

Step 6 Verify that all the enabled LEDs (on the interface processors) are on.

Step 7 In systems with a second RSP4 installed (and HSA configured), use the show version command to verify that the slave RSP4 is recognized by the system. Following is a sample from a Cisco 7513:

Router> show version
Cisco Internetwork Operating System Software
IOS (tm) GS Software (RSP-K-M), Version 11.1(8)CA1 [biff 51096]
Copyright (c) 1986-1996 by cisco Systems, Inc.
Compiled Mon 22-Jan-96 21:15 by biff
Image text-base: 0x600108A0, data-base: 0x607B8000
 
[additional displayed text omitted from this example]
 
Slave in slot 7 is running Cisco Internetwork Operating System Software
 
(Note that this could also be "slot 6" depending on which RSP4 is configured as the slave or the recent crash history of your router.)
 
IOS (tm) GS Software (RSP-DW-M), Version 11.1(8)CA1 [biff 51096]
Copyright (c) 1986-1996 by cisco Systems, Inc.
Compiled Mon 22-Jan-96 20:59 by biff
 
Configuration register is 0x0102

When you have verified all the conditions in Step 2 through Step 6 (or Step 7 if you have a second RSP4 installed and want to use the HSA feature), the installation is complete. If you replaced the RSP4 and saved your configuration file to a remote server before doing so, proceed to the "Retrieving the Configuration File" section. If you replaced the RSP4 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 boot error or CPU halt LEDs 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 on the Documentation CD-ROM or as printed copies.

If you have a second RSP4 installed, you must configure the HSA feature for your Cisco 7507 or Cisco 7513 router. Read the following caution, and then proceed to the following the"Configuring High System Availability Operation" section.

Caution When you install a second RSP4 card for the first time and plan to enable the HSA feature, you must immediately configure it correctly. This ensures that the new slave is configured consistently with the master. Failure to do so might result in an unconfigured slave RSP4 card taking over control of the router when the master fails, rendering the network inoperable.

This completes the procedure for restarting the system.

Configuring High System Availability Operation

High system availability (HSA) refers to the speed with which your router returns to an operational status after a failure occurs. You can install two RSP4 cards in a single router to improve system availability.

Note With the HSA feature, the RSP4 can interoperate with an RSP2 in a Cisco 7507 or Cisco 7513 router; this document describes systems with two RSP4s. If you plan to use an RSP4 and an RSP2 in the same router for the HSA feature, refer also to the configuration notes Route Switch Processor (RSP2) Installation and Configuration (Document Number 78-2026-06 or later) and Upgrading the Boot ROM on the RSP2 and Initializing the HSA Feature (Document Number 78-2883-03 or later) to prepare your RSP2 properly.

The Cisco 7576 does not support the HSA feature.

For more complete HSA configuration information, refer to the Configuration Fundamentals Configuration Guide and the Configuration Fundamentals Command Reference publications, which are available on the Cisco Documentation CD-ROM or as printed copies.

Two RSP4 cards in a router provide the most basic level of increased system availability through a "cold restart " feature. A "cold restart" means that when one RSP4 card fails, the other RSP4 card reboots the router. In this way, your router is never in a failed state for very long, thereby increasing system availability.

When one RSP4 card takes over operation from another, system operation is interrupted. Such a change is similar to issuing the reload command. The following events occur when one RSP4 card fails and the other takes over:

The router stops passing traffic.
Route information is lost.
All connections are lost.
The backup or "slave" RSP4 becomes the active or "master" RSP4 that reboots and runs the router. Thus, the slave has its own image and configuration file to be a complete router that can act as a single processor.

Note HSA does not affect performance in terms of packets per second or overall bandwidth. Additionally, HSA does not provide fault-tolerance or redundancy.

HSA Master and Slave Operation

A router configured for HSA operation has one RSP4 card that is the master and one that is the slave. The master RSP4 card functions as if it were a single processor, controlling all functions of the router. The slave RSP4 card does nothing but actively monitor the master for failure. A system crash can cause the master RSP4 to fail or go into a nonfunctional state. When the slave RSP4 detects a nonfunctional master, the slave resets itself and takes part in master-slave arbitration. Master-slave arbitration is a ROM monitor process that determines which RSP4 card is the master and which is the slave upon startup (or reboot).

If a system crash causes the master RSP4 to fail, the slave RSP4 becomes the new master RSP4 and uses its own system image and configuration file to reboot the router. The failed RSP4 card (now the slave) remains inactive until you perform diagnostics, correct the problem, and then issue the slave reload command.

Caution To ensure that the slave RSP4 operates properly with the full system configuration should the master RSP4 ever fail, the slave RSP4 should have the same DRAM configuration as the master RSP4.

With HSA operation, the following items are important:

An RSP4 card that acts as the slave runs a subset of the Cisco IOS software when it acts as the system master. The slave-mode software is a subset of the master-mode software.

The two RSP4 cards do not have to run the same master software image and configuration file. When the slave reboots the system and becomes the new master, it uses its own system image and configuration file to reboot the router.

When enabled, automatic synchronization mode automatically ensures that the master and the slave RSP4 card have the same configuration file. (See the "Software Prerequisites" section.)
Both hardware and software failures can cause the master RSP4 to enter a nonfunctional state, but the system does not indicate the type of failure.
The console is always connected to the master. Thus, your view of the environment is always from the master's perspective.
You must not remove the system master RSP4 while the system is operating; however, the system slave RSP4 can be removed while the system is operating.

Both RSP4s should have the same DRAM and boot ROM configurations. (See the "Hardware Prerequisites" section.)

HSA Implementation Methods

The two common ways to use HSA are as follows:

Simple hardware backup

: Use this method to protect against an RSP4 card failure. With this method, you configure both RSP4 cards with the same software image and configuration information. Also, you configure the router to automatically synchronize configuration information on both cards when changes occur.

Software error protection

: Use this method to protect against critical Cisco IOS software errors in a particular release. With this method, you configure the RSP4 cards with different software images, but with the same configuration information.

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

Similar software versions, but different configuration files
Different software images and different configuration files
Widely varied configuration files (for example, various features or interfaces can be turned off or on per card)

Note Although other, more complex uses of HSA are possible, the configuration information in this publication describes tasks for only the two common uses—simple hardware backup and software error protection.

The following HSA configuration examples specifically refer to a Cisco 7513. The primary difference between the Cisco 7507 (not discusses) and the Cisco 7513, with respect to HSA configuration, is that the RSP master and slave slots in the Cisco 7507 are slot 2 and slot 3 respectively.

HSA System Requirements

To configure HSA operation, you must have a Cisco 7507 or Cisco 7513 containing two RSP4 processor cards and Cisco IOS Release 11.1(8)CA1, or a later release of 11.1 CA1. The slave RSP4 should have the same DRAM configuration as the master RSP4.

Configure HSA Operation Task List

When configuring HSA operation, complete the tasks in the following sections:

The first task is required. Depending on the outcome of the first task, the second or third task is also required. The fourth and fifth tasks are optional.

Determining the HSA Implementation Method to Use

Before you can configure HSA operation, you must first decide how you want to use HSA in your internetwork. Do you want to use HSA 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, proceed to either the "Configuring HSA for Simple Hardware Backup" section or the "Configuring HSA for Software Error Protection" section .

Configuring HSA for Simple Hardware Backup

With the simple hardware backup method, you configure both RSP4 cards with the same software image and configuration information. To configure HSA for simple hardware backup, perform the tasks in the following sections. The first task is optional.

Specifying the Default Slave RSP4

Because your view of the environment is always from the master RSP4's perspective, you must define a default slave RSP4. The router uses the default slave information when booting:

If a system boot is due to powering up the router or using the reload command, then the specified default slave is the slave RSP4.
If a system boot is due to a system crash or hardware failure, then the system ignores the default slave designation and makes the crashed or faulty RSP4 the slave RSP4.

To define the default slave RSP4, perform the following tasks, beginning in global configuration mode:

Tasks
Command

1. Enter the configuration mode from the terminal.

configure terminal

2. Define the default slave RSP4.

slave default-slot processor-slot-number

3. Exit configuration mode.

Ctrl-Z

4. Save this information to your startup configuration.

copy running-config startup-config

Tasks	Command
1. Enter the configuration mode from the terminal.	configure terminal
2. Define the default slave RSP4.	slave default-slot processor-slot-number
3. Exit configuration mode.	Ctrl-Z
4. Save this information to your startup configuration.	copy running-config startup-config

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

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

The following example sets the default slave RSP4 to processor slot 2 on a Cisco 7507:

Router# configure terminal
Router (config)# slave default-slot 2
^Z
Router# copy running-config startup-config

Ensuring That Both RSP4 Cards Contain the Same Images

To ensure that both RSP4 cards have the same system image, perform the following tasks in EXEC mode:

Tasks
Command

1. Display the contents of the BOOT environment variable to learn the current booting parameters for the master and the slave RSP4.

show boot

2. Verify the location and version of the master RSP4 software image.

dir [/all | /deleted] [/long] {bootflash | slot0 | slot1} [filename]

3. Determine whether the slave RSP4 contains the same software image in the same location.

dir [/all | /deleted] [/long] {slavebootflash | slaveslot0 | slaveslot1} [filename]

4. If the slave RSP4 does not contain the same system image in the same location, copy the master's system image to the appropriate slave location.

copy file_id {slavebootflash | slaveslot0 | slaveslot1}

Note that you might also have to use the delete and squeeze commands in conjunction with the copy command to accomplish this step.

Tasks	Command
1. Display the contents of the BOOT environment variable to learn the current booting parameters for the master and the slave RSP4.	show boot
2. Verify the location and version of the master RSP4 software image.	dir [/all \| /deleted] [/long] {bootflash \| slot0 \| slot1} [filename]
3. Determine whether the slave RSP4 contains the same software image in the same location.	dir [/all \| /deleted] [/long] {slavebootflash \| slaveslot0 \| slaveslot1} [filename]
4. If the slave RSP4 does not contain the same system image in the same location, copy the master's system image to the appropriate slave location.	copy file_id {slavebootflash \| slaveslot0 \| slaveslot1} Note that you might also have to use the delete and squeeze commands in conjunction with the copy command to accomplish this step.

The following example ensures that both RSP4 cards have the same system image. Note that because no environment variables are set, the default environment variables are in effect for both the master and the slave RSP4.

Router# show boot
BOOT variable =
CONFIG_FILE variable =
Current CONFIG_FILE variable =
BOOTLDR variable does not exist
Configuration register is 0x0
 
Slave auto-sync config mode is on
 
current slave is in slot 7
BOOT variable =
CONFIG_FILE variable =
BOOTLDR variable does not exist
 
Configuration register is 0x0
 
Router# dir slot0:
-#- -length- -----date/time------ name
1    3482498  May 4  1993 21:38:04 rsp-k-mz11.2
 
7993896 bytes available (1496 bytes used)
 
Router# dir slaveslot0:
-#- -length- -----date/time------ name
1    3482498  May 4  1993 21:38:04 rsp-k-mz11.1
 
7993896 bytes available (1496 bytes used)
 
Router# delete slaveslot0:rsp-k-mz11.1
Router# copy slot0:rsp-k-mz11.2 slaveslot0:rsp-k-mz11.2

To ensure that both RSP4 cards have the same microcode images, perform the following tasks in privileged EXEC mode:

Tasks
Command

1. Determine the microcode images used on the interface processors. If all interface processors are running from the bundled system microcode, no further action is required.

show controller cbus

2. If any interface processors are running from the Flash memory file system, verify the location and version of the master RSP4's supplementary microcode.

dir [/all | /deleted] [/long] {bootflash | slot0 | slot1} [filename]

3. Determine whether the slave RSP4 contains the same microcode image in the same location.

dir [/all | /deleted] [/long] {slavebootflash | slaveslot0 | slaveslot1} [filename]

4. If the slave RSP4 does not contain the same microcode image in the same location, copy the master's microcode image to the appropriate slave location.

copy file_id {slavebootflash | slaveslot0 | slaveslot1}

Note that you might also have to use the delete and squeeze commands in conjunction with the copy command to accomplish this step.

Tasks	Command
1. Determine the microcode images used on the interface processors. If all interface processors are running from the bundled system microcode, no further action is required.	show controller cbus
2. If any interface processors are running from the Flash memory file system, verify the location and version of the master RSP4's supplementary microcode.	dir [/all \| /deleted] [/long] {bootflash \| slot0 \| slot1} [filename]
3. Determine whether the slave RSP4 contains the same microcode image in the same location.	dir [/all \| /deleted] [/long] {slavebootflash \| slaveslot0 \| slaveslot1} [filename]
4. If the slave RSP4 does not contain the same microcode image in the same location, copy the master's microcode image to the appropriate slave location.	copy file_id {slavebootflash \| slaveslot0 \| slaveslot1} Note that you might also have to use the delete and squeeze commands in conjunction with the copy command to accomplish this step.

The following example ensures that both RSP4 cards 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 FSIP processor 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 slave RSP4 has a copy of the same FSIP microcode in the same location.

Router# show controller cbus
MEMD at 40000000, 2097152 bytes (unused 416, recarves 3, lost 0)
  RawQ 48000100, ReturnQ 48000108, EventQ 48000110
  BufhdrQ 48000128 (2948 items), LovltrQ 48000140 (5 items, 1632 bytes)
  IpcbufQ 48000148 (16 items, 4096 bytes)
  3571 buffer headers (48002000 - 4800FF20)
  pool0: 28 buffers, 256 bytes, queue 48000130
  pool1: 237 buffers, 1536 bytes, queue 48000138
  pool2: 333 buffers, 4544 bytes, queue 48000150
  pool3: 4 buffers, 4576 bytes, queue 48000158
  slot0: EIP, hw 1.5, sw 20.00, ccb 5800FF30, cmdq 48000080, vps 4096
    software loaded from system 
    Ethernet0/0, addr 0000.0ca3.cc00 (bia 0000.0ca3.cc00)
      gfreeq 48000138, lfreeq 48000160 (1536 bytes), throttled 0
      rxlo 4, rxhi 42, rxcurr 0, maxrxcurr 2
      txq 48000168, txacc 48000082 (value 27), txlimit 27
                       .........
  slot1: FIP, hw 2.9, sw 20.02, ccb 5800FF40, cmdq 48000088, vps 4096
    software loaded from system 
    Fddi1/0, addr 0000.0ca3.cc20 (bia 0000.0ca3.cc20)
      gfreeq 48000150, lfreeq 480001C0 (4544 bytes), throttled 0
      rxlo 4, rxhi 165, rxcurr 0, maxrxcurr 0
      txq 480001C8, txacc 480000B2 (value 0), txlimit 95
  slot4: AIP, hw 1.3, sw 20.02, ccb 5800FF70, cmdq 480000A0, vps 8192
    software loaded from system 
    ATM4/0, applique is SONET (155Mbps)
      gfreeq 48000150, lfreeq 480001D0 (4544 bytes), throttled 0
      rxlo 4, rxhi 165, rxcurr 0, maxrxcurr 0
      txq 480001D8, txacc 480000BA (value 0), txlimit 95
  slot9: MIP, hw 1.0, sw 20.02, ccb 5800FFC0, cmdq 480000C8, vps 8192
    software loaded from system 
    T1 9/0, applique is Channelized T1
      gfreeq 48000138, lfreeq 480001E0 (1536 bytes), throttled 0
      rxlo 4, rxhi 42, rxcurr 0, maxrxcurr 0
      txq 480001E8, txacc 480000C2 (value 27), txlimit 27
                    .......
 
  slot10: TRIP, hw 1.1, sw 20.00, ccb 5800FFD0, cmdq 480000D0, vps 4096
    software loaded from system 
    TokenRing10/0, addr 0000.0ca3.cd40 (bia 0000.0ca3.cd40)
      gfreeq 48000150, lfreeq 48000200 (4544 bytes), throttled 0
      rxlo 4, rxhi 165, rxcurr 1, maxrxcurr 1
      txq 48000208, txacc 480000D2 (value 95), txlimit 95
                   .........
                     
  slot11: FSIP, hw 1.1, sw 20.01, ccb 5800FFE0, cmdq 480000D8, vps 8192
    software loaded from flash slot0:pond/bath/rsp_fsip20-1 
    Serial11/0, applique is Universal (cable unattached)
      gfreeq 48000138, lfreeq 48000240 (1536 bytes), throttled 0
      rxlo 4, rxhi 42, rxcurr 0, maxrxcurr 0
      txq 48000248, txacc 480000F2 (value 5), txlimit 27
                  ...........
Router# dir slot0:pond/bath/rsp_fsip20-1
-#- -length- -----date/time------ name
3   10242    Jan 01 1995 03:46:31 pond/bath/rsp_fsip20-1
 
Router# dir slaveslot0:pond/bath/rsp_fsip20-1
No such file
 
4079832 bytes available (3915560 bytes used)
 
Router# copy slot0:pond/bath/rsp_fsip20-1 slaveslot0:
4079704 bytes available on device slaveslot0, proceed? [confirm]
 
Router# dir slaveslot0:pond/bath/rsp_fsip20-1                     
-#- -length- -----date/time------ name
3   10242    Mar 01 1993 02:35:04 pond/bath/rsp_fsip20-1
 
4069460 bytes available (3925932 bytes used)
Router#

Ensuring That Both RSP4 Cards Contain the Same Configuration File

With the simple hardware backup and software error protection implementation methods, you always want your master and slave configuration files to match. To ensure that they match, turn on automatic synchronization. In automatic synchronization mode, the master copies its startup configuration to the slave's startup configuration when you issue a copy command that specifies the master's startup configuration (startup-config) as the target.

Automatic synchronization mode is on by default; however, to turn it on manually, perform the following tasks in global configuration mode:

Tasks
Command

1. Enter the configuration mode from the terminal.

configure terminal

2. Turn on automatic synchronization mode.

slave auto-sync config

3. Exit configuration mode.

Ctrl-Z

4. Save this information to your startup configuration and copy the configuration to the slave's startup configuration.

copy running-config startup-config

The following example turns on automatic configuration file synchronization:

Router# configure terminal
Router (config)# slave auto-sync config
Router (config)# ^Z
Router# copy running-config startup-config

Configuring HSA for Software Error Protection

With the software error protection method, you configure the RSP4 cards with different software images, but with the same configuration information. To configure HSA for software error protection, perform the tasks in the following sections. (The first task is optional.)

Specifying the Default Slave RSP4 (in the previous section "Configuring HSA for Simple Hardware Backup")
Ensuring That Both RSP4 Cards Contain the Same Configuration File (in the previous section "Configuring HSA for Simple Hardware Backup")
Specifying Different Startup Images for the Master and the Slave RSP4 (which follows)

Specifying Different Startup Images for the Master and the Slave RSP4

When the factory sends you a new router with two RSPs, you receive the same system image on both RSP4 cards. To configure the HSA feature for software error protection, you need two separate software images on the RSP4 cards. Thus, you copy a desired image to the master RSP4 card and modify the boot system commands to reflect booting two separate system images. Each RSP4 card uses its own image to boot the router when it becomes the master.

To specify different startup images for the master and the slave RSP4, perform the following tasks in EXEC mode:

Tasks
Command

1. Verify the location and version of the master RSP4 software image.

dir [/all | /deleted] [/long] {bootflash | slot0 | slot1} [filename]

2. Determine whether the slave RSP4 contains the same software image in the same location.

dir [/all | /deleted] [/long] {slavebootflash | slaveslot0 | slaveslot1} [filename]

3. Copy a different system image to the master RSP4.

copy file_id {bootflash | slot0 | slot1}

copy flash {bootflash | slot0 | slot1}

copy rcp {bootflash | slot0 | slot1}

copy tftp {bootflash | slot0 | slot1}

4. Enter configuration mode from the terminal.

configure terminal

5. From global configuration mode, configure the master RSP4 to boot the new image from the appropriate location.

boot system flash bootflash:[filename]
boot system flash slot0:[filename]
boot system flash slot1:[filename]

6. Also, add a boot system command that specifies the slave's boot image and location. This is the boot image that the slave uses when it becomes the master RSP4 and boots the system. Note that because the slave boots this image when the slave is actually the new master RSP4, the command syntax does not use a "slave" prefix.

boot system flash bootflash:[filename]
boot system flash slot0:[filename]
boot system flash slot1:[filename]

7. Configure the master RSP4 to boot from a network server.

boot system [rcp | tftp] filename [ip-address]

8. Set the configuration register to enable loading of the system image from a network server or Flash memory.

config-register value ¹

9. Exit configuration mode.

Ctrl-Z

10. Save the configuration file to the master's startup configuration. Because automatic synchronization is turned on, this step saves the boot system commands to the master and the slave startup configuration.

copy running-config startup-config

11. Reset the router with the new configuration information.

reload

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

In the following sample scenario, assume the following:

The master RSP4 is in processor slot 6, and the slave RSP4 is in processor slot 7 of a Cisco 7513.
The system has the same image, rsp-k-mz11.1, in PCMCIA slot 0 of both the master and the slave RSP4 card.
You want to upgrade to Cisco IOS Release 11.2, but you want to guard against software failures. So you must configure HSA operation for software error protection.

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

Figure 8: Software Error Protection: Upgrading to a New Software Version

Because you always view the environment from the master RSP4's perspective, in the following command you view the master's slot 0 to verify the location and version of the master's software image:

Router# dir slot0:
-#- -length- -----date/time------ name
1    3482496  May 4  1993 21:38:04 rsp-k-mz11.1
 
7993896 bytes available (1496 bytes used)

Now view the slave's software image location and version:

Router# dir slaveslot0:
-#- -length- -----date/time------ name
1    3482496  May 4  1993 21:38:04 rsp-k-mz11.1
 
7993896 bytes available (1496 bytes used)

Because you want to run the Release 11.2 system image on one RSP4 card and the Release 11.1 system image on the other RSP4 card, copy the Release 11.2 system image to the master's slot 0:

Router# copy tftp slot0:rsp-k-mz11.2

Enter global configuration mode and configure the system to boot first from a Release 11.2 system image and then from a Release 11.1 system image.

Router# configure terminal
Router (config)# boot system flash slot0:rsp-k-mz11.2
Router (config)# boot system flash slot0:rsp-k-mz11.1

With this configuration, when the slot 6 RSP4 card is master, it looks first in its PCMCIA slot 0 for the system image file rsp-k-mz11.2 to boot. Finding this file, the router boots from that system image. When the slot 7 RSP4 card is master, it also looks first in its slot 0 for the system image file rsp-k-mz11.2 to boot. Because that image does not exist in that location, the slot 7 RSP4 card looks for the system image file rsp-k-mz11.1 in slot 0 to boot. Finding this file in its PCMCIA slot 0, the router boots from that system image. In this way, each RSP4 card can reboot the system using its own system image when it becomes the master RSP4 card.

Configure the system further with a fault-tolerant booting strategy:

Router (config)# boot system tftp rsp-k-mz11.1 1.1.1.25

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 master and the slave startup configuration file:

Router (config)# config-register 0x010F
Router (config)# ^Z
Router# copy running-config startup-config

Reload the system so that the master RSP4 uses the new Release 11.2 system image:

Router# reload

In the following sample scenario, assume the following:

The master RSP4 is in processor slot 6, and the slave RSP4 is in processor slot 7 of a Cisco 7513.
The system has the same image, rsp-k-mz11.2, in PCMCIA slot 0 of both the master and the slave RSP4 card.
You want to use to Cisco IOS Release 11.1 as backup to guard against software failures. So you configure HSA operation for software error protection.

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

Figure 9: Software Error Protection: Backing Up with an Older Software Version, Part I

Next, you copy the rsp-k-mz11.1 image to the master and the slave RSP4 card, as shown in Figure 10.

Figure 10: Software Error Protection: Backing Up with an Older Software Version, Part I1

Last, delete the rsp-k-mz11.2 image from the slave RSP4 card, as shown in Figure 11:

Figure 11: Software Error Protection: Backing Up with an Older Software Version, Part III

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

View the master and the slave slot 0 to verify the location and version of their software images:

Router# dir slot0:
-#- -length- -----date/time------ name
1    3482498  May 4  1993 21:38:04 rsp-k-mz11.2
 
7993896 bytes available (1496 bytes used)
 
Router# dir slaveslot0:
-#- -length- -----date/time------ name
1    3482498  May 4  1993 21:38:04 rsp-k-mz11.2
 
7993896 bytes available (1496 bytes used)

Copy the Release 11.1 system image to the master and the slave slot 0:

Router# copy tftp slot0:rsp-k-mz11.1
Router# copy tftp slaveslot0:rsp-k-mz11.1

Delete the rsp-k-mz11.2 image from the slave RSP4 card:

Router# delete slaveslot0:rsp-k-mz11.2

Configure the system to boot first from a Release 11.2 system image and then from a Release 11.1 system image.

Router# configure terminal
Router (config)# boot system flash slot0:rsp-k-mz11.2
Router (config)# boot system flash slot0:rsp-k-mz11.1

Configure the system further with a fault-tolerant booting strategy:

Router(config)# boot system tftp rsp-k-mz11.1 1.1.1.25

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 master and the slave startup configuration file:

Router(config)# config-register 0x010F
Crtl-z
Router# copy running-config startup-config

Note You do not need to reload the router in this example, because the router is currently running the Release 11.2 image.

Setting Environment Variables on the Master and the Slave RSP4

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

Note When you configure 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 RSP4 card. For example, if you set one RSP4 card's CONFIG_FILE environment variable device to NVRAM, then set the other RSP4 card's CONFIG_FILE environment variable device to NVRAM also.

You set environment variables on the master RSP4 just as you would if it were the only RSP4 card in the system. You can set the same environment variables on the slave RSP4 card, 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 on the Documentation CD-ROM or as printed copies.

Manually Setting Environment Variables on the Slave RSP4

Once you set the master's environment variables, you can manually set the same environment variables on the slave RSP4 card using the slave sync config command.

To manually set environment variables on the slave RSP4, perform the following steps in global configuration mode:

Tasks
Command

1. Set the master's environment variables. For more complete HSA 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 copies.

boot system

boot bootldr

boot config

2. Save the settings to the startup configuration. This also puts the information under that RSP4 card's ROM monitor control.

copy running-config startup-config

3. Save the same environment variables to the slave RSP4 by manually synchronizing their configuration files.

slave sync config

4. Verify the environment variable settings.

show boot

Automatically Setting Environment Variables on the Slave RSP4

With automatic synchronization turned on, when you set the master's environment variables and save them, the system automatically saves the same environment variables to the slave's startup configuration.

Note Automatic synchronization mode is on by default.

To set environment variables on the slave RSP4 when automatic synchronization is on, perform the following steps in global configuration mode:

Tasks
Command

1. Set the master's environment variables. For more complete HSA 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 copies.

boot system

boot bootldr

boot config

2. Save the settings to the startup configuration. This also puts the information under that RSP4 card's ROM monitor control.

copy running-config startup-config

3. Verify the environment variable settings.

show boot

Monitoring and Maintaining HSA Operation

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

Tasks
Command

Specify which image the slave runs.

slave image {system | device:filename}

You can manually synchronize configuration files and ROM monitor environment variables on the master and the slave RSP4 card. To do so, perform the following task in privileged EXEC mode:

Tasks
Command

Manually synchronize master and slave configuration files.

slave sync config

Caution When you install a second RSP4 card for the first time, you must immediately configure it using the slave sync config command. This ensures that the new slave is configured consistently with the master. Failure to do so might result in an unconfigured slave RSP4 card taking control of the router when the master 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 or as printed copies.

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 RSP4(s) 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 overtemperature 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 on the Documentation CD-ROM or in print.

RSP4 LEDs

Figure 12 shows the LEDs on the RSP4 faceplate. The LEDs on the RSP4 indicate the system and RSP4 status and which Flash memory 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 RSP4 is receiving +5V. The slot 0 and slot 1 LEDs indicate which PCMCIA (Flash memory) card slot is in use, and each LED blinks when the card is accessed by the system. The master and the slave LEDs provide a visual indication of whether the RSP4 is designated a master or a slave device.

Figure 12: RSP4 LEDs, Master/Slave Switch, and Reset Switch
(Vertical Partial Front-Panel View)

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

Interface Processor LEDs

Each interface processor contains an enabled LED. The enabled LED goes on to indicate that the interface processor is operational and that it is powered up. It does not necessarily mean that the interface ports on the interface processors are functional or enabled. When the boot sequence is complete, all the enabled LEDs should go on.

If any do not, one of the following errors is indicated:

The interface processor is not installed correctly (it is not fully seated in the backplane connector)
The microcode and software that are loading at startup are not compatible
The interface processor has failed

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 normal startup sequence to isolate the problem, 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 end of this document 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. If your router 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:

%SYS-5-RELOAD: Reload requested
System Bootstrap, Version 11.1(8)CA1
Copyright (c) 1986-1996 by cisco Systems, Inc.
 
[System initializes memory at this point in the display]

Note The procedures in this section are based on the assumption that your system was operating correctly until you removed (or replaced) the RSP4. If the following sequence indicates 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:

1. When you restart the system, the system power and AC (DC) OK LEDs should go on.

If the system power LED remains off, the RSP4 is probably not fully inserted and connected to the backplane. Loosen the captive installation screws on the RSP4, then use the ejector levers to release the RSP4 and reseat it in the backplane. (For a description and illustration of the ejector levers, see the "Replacing the RSP4" section.) Tighten both captive installation screws.

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

If the system power LED goes on, the power source is good, and the power supply is functional.

: When the system power LED indicates normal operation, proceed to the following item.

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.

3. When you have verified that the power supply is functioning properly, observe the LEDs on the RSP4. The CPU halt LED on the RSP4 should always remain off. If it goes on during the startup sequence, the system has encountered a processor hardware error.

Use the show version command to check the current configuration register settings.
If the CPU halt LED goes on during a second startup attempt, suspect a processor hardware error and contact a service representative.

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.

5. When the system boot is complete, the RSP4 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.

If the enabled LEDs on the interface processors go on, the system has booted successfully and is now functional.

If the RSP4 LEDs previously indicated a successful system boot, but none of the enabled LEDs on the interface processors go on, suspect that one of the interface processors has shifted out of its backplane connector and halted the system. Use the ejector levers to release the interface processor and reseat it in the backplane. (For an illustration of the ejector levers, see Figure 4.) Tighten both captive installation screws.
If the enabled LED on a single interface processor remains off, suspect that the interface processor has shifted out of its slot. Use the ejector levers to release the interface processor and reseat it in the backplane. (For an illustration of the ejector levers, see Figure 4.) Tighten both captive installation screws. After the system reinitializes the interfaces, the enabled LED on the interface processor should go on.
If an enabled LED still fails to go on after you perform these steps, suspect that the specific interface processor has failed.

6. When the system boot is complete and all interface processors have been initialized, the master RSP4's console screen displays a script and a system banner similar to the following:

System Bootstrap, Version 11.1(8)CA1, RELEASED SOFTWARE
Copyright (c) 1986-1996 by cisco Systems, Inc.
SLOT 6 RSP4 is system master (SLOT 2 for a Cisco 7507)
SLOT 7 RSP4 is system slave (SLOT 3 for a Cisco 7507, if installed)
RSP4 processor with 32 Mbytes of main memory
 
ROM: System Bootstrap, Version 11.1(2) [biff 2], RELEASE SOFTWARE (fc1)
ROM: GS Bootstrap Software (RSP-BOOT-M), Version 10.3(7), RELEASE SOFTWARE
 
Warning: monitor nvram area is corrupt ... using default values
SLOT 2 RSP4 is system master
SLOT 3 RSP4 is system slave
RSP4 processor with 32 Mbytes of main memory
 
[additional displayed text omitted from this example]

If all the previous conditions are met and this banner is displayed, the system startup was successful and your installation is complete.
If an error message is displayed on the terminal, refer to the appropriate software publication for error message definitions.
If the console screen is blank, check the terminal to ensure that it is turned on and that the console cable is correctly connected between the terminal and the console port on the RSP4.
Check the terminal settings to ensure that the terminal is set for 9600 baud, 8 data bits, no parity, and 2 stop bits.
If the terminal is set correctly and still fails to operate, suspect that the terminal is faulty. Connect a different terminal and restart the system.

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.

Troubleshooting a Failed RSP4

When a new master RSP4 takes over ownership of the router, it automatically reboots the failed RSP4 as the slave RSP4. You can access the state of the failed RSP4 in the form of a stack trace from the master console using the show stacks command.

You can also manually reload a failed RSP4 from the master console. To do so, perform the following task from global configuration mode:

Tasks
Command

Reload the inactive slave RSP card.

slave reload

Displaying Information about the Master and the Slave RSP4

You can also display information about the master and the slave RSP4s. To do so, perform any of the following tasks from EXEC mode:

Tasks
Command

Display the environment variable settings and configuration register settings for the master and the slave RSP cards.

show boot

Show a list of flash devices currently supported on the router.

show flash devices

Display the software version running on the master and the slave RSP card.

show version

Display the stack trace and version information of the master and the slave RSP cards.

show stacks ¹

¹This command is documented in the "System Management Commands" chapter of the Configuration Fundamentals Command Reference publication.

Reference Information

The following sections include important reference information and configuration and maintenance procedures for the RSP4. The following sections are included:

Console Port Signals

The console port on the RSP4 is an EIA/TIA-232, DCE, DB-25 receptacle. Both DSR and DCD are active when the system is running. The RTS signal tracks the state of the 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 3 lists the signals used on this port.

Table 3: Console Port Signals

Pin Signal Direction Description

1

GND

-

Ground

2

TxD

<—

Transmit Data

3

RxD

—>

Receive Data

6

DSR

—>

Data Set Ready (always on)

7

GND

-

Ground

8

DCD

—>

Data Carrier Detect (always on)

Auxiliary Port Signals

The auxiliary port on the RSP4 is an EIA/TIA-232 DTE, DB-25 plug to which you can attach a CSU/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 4 lists the signals used on this port.

Table 4: Auxiliary Port Signals

Pin Signal Direction Description

2

TxD

—>

Transmit Data

3

RxD

<—

Receive Data

4

RTS

—>

Request To Send (used for hardware flow control)

5

CTS

<—

Clear To Send (used for hardware flow control)

6

DSR

<—

Data Set Ready

7

Signal Ground

-

Signal Ground

8

CD

<—

Carrier Detect (used for modem control)

20

DTR

—>

Data Terminal Ready (used for modem control only)

Console and Auxiliary Y-Cable Pinouts

The console and auxiliary Y-cables allow you to simultaneously connect the console ports or auxiliary ports on two RSP4s (configured as system master and slave in RSP slots 2 and 3 in the Cisco 7507, and RSP slots 6 and 7 in the Cisco 7513) to one console terminal or external auxiliary device (such as a modem, and so forth).

The two Y-cables (CAB-RSP4CON=, shown in Figure 6, and CAB-RSP4AUX=, shown in Figure 7) ship with the router and are available as spare parts. The console Y-cable pinout is listed in Table 5, and the auxiliary Y-cable pinout is listed in Table 6.

Table 5: Console Y-Cable Signals (CAB-RSP4CON=)

Female DB-25 Pins Male DB-25 Pins Signal Description

P1-1

J1-1 and J2-1

Ground)

P1-2

J1-2, and J2-2

Receive Data (RxD)

P1-3

J1-3 and J2-3

Transmit Data (TxD)

P1-4

J1-4 and J2-4

Clear To Send (CTS); looped to 5

P1-5

J1-5 and J2-5

Request To Send (RTS); looped to 4

P1-6

J1-6 and J2-6

Data Set Ready (DSR)

P1-7

J1-7 and J2-7

Ground

P1-8

J1-8 and J2-8

Data Carrier Detect (DCD)

P1-13

J1-13 and J2-13

YCBL Detect Ground

P1-19

J1-19 and J2-19

YCBL Detect

P1-20

J1-20 and J2-20

Data Terminal Ready (DTR)

Table 6: Auxiliary Y-Cable Signals (CAB-RSP4AUX=)

Male DB-25 Pins Female DB-25 Pins Signal Description

P1-1

J1-1 and J2-1

Ground

P1-2

J1-2 and J2-2

TxD

P1-3

J1-3 and J2-3

RxD

P1-4

J1-4 and J2-4

RTS

P1-5

J1-5 and J2-5

CTS

P1-7

J1-7 and J2-7

Ground

P1-8

J1-8 and J2-8

DCD

P1-13

J1-13 and J2-13

YCBL Detect

P1-19

J1-19 and J2-19

YCBL Detect Ground

P1-20

J1-20 and J2-20

DTR

P1-22

J1-22 and J2-22

Ring

Replacing and Upgrading DRAM DIMMs

This section describes the steps for increasing the amount of DRAM by replacing up to two dual in-line memory modules (DIMMs), which you obtain from Cisco Systems.

The system DRAM resides on up to two DIMMs on the RSP4. The DRAM DIMM sockets are U10 (bank 0) and U13 (bank 1). (See Figure 13 and Table 7.) The default DRAM configuration is 32 MB (one 32-MB DIMM in U10) for the RSP4; the default DRAM configuration is 64 MB (one 32-MB DIMM in U10 and U13) for the RSP4+. If two different sizes of DRAM DIMMs are installed, U10 must contain the larger DRAM DIMM.

Caution To prevent system problems, do not use DRAM single in-line memory modules (SIMMs) from an RSP2 in the RSP4. The RSP4 requires DRAM dual in-line memory modules (DIMMs).

Note The total number of memory devices per DIMM differs for each manufacturer. The DIMMs in the following illustrations are generic representations of the actual DRAM DIMMs for your RSP4.

Figure 13: RSP4 DRAM DIMM Locations

Note Each RSP4 DIMM socket has one plastic lever on one end, which is used to remove the DIMM from its socket. (See Figure 14.)

Before proceeding, ensure that you have the proper tools and ESD-prevention equipment available. To upgrade DRAM, you install DIMMs in one or two banks (U10 and U13). Table 7 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.

Depending on your router's configuration and the protocols and features your system is running, you might require more than 32 MB of DRAM for your RSP4. Upgrade your system DRAM based on your current configuration, this potential requirement, and the information in Table 7.

Table 7: DRAM DIMM Configurations

DRAM Sockets Quantity Totals Product Numbers

U10

One 32-MB DIMM

32 MB

MEM-RSP4-32M¹

U13

One 32-MB DIMM

32 MB²

MEM-RSP4-32M=²

U10 and U13

Two 32-MB DIMMs

64 MB

MEM-RSP4-64M^³

U10

One 128-MB DIMM

128 MB

MEM-RSP4-128M(=)

U10 and U13

Two 128-MB DIMMs

256 MB

MEM-RSP4-256M(=)

¹This is the standard (default) DRAM configuration for the RSP4.
²This DRAM option assumes you already have one 32-MD DRAM DIMM installed in U10 and want to upgrade to 64 MB of DRAM by adding a second 32-MB DRAM DIMM to U13.
³This is the standard (default) DRAM configuration for the RSP4+.

Two different sizes of DRAM DIMMs can occupy the two DRAM DIMM sockets (U10 and U13); however, the larger DRAM DIMM must occupy the U10 socket.

Caution To prevent system and memory problems when installing one 128-MB DIMM on an RSP4 with one 32-MB DRAM DIMM in U10, remember that U10 must contain the largest DRAM DIMM; therefore, install the 128-MB DIMM in U10, only after you move the 32-MB DRAM DIMM to U13.

Removing DIMMs

This section discusses the procedure for removing DIMMs from your RSP4.

Note If you plan to upgrade from 64 MB to 256 MB, you must replace both DRAM DIMMs; therefore, the following procedure is required. However, this procedure is not required if you want to add one DIMM to a DRAM configuration that uses only one DIMM. For example, if you want to upgrade from 32 MB to 64 MB or from 128 MB to 256 MB, you need to add one DRAM DIMM to U13; therefore, proceed to the "Installing New DIMMs" section.

Use this procedure to remove the existing DIMM(s):

Step 1 Turn OFF the system power and follow the steps in the "Removing the RSP4" section.

Step 2 Place the RSP4 on an antistatic mat or pad and ensure that you are wearing an antistatic device, such as a wrist strap.

Step 3 Position the RSP4 so that the faceplate is toward you and the bus connectors are away from you—this position is shown in Figure 13.

Step 4 Locate the DRAM DIMMs on the RSP4. The DIMMs occupy U10 (bank 0) and U13 (bank 1). (See Figure 13.)

Step 5 For the DIMM you want to remove, pull down the lever on the DIMM socket to release the DIMM from the socket. (See Figure 14.)

Figure 14: Using the DIMM Socket's Release Lever to Remove a DIMM

Step 6 When one end of the DIMM is released from the socket, grasp each end of the DIMM with your thumb and forefinger and pull the DIMM completely out of the socket. Handle the edges of the DIMM only (see Figure 15); avoid touching the memory module or pins and the metal traces, or fingers, along the socket edge.

Step 7 Place the DIMM in an antistatic bag 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.

Installing New DIMMs

This section discusses the procedure for installing DIMMs on your RSP4.

Note If you are upgrading from 32 MB to 64 MB or from 128 MB to 256 MB, you need to add one DRAM DIMM to U13; therefore, the following procedure is required. Two different sizes of DRAM DIMMs can occupy the two DRAM DIMM sockets (U10 and U13); however, the larger DRAM DIMM must occupy the U10 socket.

Caution To prevent system and memory problems when you install DRAM, the RSP4's DRAM DIMMS must be 3.3-V devices. Do not attempt to install higher-voltage devices (such as those designed for the RSP2) in the RSP4's DIMM sockets. Further, DIMMs are sensitive components that can be shorted by mishandling; they are susceptible to ESD damage. Handle DIMMs by the edges only; avoid touching the DIMMs, pins, or traces (the metal fingers along the connector edge of the DIMM). (See Figure 15 .)

Figure 15: Handling a DIMM

Use this procedure to install new DIMMs:

Step 1 Place the RSP4 on an antistatic mat or pad, and ensure that you are wearing an antistatic device, such as a wrist strap.

Step 2 Position the RSP4 so that the faceplate is toward you and the bus connectors are away from you, as shown in Figure 13.

Caution To prevent system problems and grounding problems if you plan to install one 128-MB DIMM for the 128-MB DRAM option or two 128-MB DRAM DIMMs for the 256-MB DRAM option, you must first install a protective post on the RSP4. (See Figure 16.) The protective post prevents the tops of installed 128-MB DRAM DIMMs from coming into contact with the metal carrier on an adjacent card when you install or remove your RSP4; this procedure is required if you plan to install any 128-MB DIMMs.

Figure 16: Protective Post for an RSP4 with 128-MB DRAM DIMMs

Note The protective post ships with the 128-MB DRAM DIMM kits.

Proceed to Step 3 to install the post; Steps 3 through 6 are required only if you plan to install 128-MB DRAM DIMMs.

If you do not plan to install 128-MB DRAM DIMMs, proceed to Step 7.

Step 3 With the RSP4 positioned as shown in Figure 17 , locate the screw shown in the enlargement; this is where you attach the protective post to your RSP4.

Figure 17: Determining the Placement for the Protective Post on Your RSP4

Step 4 Carefully remove the screw from the RSP4 using a screwdriver. (See Figure 18a.)

Step 5 Insert the screw through the screw hole in the base of the post. (See Figure 18b.)

Caution To prevent damaging the RSP4's printed circuit board, do not overtighten the screw.

Step 6 Position the post correctly; attach the screw and post to the RSP4. (See Figure 18c.) Carefully note the proper orientation of the protective post, as shown in Figure 18c.

Note After you install the protective post on your RSP4, proceed to Step 7.

Figure 18: Installing the Protective Post on Your RSP4

Step 7 Remove a new DIMM from its antistatic bag or box.

Step 8 Hold the DIMM component-side up, with the connector edge (the metal fingers) closest to you. Hold the ends of the DIMM between your thumb and forefinger. (See Figure 15 .)

Step 9 Tilt the DIMM to approximately the same angle as the socket and insert the entire the connector edge into the socket. Note the two notches (keys) on the connector edge of the DIMM. (See Figure 15 .) These keys are intended to ensure correct orientation of the DIMM in the socket.

Step 10 Note the orientation of the socket key on the DIMM (see Figure 15) and the DIMM socket and gently push the DIMM into the socket until the lever is flush against the side of the DIMM socket (see Figure 19), and the DIMM edge connector is fully inserted. If necessary, rock the DIMM gently back and forth to seat it properly.

Figure 19: Installing a DRAM DIMM in the DIMM Socket

Step 11 When the DIMM is installed, check that the release lever is flush against the side of the DIMM socket. (See Figure 19.) If it is not, the DIMM might not be seated properly. If the DIMM appears misaligned, carefully remove it according to the removal procedure, and reseat it in the socket. Push the DIMM firmly back into the socket until the release lever is flush against the side of the DIMM socket.

Caution When inserting DIMMs, use firm but not excessive pressure. If you damage a socket, you will have to return the RSP4 to the factory for repair.

Step 12 Repeat Step 7 through Step 11 for the remaining DIMM, as required for your DRAM configuration.

This completes the procedure for installing DRAM DIMMs. Proceed to the following section to check the installation.

Checking the DIMM Installation

This section provides information for checking the DIMM installation.

Note The 128-MB DRAM DIMMs require that you first install a protective post that shipped with your 128-MB DRAM DIMM kit, on your RSP4; verify that the protective post is installed. If the post is not installed, follow Steps Step 3 through Step 6 in the section ""Installing New DIMMs" section" to install the protective post.

If the system fails to boot properly or if the console terminal displays a checksum or memory error after you have installed new DIMMs and reinstalled the RSP4, check the following:

Ensure that all DIMMs are installed correctly. If necessary, shut down the system and remove the RSP4. Check the DIMMs by looking straight down on them to inspect them at eye level. The DIMMs should all be aligned at the same angle and the same height when properly installed. If a DIMM appears to stick out or rest in the socket at a different angle from the others, remove the DIMM and reinsert it. Then replace the RSP4 and reboot the system for another installation check.
In DRAM configurations with two DRAM DIMMs, each bank can contain a DIMM of a different memory size; however, the larger DRAM DIMM must occupy the U10 socket, or else the system might not operate properly. Further, all DIMMs must operate at 60 ns or faster; the speed is printed along one edge of the DIMM.

If after several attempts the system fails to restart properly, contact 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.

To replace the RSP4 in the router, proceed to the "Replacing the RSP4" section, and then restart the system for an RSP4 installation check.

Software Configuration Register Settings

Settings for the 16-bit software configuration register are written into the NVRAM. Following are some reasons for changing the software configuration register settings:

To select a boot source and default boot filename
To enable or disable the Break function
To control broadcast addresses
To set the console terminal baud rate
To load operating software from Flash memory
To enable booting from a Trivial File Transfer Protocol (TFTP) server
To recover a lost password
To allow you to manually boot the system using the b command at the bootstrap program prompt
To force the router to boot automatically from the system bootstrap software (boot image) or from its default system image in onboard Flash memory, and to read any boot system commands that are stored in the configuration file in NVRAM.

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

Table 8 lists the meaning of each of the software configuration memory bits, and Table 9, 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 8. For example, the factory default value of 0x0101 is a combination of settings.

Table 8: Software Configuration Register Bit Meanings

Bit Number¹ Hexadecimal Meaning

00 to 03

0x0000 to 0x000F

Boot field (see Table 9)

06

0x0040

Causes system software to ignore NVRAM contents

07

0x0080

OEM bit enabled²

08

0x0100

Break disabled

09

0x0200

Use secondary bootstrap

10

0x0400

Internet Protocol (IP) broadcast with all zeros

11 to 12

0x0800 to 0x1000

Console line speed (default is 9600 baud)

13

0x2000

Boot default Flash memory software if network boot fails

14

0x4000

IP broadcasts do not have network numbers

15

0x8000

Enable diagnostic messages and ignore NVRAM contents

¹The factory default value for the configuration register is 0x0101. This value is a combination of the following: bit 8 = 0x0100 and bits 00 through 03 = 0x0001 (see Table 9).
²OEM = original equipment manufacturer.

Table 9: Explanation of Boot Field (Software Configuration Register Bits 00 to 03)

Boot Field Meaning

00

Stays at the system bootstrap prompt

01

Boots the first system image in onboard Flash memory

02 to 0F

Specifies a default netboot filename Enables boot system commands that override the default netboot filename

Changing Settings

To change the configuration register while running the system software, follow these steps:

Step 1 Enter the enable command and your password to enter privileged level, as follows:

Router> enable
Password: 
router#

Step 2 At the privileged-level system prompt (router #), enter the configure terminal command. You are prompted, as shown in the following example:

Router# conf t
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#

Step 3 To set the contents of the configuration register, enter the config-register value configuration command, where value is a hexadecimal number preceded by 0x
(see Table 8), as in the following:

Router(config)# config-register 0xvalue

Step 4 Exit the configuration mode by entering Ctrl-Z. The new value settings are saved to memory; however, the new settings do not take effect until the system software is reloaded by rebooting 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 EXEC command. The value is displayed on the last line of the screen display, as in the following example:

Configuration register is 0x141 (will be 0x101 at next reload)

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 for changing settings.

Bit Meanings

The lowest four bits of the software configuration register (bits 3, 2, 1, and 0) form the boot field. (See Table 9.) 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:

> b [tftp] flash filename

Definitions of the various b command options follow:

b—Boots the default system software from Flash memory
b flash—Boots the first file in onboard Flash memory
b slot0: filename—Boots the file filename from the Flash memory card in PCMCIA slot 0
b slot1: filename—Boots the file filename from the Flash memory card in PCMCIA slot 1
b filename [host]—Boots from server host using TFTP
b bootflash: [filename]—Boots the file filename from onboard Flash memory

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

Router# conf term
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)# config-register 0x102
Router(config)# boot system flash [filename]
Crtl-z
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 10 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.

Table 10: Default Boot Filenames

Action/Filename Bit 3 Bit 2 Bit 1 Bit 0

Bootstrap mode

0

0

0

0

Default software

0

0

0

1

cisco2-RSP

0

0

1

0

cisco3-RSP

0

0

1

1

cisco4-RSP

0

1

0

0

cisco5-RSP

0

1

0

1

cisco6-RSP

0

1

1

0

cisco7-RSP

0

1

1

1

cisco10-RSP

1

0

0

0

cisco11-RSP

1

0

0

1

cisco12-RSP

1

0

1

0

cisco13-RSP

1

0

1

1

cisco14-RSP

1

1

0

0

cisco15-RSP

1

1

0

1

cisco16-RSP

1

1

1

0

cisco17-RSP

1

1

1

1

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 11 shows the combined effect of bits 10 and 14.

Table 11: Configuration Register Settings for Broadcast Address Destination

Bit 14 Bit 10 Address (<net> <host>)

Off

Off

<ones> <ones>

Off

On

<zeros> <zeros>

On

On

<net> <zeros>

On

Off

<net> <ones>

Bits 11 and 12 in the configuration register determine the baud rate of the console terminal. Table 12 shows the bit settings for the four available baud rates. (The factory-set default baud rate is 9600.)

Table 12: System Console Terminal Baud Rate Settings

Baud Bit 12 Bit 11

9600

0

0

4800

0

1

1200

1

0

2400

1

1

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.

Using the Software Configuration Register to Enable Booting from Flash Memory

To enable booting 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 configuration mode while in the system software image and specify a Flash memory filename from which to boot, enter the configure terminal command at the enable prompt, as follows:

Router# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)# boot system flash device:filename

To disable the Break function and enable the boot system flash device:filename command, enter the config-register command with the value shown in the following example:

Router(config)# config-reg 0x0102
Crtl-z
Router#

Recovering a Lost Password

An overview of recovering a lost password follows:

Enter the show version command to note the existing software configuration register value.
Break to the bootstrap program prompt.
Change the configuration register to ignore NVRAM.

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.

Enter privileged level in the system EXEC.

Enter the show startup-configuration command to display the enable password.
Change the configuration register value back to its original setting.

To recover a lost password, follow these procedures.

Note If the enable password is encrypted, the following procedure does not work for password recovery and you must reconfigure the router using the displayed configuration (shown in Step 11), instead of being rebooted.

Step 1 Attach an ASCII terminal to the router console port, which is located on the rear panel.

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 Enter 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 the Break key or send a break (^[) and then proceed to Step 5.

Step 5 Within 5 seconds of turning on the router, press the Break key. This action causes the terminal to display the bootstrap program prompt:

rommon 1 >

Step 6 Set the configuration register to ignore the configuration file information as follows:

rommon 1 > confreg
 
	Configuration Summary
enabled are:
console baud: 9600
boot: image specified by the boot system command
	or default to: cisco2-RSP
 
do you wish to change the configuration? y/n [n]: y
enable "diagnostic mode"? y/n [n]:
enable "use net in IP bcast address"? y/n [n]:
enable "load rom after netbootfails"? y/n [n]:
enable "use all zero broadcast"? y/n [n]:
enable "break/abort has effect?" y/n [n]:
enable "ignore system config info?" [n]: y
change console baud rate? y/n [n]:
change boot characteristics? y/n [n]
 
	Configuration Summary
enabled are:
console baud: 9600
boot: image specified by the boot system command
	or default to: cisco2-RSP
 
do you wish to change the configuration? y/n [n]
 
You must reset or power cycle for the new config to take effect

Step 7 Initialize the router by entering the i command as follows:

rommon 1 > i

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:

         --- System Configuration Dialog ---

Step 8 Enter no in response to the system configuration dialog prompts until the following system message is displayed:

Press RETURN to get started!

Step 9 Press Return. After some interface information, the prompt appears as follows:

Router >

Step 10 Enter the enable command to enter the enabled mode. The prompt changes to the following:

Router #

Step 11 Enter the show configuration EXEC command to display the enable password in the configuration file.

Step 12 Enter the configure terminal command at the EXEC prompt. You are prompted as follows:

Router# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)#

Step 13 Using the config-register 0x<value> command, change the configuration register value back to its original value (noted from Step 3) or change it to a value of 0x0101 (factory default).

Step 14 Exit the configuration mode by entering Ctrl-Z.

Step 15 Reboot the router and enable it using the recovered password.

This completes the procedure for recovering from a lost password.

Using Flash Memory

The Flash memory (PCMCIA) slots on the front panel of the RSP2 support additional PCMCIA-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.

Note A complete discussion of PCMCIA-based Flash memory is beyond the scope of this publication.

For detailed information on Flash memory cards, refer to the configuration note Flash Memory Card Installation Instructions (Document Number 78-2083-xx, where xx is the latest version of this document).

For detailed information on Flash Disks, refer to the configuration note Using the PCMCIA Flash Disk (Document Number 78-5819-xx, where xx is the latest version of this document).

Cisco Connection Online

Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

WWW: http://www.cisco.com
WWW: http://www-europe.cisco.com
WWW: http://www-china.cisco.com
Telnet: cco.cisco.com
Modem: From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and connection rates up to 28.8 kbps.

For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.

Tasks	Command
1. Verify the location and version of the master RSP4 software image.	dir [/all \| /deleted] [/long] {bootflash \| slot0 \| slot1} [filename]
2. Determine whether the slave RSP4 contains the same software image in the same location.	dir [/all \| /deleted] [/long] {slavebootflash \| slaveslot0 \| slaveslot1} [filename]
3. Copy a different system image to the master RSP4.	copy file_id {bootflash \| slot0 \| slot1} copy flash {bootflash \| slot0 \| slot1} copy rcp {bootflash \| slot0 \| slot1} copy tftp {bootflash \| slot0 \| slot1}
4. Enter configuration mode from the terminal.	configure terminal
5. From global configuration mode, configure the master RSP4 to boot the new image from the appropriate location.	boot system flash bootflash:[filename] boot system flash slot0:[filename] boot system flash slot1:[filename]
6. Also, add a boot system command that specifies the slave's boot image and location. This is the boot image that the slave uses when it becomes the master RSP4 and boots the system. Note that because the slave boots this image when the slave is actually the new master RSP4, the command syntax does not use a "slave" prefix.	boot system flash bootflash:[filename] boot system flash slot0:[filename] boot system flash slot1:[filename]
7. Configure the master RSP4 to boot from a network server.	boot system [rcp \| tftp] filename [ip-address]
8. Set the configuration register to enable loading of the system image from a network server or Flash memory.	config-register value ¹
9. Exit configuration mode.	Ctrl-Z
10. Save the configuration file to the master's startup configuration. Because automatic synchronization is turned on, this step saves the boot system commands to the master and the slave startup configuration.	copy running-config startup-config
11. Reset the router with the new configuration information.	reload

Tasks	Command
1. Set the master's environment variables. For more complete HSA 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 copies.	boot system boot bootldr boot config
2. Save the settings to the startup configuration. This also puts the information under that RSP4 card's ROM monitor control.	copy running-config startup-config
3. Save the same environment variables to the slave RSP4 by manually synchronizing their configuration files.	slave sync config
4. Verify the environment variable settings.	show boot

Tasks	Command
Specify which image the slave runs.	slave image {system \| device:filename}

Tasks	Command
Manually synchronize master and slave configuration files.	slave sync config

Tasks	Command
Reload the inactive slave RSP card.	slave reload

Tasks	Command
Display the environment variable settings and configuration register settings for the master and the slave RSP cards.	show boot
Show a list of flash devices currently supported on the router.	show flash devices
Display the software version running on the master and the slave RSP card.	show version
Display the stack trace and version information of the master and the slave RSP cards.	show stacks ¹

Pin	Signal	Direction	Description
1	GND	-	Ground
2	TxD	<—	Transmit Data
3	RxD	—>	Receive Data
6	DSR	—>	Data Set Ready (always on)
7	GND	-	Ground
8	DCD	—>	Data Carrier Detect (always on)

Female DB-25 Pins	Male DB-25 Pins	Signal Description
P1-1	J1-1 and J2-1	Ground)
P1-2	J1-2, and J2-2	Receive Data (RxD)
P1-3	J1-3 and J2-3	Transmit Data (TxD)
P1-4	J1-4 and J2-4	Clear To Send (CTS); looped to 5
P1-5	J1-5 and J2-5	Request To Send (RTS); looped to 4
P1-6	J1-6 and J2-6	Data Set Ready (DSR)
P1-7	J1-7 and J2-7	Ground
P1-8	J1-8 and J2-8	Data Carrier Detect (DCD)
P1-13	J1-13 and J2-13	YCBL Detect Ground
P1-19	J1-19 and J2-19	YCBL Detect
P1-20	J1-20 and J2-20	Data Terminal Ready (DTR)

DRAM Sockets	Quantity	Totals	Product Numbers
U10	One 32-MB DIMM	32 MB	MEM-RSP4-32M¹
U13	One 32-MB DIMM	32 MB²	MEM-RSP4-32M=²
U10 and U13	Two 32-MB DIMMs	64 MB	MEM-RSP4-64M^³
U10	One 128-MB DIMM	128 MB	MEM-RSP4-128M(=)
U10 and U13	Two 128-MB DIMMs	256 MB	MEM-RSP4-256M(=)

Bit Number¹	Hexadecimal	Meaning
00 to 03	0x0000 to 0x000F	Boot field (see Table 9)
06	0x0040	Causes system software to ignore NVRAM contents
07	0x0080	OEM bit enabled²
08	0x0100	Break disabled
09	0x0200	Use secondary bootstrap
10	0x0400	Internet Protocol (IP) broadcast with all zeros
11 to 12	0x0800 to 0x1000	Console line speed (default is 9600 baud)
13	0x2000	Boot default Flash memory software if network boot fails
14	0x4000	IP broadcasts do not have network numbers
15	0x8000	Enable diagnostic messages and ignore NVRAM contents

Boot Field	Meaning
00	Stays at the system bootstrap prompt
01	Boots the first system image in onboard Flash memory
02 to 0F	Specifies a default netboot filename Enables boot system commands that override the default netboot filename

Action/Filename	Bit 3	Bit 2	Bit 1	Bit 0
Bootstrap mode	0	0	0	0
Default software	0	0	0	1
cisco2-RSP	0	0	1	0
cisco3-RSP	0	0	1	1
cisco4-RSP	0	1	0	0
cisco5-RSP	0	1	0	1
cisco6-RSP	0	1	1	0
cisco7-RSP	0	1	1	1
cisco10-RSP	1	0	0	0
cisco11-RSP	1	0	0	1
cisco12-RSP	1	0	1	0
cisco13-RSP	1	0	1	1
cisco14-RSP	1	1	0	0
cisco15-RSP	1	1	0	1
cisco16-RSP	1	1	1	0
cisco17-RSP	1	1	1	1

Bit 14	Bit 10	Address (<net> <host>)
Off	Off	<ones> <ones>
Off	On	<zeros> <zeros>
On	On	<net> <zeros>
On	Off	<net> <ones>

Table of Contents

Route Switch Processor (RSP4) Installation and Configuration