09-10-2017 04:42 AM
Need your support to get understand the merging of multiple Brocade SAN switch in different SAN switch.
In our environment we 2 data center.
Each Datacenter has 2 Core switch and 2 HP C7000 Enclosure and 1 Storage
Each C7000 enclosure aslo has 2 SAN switch and 16 Balde serevr.
Each blader switch is connected with Core switch in each data center with trunking.
Also two Data Center also connected each other with ISL trunking.
Now from where I can start zoning, It would be helpful if you share the steps.
I am also attaching the logical diagram of our environment for better understanding.
09-10-2017 05:39 AM
09-10-2017 05:56 AM
Thank your for your response.
In each blade we have ""Brocade 8/16Gb FC Switch (T5517A)
Data Center switch "" Brocade 16Gb/16c Embedded SAN Switch (C8S45A)
We are going to use Dark Fiber between site.
Yes we have to merge febric.
09-14-2017 03:35 PM
There are several conditions which will not allow two fabrics(single switches, or multiple switch fabrics) to merge when connected with a native fiber cable(ISL). It's unlikely that you have changed any of the fabric parameters, but that will stop a fabric from merging together.
Most common are differences in the zone configuration between the two fabrics. One fabric will have the zone info for its devices, and the other fabric will have zone info for its devices. When you try to merge two fabrics, there are two basic scenarios where you can setup the zoning so that the fabrics will merge.
The general rule is that the Effective and Defined zone entries must match EXACTLY. Including the size of all the entries in the zone databases, and the order of the members in the zone.
Here is an abstract of the process from the SAN admin guide for FOS 7.4.x, with the relevant steps for checking a zone conflict in bold near the bottom.
When a new switch is added to the fabric, it automatically takes on the zone configuration information from the fabric. You can verify the zone configuration on the switch using the procedure described in Viewing the configuration in the effective zone database.
If you are adding a switch that is already configured for zoning, clear the zone configuration on that switch before connecting it to the zoned fabric. Refer to Clearing all zone configurations for instructions.
Adding a new fabric that has no zone configuration information to an existing fabric is very similar to adding a new switch. All switches in the new fabric inherit the zone configuration data. If the existing fabric has an effective zone configuration, then the same configuration becomes the effective configuration for the new switches.
Before the new fabric can merge successfully, it must pass the following criteria:
The fabric is checked for segmentation during power-up, when a switch is disabled or enabled, or when a new switch is added.
The zone configuration database is stored in nonvolatile memory by the cfgSave command. All switches in the fabric have a copy of this database. When a change is made to the defined configuration, the switch where the changes were made must close its transaction for the changes to be propagated throughout the fabric.
If you have implemented default zoning, you must set the switch you are adding into the fabric to the same default zone mode setting as the rest of the fabric to avoid segmentation.
Both fabrics have identical zones and configurations enabled, including the default zone mode. The two fabrics will join to make one larger fabric with the same zone configuration across the newly created fabric.
If the two fabrics have different zone configurations, they will not be merged. If the two fabrics cannot join, the ISL between the switches will segment.
When a merge conflict is present, a merge will not take place and the ISL will segment. Use the switchShow or errDump commands to obtain additional information about possible merge conflicts, because many non-zone-related configuration parameters can cause conflicts. Refer to the Fabric OS Command Reference for detailed information about these commands.
If the fabrics have different zone configuration data, the system attempts to merge the two sets of zone configuration data. If the zones cannot merge, the ISL will be segmented.
A merge is not possible if any of the following conditions exist: