HP SN3000B

Fabric OS Administrator’s Guide 267
53-1002446-01
Zone merging
11
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
TABLE 54 Zone merging scenarios: Different names (Continued)
Description Switch A Switch B Expected results
TABLE 55 Zone merging scenarios: TI zones
Description Switch A Switch B Expected results
Switch A does not have Traffic Isolation
(TI) zones.
Switch B has TI zones.
defined: cfg1
effective: cfg1
defined: cfg1
TI_zone1
effective: cfg1
Clean merge. TI zones are not automatically
activated after the merge.
Switch A has TI zones.
Switch B has identical TI zones.
defined: cfg1
TI_zone1
effective: cfg1
defined: cfg1
TI_zone1
effective: cfg1
Clean merge. TI zones are not automatically
activated after the 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.
Switch A has Enhanced TI zones.
Switch B is running Fabric OS v6.4.0 or
later.
defined: cfg1
TI_zone1
TI_zone2
defined: none Clean merge. TI zones are not automatically
activated after the merge.
Switch A has Enhanced TI zones.
Switch B is running a Fabric OS version
earlier than v6.4.0.
defined: cfg1
TI_zone1
TI_zone2
defined: none Fabric segments because all switches in the
fabric must be running Fabric OS v6.4.0 or
later to support Enhanced TI zones.
TABLE 56 Zone merging scenarios: Default access mode
Description Switch A Switch B Expected results
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
Same default zone access mode
settings.
defzone: allaccess defzone: allaccess Clean merge — defzone configuration is
allaccess in the fabric.
Same default zone access mode
settings.
defzone: noaccess defzone: noaccess Clean merge — defzone configuration is
noaccess in the fabric.