|
|
Product Numbers:
RSP4=
CISCO7505/4(=)
CISCO7507/4(=)
CISCO7513/4(=)
CISCO7507/4x2(=)
CISCO7513/4x2(=)
MEM-RSP4-32M=1
MEM-RSP4-64M=
MEM-RSP4-128M=
MEM-RSP4-256MB=
This configuration note discusses the next-generation Route Switch Processor (RSP4), which is an optional, new main system processor available for the Cisco 7500 series routers: Cisco 7505, Cisco 7507, and Cisco 7513. The RSP4 combines all of the switched routing and high-speed switching functions required by the Cisco 7500 series. (For more information, refer to the section "What Is the RSP4?, page 3.)
In addition, the RSP4 supports the high system availability (HSA) feature, which is a new feature, and which allows two RSP4s to be used simultaneously in a Cisco 7507 or Cisco 7513 router with the HSA feature enabled and configured. (To determine which Cisco IOS software release your router is running, refer to the section "System Software Requirements" on page 12.)
With the HSA feature, one RSP4 operates as system master and the other RSP4 operates as the system slave, which takes over if the master RSP4 fails. An RSP4 and an RSP2 can also be used simultaneously with the HSA feature. (Refer to the section "Hardware Requirements" on page 13.)
Following are the sections in this document:
The Cisco IOS software running your router contains extensive features and functionality. The effective use of many of many of these features is easier if you have more information at hand. For additional information on configuring and maintaining the router and the RSP4, the following documentation resources are available to you:
The RSP4 is the newest main system processor module for the Cisco 7500 series routers. (See Figure 1.)
The RSP4 is available as follows:
The RSP4 contains the following components:
In addition to running the system software from DRAM, the RSP4 contains and executes the following management functions that control the system:
The high-speed switching section of the RSP4 communicates with and controls the interface processors on the high-speed CyBus. This switching section of the RSP4 decides the destination of a packet and switches it based on that decision.
The RSP4 combines all of the switched routing and high-speed switching functions. The RSP4 supports the HSA feature, which allows two RSP4s to be used in a Cisco 7507 or Cisco 7513 router. By default, the system master is the RSP4 that occupies the first RSP slot in the router: slot 2 in the Cisco 7507, and slot 6 in the Cisco 7513.
The Cisco 7507 and Cisco 7513 routers support downloadable system software and microcode for most Cisco IOS and microcode upgrades, which enables you to remotely download, store, and boot from a new image. The publication Upgrading Software and Microcode in Cisco 7000 Series and Cisco 7500 Series Routers (Document Number 78-1144-xx), which accompanies all Cisco IOS upgrade kits, provides instructions for upgrading over the network or from floppy disks. Flash memory contains the default system software image and bundled microcode images. Both PCMCIA-based and SIMM-based Flash memory is supported.
At system startup, an internal system utility scans for compatibility problems between the installed interface processor types and the bundled microcode images, then decompresses the images into running dynamic random-access memory (DRAM). The bundled microcode images then function the same as the EPROM images.
The Cisco IOS software images reside in Flash memory, which is located either on the RSP4, in the form of a single in-line memory module (SIMM), or on up to two Personal Computer Memory Card International Association (PCMCIA) cards (called Flash memory cards) that insert in the two PCMCIA slots (slot 0 and slot 1) on the front of the RSP4. (See Figure 1 or Figure 2.) Storing the Cisco IOS images in Flash memory enables you to download and boot from upgraded Cisco IOS images remotely or from software images resident in the RSP4 Flash memory.
While no monitoring of +/-12V or temperature is done by the RSP4, a comparator device ensures that +/-12V are within the normal operating ranges, and three temperature sensors on the RSP4 send temperature information to the chassis interface (CI) card. The CI card reports all voltage and temperature readings, and these readings are available via standard software commands for environmental monitoring. The RSP4 uses a software-controlled configuration register, so you do not have to remove the RSP4 to configure jumpers. There are no user-configurable jumpers on the RSP4.
Figure 2 shows the various types of memory components on the RSP4, and Table 1 lists the functions of each type.
| Type | Size | Quantity | Description | Location |
|---|---|---|---|---|
| DRAM | 321 to 256 MB DIMMs | 1 or 2 | 32-, 64-, or 128-MB DIMMs (based on DRAM required) for main Cisco IOS image functions. | U10 or U10 and U13 |
| SRAM2 | 2 MB (fixed) | - | SRAM for packet buffering functions (MEMD) | - |
| 512 KB (fixed) | - | SRAM for secondary CPU cache memory functions | - | |
| NVRAM | 128 KB | 1 | Nonvolatile SRAM for the system configuration file.3 | - |
| Flash Memory | 8-MB SIMM | 1 | Contains the Cisco IOS images on the RSP4. | U1 |
| 164 and 20 MB | Up to 2 | Contains the Cisco IOS images on up to two PCMCIA-based Flash memory cards.5 | Slot 0 and slot 1 | |
| Flash boot ROM | 256 KB | 1 | Flash EPROM for the ROM monitor program image.6 | U5 |
DRAM stores routing tables, protocols, and network accounting applications, and runs the Cisco IOS software. The standard (default) RSP4 configuration is 32 megabytes (MB) of DRAM, with up to 256 MB available through DIMM upgrades. DRAM is contained in up to two DIMM sockets: U10 (also called bank 0) and U13 (also called bank1). When upgrading DRAM, you must use DIMMs from an approved vendor. (Also see the section "Compatibility Requirements, page 11.)
 | Caution To prevent memory problems, DRAM DIMMS must be 3.3--volt (V) devices. Do not attempt to install higher-voltage devices (such as those designed for the RSP2) in the RSP4's DIMM sockets. |
SRAM provides packet buffering and CPU cache memory functions. The standard RSP4 configuration is 2 MB of DRAM for packet buffering, and 512 kilobytes (KB) of secondary CPU cache memory.
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 five years. When replacing an RSP4, be sure to back up your configuration to a remote server so you can retrieve it later.
| Caution Before you replace an RSP4 in a system with one RSP4, back up the running configuration to a Trivial File Transfer Protocol (TFTP) file server or to Flash memory so you can retrieve it later. If the configuration is not saved, the entire configuration will be lost--inside the NVRAM on the removed RSP4--and you will have to reenter the entire configuration manually. For instructions on how to save the configuration file, refer to the section "Saving and Retrieving the Configuration File, page 14. This procedure is not necessary if you are temporarily removing an RSP4; lithium batteries retain the configuration in memory until you replace the RSP4 in the system. |
Both the onboard 8-MB Flash memory and the 16- or 20-MB PCMCIA-card-based Flash memory allow you to remotely load and store multiple Cisco IOS software and microcode images. (The 16-MB Flash memory card is the default Flash memory card that ships with the RSP4.) You can download a new image over the network or from a local server and then add the new image to Flash memory or replace the existing files. You can then boot routers either manually or automatically from any of the images stored in Flash memory. Flash memory also functions as a TFTP server to allow other servers to boot remotely from stored images or to copy them into their own Flash memory.
| Caution To prevent system problems, use Flash memory cards in the RSP4 that were formatted on an RP, RSP1, RSP2, RSP7000, or RSP4 running Cisco IOS Release 11.1(8)CA1 or later. You cannot use Flash memory cards on the RSP4 (as storage or boot devices) that were formatted on an RP, RSP1, RSP2, or RSP7000 using a Cisco IOS boot image earlier than Cisco IOS Release 11.1(8)CA1. |
There are no user-configurable jumpers on the RSP4.
Several LEDs on the RSP4 indicate the system and RSP4 status. The normal LED is on when the system is operational and indicates that the RSP4 is receiving +5V. During normal operation, the CPU halt LED should be off. The CPU halt LED goes on only if the system detects a processor hardware failure. The RSP4 controls the normal and CPU halt LEDs and turns them on in parallel to indicate that the system is operational.
The master/slave LEDs indicate whether an RSP4 is the master or slave in a system configured for the high system availability (HSA) feature. The slot 0 and slot 1 PCMCIA LEDs are on when a PCMCIA card is being accessed while inserted in the respective PCMCIA slot.
The RSP4 has two PCMCIA slots available. Either slot can support a Flash memory card or an input/output (I/O) device. Type 1, Type 2, and Type 3 PCMCIA cards can be used in PCMCIA slot 1, and Type 1 and Type 2 PCMCIA cards can be used in slot 0. Not all Flash memory cards that are commercially available are supported, and not all I/O devices are supported.
Other Flash memory card limitations might apply; refer to the sections "Flash Memory," on page 7, and "Hardware Requirements" on page 13.
Two asynchronous serial ports on the RSP4, labeled Console and Auxiliary, allow you to connect external terminal devices to monitor and manage the system. The console port is an Electronics Industries Association/Telecommunications Industry Association (EIA/TIA)-232 receptacle (female) that provides a data circuit-terminating equipment (DCE) interface for connecting a console terminal.
The auxiliary port is an EIA/TIA-232 plug (male) that provides a data terminal equipment (DTE) interface; the auxiliary port supports flow control and is often used to connect a modem, a channel service unit (CSU), or other optional equipment for Telnet management.
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, may harm you. A warning symbol precedes each warning statement.
Warning 
Means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. To see translations of the warnings that appear in this publication, refer to the Regulatory Compliance and Safety Information document that accompanied this device.
Waarschuwing Dit waarschuwingssymbool betekent gevaar. U verkeert in een situatie die lichamelijk letsel kan veroorzaken. Voordat u aan enige apparatuur gaat werken, dient u zich bewust te zijn van de bij elektrische schakelingen betrokken risico's en dient u op de hoogte te zijn van standaard maatregelen om ongelukken te voorkomen. Voor vertalingen van de waarschuwingen die in deze publicatie verschijnen, kunt u het document Regulatory Compliance and Safety Information (Informatie over naleving van veiligheids- en andere voorschriften) raadplegen dat bij dit toestel is ingesloten.
Varoitus Tämä varoitusmerkki merkitsee vaaraa. Olet tilanteessa, joka voi johtaa ruumiinvammaan. Ennen kuin työskentelet minkään laitteiston parissa, ota selvää sähkökytkentöihin liittyvistä vaaroista ja tavanomaisista onnettomuuksien ehkäisykeinoista. Tässä julkaisussa esiintyvien varoitusten käännökset löydät laitteen mukana olevasta Regulatory Compliance and Safety Information -kirjasesta (määräysten noudattaminen ja tietoa turvallisuudesta).
Attention Ce symbole d'avertissement indique un danger. Vous vous trouvez dans une situation pouvant causer des blessures ou des dommages corporels. Avant de travailler sur un équipement, soyez conscient des dangers posés par les circuits électriques et familiarisez-vous avec les procédures couramment utilisées pour éviter les accidents. Pour prendre connaissance des traductions d'avertissements figurant dans cette publication, consultez le document Regulatory Compliance and Safety Information (Conformité aux règlements et consignes de sécurité) qui accompagne cet appareil.
Warnung Dieses Warnsymbol bedeutet Gefahr. Sie befinden sich in einer Situation, die zu einer Körperverletzung führen könnte. Bevor Sie mit der Arbeit an irgendeinem Gerät beginnen, seien Sie sich der mit elektrischen Stromkreisen verbundenen Gefahren und der Standardpraktiken zur Vermeidung von Unfällen bewußt. Übersetzungen der in dieser Veröffentlichung enthaltenen Warnhinweise finden Sie im Dokument Regulatory Compliance and Safety Information (Informationen zu behördlichen Vorschriften und Sicherheit), das zusammen mit diesem Gerät geliefert wurde.
Avvertenza Questo simbolo di avvertenza indica un pericolo. La situazione potrebbe causare infortuni alle persone. Prima di lavorare su qualsiasi apparecchiatura, occorre conoscere i pericoli relativi ai circuiti elettrici ed essere al corrente delle pratiche standard per la prevenzione di incidenti. La traduzione delle avvertenze riportate in questa pubblicazione si trova nel documento Regulatory Compliance and Safety Information (Conformità alle norme e informazioni sulla sicurezza) che accompagna questo dispositivo.
Advarsel Dette varselsymbolet betyr fare. Du befinner deg i en situasjon som kan føre til personskade. Før du utfører arbeid på utstyr, må du vare oppmerksom på de faremomentene som elektriske kretser innebærer, samt gjøre deg kjent med vanlig praksis når det gjelder å unngå ulykker. Hvis du vil se oversettelser av de advarslene som finnes i denne publikasjonen, kan du se i dokumentet Regulatory Compliance and Safety Information (Overholdelse av forskrifter og sikkerhetsinformasjon) som ble levert med denne enheten.
Aviso Este símbolo de aviso indica perigo. Encontra-se numa situação que lhe poderá causar danos físicos. Antes de começar a trabalhar com qualquer equipamento, familiarize-se com os perigos relacionados com circuitos eléctricos, e com quaisquer práticas comuns que possam prevenir possíveis acidentes. Para ver as traduções dos avisos que constam desta publicação, consulte o documento Regulatory Compliance and Safety Information (Informação de Segurança e Disposições Reguladoras) que acompanha este dispositivo.
¡Advertencia! Este símbolo de aviso significa peligro. Existe riesgo para su integridad física. Antes de manipular cualquier equipo, considerar los riesgos que entraña la corriente eléctrica y familiarizarse con los procedimientos estándar de prevención de accidentes. Para ver una traducción de las advertencias que aparecen en esta publicación, consultar el documento titulado Regulatory Compliance and Safety Information (Información sobre seguridad y conformidad con las disposiciones reglamentarias) que se acompaña con este dispositivo.
Varning! Denna varningssymbol signalerar fara. Du befinner dig i en situation som kan leda till personskada. Innan du utför arbete på någon utrustning måste du vara medveten om farorna med elkretsar och känna till vanligt förfarande för att förebygga skador. Se förklaringar av de varningar som förkommer i denna publikation i dokumentet Regulatory Compliance and Safety Information (Efterrättelse av föreskrifter och säkerhetsinformation), vilket medföljer denna anordning.
Use the following basic guidelines when working with any electrical equipment:
Use the following guidelines when working with any equipment that is connected to telephone wiring or to other network cabling:
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 RSP4.
Following are chassis slot and DRAM requirements for ensuring RSP4 compatibility. There are no restrictions on installing an RSP4 in a Cisco 7507 provided that you install the RSP4 in slot 2 and/or slot 3. (See the section "What Is the Cisco 7507?, page 21.)
There are no restrictions on installing an RSP4 in a Cisco 7513 provided that you install the RSP4 in slot 6 and/or slot 7. (See the section "What Is the Cisco 7513?, page 22.)
Installing two RSP4s assumes you will be configuring and enabling the HSA feature.
You must obtain replacement DRAM DIMMs from an approved vendor. To ensure that you obtain the latest available product and vendor information, obtain the list from one of the following sources:
Although the PCMCIA card and DRAM DIMM specifications are defined in the manufacturers' part numbers, they must meet the following requirements:
Following are Flash memory card requirements for ensuring RSP4 compatibility.
You cannot boot from or use a Flash memory card in the RSP4 that was formatted on another type of RSP-based system (including RSP7000, RSP1 and RSP2) that was running a Cisco IOS software version earlier than Cisco IOS Release 11.1(8)CA1, or later.
You must first reformat the Flash memory card, formatted on one of these other RSP-based systems, before you can use it as a boot or storage source with the RSP4. (Downloading ROM monitor images directly to the Flash boot ROM device [U5] is not supported functionality with the initial release of the RSP4; this functionality will be available in a future Cisco IOS release.)
| Caution To prevent system problems, use Flash memory cards in the RSP4 that were formatted on an RSP1, RSP2, RSP7000, or RSP4 running Cisco IOS Release 11.1(8)CA1 or later. |
The RSP4 is compatible with Cisco IOS Release 11.1(8)CA1 or later, and Cisco IOS Release 11.2(7)P or later.
The show version and show hardware commands display the current hardware configuration of the router, including the system software version that is currently loaded and running. The show microcode command lists the bundled microcode (and target hardware) version for each processor type. The show controller cbus command shows the microcode version you are running. The show diagbus command shows the RSP4 board's hardware version (Version 1.0 at initial release) and revision (Revision A0 at initial release).
For additional descriptions of show commands, refer to the Configuration Fundamentals Configuration Guide and Configuration Fundamentals Command Reference publications, listed in the section "If You Need More Information," on page 2, and which are available on the Documentation CD-ROM or as printed copies.
To ensure that the slave RSP4 will operate properly with the full system configuration, should the master RSP4 ever fail in a system with the HSA feature configured, the slave RSP4 should have the same DRAM configuration and boot-ROM version as the master RSP4.
| Caution Removing the system master RSP4, while the system is operating, will cause the system to crash; however, the system will reload with the slave RSP4 as the new system master. To prevent any system problems, do not remove the system master RSP4 while the system is operating. |
| Caution Before you can use a Flash memory card that was previously formatted and used in a Route Processor (RP), a 7000 Series Route Switch Processor (RSP7000), or a Route Switch Processor (RSP1 or RSP2), you must reformat the Flash memory card. Flash memory cards formatted on any of these processors will not work properly in an RSP4. To ensure that you can boot a Cisco IOS software image from a Flash memory card that was formatted and used in any of these systems, you must first reformat it on your RSP4 system. |
Microcode is a set of processor-specific software instructions that enables and manages the features and functions of a specific processor type. At system startup or reload, the system loads the microcode for each processor type present in the system. The latest available microcode image for each processor type is bundled and distributed with the system software image.
New microcode is released to enable new features, improve performance, or fix bugs in earlier versions. The Cisco routers feature downloadable software and microcode for most upgrades. These features enable you to download new (upgraded) images remotely, store the images in router memory, and load the new images at system startup without having to physically access the router.
You can store multiple versions for a specific processor type in Flash memory and use configuration commands to specify which version the system should load at startup. All interfaces of the same type (for example, all CIPs) use the same microcode image. Although most upgrades can be downloaded, some exceptions require ROM replacement to ensure proper startup and operation. Microcode images that are bundled with the system image load automatically along with the new software image, except for the Channel Interface Processor (CIP) microcode image, which is bundled separately. The software and interface processor microcode images are carefully optimized and bundled to work together.
You need some or all of the following tools and parts to install, remove, and replace an RSP4 or upgrade DRAM. If you need additional equipment, contact a customer service representative for ordering information.
| Caution To prevent memory problems, DRAM DIMMS must be 3.3--volt (V) devices. Do not attempt to install higher-voltage devices (such as those designed for the RSP2) in the RSP4's DIMM sockets. |
This section describes the procedures for saving and retrieving the system configuration. Configuration information resides in two places when the router is operating: the default (permanent) configuration in NVRAM, and the running (temporary) memory in RAM. The default configuration always remains available; NVRAM retains the information even when the power is shut down. The current information is lost if the system power is shut down. The current configuration contains all nondefault configuration information that you added with the configure command, the setup command facility, or by editing the configuration file.
The copy running-config startup-config command adds the current configuration to the default configuration in NVRAM so that it will also be saved when power is shut down. Whenever you make changes to the system configuration, issue the copy running-config startup-config command to ensure that the new configuration is saved.
If you replace the RSP4 in a system with only one RSP4, you also replace the entire configuration, which resides in NVRAM on the RSP4. If you copy the configuration file to a remote server before removing the RSP4, you can retrieve it later and write it into NVRAM on the new RSP4. You can also use the copy running-config slot0:config-file command to save the configuration file in to Flash memory, and then use the copy slot0:config-file nvram: command to restore it.
If you do not copy the configuration file, you will have to use the configure command or the setup command facility to reenter the configuration information after you install the new RSP4. For complete descriptions of these two commands, and instructions for using them, refer to the appropriate software documentation.
If you are temporarily removing an RSP4, it is not necessary to copy the configuration file to a remote server; the lithium batteries will retain the configuration file in memory until you replace the RSP4 in the system. This procedure requires privileged-level access to the EXEC command interpreter, which usually requires a password. Refer to the description that follows and contact your system administrator to obtain access, if necessary.
Before you use the configure command, 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:
enable
Step 2 Enter the password (the password is case sensitive). For security purposes, the password is not displayed.
Step 3 When you enter the correct password, the system displays the privileged-level system prompt (#) as follows:
The pound sign (#) at the system prompt indicates the privileged level of the EXEC command interpreter, from which you can execute EXEC-level commands described in the following sections.
Before you attempt to copy or retrieve a file from a remote host, ensure that the connection is good between the router and the remote server by using the packet internet groper (ping) program. The ping program sends a series of echo request packets to the remote device and waits for a reply. If the connection is good, the remote device echoes them back to the local device.
The console terminal displays the results of each message sent: an exclamation point (!) indicates that the local device received an echo, and a period (.) indicates that the server timed out while awaiting the reply. If the connection between the two devices is good, the system displays a series of exclamation points (! ! !) or [ok]. If the connection fails, the system displays a series of periods (. . .) or [timed out] or [failed].
To verify the connection between the router and a remote host, issue the ping command followed by the name or Internet Protocol (IP) address of the remote server; then press Return. Although the ping command supports configurable options, the defaults, including IP as the protocol, are enabled when you enter a host name or address on the same line as the ping command. For a description of the configurable options, refer to the appropriate software documentation.
The following example shows a successful ping operation:
Router# ping 1.1.1.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 12/12/12 ms
The following example shows the results of a failed ping operation:
Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) Router#
If the connection fails, check the physical connection to the remote file server and verify that you are using the correct address or name, 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 (save) the running configuration to a TFTP file server, ensure the following:
To store information on a remote host, enter the privileged EXEC command write network. The command prompts you for the destination host's address and a filename, then displays the instructions for confirmation. When you confirm the instructions, the router sends a copy of the currently running configuration to the remote host. The system default is to store the configuration in a file called by the name of the router with -confg appended. You can either accept the default filename by pressing Return at the prompt, or enter a different name before pressing Return.
Follow these steps to copy the currently running configuration to a remote host:
Step 1 The system prompt should display a pound sign (#) to indicate the privileged level of the EXEC command interpreter. If it does not, follow the steps in the section "Using the EXEC Command Interpreter," on page 15, to enable the privileged level.
Step 2 Use the ping command to check the connection between the router and the remote host. (See the previous section "Using the ping Command.")
Step 3 Issue the show running-config command to display the currently running configuration on the terminal and ensure that the configuration information is complete and correct. If it is not, use the configure command to add or modify the existing configuration. (Refer to the appropriate software documentation for descriptions of the configuration options available for the system and individual interfaces, and for specific configuration instructions.)
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.)
copy startup-config tftp
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:
copy startup-config tftp
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:
Step 8 Before the router executes the copy process, it displays the instructions you entered for confirmation. If the instructions are not correct, enter n (no) then Return to abort the process. To accept the instructions, press Return, or y and then Return, and the system begins the copy process. In the following example, the default is accepted:
While the router copies the configuration to the remote host, it displays a series of exclamation points (! ! !) or periods (. . .). The !!!! and [ok] indicate that the operation is successful. A display of . . . [timed out] or [failed] indicates a failure, which would probably be due to a network fault or the lack of a writable, readable file on the remote file server.
Step 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):
your configuration was not saved. Repeat the preceding steps, or select a different remote file server and repeat the preceding steps.
After you upload the configuration file, proceed to the section "Removing the RSP4, page 23. If you are unable to copy the configuration to a remote host successfully, contact your network administrator or refer to the end of this document for instructions on contacting technical assistance.
After you install the new RSP4, you can retrieve the saved configuration and copy it to NVRAM. To retrieve the configuration, enter configuration mode and specify that you will configure the router from the network. The system prompts you for a host name and address, the name of the configuration file stored on the host, and confirmation to reboot using the remote file.
You can access the router through a console terminal attached directly to the RSP4 console port, or you can configure an interface port and Telnet to the router from a remote terminal.
Follow these steps to retrieve the currently running configuration from a remote host:
Step 1 On the console terminal, the system prompt should display a pound sign (#) to indicate the privileged level of the EXEC command interpreter. If it does not, follow the steps in the section "Using the EXEC Command Interpreter, page 15 to enable the privileged level.
Step 2 Configure an interface port on the router for a connection to a remote host (TFTP server).
Step 3 Use the ping command to verify the connection between the router and the remote host. (See the section "Using the ping Command" on page 15.)
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).
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).
1.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.
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.
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 will appear:
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:
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 refer to 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:
show startup-config
Step 11 Ensure that the startup configuration file stored in NVRAM is the default running configuration file used by the system, issue the copy startup-config running-config command as follows:
copy startup-config running-config
This completes the procedure for retrieving the saved configuration file.
The Cisco 7505 is a 5-slot router chassis, which uses the Route Switch Processor (RSP4) (or RSP1) and CxBus and CyBus interface processors. The Cisco 7505 provides up to four interface processor slots. While the Cisco 7505 has one high-speed, 1.067-gigabit-per-second (Gbps) CyBus, it can accommodate all CxBus-based interface processors.
In the Cisco 7505 (see Figure 3), one slot (4) is reserved for the RSP4, which contains the system processor and performs packet switching functions. Slots 0 through 3 are for interface processors.
The Cisco 7507 is a 7-slot router chassis, which uses up to two Route Switch Processors (RSP4s) (or two RSP2s, or one RSP4 and one RSP2) and CxBus and CyBus interface processors. The Cisco 7507 provides up to five interface processor slots. Although the Cisco 7507 uses two high-speed, 1.067-gigabit-per-second (Gbps) CyBuses, it can accommodate all CxBus-based interface processors.
Figure 4 shows the rear of the seven-slot Cisco 7507 router. In the Cisco 7507, up to two slots (2 and 3) are reserved for the RSP, which contains the system processor and performs packet switching functions. Slots 0 and 1 and 4 through 6 are for interface processors. The five interface processor slots numbered slot 0 (far left) and slot 1 (called CyBus 0), and slot 4 through slot 6 (called CyBus 1).
The Cisco 7513 is a 13-slot router chassis, which uses up to two Route Switch Processors (RSP4s) (or two RSP2s, or one RSP4 and one RSP2) and CxBus and CyBus interface processors. The Cisco 7513 provides up to eleven interface processor slots. Although the Cisco 7513 uses two high-speed, 1.067-gigabit-per-second (Gbps) CyBuses, it can accommodate all CxBus-based interface processors.
Figure 5 shows the interface processor end of the Cisco 7513, which provides access to the thirteen slots, the system blower, and the power supplies. When facing the interface processor end of the router, the RSP is installed in RSP slot 6 and/or 7. The eleven interface processor slots are numbered from slot 0 (far left) through slot 5 (called CyBus 0) and slot 8 through slot 12 (called CyBus 1).
The following sections describe the procedures for installing or replacing an RSP4. Ensure that your system meets the minimum software, hardware, and microcode requirements described in the sections "System Software Requirements, page 12, "Hardware Requirements" on page 13, and "Microcode Requirements, page 13. Proceed to the section "Removing the RSP4" for instructions on removing the RSP4, and then to the section "Replacing the RSP4" for the installation instructions. After the new RSP4 is secure, follow the procedures in the section "Troubleshooting the Installation, page 45 to verify that it is installed and functioning properly.
| Caution Removing the only installed RSP4 from a system, while the system is operating, will cause the system to crash. Consider this before removing an RSP4 while the system is operating. To ensure that the slave RSP4 will operate properly with the full system configuration, should the master RSP4 ever fail, the slave RSP4 should have the same boot-ROM and DRAM configuration as the master RSP4. |
When you remove or install the RSP4, be sure to use the ejector levers, which help to ensure that the RSP4 is fully inserted in the backplane or fully dislodged from it. An RSP4 that is only partially connected to the backplane can halt the system unless a second RSP4 is installed. Figure 7 on page 25 shows a detail of the ejector lever mechanism in a horizontal position that is appropriate for the router. When you simultaneously push the ejector levers inward (toward the carrier handle), the levers push the RSP4 into the slot and ensure that the board connectors are fully seated in the backplane. Follow these steps to remove the RSP4:
Step 1 Optional step: If you are replacing the RSP4 in a system with one RSP4, copy the currently running configuration file to a TFTP server so you can retrieve it later. (See the section "Saving and Retrieving the Configuration File, page 14.)
Step 2 Attach an antistatic strap to yourself and then connect the equipment end of the strap to a captive installation screw on an installed interface processor, or to any unfinished chassis surface.
Step 3 If you are replacing the RSP4, disconnect any devices that are attached to the console or auxiliary ports. If you are removing the RSP4 for maintenance and will reinstall the same one, you can leave the devices attached provided that doing so will not strain the cables.
Step 4 Use a screwdriver (number 2 Phillips or 3/16 -inch flat-blade) to loosen the two captive installation screws. (See Figure 7 on page 25.)
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 7c) to release the carrier from the slot and to dislodge the RSP4 from the backplane.
Step 6 Grasp the handle of the RSP4 with one hand and pull the RSP4 straight out of the slot, keeping your other hand under the carrier to guide it. (See Figure 7.) Keep the carrier parallel to the backplane. Avoid touching the board or any connector pins.
Step 7 Place the removed RSP4 on an antistatic mat or foam. If you plan to return the RSP4 to the factory, immediately place it in an antistatic bag to prevent ESD damage.
Step 8 Attach the equipment end of the ESD-preventive strap to the RSP4 before performing any maintenance on the RSP4 that might create an ESD hazard.
This completes the removal procedure. If you removed the RSP4 to replace DIMMs, proceed to the appropriate section. If you are replacing the RSP4, proceed to the next section to install the new RSP4.
The RSP4 is keyed for installation only in an RSP slot. (See Figures 1 and 2.) By default, the system master is the RSP4 that occupies the first RSP slot in the router: slot 2 in the Cisco 7507, and slot 6 in the Cisco 7513. Follow these steps to install an RSP4:
Step 1 Grasp the RSP4 handle with one hand and place your other hand under the carrier to support and guide it into the slot. (See Figure 7.) Avoid touching the board or any connectors.
Step 2 Place the back of the RSP4 in the appropriate RSP slot and align the notches along the edge of the carrier with the grooves in the slot. (See Figure 7a.)
| Caution To prevent damage to the backplane, you must install the RSP4 in one of the two RSP slots on the router. (See Figure 5 on page 22.) The slots are keyed for correct installation. Forcing the RSP4 into a different slot can damage the backplane and the RSP4. |
Step 3 While keeping the RSP4 parallel to the backplane, carefully slide the carrier into the slot until the RSP4 faceplate makes contact with the ejector levers, then stop. (See Figure 7b.)
Step 4 Using the thumb and forefinger of each hand to pinch each ejector, simultaneously push both ejectors inward (toward the handle) until they parallel to the faceplate. (See Figure 7c.)
Step 5 Use a screwdriver (number 2 Phillips or 3/16-inch flat-blade) to tighten the captive installation screws on the ends of the RSP4. (See Figure 7a.)
Step 6 Use a screwdriver to tighten the two captive screws on the RSP4 faceplate to prevent the RSP4 from becoming partially dislodged from the backplane and to ensure proper EMI shielding. (These screws must be tightened to meet EMI specifications.)
Step 7 If you disconnected the console terminal to remove the RSP4, or if you are installing a new RSP4, connect the console terminal to the console port. (Refer to the section "Connecting a Console Terminal" on page 26.)
Step 8 Ensure that a console terminal is connected (refer to the section "Connecting a Console Terminal" on page 26) and that it is turned on.
Step 9 Turn the system power back ON, and proceed to the section "Restarting the System," on page 28, to check the installation.
The system console port on the RSP4 is a DB-25 receptacle DCE port for connecting a data terminal, which you will need to configure and communicate with your system. The console port is located on the RSP4 just below the auxiliary port, as shown in Figure 8, and is labeled Console.
Before connecting the console port, check your terminal's 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 RSP4, then follow the steps in the section "Restarting the System" on page 28.
The auxiliary port on the RSP4 is a DB-25 plug DTE port for connecting a modem or other DCE device (such as a CSU/DSU or other router) to the router. The port is located next to the console port on the RSP4 and is labeled AUX. An example of a modem connection is shown in Figure 8.
For systems with two RSP4s installed (one as master and one as slave in RSP slots 2 and 3, in the Cisco 7507, and slots 6 and 7 in the Cisco 7513, using the HSA feature), you can simultaneously connect to both console or auxiliary ports using a special, optional Y-cable. RSP4 defaults as the system master if only one is installed.
Figure 9 shows the console Y-cable and Figure 10 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 section "System Startup Sequence, page 47.)
Follow these steps to verify that the RSP4 is installed and functioning properly:
Step 1 Check the RSP4 connections to make sure they are secure:
Step 2 Observe the RSP4 LEDs. While the system initializes, the CPU halt LED on the RSP4 stays on, then goes off when the boot process is complete. As the RSP4 initializes each interface processor, the status LEDs on each interface processor go on and off in irregular sequence.
Step 3 For a Cisco 7507 or Cisco 7513 with HSA configured, verify that the console terminal displays the system banner and startup screen as the system restarts. The master console display should look similar to the following for a Cisco 7513 (note the RSP slots indicated):
The master console display should look similar to the following for a Cisco 7507 (note the RSP slots indicated):
[additional displayed text omitted from this example]
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 RSP4 (non-HSA), verify that the console terminal displays the system banner and startup screen as the system restarts. The display should look similar to the following:
Step 5 After the system boots the software and initializes the interface processors, verify that the RSP4 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 RSP4 installed, use the show version command to verify that the slave RSP4 is recognized by the system. Following is a sample from a Cisco 7513:
show version
When you have verified all the conditions in Steps 2 through 6 (or Step 7 if you have a second RSP4 installed and want to use the HSA feature), the installation is complete. If you replaced the RSP4 and saved your configuration file to a remote server before doing so, proceed to the section "Retrieving the Configuration File, page 18. If you replaced the RSP4 and did not save the configuration, use the configure command or the setup command facility to reenter the configuration information.
An error condition exists if no LEDs go on at power up or after initialization, or if the boot error or CPU halt LEDs go on and remain on. If this happens, proceed to the section "Troubleshooting the Installation," on page 45, to try to isolate the problem. For more complete configuration information, refer to the Configuration Fundamentals Configuration Guide and the Configuration Fundamentals Command Reference publications, which are available on the Documentation CD-ROM or as printed copies.
If you have a second RSP4 installed, you must configure the HSA feature for your Cisco 7507 or Cisco 7513 router. Read the following caution, then proceed to the following section "Configuring High System Availability Operation."
| Caution When you install a second RSP4 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 RSP4 card taking over mastership of the router when the master fails, rendering the network inoperable. |
High system availability (HSA) refers to how quickly your router returns to an operational status after a failure occurs. You can install two RSP4 cards in a single router to improve system availability.
For more complete HSA configuration information, refer to the Configuration Fundamentals Configuration Guide and the Configuration Fundamentals Command Reference publications, which are available on the Cisco Documentation CD-ROM or as printed copies.
Two RSP4 cards in a router provide the most basic level of increased system availability through a "cold restart" feature. A "cold restart" means that when one RSP4 card fails, the other RSP4 card reboots the router. In this way, your router is never in a failed state for very long, thereby increasing system availability.
When one RSP4 card takes over operation from another, system operation is interrupted. Such a change is similar to issuing the reload command. The following events occur when one RSP4 card fails and the other takes over:
A router configured for HSA operation has one RSP4 card that is the master and one that is the slave. The master RSP4 card functions as if it were a single processor, controlling all functions of the router. The slave RSP4 card does nothing but actively monitor the master for failure. A system crash can cause the master RSP4 to fail or go into a nonfunctional state. When the slave RSP4 detects a nonfunctional master, the slave resets itself and takes part in master-slave arbitration. Master-slave arbitration is a ROM monitor process that determines which RSP4 card is the master and which is the slave upon startup (or reboot).
If a system crash causes the master RSP4 to fail, the slave RSP4 becomes the new master RSP4 and uses its own system image and configuration file to reboot the router. The failed RSP4 card (now the slave) remains inactive until you perform diagnostics, correct the problem, and then issue the slave reload command.
| Caution To ensure that the slave RSP4 will operate properly with the full system configuration should the master RSP4 ever fail, the slave RSP4 should have the same DRAM configuration as the master RSP4. |
With HSA operation, the following items are important to note:
| Caution Removing the system master RSP4 while the system is operating will cause the system to crash; however, the system will reload with the slave RSP4 as the new system master. To prevent any system problems, do not remove the system master RSP4 while the system is operating. |
There are two common ways to use HSA as follows:
You can also use HSA for advanced implementations. For example, you can configure the RSP4 cards with the following:
To configure HSA operation, you must have a Cisco 7507 or Cisco 7513 containing two RSP4 processor cards and Cisco IOS Release 11.1(8)CA1, or later. The slave RSP4 should have the same DRAM configuration as the master RSP4.
When configuring HSA operation, complete the tasks in the following sections. The first task is required. Depending on the outcome of the first task, the second or third task is also required. The fourth and fifth tasks are optional.
Before you can configure HSA operation, you must first decide how you want to use HSA in your internetwork. Do you want to use HSA for simple hardware backup or for software error protection? If you are using new or experimental Cisco IOS software, consider using the software error protection method; otherwise, use the simple hardware backup method.
Once you have decided which method to use, proceed to either the "Configuring HSA for Simple Hardware Backup" section or the "Configuring HSA for Software Error Protection" section.
With the simple hardware backup method, you configure both RSP4 cards with the same software image and configuration information. To configure HSA for simple hardware backup, perform the tasks in the following sections. The first task is optional.
Because your view of the environment is always from the master RSP4's perspective, you define a default slave RSP4. The router uses the default slave information when booting:
To define the default slave RSP4, perform the following task, beginning in global configuration mode:
Upon the next system reboot, the above changes take effect (if both RSP4 cards are operational). Thus, the specified default slave becomes the slave RSP4 card. The other RSP4 card takes over mastership of the system and controls all functions of the router.
If you do not specifically define the default slave RSP4, the RSP4 card located in the higher number processor slot is the default slave. On the Cisco 7507, processor slot 3 contains the default slave RSP4. On the Cisco 7513, processor slot 7 contains the default slave RSP4.
The following example sets the default slave RSP4 to processor slot 2 on a Cisco 7507:
Router#configure terminalRouter (config)#slave default-slot 2^ZRouter#copy running-config startup-config
To ensure that both RSP4 cards have the same system image, perform the following tasks in EXEC mode:
The following example ensures that both RSP4 cards have the same system image. Note that because no environment variables are set, the default environment variables are in effect for both the master and slave RSP4.
Router#show bootBOOT variable = CONFIG_FILE variable = Current CONFIG_FILE variable = BOOTLDR variable does not exist Configuration register is 0x0 Slave auto-sync config mode is on current slave is in slot 7 BOOT variable = CONFIG_FILE variable = BOOTLDR variable does not exist Configuration register is 0x0 Router#dir slot0:-#- -length- -----date/time------ name 1 3482498 May 4 1993 21:38:04 rsp-k-mz11.2 7993896 bytes available (1496 bytes used) Router#dir slaveslot0:-#- -length- -----date/time------ name 1 3482498 May 4 1993 21:38:04 rsp-k-mz11.1 7993896 bytes available (1496 bytes used) Router#delete slaveslot0:rsp-k-mz11.1Router#copy slot0:rsp-k-mz11.2 slaveslot0:rsp-k-mz11.2
To ensure that both RSP4 cards have the same microcode images, perform the following tasks beginning in privileged EXEC mode:
The following example ensures that both RSP4 cards have the same microcode image. Notice that slots 0, 1, 4, 9, and 10 load microcode from the bundled software, as noted by the statement software loaded from system. 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 RSP4 has a copy of the same FSIP microcode in the same location.
Router#show controller cbusMEMD 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-1No 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's startup configuration when you issue a copy command that specifies the master's startup configuration (startup-config) as the target.
Automatic synchronization mode is on by default; however, to turn it on manually, perform the following tasks beginning in global configuration mode:
The following example turns on automatic configuration file synchronization:
Router#configure terminalRouter (config)#slave auto-sync configRouter (config)#^ZRouter#copy running-config startup-config
With the software error protection method, you configure the RSP4 cards with different software images, but with the same configuration information. To configure HSA for software error protection, perform the following tasks. The first task is optional.
When the factory sends you a new router with two RSPs, you receive the same system image on both RSP4 cards. To configure the HSA feature for software error protection, you need two separate software images on the RSP4 cards. Thus, you copy a desired image to the master RSP4 card and modify the boot system commands to reflect booting two separate system images. Each RSP4 card uses its own image to boot the router when it becomes the master.
To specify different startup images for the master and slave RSP4, perform the following tasks beginning in EXEC mode:
| Tasks | Command |
| Step 1 Verify the location and version of the master RSP4 software image. | dir [/all | /deleted] [/long] {bootflash | slot0 | slot1} [filename] |
| Step 2 Determine if the slave RSP4 contains the same software image in the same location. | dir [/all | /deleted] [/long] {slavebootflash | slaveslot0 | slaveslot1} [filename] |
| Step 3 Copy a different system image to the master RSP4. | copy file_id {bootflash | slot0 | slot1}
copy flash {bootflash | slot0 | slot1} |
| Step 4 Enter configuration mode from the terminal. | configure terminal |
| Step 5 From global configuration mode, configure the master RSP4 to boot the new image from the appropriate location. | boot system flash bootflash:[filename] boot system flash slot0:[filename] boot system flash slot1:[filename] |
| Step 6 Also, add a boot system command that specifies the slave's boot image and location. This is the boot image that the slave uses when it becomes the master RSP4 and boots the system. Note that because the slave will boot this image when the slave is actually the new master RSP4, the command syntax does not use a "slave" prefix. | boot system flash bootflash:[filename] boot system flash slot0:[filename] boot system flash slot1:[filename] |
| Step 7 Configure the master RSP4 to boot from a network server. | boot system [rcp | tftp] filename [ip-address]
|
| Step 8 Set the configuration register to enable loading of the system image from a network server or Flash. | config-register value 1 |
| Step 9 Exit configuration mode. | Ctrl-Z |
| Step 10 Save the configuration file to the master's startup configuration. Because automatic synchronization is turned on, this step saves the boot system commands to the master and slave startup configuration. | copy running-config startup-config |
| Step 11 Reset the router with the new configuration information. | reload |
In the following example scenario, assume the following:
Figure 11 illustrates the software error protection configuration for this example scenario. The configuration commands for this configuration follow the figure.
Because you always view the environment from the master RSP4's perspective, in the following command you view the master's slot 0 to verify the location and version of the master's software image:
Router# dir slot0:
-#- -length- -----date/time------ name
1 3482496 May 4 1993 21:38:04 rsp-k-mz11.1
7993896 bytes available (1496 bytes used)
Now view the slave's software image location and version:
Router# dir slaveslot0:
-#- -length- -----date/time------ name
1 3482496 May 4 1993 21:38:04 rsp-k-mz11.1
7993896 bytes available (1496 bytes used)
Because you want to run the Release 11.2 system image on one RSP4 card and the Release 11.1 system image on the other RSP4 card, copy the Release 11.2 system image to the master's slot 0:
Router# copy tftp slot0:rsp-k-mz11.2
Enter global configuration mode and configure the system to boot first from a Release 11.2 system image and then from a Release 11.1 system image.
Router#configure terminalRouter (config)#boot system flash slot0:rsp-k-mz11.2Router (config)#boot system flash slot0:rsp-k-mz11.1
With this configuration, when the slot 6 RSP4 card is master, it looks first in its PCMCIA slot 0 for the system image file rsp-k-mz11.2 to boot. Finding this file, the router boots from that system image. When the slot 7 RSP4 card is master, it also looks first in its slot 0 for the system image file rsp-k-mz11.2 to boot. Because that image does not exist in that location, the slot 7 RSP4 card looks for the system image file rsp-k-mz11.1 in slot 0 to boot. Finding this file in its PCMCIA slot 0, the router boots from that system image. In this way, each RSP4 card can reboot the system using its own system image when it becomes the master RSP4 card.
Configure the system further with a fault-tolerant booting strategy:
Router (config)# boot system tftp rsp-k-mz11.1 1.1.1.25
Set the configuration register to enable loading of the system image from a network server or from Flash and save the changes to the master and slave startup configuration file:
Router (config)#config-register 0x010FRouter (config)#^ZRouter#copy running-config startup-config
Reload the system so that the master RSP4 uses the new Release 11.2 system image:
Router# reload
In the following example scenario, assume the following:
In this scenario, you begin with the configuration shown in Figure 12.
Next, you copy the rsp-k-mz11.1 image to the master and slave RSP4 card, as shown in Figure 13.
Last, delete the rsp-k-mz11.2 image from the slave RSP4 card as shown in Figure 14:
The following commands configure software error protection for this example scenario.
View the master and slave slot 0 to verify the location and version of their software images:
Router#dir slot0:-#- -length- -----date/time------ name 1 3482498 May 4 1993 21:38:04 rsp-k-mz11.2 7993896 bytes available (1496 bytes used) Router#dir slaveslot0:-#- -length- -----date/time------ name 1 3482498 May 4 1993 21:38:04 rsp-k-mz11.2 7993896 bytes available (1496 bytes used)
Copy the Release 11.1 system image to the master and slave slot 0:
Router#copy tftp slot0:rsp-k-mz11.1Router#copy tftp slaveslot0:rsp-k-mz11.1
Delete the rsp-k-mz11.2 image from the slave RSP4 card:
Router# delete slaveslot0:rsp-k-mz11.2
Configure the system to boot first from a Release 11.2 system image and then from a Release 11.1 system image.
Router#configure terminalRouter (config)#boot system flash slot0:rsp-k-mz11.2Router (config)#boot system flash slot0:rsp-k-mz11.1
Configure the system further with a fault-tolerant booting strategy:
Router(config)# boot system tftp rsp-k-mz11.1 1.1.1.25
Set the configuration register to enable loading of the system image from a network server or from Flash and save the changes to the master and slave startup configuration file:
Router(config)#config-register 0x010FCrtl-zRouter#copy running-config startup-config
You can optionally set environment variables on both RSP4 cards in a Cisco 7507 and Cisco 7513.
You set environment variables on the master RSP4 just as you would if it were the only RSP4 card in the system. You can set the same environment variables on the slave RSP4 card, manually or automatically.
The following sections describe these two methods:
For more complete configuration information on how to set environment variables, refer to the Configuration Fundamentals Configuration Guide and the Configuration Fundamentals Command Reference publications, which are available on the Documentation CD-ROM or as printed copies.
Once you set the master's environment variables, you can manually set the same environment variables on the slave RSP4 card using the slave sync config command.
To manually set environment variables on the slave RSP4, perform the following steps beginning in global configuration mode:
With automatic synchronization turned on, when you set the master's environment variables and save them, the system automatically saves the same environment variables to the slave's startup configuration.
To set environment variables on the slave RSP4 when automatic synchronization is on, perform the following steps beginning in global configuration mode:
To monitor and maintain HSA operation, you can override the slave image that is bundled with the master image. To do so, perform the following task in global configuration mode:
| Tasks | Command |
| Specify which image the slave runs. | slave image {system | device:filename} |
You can manually synchronize configuration files and ROM monitor environment variables on the master and slave RSP4 card. To do so, perform the following task in privileged EXEC mode:
| Tasks | Command |
| Manually synchronize master and slave configuration files. | slave sync config |
| Caution When you install a second RSP4 card for the first time, you must immediately configure it using the slave sync config command. This ensures that the new slave is configured consistently with the master. Failure to do so may result in an unconfigured slave RSP4 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 your system does not restart and boot up as expected. Review the descriptions that follow so you can anticipate the expected system startup sequence. Then restart the system and try to isolate the problem by observing the LEDs as the system attempts to boot the software and initialize the RSP4(s) and each interface processor.
Following are functional descriptions of the LEDs on the power supplies and processor modules, and the behavior you should observe at system startup.
On the router, the AC (or DC) OK LED is located on each power supply. If this LED does not go on and stay on, there is most likely a problem with the input power or one of the internal DC lines.
The AC (or DC) OK LED will not go on or will go off if the power supply reaches an out-of-tolerance temperature or voltage condition. It is unlikely that the power supply will shut down during startup because of an overtemperature condition; however, it can shut down if it detects an over or undervoltage condition during startup. For descriptions of environmental monitoring functions, refer to the Cisco 7507 Hardware Installation and Maintenance or Cisco 7513 Hardware Installation and Maintenance publications, which are available on the Documentation CD-ROM or in print.
Figure 15 shows the LEDs on the RSP4 faceplate. The LEDs on the RSP4 indicate the system and RSP4 status and which Flash memory card slot is active. The CPU halt LED, which goes on only if the system detects a processor hardware failure, should remain off. A successful boot is indicated when the normal LED goes on; however, this does not necessarily mean that the system has reached normal operation. During normal operation, the CPU halt LED should be off, and the normal LED should be on, indicating that the RSP4 is receiving +5V. The slot 0 and slot 1 LEDs indicate which PCMCIA (Flash memory) card slot is in use, and each LED blinks when the card is accessed by the system. The master and slave LEDs provide a visual indication of whether the RSP4 is designated as a master or a slave device.
| Caution The reset switch (see Figure 15) resets the RSP4 and the entire system. To prevent system errors and problems, use it only at the direction of your Cisco-certified service representative. |
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, then use the troubleshooting procedures wherever the system fails to operate as expected. If you are able to isolate the problem to a faulty hardware component, or if you are unable to successfully restart the system, refer to the end of this document for instructions on contacting a service representative.
During the boot sequence, the system banner display pauses while it initializes the memory. If your router has more than 32 MB of DRAM, you may notice an increase in the amount of time required to initialize the memory. The pause in the banner display occurs after the copyright line, and before the system displays the list of installed hardware, as shown in the following display:
%SYS-5-RELOAD: Reload requested System Bootstrap, Version 11.1(8)CA1 Copyright (c) 1986-1996 by cisco Systems, Inc. [System initializes memory at this point in the display]
Use the following startup sequences and troubleshooting procedures to isolate system problems:
When the system power LED indicates normal operation, proceed to number 2.
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 RSP4 installation and replacement procedure. For complete command descriptions and examples, refer to the Configuration Fundamentals Command Reference publication, which is available on the Documentation CD-ROM or as a paper copy.
When a new master RSP4 takes over ownership of the router, it automatically reboots the failed RSP4 as the slave RSP4. You can access the state of the failed RSP4 in the form of a stack trace from the master console using the show stacks command.
You can also manually reload a failed RSP4 from the master console. To do so, perform the following task from global configuration mode:
| Tasks | Command |
| Reload the inactive slave RSP card. | slave reload |
You can also display information about both the master and slave RSP4s. To do so, perform any of the following tasks from EXEC mode:
| Tasks | Command |
| Display the environment variable settings and configuration register settings for both the master and slave RSP cards. | show boot |
| Show a list of flash devices currently supported on the router. | show flash devices |
| Display the software version running on the master and slave RSP card. | show version |
| Display the stack trace and version information of the master and slave RSP cards. | show stacks 1 |
The following sections include reference information and configuration and maintenance procedures for the RSP4. The following sections are included:
The console port on the RSP4 is an EIA/TIA-232, DCE, DB-25 receptacle. Both DSR and DCD are active when the system is running. The RTS signal tracks the state of the CTS input. The console port does not support modem control or hardware flow control. The console port requires a straight-through EIA/TIA-232 cable. Table 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 RSP4 is an EIA/TIA-232 DTE, DB-25 plug to which you can attach a CSU/DSU or other equipment in order to access the router from the network. The asynchronous auxiliary port supports hardware flow control and modem control. Table 3 lists the signals used on this port.
| Pin | Signal | Direction | Description |
|---|---|---|---|
| 2 | TxD | --> | Transmit Data |
| 3 | RxD | <-- | Receive Data |
| 4 | RTS | --> | Request To Send (used for hardware flow control) |
| 5 | CTS | <-- | Clear To Send (used for hardware flow control) |
| 6 | DSR | <-- | Data Set Ready |
| 7 | Signal Ground | - | Signal Ground |
| 8 | CD | <-- | Carrier Detect (used for modem control) |
| 20 | DTR | --> | Data Terminal Ready (used for modem control only) |
The console and auxiliary Y-cables allow you to simultaneously connect the console ports or auxiliary ports on two RSP4s (configured as system master and slave in RSP slots 2 and 3, in the Cisco 7507, and RSP slots 6 and 7 in the Cisco 7513) to one console terminal or external auxiliary device (such as a modem, and so forth).
The two Y-cables (CAB-RSP4CON=, shown in Figure 9 on page 27, and CAB-RSP4AUX= shown in Figure 10 on page 27) ship with the router and are available as spare parts. The console Y-cable pinout is listed in Table 4, and the auxiliary Y-cable pinout is listed in Table 5.
| Female DB-25 Pins | Male DB-25 Pins | Signal Description |
|---|---|---|
| P1-1 | J1-1 and J2-1 | Ground) |
| P1-2 | J1-2, and J2-2 | Receive Data (RxD) |
| P1-3 | J1-3 and J2-3 | Transmit Data (TxD) |
| P1-4 | J1-4 and J2-4 | Clear To Send (CTS); looped to 5 |
| P1-5 | J1-5 and J2-5 | Request To Send (RTS); looped to 4 |
| P1-6 | J1-6 and J2-6 | Data Set Ready (DSR) |
| P1-7 | J1-7 and J2-7 | Ground |
| P1-8 | J1-8 and J2-8 | Data Carrier Detect (DCD) |
| P1-13 | J1-13 and J2-13 | YCBL Detect Ground |
| P1-19 | J1-19 and J2-19 | YCBL Detect |
| P1-20 | J1-20 and J2-20 | Data Terminal Ready (DTR) |
| Male DB-25 Pins | Female DB-25 Pins | Signal Description |
|---|---|---|
| P1-1 | J1-1 and J2-1 | Ground |
| P1-2 | J1-2 and J2-2 | TxD |
| P1-3 | J1-3 and J2-3 | RxD |
| P1-4 | J1-4 and J2-4 | RTS |
| P1-5 | J1-5 and J2-5 | CTS |
| P1-7 | J1-7 and J2-7 | Ground |
| P1-8 | J1-8 and J2-8 | DCD |
| P1-13 | J1-13 and J2-13 | YCBL Detect |
| P1-19 | J1-19 and J2-19 | YCBL Detect Ground |
| P1-20 | J1--20 and J2-20 | DTR |
| P1-22 | J1-22 and J2-22 | Ring |
This section describes the steps for increasing the amount of DRAM by replacing up to two dual in-line memory modules (DIMMs), which you obtain from Cisco Systems.
The system DRAM resides on up to two DIMMs on the RSP4. The DRAM DIMM sockets are U10 (bank 0) and U13 (bank 1). (See Figure 16 and Table 6.) The default DRAM configuration is 32 MB (one 32-MB DIMM in U10). If two different sizes of DRAM DIMMs are installed, U10 must contain the largest DRAM DIMM.
| Caution To prevent system problems, do not use DRAM single in-line memory modules (SIMMs) from an RSP2 in the RSP4. The RSP4 requires DRAM dual in-line memory modules (DIMMs). |
Before proceeding, ensure that you have the proper tools and ESD-prevention equipment available. To upgrade DRAM, you install DIMMs in one or two banks (U10 and U13). Table 6 lists the various configurations of DRAM DIMMs that are available, the number of DIMMs for each configuration, and the DRAM banks they occupy. Note which banks are used given the combinations of available DIMM sizes and the maximum DRAM you require.
Depending on your router's configuration and the protocols and features your system is running, you might require more than 32 MB of DRAM for your RSP4. Upgrade your system DRAM based on your current configuration, this potential requirement, and according to Table 6.
| DRAM Sockets | Quantity | Totals | Product Numbers |
| U10 | One 32-MB DIMM | 32 MB | MEM-RSP4-32M1 |
| U13 | One 32-MB DIMM | 32 MB2 | MEM-RSP4-32M=2 |
| U10 and U13 | Two 32-MB DIMMs | 64 MB | MEM-RSP4-64M |
| U10 | One 128-MB DIMM | 128 MB | MEM-RSP4-128M(=) |
| U10 and U13 | Two 128-MB DIMMs | 256 MB | MEM-RSP4-256M(=) |
| Caution To prevent system and memory problems when installing DRAM, the RSP4's DRAM DIMMS must be 3.3V devices. Do not attempt to install higher-voltage devices (such as those designed for the RSP2) in the RSP4's DIMM sockets. Further, To prevent ESD damage, handle DIMMs by the card edges only. |
Two different sizes of DRAM DIMMs can occupy the two DRAM DIMM sockets (U10 and U13); however, the largest DRAM DIMM must occupy the U10 socket.
| Caution To prevent system and memory problems when installing one 128-MB DIMM on an RSP4 with one 32-MB DRAM DIMM in U10, remember that U10 must contain the largest DRAM DIMM; therefore, install the 128-MB DIMM in U10, only after you move the 32-MB DRAM DIMM to U13. |
This section includes the procedure for removing DIMMs from your RSP4.
Use this procedure to remove the existing DIMM(s):
Step 1 Turn OFF the system power and follow the steps in the section "Removing the RSP4, page 23.
Step 2 Place the RSP4 on an antistatic mat or pad and ensure that you are wearing an antistatic device, such as a wrist strap.
Step 3 Position the RSP4 so that the faceplate is toward you and the bus connectors are away from you--this position is shown in Figure 16 on page 53.
Step 4 Locate the DRAM DIMMs on the RSP4. The DIMMs occupy U10 (bank 0) and U13 (bank 1). (See Figure 16 on page 53.)
Step 5 For the DIMM you want to remove, pull down the lever on the DIMM socket to release the DIMM from the socket. (See Figure 17.)
Step 6 When one end of the DIMM is released from the socket, grasp each end of the DIMM with your thumb and forefinger and pull the DIMM completely out of the socket. Handle the edges of the DIMM only (see Figure 18 on page 55); avoid touching the memory module or pins and the metal traces, or fingers, along the socket edge.
Step 7 Place the DIMM in an antistatic bag to protect it from ESD damage.
Step 8 Repeat Steps 4 through 7 for the remaining DIMM, if required for your upgrade.
This completes the DIMM removal procedure. Proceed to the next section to install the new DIMMs.
This section includes the procedure for installing DIMMs on your RSP4.
| Caution To prevent system and memory problems when installing DRAM, the RSP4's DRAM DIMMS must be 3.3V devices. Do not attempt to install higher-voltage devices (such as those designed for the RSP2) in the RSP4's DIMM sockets. Further, DIMMs are sensitive components that can be shorted by mishandling; they are susceptible to ESD damage. Handle DIMMs by the edges only; avoid touching the DIMMs, pins, or traces (the metal fingers along the connector edge of the DIMM). (See Figure 18.) |
Use this procedure to install new DIMMs:
Step 1 Place the RSP4 on an antistatic mat or pad, and ensure that you are wearing an antistatic device, such as a wrist strap.
Step 2 Position the RSP4 so that the faceplate is toward you and the bus connectors are away from you, as shown in Figure 16 on page 53.
| Caution To prevent system problems and grounding problems if you plan to install one 128-MB DIMM for the 128-MB DRAM option or two 128-MB DRAM DIMMs for the 256-MB DRAM option, you must first install a protective post on the RSP4. (See Figure 19.) The protective post prevents the tops of installed 128-MB DRAM DIMMs from coming into contact with the metal carrier on an adjacent card when you install or remove your RSP4; this procedure is required if you plan to install any 128-MB DIMMs. |
Step 3 With your RSP4 positioned as shown in Figure 20, locate the screw shown in the enlargement; this is where you will attach the protective post to your RSP4.
Step 4 Carefully remove the screw from the RSP4 using a Number 1 Phillips screwdriver. (See Figure 21a.)
Step 5 Insert the screw through the screw hole in the base of the post. (See Figure 21b.)
| Caution To prevent damaging the RSP4's printed circuit board, do not overtighten the screw. |
Step 6 Position the post correctly; attach the screw and post to your RSP4. (See Figure 21c.) Carefully note the proper orientation of the protective post as shown in Figure 21c.
Step 7 Remove a new DIMM from its antistatic bag or box.
Step 8 Hold the DIMM component-side up, with the connector edge (the metal fingers) closest to you. Hold the ends of the DIMM between your thumb and forefinger. (See Figure 18.)
Step 9 Tilt the DIMM to approximately the same angle as the socket and insert the entire the connector edge into the socket. Note the two notches (keys) on the connector edge of the DIMM. (See Figure 18.) These keys are intended to assure correct orientation of the DIMM in the socket.
Step 10 Note the orientation of the socket key on the DIMM (see Figure 18 on page 55) and the DIMM socket and gently push the DIMM into the socket until the lever is flush against the side of the DIMM socket (see Figure 22), and the DIMM's edge connector is fully inserted. If necessary, rock the DIMM gently back and forth to seat it properly.
Step 11 When the DIMM is installed, check that the release lever is flush against the side of the DIMM socket. (See Figure 22.) If it is not, the DIMM might not be seated properly. If the DIMM appears misaligned, carefully remove it according to the removal procedure, and reseat it in the socket. Push the DIMM firmly back into the socket until the release lever is flush against the side of the DIMM socket.
| Caution When inserting DIMMs, use firm but not excessive pressure. If you damage a socket, you will have to return the RSP4 to the factory for repair. |
Step 12 Repeat Steps 7 through 11 for the remaining DIMM, as required for your DRAM configuration.
This completes the procedure for installing DRAM DIMMs. Proceed to the following section to check the installation.
This section provides information for checking the DIMM installation.
If the system fails to boot properly or if the console terminal displays a checksum or memory error after you have installed new DIMMs and reinstalled your RSP4, check the following:
If after several attempts the system fails to restart properly, contact a service representative for assistance. Before you call, make note of any error messages, unusual LED states, or any other indications that might help solve the problem. The time required for the system to initialize might vary with different router configurations and DRAM configurations. Routers with 256 MB of DRAM might take longer to boot than those with less DRAM.
This completes the DIMM replacement procedure. To replace the RSP4 in the router, proceed to the section "Replacing the RSP4, page 24, and then restart the system for an RSP4 installation check.
Settings for the 16-bit software configuration register are written into the NVRAM. Following are some reasons for changing the software configuration register settings:
To force the router to boot automatically from the system bootstrap software (boot image) or from its default system image in onboard Flash memory, and read any boot system commands that are stored in the configuration file in NVRAM. If the router finds no boot system commands, it uses the configuration register value to form a filename from which to boot a default system image stored on a network server. (See Table 9 on page 62.)
Table 7 lists the meaning of each of the software configuration memory bits, and Table 8, on page 61, 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 Number2 | 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 enabled1 |
| 08 | 0x0100 | Break disabled |
| 09 | 0x0200 | Use secondary bootstrap |
| 10 | 0x0400 | Internet Protocol (IP) broadcast with all zeros |
| 11 to 12 | 0x0800 to 0x1000 | Console line speed (default is 9600 baud) |
| 13 | 0x2000 | Boot default Flash software if network boot fails |
| 14 | 0x4000 | IP broadcasts do not have network numbers |
| 15 | 0x8000 | Enable diagnostic messages and ignore NVRAM contents |
| Boot Field | Meaning |
|---|---|
| 00 | Stays at the system bootstrap prompt |
| 01 | Boots the first system image in onboard Flash memory |
| 02 to 0F | Specifies a default netboot filename Enables boot system commands that override the default netboot filename |
To change the configuration register while running the system software, follow these steps:
Step 1 Enter the enable command and your password to enter privileged level, as follows:
enable
Step 2 At the privileged-level system prompt (router #), enter the configure terminal command. You are prompted, as shown in the following example:
conf t
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:
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 example following:
Step 6 Reboot the router. The new value takes effect. Configuration register changes take effect only when the system reloads, such as when you issue a reload command from the console.
The lowest four bits of the software configuration register (bits 3, 2, 1, and 0) form the boot field. (See Table 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] flashfilename
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 which are listed in the section "If You Need More Information" on page 2.
If you set the boot field value to 0x2 through 0xF and there is a valid boot system command stored in the configuration file, then the router boots the system software as directed by that value. If there is no boot system command, the router forms a default boot filename for booting from a network server. (See Table 9 for the format of these default filenames.)
In the following example, the software configuration register is set to boot the router from onboard Flash memory and to ignore Break at the next reboot of the router:
Router#conf termEnter configuration commands, one per line. End with CNTL/Z. Router(config)#config-register 0x102Router(config)#boot system flash[filename]Crtl-zRouter#
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, on page 62, lists the default boot filenames or actions for the processor.
| Action/File Name | Bit 3 | Bit 2 | Bit 1 | Bit 0 |
|---|---|---|---|---|
| Bootstrap mode | 0 | 0 | 0 | 0 |
| Default software | 0 | 0 | 0 | 1 |
| cisco2-RSP | 0 | 0 | 1 | 0 |
| cisco3-RSP | 0 | 0 | 1 | 1 |
| cisco4-RSP | 0 | 1 | 0 | 0 |
| cisco5-RSP | 0 | 1 | 0 | 1 |
| cisco6-RSP | 0 | 1 | 1 | 0 |
| cisco7-RSP | 0 | 1 | 1 | 1 |
| cisco10-RSP | 1 | 0 | 0 | 0 |
| cisco11-RSP | 1 | 0 | 0 | 1 |
| cisco12-RSP | 1 | 0 | 1 | 0 |
| cisco13-RSP | 1 | 0 | 1 | 1 |
| cisco14-RSP | 1 | 1 | 0 | 0 |
| cisco15-RSP | 1 | 1 | 0 | 1 |
| cisco16-RSP | 1 | 1 | 1 | 0 |
| cisco17-RSP | 1 | 1 | 1 | 1 |
Bit 8 controls the console Break key. Setting bit 8 (the factory default) causes the processor to ignore the console Break key. Clearing bit 8 causes the processor to interpret the Break key as a command to force the system into the bootstrap monitor, thereby halting normal operation. Regardless of the setting of the break enable bit, a break will cause a return to the ROM monitor during the first few seconds (approximately five seconds) of booting.
Bit 9 is unused. Bit 10 controls the host portion of the IP broadcast address. Setting bit 10 causes the processor to use all zeros; clearing bit 10 (the factory default) causes the processor to use all ones. Bit 10 interacts with bit 14, which controls the network and subnet portions of the broadcast address.
Table 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.
An overview of recovering a lost password follows:
To recover a lost password, follow these procedures.
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 Break is disabled, power cycle the router. (To power cycle, turn off the router, wait five seconds, and then turn it on again.) If Break is enabled on the router, press the Break key or send a break (^[) and then proceed to Step 5.
Step 5 Within five seconds of turning on the router, press the Break key. This action causes the terminal to display the bootstrap program prompt:
Step 6 Set the configuration register to ignore the configuration file information as follows:
confreg
y
y
Step 7 Initialize the router by entering the i command as follows:
i
The router will power cycle, the configuration register will be set to ignore the configuration file, and the router will boot the boot system image and prompt 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:
Step 9 Press Return. After some interface information, the prompt appears as follows:
Step 10 Enter the enable command to enter the enabled mode. The prompt changes to the following:
Step 11 Enter the show configuration EXEC command to display the enable password in the configuration file.
Step 12 Enter the configure terminal command at the EXEC prompt. You are prompted as follows:
configure terminal
Step 13 Using the config-register 0x<value> command, change the configuration register value back to its original value (noted from Step 3) or change it to a value of 0x0101 (factory default).
Step 14 Exit the configuration mode by entering Ctrl-Z.
Step 15 Reboot the router and enable it using the recovered password.
This completes the procedure for recovering from a lost password.
The Flash memory (PCMCIA) card slots on the front panel of the RSP4 are for additional PCMCIA-based Flash memory for your system. You can use this Flash memory to store and run Cisco IOS images, or as a file server for other routers to access as clients. Occasionally, it might be necessary to remove and replace Flash memory cards; however, removing Flash memory cards is not recommended after the cards are installed in the slots.
It might become necessary to replace or install a Flash memory card in your RSP4. The RSP4 has two PCMCIA slots: slot 0 (left) and slot 1 (right). (See Figure 23.) The following procedure is a generic one and can be used for a Flash memory card in either slot position.
Following is the procedure for installing and removing a Flash memory card:
Step 1 Facing the front panel of the RSP4 (as shown in Figure 23a), hold the Flash memory card with the connector end of the card toward the slot.
Step 2 Insert the card into the appropriate slot until the card completely seats in the connector at the back of the slot and the eject button pops out toward you (See Figure 23b.) Note that the card does not insert all the way inside the RSP4; a portion of the card will remain outside the slot. Do not attempt to force the card past this point.
Step 3 To eject a card, press the appropriate slot's ejector button until the card is free of the connector at the back of the slot. (See Figure 23c.)
Step 4 Remove the card from the slot and place it in an antistatic bag to protect it.
The Flash memory card that shipped with your chassis contains the Cisco IOS software image you need to boot your router. In some cases, you might need to insert a new Flash memory card and copy images or backup configuration files onto it. Before you can use a new Flash memory card, you must format it.
| Caution To prevent system problems, use Flash memory cards in the RSP4 that were formatted on an RSP1, RSP2, RSP7000, or RSP4 running Cisco IOS Release 11.1(8)CA1 or later. |
Use the following procedure to format a new Flash memory card:
Step 1 Using the procedure in the section "Replacing a Flash Memory Card" on page 67, insert the Flash memory card into slot 0. (If slot 0 is not available, use slot 1.)
Step 2 To format the Flash memory card, use the format slot0: (or format slot1:) command as follows. (Use only Intel Series 2+ Flash memory cards.)
format slot0:
MyNewCard
The new Flash memory card is now formatted and ready to use.
For complete command descriptions and configuration information, refer to the Configuration Fundamentals Command Reference and the Configuration Fundamentals Configuration Guide. Refer to the section "If You Need More Information," on page 2, for information on obtaining them.
Use the following series of commands to make the image (the file named new.image) bootable. Note that, since the configuration register must be set to 0x2102, the config-register command is part of the sequence.
config terminal
no boot system
boot system flash slot0:new.image
config-register 0x2102
Crtl-z
copy running-config startup-config
reload
When the system reloads it will boot the image new.image from the Flash memory card in slot 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 filename from which to boot, enter the configure terminal command at the enable prompt, as follows:
Router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. Router(config)#boot system flashdevice:filename
To disable Break 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 0x0102Crtl-zRouter#
Copying a new image to Flash memory might be required whenever a new image or maintenance release becomes available.
| Caution You cannot copy a new image into Flash memory while the system is running from Flash memory. |
Use the command copy tftp:filename [ bootflash: | slot0: | slot1: ]:filename for the copy procedure, where tftp:filename is the source of the file and [ bootflash: | slot0: | slot1: ]:filename is the destination in onboard Flash memory or on either of the Flash memory cards.
An example of the copy tftp:filename command follows:
Router# copy tftp:myfile1 slot0:myfile1
20575008 bytes available on device slot0, proceed? [confirm]
Address or name of remote host [1.1.1.1]?
Loading new.image from 1.1.1.1 (via Ethernet1/0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 7799951/15599616 bytes]
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
Router#
Following are additional commands related to the Flash memory on the RSP4 and the Flash memory cards. You can determine which memory media you are accessing using the pwd command, as follows:
Router# pwd
slot1
You can move between Flash memory media using the cd [bootflash | slot0 | slot1 ] command, as follows:
Router#cd slot0slot0 Router#cd slot1Router#pwdslot1
You can list the directory of Flash memory media using the dir [bootflash | slot0 | slot1 ] command, as follows:
Router# dir
-#- -length- -----date/time------ name
1 4601977 May 10 1996 09:42:19 myfile1
6 679 May 10 1996 05:43:56 todays-config
7 1 May 10 1996 09:54:53 fun1
You can delete a file from any Flash memory media using the delete command, as follows:
Router#delete slot0:fun1Router#dir-#- -length- -----date/time------ name 1 4601977 May 10 1996 09:42:19 myfile1 6 679 May 10 1996 05:43:56 todays-config
Files that are deleted are simply marked as deleted, but still occupy space in Flash memory. The squeeze command removes them permanently and pushes all other undeleted files together to eliminate spaces between them.
Following is the syntax of the squeeze command:
Router# squeeze slot0:
All deleted files will be removed, proceed? [confirm]
Squeeze operation may take a while, proceed? [confirm]
ebESZ
To prevent loss of data due to sudden power loss, the "squeezed" data is temporarily saved to another location of Flash memory, which is specially used by the system.
In the preceding command display output, the character "e" means this special location has been erased (which must be performed before any write operation). The character "b" means that the data that is about to be written to this special location has been temporarily copied. The character "E" signifies that the sector which was temporarily occupied by the data has been erased. The character "S" signifies that the data was written to its permanent location in Flash memory.
The squeeze command operation keeps a log of which of these functions has been performed so upon sudden power failure, it can return to the correct place and continue with the process. The character "Z" means this log was erased after the successful squeeze command operation.
The configuration register setting 0x0101 tells the system to boot the default image (the first image) from onboard Flash memory, but not reset the Break disable or check for a default netboot filename. The configuration register setting 0x0102 tells the system to boot from Flash memory if netboot fails, disable Break, and check for a default netboot filename. For more information on the copy tftp:filename [flash | slot0 | slot1 ]:filename command, and other related commands, refer to the set of configuration fundamentals configuration and reference publications.
With the Flash memory card formatted, you can now copy a bootable image into it. To copy an image, use the following procedure, which assumes the following:
Following is the procedure for copying a bootable file (called new.image) into the Flash memory card:
Step 1 Boot the router and allow it to initialize.
Step 2 Insert an unformatted Flash memory card and format it using the procedure in the section "Formatting a Flash Memory Card" in this document, and then proceed to Step 3.
| Caution Formatting a Flash memory card will cause existing data to be lost. |
Step 3 To enable the router, copy the image new.image to the Flash memory card, make this image in the Flash memory card (in slot 0) the default boot image, and reboot the router, use the following series of commands:
en
copy tftp:new.image slot0:new.image
config terminal
no boot system
boot system flash slot0:new.image
Crtl-z
copy running-config startup-config
reload
When the system reloads, it will boot the image new.image from the Flash memory card in slot 0.
As future releases of Cisco IOS images become available, you will receive these images either as a file booted from a network server, a file on floppy disk, or a file on a Flash memory card.
The following scenario describes how to use a newly released image on a Flash memory card, in a system that has an older image on a Flash memory card in slot 0 and a default boot image in the onboard Flash DIMM.
For this scenario, the filenames are as follows:
You will copy the new image from the new Flash memory card onto the Flash memory card that contains the old image.
Use a newly released image on a Flash memory card as follows:
Step 1 Boot the router. By default, the file image.boot will be used.
Step 2 Enable the router as follows:
en
Step 3 Insert the new Flash memory card in slot 1.
Step 4 Use the following command to copy the file image.new in slot 1 to the Flash memory card in slot 0, only if there is enough memory space for the two images to coexist. If there is not enough memory space, proceed to Step 5.
copy slot1:image.new slot0:image.new
Step 5 Use the following series of commands to designate the file image.new (which is in the Flash memory card in slot 0) as the default boot image:
config t
no boot system
boot system flash slot0:image.new
Crtl-z
copy running-config startup-config
reload
When the system reloads, it will boot the file image.new from the Flash memory card in slot 0.
Copying a configuration file to a Flash memory card in PCMCIA slot 0 or slot 1, might be required if you do not have access to a TFTP server on which you can temporarily store your configuration file. You can then copy the configuration file back to NVRAM after the boot ROM replacement procedure is complete. Use the following sections to first copy the configuration file to a Flash memory card, and then to copy the configuration from the Flash memory card back to NVRAM.
You can use the command copy startup-config [ slot0: | slot1: ]:filename for the copy procedure where startup-config is the file's source (NVRAM) and [slot0: | slot1: ]:filename is the file's destination, in either of the Flash memory cards; however, the environmental variable CONFIG_FILE must be pointing (set) to NVRAM, which is the system default.
Step 1 Use the show boot command to display the current setting for the environmental variable CONFIG_FILE as follows:
show boot
Step 2 Use the copy startup-config slot0:filename command as follows:
Router# copy startup-config slot0:myfile2
20575008 bytes available on device slot0, proceed? [confirm]
Address or name of remote host [1.1.1.1]?
Loading new.image from 1.1.1.1 (via Ethernet1/0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 7799951/15599616 bytes]
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
Router#
Step 3 To verify the file was copied correctly, use the dir command as follows:
dir slot0:
This completes the procedure for copying files between RSP4 NVRAM and a Flash memory card.
You can use the command copy running-config [ slot0: | slot1: ]:filename for the copy procedure where running-config is the file's source (the temporary configuration in DRAM) and [slot0: | slot1: ]:filename is the file's destination, in either of the Flash memory cards. An example of the copy startup-config slot0:filename command follows:
Router# copy running-config slot0:myfile2
20575008 bytes available on device slot0, proceed? [confirm]
Address or name of remote host [1.1.1.1]?
Loading new.image from 1.1.1.1 (via Ethernet1/0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 7799951/15599616 bytes]
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
Router#
To verify the file was copied correctly, use the dir command as follows:
Router# dir slot0:
-#- -length- -----date/time------ name
1 5200084 Jul 11 1996 19:24:12 rsp-jv-mz.111-4
3 1215 Jul 11 1996 20:30:52 myfile1
4 6176844 Jul 11 1996 23:04:10 rsp-jv-mz.111-472
5 1186 Jul 12 1996 16:56:50 myfile2
9197156 bytes available (11381148 bytes used)
Router#
This completes the procedure for copying a configuration from RSP4 DRAM to a Flash memory card on the RSP4.
Following is the procedure for copying your configuration file from the Flash memory card in PCMCIA slot 0 or slot 1, back to NVRAM.
Use the command copy [ slot0: | slot1: ]:filename startup-config for this copy procedure, where [slot0 | slot1 ]:filename is the source of the file (Flash memory card) and startup-config is the destination (NVRAM).
An example of the copy slot0:filename startup-config command follows:
Router# copy slot0:myfile startup-config
[ok]
Router#
To ensure that the startup configuration file, now stored in NVRAM, is the default running configuration file used by the system, issue the copy startup-config running-config command as follows:
Router# copy startup-config running-config
Router#
%SYS-5-CONFIG_I: Configured from memory by console
Router#
A locked block in Flash memory cards occurs when power is lost or a Flash memory card is unplugged during a write or erase operation. When a block of Flash memory is locked, it cannot be written to or erased, and the operation will consistently fail at a particular block location. The only way to recover from locked blocks is by reformatting the Flash memory card with the format command.
| Caution Formatting a Flash memory card will cause existing data to be lost. |
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.
|
|