HP StorageWorks 8/8 HP StorageWorks Fabric OS 6.2 administrator guide (5697-00 - Page 267
Description, Switch A, Switch B, Expected results
View all HP StorageWorks 8/8 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 267 highlights
Table 66 Zone merging scenarios (continued) Description Switch A Same content, different effective cfg name. defined: cfg1 zone1: ali1; ali2 effective: cfg1 zone1: ali1; ali2 Same content, different zone name. Same content, different alias name. Same alias name, same content, different order. defined: cfg1 zone1: ali1; ali2 effective: irrelevant defined: cfg1 ali1: A; B effective: irrelevant defined: cfg1 ali1: A; B; C effective: irrelevant Same name, different types. Same name, different types. Same name, different types. Switch A does not have Traffic Isolation (TI) zones. Switch B has TI zones. Switch A has TI zones. Switch B has identical TI zones. effective: zone1: MARKETING effective: zone1: MARKETING effective: cfg1: MARKETING defined: cfg1 defined: cfg1 TI_zone1 Switch A has a TI zone. Switch B has a different TI zone. defined: cfg1 TI_zone1 Different default zone access mode defzone: allaccess settings. Different default zone access mode defzone: noaccess settings. Same default zone access mode settings. Same default zone access mode settings. Effective zone configuration. Effective zone configuration. defzone: allaccess defzone: noaccess No effective configuration. defzone = allaccess No effective configuration. defzone = noaccess Switch B defined:cfg2 zone1: ali1; ali2 effective: cfg2 zone1: ali1; ali2 defined: cfg1 zone2: ali1; ali2 effective: irrelevant defined:cfg1 ali2: A; B effective: irrelevant defined: cfg1 ali1: B; C; A effective: irrelevant effective: cfg1: MARKETING effective: alias1: MARKETING effective: alias1: MARKETING defined: cfg1 TI_zone1 defined: cfg1 TI_zone1 defined: cfg1 TI_zone2 defzone: noaccess defzone: allaccess defzone: allaccess defzone: noaccess effective: cfg2 effective: cfg2 Expected results Fabric segments due to: Zone Conflict cfg mismatch Fabric segments due to: Zone Conflict content mismatch Fabric segments due to: Zone Conflict content mismatch Fabric segments due to: Zone Conflict content mismatch Fabric segments due to: Zone Conflict type mismatch Fabric segments due to: Zone Conflict type mismatch Fabric segments due to: Zone Conflict type mismatch Clean merge. Clean merge. Fabric segments due to: Zone Conflict cfg mismatch. Cannot merge switches with different TI zone configurations. Clean merge: noaccess takes precedence and defzone configuration from Switch B propagates to fabric. defzone: noaccess Clean merge: noaccess takes precedence and defzone configuration from Switch A propagates to fabric. defzone: noaccess Clean merge: defzone configuration is allaccess in the fabric. Clean merge: defzone configuration is noaccess in the fabric. Clean merge: effective zone configuration from Switch B propagates to fabric. Fabric segments because Switch A has a hidden zone configuration (no access) activated and Switch B has an explicit zone configuration activated. Fabric OS 6.2 administrator guide 265