HP A7533A - Brocade 4Gb SAN Switch Base Administrator's Manual page 267

Table 66 Zone merging scenarios (continued)
Description
Same content, different effective cfg
name.
Same content, different zone name.
Same content, different alias name.
Same alias name, same content,
different order.
Same name, different types.
Same name, different types.
Same name, different types.
Switch A does not have Traffic
Isolation (TI) zones.
Switch B has TI zones.
Switch A has TI zones.
Switch B has identical TI zones.
Switch A has a TI zone.
Switch B has a different TI zone.
Different default zone access mode
settings.
Different default zone access mode
settings.
Same default zone access mode
settings.
Same default zone access mode
settings.
Effective zone configuration.
Effective zone configuration.
Switch A Switch B
defined: cfg1 defined:cfg2
zone1: ali1; ali2 zone1: ali1; ali2
effective: cfg1 effective: cfg2
zone1: ali1; ali2 zone1: ali1; ali2
defined: cfg1 defined: cfg1
zone1: ali1; ali2 zone2: ali1; ali2
effective: irrelevant effective: irrelevant
defined: cfg1 defined:cfg1
ali1: A; B ali2: A; B
effective: irrelevant effective: irrelevant
defined: cfg1 defined: cfg1
ali1: A; B; C ali1: B; C; A
effective: irrelevant effective: irrelevant
effective: zone1: effective: cfg1:
MARKETING MARKETING
effective: zone1: effective: alias1:
MARKETING MARKETING
effective: cfg1: effective: alias1:
MARKETING MARKETING
defined: cfg1 defined: cfg1
TI_zone1
defined: cfg1 defined: cfg1
TI_zone1 TI_zone1
defined: cfg1 defined: cfg1
TI_zone1 TI_zone2
defzone: allaccess defzone: noaccess
defzone: noaccess defzone: allaccess
defzone: allaccess defzone: allaccess
defzone: noaccess defzone: noaccess
No effective effective: cfg2
configuration.
defzone = allaccess
No effective effective: cfg2
configuration.
defzone = noaccess
Expected results
Fabric segments due to: Zone
Conflict cfg mismatch
Fabric segments due to: Zone
Conflict content mismatch
Fabric segments due to: Zone
Conflict content mismatch
Fabric segments due to: Zone
Conflict content mismatch
Fabric segments due to: Zone
Conflict type mismatch
Fabric segments due to: Zone
Conflict type mismatch
Fabric segments due to: Zone
Conflict type mismatch
Clean merge.
Clean merge.
Fabric segments due to: Zone
Conflict cfg mismatch. Cannot
merge switches with different TI
zone configurations.
Clean merge: noaccess takes
precedence and defzone
configuration from Switch B
propagates to fabric.
defzone: noaccess
Clean merge: noaccess takes
precedence and defzone
configuration from Switch A
propagates to fabric.
defzone: noaccess
Clean merge: defzone
configuration is allaccess in the
fabric.
Clean merge: defzone
configuration is noaccess in the
fabric.
Clean merge: effective zone
configuration from Switch B
propagates to fabric.
Fabric segments because Switch A
has a hidden zone configuration
(no access) activated and Switch B
has an explicit zone configuration
activated.
Fabric OS 6.2 administrator guide 265