Reference Guide

∙ iSCSI
∙ CryptoDev
∙ FICU saved files
∙ VS_SW_CONF
∙ MAPS configuration
∙ Banner
Configuration file backup
Brocade recommends keeping a backup configuration file. You should keep individual backup files for all switches in the fabric and avoid
copying configurations from one switch to another. The configUpload command, by default, only uploads the switch context
configuration for the logical switch context in which the command is executed.
In non-Virtual Fabric mode, you must use the configUpload -all command to include both the switch and the chassis information. In
Virtual Fabric mode, the configUpload -all command can be selected to upload all logical switches and the chassis configuration. Only
administrators with chassis permissions are allowed to upload other FIDs or the chassis configuration.
The following information is notsaved in a backup:
∙ dnsConfig command information
∙ Passwords
Before you upload a configuration file, verify that you can reach the FTP server from the switch. Using a Telnet connection, save a
backup copy of the configuration file from a logical switch to a host computer.
Secure File Transfer Protocol (SFTP) is now an option when uploading a configuration file. SFTP is analogous to Secure Copy Protocol
(SCP). SFTP can be used for the configupload , configdownload , supportsave , and auto FFDC/trace upload (supportftp ) commands.
NOTE
If you download a configuration file which was uploaded from a switch whose default FID (128) was changed, then you should
download the VF configuration file first before you download the normal configuration file to ensure that all the logical switches
are same in both switches. Hence, follow these steps:
1. Run the configUpload -vf command from the old setup.
2. Run the configUpload -all command from the old setup.
3. Run the configDownload -vf command in the new setup.
4. Run the configDownload -all command in the new setup.
Considerations for FTP server credentials with special characters
FTP server credentials may include special characters that need to be handled in specified manner on the Command Line Interface
(CLI).
Special characters also referred to as meta-characters, are members of an exempt set of characters, which when used in command line
mode are evaluated as characters with non-literal meaning. These characters are designated to carry out a special instruction, or have an
alternate meaning.
NOTE
This list is not exhaustive and alternate meaning for some characters is contextual. For more information, refer to any Linux
scripting information available for general use on the internet.
Maintaining the Switch Configuration File
Brocade Fabric OS Administration Guide, 8.0.1
53-1004111-02 259