67
OL-4923-01 B0
If you replace the RSP2 in a system with only one RSP2, you also replace the entire configuration, which
resides in NVRAM on the RSP2. If you copy the configuration file to a remote server before removing
the RSP2, you can retrieve it later and write it into NVRAM on the new RSP2. You can also use the copy
running-config slot0:config-file command to save the configuration file to Flash memory, and then use
the copy slot0:config-file nvram:startup-config command to restore it.
If you do not copy the configuration file, you must use the configure command or the setup command
facility to re-enter the configuration information after you install the new RSP2. For complete
descriptions of these two commands, and instructions for using them, refer to the appropriate software
documentation.
If you are temporarily removing an RSP2, it is not necessary to copy the configuration file to a remote
server; the lithium batteries retain the configuration file in memory until you replace the RSP2 in the
system. This procedure requires privileged-level access to the EXEC command interpreter, which
usually requires a password. See the
“Using the EXEC Command Interpreter” section on page 22
and
contact your system administrator to obtain access, if necessary.
For configuration information and support, refer to the Cisco IOS software configuration documentation
set that corresponds to the software release installed on your Cisco hardware.
Using the ping Command to Ensure Connectivity
Before you attempt to copy or retrieve a file from a remote host, ensure that the connection is good
between the router and the remote server by using the packet internet groper (ping) program. The ping
program sends a series of echo request packets to the remote device and waits for a reply. If the
connection is good, the remote device echoes them back to the local device.
The console terminal displays the results of each message sent: an exclamation point (!) indicates that
the local device received an echo, and a period (.) indicates that the server timed out while awaiting the
reply. If the connection between the two devices is good, the system displays a series of exclamation
points (! ! !) or [ok]. If the connection fails, the system displays a series of periods (. . .) or [timed out]
or [failed].
To verify the connection between the router and a remote host, enter the ping command followed by the
name or Internet Protocol (IP) address of the remote server; then press Return. Although the ping
command supports configurable options, the defaults, including IP as the protocol, are enabled when you
enter a host name or address on the same line as the ping command. For a description of the configurable
options, refer to the appropriate software documentation.
The following example shows a successful ping operation:
Router# ping 10.1.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/12/12 ms
The following example shows the results of a failed ping operation:
Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Router#
If the connection fails, check the physical connection to the remote file server and verify that you are
using the correct address or name, and then ping the server again. If you are unable to establish a good
connection, contact your network administrator or
“Obtaining Technical Assistance” section on page 86
for instructions on contacting technical assistance.
