How to start using the program?

Everything is simple. For the beginning, download archives of program that contains the script itself, as well as the necessary configuration files and directories - sites.google.com/site/san4fan/project - fbr.tar.gz. And deploy to your UNIX server from which you have SSH access to the switches.
And unpack: tar xvf fbr.tar.gz

Now you have folder ops with the following structure:

OBJ

conf

tmp

util

txt_get_zone_brc.sh

txt_get_zone_cis.sh

txt_get_zones.sh

File txt_get_zones.sh is actually a script, txt_get_zone_brc.sh and txt_get_zone_cis.sh complements for working with Brocade and Cisco devices, respectively.

The folder tmp - here all is clear, as the name, is used to store temporary files.

The folder conf - contains the following configuration files:
fabric - includes the type and name of your fabrics, as well as switch to communicate with them:

#Cisco

<SW_Type>#<FBR_Name>#<SW_Name>#<VSAN>

#Brocade

<SW_Type>#<FBR_Name>#<SW_Name>#

for example:

CIS#PROD1#switch-1#1    -   That is, Cisco fabric with the name PROD1available through the switch-1 switch for VSAN 1

BRC#TEST1#switch-2#     -    That is Brocade fabric named TEST1 is available through the switch-2 switch

I will note, that if you use multiple Cisco VSAN-s then you have to do it for each row, it makes possible to distinguish between the VSAN-s and the script will not allow to construct zone between objects in different VSANs.

auth - contains the data for access to all elements of controlled by, if the object library (see below), you'll create manually - just enough to specify the information to access the switches.
contains:

##Switches

#SW#<FBR_Name>#<SW_Name1,SW_Name2...>#<User>#<Key_file>#<Password>

for example:
SW # PROD1 # switch-1, switch-2 # admin # / root / .ssh / .id_key # -Switches switch-1 and 2 are available from the current server for admin user with SSH key stored in /root/.ssh/.id_key

##Storage

#ST#<ST_Type>#<Storage_Name>#<Connection_string>#                 -   Connection_string allowed in quite complicated expressions, but more onthat later.
for example:  

ST # NETAPP # netapp1a # rsh # - Specifies the access to Netapp netapp1a via rsh protocol for the current user
ST # CLAR # 10.127.0.5 #-password password -scope 0 -user admin #    -  Specifies the access to the Clariion (EMC) for the admin user and password password.

##Servers

#SR#<SRV_Type>#<SR_Name1,SR_Name2...>#<User>#<Key_file>#<Password>

SR#HPBC#hpbc01,hpbc02p#Administrator#/root/.ssh/.id_key#                 -  Defines access to the HP Blade System for Administrator user with SSHkey stored in /root/.ssh/.id_key file.

serv - contains a list of all servers (or blade system as in my case)

##Servers

#<SRV_Type>#<FBR_Name>_<FBR_Type>#<System_Name>#<HBA_N{1|2}>

HPBC#PROD1_BRC#hpbc02p#1                                                            -  The system type HPBC (HP Blade Center) named hpbc02p connected to a fabric PROD1 - Brocade type through HBA 1. The last field is important for cases when the server is connected to the two redundant fabrics.

stor - contains a list of storages

##<ST_Type>#<ST_Alias>#<ST_Name>   

##Netapp

#NETAPP#N1A#netapp1a

##VNX & Clariion

#VNX#VNX7500#10.10.0.5

#CLAR#CLAR960#clariion1

#VMAX

#VMAX#VMAX282#000292600111                                                       -  Since the VMAX is controlled via FC and not on the network as the parameter used SID  

#Hitachi

#HIT#HIT_2#hitachi2

Folder OBJ - will contain a library of all objects (ports of servers and storages) presented in each managed fabric.
Its structure is:

./OBJ/<FBR>_<SW_TP>/stor/<ST_Name>

./OBJ/<FBR>_<SW_TP>/serv/<SR_GR_Name>

where:
<FBR> - The name of the fabric (eng. case sensitive), eg PROD1
<SW_TP> - type of fabric BRC for Brocade or CIS for Cisco, respectively (other types of switches are not supported)
<ST_Name> - The name of the storage in a convenient to build a zone name format (eng. case sensitive), eg VMAX111
<SR_GR_Name> - The name of the server group (eng. case sensitive),eg HPBS - HP Blade System.

a result we get something like:

./OBJ/PROD1_CIS/stor/VMAX111

./OBJ/TEST2_BRC/serv/HPBC

Files <SR_GR_Name> and <ST_Name> and have the following format:
<SR_GR_Name>
<Server_name> _ # _ <WWN> - Such 

serv1_ # _50:01:43:80:04:BC:1A:1C or serv2.dom.com_ # _50:01:43:80:08:BC:1B:1D

<ST_Name>

<PORT>  <PWWN> - for example (for VMAX) 8G:0 50:00:09:74:08:A3:17:8C or  (for Netapp) 0A 50:0A:09:82:6F:3D:7B:F7

The server name and port you can use later as a parameters of the scripts fabric's control. To create these files, there are two ways: manually - using the information available from your systems, or through a set of utilities. On both of these methods will be discussed later.