|
|
Product Numbers:
RSP8=
CISCO7507/8-MX
CISCO7513/8-MX
CISCO7507/8x2-MX
CISCO7513/8x2-MX
MEM-RSP8-64M=1
MEM-RSP8-128M=
MEM-RSP8-256MB=
This configuration note discusses the next-generation Route Switch Processor (RSP8), which is the main system processor available for the Cisco 7507-MX and Cisco 7513-MX routers. The RSP8 combines all of the switched routing and high-speed switching functions required by
Cisco 7500 series routers. (For more information, see the "Product Description" section.)
In addition, the RSP8 supports the high system availability (HSA) feature, which allows two RSP8s to be used simultaneously in a Cisco 7507, Cisco 7507-MX, Cisco 7513, or
Cisco 7513-MX router with the HSA feature enabled and configured. The RSP8 is also compatible with the Cisco 7505 and Cisco 7576 routers, although these routers do not support the HSA function.
With the HSA feature, one RSP8 operates as the system master and the other RSP8 operates as the system slave, which takes over if the master RSP8 fails. The HSA feature only operates with two RSP8s. (See the "Hardware Prerequisites" section.)
This publication contains the following sections:
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:
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.
This section lists safety guidelines you should follow when working with any equipment that connects to electrical power or telephone wiring.
Safety warnings appear throughout this publication in procedures that, if performed incorrectly, might harm you. A warning symbol precedes each warning statement.
Warning 
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.
Use the following basic guidelines when working with any electrical equipment:
Use the following guidelines when working with any equipment that is connected to telephone wiring or to other network cabling:
Electrostatic discharge (ESD) damage, which can occur when electronic cards or components are improperly handled, can result in complete or intermittent failures. Each processor module contains a printed circuit card that is fixed in a metal carrier.
Electromagnetic interference (EMI) shielding, connectors, and a handle are integral components of the carrier. Although the metal carrier helps to protect the board from ESD, use an ESD-preventive wrist or ankle strap whenever you handle any electronic system component.
Following are guidelines for preventing ESD damage:
 | Caution
For safety, periodically check the resistance value of the antistatic strap. The measurement should be between 1 and 10 megohms (Mohm). |
This section describes important compatibility requirements for the RSP8.
Following are chassis slot and DRAM requirements for ensuring RSP8 compatibility.
There are no restrictions on installing an RSP8 in a Cisco 7505. However, the Cisco 7505 does not support the HSA feature.
There are no restrictions on installing an RSP8 in a Cisco 7507 or Cisco 7507-MX provided that you install the RSP8 in slot 2, slot 3, or both. (With the HSA feature enabled, you will install an RSP8 in both RSP slots.)
There are no restrictions on installing an RSP8 in a Cisco 7513 or Cisco 7513-MX provided that you install the RSP8 in slot 6, slot 7, or both. (With the HSA feature enabled, you will install an RSP8 in both RSP slots.)
There are no restrictions on installing an RSP8 in a Cisco 7576 provided that you install the RSP8 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 RSP8s in the Cisco 7507, Cisco 7507-MX, Cisco 7513, or Cisco 7513-MX you plan to enable and configure the HSA feature.
Flash memory PC Cards and Flash Disk PC Cards (formerly called PCMCIA cards) and DRAM DIMM specifications are defined in the manufacturers' part numbers; however, they must meet the following requirements:
Following are Flash memory card requirements for ensuring RSP8 compatibility.
You cannot boot from or use a Flash memory card in the RSP8 that was formatted on another type of RSP-based system (including the RSP7000, RSP1, RSP2, and RSP4) that was running a
Cisco IOS software version earlier than Cisco IOS Release 12.0(9)S.
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 RSP8.
| Caution In order for a Flash memory card that was formatted on an RSP1, RSP2, RSP4, or RSP7000 to be compatible in an RSP8, the Flash memory card must be formatted with a boot or Cisco IOS software image that is compatible with the RSP8. To prevent system problems, use Flash memory cards in the RSP8 that were formatted on an RSP7000, RSP1, RSP2, RSP4, or RSP8 running Cisco IOS Release 12.0(9)S or a later release of 12.0 S. |
The RSP8 is compatible with Cisco IOS Release 12.0(9)S or a later release of 12.0 S. This IOS software release applies to all systems that support the RSP8. 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 controllers command shows the microcode version you are running. The show diagbus command shows the RSP8 board's hardware version and revision.
For additional descriptions of show commands, refer to the Configuration Fundamentals Configuration Guide and Configuration Fundamentals Command Reference publications, which are available on the Documentation CD-ROM or as printed copies.
To ensure that the slave RSP8 operates properly with the full system configuration should the master RSP8 ever fail, the slave RSP8 must have the same (or higher) DRAM and flash memory capacity as the master RSP8. See the "Memory Components" section for RSP8 memory component requirements.
| Caution Removing the system master RSP8 while the system is operating will cause the system to crash; however, the system reloads with the slave RSP8 as the new system master provided that the autoboot feature is enabled. To prevent any system problems, do not remove the system master RSP8 while the system is operating. |
| Caution Before you can use a Flash memory card that was previously formatted and used in an RP, RSP7000, RSP1, RSP2, or RSP4, you must reformat the Flash memory card. Flash memory cards formatted on any of these processors do not work properly in an RSP8. 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 RSP8 system. |
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.
You need some or all of the following parts and tools to install, remove, and replace an RSP8 or to upgrade DRAM. If you need additional equipment, contact a customer service representative for ordering information.
| Caution To prevent memory problems, DRAM DIMMS must be 3.3-volt (V) devices. Do not attempt to install higher-voltage devices (such as those designed for the RSP2) in the RSP8's DIMM sockets. |
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 editing of the configuration file.
The 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, enter the copy system:running-config nvram:startup-config command to ensure that the new configuration is saved.
If you replace the RSP in a system with only one RSP8, you also replace the entire configuration, which resides in NVRAM on the RSP. If you copy the configuration file to a remote server before removing the RSP, you can retrieve it later and write it into NVRAM on the new RSP8. You can also use the copy running-config disk0:config-file command to save the configuration file to Flash memory, and then use the copy disk0: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 RSP8. For complete descriptions of these two commands, and instructions for using them, refer to the appropriate software documentation.
If you are temporarily removing an RSP8, it is not necessary to copy the configuration file to a remote server; the lithium batteries retain the configuration file in memory until you replace the RSP8 in the system. This procedure requires privileged-level access to the EXEC command interpreter, which usually requires a password. See the description that follows and contact your system administrator to obtain access, if necessary.
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.
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, enter 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 10.1.1.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.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 10.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.
Before you copy (save) the running configuration to a TFTP file server, ensure the following:
To store information on a remote host, enter the privileged EXEC command
copy system:running-config. 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 Enter the show running-config command to display the currently running configuration on the terminal and ensure that the configuration information is complete and correct.
Step 4 If it is not, use the configure command to add or modify the existing configuration.
(Refer to the appropriate software documentation for descriptions of the configuration options available for the system and individual interfaces, and for specific configuration instructions.)
Step 5 Create a file on the TFTP server.
Step 6 Enter 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 7 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 (10.1.1.1) [OK]
Step 8 The EXEC command interpreter prompts you for the name of the file that will contain the configuration. By default, the system appends -confg to the router's name to create the new filename. Press Return to accept the default filename, or enter a different name for the file before pressing Return. In the following example, the default is accepted:
Name of configuration file to write [Router-confg]? Write file Router-confg on host 10.1.1.1? [confirm] Writing Router-confg .....
Step 9 Before the router executes the copy process, it displays the instructions you entered for confirmation. If the instructions are not correct, enter n (no) and then press Return to end the process. To accept the instructions, press Return, or press y and then press Return, and the system begins the copy process. In the following example, the default is accepted:
Write file Router-confg on host 10.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 10 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 RSP8" 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.
After you install the new RSP8, 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 RSP8 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.
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, enter 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]? 10.1.1.1
Step 6 The system prompts you for the name of the configuration file. The default is to use the name of the router with the suffix -confg (router-confg in the following example). If you specified a different filename when you copied the configuration, 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 10.1.1.1? [confirm] Loading Router-confg from 10.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 10.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, enter the
show startup-config command and look at the first line for the configuration file size. Compare it with the file you retrieved from the TFTP server to confirm that it is correct. Following is an example:
Router# show startup-config Using 1186 out of 126968 bytes ! version 12.0(9)S 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, enter the copy system:running-config nvram:startup-config command as follows:
Router# copy system:running-config nvram:startup-config Router# %SYS-5-CONFIG_I: Configured from memory by console Router#
This completes the procedure for retrieving the saved configuration file.
The RSP8 is the newest main system processor module for Cisco 7500 series routers.
(See Figure 1 and Figure 2.)
The RSP8 is available as follows:
The RSP8 contains the following components:
In addition to running the system software from DRAM, the RSP8 contains and executes the following management functions that control the system:
The high-speed switching section of the RSP8 communicates with and controls the interface processors on the high-speed CyBus. This switching section of the RSP8 decides the destination of a packet and switches it based on that decision.
The RSP8 combines all of the switched routing and high-speed switching functions. The RSP8 supports the HSA feature, which allows two RSP8s to be used in a Cisco 7507, Cisco 7507-MX, Cisco 7513, or Cisco 7513-MX router. By default, the system master is the RSP8 that occupies the first RSP slot in the router: slot 2 in the Cisco 7507 and Cisco 7507-MX, and slot 6 in the Cisco 7513 and Cisco 7513-MX.
The Cisco 7507, Cisco 7507-MX, Cisco 7513, and Cisco 7513-MX routers support downloadable system software and microcode for most Cisco IOS and microcode upgrades. This enables you to remotely download, store, and boot from a new image. The publication Upgrading Software and Microcode in Cisco 7000 Series and Cisco 7500 Series Routers (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 SIMM-based and Flash memory cards 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 RSP8, in the form of a single in-line memory module (SIMM), or on Flash memory cards that insert in the two PC Card slots (slot 0 and slot 1) on the front of the RSP8. (See Figure 2.) Storing the
Cisco IOS images in Flash memory enables you to download and boot from upgraded Cisco IOS images remotely or from software images resident in the RSP8 Flash memory.
Although no monitoring of voltage or temperature is done by the RSP8, a comparator device ensures that voltage is within the normal operating ranges, and three temperature sensors on the RSP8 send temperature information to the chassis interface (CI) card. The CI card reports all voltage and temperature readings, and these readings are available through standard software commands for environmental monitoring. The RSP8 uses a software-controlled configuration register, so you do not have to remove the RSP8 to configure jumpers. There are no user-configurable jumpers on the RSP8.
Figure 2 shows the various types of memory components on the RSP8, and Table 1 lists the functions of each type.
| Type | Size | Quantity | Description | Location |
|---|---|---|---|---|
DRAM | 64-MB1 to 256-MB DIMMs | 1 or 2 | Any combination of 32-MB, 64-MB, or 128-MB DIMMs (based on DRAM required) for main Cisco IOS image functions | U12 or U12 and U152 |
SRAM3 | 8 MB (fixed) | - | SRAM for packet buffering functions (MEMD) | - |
| 2 MB (fixed) | - | SRAM for tertiary (L3) CPU cache memory functions | - |
NVRAM | 2 MB | 1 | Nonvolatile SRAM for the system configuration file4 | - |
Flash memory | 16-MB SIMM | 1 | U1 | |
| Up to 2 | Contains the Cisco IOS images on up to two Flash Disks5 | Slot 0 or slot 0 and slot 1 | |
| 16-MB or 20-MB Flash memory card | Up to 2 | Contains the Cisco IOS images on up to two Flash memory cards | Slot 0 or slot 0 and slot 1 |
Flash boot ROM | 256 KB | 1 | Flash EPROM for the ROM monitor program image | U7 |
| 164 MB of DRAM is the default DRAM configuration for the RSP8. The RSP8 is pre-configured with either two 32-MB DIMMs, or one 64-MB DIMM. 2Note that the larger DRAM DIMM must be placed in the U12 socket. 3SRAM is not user-configurable or field-upgradable. 4A system configuration file is contained in NVRAM, which allows the Cisco IOS software to control several system variables. 5Type I, Type II, and Type III PC Cards can be used in PC Card slot 1, and Type I and Type II PC Cards can be used in slot 0. |
DRAM stores routing tables, protocols, and network accounting applications and runs the
Cisco IOS software. The standard (default) RSP8 configuration is 64 MB (pre-configured with either two 32-MB DIMMs or one 64-MB DIMM) of DRAM, with up to 256 MB available through DIMM upgrades. DRAM is contained in up to two DIMM sockets: U12 (also called bank 0) and U15 (also called bank 1). When upgrading DRAM, you must use DIMMs from 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 RSP8 DIMM sockets. |
SRAM provides packet buffering and CPU cache memory functions. The standard RSP8 configuration is 8 MB of SRAM for packet buffering and 2 MB of tertiary (L3) CPU cache memory.
The system configuration, software configuration register settings, and environmental monitoring logs are contained in the 2-MB NVRAM, which is backed up with built-in lithium batteries that retain the contents for a minimum of 5 years. When replacing an RSP8, be sure to back up your configuration to a remote server so you can retrieve it later.
| Caution Before you replace an RSP8 in a system with one RSP8, back up the running configuration to a Trivial File Transfer Protocol (TFTP) file server or to Flash memory so you can retrieve it later. If the configuration is not saved, the entire configuration will be lost---inside the NVRAM on the removed RSP8---and you will have to reenter the entire configuration manually. For instructions on how to save the configuration file, see the "Saving and Retrieving a Configuration File" section. This procedure is not necessary if you are temporarily removing an RSP8; lithium batteries retain the configuration in memory until you replace the RSP8 in the system. |
Flash memory PC Cards (formerly called PCMCIA card) allow you to remotely load and store multiple Cisco IOS software and microcode images. You can download a new image over the network or from a local server and then add the new image to Flash memory or replace the existing files. You can then boot routers either manually or automatically from any of the images stored in Flash memory. Flash memory also functions as a TFTP server to allow other servers to boot remotely from stored images or to copy them into their own Flash memory. Two types of Flash memory are available. Flash Disks are available in 48-MB and 128-MB sizes. Flash memory cards are available in 16-MB and 20-MB sizes. Flash memory cards can be used in the RSP8s second PC Card slot for additional space, or as a backup to the main Flash memory.
| Caution In order for a Flash memory card that was formatted on an RSP1, RSP2, RSP4, or RSP7000 to be compatible in an RSP8, the Flash memory card must be formatted with a boot image or Cisco IOS software image that is compatible with the RSP8. To prevent system problems, use Flash memory cards in the RSP8 that were formatted on an RSP1, RSP2, RSP4, RSP7000, or RSP8 running Cisco IOS Release 12.0(9)S or a later release of 12.0 S. |
There are no user-configurable jumpers on the RSP8.
Table 2 describes the operation of the LEDs found on the RSP8:
| LED Label | Color | State | Indication |
|---|---|---|---|
Green | On | RSP8 is on and receiving +5V. | |
CPU halt1 | Green Yellow | Off On | RSP8 is operating normally. Processor hardware failure has been detected. |
Master | Green | On | RSP8 is a master. |
Slave | Green | On | RSP8 is a slave (HSA configuration required). |
Slot 0 PC Card | Green | On | PC Card in this slot is being accessed. |
Slot 1 PC Card | Green | On | PC Card in this slot is being accessed. |
| 1The RSP8 controls these LEDs and turns them on in parallel to indicate that the system is operational. |
The RSP8 has two PC Card slots available. Either slot can support a Flash memory card or an input/output (I/O) device. Type I and Type II PC Cards can be used in PC Card slot 0 and slot 1. Type III PC Cards can be used in slot 1. Not all Flash memory cards that are commercially available are supported, and not all I/O devices are supported.
Two asynchronous serial ports on the RSP8, labeled Console and Auxiliary, allow you to connect external terminal devices to monitor and manage the system. The console port is an Electronics Industries Association/Telecommunications Industry Association (EIA/TIA)-232 receptacle (female) that provides a data circuit-terminating equipment (DCE) interface for connecting a console terminal.
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.
The following sections describe the procedures for installing or replacing an RSP8. 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 RSP8" section for instructions on removing the RSP8, and then to the section "Replacing the RSP8" section for installation instructions. After the new RSP8 is secure, follow the procedures in the "Troubleshooting the Installation" section to verify that it is installed and functioning properly.
| Caution Removing the only installed RSP8 from a system while the system is operating will cause the system to crash. Consider this before removing an RSP8 while the system is operating. To ensure that the slave RSP8 operates properly with the full system configuration should the master RSP8 ever fail, the slave RSP8 must have the same (or higher) DRAM and flash memory capacity as the master RSP8. See the "Memory Components" section for RSP8 memory component requirements. |
When you remove or install the RSP8, be sure to use the ejector levers, which help to ensure that the RSP8 is fully inserted in the backplane or fully dislodged from it. An RSP8 that is only partially connected to the backplane can halt the system unless a second RSP8 is installed.
Figure 4 on page 22 shows a detail of the ejector lever mechanism that is appropriate for the router. When you simultaneously push the ejector levers inward (toward the carrier handle), the levers push the RSP8 into the slot and ensure that the board connectors are fully seated in the backplane. Follow these steps to remove the RSP8:
Step 1 Optional step: If you are replacing the RSP8 in a system with one RSP8, 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 RSP8, disconnect any devices that are attached to the console or auxiliary ports. If you are removing the RSP8 for maintenance and will reinstall the same one, you can leave the devices attached provided that doing so will not strain the cables.
Step 4 Use a screwdriver to loosen the two captive installation screws. (See Figure 4 on page 22.)
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 RSP8 from the backplane.
Step 6 Grasp the handle of the RSP8 with one hand and pull the RSP8 straight out of the slot, keeping your other hand under the carrier to guide it. (See Figure 3.) Keep the carrier parallel to the backplane. Avoid touching the board or any connector pins.
Step 7 Place the removed RSP8 on an antistatic mat or foam. If you plan to return the RSP8 to the factory, immediately place it in an antistatic bag to prevent ESD damage.
Step 8 Attach the equipment end of the ESD-preventive strap to the RSP8 before performing any maintenance on the RSP8 that might create an ESD hazard.
This completes the removal procedure. If you removed the RSP8 to replace DIMMs, proceed to the "Replacing and Upgrading DRAM DIMMs" section. If you are replacing the RSP8, proceed to the next section to install the new RSP8.
The RSP8 is keyed for installation only in an RSP slot. By default, the system master is the RSP that occupies the first RSP slot in the router: slot 2 in the Cisco 7507 and Cisco 7507-MX, and slot 6 in the Cisco 7513 and Cisco 7513-MX. Follow these steps to install an RSP8:
Step 1 Grasp the RSP8 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 RSP8 in the appropriate RSP slot and align the notches along the edge of the carrier with the grooves in the slot. (See Figure 4a.)
| Caution To prevent damage to the backplane, you must install the RSP8 in one of the two RSP slots on the router. The slots are keyed for correct installation. Forcing the RSP8 into a different slot can damage the backplane and the RSP8. |
Step 3 While keeping the RSP8 parallel to the backplane, carefully slide the carrier into the slot until the RSP8 faceplate makes contact with the ejector levers, and then stop.
(See Figure 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 RSP8.
(See Figure 4a.)
Step 6 Use a screwdriver to tighten the two captive screws on the RSP8 faceplate to prevent the RSP8 from becoming partially dislodged from the backplane and to ensure proper EMI shielding. (These screws must be tightened to meet EMI specifications.)
Step 7 If you disconnected the console terminal to remove the RSP8, or if you are installing a new RSP8, connect the console terminal to the console port. (See the next section, "Connecting a Console Terminal.")
Step 8 Ensure that a console terminal is connected (see the next section, "Connecting a Console Terminal") 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.
The system console port on the RSP8 is a DB-25 receptacle DCE port for connecting a data terminal, which you need to configure in order to communicate with your system. The console port is located on the RSP8 just below the auxiliary port, as shown in Figure 5, and is labeled Console.
Before connecting the console port, check the documentation for your terminal to determine the baud rate of the terminal you are using. The baud rate of the terminal must match the default baud rate (9600 baud). Set up the terminal as follows: 9600 baud, 8 data bits, no parity, and 2 stop bits (9600,8N2). Use the console cable provided to connect the terminal to the console port on the RSP8, and then follow the steps in the "Restarting the System" section.
The auxiliary port on the RSP8 is a DB-25 plug DTE port for connecting a modem or other DCE device (such as a channel service unit [CSU], data service unit [DSU], or other router) to the router. The port is located next to the console port on the RSP8 and is labeled AUX. An example of a modem connection is shown in Figure 5.
For systems with two RSP8s installed (one as master and one as slave in RSP slots 2 and 3 in the
Cisco 7507 and Cisco 7507-MX, and slots 6 and 7 in the Cisco 7513 and Cisco 7513-MX, using the HSA feature), you can simultaneously connect to both console or auxiliary ports using a special, optional Y-cable. If only one RSP8 is installed, it is the system master by default.
Figure 6 shows the console Y-cable and Figure 7 shows the auxiliary Y-cable.
When you turn the system power back on, verify that the system boots and resumes normal operation. If you are restarting the system after upgrading the DRAM, expect that it will take the system longer to complete the memory initialization portion of the boot sequence with more DRAM. (See the "Verifying System Startup Sequence" section.)
Follow these steps to verify that the RSP8 is installed and functioning properly:
Step 1 Check the RSP8 connections to make sure they are secure:
Step 2 Observe the RSP8 LEDs. While the system initializes, the CPU halt LED on the RSP8 stays on. It goes off when the boot process is complete. As the RSP8 initializes each interface processor, the status LEDs on each interface processor go on and off in irregular sequence.
Step 3 For a Cisco 7507, Cisco 7507-MX, Cisco 7513, or Cisco 7513-MX with HSA configured, verify that the console terminal displays the system banner and startup screen as the system restarts.
System Bootstrap, Version 12.0(9)S, RELEASED SOFTWARE
Copyright (c) 1986-1999 by cisco Systems, Inc.
SLOT 6 RSP8 is system master
SLOT 7 RSP8 is system slave
RSP8 processor with 128 Mbytes of main memory
[additional displayed text omitted from this example]
Cisco Internetwork Operating System Software
IOS (tm) RSP Software (RSP-JSV-M), Version 12.0(9)S [biff 51096]
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Mon 22-Sep-99 21:15 by biff
Image text-base: 0x600108A0, data-base: 0x607B8000
cisco RSP8 (R7000) processor with 131072K/8216K bytes of memory.
R7000 CPU at 250Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache
[additional displayed text omitted from this example]
2043K bytes of non-volatile configuration memory.
41115648 bytes total (14741504 bytes free)
Slave in slot 7 is halted.
[additional displayed text omitted from this example]
System Bootstrap, Version 12.0(9)S, RELEASED SOFTWARE Copyright (c) 1986-1999 by cisco Systems, Inc. SLOT 2 RSP8 is system master SLOT 3 RSP8 is system slave RSP8 processor with 128 Mbytes of main memory [additional displayed text omitted from this example] Slave in slot 3 is halted.
Step 4 With a single RSP8 (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 12.0(9)S, RELEASED SOFTWARE Copyright (c) 1986-1999 by cisco Systems, Inc. SLOT 6 RSP8 is system master RSP8 processor with 128 Mbytes of main memory [additional displayed text omitted from this example]
Step 5 After the system boots the software and initializes the interface processors, verify that the RSP8 LEDs are in the following states:
Step 6 Verify that all the enabled LEDs (on the interface processors) are on.
Step 7 In systems with a second RSP8 installed (and HSA configured), use the show version command to verify that the slave RSP8 is recognized by the system. Following is a sample from a Cisco 7513:
Router> show version Cisco Internetwork Operating System Software IOS (tm) RSP Software (RSP-JSV-M), Version 12.0(9)S [biff 51096] Copyright (c) 1986-1999 by cisco Systems, Inc. Compiled Mon 22-Sep-99 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 RSP is configured as the slave or the recent crash history of your router.)
When you have verified all the conditions in Step 2 through Step 6 (or Step 7 if you have a second RSP8 installed and want to use the HSA feature), the installation is complete. If you replaced the RSP8 and saved your configuration file to a remote server before doing so, proceed to the "Retrieving the Configuration File" section. If you replaced the RSP8 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 RSP8 installed, you must configure the HSA feature for your Cisco 7507,
Cisco 7507-MX, Cisco 7513, or Cisco 7513-MX router. Read the following caution, and then proceed to the following section, "Configuring High System Availability Operation."
| Caution When you install a second RSP8 card for the first time and plan to enable the HSA feature, you must immediately configure it correctly. See the "Configuring High System Availability Operation" section. This ensures that the new slave is configured consistently with the master. Failure to do so might result in an unconfigured slave RSP8 card taking over control of the router when the master fails, rendering the network inoperable. |
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 RSP8 cards in a single router to improve system availability. HSA is only supported with an RSP8 card in each RSP slot with the Cisco 7507,
Cisco 7507-MX, Cisco 7513, and Cisco 7513-MX routers.
| Caution
To ensure that the slave RSP8 operates properly with the full system configuration should the master RSP8 ever fail, the slave RSP8 must have the same (or higher) DRAM and flash memory capacity as the master RSP8. |
Two RSP8 cards in a router provide the most basic level of increased system availability through a "cold restart" feature. A "cold restart" means that when the master RSP8 card fails, the other RSP8 card reboots the router. In this way, your router is never in a failed state for very long, thereby increasing system availability. The "cold restart" feature only works when the autoboot feature is enabled.
When one RSP8 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 RSP8 card fails and the other takes over:
A router configured for HSA operation has one RSP8 card that is the master and one RSP8 card that is the slave. The master RSP8 card functions as if it were a single processor, controlling all functions of the router. The slave RSP8 card does nothing but actively monitor the master for failure. A system crash can cause the master RSP8 to fail or become nonfunctional. When the slave RSP8 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 RSP8 card is the master and which is the slave upon startup (or reboot).
If a system crash causes the master RSP8 to fail, the slave RSP8 becomes the new master RSP8 and uses its own system image and configuration file to reboot the router. The failed RSP8 card (now the slave) remains inactive until you perform diagnostics, correct the problem, and then enter the
slave reload command at the master RSP8.
| Caution To ensure that the slave RSP8 operates properly with the full system configuration should the master RSP8 ever fail, the slave RSP8 must have the same (or higher) DRAM and flash memory capacity as the master RSP8. See the "Memory Components" section for RSP8 memory component requirements. |
With HSA operation, the following items are important:
| Caution Removing the system master RSP8 while the system is operating will cause the system to crash; however, the system reloads with the slave RSP8 as the new system master provided that the autoboot feature is enabled. To prevent any system problems, do not remove the system master RSP8 while the system is operating. |
The two common ways to use HSA are as follows:
You can also use HSA for advanced implementations. For example, you can configure the RSP8 cards with the following:
To configure HSA operation with the RSP8, you must have a Cisco 7507, Cisco 7507-MX,
Cisco 7513, or Cisco 7513-MX containing one RSP8 master processor card, one RSP8 slave processor card, and Cisco IOS Release 12.0(9)S or a later release of 12.0 S.
| Caution The HSA feature only works with two RSP8 cards. HSA does not operate properly with any other combination of RSP cards. To ensure that the slave RSP8 operates properly with the full system configuration should the master RSP8 ever fail, the slave RSP8 must have the same (or higher) DRAM and flash memory capacity as the master RSP8. See the "Memory Components" section for RSP8 memory component requirements. |
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.
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.
With the simple hardware backup method, you configure both RSP8 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.
Because your view of the environment is always from the master RSP8s perspective, you must define a default slave RSP8. The router uses the default slave information when booting.
To define the default slave RSP8, perform the following steps, beginning in global configuration mode:
| Step | Command | Purpose | ||
| configure terminal | Enter the configuration mode from the terminal. | ||
| slave auto-sync config | Turn on automatic synchronization mode. | ||
| Define the default slave RSP8. | |||
| Ctrl-Z | Exit configuration mode. | ||
| copy system:running-config nvram:startup-config | Save this information to your startup configuration. |
Upon the next system reboot, the above changes take effect (if both RSP8 cards are operational). Thus, the specified default slave becomes the slave RSP8 card. The other RSP8 card takes over control of the system and controls all functions of the router.
If you do not specifically define the default slave RSP8, the RSP8 card located in the higher number processor slot is the default slave. On the Cisco 7507 and Cisco 7507-MX, processor slot 3 contains the default slave RSP. On the Cisco 7513 and Cisco 7513-MX, processor slot 7 contains the default slave RSP.
The following example sets the default slave RSP8 to processor slot 2 on a Cisco 7507 or
Cisco 7507-MX:
Router# configure terminal Router (config)# slave default-slot 2 Ctrl-Z Router# copy system:running-config nvram:startup-config
To ensure that both RSP8 cards have the same system image, perform the following steps in EXEC mode:
The following example ensures that both RSP8 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 RSP8.
Router# show bootvar 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 disk0: -#- -length- -----date/time------ name 1 3482498 May 4 1999 21:38:04 rsp-jsv-m12.0(10)S 7993896 bytes available (1496 bytes used) Router# dir slavedisk0: -#- -length- -----date/time------ name 1 3482498 May 4 1999 21:38:04 rsp-jsv-m12.0(9)S 7993896 bytes available (1496 bytes used) Router# delete slavedisk0:rsp-jsv-m12.0(9)S Router# copy disk0:rsp-jsv-m12.0(10)S slavedisk0:rsp-jsv-m12.0(10)S
To ensure that both RSP8 cards have the same microcode images, perform the following steps in privileged EXEC mode:
| Step | Command | Purpose | ||
| show controllers | 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. | ||
| dir {bootflash: | disk0: | disk1:} | If any interface processors are running from the Flash memory file system, verify the location and version of the master RSP8s supplementary microcode. | ||
| dir {slavebootflash: | slavedisk0: | slavedisk1:} | Determine whether the slave RSP8 contains the same microcode image in the same location. | ||
| copy {bootflash:[filename] | disk0:[filename] | disk1:[filename]}{slavebootflash:[filename] | slavedisk0:[filename] | slavedisk1:[filename]} Note that you might also have to use the delete command in conjunction with the copy command to accomplish this step. | If the slave RSP8 does not contain the same microcode image in the same location, copy the master's microcode image to the appropriate slave location. |
The following example ensures that both RSP8 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 Fast Serial Interface Processor (FSIP) in slot 11 does not use the microcode bundled with the system. Instead, it loads the microcode from disk0:pond/bath/rsp_fsip20-1. Thus, you must ensure that the slave RSP8 has a copy of the same FSIP microcode in the same location.
Router# show controllers
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
disk0: 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
.........
disk1: 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
.......
slot 10: 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 disk0: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 disk0:pond/bath/rsp_fsip20-1
-#- -length- -----date/time------ name
3 10242 Jan 01 1999 03:46:31 pond/bath/rsp_fsip20-1
Router# dir slavedisk0:pond/bath/rsp_fsip20-1
No such file
4079832 bytes available (3915560 bytes used)
Router# copy disk0:pond/bath/rsp_fsip20-1 slavedisk0:
4079704 bytes available on device slavedisk0, proceed? [confirm]
Router# dir slavedisk0:pond/bath/rsp_fsip20-1
-#- -length- -----date/time------ name
3 10242 Mar 01 1999 02:35:04 pond/bath/rsp_fsip20-1
4069460 bytes available (3925932 bytes used)
Router#
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 (system:startup-config) as the target.
Automatic synchronization mode is on by default; however, to turn it on manually, perform the following steps in global configuration mode:
| Step | Command | Purpose | ||
| configure terminal | Enter the configuration mode from the terminal. | ||
| Turn on automatic synchronization mode. | |||
| Ctrl-Z | Exit configuration mode. | ||
| copy system:running-config nvram:startup-config | Save this information to your startup configuration and copy the configuration to the slave's startup configuration. |
The following example turns on automatic configuration file synchronization:
Router# configure terminal Router (config)# slave auto-sync config Router (config)# Ctrl-Z Router# copy system:running-config nvram:startup-config
With the software error protection method, you configure the RSP8 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.)
When the factory sends you a new router with two RSP8s, you receive the same system image on both RSP8 cards. To configure the HSA feature for software error protection, you need two separate software images on the RSP8 cards. Thus, you copy a desired image to the master RSP8 card and modify the boot system commands to reflect booting two separate system images. Each RSP8 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 RSP8, perform the following steps in EXEC mode:
| Step | Command | Purpose | ||
| Verify the location and version of the master RSP8 software image. | |||
| dir {slavebootflash: | slavedisk0: | slavedisk1:} | Determine whether the slave RSP8 contains the same software image in the same location. | ||
| copy source {bootflash: | disk0: | disk1:} | Copy a different system image to the master RSP8. | ||
| configure terminal | Enter configuration mode from the terminal. | ||
| boot system flash bootflash:[filename] | From global configuration mode, configure the master RSP8 to boot the new image from the appropriate location. | ||
| boot system flash bootflash:[filename] | 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 RSP8 and boots the system. Note that because the slave boots this image when the slave is actually the new master RSP8, the command syntax does not use a "slave" prefix. | ||
| Configure the master RSP8 to boot from a network server. | |||
| config-register value 1 | Set the configuration register to enable loading of the system image from a network server or Flash memory. | ||
| Ctrl-Z | Exit configuration mode. | ||
| copy system:running-config nvram:startup-config | 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. | ||
| reload | Reset the router with the new configuration information. |
| 1See the "Software Configuration Register Settings" section for more information on systems that can use this command to modify the software configuration register. |
In the following sample scenario, assume the following:
Figure 8 illustrates the software error protection configuration for this sample scenario. The configuration commands for this configuration follow the figure.
Step 1 Because you always view the environment from the master RSP8s perspective, in the following command you view the master's PC Card slot 0 to verify the location and version of the master's software image:
Router# dir disk0: -#- -length- -----date/time------ name 1 3482496 May 4 1999 21:38:04 rsp-jsv-m12.0(9)S 7993896 bytes available (1496 bytes used)
Step 2 Now view the slave's software image location and version:
Router# dir slavedisk0: -#- -length- -----date/time------ name 1 3482496 May 4 1999 21:38:04 rsp-jsv-m12.0(9)S 7993896 bytes available (1496 bytes used)
Step 3 Because you want to run the Release 12.0(10)S system image on one RSP8 card and the Release 12.0(9)S system image on the other RSP8 card, copy the Release 12.0(10)S system image to the master's slot 0:
Router# copy tftp disk0:rsp-jsv-m12.0(10)S
Step 4 Enter global configuration mode and configure the system to boot first from a
Release 12.0(10)S system image and then from a Release 12.0(9)S system image.
Router# configure terminal Router (config)# boot system flash disk0:rsp-jsv-m12.0(10)S Router (config)# boot system flash disk0:rsp-jsv-m12.0(9)S
With this configuration, when the slot 6 RSP8 card is master, it looks first in its PC Card slot 0 for the system image file rsp-jsv-m12.0(10)S to boot. Finding this file, the router boots from that system image. When the slot 7 RSP8 card is master, it also looks first in its slot 0 for the system image file rsp-jsv-m12.0(10)S to boot. Because that image does not exist in that location, the slot 7 RSP8 card looks for the system image file rsp-jsv-m12.0(9)S in slot 0 to boot. Finding this file in its PC Card slot 0, the router boots from that system image. In this way, each RSP8 card can reboot the system using its own system image when it becomes the master RSP8 card.
Step 5 Configure the system further with a fault-tolerant booting strategy:
Router (config)# boot system tftp rsp-jsv-m12.0(9)S 1.1.1.25
Step 6 Set the configuration register to enable loading of the system image from a network server or from Flash memory and save the changes to the master and the slave startup configuration file:
Router (config)# config-register 0x010F Router (config)# Ctrl-Z Router# copy system:running-config nvram:startup-config
Step 7 Reload the system so that the master RSP8 uses the new Release 12.0(10)S system image:
Router# reload
In the following sample scenario, assume the following:
In this scenario, you begin with the configuration shown in Figure 9.
Next, you copy the rsp-jsv-m12.0(9)S image to the master and the slave RSP8 card, as shown in Figure 10.
Last, delete the rsp-jsv-m12.0(10)S image from the slave RSP8 card, as shown in Figure 11:
The following commands configure software error protection for this sample scenario.
Step 1 View the master and the slave slot 0 to verify the location and version of their software images:
Router# dir disk0: -#- -length- -----date/time------ name 1 3482498 May 4 1999 21:38:04 rsp-jsv-m12.0(10)S 7993896 bytes available (1496 bytes used) Router# dir slavedisk0: -#- -length- -----date/time------ name 1 3482498 May 4 1999 21:38:04 rsp-jsv-m12.0(10)S 7993896 bytes available (1496 bytes used)
Step 2 Copy the Release 12.0(9)S system image to the master and the slave PC Card slot 0:
Router# copy tftp disk0:rsp-jsv-m12.0(9)S Router# copy tftp slavedisk0:rsp-jsv-m12.0(9)S
Step 3 Delete the rsp-jsv-m12.0(10)S image from the slave RSP8 card:
Router# delete slavedisk0:rsp-jsv-m12.0(10)S
Step 4 Configure the system to boot first from a Release 12.0(10)S system image and then from a Release 12.0(9)S system image.
Router# configure terminal Router (config)# boot system flash disk0:rsp-jsv-m12.0(10)S Router (config)# boot system flash disk0:rsp-jsv-m12.0(9)S
Step 5 Configure the system further with a fault-tolerant booting strategy:
Router(config)# boot system tftp rsp-jsv-m12.0(9)S 1.1.1.25
Step 6 Set the configuration register to enable loading of the system image from a network server or from Flash memory and save the changes to the master and the slave startup configuration file:
Router(config)# config-register 0x010F Crtl-Z Router# copy system:running-config nvram:startup-config
You can optionally set environment variables on both RSP8 cards in a Cisco 7507, Cisco 7507-MX, Cisco 7513, or a Cisco 7513-MX.
You set environment variables on the master RSP8 just as you would if it were the only RSP8 card in the system. You can set the same environment variables on the slave RSP8 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.
Once you set the master's environment variables, you can manually set the same environment variables on the slave RSP8 card using the slave sync config command.
To manually set environment variables on the slave RSP8, perform the following steps in global configuration mode:
| Step | Command | Purpose | ||
| boot system boot bootldr boot config | 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. | ||
| copy system:running-config nvram:startup-config | Save the settings to the startup configuration. This also puts the information under that RSP8 card's ROM monitor control. | ||
| Save the same environment variables to the slave RSP8 by manually synchronizing their configuration files. | |||
| show bootvar | Verify the environment variable settings. |
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.
To set environment variables on the slave RSP8 when automatic synchronization is on, perform the following steps in global configuration mode:
| Step | Command | Purpose | ||
| boot system boot bootldr boot config | 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. | ||
| copy system:running-config nvram:startup-config | Save the settings to the startup configuration. This also puts the information under that RSP8 card's ROM monitor control. | ||
| show bootvar | Verify the environment variable settings. |
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:
Router(config)# slave image {system|device:filename}
Router# slave sync config
| Caution When you install a second RSP8 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 RSP8 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.
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 RSP8s and each interface processor.
Following are functional descriptions of the LEDs on the power supplies and processor modules, and the behavior you should observe at system startup.
On the router, the AC (or DC) OK LED is located on each power supply. If this LED does not go on and stay on, there is most likely a problem with the input power or one of the internal DC lines.
The AC (or DC) OK LED will not go on or will go off if the power supply reaches an out-of-tolerance temperature or voltage condition. It is unlikely that the power supply will shut down during startup because of an 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.
Figure 12 shows the LEDs on the RSP8 faceplate. The LEDs on the RSP8 indicate the system and RSP8 status and which PC Card slot is active. The CPU halt LED, which goes on only if the system detects a processor hardware failure, should remain off. A successful boot is indicated when the normal LED goes on; however, this does not necessarily mean that the system has reached normal operation. During normal operation, the CPU halt LED should be off, and the normal LED should be on, indicating that the RSP8 is receiving +5V. The slot 0 and slot 1 LEDs indicate which PC Card slot is in use, and each LED blinks when the card is accessed by the system. The master and the slave LEDs provide a visual indication of whether the RSP8 is designated a master or a slave device.
| Caution The reset switch (see Figure 12) resets the RSP8 and the entire system. To prevent system errors and problems, use it only at the direction of your Cisco-certified service representative. |
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:
By checking the state of the LEDs, you can determine when and where the system failed in the startup sequence. Because you turn on the system power with the on/off switches on each
power supply, it is easiest to observe the startup behavior from the rear of the router. Use the following descriptions of the normal startup sequence to isolate the problem, and then use the troubleshooting procedures wherever the system fails to operate as expected. If you are able to isolate the problem to a faulty hardware component, or if you are unable to successfully restart the system, see the end of this document for instructions on contacting a service representative.
During the boot sequence, the system banner display pauses while it initializes the memory. Since your RSP8 has more than 32 MB of DRAM, you might notice an increase in the amount of time required to initialize the memory. The pause in the banner display occurs after the copyright line and before the system displays the list of installed hardware, as shown in the following display:
%SYS-5-RELOAD: Reload requested System Bootstrap, Version 12.0(9)S Copyright (c) 1986-1999 by cisco Systems, Inc. [System initializes memory at this point in the display]
Use the following startup sequences and troubleshooting procedures to isolate system problems:
Step 1 When you restart the system, the system power and AC (DC) OK LEDs should go on.
When the system power LED indicates normal operation, proceed to the next step.
Step 2 Listen for the system blower and observe the fan OK LED. You should hear the system blower start operating immediately after you turn on the system power. If you determine that the power supply is functioning normally and that an internal fan (or the system blower) is faulty, contact a service representative. If the blower or a power supply fan does not function properly at initial startup, you cannot make any installation adjustments.
Step 3 When you have verified that the power supply is functioning properly, observe the LEDs on the RSP8. The CPU halt LED on the RSP8 should always remain off. If it goes on during the startup sequence, the system has encountered a processor hardware error.
Step 4 During the boot process, the LEDs on most of the interfaces light in irregular sequence; this does not indicate either correct system startup or failure.
Step 5 When the system boot is complete, the RSP8 begins to initialize the interface processors. During this initialization, the LEDs on each interface processor behave differently (most flash on and off). The enabled LED on each interface processor goes on when initialization has been completed.
Step 6 When the system boot is complete and all interface processors have been initialized, the master RSP8s console screen displays a script and a system banner similar to the following:
System Bootstrap, Version 12.0(9)S, RELEASED SOFTWARE Copyright (c) 1986-1999 by cisco Systems, Inc. SLOT 6 RSP8 is system master (SLOT 2 for a Cisco 7507) SLOT 7 RSP8 is system slave (SLOT 3 for a Cisco 7507, if installed) RSP8 processor with 128 Mbytes of main memory ROM: System Bootstrap, Version 12.0(9)S [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 6 RSP8 is system master SLOT 7 RSP8 is system slave RSP8 processor with 128 Mbytes of main memory [additional displayed text omitted from this example]
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.
When a new master RSP8 takes over ownership of the router, it automatically reboots the failed RSP8 as the slave RSP. You can access the state of the failed RSP8 in the form of a stack trace from the master console using the show stacks command.
Router(config)# slave reload
| Tasks | Command |
Display the environment variable settings and configuration register settings for the master and the slave RSP8 cards. | show boot var |
Show a list of Flash devices currently supported on the router. | |
Display the software version running on the master and the slave RSP8 card. | |
Display the stack trace and version information of the master and the slave RSP8 cards. | show stacks 1 |
| 1This command is documented in the "System Management Commands" chapter of the Configuration Fundamentals Command Reference publication. |
The following sections include important reference information and configuration and maintenance procedures for the RSP8. The following sections are included:
The console port on the RSP8 is an EIA/TIA-232, DCE, DB-25 receptacle. Both Data Set Ready (DSR) and Data Carrier Detect (DCD) are active when the system is running. The Request to Send (RTS) signal tracks the state of the Clear to Send (CTS) input. The console port does not support modem control or hardware flow control. The console port requires a straight-through EIA/TIA-232 cable. Table 3 lists the signals used on this port.
| 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) |
The auxiliary port on the RSP8 is an EIA/TIA-232 DTE, DB-25 plug to which you can attach a CSU or DSU or other equipment in order to access the router from the network. The asynchronous auxiliary port supports hardware flow control and modem control. Table 4 lists the signals used on this port.
| 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) |
The console and auxiliary Y-cables allow you to simultaneously connect the console ports or auxiliary ports on two RSPs (configured as system master and slave in RSP slots 2 and 3 in the
Cisco 7507 and Cisco 7507-MX, and RSP slots 6 and 7 in the Cisco 7513 and Cisco 7513-MX) to one console terminal or external auxiliary device (such as a modem).
The two Y-cables (Product Number CAB-RSP8CON=, shown in Figure 6 on page 24, and
Product Number CAB-RSP8AUX=, shown in Figure 7 on page 24) 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.
| 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) |
| 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 |
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 RSP8. The DRAM DIMM sockets are U12 (bank 0) and U15 (bank 1). (See Figure 13 and Table 7.) The default DRAM configuration is 64 MB (installed on the RSP8 as either two 32-MB DIMMs, or a single 64-MB DIMM). If two different sizes of DRAM DIMMs are installed, U12 (slot 0) 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 an RSP8. The RSP8 requires DRAM dual in-line memory modules (DIMMs). |
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 (U12 and U15). 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 routers configuration and the protocols and features your system is running, you might require more than the 64 MB of DRAM that is shipped with the RSP8. Upgrade your system DRAM based on your current configuration, this potential requirement, and the information in Table 7.
| DRAM Sockets | Quantity | Totals | Product Numbers |
U12 and U15 or U12 | Two 32-MB DIMMs or one 64-MB DIMM | 64 MB | MEM-RSP8-64M=1 |
U12 | One 128-MB DIMM | 128 MB | MEM-RSP8-128M= |
U12 and U15 | Two 128-MB DIMMs | 256 MB | MEM-RSP8-256M= |
| 1The RSP8s default DRAM configuration is 64-MB. The RSP8 ships with either two 32-MB DIMMS or one 64-MB DIMM. When using the MEM-RSP8-64M= part number to order spare DRAM, note that two 32-MB DIMMS are currently shipped. As DRAM supplies warrant, these orders may be fulfilled with one 64-MB DIMM in the future. |
| Caution To prevent system and memory problems when you install DRAM, the RSP8s 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 RSP8s DIMM sockets. To prevent ESD damage, handle DIMMs by the card edges only. |
Two different sizes of DRAM DIMMs can occupy the two DRAM DIMM sockets (U12 and U15); however, the larger DRAM DIMM must occupy the U12 socket.
| Caution To prevent system and memory problems when installing two different sized DIMMs on an RSP8, remember that U12 must contain the largest DRAM DIMM. |
This section discusses the procedure for removing DIMMs from your RSP8.
Use this procedure to remove the existing DIMM(s):
Step 1 Turn off the system power and follow the steps in the "Removing the RSP8" section.
Step 2 Place the RSP8 on an antistatic mat or pad and ensure that you are wearing an antistatic device, such as a wrist strap.
Step 3 Position the RSP8 so that the faceplate is toward you and the bus connectors are away from you---this position is shown in Figure 13.
Step 4 Locate the DRAM DIMMs on the RSP8. The DIMMs occupy U12 (bank 0) and U15 (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.)
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.
This section discusses the procedure for installing DIMMs on your RSP8.
| Caution To prevent system and memory problems when you install DRAM, the RSP8s 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 RSP8s 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.) |
Use this procedure to install new DIMMs:
Step 1 Place the RSP8 on an antistatic mat or pad, and ensure that you are wearing an antistatic device, such as a wrist strap.
Step 2 Position the RSP8 so that the faceplate is toward you and the bus connectors are away from you, as shown in Figure 13 on page 51.
| 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 RSP8. (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 RSP8; this procedure is required if you plan to install any 128-MB DIMMs. |
Step 3 With the RSP8 positioned as shown in Figure 17, locate the screw shown in the enlargement; this is where you attach the protective post to your RSP8.
Step 4 Carefully remove the screw from the RSP8 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 RSP8s printed circuit board, do not overtighten the screw. |
Step 6 Position the post correctly; attach the screw and post to the RSP8. (See Figure 18c.) Carefully note the proper orientation of the protective post, as shown in Figure 18c.
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 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.
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 RSP8 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.
This section provides information for checking the DIMM installation.
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 RSP8, 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. 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 RSP8 in the router, proceed to the "Replacing the RSP8" section, and then restart the system for an RSP8 installation check.
Settings for the 16-bit software configuration register are written into the NVRAM. Following are some reasons for changing the software configuration register settings:
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. |
| Bit Number1 | Hexadecimal | Meaning |
|---|---|---|
00 to 0F | 0x0000 to 0x000F | Boot field (see Table 9) |
06 | 0x0040 | Causes system software to ignore NVRAM contents |
07 | 0x0080 | OEM bit enabled2 |
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 |
| 1The 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). 2OEM = original equipment manufacturer. |
| 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 network boot filename Enables boot system commands that override the default network boot filename |
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 for further commands, as shown in the following example:
Router# configure terminal 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.
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:
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.)
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# config-register 0x102 Router(config)# boot system flash [filename] 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.
| 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.
| 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.)
| 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.
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:, disk0:, or disk1:, 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 Router#
An overview of the procedure for recovering a lost password follows:
To recover a lost password, follow these steps.
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 a lost password.
The Flash memory (PC Card) slots on the front panel of the RSP8 support PC Card-based Flash memory media for your system. You can use this Flash memory to store and run IOS software images, or as a file server for other routers to access as clients. Optionally, you can install a second Flash Disk or Flash memory card for redundancy.
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:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
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 current 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. You can also access Cisco 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 product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
Posted: Tue Feb 1 15:14:33 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.