Fabric Segmentation And Zoning; Zone Merging Scenarios; Table 52 Zone Merging Scenarios: Defined And Effective Configurations; Table 53 Table - HP SN3000B Administrator's Manual

Brocade fabric os administrator's guide - supporting fabric os v7.0.1 (53-1002446-01, march 2012)
Hide thumbs Also See for SN3000B:
Table of Contents

Advertisement

Fabric segmentation and zoning

If the connections between two fabrics are no longer available, the fabric segments into two
separate fabrics. Each new fabric retains the same zone configuration.
If the connections between two fabrics are replaced and no changes have been made to the zone
configuration in either of the two fabrics, then the two fabrics merge back into one single fabric. If
any changes that cause a conflict have been made to either zone configuration, then the fabrics
might segment.

Zone merging scenarios

The following tables provide information on merging zones and the expected results.
TABLE 52
Zone merging scenarios: Defined and effective configurations
Description
Switch A has a defined configuration.
Switch B does not have a defined
configuration.
Switch A has a defined and effective
configuration.
Switch B has a defined configuration
but no effective configuration.
Switch A and Switch B have the same
defined configuration. Neither have an
effective configuration.
Switch A and Switch B have the same
defined and effective configuration.
Switch A does not have a defined
configuration.
Switch B has a defined configuration.
Fabric OS Administrator's Guide
53-1002446-01
NOTE
If the zoneset members on two switches are not listed in the same order, the configuration is
considered a mismatch, resulting in the switches being segmented from the fabric. For
example:
cfg1 = z1; z2
configuration are the same. If zoneset members on two switches have the same names
defined in the configuration, make sure zoneset members are listed in the same order.
Table 52
on page 265: Defined and effective configurations
Table 53
on page 266: Different content
Table 54
on page 266: Different names
Table 55
on page 267: TI zones
Table 56
on page 267: Default access mode
Table 57
on page 268: Mixed Fabric OS versions
Switch A
defined:
cfg1:
zone1: ali1; ali2
effective: none
defined: cfg1
zone1: ali1; ali2
effective: cfg1:
defined: cfg1
zone1: ali1; ali2
effective: none
defined: cfg1
zone1: ali1; ali2
effective: cfg1:
defined: none
effective: none
is different from
cfg1 = z2; z1
Switch B
defined: none
effective: none
defined: cfg1
zone1: ali1; ali2
effective: none
defined: cfg1
zone1: ali1; ali2
effective: none
defined: cfg1
zone1: ali1; ali2
effective: cfg1:
defined:cfg1
zone1: ali1; ali2
effective: none
Zone merging
even though members of the
,
Expected results
Configuration from Switch A to propagate
throughout the fabric in an inactive state,
because the configuration is not enabled.
Configuration from Switch A to propagate
throughout the fabric. The configuration is
enabled after the merge in the fabric.
No change (clean merge).
No change (clean merge).
Switch A will absorb the configuration from the
fabric.
11
265

Advertisement

Table of Contents
loading

This manual is also suitable for:

Fabric os v7.0.1

Table of Contents