HP A7533A - Brocade 4Gb SAN Switch Base User Manual page 238

Table 52 Zone merging scenarios (continued)
Description
There is a cfg content
mismatch.
Same content, with a
different effective cfg name.
Same content with different
zone name.
Same content with a different
alias name.
Same name with different
types.
Same name with different
types.
Same name with different
types.
238 Zone merging scenarios
Switch A
defined: cfg1
zone1: ali1; ali2
effective: irrelevant
defined: cfg1
zone1: ali1; ali2
effective: irrelevant
defined: cfg1
zone1: ali1; ali2
effective: cfg1
zone1: ali1; ali2
defined: cfg1
zone1: ali1; ali2
effective: irrelevant
defined: cfg1 ali1: A; B
effective: irrelevant
effective: zone1:
MARKETING
effective: zone1:
MARKETING
effective:cfg1:
MARKETING
Switch B
defined: cfg1
zone1: ali3; ali4
effective: irrelevant
defined: cfg1
zone1: ali1; ali4
effective: irrelevant
defined:cfg2
zone1: ali1; ali2
effective:cfg2
zone1: ali1; ali2
defined: cfg1
zone2: ali1; ali2
effective: irrelevant
defined:cfg1:ali2: A; B
effective: irrelevant
effective: cfg1:
MARKETING
effective: alias1:
MARKETING
effective:alias1:
MARKETING
Expected Results
Fabric segments due to a zone conflict
content mismatch.
Fabric segments due to a zone conflict
content mismatch.
Fabric segments due to a zone conflict
cfg mismatch.
Fabric segments due to a zone conflict
content mismatch.
Fabric segments due to a zone conflict
content mismatch.
Fabric segments due to a zone conflict
type mismatch.
Fabric segments due to a zone conflict
type mismatch.
Fabric segments due to a zone conflict
type mismatch.