Step-by-step guide for Backing up and Restoring Brocade Switch Configuration.

Config_upload_Download
  1. Log in to the switch:
    • Use SSH or the console to access the switch:
      • ssh admin@<switch-IP>
  2. Backup the configuration:
    • Use the configupload command to upload the config to an FTP server:
      • configupload
      • Select the protocol: Choose FTP/SFTP/SCP.
      • Provide the FTP/SFTP/SCP server details:
        • Host IP
        • Path (where the config file will be stored)
        • Username and Password

    • Examples
      • To upload the switch configuration interactively from a switch that is not enabled for Virtual Fabrics:
          • switch:admin> configupload
          • Protocol (scp, ftp, sftp, local) [ftp]: sftp
          • Server Name or IP Address [host]: xxx.xx.xxx.xxx
          • User Name [user]: user
          • File Name [<home dir>/config.txt]:  /remote_dir/file_name.txt
          • Section (all|chassis|switch [all]):
          • Password: ******
        • configUpload complete: All config parameters are uploaded
  3. Verify backup:
    • Confirm that the config file is successfully uploaded to your FTP server.
  1. Ensure minimal activity:
    • Since restore is disruptive, schedule this during a maintenance window.
  2. Restore using configdownload:
    • configdownload
      • Protocol: FTP/SFTP/SCP
      • Server details: IP, path, and credentials
      • Confirm overwrite when prompted
    • Examples:
      • To download the switch configuration file interactively to the current logical switch from a local directory (no chassis permissions):
          • switch:admin> configdownload
          • Protocol (scp, ftp, sftp, local) [ftp]: sftp
          • Server Name or IP Address [host]: xxx.xxx.xxx.xxx
          • User Name [user]: admin
          • Path/Filename [<home dir>/config.txt]:/remote_dir/file_name.txt
          • Section (all|chassis|FID# [all]):
        •  *** CAUTION ***
          • This command is used to download a backed-up configuration
          • for a specific switch. If using a file from a different
          • switch, this file’s configuration settings will override
          • any current switch settings. Downloading a configuration
          • file, which was uploaded from a different type of switch,
          • may cause the switch to fail.
          • A switch reboot is required for the changes to take effect.
          • Please make sure all the switches are disabled by
          • using chassisdisable command. Downloading configuration
          • to an online switch may result in some configuration not
          • being downloaded to that switch.
          • configDownload operation may take several minutes
          • to complete for large files.
          • Do you want to continue [y/n]: y
          • Password: *******
          • Activating configDownload: Switch is disabled
          • configDownload complete: All config parameters are downloaded
  3. Reboot the switch if needed:

    Some configurations might require a switch reboot:

    1. To reboot a standalone switch with a single CP:
          • switch:admin> reboot                                                  
          • Warning: This command would cause the switch to reboot
          • and result in traffic disruption.
          • Are you sure you want to reboot the switch [y/n]? y                        
          • Rebooting!…….
          • The system is going down for reboot NOW !!
    1. To reboot a CP when HA is enabled:
          • switch:admin> reboot                                                  
          • Warning: This command is being run on a control processor (CP)
          • based system and will cause the active CP to reboot.
          • Are you sure you want to reboot the active CP [y/n]? y                  
          • Rebooting!……
          • The system is going down for reboot NOW !!
    1. To reboot a CP when haFailoveris disabled:
          • switch:admin> reboot                                                  
          •  This command is being run on a control processor (CP)
          •  based system. Because HA is disabled, it will cause both
          •  active CP and the standby CP to reboot. After reboot, the
          •  HA will be enabled.
          •  Do you want to continue [y/n] y
          • Rebooting!  …….
          •  The system is going down for reboot NOW !!
    1. To perform Ha reboot in the switch-based systems:
          • switch:admin> hareboot                                                             
          • HA Rebooting …
    1. To perform Ha reboot in the chassis-based systems:
          • switch:admin> hareboot                                     
          • Restarting system with command ‘Machine Rebooting
  • Backup is non-disruptive — it won’t affect switch operations.
  • Restore is disruptive — might cause a brief outage.
  • FTP server is mandatory for backups — local backups on the switch aren’t supported.
  • Always verify the integrity of your backups before upgrading firmware.
Scroll to Top