HP StorageWorks MSA 2.8 SAN Switch - Manual (Page 42)

Zoning Concepts
42 Zoning Version 3.1.x/4.1.x User Guide
Resolving Zone Conflicts
Zone conflicts can be resolved by using configupload and performing a cut
and paste operation so the config info matches in both fabrics being merged.
Zone conflicts can also be resolved by performing a cfgClear followed by a
cfgDisable on the segmented fabric that is incorrectly configured. Then do a
portDisable/portEnable on one of the ISL ports that connects the fabrics.
This will cause a merge that will make the fabric consistent with the good
configuration. Be careful in using the
cfgClear command; this command can
inadvertently delete the zone configuration in the fabric.
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 Conflictcfg
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 Conflictcontent
mismatch.
Same name;
different types. effective: zone1:
MARKETING effective: cfg1:
MARKETING Fabric segments due to
Zone Conflicttype
mismatch.
Same name;
different types. effective: zone1:
MARKETING effective: alias1:
MARKETING Fabric segments due to
Zone Conflicttype
mismatch.
Same name;
different types. effective: cfg1:
MARKETING effective: alias1:
MARKETING Fabric segments due to
Zone Conflicttype
mismatch.
Table 3: Zone Merging Scenarios (Continued)
Description Switch A Switch B Expected Results