Zone Merging Scenarios - Brocade Communications Systems 53-1001763-02 Administrator's Manual

11

Zone merging scenarios

When two secure fabrics join, the traditional zoning merge does not occur. Instead, a zoning
database is downloaded from the primary FCS switch of the merged secure fabric. When E_Ports
are active between two switches, the name of the FCS server and a zoning policy set version
identifier are exchanged between the switches. If the views of the two secure fabrics are the same,
the fabric's primary FCS server downloads the zoning database and security policy sets to each
switch in the fabric. If there is a view conflict, the E_Ports are segmented due to incompatible
security data.
As part of zoning architecture, you must determine which of the two basic zoning architectures
(hard or soft) works best for your fabric. With time and planning, the basic hard zone configuration
works for most sites.

Zone merging scenarios

Table 51
TABLE 51
Zone merging scenarios
Description
Switch A has a defined configuration.
Switch B does not have a defined
configuration.
Switch A has a defined and enabled
configuration.
Switch B has a defined configuration
but no effective configuration.
Switch A and Switch B have the same
defined configuration. Neither have an
enabled configuration.
Switch A and Switch B have the same
defined and enabled configuration.
Switch A does not have a defined
configuration.
Switch B has a defined configuration.
Switch A does not have a defined
configuration.
Switch B has a defined configuration.
Switch A and Switch B have the same
defined configuration. Only Switch B
has an enabled configuration.
Switch A and Switch B have different
defined configurations. Neither have
an enabled zone configuration.
264
provides information on merging zones and the expected results.
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
defined: none
effective: none
defined: cfg1
zone1: ali1; ali2
effective: none
defined: cfg2
zone2: ali3; ali4
effective: none
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
defined:cfg1
zone1: ali1; ali2
effective: cfg1
defined: cfg1
zone1: ali1; ali2
effective: cfg1
defined: cfg1
zone1: ali1; ali2
effective: none
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.
Switch A will absorb the configuration
from the fabric, with cfg1 as the
effective configuration.
Clean merge, with cfg1 as the
effective configuration.
Clean merge. The new configuration
will be a composite of the two.
defined: cfg1
zone1: ali1; ali2
cfg2:
zone2: ali3; ali4
effective: none
Fabric OS Administrator's Guide
53-1001763-02