Table 57 Zone Merging Scenarios: Mixed Fabric Os Versions - HP SN3000B Administrator's Manual

11
Zone merging
TABLE 56
Zone merging scenarios: Default access mode (Continued)
Description
Effective zone configuration.
Effective zone configuration.
Effective zone configuration
Effective zone configuration
TABLE 57
Zone merging scenarios: Mixed Fabric OS versions
Description
Switch A is running Fabric OS 7.0.0 or
later.
Switch B is running a Fabric OS version
earlier than 7.0.0.
Switch A is running Fabric OS 7.0.0 or
later.
Switch B is running a Fabric OS version
earlier than 7.0.0.
NOTE
When merging mixed versions of Fabric OS where both sides have default zone mode No Access set,
the merge results vary depending on which switch initiates the merge.
268
Switch A Switch B
No effective effective: cfg2
configuration.
defzone: allaccess or
defzone = allaccess
noaccess
No effective effective: cfg2
configuration.
defzone: allaccess
defzone = noaccess
effective: cfg1 No effective
configuration.
defzone: noaccess
defzone: noaccess
effective: cfg1 No effective
configuration.
defzone: allaccess
defzone: noaccess
Switch A Switch B
effective: cfg1 No effective
configuration.
defzone = allaccess
defzone - noaccess
No effective effective: cfg2
configuration.
defzone - allaccess
defzone = noaccess
Expected results
Clean merge — effective zone configuration
and defzone mode 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.
Clean merge — effective zone configuration
from Switch A propagates to fabric.
Fabric segments. You can resolve the zone
conflict by changing defzone to noaccess on
Switch 1.
Expected results
Fabric segments due to zone conflict.
Fabric segments due to zone conflict.
Fabric OS Administrator's Guide
53-1002446-01