Uploading the configuration/crash report, Creating alternate configuration files, Full-config backup – Enterasys Networks Security Router X-PeditionTM User Manual
Page 64
Utilizing the Command Line Interface
2-28 Managing the XSR
For more command details, refer to the XSR CLI Reference Guide.
Uploading the Configuration/Crash Report
An upload copies the XSR startup-configuration file (partial) to a system in a CLI script format
using TFTP. You can later retrieve the file with TFTP.
To perform the task correctly, the TFTP server must be running on a remote device. You then enter
the
copy startup-config tftp:
command in EXEC mode to copy
the file to the server. A successful upload produces the following sample output:
XSR#copy startup-config tftp:
Address of remote host [0.0.0.0]: 10.10.10.10
Destination file name [startup-config]:
Copy 'startup-config' from Flash to server
as 'startup-config'(y/n) ? y
Upload to server done
File size: 976 bytes
You can also upload the crash report via TFTP using the same procedure as the one used to
upload the configuration file.
Refer to the XSR CLI Reference Guide for more command details.
Full-config Backup
Alternately, you can backup and restore the full configuration file suite including encoded VPN
users, usernames, passwords, certificates, and SNMPv3 data files (
user.dat
,
cert.dat
, and
private-config
) to a remote site with a full configuration backup. This method employs a modified
backup/restore algorithm to copy the data encoded by the master encryption key to the
temporary
full-config
file then restores the data in
startup-config
and other data files. Be
aware that the same master encryption key is required for both backup (on the source XSR) and
restore (on the destination XSR) operations. Information in the
full-config
file is stored either as
ASCII text (
startup-config
data) or encrypted binary text (data files).
The
full-config
backup/restore option is also available using SNMP. Refer to
on page 2-43 for details.
Creating Alternate Configuration Files
The XSR permits you to create multiple configurations, a useful option if you want to quickly
select one of two configuration files stored in
flash:
or
cflash:
, for example:
startup-config
and
startup-configB
. The file named
startup-config
is used by the autoboot process. You can
use any file name for the alternate configuration.
To make an alternate configuration file available, rename
startup-config
to
startup-configA
(for example), and
startup-configB
to
startup-config
., using the
rename
command. Then
issue the
reload
command to use the new configuration.
Note: If you have inadvertently added errors to the CLI script file, the restoration of startup-
config will be stopped at the error line. So, any commands after that line in startup-config are
not executed.