Operation Manual

File Management Commands
Mobility System Software Command Reference Guide
Version 7.3
21 – 494
● show version on page 500
restore
Unzips a system archive created by the backup command and copies the files from the archive
onto the switch.
Syntax restore system [tftp:/ip-addr/]filename [all | critical] [force]
Defaults The default is critical.
Access Enabled.
History Introduced in MSS Version 3.2.
Usage If a file in the archive has a counterpart on the switch, the archive version of the file
replaces the file on the MX. The restore command does not delete files that do not have
counterparts in the archive. For example, the command does not completely replace the user files
area. Instead, files in the archive are added to the user files area. A file in the user area is
replaced only if the archive contains a file with the same name.
The backup command stores the MAC address of the switch in the archive. By default, the
restore command works only if the MAC address in the archive matches the MAC address of the
switch where the restore command is entered. The force option overrides this restriction and
allows you to unpack an archive from one MX onto another MX.
If the configuration running on the MX is different from the one in the archive or you renamed the
configuration file, and you want to retain changes made after the archive was created, see the
“Managing System Files” chapter of the Trapeze Mobility System Software Configuration Guide.
Examples The following command restores system-critical files on a MX from archive sysa_bak:
MX# restore system tftp:/10.10.20.9/sysa_bak
success: received 11908 bytes in 0.150 seconds [ 79386 bytes/sec]
[tftp:/ip-addr/]filename Name of the archive file to load. The archive can be located in the MX
nonvolatile storage or on a TFTP server.
all Restores system files and the user files from the archive.
critical Restores system files only, including the configuration file used when
booting, and certificate files.
force Replaces files on the MX with those in the archive, even if the MX is not
the same as the one from which the archive was created.
CAUTION! Do not use this option unless advised to do so by Trapeze
Networks TAC. If you restore MX system files from one MX onto another
MX, you must generate new key pairs and certificates on the MX.
Note:
If the archive’s files cannot fit on the MX, the restore operation fails. Trapeze
Networks recommends deleting unneeded image files before creating or
restoring an archive.
!
Caution
Do not use the force option unless you are certain you want to replace the
MX files with files from another MX. If you restore one MX system files onto
another MX, you must generate new key pairs and certificates on the MX.