|
|
Product Number ROMMON-RSP2=
This configuration note discusses the procedures required to replace the boot read-only memory (boot ROM) device on the Route Switch Processor (RSP2) in Cisco 7507 and Cisco 7513 routers and to initialize the high system availability (HSA) feature.
The HSA feature allows two RSP2s to be used simultaneously in a Cisco 7507 or Cisco 7513 router. One RSP2 operates as system master and the other RSP2 operates as the system slave, which takes over if the master RSP2 fails.
The boot ROM device for the RSP2 is an erasable programmable read-only memory (EPROM) device located in socket U30 on the RSP2, and is a dual in-line package (DIP).
 | Caution Changing the boot ROM device on the RSP2 makes your current configuration file stored in nonvolatile random-access memory (NVRAM) unreadable and unusable. If you do not save the system configuration file before changing the boot ROM, you must then use the configure command or the setup command facility to reenter the configuration information after the RSP2 is reinstalled. We recommend that you save the system configuration file to a Trivial File Transfer Protocol (TFTP) server or a Flash memory card before you replace the boot ROM. Refer to the "Saving and Retrieving the Configuration File" section. |
This publication provides information on the following topics:
Your router and the IOS software running on it contain extensive features and functionality. For information on IOS software and for general installation and maintenance information for your router, use the following resources:
Following is the recommended order for the procedures you need to perform to replace the boot ROM device and then initialize the HSA feature:
1. Ensure you have what you need to upgrade the boot ROM device, and then review the electrostatic discharge prevention requirements. (Refer to the "Parts and Tools Required" section, and the "Preventing Electrostatic Discharge Damage" section.)
2. Ensure that you understand all of the requirements for the boot ROM upgrade and HSA initialization. (Refer to the "Software and Hardware Prerequisites" section.)
3. Verify which Cisco IOS release is currently installed (must be Cisco IOS Release 11.1[4] or later) and the system bootstrap version currently installed on your RSP2s (must be System Bootstrap Version 11.1[2] or later). (Refer to the "Determining Your Current Cisco IOS Release and System Bootstrap Version" section.)
4. Save the configuration file on the RSP2 on which you want to install the new boot ROM (system bootstrap) version; save the configuration file to a TFTP server. (Use the appropriate procedure in the "Saving and Retrieving the Configuration File" section.) If you do not have access to a TFTP server, refer to the "Copying Files Between RSP2 NVRAM and a Flash Memory Card" section for an alternative procedure.
5. Upgrade the boot ROM device (ROMMON-RSP2=) on all RSP2s as required, and reinstall the RSP2s. (Refer to the "Upgrading the Boot ROM Device" section.)
6. Restart the router and initialize the HSA feature. (Refer to the "Restarting the System and Initializing the HSA Feature" section.)
7. Verify that the HSA feature is properly initialized. (Refer to the "Verifying that the HSA Feature Is Properly Initialized" section.)
8. Restore (retrieve) the saved configuration files from the TFTP server. (Refer to the appropriate procedure in the "Saving and Retrieving the Configuration File" section.) If you do not have access to a TFTP server, refer to the "Copying Files Between RSP2 NVRAM and a Flash Memory Card" section for an alternative procedure.
The procedures for replacing the boot ROM and initializing HSA require the following parts and tools. (Also refer to the "Software and Hardware Prerequisites" section for specific RSP2 DRAM requirements.)
Electrostatic discharge (ESD) can damage equipment and impair electrical circuitry. It occurs when electronic components are improperly handled and can result in intermittent or complete failures. Always follow ESD-prevention procedures when removing and replacing components. Ensure that the chassis is electrically connected to earth ground. Wear an ESD-preventive wrist strap, ensuring that it makes good skin contact. To channel unwanted ESD voltages safely to ground, connect the clip to an unpainted surface of the chassis frame. If no wrist strap is available, ground yourself to the metal chassis.
| Caution For safety, periodically check the resistance value of the antistatic strap. The measurement should be between 1 and 10 megohms. |
For the high system availability (HSA) feature to operate properly, the following prerequisites must be observed:
| Caution Replacing the boot ROM on your RSP2 makes your current configuration file stored in NVRAM unreadable and unusable. Before removing the RSP2 and installing the new boot ROM, you must save your configuration file to a TFTP server or a Flash memory card on your RSP2, and then retrieve it after the new boot ROM is installed. (Refer to the "Saving and Retrieving the Configuration File" section. If you do not have access to a TFTP server, refer to the "Copying Files Between RSP2 NVRAM and a Flash Memory Card" section for an alternative procedure.) |
With HSA operation, the following items are important to note:
| Caution To ensure that the slave RSP2 operates properly with the full system configuration should the master RSP2 ever fail, the slave RSP2 should have the same DRAM configuration as that of the master RSP2. |
| Caution Removing the system master RSP2 while the system is operating will cause the system to crash; however, the system will reload with the slave RSP2 as the new system master. To prevent any system problems, do not remove the system master RSP2 while the system is operating. |
The HSA feature requires Cisco IOS Release 11.1(4), or later, and System Bootstrap Version 11.1(2) or later. Your system might already be running System Bootstrap Version 11.1(2). Use the show version command to display the system bootstrap version currently running on the RSP2(s) in your Cisco 7507 or Cisco 7513.
Following is sample output of the show version command. (Take special note of the display lines preceded by angle brackets. These lines indicate the Cisco IOS release and system bootstrap version currently running on your system.)
Router> show version
Cisco Internetwork Operating System Software >> IOS (tm) GS Software (RSP-JV-M), Version 11.1(4) [biff 51096] Copyright (c) 1986-1996 by cisco Systems, Inc. Compiled Mon 22-Jan-96 21:15 by biff Image text-base: 0x600108A0, data-base: 0x607B8000 (additional displayed text omitted) >> ROM: System Bootstrap, Version 11.1(2) [biff 2], RELEASE SOFTWARE (fc1) ROM: GS Bootstrap Software (RSP-BOOT-M), Version 10.3(7), RELEASE SOFTWARE Router uptime is 85 hours, 39 minutes System restarted by reload System image file is "slot0:rsp-jv-mz.111-4", booted via slot0 cisco RSP2 (R4600) processor with 81920K bytes of memory. R4600 processor, Implementation 32, Revision 2.0
If you determine that your Cisco IOS release is not Cisco IOS Release 11.1(4) or later, you need to install the correct Cisco IOS release on the Flash memory card installed in PCMCIA slot 0. The following sections describe the procedures for copying a new Cisco IOS image to the Flash memory cards in the PCMCIA slots on your RSP2.
While there are several methods for copying Cisco IOS images from a TFTP server to a Flash memory device, the following method is recommended. Press Return after each command.
Use the following procedure to copy a Cisco IOS image to Flash memory:
Step 1 Use the cd command to change directory to the Flash memory device on which you want the new Cisco IOS image to be stored, as follows:
Step 2 Verify that the Flash device is present and was correctly selected, as follows:
Step 3 Use the dir command to verify that the Flash memory device has enough unused memory space for the new file, as follows:
Step 4 Use the copy tftp flash command to copy a Cisco IOS image from the TFTP server to the present Flash memory device, as follows:
Step 5 Use the dir command to verify that the new Cisco IOS image is now present on the Flash memory device, as follows:
Following is the procedure for configuring the system to boot from the correct Cisco IOS image stored in the Flash memory device. For HSA compatibility, this is Cisco IOS Release 11.1(4) or later. If the file from which you want to boot is the first file on the Flash memory device in slot 0, no modification is required to boot the new file; use the command boot system flash. However, if the file is not the first file listed in the Flash memory device, or is on another Flash memory device, you need to modify the configuration file to point to the Flash memory device and to the specific Cisco IOS image filename within it.
Use the following procedure to configure the system:
Step 1 Enter configuration mode and issue the boot system flash command as follows:
Step 2 Save this new configuration to NVRAM using the copy running-config startup-config (or write memory) command, as follows:
Step 3 To further verify that the system is correctly configured, use the show boot command to view the environment settings, as follows:
Step 4 Reload the new Cisco IOS image on the system by issuing the reload command.
The boot ROM device is located in socket U30 on your RSP2. (See Figure 2.) Though the RSP slots are numbered differently in the Cisco 7507 and Cisco 7513, the procedures to remove an RSP2, replace the boot ROM device, and reinstall the RSP2 are identical for each chassis. Differences between the Cisco 7507 and the Cisco 7513 are clearly noted. Upgrade both RSP2s if required.
| Caution Replacing the boot ROM on your RSP2 makes your current configuration file stored in NVRAM unreadable and unusable. Before removing the RSP2 and installing the new boot ROM, you must save your configuration file to a TFTP server or a Flash memory card on your RSP2, and then retrieve it after the new boot ROM is installed. (Refer to the "Saving and Retrieving the Configuration File" section. If you do not have access to a TFTP server, refer to the "Copying Files Between RSP2 NVRAM and a Flash Memory Card" section for an alternative procedure.) |
Use the following procedure to remove the RSP2:
Step 1 Turn OFF power to the chassis before removing an RSP2.
Step 2 Attach an ESD-preventive strap between you and an unfinished chassis surface.
Step 3 Locate the RSP2 that you want to remove for the boot ROM upgrade. The RSP2 slots in the Cisco 7507 are slots 2 and 3, and in the Cisco 7513 they are slots 6 and 7.
Step 4 Disconnect any devices that are attached to the console or auxiliary ports. You can leave the devices attached provided that doing so will not strain the cables.
Step 5 Using a screwdriver (number 2 Phillips or 3/16-inch flat-blade), loosen the two captive installation screws on the RSP2. (See Figure 3a.)
Step 6 Place your thumbs on the ends of each of the ejector levers and simultaneously pull them both outward, away from the carrier handle (in the direction shown in Figure 3c) to release the carrier from the slot and to dislodge the RSP2 from the backplane.
Step 7 Grasp the handle of the RSP2 with one hand and pull the RSP2 straight out of the slot, keeping your other hand under the carrier to guide it. Keep the carrier at a 90-degree orientation to the backplane. Avoid touching the board or any connector pins.
Step 8 Place the removed RSP2 on an antistatic mat or foam.
This completes the RSP2 removal procedure. Proceed to the section "Changing the Boot ROM."
This section provides the procedure for upgrading the boot ROM device on the RSP2.
| Caution Replacing the boot ROM on your RSP2 makes your current configuration file stored in NVRAM unreadable and unusable. Before removing the RSP2 and installing the new boot ROM, you must save your configuration file to a TFTP server or a Flash memory card on your RSP2, and then retrieve it after the new boot ROM is installed. (Refer to the "Saving and Retrieving the Configuration File" section. If you do not have access to a TFTP server, refer to the "Copying Files Between RSP2 NVRAM and a Flash Memory Card" section for an alternative procedure.) |
Use the following procedure to upgrade the boot ROM device:
Step 1 Attach an ESD-preventive strap between you and any unpainted chassis surface.
Step 2 With the RSP2 lying flat on an antistatic mat or foam, refer to Figure 4 and locate the boot ROM device, which is located at U30 along the right edge of the RSP2. Now locate this device on your RSP2.
Step 3 Carefully remove the new boot ROM from its packaging and, referring to Figure 5, verify that the new boot ROM (ROMMON-RSP2, Version 11.1[2] or later) is the correct boot ROM (system bootstrap) version for this upgrade. Return the new boot ROM to its packaging.
Step 4 Place the angled tips of the IC removal tool beneath the ends of the boot ROM. (See Figure 6.)
Step 5 Squeeze the arms of the IC removal tool and gently, but firmly, pull up on the boot ROM until its pins are clear of the socket. Apply even pressure to both tips of the IC removal tool. (See Figure 7.) It might be necessary to rock gently the IC removal tool and boot ROM end to end until the boot ROM is free of the socket.
| Caution To prevent bent pins, pull the boot ROM straight up and out of its socket. |
Step 6 Set the old boot ROM aside (preferably in an antistatic bag), and remove the new boot ROM device from its packaging.
Step 7 Align the new boot ROM with the U30 socket, and note the notch at the end of the socket and boot ROM. Match the notch at the end of the boot ROM with the notch on the socket.
| Caution If the boot ROM notch is not aligned with the socket notch, the boot ROM will be destroyed when power is turned on. |
Step 8 Applying pressure evenly, gently press the boot ROM's pins into the holes in the U30 socket. (See Figure 8.) Take care not to bend any pins. You can straighten bent pins using small needlenose pliers; however, a broken pin means that the boot ROM is unusable, and you must order a new one.
| Caution To prevent bent pins, push the boot ROM straight down into its socket, applying pressure evenly. |
Step 9 When you have inserted the new boot ROM all the way into its socket, check around the boot ROM for any bent pins.
Step 10 Repeat Steps 1 through 9 for the second RSP2 as required.
If any pins are bent, remove the boot ROM, use the needlenose pliers to straighten the pins, and reinsert the boot ROM using steps 7 through 9. Note that a broken pin means that the boot ROM is unusable, and you must order a new one.
If all pins are inserted correctly and the boot ROM notch is aligned with the socket notch, the boot ROM is properly installed. Proceed to the section "Replacing the RSP2."
The RSP2 is keyed for installation only in an RSP2 slot. By default, the system master is the RSP2 that occupies the first RSP slot in the chassis---slot 2 in the Cisco 7507 and slot 6 in the Cisco 7513. Install both RSP2s in the chassis as required.
Use the following procedure to install the RSP2:
Step 1 Attach an ESD-preventive strap between you and any unpainted chassis surface.
Step 2 Grasp the RSP2 handle with one hand and place your other hand under the carrier edge to support and guide it into the slot. Avoid touching the board or any connectors.
Step 3 Place the back of the RSP2 in the appropriate RSP slot and align the notches along the edge of the carrier with the grooves in the slot. (See Figure 3a.)
| Caution To prevent damage to the backplane, you must install the RSP2 in one of the two RSP slots on the chassis. The slots are keyed for correct installation. Forcing the RSP2 into a different slot can damage the backplane and the RSP2. |
Step 4 While keeping the RSP2 parallel to the backplane, carefully slide the carrier into the slot until the RSP2 faceplate makes contact with the ejector levers, then stop. (See Figure 3b.)
Step 5 Using the thumb and forefinger of each hand to pinch each ejector, simultaneously push both ejectors inward (toward the handle) until they are parallel to the faceplate. (See Figure 3c.)
Step 6 Use a screwdriver to tighten the two captive screws on the RSP2 faceplate (see Figure 3a) to prevent the RSP2 from becoming partially dislodged from the backplane and to ensure proper EMI shielding. (These screws must be tightened to meet EMI specifications.)
Step 7 If you disconnected the console terminal to remove the RSP2, connect the console terminal to the console port.
Step 8 Repeat Steps 1 through 6 for the second RSP2, if required.
Step 9 Ensure that the console terminal is turned on.
Step 10 Turn the system power back ON, and proceed to the next section to check the installation.
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.
Use the following procedure to verify that the RSP2 is installed and functioning properly:
Step 1 Ensure that both RSP2s are properly installed in the chassis.
Step 2 Install a Y-cable (CAB-RSP2CON); attach the combined end to your console terminal and each single end to the console connection of each RSP2.
As an alternative, you can install a separate console cable to each RSP2. The master console controls both the master and slave; you can view the slave through the master console connection, but you cannot view the master console from the slave console connection. The following steps are directed to the master RSP2 only.
Step 3 Check all RSP2 connections to make sure they are secure:
Step 4 Observe the RSP2 LEDs on system startup. While the system initializes, the yellow CPU halt LED on each RSP2 blinks when power is applied. The normal LED on the master RSP2 in slot 6 should be on and the normal LED on the slave RSP2 in slot 7 should be on. The master LED on the RSP2 in slot2 or slot 6 should be on and the slave LED on the RSP2 in slot 3 or slot 7 should be on. As each interface processor initializes, their status LEDs go on and off in irregular sequence.
Step 5 Verify that the master console terminal displays the correct system banner and startup screen as the system restarts. For a Cisco 7513, the master console display should look similar to the following (note the RSP2 slots preceded by angle brackets in this example):
For a Cisco 7507, the master console display should look similar to the following (note the RSP2 slots indicated):
Step 6 At the ROM monitor prompt, issue the sync boot ROM command to write the ROM monitor environment to NVRAM, as follows:
Step 7 Verify that the correct HSA-compatible Cisco IOS image resides in Flash memory by issuing the dir device: command, where device: can be bootflash:, slot0:, or slot1:. An example follows:
Step 8 Boot the appropriate HSA-compatible Cisco IOS subset image using the boot slot0:filename command, as follows:
The system boots up and automatically enables the HSA defaults.
Step 9 After the system boots the Cisco IOS image and initializes the interface processors (approximately 30 seconds for systems with 16 MB of DRAM, and approximately 2 minutes for systems with 64 MB of DRAM), verify that the RSP2 LEDs are in the following states:
You should see the following screen banner displayed:
Step 10 Enable EXEC command mode by using the enable command and your enable secret password.
Step 11 If you have a second RSP2 installed, use the show version command to verify that the slave RSP2 is recognized by the system. Following is a sample from a Cisco 7513. (Take special note of the line preceded by angle brackets.)
An error condition exists if no LEDS go on at power up or after initialization, or if both slave and master LEDS on an RSP2 stay on.
Step 12 The boot ROM replacement automatically changes the configuration register setting to 0x100. To operate correctly, you must change the configuration register setting to 0x102, so you can boot a Cisco IOS image from a Flash memory device (slot0: or slot1:). Change the configuration register setting using the config-register command as follows:
You can verify that the configuration register will change to 0x102 on the next router reload by viewing the last line of the output from the show version command, which appears as follows:
Step 13 Restore your saved configuration file to NVRAM. Refer to the appropriate procedure in the "Saving and Retrieving the Configuration File" section. If you saved your configuration file on a Flash memory card, refer to the "Copying a Configuration File from a Flash Memory Card to RSP2 NVRAM" section. Then proceed to the "Verifying that the HSA Feature Is Properly Initialized" section.
Amend the configuration file to boot the HSA-compatible Cisco IOS image on the slave RSP2 by copying the HSA-compatible Cisco IOS image to the Flash memory device on the slave RSP2. (The Flash memory device can be bootflash:, slot0:, or slot1:, but slot0: is used in the following examples.)
Proceed as follows:
Step 1 Verify whether or not the HSA-compatible Cisco IOS image file exists on the slave's Flash memory card in PCMCIA slot 0 using the dir slaveslot0: command as follows:
If the file does not exist and you do not have enough space available on the slave's Flash memory card, delete a file, using the delete command, then remove the file marked for deletion using the squeeze command as follows. (For descriptions of the delete and squeeze commands, and other Flash memory commands, refer to the "Additional Flash Memory Commands" section.)
If the file does exist, but is not the first file listed in the Flash memory card in PCMCIA slot 0, modify the configuration using the boot system flash device:filename command to specify the file from which to boot the system.
If your slave RSP2 (in slot 7 or slot 3) has the HSA-compatible Cisco IOS image file in the Flash memory card in PCMCIA slot 1, and the master RSP2 (in slot 6 or slot 2) has this file in the Flash memory card in PCMCIA slot 0, you need to modify the configuration using the boot system flash slot0:filename and boot system flash slot1:filename commands.
Step 2 You must now copy the HSA-compatible Cisco IOS image file to the slave's Flash memory card in slot 0 using the copy slot0:filename slaveslot0: command as follows:
Step 3 When the copy process is complete, use the dir slavedevice: command to verify it is in the slave's Flash memory card in PCMCIA slot 0, as follows:
Following is the procedure for verifying HSA initialization. Verify that the HSA feature is properly initialized using the show version and show boot commands. An example from a Cisco 7513 follows. (Take special note of the lines preceded by angle brackets.)
Router# show version
Cisco Internetwork Operating System Software >> IOS (tm) GS Software (RSP-JV-M), Version 11.1(4), RELEASE SOFTWARE (fc1) Copyright (c) 1986-1996 by cisco Systems, Inc. Compiled Mon 17-Jun-96 16:14 by biff Image text-base: 0x600108A0, data-base: 0x60864000 >> ROM: System Bootstrap, Version 11.1(2) [biff 2], RELEASE SOFTWARE (fc1) Router uptime is 12 minutes System restarted by reload System image file is "slot0:rsp-jv-mz.111-4", booted via cisco RSP2 (R4600) processor with 81920K bytes of memory. R4600 processor, Implementation 32, Revision 2.0 Last reset from power-on G.703/E1 software, Version 1.0. SuperLAT software copyright 1990 by Meridian Technology Corp). Bridging software. X.25 software, Version 2.0, NET2, BFE and GOSIP compliant. TN3270 Emulation software (copyright 1994 by TGV Inc). Chassis Interface. 1 EIP controller (6 Ethernet). 1 FSIP controller (4 Serial). PSFAIL: Power supply1 TRIP controller (4 Token Ring). 6 Ethernet/IEEE 802.3 interfaces. 4 Token Ring/IEEE 802.5 interfaces. 4 Serial network interfaces. 123K bytes of non-volatile configuration memory. 20480K bytes of Flash PCMCIA card at slot 0 (Sector size 128K). 8192K bytes of Flash internal SIMM (Sector size 256K). >> Slave in slot 7 is running Cisco Internetwork Operating System Software >> IOS (tm) GS Software (RSP-DW-M), Version 11.1(4), RELEASE SOFTWARE (fc1) Copyright (c) 1986-1996 by cisco Systems, Inc. Compiled Mon 17-Jun-96 16:15 by biff Loaded from system Configuration register is 0x100 (will be 0x102 at next reload)
Issue the show boot command. An example from a Cisco 7513 follows. (Take special note of the line preceded by angle brackets.)
Router# sh boot
BOOT variable = CONFIG_FILE variable = Current CONFIG_FILE variable = BOOTLDR variable does not exist Configuration register is 0x100 (will be 0x102 at next reload) Slave auto-sync config mode is on >> Current slave is in slot 7. slave BOOT variable = slave CONFIG_FILE variable = slave BOOTLDR variable = slave Configuration register is 0x102 Router#
The HSA feature is now initialized. Refer to the "Reference Information" section for information on specific HSA configuration documentation.
If you need additional troubleshooting information for your Cisco 7507 or Cisco 7513, refer to the Cisco 7507 Hardware Installation and Maintenance or Cisco 7513 Hardware Installation and Maintenance publications.
If you need to configure the HSA feature for your RSP2, refer to the following publications:
All publications are available on the Cisco Connection Documentation, Enterprise Series CD-ROM, Cisco's online library of product information, or as printed copies.
The following sections include information on saving a configuration file to a server, retrieving the configuration file from a TFTP server, copying configuration files between your RSP2 NVRAM and a Flash memory card, and contacting Cisco Systems for additional information or assistance.
This section describes the procedures for saving (copying) and retrieving the system configuration using a Trivial File Transfer Protocol (TFTP) server.
Configuration information resides in two places when the router is operating: the default startup (permanent) configuration in NVRAM and the running (temporary) configuration in DRAM. The startup configuration always remains available; NVRAM retains the information even when the power is shut down.
The running configuration is lost if the system power is shut down. The startup configuration (in NVRAM) contains all nondefault configuration information that you added with the configure command, the setup command facility, or by editing the configuration file.
The copy running-config startup-config command saves the running configuration to the startup configuration file in NVRAM, so that it will also be saved when power is shut down. Whenever you make changes to the system configuration file, issue the copy running-config startup-config command to ensure that the new configuration information is saved.
Save the configuration file to a remote server before removing the RSP2. You can retrieve it later and write it back into NVRAM. 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 reinstall the RSP2. 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, use the following procedure to enter the privileged level:
Step 1 At the EXEC prompt (>), enter the enable command. The EXEC command interpreter prompts you for a privileged-level password, as follows:
Step 2 Enter the password (the password is case sensitive). For security purposes, the password is not displayed.
Step 3 When you enter the correct password, the system displays the privileged-level system prompt (#) as follows:
The pound sign (#) at the system prompt indicates that you are at the privileged level of the EXEC command interpreter; you can now execute the EXEC-level commands that are described in the following sections.
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 interface processor as the protocol, are enabled when you enter a host name or address on the same line as the ping command. For a description of the configurable options, refer to the appropriate software documentation.
The following example shows a successful ping 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 Router#
The following example shows 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 the running configuration to the TFTP file server, ensure the following:
To store information on a remote host, enter the copy startup-config tftp privileged EXEC command. The command prompts you for the destination host's address and a filename, then displays the instructions for confirmation. When you confirm the instructions, the router sends a copy of the currently running configuration to the remote host. The system default is to store the configuration in a file called by the name of the router with -confg appended. You can either accept the default filename by pressing Return at the prompt, or enter a different name before pressing Return.
Use the following procedure to copy the currently running configuration to a remote host:
Step 1 The system prompt should display a pound sign (#) to indicate the privileged level of the EXEC command interpreter. If it does not, follow the steps in the "Using the EXEC Command Interpreter" section to enable the privileged level.
Step 2 Use the ping command to check the connection between the router and the remote host. (See the previous section, "Using the ping Command to Verify Server Connectivity.")
Step 3 Issue the show running-config (or write term) command to display the currently running configuration on the terminal, and ensure that the configuration information is complete and correct. If it is not, use the configure command to add or modify the existing configuration. (Refer to the appropriate software documentation for descriptions of the configuration options available for the system and individual interfaces, and for specific configuration instructions.)
Step 4 Create a file on the TFTP server.
Step 5 Issue the copy startup-config tftp command. The EXEC command interpreter prompts you for the name or interface processor address of the remote host that is to receive the configuration file. (The prompt might include the name or address of a default file server.)
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:
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 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), then your configuration was not saved.
Repeat the preceding steps, or select a different remote file server and repeat the preceding steps.
Step 10 To further ensure that the configuration file was copied correctly, issue the show startup-config command and look at the first line for the configuration file's size. Match it with the file you copied to the TFTP server. Following is an example. (Take special note the line preceded by angle brackets.)
After you copy the configuration file, proceed to the "Upgrading the Boot ROM Device" section. Then proceed to the next section "Retrieving the Configuration File," after you have replaced the boot ROM and reinstalled the RSP2. If you are unable to copy the configuration file to a remote host successfully, contact your network administrator or refer to the end of this document for instructions on contacting technical assistance.
After you reinstall the RSP2, you can retrieve the saved configuration and copy it back to NVRAM. To retrieve the configuration, enter configuration mode and specify that you will configure the router from the network. The system prompts you for a host name and address, the name of the configuration file stored on the host, and confirmation to reboot using the remote file.
Use the following procedure to retrieve the currently running configuration from a remote host:
Step 1 On the console terminal, the system prompt should display a pound sign (#) to indicate the privileged level of the EXEC command interpreter. If it does not, follow the steps in the "Using the EXEC Command Interpreter" section, to enable the privileged level.
Step 2 Configure an interface port on the router for a connection to a remote host (TFTP server).
Step 3 Use the ping command to verify the connection between the router and the remote host. (See the "Using the ping Command to Verify Server Connectivity" section.)
Step 4 At the system prompt, issue the copy tftp startup-config command and press Return to enter the configuration mode and specify that you will configure the system from a network device (instead of from the console terminal, which is the default).
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).
Step 6 The system prompts you to select a host or network configuration file. The default is host; press Return to accept the default.
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 appears:
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:
Step 11 To ensure that the startup configuration file stored in NVRAM is the default running configuration file used by the system, issue the copy startup-config running-config command as follows:
This completes the procedure for retrieving the saved configuration file.
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.
Use the show boot command to display the current setting for the environmental variable CONFIG_FILE as follows:
Router# show boot
(display text omitted) CONFIG_FILE variable = Current CONFIG_FILE variable = (display text omitted)
Use the following procedure to copy a configuration file from RSP2 NVRAM to a Flash memory card:
Step 1 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 2 To verify the file was copied correctly, use the dir command as follows:
After you copy your configuration file to a Flash memory card and have verified that it was copied correctly, proceed to the "Upgrading the Boot ROM Device" section. When you have finished replacing the boot ROM and reinstalling the RSP2, refer to the next section, "Copying a Configuration File from a Flash Memory Card to RSP2 NVRAM."
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#
After you copy your configuration file, proceed to the "Upgrading the Boot ROM Device" section. When you have finished replacing the boot ROM and reinstalling the RSP2, refer to the next section, "Copying a Configuration File from a Flash Memory Card to RSP2 NVRAM."
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#
Following are additional commands related to the Flash memory in the single in-line memory module (SIMM) on the RSP2 (called bootflash) and in PCMCIA-based Flash memory cards. (The following example assumes you are currently in PCMCIA slot 0.) You can determine which PCMCIA slot you are accessing using the pwd command as follows:
Router# pwd
slot0
You can move between Flash memory media using the cd [ bootflash: | slot0: | slot1: ] command as follows:
Router# cd slot1
slot1 Router# cd slot0
Router# pwd
slot1
You can list the directory of any Flash memory media using the dir [ bootflash: | slot0: | slot1: ] command as follows:
Router# dir
-#- -length- -----date/time------ name 1 1 Jul 12 1996 09:54:53 fun1
You can delete a file from any Flash memory media using the delete command as follows:
Router# delete slot0:fun1
Router# dir
-#- -length- -----date/time------ name
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 that 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 come back to the right place and continue with the process. The character "Z" means this log was erased after the successful squeeze command operation.
A locked block of Flash memory 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.
|
|