beautypg.com

Brocade Network OS Administrator’s Guide v4.1.1 User Manual

Page 194

background image

Zone merging scenarios: Different content

TABLE 34

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

Zone merging scenarios: Different names

TABLE 35

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

Zone merging scenarios: Default access mode

TABLE 36

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.

Administering Zones

194

Network OS Administrator’s Guide

53-1003225-04