Summary of Tasks
The following summary describes only the CLI involved to transfer the
configuration and load it on the switch; it is assumed that you know how to modify the
configuration file with a text editor. As previously described, to use these commands, use
the .xsf file extension, as these steps are not applicable to configurations that use the
.cfg file extension.
To work with an ASCII-formatted configuration file, complete the
following tasks:
-
Upload the configuration to a network TFTP server
using the following command:
upload configuration [hostname | ipaddress] filename {vr
vr-name} {block-size
block_size}
After the configuration file is on the TFTP
server, use a text editor to enter the desired changes, and rename the file if necessary
so it has the .xsf extension.
-
Download the configuration from the TFTP server
to the switch using one of the tftp and
tftp get commands.
-
Verify the configuration file is on the switch
using the ls
command
-
Load and restore the new configuration file on the switch
using the following command:
load script filename {arg1} {arg2} ... {arg9}
-
Save the configuration to the configuration database
so the switch can reapply the configuration after switch reboot
using the following command:
save configuration {primary | secondary | existing-config | new-config}
When you save the configuration file, the switch
automatically adds the .cfg file extension to the filename. This saves the ASCII
configuration as an XML-based configuration file.
Note
Configuration files are forward compatible only and not backward compatible.
That is, configuration files created in a newer release, such as ExtremeXOS 15.5, might
contain commands that do not work properly in an older release, such as ExtremeXOS
15.3.
Print
this page
Email this topic
Feedback
View PDF
Download EPUB