Fabric OS 5.2.x administrator guide 413
E
Zone merging scenarios
Table 98
provides information on merging zones and the expected results.
Table 98
Zone merging scenarios
Description
Switch A
Switch B
Expected results
Switch A
with a defined
configuration
Switch B
does not have a defined
configuration
defined:
cfg1:
zone1: ali1; ali2
effective: none
defined: none
effective: none
Configuration from
Switch A
to
propagate throughout the fabric in
an inactive state, because the
configuration is not enabled.
Switch A
with a defined and
enabled configuration
Switch B
has a defined
configuration but no effective
configuration
defined: cfg1
zone1: ali1; ali2
effective: cfg1:
defined: cfg1
zone1: ali1; ali2
effective: none
Configuration from
Switch A
to
propagate throughout the fabric.
The configuration is enabled after
the merge in the fabric.
Switch A
and
Switch B
have the
same defined configuration.
Neither have an enabled
configuration.
defined: cfg1
zone1: ali1; ali2
effective: none
defined: cfg1
zone1: ali1; ali2
effective: none
No change (clean merge).
Switch A
and
Switch B
have the
same defined and enabled
configuration.
defined: cfg1
zone1: ali1; ali2
effective: cfg1:
defined: cfg1
zone1: ali1; ali2
effective: cfg1:
No change (clean merge).
Switch A
does not have a defined
configuration
Switch B
with a defined
configuration
defined: none
effective: none
defined:cfg1
zone1: ali1; ali2
effective: none
Switch A
will absorb the
configuration from the fabric.
Switch A
does not have a defined
configuration
Switch B
with a defined
configuration
defined: none
effective: none
defined:cfg1
zone1: ali1; ali2
effective: cfg1
Switch A
will absorb the
configuration from the fabric - with
cfg1 as the effective cfg.
Switch A
and
Switch B
have the
same defined configuration. Only
Switch B
has an enabled
configuration.
defined: cfg1
zone1: ali1; ali2
effective: none
defined: cfg1
zone1: ali1; ali2
effective: cfg1
Clean merge - with cfg1 as the
effective cfg.
Switch A
and
Switch B
have
different defined configurations.
Neither have an enabled zone
configuration.
defined: cfg2
zone2: ali3; ali4
effective: none
defined: cfg1
zone1: ali1; ali2
effective: none
Clean merge - the new cfg will be a
composite of the two --
defined: cfg1
zone1: ali1; ali2
cfg2:
zone2: ali3; ali4
effective: none
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 will be
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
Summary of Contents for AE370A - Brocade 4Gb SAN Switch 4/12
Page 18: ...18 ...
Page 82: ...82 Managing user accounts ...
Page 102: ...102 Configuring standard security features ...
Page 126: ...126 Maintaining configurations ...
Page 198: ...198 Routing traffic ...
Page 238: ...238 Using the FC FC routing service ...
Page 260: ...260 Administering FICON fabrics ...
Page 280: ...280 Working with diagnostic features ...
Page 332: ...332 Administering Extended Fabrics ...
Page 414: ...398 Configuring the PID format ...
Page 420: ...404 Configuring interoperability mode ...
Page 426: ...410 Understanding legacy password behaviour ...
Page 442: ...426 ...
Page 444: ......
Page 447: ......