Zone merging scenarios, Table 52 zone merging scenarios, E zone merging scenarios – HP StorageWorks 2.128 SAN Director Switch User Manual

Page 237: 52 zone merging scenarios, Ezone merging scenarios

Advertising
background image

Fabric OS 5.x administrator guide 237

E

Zone merging scenarios

Table 52

provides information on merging zones and the expected results.

Table 52

Zone merging scenarios

Description

Switch A

Switch B

Expected Results

Switch A has a defined

configuration.
Switch B does not have a

defined configuration.

defined: none

cfg1: none

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 has 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 has a defined

configuration.

defined: none

effective: none

defined:cfg1

zone1: ali1; ali2

effective: none

Switch A absorbs the configuration from

the fabric.

Switch A does not have a

defined configuration.
Switch B has a defined

configuration.

defined: none

effective: none

defined:cfg1

zone1: ali1; ali2

effective: cfg1

Switch A absorbs 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 is 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 is a

composite of the two, with cfg1 as the

effective cfg.

There is an 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 a zone conflict

cfg mismatch.

Advertising