|
|
Product Numbers:
RSP2=
ROMMON-RSP2=
MEM-RSP-8M=
MEM-RSP-16M
MEM-RSP-24M
MEM-RSP-32M(=)
MEM-RSP-64M(=)
MEM-RSP-128M(=)
This configuration note describes the Route Switch Processor (RSP2), which is the main processor module for the Cisco 7505 router. The RSP2 combines all of the switched routing and high-speed switching functions required by the Cisco 7500 series routers. (For more information about the RSP2, see the "Product Description" section.)
The RSP2 supports high system availability (HSA), which is a feature in Cisco IOS Release 11.1(4) or a later release of 11.1, that allows two RSPs to be used simultaneously in a Cisco 7507,
Cisco 7507-MX, Cisco 7513, or Cisco 7513-MX router. One RSP operates as the system master and the other RSP operates as the system slave, which takes over if the master RSP fails. (The HSA feature is not supported in the Cisco 7505 or Cisco 7576. It is also not supported when the RSP2 is used with the RSP8.)
 | Caution
Cisco strongly recommends that you do not use the RSP2 in the Cisco 7507-MX, Cisco 7513-MX, and Cisco 7576. The Cisco 7507-MX and Cisco 7513-MX routers ship by default with an RSP8. The HSA feature does not function when the RSP2 is used with the RSP8. Throughout the remainder of this document, references made to the HSA feature are limited to Cisco 7507 and Cisco 7513 routers configured with RSP2s. |
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:
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 will perform, and that you have all the parts and tools you will need. Also, review safety and ESD-prevention guidelines to help you to avoid injury or damage to the equipment.
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.
Follow these basic guidelines when working with any electrical equipment:
Use the following guidelines when working with any equipment that is connected to telephone wiring or to other network cabling:
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. |
This section describes important compatibility requirements for the RSP2.
There are no restrictions on installing an RSP2 in a Cisco 7505. However, the Cisco 7505 does not support the HSA feature.
There are no restrictions on installing an RSP2 in a Cisco 7507 provided that you install the RSP2 in slot 2 or slot 3. (With the HSA feature enabled, you use both RSP slots.)
There are no restrictions on installing an RSP2 in a Cisco 7513 provided that you install the RSP2 in slot 6 or slot 7. (With the HSA feature enabled, you use both RSP slots.)
There are no restrictions on installing an RSP2 in a Cisco 7576 provided that you install the RSP2 in slot 6 (for router A) or slot 7 (for router B). (The Cisco 7576 does not support the HSA feature and Cisco does not recommend the use of an RSP2 with the Cisco 7576.)
Installing two RSP2s in the Cisco 7507 or Cisco 7513 assumes you plan to enable and configure the HSA feature.
Although the PC Card (formerly called PCMCIA) and DRAM SIMM specifications are defined in the manufacturers' part numbers, they must meet the following requirements:
The RSP2 is compatible with IOS Release 10.3(571) or a later release of 10.3. The HSA feature requires Cisco IOS Release 11.1(4) or a later release of 11.1.
The show version and show hardware commands display the current hardware configuration of the router, including the system software version that is currently loaded and running. The show microcode command lists the bundled microcode (target hardware) version for each processor type. The show controller cbus command shows the microcode version you are running. (For complete descriptions of show commands, refer to the Configuration Fundamentals Configuration Guide and Configuration Fundamentals Command Reference publications, which are available on the Documentation CD-ROM or as printed copies.)
You can determine the current version of software or microcode stored in ROM in either of two ways: removing the processor module and checking the ROM labels; configuring the system to boot the system software or microcode from ROM, reloading the system, and using show commands to check the version that is loaded and running. Refer to the appropriate software documentation for complete configuration instructions and examples.
Second-generation Versatile Interface Processors (VIP2s) can be used in Cisco 7507 and Cisco 7513 routers configured for HSA, provided that the Cisco 7507 or Cisco 7513 routers are running Cisco IOS Release 11.1(6)CA or a later release of 11.1. (For additional details on the HSA feature, see the "HSA System Requirements" section.)
The minimum required DRAM configuration for the RSP2s in your system is 32 MB. The HSA feature requires that the boot read-only memory (ROM) device (U30, shown in the "Memory Components" section) be updated to Version 11.1(2) or a later release of 11.1 (ROMMON-RSP2=).
New RSP2s are shipping with this new boot ROM version; however, to check the boot ROM (also called the system bootstrap) version currently running on your RSP2, use the show version command and check the boot ROM version number as follows:
Router# show version (display text omitted) System Bootstrap, Version 11.1(2)
| Caution Changing the boot ROM device on the RSP2 will make your current configuration file unreadable and unusable. If you do not save the system configuration file before changing the boot ROM, you must then use the configure command or the setup command facility to reenter the configuration information after the RSP2 is reinstalled. We recommend that you save the system configuration file to a TFTP server or a Flash memory card before you replace the boot ROM. See the "Saving and Retrieving the Configuration File" section. |
| Caution To ensure that the slave RSP2 will operate properly with the full system configuration, should the master RSP2 ever fail, the slave RSP2 should have the same DRAM configuration as the master RSP2. In addition, removing the system master RSP2 while the system is operating will cause the system to crash; however, the system will reload with the slave RSP2 as the new system master. To prevent any system problems, do not remove the system master RSP2 while the system is operating. |
If you have a Cisco 7507 or a Cisco 7513 with an RSP2 configured as the system slave, we strongly recommend that you use the following procedure to remove and replace an interface processor:
Step 1 Remove the slave RSP2.
Step 2 Wait 15 seconds.
Step 3 Remove and replace the interface processor, using the procedures in the configuration note that shipped with your interface processor or in the Cisco 7500 Series Installation and Configuration Guide.
Step 4 Wait 15 seconds.
Step 5 Reinsert the slave RSP2.
Microcode is a set of processor-specific software instructions that enables and manages the features and functions of a specific processor type. At system startup or reload, the system loads the microcode for each processor type present in the system. The latest available microcode image for each processor type is bundled and distributed with the system software image.
New microcode is released to enable new features, improve performance, or fix bugs in earlier versions. The Cisco routers feature downloadable software and microcode for most upgrades. These features enable you to download new (upgraded) images remotely, store the images in router memory, and load the new images at system startup without having to physically access the router.
You can store multiple versions for a specific processor type in Flash memory and use configuration commands to specify which version the system should load at startup. All interfaces of the same type (for example, all CIP2s) use the same microcode image. Although most upgrades can be downloaded, some exceptions require ROM replacement to ensure proper startup and operation.
Microcode images that are bundled with the system image load automatically along with the new software image, except for the Channel Interface Processor (CIP) microcode image, which is bundled separately.
You need some or all of the following parts and tools to remove and replace an RSP2. If you need additional equipment, contact a customer service representative for ordering information.
This section describes the procedures for saving (copying) and retrieving a system configuration file using a TFTP server.
Configuration information resides in two places when the router is operating: the default startup (permanent) configuration in NVRAM, and the running (temporary) configuration in DRAM. The startup configuration always remains available; NVRAM retains the information even when the power is shut down. The running configuration is lost if the system power is shut down. The startup configuration (in NVRAM) contains all nondefault configuration information that you added with the configure command or the setup command facility, or by editing the configuration file.
The copy running-config startup-config command adds the current configuration to the default configuration in NVRAM, so that it will also be saved when power is shut down. Whenever you make changes to the system configuration, issue the copy running-config startup-config command to ensure that the new configuration is saved.
If you replace the RSP2 in a system with only one RSP2, you also replace the entire configuration (NVRAM resides in socket U18 on the RSP2). If you copy the configuration file to a remote server before removing the RSP2, you can retrieve it later and write it into NVRAM on the new RSP2.
If you do not copy the configuration file, you will have to use the configure command or the setup command facility to reenter the configuration information after you install the new RSP2. For complete descriptions of these commands and instructions for using them, refer to the appropriate software documentation.
The preceding procedure is not necessary if you are temporarily removing an RSP2; the lithium batteries will retain the configuration in memory until you replace the RSP2 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 ping program. The ping program sends a series of echo request packets to the remote device and waits for a reply. If the connection is good, the remote device echoes them back to the local device.
The console terminal displays the results of each message sent: an exclamation point (!) indicates that the local device received an echo, and a period (.) indicates that the server timed out while awaiting the reply. If the connection between the two devices is good, the system displays a series of exclamation points (! ! !) or [ok]. If the connection fails, the system displays a series of periods (. . .) or [timed out] or [failed].
To verify the connection between the router and a remote host, issue the ping command followed by the name or 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 refer to the end of this document for instructions on contacting technical assistance.
Before you copy the running configuration to the TFTP file server, ensure the following:
To store information on a remote host, enter the copy startup-config tftp privileged EXEC command. The command prompts you for the destination host's address and a filename, and then displays the instructions for confirmation. When you confirm the instructions, the router sends a copy of the currently running configuration to the remote host. The system default is to store the configuration in a file called by the name of the router with -confg appended. You can either accept the default filename by pressing Return at the prompt, or enter a different name before pressing Return.
Use the following procedure 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, enable the privileged level.
Step 2 Use the ping command to check the connection between the router and the remote host. (See the previous section, "Using the ping Command to Ensure Connectivity.")
Step 3 Issue the show running-config (or write term) command to display the currently running configuration on the terminal, and ensure that the configuration information is complete and correct. If it is not, use the configure command to add or modify the existing configuration. (Refer to the appropriate software documentation for descriptions of the configuration options available for the system and individual interfaces, and for specific configuration instructions.)
Step 4 Create a file on the TFTP server.
Step 5 Issue the copy startup-config tftp command. The EXEC command interpreter prompts you for the name or interface processor address of the remote host that is to receive the configuration file. (The prompt might include the name or address of a default file server.)
Router# copy startup-config tftp Remote host []?
Step 6 Enter the name or interface processor address of the remote host. In the following example, the name of the remote server is servername:
Router# copy startup-config tftp Remote host []? servername Translating "servername"...domain server (1.1.1.1) [OK]
Step 7 The EXEC command interpreter prompts you for the name of the file that will contain the configuration. By default, the system appends -confg to the router's name to create the new filename. Press Return to accept the default filename, or enter a different name for the file before pressing Return. In the following example, the default is accepted:
Name of configuration file to write [Router-confg]? Write file Router-confg on host 1.1.1.1? [confirm] Writing Router-confg .....
Step 8 Before the router executes the copy process, it displays the instructions you entered for confirmation. If the instructions are not correct, enter n (no) and then press Return to abort the process. To accept the instructions, press Return or y and then Return, and the system begins the copy process. In the following example, the default is accepted:
Write file Router-confg on host 1.1.1.1? [confirm] Writing Router-confg: !!!! [ok]
While the router copies the configuration to the remote host, it displays a series of exclamation points (! ! !) or periods (. . .). The !!!! and [ok] indicate that the operation is successful. A display of . . . [timed out] or [failed] indicates a failure, which would probably be due to a network fault or the lack of a writable, readable file on the remote file server.
Step 9 If the display indicates that the process was successful (with the series of ! ! ! and [ok]), the copy process is complete. The configuration is safely stored in the temporary file on the remote file server.
If the display indicates that the process failed (with the series of . . . as shown in the following example):
Writing Router-confg .....
your configuration was not saved. Repeat the preceding steps, or select a different remote file server and repeat the preceding steps.
Step 10 To further ensure that the configuration file was copied correctly, issue the show startup-config command and look at the first line for the configuration file's size. Compare it with the file you copied to the TFTP server. Following is an example. (Take special note of the line preceded by >>.)
Router# show startup-config >> Using 1186 out of 126968 bytes ! version 11.1 hostname Router Router#
After you copy the configuration file, proceed to the following section, "Retrieving the Configuration File," after you have replaced the boot ROM and reinstalled the RSP2. If you are unable to copy the configuration file to a remote host successfully, contact your network administrator or see the end of this document for instructions on contacting technical assistance.
After you reinstall the RSP2, you can retrieve the saved configuration and copy it back 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.
Use the following procedure 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, 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, issue the copy tftp startup-config command and press Return to enter the configuration mode and specify that you will configure the system from a network device (instead of from the console terminal, which is the default).
Router# copy tftp startup-config
Step 5 The system prompts you for the IP address of the host. Enter the IP address or name of the remote host (the remote TFTP server to which you originally saved the configuration file).
Address of remote host [255.255.255.255]? 10.1.1.1
Step 6 The system prompts you to select a host or network configuration file. The default is host; press Return to accept the default.
Name of configuration file [Router-confg]? Router-confg
Step 7 The system prompts you for the name of the configuration file. When copying the file, the default is to use the name of the router with the suffix -confg (router-confg in the following example). If you specified a different filename when you copied the configuration, enter the filename; otherwise, press Return to accept the default.
Name of configuration file [Router-confg]?
Step 8 Before the system reloads the new configuration file in NVRAM, it displays the instructions you entered for confirmation. If the instructions are not correct, enter n (no), and then press Return to cancel the process. To accept the instructions, press Return or y, and then 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 9 If the display indicates that the process was successful, as shown in Step 8, 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 10 To ensure that the configuration file was retrieved correctly, issue the show startup-config command and look at the first line for the configuration file's size. Match it with the file you retrieved from the TFTP server. Following is an example:
Router# show startup-config Using 1186 out of 126968 bytes ! version 11.1 hostname Router ! Router#
Step 11 Ensure that the startup configuration file stored in NVRAM is the default running configuration file used by the system, and then issue the copy startup-config running-config command as follows:
Router# copy startup-config running-config Router# %SYS-5-CONFIG_I: Configured from memory by console Router#
This completes the procedure for retrieving the saved configuration file.
The RSP2 is the main system processor module for the Cisco 7505 router. It combines all of the switched routing and high-speed switching functions of the separate Route Processor (RP) and Switch Processor (SP), which are used in the Cisco 7000 series routers. The RSP2 supports high system availability (HSA), which is a feature in Cisco IOS Release 11.1(4) or a later release of 11.1, that allows two RSPs to be used in a Cisco 7507 or Cisco 7513 router. By default, the system master is the RSP that occupies the first RSP slot in the router: slot 2 in the Cisco 7507, and slot 6 in the Cisco 7513. The HSA feature is not supported by the Cisco 7505 and Cisco 7576 routers.
The RSP2 contains the central processing unit (CPU) and most of the memory components for the router. The IOS software images reside in Flash memory, which is located either on the RSP2, in the form of a single in-line memory module (SIMM), or on up to two PC Cards (called Flash memory cards) that insert in the two PC Card slots (slot 0 and slot 1) on the front of the RSP2. (See Figure 1.)
Storing the IOS software images in Flash memory enables you to download and boot from upgraded IOS software images remotely or from software images resident in the RSP2 Flash memory, without having to remove and replace read-only memory (ROM) devices.
The RSP2 uses a software-controlled configuration register, so you do not have to remove the RSP2 to configure jumpers. There are no user-configurable jumpers on the RSP2.
The RSP2 contains the following components:
In addition to the system software, the RSP2 contains and executes the following management functions that control the system:
The high-speed switching section of the RSP2 communicates with and controls the interface processors on the high-speed CyBus. This switching section decides the destination of a packet and switches it based on that decision. The RSP2 uses a 16-million-instructions-per-second (mips) processor to provide high-speed, autonomous switching and routing.
Figure 1 shows the various types of memory components on the RSP2, and Table 1 lists the functions of each type.
| Type | Size | Quantity | Description | Location |
|---|---|---|---|---|
DRAM | 32 to 128 MB | 2 to 4 | 16- or 32-MB SIMMs (based on maximum DRAM required). | Bank 0: U21 and U33 Bank 1: U12 and U4 |
NVRAM | 128 KB | 1 | Nonvolatile SRAM for the system configuration file.1 | U18 |
Flash SIMM | 8 MB | 1 | Contains the IOS software images on the RSP2. | U1 |
Boot ROM3 | 256 KB | 1 | EPROM for the ROM monitor program. | U30 |
The Cisco 7505, Cisco 7507, and Cisco 7513 routers support downloadable system software and microcode for most IOS software and microcode upgrades. This download feature enables you to remotely download, store, and boot from a new image. Flash memory contains the default system software. An erasable programmable read-only memory (EPROM) device contains the latest microcode version, in compressed form, for each interface processor. At system startup, an internal system utility scans for compatibility problems between the installed interface processor types and the bundled microcode images, and then decompresses the images into running DRAM. The bundled microcode images then function the same as the EPROM images.
DRAM stores routing tables, protocols, and network accounting applications. The standard RSP2 configuration is 32 MB of DRAM, with up to 128 MB available through SIMM upgrades.
The system configuration, software configuration register settings, and environmental monitoring logs are contained in the 128-KB NVRAM, which is backed up with built-in lithium batteries that retain the contents for a minimum of 5 years. When replacing an RSP2, be sure to back up your configuration to a remote server so you can retrieve it later.
| Caution Before you replace an RSP2 in a system with one RSP2, back up the running configuration to a TFTP file server so you can retrieve it later. If the configuration is not saved, the entire configuration is lost---inside the NVRAM on the removed RSP2---and you must reenter the entire configuration manually. For instructions on how to save the configuration file, see the "Saving and Retrieving the Configuration File" section. This procedure is not necessary if you are temporarily removing an RSP2; lithium batteries retain the configuration in memory until you replace the RSP2 in the system. |
Both the onboard and PC Card-based Flash memory allow you to remotely load and store multiple IOS software and microcode images. You can download a new image over the network or from a local server and then add the new image to Flash memory or replace the existing files. You can then boot routers either manually or automatically from any of the stored images. Flash memory also functions as a TFTP server to allow other servers to boot remotely from stored images or to copy them into their own Flash memory.
Before you can use a Flash memory card that was previously used on a Route Processor (RP) in a Cisco 7000 series router, you must reformat the Flash memory card. Flash memory cards formatted on RP-based (Cisco 7000 series) routers do not work properly in RSP2-based routers.
There are no user-configurable jumpers on the RSP2.
Two LEDs on the RSP2, normal and CPU halt, indicate the system and RSP2 status. The normal LED is on when the system is operational and indicates that the RSP2 is receiving +5V. During normal operation, the CPU halt LED should be off. The CPU halt LED goes on only if the system detects a processor hardware failure. The RSP2 controls both LEDs and turns both on in parallel to indicate that the system is operational. The master and slave LEDs indicate whether an RSP2 is the CyBus master or a slave to the CyBus master.
The RSP2 has two PC Card slots available. Either slot can support a Flash memory card or an input/output (I/O) device. Type I and Type II PC Cards can be used in PC Card slot 0 and slot 1. Not all Flash memory cards that are commercially available are supported, and not all I/O devices are supported. The RSP2 also supports the use of Flash Disks for storage of Cisco IOS images, microcode images, and configuration files, and as TFTP servers.
Two asynchronous serial ports on the RSP2, the console and auxiliary ports, allow you to connect external devices to monitor and manage the system. The console port is an EIA/TIA-232 receptacle (female) that provides a DCE interface for connecting a console terminal.
The auxiliary port is an EIA/TIA-232 plug (male) that provides a DTE interface; the auxiliary port supports flow control and is often used to connect a modem, a CSU, or other optional equipment for Telnet management.
The following sections describe the procedures for installing or replacing an RSP2. Ensure that your system meets the minimum software, hardware, and microcode requirements described in the following sections: the "Software Prerequisites" section; the "Hardware Prerequisites" section; and the "Microcode Requirements" section.
For instructions on removing the RSP2, proceed to the section "Removing the RSP2" and then to the section "Replacing the RSP2" for the installation instructions. After the new RSP2 is secure and to verify that it is installed and functioning properly, use the procedures in the "Troubleshooting the Installation" section.
| Caution Removing the only installed RSP2 from a system while the system is operating causes the system to crash. Consider this before removing an RSP2 while the system is operating. To ensure that the slave RSP2 will operate properly with the full system configuration should the master RSP2 ever fail, the slave RSP2 should have the same DRAM configuration as the master RSP2. |
When you remove or install the RSP2, be sure to use the ejector levers, which help to ensure that the RSP2 is fully inserted in the backplane or fully dislodged from it. An RSP2 that is only partially connected to the backplane can halt the system, unless a second RSP2 is installed. Figure 2 on page 21 shows a detail of the ejector lever mechanism. When you simultaneously push the ejector levers inward (toward the carrier handle), the levers push the RSP2 into the slot and ensure that the board connectors are fully seated in the backplane. Use the following procedure to remove the RSP2:
Step 1 Optional step: If you are replacing the RSP2 in a system with one RSP2, copy the currently running configuration file to a TFTP server so you can retrieve it later. (See the "Saving and Retrieving the Configuration File" section.)
Step 2 Slip on an antistatic strap and connect the equipment end of the strap to a captive installation screw on an installed interface processor, or to the chassis ground screw that is located to the left of the power receptacle.
Step 3 If you are replacing the RSP2, disconnect any devices that are attached to the console or auxiliary ports. If you are removing the RSP2 for maintenance and will reinstall the same one, you can leave the devices attached provided that doing so will not strain the cables.
Step 4 Use a screwdriver (number 2 Phillips or 1/4-inch flat-blade) to loosen the two captive installation screws. (See Figure 2 on page 21.)
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 2c) to release the carrier from the slot and to dislodge the RSP2 from the backplane.
Step 6 Grasp the handle of the RSP2 with one hand and pull the RSP2 straight out of the slot, keeping your other hand under the carrier to guide it. (See Figure 2.) Keep the carrier at a parallel orientation to the backplane. Avoid touching the board or any connector pins.
Step 7 Place the removed RSP2 on an antistatic mat or foam. If you plan to return the RSP2 to the factory, immediately place it in an antistatic bag to prevent ESD damage.
This completes the removal procedure. If you removed the RSP2 to replace SIMMs, proceed to the appropriate section. If you are replacing the RSP2, proceed to the next section to install the new RSP2.
The RSP2 is keyed for installation only in an RSP slot. By default, the system master is the RSP2 that occupies the first RSP slot in the router: slot 4 in the Cisco 7505, slot 2 in the
Cisco 7507, and slot 6 in the Cisco 7513. Use the following procedure to install an RSP2:
Step 1 Grasp the RSP2 handle with one hand and place your other hand under the carrier to support and guide it into the slot. (See Figure 2.) Avoid touching the board or any connectors.
Step 2 Place the back of the RSP2 in the appropriate RSP slot and align the notches along the edge of the carrier with the grooves in the slot. (See Figure 2a.)
| Caution To prevent damage to the backplane, you must install the RSP2 in the RSP slots on the router. The RSP slots are keyed for correct installation. Forcing the RSP2 into a different slot can damage the backplane and the RSP2. |
Step 3 While keeping the RSP2 at a parallel orientation to the backplane, carefully slide the carrier into the slot until the RSP2 faceplate makes contact with the ejector levers, and then stop. (See Figure 2b.)
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 at a full parallel orientation to the faceplate. (See Figure 2c.)
Step 5 Use a screwdriver (number 2 Phillips or 1/4-inch flat-blade) to tighten the captive installation screws on the ends of the RSP2. (See Figure 2a.)
Step 6 Use a screwdriver to tighten the two captive screws on the RSP2 faceplate to prevent the RSP2 from becoming partially dislodged from the backplane and to ensure proper EMI shielding. (These screws must be tightened to meet EMI specifications.)
Step 7 If you disconnected the console terminal to remove the RSP2, or if you are installing a new RSP2, connect the console terminal to the console port. (See the "Connecting the Console Terminal" section.)
Step 8 Ensure that the console terminal is turned on.
Step 9 Turn system power back on and proceed to the "Restarting the System" section to check the installation.
The system console port on the RSP2 is a DCE DB-25 receptacle for connecting a consloe terminal, which you will need to configure and communicate with your system. The console port is located on the RSP2 to the right of the auxiliary port and is labeled Console, as shown in Figure 3.
Before connecting the console port, check your terminal documentation to determine the baud rate of the terminal you will be using. The baud rate of the terminal must match the default baud rate (9600 baud). Set up the terminal as follows: 9600 baud, 8 data bits, no parity, and 2 stop bits (9600,8N2).
Use the console cable provided to connect the terminal to the console port on the RSP2, and then follow the steps in the "Restarting the System" section.
The auxiliary port on the RSP2 is a DB-25 plug DTE port for connecting a modem or other DCE device (such as a CSU/DSU or other router) to the router. The port is located above the console port on the RSP2 and is labeled Auxiliary. An example of a modem connection is shown in Figure 3.
For systems with two RSP2s installed (one as master and one as slave, and you are using the HSA feature), you can simultaneously connect to both console or auxiliary ports using a special Y-cable. If only one RSP2 is installed, it is automatically the system master. Figure 4 shows the console Y-cable and Figure 5 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 "System Startup Sequence" section.)
Use the following procedure to verify that the RSP2 is installed and functioning properly:
Step 1 Check the RSP2 connections to make sure they are secure:
Step 2 Observe the RSP2 LEDs. As the RSP2 initializes each interface processor, the status LEDs on each interface processor go on and off in irregular sequence.
Step 3 For a Cisco 7507 or Cisco 7513 with HSA configured, verify that the console terminal displays the system banner and startup screen as the system restarts. The master console display should look similar to the following for a Cisco 7513 (note the RSP2 slots indicated):
System Bootstrap, Version 11.1(2), RELEASED SOFTWARE Copyright (c) 1986-1996 by cisco Systems, Inc. SLOT 6 RSP2 is system master SLOT 7 RSP2 is system slave RSP2 processor with 16384 Kbytes of main memory [additional displayed text omitted from this example] Cisco Internetwork Operating System Software IOS (tm) GS Software (RSP-JV), Version 11.1(4) [biff 51096] Copyright (c) 1986-1996 by cisco Systems, Inc. Compiled Mon 22-Jan-96 21:15 by biff Image text-base: 0x600108A0, data-base: 0x607B8000 cisco RSP2 (R4600) processor with 16384K bytes of memory. R4600 processor, Implementation 32, Revision 2.0 [additional displayed text omitted from this example] 8192K bytes of Flash PCMCIA card at slot 0 (Sector size 128K). 8192K bytes of Flash internal SIMM (Sector size 256K). Slave in slot 7 is halted. [additional displayed text omitted from this example]
The master console display should look similar to the following for a Cisco 7507 (note the RSP2 slots indicated):
System Bootstrap, Version 11.1(2), RELEASED SOFTWARE Copyright (c) 1986-1996 by cisco Systems, Inc. SLOT 2 RSP2 is system master SLOT 3 RSP2 is system slave RSP2 processor with 16384 Kbytes of main memory [additional displayed text omitted from this example] Cisco Internetwork Operating System Software IOS (tm) GS Software (RSP-JV), Version 11.1(4) [biff 51096] Copyright (c) 1986-1996 by cisco Systems, Inc. Compiled Mon 22-Jan-96 21:15 by biff Image text-base: 0x600108A0, data-base: 0x607B8000 cisco RSP2 (R4600) processor with 16384K bytes of memory. R4600 processor, Implementation 32, Revision 2.0 [additional displayed text omitted from this example] 8192K bytes of Flash PCMCIA card at slot 0 (Sector size 128K). 8192K bytes of Flash internal SIMM (Sector size 256K). Slave in slot 3 is halted. [additional displayed text omitted from this example]
Step 4 For a Cisco 7507 or Cisco 7513 with a single RSP2 (non-HSA), verify that the console terminal displays the system banner and startup screen as the system restarts. The display should look similar to the following:
System Bootstrap, Version 11.1(2) [biff 51096], RELEASED SOFTWARE Copyright (c) 1994-1996 by cisco Systems, Inc. SLOT 6 RSP2 is system master RSP2 processor with 16384 Kbytes of main memory [additional displayed text omitted from this example] Cisco Internetwork Operating System Software IOS (tm) GS Software (RSP-JV), Version 11.1(4) [biff 51096] Copyright (c) 1986-1996 by cisco Systems, Inc. Compiled Mon 22-Jan-96 21:15 by biff Image text-base: 0x600108A0, data-base: 0x607B8000 cisco RSP2 (R4600) processor with 16384K bytes of memory. R4600 processor, Implementation 32, Revision 2.0 [additional displayed text omitted from this example]
Step 5 After the system boots the software and initializes the interface processors (approximately 30 seconds for systems with 16 MB of DRAM, and approximately 2 minutes for systems with 64 MB of DRAM), verify that the RSP2 LEDs are in the following states:
Step 6 Verify that all the enabled LEDs (on the interface processors) are on.
Step 7 In systems with a second RSP2 installed, use the show version command to verify that the slave RSP2 is recognized by the system. Following is a sample from a Cisco 7513:
Router> show version Cisco Internetwork Operating System Software IOS (tm) GS Software (RSP-JV), Version 11.1(4) [biff 51096] Copyright (c) 1986-1996 by cisco Systems, Inc. Compiled Mon 22-Jan-96 21:15 by biff Image text-base: 0x600108A0, data-base: 0x607B8000 [additional displayed text omitted from this example] Slave in slot 7 is running Cisco Internetwork Operating System Software (Note that this could also be "slot 6" depending on which RSP2 is configured as the slave or the recent crash history of your router.) IOS (tm) GS Software (RSP-JV), Version 11.1(4) [biff 51096] Copyright (c) 1986-1996 by cisco Systems, Inc. Compiled Mon 22-Jan-96 20:59 by biff Configuration register is 0xF Router>
When you have verified all the conditions in Steps 2 through Step 6 (or Step 7 if you have a second RSP2 installed and want to use the HSA feature), the installation is complete. If you replaced the RSP2 and saved your configuration file to a remote server before doing so, proceed to the "Retrieving the Configuration File" section. If you replaced the RSP2 and did not save the configuration, use the configure command or the setup command facility to reenter the configuration information.
An error condition exists if no LEDs go on at power up or after initialization, or if the CPU halt LED goes on and remains on. If this happens, proceed to the "Troubleshooting the Installation" section to try to isolate the problem.
For more complete configuration information, refer to the Configuration Fundamentals Configuration Guide and the Configuration Fundamentals Command Reference publications, which are available on the Documentation CD-ROM or as printed copies.
If you have a second RSP2 installed, you must configure the HSA feature for your Cisco 7507 or Cisco 7513 router. Read the following caution, and then proceed to the following section, "Configuring High System Availability Operation."
| Caution When you install a second RSP2 card for the first time, you must immediately configure it correctly. This ensures that the new slave is configured consistently with the master. Failure to do so may result in an unconfigured slave RSP2 card taking over the router when the master fails, rendering the network inoperable. |
High system availability (HSA) (available with Cisco IOS Release 11.1[4] or a later release of 11.1) refers to how quickly your router returns to an operational status after a failure occurs.
On the Cisco 7507 and Cisco 7513, you can install two RSP2 cards in a single router to improve system availability.
Two RSP2 cards in a router provide the most basic level of increased system availability through a "cold restart" feature. A "cold restart" means that when one RSP2 card fails, the other RSP2 card reboots the router. In this way, your router is never in a failed state for very long, thereby increasing system availability.
When one RSP2 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 RSP2 card fails and the other takes over:
A router configured for HSA operation has one RSP2 card that is the master and one that is the slave. The master RSP2 card functions as if it were a single processor, controlling all functions of the router. The slave RSP2 card does nothing but actively monitor the master for failure. A system crash can cause the master RSP2 to fail or go into a nonfunctional state. When the slave RSP2 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 RSP2 card is the master and which is the slave upon startup (or reboot).
If a system crash causes the master RSP2 to fail, the slave RSP2 becomes the new master RSP2 and uses its own system image and configuration file to reboot the router. The failed RSP2 card (now the slave) remains inactive until you perform diagnostics, correct the problem, and then issue the slave reload command.
| Caution To ensure that the slave RSP2 will operate properly with the full system configuration should the master RSP2 ever fail, the slave RSP2 should have the same ROM monitor version and the same DRAM configuration as the master RSP2. |
With HSA operation, the following items are important to note:
| Caution Removing the system master RSP2 while the system is operating will cause the system to crash; however, the system will reload with the slave RSP2 as the new system master. To prevent any system problems, do not remove the system master RSP2 while the system is operating. |
Two common ways to use HSA:
You can also use HSA for advanced implementations. For example, you can configure the RSP2 cards with the following:
To ensure that the high system availability (HSA) feature operates properly, observe the following prerequisites:
When configuring HSA operation, complete the tasks in the following sections. The first is required. Depending on the outcome of the first, the second or third is also required. The fourth and fifth 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 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 RSP2 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 RSP2's perspective, you define a default slave RSP2. The router uses the default slave information when booting:
To define the default slave RSP2, perform the following steps, beginning in global configuration mode:
| Step | Command | Purpose | ||
| configure terminal | Enter the configuration mode from the terminal. | ||
| Define the default slave RSP2. | |||
| Ctrl-Z | Exit configuration mode. | ||
| copy running-config startup-config | Save this information to your startup configuration. |
Upon the next system reboot, the above changes take effect (if both RSP2 cards are operational). Thus, the specified default slave becomes the slave RSP2 card. The other RSP2 card takes over the system and controls all functions of the router.
If you do not specifically define the default slave RSP2, the RSP2 card located in the higher-number processor slot is the default slave. On the Cisco 7507, processor slot 3 contains the default slave RSP2. On the Cisco 7513, processor slot 7 contains the default slave RSP2.
The following example sets the default slave RSP2 to processor slot 2 on a Cisco 7507:
Router# configure terminal Router (config)# slave default-slot 2 Ctrl-Z Router# copy running-config startup-config
To ensure that both RSP2 cards have the same system image, perform the following steps in EXEC mode:
The following example ensures that both RSP2 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 RSP2.
Router# show boot BOOT variable = CONFIG_FILE variable = Current CONFIG_FILE variable = BOOTLDR variable does not exist Configuration register is 0x0 Slave auto-sync config mode is on current slave is in slot 7 BOOT variable = CONFIG_FILE variable = BOOTLDR variable does not exist Configuration register is 0x0 Router# dir slot0: -#- -length- -----date/time------ name 1 3482498 May 4 1993 21:38:04 rsp-jv-mz11.2 7993896 bytes available (1496 bytes used) Router# dir slaveslot0: -#- -length- -----date/time------ name 1 3482498 May 4 1993 21:38:04 rsp-jv-mz11.1 7993896 bytes available (1496 bytes used) Router# delete slaveslot0:rsp-jv-mz11.1 Router# copy slot0:rsp-jv-mz11.2 slaveslot0:rsp-jv-mz11.2
To ensure that both RSP2 cards have the same microcode images, perform the following steps beginning in privileged EXEC mode:
| Step | Command | Purpose | ||
| 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 [/all | /deleted] [/long] {bootflash | slot0 | slot1} [filename] | If any interface processors are running from the flash file system, verify the location and version of the master RSP2's supplementary microcode. | ||
| dir [/all | /deleted] [/long] {slavebootflash | slaveslot0 | slaveslot1} [filename] | Determine if the slave RSP2 contains the same microcode image in the same location. | ||
| copy file_id {slavebootflash | slaveslot0 | slaveslot1} Note that you might also have to use the delete and/or squeeze command in conjunction with the copy command to accomplish this step. | If the slave RSP2 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 RSP2 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." Slot 11, the FSIP processor, does not use the microcode bundled with the system. Instead, it loads the microcode from slot0:pond/bath/rsp_fsip20-1. Thus, you must ensure that the slave RSP2 has a copy of the same FSIP microcode in the same location.
Router# show controllers cbus
MEMD at 40000000, 2097152 bytes (unused 416, recarves 3, lost 0)
RawQ 48000100, ReturnQ 48000108, EventQ 48000110
BufhdrQ 48000128 (2948 items), LovltrQ 48000140 (5 items, 1632 bytes)
IpcbufQ 48000148 (16 items, 4096 bytes)
3571 buffer headers (48002000 - 4800FF20)
pool0: 28 buffers, 256 bytes, queue 48000130
pool1: 237 buffers, 1536 bytes, queue 48000138
pool2: 333 buffers, 4544 bytes, queue 48000150
pool3: 4 buffers, 4576 bytes, queue 48000158
slot0: EIP, hw 1.5, sw 20.00, ccb 5800FF30, cmdq 48000080, vps 4096
software loaded from system
Ethernet0/0, addr 0000.0ca3.cc00 (bia 0000.0ca3.cc00)
gfreeq 48000138, lfreeq 48000160 (1536 bytes), throttled 0
rxlo 4, rxhi 42, rxcurr 0, maxrxcurr 2
txq 48000168, txacc 48000082 (value 27), txlimit 27
.........
slot1: FIP, hw 2.9, sw 20.02, ccb 5800FF40, cmdq 48000088, vps 4096
software loaded from system
Fddi1/0, addr 0000.0ca3.cc20 (bia 0000.0ca3.cc20)
gfreeq 48000150, lfreeq 480001C0 (4544 bytes), throttled 0
rxlo 4, rxhi 165, rxcurr 0, maxrxcurr 0
txq 480001C8, txacc 480000B2 (value 0), txlimit 95
slot4: AIP, hw 1.3, sw 20.02, ccb 5800FF70, cmdq 480000A0, vps 8192
software loaded from system
ATM4/0, applique is SONET (155Mbps)
gfreeq 48000150, lfreeq 480001D0 (4544 bytes), throttled 0
rxlo 4, rxhi 165, rxcurr 0, maxrxcurr 0
txq 480001D8, txacc 480000BA (value 0), txlimit 95
slot9: MIP, hw 1.0, sw 20.02, ccb 5800FFC0, cmdq 480000C8, vps 8192
software loaded from system
T1 9/0, applique is Channelized T1
gfreeq 48000138, lfreeq 480001E0 (1536 bytes), throttled 0
rxlo 4, rxhi 42, rxcurr 0, maxrxcurr 0
txq 480001E8, txacc 480000C2 (value 27), txlimit 27
.......
slot10: TRIP, hw 1.1, sw 20.00, ccb 5800FFD0, cmdq 480000D0, vps 4096
software loaded from system
TokenRing10/0, addr 0000.0ca3.cd40 (bia 0000.0ca3.cd40)
gfreeq 48000150, lfreeq 48000200 (4544 bytes), throttled 0
rxlo 4, rxhi 165, rxcurr 1, maxrxcurr 1
txq 48000208, txacc 480000D2 (value 95), txlimit 95
.........
slot11: FSIP, hw 1.1, sw 20.01, ccb 5800FFE0, cmdq 480000D8, vps 8192
software loaded from flash slot0:pond/bath/rsp_fsip20-1
Serial11/0, applique is Universal (cable unattached)
gfreeq 48000138, lfreeq 48000240 (1536 bytes), throttled 0
rxlo 4, rxhi 42, rxcurr 0, maxrxcurr 0
txq 48000248, txacc 480000F2 (value 5), txlimit 27
...........
Router# dir slot0:pond/bath/rsp_fsip20-1
-#- -length- -----date/time------ name
3 10242 Jan 01 1995 03:46:31 pond/bath/rsp_fsip20-1
Router# dir slaveslot0:pond/bath/rsp_fsip20-1
No such file
4079832 bytes available (3915560 bytes used)
Router# copy slot0:pond/bath/rsp_fsip20-1 slaveslot0:
4079704 bytes available on device slaveslot0, proceed? [confirm]
Router# dir slaveslot0:pond/bath/rsp_fsip20-1
-#- -length- -----date/time------ name
3 10242 Mar 01 1993 02:35:04 pond/bath/rsp_fsip20-1
4069460 bytes available (3925932 bytes used)
Router#
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 startup configuration when you issue a copy command that specifies the master startup configuration (startup-config) as the target.
Automatic synchronization mode is on by default; however, to turn it on manually, perform the following steps, beginning 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 running-config 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 running-config startup-config
With the software error protection method, you configure the RSP2 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 Cisco 7507 or Cisco 7513 with two RSPs, you receive the same system image on both RSP2 cards. For the software error protection method, you need two different software images on the RSP2 cards. Thus, you copy a desired image to the master RSP2 card and modify the boot system commands to reflect booting two different system images. Each RSP2 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 RSP2, perform the following steps, beginning in EXEC mode:
| Step | Command | Purpose | ||
| dir [/all | /deleted] [/long] {bootflash | slot0 | slot1} [filename] | Verify the location and version of the master RSP2 software image. | ||
| dir [/all | /deleted] [/long] {slavebootflash | slaveslot0 | slaveslot1} [filename] | Determine if the slave RSP2 contains the same software image in the same location. | ||
| copy file_id {bootflash | slot0 | slot1} copy flash {bootflash | slot0 | slot1} | Copy a different system image to the master RSP2. | ||
| configure terminal | Enter configuration mode from the terminal. | ||
| boot system flash bootflash:[filename] | From global configuration mode, configure the master RSP2 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 RSP2 and boots the system. Note that because the slave will boot this image when the slave is actually the new master RSP2, the command syntax does not use a "slave" prefix. | ||
| Configure the master RSP2 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 running-config 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 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 6 illustrates the software error protection configuration for this sample scenario. The configuration commands for this configuration follow the figure.
Because you always view the environment from the master RSP2's perspective, in the following command you view the master slot 0 to verify the location and version of the master software image:
Router# dir slot0: -#- -length- -----date/time------ name 1 3482496 May 4 1993 21:38:04 rsp-jv-mz11.1 7993896 bytes available (1496 bytes used)
Now view the slave software image location and version:
Router# dir slaveslot0: -#- -length- -----date/time------ name 1 3482496 May 4 1993 21:38:04 rsp-jv-mz11.1 7993896 bytes available (1496 bytes used)
Because you want to run the Release 11.2 system image on one RSP2 card and the Release 11.1 system image on the other RSP2 card, copy the Release 11.2 system image to the master slot 0:
Router# copy tftp slot0:rsp-jv-mz11.2
Enter global configuration mode and configure the system to boot first from a Release 11.2 system image and then from a Release 11.1 system image.
Router# configure terminal Router (config)# boot system flash slot0:rsp-jv-mz11.1.2 Router (config)# boot system flash slot0:rsp-jv-mz11.1
With this configuration, when the slot 6 RSP2 card is master, it looks first in its PC Card slot 0 for the system image file rsp-jv-mz11.2 to boot. Finding this file, the router boots from that system image. When the slot 7 RSP2 card is master, it also looks first in its slot 0 for the system image file rsp-jv-mz11.2 to boot. Because that image does not exist in that location, the slot 7 RSP2 card looks for the system image file rsp-jv-mz11.1 in slot 0 to boot. Finding this file in its PC Card slot 0, the router boots from that system image. In this way, each RSP2 card can reboot the system using its own system image when it becomes the master RSP2 card.
Configure the system further with a fault-tolerant booting strategy:
Router (config)# boot system tftp rsp-jv-mz11.1 192.37.1.25
Set the configuration register to enable loading of the system image from a network server or from Flash memory and save the changes to the master and slave startup configuration file:
Router (config)# config-register 0x010F Router (config)# Ctrl-Z Router# copy running-config startup-config
Reload the system so that the master RSP2 uses the new Release 11.2 system image:
Router# reload
In the following sample scenario, assume the following:
In this scenario, you begin with the configuration shown in Figure 7.
Next, you copy the rsp-jv-mz11.1 image to the master and the slave RSP2 card, as shown in Figure 8.
Last, delete the rsp-jv-mz11.2 image from the slave RSP2 card, as shown in Figure 9:
The following commands configure software error protection for this sample scenario.
View the master and the slave slot 0 to verify the location and version of their software images:
Router# dir slot0: -#- -length- -----date/time------ name 1 3482498 May 4 1993 21:38:04 rsp-jv-mz11.2 7993896 bytes available (1496 bytes used) Router# dir slaveslot0: -#- -length- -----date/time------ name 1 3482498 May 4 1993 21:38:04 rsp-jv-mz11.2 7993896 bytes available (1496 bytes used)
Copy the Release 11.1 system image to the master and the slave slot 0:
Router# copy tftp slot0:rsp-jv-mz11.1 Router# copy tftp slaveslot0:rsp-jv-mz11.1
Delete the rsp-jv-mz11.2 image from the slave RSP2 card:
Router# delete slaveslot0:rsp-jv-mz11.2
Configure the system to boot first from a Release 11.2 system image and then from a Release 11.1 system image.
Router# configure terminal Router (config)# boot system flash slot0:rsp-jv-mz11.2 Router (config)# boot system flash slot0:rsp-jv-mz11.1
Configure the system further with a fault-tolerant booting strategy:
Router(config)# boot system tftp rsp-jv-mz11.1 192.37.1.25
Set the configuration register to enable loading of the system image from a network server or from Flash memory and save the changes to the master and slave startup configuration file:
Router(config)# config-register 0x010F Crtl-z Router# copy running-config startup-config
You can optionally set environment variables on both RSP2 cards in a Cisco 7507 and a Cisco 7513.
You set environment variables on the master RSP2 just as you would if it were the only RSP2 card in the system. You can set the same environment variables on the slave RSP2 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 RSP2 card using the slave sync config command.
To set environment variables manually on the slave RSP2, perform the following steps beginning in global configuration mode:
| Step | Command | Purpose | ||
| boot system boot bootldr boot config | Set the master RSP2 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 running-config startup-config | Save the settings to the startup configuration. This also puts the information under that RSP2 card's ROM monitor control. | ||
| Save the same environment variables to the slave RSP2 by manually synchronizing their configuration files. | |||
| show boot | Verify the environment variable settings. |
With automatic synchronization turned on, the system automatically saves the same environment variables to the slave's startup configuration when you set the master's environment variables and save them.
To set environment variables on the slave RSP2 when automatic synchronization is on, perform the following steps beginning in global configuration mode:
| Step | Command | Purpose | ||
| boot system boot bootldr boot config | Set the master RSP2 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 running-config startup-config | Save the settings to the startup configuration. This also puts the information under that RSP2 card's ROM monitor control. | ||
| show boot | 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, enter the following command in global configuration mode to specify which image the slave should run:
slave image {system | device:filename}
slave sync config
| Caution When you install a second RSP2 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 may result in an unconfigured slave RSP2 card taking over mastership 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 the 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 RSP2(s) 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 chassis, 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 hardware installation and configuration publication that shipped with your router. This publication is available on the Documentation CD-ROM or in print.)
Figure 10 shows the LEDs on the RSP2 faceplate. The LEDs on the RSP2 indicate the system and RSP2 status and which Flash memory card slot is active. The CPU halt LED, which goes on only if the system detects a processor hardware failure, should remain off. A successful boot is indicated when the normal LED goes on; however, this does not necessarily mean that the system has reached normal operation. During normal operation, the CPU halt LED should be off, and the normal LED should be on, indicating that the RSP2 is receiving +5V. The slot 0 and slot 1 LEDs indicate which PC Card (Flash memory) card slot is in use, and each LED blinks when the card is accessed by the system.
If you did not install a new boot ROM device correctly, the corresponding RSP2 is placed in a "nonparticipant" mode and both of its slave and master LEDs will be on. This can be caused by a bent boot ROM pin, a misaligned boot ROM, or a misprogrammed boot ROM. If this condition occurs, power down the system and verify that the boot ROM device is properly installed. If the boot ROM device was installed backwards, severe damage may have resulted, rendering the boot ROM device unusable. You will have to install a new boot ROM device.
| Caution The reset switch (see Figure 10) resets the RSP2 and the entire system. To prevent system errors and problems, use it only at the direction of your 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 can isolate the problem to a faulty hardware component, or if you cannot successfully restart the system, see the end of this document for instructions on contacting a service representative.
During the boot sequence, the system banner pauses while it initializes the memory. If your router has more than 16 MB of DRAM, you may notice an increase in the amount of time required to initialize the memory. The pause in the banner occurs after the copyright line, and before the system displays the list of installed hardware, as shown in the following example:
%SYS-5-RELOAD: Reload requested System Bootstrap, Version 11.1(2) Copyright (c) 1986-1996 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:
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 number 2.
2. Listen for the system blower and observe the fan OK LED. You should hear the system blower start operating immediately after you turn on the system power. If you determine that the power supply is functioning normally and that an internal fan (or the system blower) is faulty, contact a service representative. If the blower or a power supply fan does not function properly at initial startup, you cannot make any installation adjustments.
3. When you have verified that the power supply is functioning properly, observe the LEDs on the RSP2. The CPU halt LED on the RSP2 should always remain off. If it goes on during the startup sequence, the system has encountered a processor hardware error.
4. During the boot process, the LEDs on most of the interfaces light in irregular sequence; this does not indicate either correct system startup or failure.
5. When the system boot is complete, the RSP2 begins to initialize the interface processors. During this initialization, the LEDs on each interface processor behave differently (most flash on and off). The enabled LED on each interface processor goes on when initialization has been completed.
6. When the system boot is complete and all interface processors have been initialized, the master RSP2 console screen displays a script and system banner similar to the following:
Cisco Internetwork Operating System Software IOS (tm) GS Software (RSP-JV-M), Version 11.1(4) [biff 51096] Copyright (c) 1986-1996 by cisco Systems, Inc. Compiled Mon 22-Jan-96 21:15 by biff Image text-base: 0x600108A0, data-base: 0x607B8000 ROM: System Bootstrap, Version 11.1(2) [biff 2], RELEASE SOFTWARE (fc1) ROM: GS Bootstrap Software (RSP-BOOT-M), Version 10.3(7), RELEASE SOFTWARE Warning: monitor nvram area is corrupt ... using default values SLOT 2 RSP2 is system master SLOT 3 RSP2 is system slave RSP2 processor with 81920 Kbytes 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 RSP2 installation and replacement procedure. For complete command descriptions and examples, refer to the Configuration Fundamentals Command Reference publication.
When a new master RSP2 takes control of the router, it automatically reboots the failed RSP2 as the slave RSP2. You can access the state of the failed RSP2 in the form of a stack trace from the master console using the show stacks command.
slave reload
| Command | Purpose |
Display the environment variable settings and configuration register settings for both the master and the slave RSP cards. | |
Show a list of Flash memory devices currently supported on the router. | |
Display the software version running on the master and the slave RSP card. | |
show stacks 1 | Display the stack trace and version information of the master and the slave RSP cards. |
| 1This command is documented in the "System Management Commands" chapter of the Configuration Fundamentals Command Reference publication. |
If you have a Cisco 7507 or a Cisco 7513 with an RSP2 configured as the system slave, we strongly recommend that you use the following procedure to remove and replace an interface processor:
Step 1 Remove the slave RSP2.
Step 2 Wait 15 seconds.
Step 3 Remove and replace the interface processor, using the procedures in the configuration note that shipped with your interface processor or in the Cisco 7500 Series Installation and Configuration Guide.
Step 4 Wait 15 seconds.
Step 5 Reinsert the slave RSP2.
The following sections provide reference information for the RSP2:
The console port on the RSP2 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 console port does not support modem control or hardware flow control. The console port requires a straight-through EIA/TIA-232 cable. Table 2 lists the signals used on this port.
| 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 RSP2 is an EIA/TIA-232 DTE, DB-25 plug to which you can attach a CSU, DSU, or other equipment to access the router from the network. The RTS signal tracks the state of the CTS input. The asynchronous auxiliary port supports hardware flow control and modem control. Table 3 lists the EIA/TIA-232 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 RSP2s (configured as system master and slave) to one console terminal or external auxiliary device (such as a modem).
The two cables (Product Numbers CAB-RSP2CON= and CAB-RSP2AUX=) ship with the router and are available as spare parts. The console Y-cable pinouts are listed in Table 4, and the auxiliary Y-cable pinouts are listed in Table 5.
| Female DB-25 Pins | Male3 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 | Female3 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 four SIMMs that you obtain from an approved vendor. The system DRAM resides on up to four SIMMs on the RSP2. The DRAM SIMM sockets are U21 and U33 for bank 0, and U4 and U12 for bank 1. (See Figure 11 and Table 6.) The default DRAM configuration is 32 MB.
The SIMM sockets use thumb tabs that are often used in PCs and other computer equipment. Each RSP2 SIMM socket has two metal retaining springs, one at each end. (See Figure 12 on page 52.) When a SIMM is fully seated in the socket, the retaining springs snap over the ends of the SIMM to lock it in the socket.
Before proceeding, ensure that you have the proper tools and ESD-prevention equipment available. To upgrade DRAM, you install SIMMs in one or two banks. Table 6 lists the various configurations of DRAM SIMMs that are available. Note which banks are used given the combinations of available SIMM sizes and the maximum DRAM you require.
| DRAM Bank 0 | Quantity | DRAM Bank 1 | Quantity | Total DRAM | Product Numbers |
U33 and U21 | 2 8-MB SIMMs and 2 4-MB SIMM | U12 and U4 | 2 4-MB SIMMs | 24 MB | MEM-RSP-24M |
U33 and U21 | 2 16-MB SIMMs | U12 and U4 | - | 32 MB1 | MEM-RSP-32M(=) |
U33 and U21 | 2 32-MB SIMMs | U12 and U4 | - | 64 MB | MEM-RSP-64M(=) |
U33 and U21 | 2 32-MB SIMMs | U12 and U4 | 2 32-MB SIMMs | 128 MB | MEM-RSP-128M(=) |
| 1The 32-MB DRAM configuration is the minimum DRAM requirement for the HSA feature. |
| Caution To prevent DRAM errors, each DRAM bank used must contain no less than two SIMMs of the same type. You must install either two SIMMs in bank 0 or four SIMMs in banks 0 and 1. |
Place removed SIMMs on an antistatic mat and store them in an antistatic bag. You can use the SIMMs that you remove in compatible equipment.
| Caution To prevent ESD damage, handle SIMMs by the card edges only. |
Use the following procedure to remove the existing SIMMs:
Step 1 Turn off the system power and follow the steps in the "Removing the RSP2" section.
Step 2 Place the RSP2 on an antistatic mat or pad, and ensure that you are wearing an antistatic device, such as a wrist strap. Position the RSP2 so that the faceplate is away from you and the edge connector is toward you---the opposite of the position shown in Figure 11 on page 50.
Step 3 Locate the DRAM SIMMs on the RSP2. The SIMMs occupy U33 and U21 in bank 0, and U12 and U4 in bank 1. (See Figure 11.)
Step 4 Release the spring clips from the SIMM you want to remove and release the SIMM from the socket. (See Figure 12.)
Step 5 When both ends of the SIMM are released from the socket, grasp the ends of the SIMM with your thumb and forefinger and pull the SIMM completely out of the socket. Handle the edges of the SIMM only; avoid touching the memory module or pins and the metal traces, or fingers, along the socket edge.
Step 6 Place the SIMM in an antistatic bag to protect it from ESD damage.
Step 7 Repeat Steps 4 through Step 6 for the remaining SIMMs, as required for your upgrade.
This completes the SIMM removal procedure. Proceed to the next section to install the new SIMMs.
Following is the procedure for installing new SIMMs.
| Caution SIMMs are sensitive components that can be shorted by mishandling, and they are susceptible to ESD damage. Handle SIMMs by the edges only; avoid touching the memory modules, pins, or traces (the metal fingers along the connector edge of the SIMM). (See Figure 13.) |
Use the following procedure to install the new SIMMs:
Step 1 Ensure that the RSP2 is in the same orientation as in the previous procedure (with the handle away from you and the edge connector toward you).
Step 2 Remove a new SIMM from the antistatic bag.
Step 3 Hold the SIMM component-side-up, with the connector edge (the metal fingers) closest to you. Hold the sides of the SIMM between your thumb and middle finger, with your forefinger against the far edge, opposite the connector edge. (See Figure 13.)
Step 4 Tilt the SIMM to approximately the same angle as the socket and insert the entire connector edge into the socket. (Install the first SIMM in the slot farthest away from you. Install the last SIMM in the slot closest to you.)
| Caution When inserting SIMMs, use firm but not excessive pressure. If you damage a socket, you will have to return the RSP2 to the factory for repair. |
Step 5 Gently push the SIMM into the socket until the spring clips snap over the ends of the SIMM. If necessary, rock the SIMM gently back and forth to seat it properly.
Step 6 Repeat Steps 2 through Step 5 for the remaining SIMMs.
Step 7 When all SIMMs are installed, check all alignment holes (two on each SIMM) to ensure that the spring retainer is visible. If it is not, the SIMM is not seated properly. If any SIMM appears misaligned, carefully remove it and reseat it in the socket. Push the SIMM firmly back into the socket until the retainer springs snap into place.
If the system fails to boot properly, or if the console terminal displays a checksum or memory error, check the following:
If after several attempts the system fails to restart properly, contact a service representative for assistance. Before you call, make note of any error messages, unusual LED states, or any other indications that might help solve the problem.
This completes the SIMM replacement procedure.
To replace the RSP2 in the router, proceed to the "Replacing the RSP2" section, and then restart the system for an installation check.
Settings for the 16-bit software configuration register are written into NVRAM. Following are some reasons for changing the software configuration register settings:
Table 7 lists the meaning of each of the software configuration memory bits, and Table 8 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 7. For example, the factory default value of 0x0101 is a combination of settings. |
| Bit Number1 | Hexadecimal | Meaning |
|---|---|---|
00 to 03 | 0x0000 to 0x000F | Boot field (see Table 8) |
06 | 0x0040 | Causes system software to ignore NVRAM contents |
07 | 0x0080 | OEM bit enabled2 |
08 | 0x0100 | Break function disabled |
09 | 0x0200 | Use secondary bootstrap |
10 | 0x0400 | IP broadcast with all zeros |
11 to 12 | 0x0800 to 0x1000 | Console line speed (default is 9600 baud) |
13 | 0x2000 | Boot default Flash 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 8). 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 |
Use the following procedure to change the configuration register while running the system software:
Step 1 Enter the enable command and your password to enter the privileged level, as follows:
Router> enable Password: router#
Step 2 At the privileged-level system prompt (router #), enter the configure terminal command. You are prompted, as shown in the following example:
Router# conf t Enter configuration commands, one per line. End with CNTL/Z. Router(config)#
Step 3 To set the contents of the configuration register, enter the config-register value configuration command, where value is a hexadecimal number preceded by 0x
(see Table 7), as in the following example:
Router(config)# config-register 0xvalue
Step 4 Exit the configuration mode by entering Ctrl-Z. The new value settings will be 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 server restarts, such as when you switch the power off and on or 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 8.) 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:
For more information about the b [tftp] flash [filename] command, refer to the set of configuration fundamentals publications.
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 you set the boot field to any other bit pattern, the router uses the resulting number to form a default boot filename for booting from a network server. (See Table 9.)
Router# configure term Enter configuration commands, one per line. End with CNTL/Z. Router(config)# config-register 0x102 Router(config)# boot system flash filename Crtl-z Router#
The server creates a default boot filename as part of the automatic configuration processes. To form the boot filename, the server starts with the name cisco and adds the octal equivalent of the boot field number, a hyphen, and the processor-type name. Table 9 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. A break can be sent in the first 60 seconds while the system reboots, regardless of the configuration settings.
Bit 9 controls the secondary bootstrap program function. Setting bit 9 causes the system to use the secondary bootstrap; clearing bit 9 causes the system to ignore the secondary bootstrap. The secondary bootstrap program is used for system debugging and diagnostics.
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 10 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 11 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:, slot0:, or slot1:, and filename is the name of the file from which you want to boot the system.
To enter configuration mode while in the system software image and specify a Flash memory filename from which to boot, enter the configure terminal command at the enable prompt, as follows:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# boot system flash device:filename
To disable the Break function and enable the boot system flash device:filename command, enter the config-register command with the value shown in the following example:
Router(config)# config-reg 0x0102 Crtl-Z Router#
An overview of recovering a lost password follows:
Use the following procedure to recover a lost password:
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 five 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 60 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 startup-config 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 (the factory default).
Step 14 Exit the configuration mode by entering Ctrl-Z.
Step 15 Reboot the router and enable it using the recovered password.
This completes the procedure for recovering from a lost password.
The Flash memory (PC Card) slots on the front panel of the RSP2 support additional 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.
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 Jan 25 20:21:28 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.