Zoning Brocade switches: Putting it all together

I wanted to conclude my Brocade zoning posts by discussing a couple of best practices. Two issues I have seen in the real world are inconsistent and non-descriptive names, and a lack of configuration backups. Using descriptive names such as “Fabric1Switch1Port8″ or “AppServer1Port1″ makes the output quite a bit more readable, which is extremely helpful when you are trying to gauge the impact of a faulty initiator or SFP at 3am.

Backing up the configuration on a switch is super easy to do, and there are a number of tools available to automate this process (I have written pexpect scripts to do this). To perform a manual backup of a switch configuration, you can run the “configupload” utility:

Fabric1Switch1:admin> configupload
Server Name or IP Address [host]:
User Name [user]: matty
File Name [config.txt]: switch1config.txt
Protocol (RSHD or FTP) [rshd]: ftp
upload complete

This will prompt you for the IP of a server to write the configs to, as well as the name of the file to write the configuration to. I have thoroughly enjoyed working with Brocade switches over the past few years, and really enjoy the simplicity and power that they provide in their CLI. Nice!


Alex  on July 10th, 2009

By the way it may be a good idea to put in place a cron that logs into the Brocade switch and runs the configupload command on a regular basis. I’ve done this using Perl and expect and it works great. I backup switches weekly to a ftp server where it gets picked up by the enterprise backup solution.

iqbal  on August 3rd, 2010

Hi, Alex,

Can you upload that peal script.


kerkael  on December 30th, 2011


The simplest way I found is to pass successive commands as echo in a pipe :

With ssh, you’ll us interactive login by entering the password on demand
bash-3.00# { sleep 2; echo “zoneshow”; sleep 2;}|ssh admin@

With telnet, username and password are clear in the { }
bash-3.00# { sleep 2; echo admin; sleep 2; echo “password”;sleep 2; echo “zoneshow”;sleep 1;}|telnet

In both case, don’t forget a sleep as the last command in { } to be sure you’ll get the last display before being logged out.

Depending on the time the previous command takes, you may increase the last sleep to several seconds.

Leave a Comment