
3 – Managing Fabrics | 0 | |
|
| |
Zoning a Fabric |
|
|
|
|
|
|
|
|
3.7.7
Merging Fabrics and Zoning
If you join two fabrics with an
3.7.7.1
Zone Merge Failure
If a zone merge is unsuccessful, the
A zone merge will fail if the two active zone sets have member zones with identical names that differ in membership or type. For example, consider Fabric A and Fabric B each with a soft zone named “ZN1” in its active zone set. Fabric A "ZN1" contains a member specified by Domain ID 1 and Port 1; Fabric B “ZN1” contains a member specified by Domain ID 1 and Port 2. In this case, the merge will fail because the two zones have the same name, but different membership.
3.7.7.2
Zone Merge Failure Recovery
When a zone merge failure occurs, the conflict that caused the failure must be resolved. You can correct a failure due to a zone conflict by deactivating one of the active zone sets or by editing the conflicting zones so that their membership is the same. You can deactivate the active zone set on one fabric if the active zone set on the other fabric accurately defines your zoning needs. If not, you must edit the zone memberships, and reactivate the zone sets. After correcting the zone membership, reset the isolated ports to allow the fabrics to join. Refer to ”Managing Zones” on page
Note: If you deactivate the active zone set in one fabric and the Interop Auto Save parameter is enabled, the active zone set from the second fabric will propagate to the first fabric and replace all zones with matching names in the configured zone sets. If the zone sets to merge have the same Zone A that only differ in the type of zone (soft vs. ACL), the zone sets will merge. If this is a two switch fabric, Switch 1 will state that Zone A is soft and Switch 2 will state that Zone A is ACL.