Brocade config backup and supportsave commands

 Before doing any kind of changes to a Brocade FC switch it’s a good idea to backup its config first. We backup Brocade switches using the configupload command.

Prerequisites – The switches need an FTP server to backup to.  You will need to know the IP address of the FTP server and a user account with access to proceed.

1 Establish a putty session to the switch and login as normal

2 Enter the command

configupload

3 At the protocol selection prompt choose the protocol appropriate for you FTP server. Press enter to select the default FTP

Protocol (scp, ftp, sftp, local) [ftp]

4 At the IP Address prompt enter the IP address of the FTP server

Server Name or IP Address [host]: 10.10.10.5

5 User Name, enter a user with access

User Name [user]

6 Path/filename, press enter to accept the home directory or enter path

Path/Filename [<home dir>/config.txt]:

7 Section, press enter to select all components or enter the element to backup

Section (all|chassis|switch [all]):

8 Go to your FTP server and you should see a file called config.txt.  Rename this to something logical like the switch name and date

Below is an example of all the steps completed

FCSWITCH01:admin> configupload
Protocol (scp, ftp, sftp, local) [ftp]:
Server Name or IP Address [host]: 10.10.10.5
User Name [user]: anonymous
Path/Filename [<home dir>/config.txt]:
Section (all|chassis|switch [all]):

Use the “supportsave” CLI command. Be aware: This needs an FTP server to be configured and running on a management workstation reachable by the switch!
Example:
 
Supportsave
 
This command will collect RASLOG, TRACE, supportShow, core file, FFDC data and other support information and then transfer them to a FTP/SCP server or a USB device. This operation can take several minutes.
..
..
OK to proceed? (yes, y, no, n): [no] y
Host IP or Host Name: xxx.xxx.xxx.xxx
User Name: YYYY
Password:
Protocol (ftp or scp):
 
Your FTP server will receive multiple files. Please compress them and give the resulting archive file a meaningful name. For example:
TicketNumber_SwitchName_Date_Description.zip