beautypg.com

Table 65, Different content, Table 66 – Brocade Fabric OS Administrators Guide (Supporting Fabric OS v7.3.0) User Manual

Page 333: Different names, Table 67, Ti zones

background image

Zone merging scenarios: Different content

TABLE 65

Description

Switch A

Switch B

Expected results

Effective configuration
mismatch.

defined: cfg1 zone1: ali1;
ali2effective: cfg1 zone1: ali1;
ali2

defined: cfg2 zone2: ali3;
ali4 effective: cfg2 zone2:
ali3; ali4

Fabric segments due to:
Zone Conflict cfg mismatch

Configuration content
mismatch.

defined: cfg1 zone1: ali1;
ali2effective: irrelevant

defined: cfg1 zone1: ali3;
ali4 effective: irrelevant

Fabric segments due to:
Zone Conflict content
mismatch

Zone merging scenarios: Different names

TABLE 66

Description

Switch A

Switch B

Expected results

Same content, different
effective cfg name.

defined: cfg1 zone1: ali1;
ali2 effective: cfg1 zone1:
ali1; ali2

defined:cfg2 zone1: ali1; ali2
effective: cfg2 zone1: ali1;
ali2

Fabric segments due to:
Zone Conflict cfg mismatch

Same content, different
zone name.

defined: cfg1 zone1: ali1;
ali2 effective: irrelevant

defined: cfg1 zone2: ali1; ali2
effective: irrelevant

Fabric segments due to:
Zone Conflict content
mismatch

Same content, different
alias name.

defined: cfg1 ali1: A; B
effective: irrelevant

defined:cfg1ali2: A;
Beffective: irrelevant

Fabric segments due to:
Zone Conflict content
mismatch

Same alias name, same
content, different order.

defined: cfg1ali1: A; B;
Ceffective: irrelevant

defined: cfg1ali1: B; C;
Aeffective: irrelevant

Fabric segments due to:
Zone Conflict content
mismatch

Same name, different
types.

effective: zone1:
MARKETING

effective: cfg1: MARKETING Fabric segments due to:

Zone Conflict type
mismatch

Same name, different
types.

effective: zone1:
MARKETING

effective: alias1:
MARKETING

Fabric segments due to:
Zone Conflict type
mismatch

Same name, different
types.

effective: cfg1:
MARKETING

effective: alias1:
MARKETING

Fabric segments due to:
Zone Conflict type
mismatch

Zone merging scenarios: TI zones

TABLE 67

Description

Switch A

Switch B

Expected results

Switch A does not have Traffic Isolation
(TI) zones.

Switch B has TI zones.

defined: cfg1

effective: cfg1

defined: cfg1

TI_zone1

effective: cfg1

Clean merge. TI zones are not
automatically activated after the merge.

Switch A has TI zones.

Switch B has identical TI zones.

defined: cfg1

TI_zone1

effective: cfg1

defined: cfg1

TI_zone1

effective: cfg1

Clean merge. TI zones are not
automatically activated after the merge.

Administering Advanced Zoning

Fabric OS Administrators Guide

333

53-1003130-01