HP Brocade 4Gb SAN Switch for HP BladeSystem p-Class - Manual (Page 238)

238 Zone merging scenarios
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 cfg is a
composite of the two, with cfg1
as the effective cfg.
Effective cfg 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
cfg content mismatch defined: cfg1
zone1: ali1; ali2
effective: irrelevant
defined: cfg1
zone1: ali3; ali4
effective: irrelevant
Fabric segments due to: Zone
Conflict content mismatch
defined: cfg1
zone1: ali1; ali2
effective: irrelevant
defined: cfg1
zone1: ali1; 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 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
Table 43 Zone merging scenarios (continued)
Description Switch A Switch B Expected results