Network OS Administration Guide

Supporting Network OS 6.0.1a

Part Number: 53-1003768-04

Zone merging scenarios

The following tables provide information on merging zones and the expected results.

Table 25 Zone merging scenarios: Defined and enabled configurations

Description

Switch A

Switch B

Expected results

Switch A has a defined configuration.

Switch B does not have a defined configuration.

defined:cfg1 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

enabled: none

defined: none

enabled: none

Configuration from Switch A propagates 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 enabled configuration.

defined: cfg1 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

enabled: cfg1

defined: cfg1 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

enabled: none

Configuration from Switch A propagates 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: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

enabled: none

defined: cfg1 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

enabled: none

No change (clean merge).

Switch A and Switch B have the same defined and enabled configuration.

defined: cfg1 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

enabled: cfg1:

defined: cfg1 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

enabled: cfg1:

No change (clean merge).

Switch A does not have a defined configuration.

Switch B has a defined configuration.

defined: none

enabled: none

defined:cfg1 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

enabled: none

Switch A absorbs the configuration from the fabric.

Switch A does not have a defined configuration.

Switch B has a defined and enabled configuration.

defined: none

enabled: none

defined:cfg1 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

enabled: cfg1

Switch A absorbs the configuration from the fabric, with cfg1 as the enabled configuration.

Switch A and Switch B have the same defined configuration. Only Switch B has an enabled configuration.

defined: cfg1 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

enabled: none

defined: cfg1 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

enabled: cfg1

Clean merge, with cfg1 as the enabled configuration.

Switch A and Switch B have different defined configurations. Neither have an enabled configuration.

defined: cfg2 zone2: 10:00:00:90:69:00:00:8c; 10:00:00:90:69:00:00:8d

enabled: none

defined: cfg1 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

enabled: none

Clean merge. The new configuration will be a composite of the two.

defined: cfg1 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

defined: cfg2 zone2: 10:00:00:90:69:00:00:8c; 10:00:00:90:69:00:00:8d

enabled: none

Switch A and Switch B have different defined configurations. Switch B has an enabled configuration.

defined: cfg2 zone2: 10:00:00:90:69:00:00:8c; 10:00:00:90:69:00:00:8d

enabled: none

defined: cfg1 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

enabled: cfg1

Clean merge. The new configuration is a composite of both, with cfg1 as the enabled configuration.

Switch A does not have a defined configuration.

Switch B has a defined configuration and an enabled configuration, but the enabled configuration is different from the defined configuration.

defined: none

enabled: none

defined: cfg1 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

effective: cfg1

zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

zone2: 10:00:00:90:69:00:00:8c, 10:00:00:90:69:00:00:8d

Clean merge. Switch A absorbs the defined configuration from the fabric, with cfg1 as the effective configuration.

In this case, however, the effective configurations for Switch A and Switch B are different. You should issue a zoning enabled-configuration cfg-name command from the switch with the proper effective configuration.

Table 26 Zone merging scenarios: Different content

Description

Switch A

Switch B

Expected results

Enabled configuration mismatch.

defined: cfg1 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

enabled: cfg1 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

defined: cfg2 zone2: 10:00:00:90:69:00:00:8c; 10:00:00:90:69:00:00:8d

enabled: cfg2 zone2: 10:00:00:90:69:00:00:8c; 10:00:00:90:69:00:00:8d

Fabric segments due to mismatching zone configurations

Configuration content mismatch.

defined: cfg1 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

enabled: irrelevant

defined: cfg1 zone1: 10:00:00:90:69:00:00:8c; 10:00:00:90:69:00:00:8d

enabled: irrelevant

Fabric segments due to mismatching zone content

Table 27 Zone merging scenarios: Different names

Description

Switch A

Switch B

Expected results

Same content, different enabled configuration name.

defined: cfg1 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

enabled: cfg1 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

defined:cfg2 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

enabled: cfg2 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

Fabric segments due to mismatching zone configurations

Same content, different zone name.

defined: cfg1 zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

enabled: irrelevant

defined: cfg1 zone2: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b

enabled: irrelevant

Fabric segments due to mismatching zone content

Same name, same content, different order.

defined: cfg1zone1: 10:00:00:90:69:00:00:8a; 10:00:00:90:69:00:00:8b; 10:00:00:90:69:00:00:8c

enabled: irrelevant

defined: cfg1zone1: 10:00:00:90:69:00:00:8b; 10:00:00:90:69:00:00:8c; 10:00:00:90:69:00:00:8a

enabled: irrelevant

Fabric segments due to mismatching zone content

Same name, different types.

effective: zone1: MARKETING

enabled: cfg1: MARKETING

Fabric segments due to mismatching types

Table 28 Zone merging scenarios: Default access mode

Description

Switch A

Switch B

Expected results

Different default zone access mode settings.

default zone: All Access

default zone: No Access

Clean merge. No Access takes precedence and default zone configuration from Switch B propagates to fabric.

default zone: No Access

Same default zone access mode settings.

default zone: All Access

default zone: All Access

Clean merge. Default zone configuration is All Access in the fabric.

Same default zone access mode settings.

default zone: No Access

default zone: No Access

Clean merge. Default zone configuration is No Access in the fabric.

Enabled zone configuration.

No enabled configuration.

default zone = All Access

enabled: cfg2

default zone: All Access or No Access

Clean merge. Enabled zone configuration and default zone mode from Switch B propagates to fabric.

Enabled zone configuration.

No enabled configuration.

default zone = No Access

enabled: cfg2

default zone: All Access

Fabric segments because Switch A has a hidden zone configuration (No Access) activated and Switch B has an explicit zone configuration activated.

Enable zone configuration.

enabled: cfg1

default zone: No Access

No enabled configuration.

default zone: No Access

Clean merge. Enabled zone configuration from Switch A propagates to fabric.

Enable zone configuration.

enabled: cfg1

default zone: All Access

No enabled configuration.

default zone: No Access

Fabric segments. You can resolve the zone conflict by changing the default zone to No Access on Switch A.