Cisco 7500 Series Routers

Table of Contents

Route Switch Processor (RSP1) Installation and Configuration

Product Numbers: RSP1=, MEM-RSP-8M=, MEM-RSP-16M, MEM-RSP-24M, MEM-RSP-32M(=), MEM-RSP-64M(=), and MEM-RSP-128M(=)

Part Number 78-1715-03
Customer Order Number: DOC-781715=

This document discusses the installation and configuration for the Route Switch Processor (RSP1), which is a processor module for the Cisco 7505 router. The RSP1 combines all of the switched routing and high-speed switching functions required by the Cisco 7505 router. Refer to the section "What Is the RSP1?.

Document Contents

Following are the sections in this document:

What Is the Cisco 7505?

The Cisco 7505 is a five-slot router chassis, which uses the RSP1 and CxBus and CyBus interface processors. The Cisco 7505 provides up to four interface processor slots. Although the Cisco 7505 uses the high-speed, 1.067-gigabit-per-second (Gbps) CyBus, it can accommodate all CxBus-based interface processors.

Any combination of network interface types is supported: Ethernet, Token Ring, Fiber Distributed Data Interface (FDDI), channel attachment, multichannel, serial, and so forth. The RSP1 and interface processors are keyed with guides on the backplane to prevent them from being fully inserted in the wrong slot.

Figure 1 shows the interface processor end of the Cisco 7505, which provides access to the five slots, the power switch, the chassis ground screw, the power receptacle, and the DC OK LED. When facing the interface processor end of the chassis, the RSP1 slot is at the top. The four interface processor slots are numbered from slot 0 (the bottom slot) through slot 3 (second slot from the top).

What Is the RSP1?

The RSP1 is the main system processor module for the Cisco 7505. It combines all of the switched routing and high-speed switching functions of the separate Route Processor (RP) and Switch Processor (SP), which are used in the Cisco 7000 series routers. Because the RSP1 combines the RP and SP functions, four slots are available for interface processors, allowing greater port density. The RSP1 contains the central processing unit (CPU) and most of the memory components for the Cisco 7505.

The Cisco Internetwork Operating System (Cisco IOS) software images reside in Flash memory, which is located either on the RSP1, in the form of a single in-line memory module (SIMM), or on up to two Personal Computer Memory Card International Association (PCMCIA) cards (called Flash memory cards) that insert in the two PCMCIA slots (slot 0 and slot 1) on the front of the RSP1. (See Figure 9.)

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

The RSP1 uses a software-controlled configuration register, so it is not necessary to remove the RSP1 to configure jumpers. There are no user-configurable jumpers on the RSP1.

The RSP1 contains the following components:

In addition to the system software, the RSP1 contains and executes the following management functions that control the system:

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

Memory Components

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

System Software

The Cisco 7505 router supports downloadable system software and microcode for most Cisco IOS and microcode upgrades, which enables you to remotely download, store, and boot from a new image. The publication Upgrading Software and Microcode in Cisco 7000 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. An erasable programmable read-only memory (EPROM) device contains the latest microcode version, in compressed form, for each interface processor. At system startup, an internal system utility scans for compatibility problems between the installed interface processor types and the bundled microcode images, then decompresses the images into running dynamic random-access memory (DRAM). The bundled microcode images then function the same as the EPROM images.

DRAM

DRAM stores routing tables, protocols, and network accounting applications. The standard RSP1 configuration is 16 megabytes (MB) of DRAM, with up to 128 MB available through single in-line memory module (SIMM) upgrades.

Note   When upgrading DRAM, you must use SIMMs from an approved vendor. To ensure that you obtain the most current vendor information, obtain the list from Customer Information Online (CIO) or the Technical Assistance Center (TAC). (See the section "Compatibility Requirements 7.)

NVRAM

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

Caution   Before you replace an RSP1, back up the running configuration to a Trivial File Transfer Protocol (TFTP) file server so you can retrieve it later. If the configuration is not saved, the entire configuration will be lost—inside the NVRAM on the removed RSP1—and you will have to reenter the entire configuration manually. For instructions on how to save the configuration file, refer to the section "Saving and Retrieving the Configuration File. This procedure is not necessary if you are temporarily removing an RSP1 you will reinstall; lithium batteries retain the configuration in memory until you replace the RSP1 in the system.

Flash Memory

The imbedded or PCMCIA card-based Flash memory allows you to remotely load and store multiple Cisco IOS software and microcode images. You can download a new image over the network or from a local server and then add the new image to Flash or replace the existing files. You can then boot routers either manually or automatically from any of the stored images. Flash memory also functions as a TFTP server to allow other servers to remotely boot from stored images or to copy them into their own Flash memory.

Before you can use a Flash memory card that was previously used on a Route Processor (RP) in a Cisco 7000 series router, you must reformat the Flash memory card. Flash memory cards formatted on RP-based (Cisco 7000 series) routers will not work properly in RSP-based (Cisco 7500 series) routers.

Jumpers

There are no user-configurable jumpers on the RSP1.

LEDs

The two LEDs on the RSP1 indicate the system and RSP1 status. The normal LED is on when the system is operational. 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 RSP1 controls both LEDs and turns both on in parallel to indicate that the system is operational.

Serial Ports

Two asynchronous serial ports on the RSP1, the console and auxiliary ports, allow you to connect external 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.

Prerequisites

Before beginning any of these procedures, review the following sections to ensure that your equipment configuration meets the minimum requirements for the upgrade or replacement you will perform, and that you have all the parts and tools you will need. Also, review safety and ESD-prevention guidelines to help you to avoid injury or damage to the equipment.

If you are replacing the existing RSP1, upload your current configuration file to a remote server before you remove the RSP1 to avoid having to reenter all your current configuration information manually. To upload the file, you need access to a remote server. Refer to the section "Saving and Retrieving the Configuration File, for instructions for uploading the file and retrieving it after the new RSP1 is installed.

Safety

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

Electrical Equipment

Follow these basic guidelines when working with any electrical equipment:

Telephone Wiring

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

Preventing Electrostatic Discharge Damage

ESD damage, which can occur when electronic cards or components are improperly handled, results in complete or intermittent failures. Each processor module contains a printed circuit card that is fixed in a metal carrier. Electromagnetic interference (EMI) shielding, connectors, and a handle are integral components of the carrier. Although the metal carrier helps to protect the board from ESD, use an ESD-preventive wrist or ankle strap whenever you handle any electronic system component.

Following are guidelines for preventing ESD damage:

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

Compatibility Requirements

You must install the RSP1 in the top slot (slot 4) of the Cisco 7505. (See the section "What Is the Cisco 7505?.) You must obtain the replacement SIMMs from an approved vendor. To ensure that you obtain the latest available product and vendor information, obtain the list from one of the following sources:

Although the PCMCIA card and SIMM specifications are defined in the manufacturers' part numbers, they must meet the following requirements:

Software Prerequisites

The RSP1 is compatible with Cisco IOS Release 10.3(3) or later. 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 (target hardware) version for each processor type. The show controller cybus or show controller cbus commands show the microcode version you are running. (For complete descriptions of show commands, refer to the Configuration Fundamentals Configuration Guide and Configuration Fundamentals Command Reference publications.)

You can determine the current version of software or microcode stored in ROM either by removing the processor module and checking the ROM labels or by configuring the system to boot the system software or microcode from ROM, reloading the system, and using show commands to check the version that is loaded and running. Refer to the appropriate software documentation for complete configuration instructions and examples.

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. (Refer to the "Obtaining Documentation" section on page 41 at the end of this document.) Cisco IOS Release 11.1(1) might require more than 16 MB of DRAM for your RSP1; refer to the "Replacing and Upgrading DRAM SIMMs" section.

Microcode Prerequisites

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.

New microcode is released to enable new features, improve performance, or fix bugs in earlier versions. The Cisco  routers feature downloadable software and microcode for most upgrades. These features enable you to download new (upgraded) images remotely, store the images in router memory, and load the new images at system startup without having to physically access the router.

You can store multiple versions for a specific processor type in Flash memory and use configuration commands to specify which version the system should load at startup. All interfaces of the same type (for example, all CIPs) use the same microcode image. Although most upgrades can be downloaded, some exceptions require ROM replacement to ensure proper startup and operation. Microcode images that are bundled with the system image load automatically along with the new software image.

Note   The software and interface processor microcode images are carefully optimized and bundled to work together. 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. The exception to this is CIP microcode, which as of Cisco IOS Release 11.1(1) is unbundled from the Cisco IOS image bundle, and is available in a separate bundle on floppy disks, a TFTP server, from CIO, or on Flash memory cards.

List of Tools and Parts

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

Saving and Retrieving the Configuration File

This section describes the procedures for saving and retrieving the system configuration. 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 when 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 will also be 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 RSP1, you will also replace the entire configuration (NVRAM resides in socket U17 on the RSP1). If you upload (copy) the configuration file to a remote server before removing the RSP1, you can retrieve it later and write it into NVRAM on the new RSP1. If you do not upload the configuration file, you will have to use the configure command or the setup command facility to reenter the configuration information after you install the new RSP1. For complete descriptions of these commands and instructions for using them, refer to the appropriate software documentation.

This procedure is not necessary if you are temporarily removing an RSP1 that you will reinstall; the lithium batteries will retain the configuration in memory until you replace the RSP1 in the system. This procedure requires privileged-level access to the EXEC command interpreter, which usually requires a password. Refer to the description that follows and contact your system administrator if necessary, to obtain access.

Using the EXEC Command Interpreter

Before you use the configure command, you must enter the privileged level of the EXEC command interpreter with the enable command. The system will prompt you for a password if one has been set.

The system prompt for the privileged level ends with a pound sign (#) instead of an angle bracket (>). At the console terminal, enter the privileged level as follows:

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

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

The pound sign (#) at the system prompt indicates that you are at the privileged level of the EXEC command interpreter; you can now execute the EXEC-level commands that are described in the following sections.

Using the Ping Command

Before you attempt to upload or retrieve a file from a remote host, ensure that the connection is good between the router and the remote server. The packet internet groper (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 will display a series of exclamation points (! ! !) or [ok]. If the connection fails, the system will display 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 interface processor 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:

The following example shows the results of a failed ping:

If the connection fails, check the physical connection to the remote file server and verify that you are using the correct address or name, then ping the server again. If you are unable to establish a good connection, contact your network administrator or refer to the end of this document for instructions on contacting technical assistance.

Uploading (Copying) the Configuration File

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

To store information on a remote host, enter the privileged EXEC command write network. The command will prompt you for the destination host's address and a filename, then display 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 upload (copy) the currently running configuration to a remote host:

Step 2   Use the ping command to check the connection between the router and the remote host. (See the "Using the Ping Command" section.)

Step 3   Issue the write term 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.)

Step 4   Issue the write net command. The EXEC command interpreter will prompt you for the name or interface processor address of the remote host that is to receive the configuration file. (The prompt might include the name or address of a default file server.)

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

Step 6   The EXEC command interpreter will prompt you for the name of the file that will contain the configuration. By default, the system appends -confg to the router's name to create the new filename. Press Return to accept the default filename, or enter a different name for the file before pressing Return. In the following example, the default is accepted:

Step 7   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 y then Return, and the system will begin the copy process. In the following example, the default is accepted:

While the router copies the configuration to the remote host, it displays a series of exclamation points (! ! !) or periods (. . .). The !!!! and [ok] indicate that the operation is successful. A 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 8   If the display indicates that the process was successful (with the series of ! ! ! and [ok]), the upload 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):

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 ""Removing the RSP1" section. If you are unable to copy the configuration to a remote host successfully, contact your network administrator or refer to the end of this document for instructions on contacting technical assistance.

Downloading (Retrieving) the Configuration File

After you install the new RSP1, 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 will prompt 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 RSP1 console port, or you can configure an interface port and Telnet to the router from a remote terminal.

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

Note   Until you retrieve the previous configuration, the router will be running from the default configuration in NVRAM. Therefore, any passwords that were configured on the previous system will not be valid until you retrieve the configuration.

Step 2   Use the ping command to verify the connection between the router and the remote host. (See the "Using the Ping Command" section.)

Step 3   At the system prompt, issue the configure network command and press Return to enter the configuration mode and specify that you will configure the system from a network device (instead of from the console terminal, which is the default).

Step 4   The system will ask you to select a host or network configuration file. The default is host; press Return to accept the default.

Step 5   The system will prompt you for the interface processor address of the host. Enter the interface processor address or name of the remote host (the remote file server to which you uploaded the configuration file.

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

Step 7   Before the system reboots with the new configuration, it displays the instructions you entered for confirmation. If the instructions are not correct, enter n (no) then press Return to cancel the process. To accept the instructions, press Return, or y then Return.

While the router retrieves and boots from the configuration on the remote host, the console display indicates whether or not the operation was 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:

Step 8   If the display indicates that the process was successful, 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, contact your network administrator or refer to the end of this document for instructions on contacting technical assistance.

Step 9   Issue the write term command to display the currently running configuration on the terminal. Review the display and ensure that the configuration information is complete and correct. If it is not, verify the filename and repeat the preceding steps to retrieve the correct file, or 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 specific configuration instructions.).

Step 10   When you have verified that the currently running configuration is correct, issue the copy running-config startup-config command to save the retrieved configuration in NVRAM. Otherwise, the new configuration will be lost if you restart the system. This completes the procedure for downloading (retrieving) the configuration file.

Installation

The following sections provide a functional overview of online insertion and removal (OIR), and describe the procedures for installing or replacing processor modules. Before installing any new interfaces, ensure that your system meets the minimum software and microcode requirements described in the "Software Prerequisites" section and the "Microcode Prerequisites" section.

The OIR feature allows you to remove and install interface processors without turning off system power. However, you must shut down the system before removing or installing the RSP1, which is a required system component.

Caution   To avoid unnecessary errors, read the following OIR overview before removing or replacing an RSP1.

Following the OIR overview, proceed to the "Removing the RSP1" section for instructions on removing the RSP1, and then to the "Replacing the RSP1" section for the installation instructions. After the new RSP1 is secure, follow the procedures in the "Troubleshooting the Installation" section to verify that it is installed and functioning properly.

Online Insertion and Removal—An Overview

OIR allows you to remove and replace CyBus interface processors while the system is operating; you do not need to notify the software or shut down the system power. This section describes the mechanical functions of the system components and stresses the importance of following the correct procedures to avoid unnecessary restarts or card failures. This section is for background information only. Subsequent sections provide specific procedures for removing and installing an RSP1.

Caution   All CyBus interface processors support OIR; however, you must shut down the system before removing or installing the RSP1, which is a required system component. Removing an RSP1 while the system is operating will cause the system to shut down or crash, and might damage or destroy memory files.

Each RSP1 and interface processor contains a bus connector with which it connects to the system backplane. The bus connector is a set of tiered pins, in three lengths. The pins send specific signals to the system as they make contact with the backplane.

The system assesses the signals it receives and the order in which it receives them to determine what event is occurring and what task it needs to perform, such as reinitializing new interfaces or shutting down removed ones. For example, when you insert an interface processor, the longest pins make contact with the backplane first, and the shortest pins make contact last. The system recognizes the signals and the sequence in which it receives them. The system expects to receive signals from the individual pins in this logical sequence, and the ejector levers help to ensure that the pins mate in this sequence.

When you remove or insert an interface processor, the backplane pins send signals to notify the system, which then performs as follows:

1. Rapidly scans the backplane for configuration changes and does not reset any interfaces.

2. Initializes all newly inserted interface processors, noting any removed interfaces and placing them in the administratively shutdown state.

3. Brings all previously configured interfaces on the interface processor back to the state they were in when they were removed. Any newly inserted interfaces are put in the administratively shutdown state, as if they were present (but unconfigured) at boot time. If a similar interface processor type has been reinserted into a slot, then its ports are configured and brought online up to the port count of the original interface processor.

OIR functionality enables you to add, remove, or replace interface processors with the system online, which provides a method that is seamless to end users on the network, maintains all routing information, and ensures session preservation.

When you insert a new interface processor, the system runs a diagnostic test on the new interfaces and compares them to the existing configuration.

If this initial diagnostic test fails, the system remains off line for another 15 seconds while it performs a second set of diagnostic tests to determine whether or not the interface processor is faulty and if normal system operation is possible.

If the second diagnostic test passes, which indicates that the system is operating normally and the new interface processor is faulty, the system resumes normal operation but leaves the new interfaces disabled. If the second diagnostic test fails, the system crashes, which usually indicates that the new interface processor has created a problem on the bus and should be removed.

The system brings online only interfaces that match the current configuration and were previously configured as up; all other interfaces require that you configure them with the configure command. On interface processors with multiple interfaces, only the interfaces that have already been configured are brought online.

For example, if you replace a single-PCA CIP with a dual-PCA CIP, only the previously configured interface is brought online automatically; the new interface remains in the administratively shutdown state until you configure it and bring it online.

Caution   When removing or replacing interface processors, you can avoid erroneous failure messages by allowing at least 15 seconds for the system to reinitialize before removing or inserting another interface processor.

Removing the RSP1

When you remove or install the RSP1, be sure to use the ejector levers, which help to ensure that the RSP1 is fully inserted in the backplane or fully dislodged from it. Any RSP1 or interface processor that is only partially connected to the backplane can halt the system. Figure 3 shows a detail of the ejector lever mechanism in a horizontal position that is appropriate for the Cisco 7505. When you simultaneously push the ejector levers inward (toward the carrier handle), the levers push the RSP1 into the slot and ensure that the board connectors are fully seated in the backplane.

Caution   You must shut down the system before removing or installing the RSP1, which is a required system component. Removing an RSP1 while the system is operating will cause the system to shut down or crash and might damage or destroy memory files.

Follow these steps to remove the RSP1:

Step 2   Slip on an antistatic strap and connect the equipment end of the strap to a captive installation screw on an installed interface processor, or to the chassis ground screw that is located to the left of the power receptacle. (See Figure 1.)

Step 3   If you are replacing the RSP1, disconnect any devices that are attached to the console or auxiliary ports. If you are removing the RSP1 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 (number 2 Phillips or 1/4-inch flat-blade) to loosen the two captive installation screws. (See Figure 3.)

Step 5   Place your thumbs on the ends of each of the ejectors and simultaneously pull them both outward, away from the carrier handle (in the opposite direction from that shown in c in Figure 3) to release the carrier from the slot and to dislodge the RSP1 from the backplane.

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

Step 7   Place the removed RSP1 on an antistatic mat or foam. If you plan to return the RSP1 to the factory, immediately place it in an antistatic bag to prevent ESD damage.

This completes the removal procedure.

If you removed the RSP1 to replace SIMMs, proceed to the appropriate section.

If you are replacing the RSP1, proceed to the next section to install the new RSP1.

Replacing the RSP1

Ensure that all system power is turned off before installing the RSP1 in the chassis. The RSP1 is keyed for installation only in the RSP1 slot. (See Figures 1 and 2.)

Follow these steps to install an RSP1:

Step 2   Grasp the RSP1 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 3   Place the back of the RSP1 in the top slot and align the notches along the edge of the carrier with the grooves in the slot. (See a in Figure 3.)

Caution   To prevent damage to the backplane, you must install the RSP1 in the top slot of the Cisco 7505. (See Figure 2.) The slots are keyed for correct installation. Forcing the RSP1 into a different slot can damage the backplane and the RSP1.

Step 4   While keeping the RSP1 at a 90-degree orientation to the backplane, carefully slide the carrier into the slot until the RSP1 faceplate makes contact with the ejector levers, then stop. (See b in Figure 3.)

Step 5   Using the thumb and forefinger of each hand to pinch each ejector, simultaneously push both ejectors inward (toward the handle) until they are at a full 90-degree orientation to the faceplate. (See c in Figure 3.)

Step 6   Use a screwdriver (number 2 Phillips or 1/4-inch flat-blade) to tighten the captive installation screws on the ends of the RSP1. (See a in Figure 3.)

Step 7   Use a screwdriver to tighten the two captive screws on the RSP1 faceplate to prevent the RSP1 from becoming partially dislodged from the backplane and to ensure proper EMI shielding. (These screws must be tightened to meet EMI specifications.)

Step 8   If you disconnected the console terminal to remove the RSP1, or if you are installing a new RSP1, connect the console terminal to the console port.

Step 9   Ensure that the console terminal is turned on.

Step 10   Turn the system power back ON, and proceed to the next section to check the installation.

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 "System Startup Sequence" section.)

Follow these steps to verify that the RSP1 is installed and functioning properly:

Step 2   Observe the RSP1 LEDs. While the system initializes, the yellow boot error LED on the RSP1 stays on, then goes off when the boot is complete. As the RSP1 initializes each interface processor, the status LEDs on each interface processor go on and off in irregular sequence.

Step 3   Verify that the console terminal displays the system banner and startup screen as the system restarts. The display should look similar to the following:

Step 4   After the system boots the software and initializes the interface processors (approximately 30 seconds for systems with 16 MB of DRAM, and approximately 2 minutes for systems with 64 MB of DRAM), verify that the RSP1 LEDs are in the following states:

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

When you have verified all the conditions in Step 2 through Step 5, the installation is complete.

If you replaced the RSP1 and saved your configuration file to a remote server before doing so, proceed to the "Downloading (Retrieving) the Configuration File" section. If you replaced the RSP1 and did not save the configuration, use the configure command or the setup command facility to reenter the configuration information. Refer to the appropriate software documentation for command descriptions and instructions for using them.

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.

Troubleshooting the Installation

This section contains procedures to follow if the system does not restart and boot 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 RSP1 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 Cisco 7505, the DC OK LED is located on the lower right of the interface processor end of the chassis and is labeled DC OK. (See Figure 1.) If the DC OK LED does not go on or stay on, there is most likely a problem with the input power or one of the internal DC lines.

The 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 7505 Hardware Installation and Maintenance publication.

RSP1 LEDs

Figure 4 shows the LEDs and reset switch on the RSP1 faceplate. The LEDs on the RSP1 indicate the system and RSP1 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.

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.

Caution   The reset switch (see Figure 4) resets the RSP1 and the entire system. To prevent system errors and problems, use it only at the direction of your 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 of the enabled LEDs should go on. If any do not, one of the following errors is indicated:

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 chassis. 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, refer to the end of this document for instructions on contacting a service representative.

Note   The time required for the system to initialize (boot) varies 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 128  MB of DRAM will be longer than in a system that contains 16 MB of DRAM.

During the boot sequence, the system banner display pauses while it initializes the memory. If your router has more than 16 MB of DRAM, you may notice an increase in the amount of time required to initialize the memory. The pause in the banner display occurs after the copyright line, and before the system displays the list of installed hardware, as shown in the following display:

Note   The procedures in this section are based on the assumption that your system was operating correctly until you removed (or replaced) the RSP1. If the following sequence indicates a new problem with the power subsystem or one of the interface processors, refer to the Cisco 7505 Hardware Installation and Maintenance publication for system startup troubleshooting procedures.

Use the following startup sequences and troubleshooting procedures to isolate system problems:

1. When you restart up the system, the system power the DC OK LED should go on.

If the LED on the power supply 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 7505 Hardware Installation and Maintenance publication for power subsystem troubleshooting procedures.

When the system power LED indicates normal operation, proceed to number 2.

2. Listen for the fans. You should hear them start operating immediately after you turn on the system power. If you determine that the power supply is functioning normally and that a fan (or the fan array) is faulty, contact a service representative. If the fan array 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 RSP1. The CPU halt LED on the RSP1 should always remain off. If it goes on during the startup sequence, the system has encountered a processor hardware error.

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

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

If the system still fails to start up or operate properly, or if you isolate the cause of the problem to a failed component, contact a service representative for further assistance. This completes the RSP1 installation and replacement procedure. For complete command descriptions and examples, refer to the appropriate software documentation.

Reference Information

Following is reference information for replacing SIMMs, configuring the software configuration register, recovering a lost password, and using the front-panel PCMCIA slots for additional Flash memory.

Console Port Signals

The console port on the RSP1 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 2 lists the signals used on this port.

Auxiliary Port Signals

The auxiliary port on the RSP1 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. Table 3 lists the EIA/TIA-232 signals used on this port.

The asynchronous auxiliary port supports hardware flow control and modem control.

Replacing and Upgrading DRAM SIMMs

The system DRAM resides on up to four SIMMs on the RSP1. The DRAM SIMM sockets are U4 and U12 for bank 0, and U18 and U25 for bank 1. The default DRAM configuration is 16 MB (two 8-MB SIMMs in bank 0). (See Figure 5.)

Note   The total number of memory devices per SIMM differs for each manufacturer. The SIMMs in the following illustrations are generic representations of the actual DRAM SIMMs for your RSP1. To be assured that you are using the correct SIMMs, refer to your specific DRAM upgrade requirements.

This section describes the steps for increasing the amount of DRAM by replacing up to four SIMMs that you obtain from an approved vendor.

The SIMM sockets use the thumb tabs that are often used in PCs and other computer equipment. Each RSP1 SIMM socket has two metal retaining springs, one at each end. (See Figure 6.) When a SIMM is fully seated in the socket, the retaining springs snap over the ends of the SIMM to lock it in the socket.

Before proceeding, ensure that you have the proper ESD-prevention equipment available. To upgrade DRAM, install SIMMs in one or two banks. Table 4 lists the various configurations of DRAM SIMMs that are available. Note which banks are used given the combinations of available SIMM sizes and the maximum DRAM you require. SIMMs must be 60 ns or faster and no taller than one inch.

Note   Depending on your router configuration, Cisco IOS Release 11.1(1) might require more than 16 MB of DRAM for your RSP7000. Upgrade your system DRAM based on your current configuration and this potential requirement.

Caution   To prevent DRAM errors, each DRAM bank used must contain no fewer than two SIMMs of the same type. You must install either two SIMMs in bank 0 or four SIMMs in two banks.

Removing SIMMs

Place removed SIMMs on an antistatic mat and store them in an antistatic bag. You can use the SIMMs that you remove in compatible equipment.

Caution   To prevent ESD damage, handle SIMMs by the card edges only.

Follow these steps to remove the existing SIMMs:

Step 2   Place the RSP1 on an antistatic mat or pad, and ensure that you are wearing an antistatic device, such as a wrist strap. Position the RSP1 so that the handle is away from you and the edge connector is toward you—opposite of the position shown in Figure 2.

Step 3   Locate the SIMMs. The DRAM SIMMs occupy U4 and U12 in bank 0, and U18 and U25 in bank 1. (See Figure 2.)

Step 4   Release the spring clips from the SIMM that you want to remove and release the SIMM from the socket. (See Figure 6.)

Step 5   When both ends of the SIMM are released from the socket, grasp the ends of the SIMM with your thumb and forefinger and pull the SIMM completely out of the socket. Handle the edges of the SIMM only; avoid touching the memory module or pins, and the metal traces, or fingers, along the socket edge.

Step 6   Place the SIMM in an antistatic bag to protect it from ESD damage.

Step 7   Repeat Steps 4 through 6 for the remaining SIMMs, as required for your upgrade.

This completes the SIMM removal procedure. Proceed to the next section to install the new SIMMs.

Installing New SIMMs

Following is the procedure for installing new SIMMs.

Caution   SIMMs are sensitive components that are susceptible to ESD damage. Handle SIMMs by the edges only; avoid touching the memory modules, pins, or traces (the metal fingers along the connector edge of the SIMM). (See Figure 7.)

*

Follow these steps to install the new SIMMs:

Step 2   Remove a new SIMM from the antistatic bag.

Step 3   Hold the SIMM component side up, with the connector edge (the metal fingers) closest to you. Hold the sides of the SIMM between your thumb and middle finger, with your forefinger against the far edge, opposite the connector edge. (See Figure 7.)

Step 4   Tilt the SIMM to approximately the same angle as the socket and insert the entire the connector edge into the socket. (Install the first SIMM in the slot farthest away from you. Install the last SIMM in the slot closest to you.)

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

Step 5   Gently push the SIMM into the socket until the spring clips snap over the ends of the SIMM. If necessary, rock the SIMM gently back and forth to seat it properly.

Step 6   Repeat Steps 2 through 5 for the remaining SIMMs.

Step 7   When all SIMMs are installed, check all alignment holes (two on each SIMM) and ensure that the spring retainer is visible. If it is not, the SIMM is not seated properly. If any SIMM appears misaligned, carefully remove it and reseat it in the socket. Push the SIMM firmly back into the socket until the retainer springs snap into place.

If the system fails to boot properly, or if the console terminal displays a checksum or memory error, check the following:

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.

Note   The time required for the system to initialize varies with different router configurations. Routers with 128 MB of DRAM will take longer to boot than those with 16 MB of DRAM.

This completes the SIMM replacement procedure.