Brocade Fabric OS Administrator's Guide Supporting Fabric OS v6.3.0 (53-1001336-02, November 2009)

Fabric OS Administrator’s Guide 255
53-1001336-02
Zone merging scenarios
11
Switch A and Switch B have different
defined configurations. Neither have
an enabled zone configuration.
defined: cfg2
zone2: ali3; ali4
effective: none
defined: cfg1
zone1: ali1; ali2
effective: none
Clean merge. The new configuration
will be a composite of the two.
defined: cfg1
zone1: ali1; ali2
cfg2:
zone2: ali3; ali4
effective: none
Switch A and Switch B have different
defined configurations. Switch B has
an enabled configuration.
defined: cfg2
zone2: ali3; ali4
effective: none
defined: cfg1
zone1: ali1; ali2
effective: cfg1
Clean merge. The new configuration
will be a composite of the two, with
cfg1 as the effective configuration.
Effective configuration mismatch. defined: cfg1
zone1: ali1; ali2
effective: cfg1
zone1: ali1; ali2
defined: cfg2
zone2: ali3; ali4
effective: cfg2
zone2: ali3; ali4
Fabric segments due to: Zone Conflict
cfg mismatch
Configuration content mismatch. defined: cfg1
zone1: ali1; ali2
effective: irrelevant
defined: cfg1
zone1: ali3; ali4
effective: irrelevant
Fabric segments due to: Zone Conflict
content mismatch
Same content, different effective cfg
name.
defined: cfg1
zone1: ali1; ali2
effective: cfg1
zone1: ali1; ali2
defined:cfg2
zone1: ali1; ali2
effective: cfg2
zone1: ali1; ali2
Fabric segments due to: Zone Conflict
cfg mismatch
Same content, different zone name. defined: cfg1
zone1: ali1; ali2
effective: irrelevant
defined: cfg1
zone2: ali1; ali2
effective: irrelevant
Fabric segments due to: Zone Conflict
content mismatch
Same content, different alias name. defined: cfg1
ali1: A; B
effective: irrelevant
defined:cfg1
ali2: A; B
effective: irrelevant
Fabric segments due to: Zone Conflict
content mismatch
Same alias name, same content,
different order.
defined: cfg1
ali1: A; B; C
effective: irrelevant
defined: cfg1
ali1: B; C; A
effective: irrelevant
Fabric segments due to: Zone Conflict
content mismatch
Same name, different types. effective: zone1:
MARKETING
effective: cfg1: MARKETING Fabric segments due to: Zone Conflict
type mismatch
Same name, different types. effective: zone1:
MARKETING
effective: alias1:
MARKETING
Fabric segments due to: Zone Conflict
type mismatch
Same name, different types. effective: cfg1:
MARKETING
effective: alias1:
MARKETING
Fabric segments due to: Zone Conflict
type mismatch
Switch A does not have Traffic Isolation
(TI) zones.
Switch B has TI zones.
defined: cfg1 defined: cfg1
TI_zone1
Clean merge.
Switch A has TI zones.
Switch B has identical TI zones.
defined: cfg1
TI_zone1
defined: cfg1
TI_zone1
Clean merge.
Switch A has a TI zone.
Switch B has a different TI zone.
defined: cfg1
TI_zone1
defined: cfg1
TI_zone2
Fabric segments due to: Zone Conflict
cfg mismatch. Cannot merge switches
with different TI zone configurations.
Different default zone access mode
settings.
defzone: allaccess defzone: noaccess Clean merge — noaccess takes
precedence and defzone configuration
from Switch B propagates to fabric.
defzone: noaccess
TABLE 49 Zone merging scenarios (Continued)
Description Switch A Switch B Expected results