HP StorageWorks 16-EL HP StorageWorks Zoning V3.1.x/4.1.x User Guide (AA-RS26C - Page 40

Zone Merging Scenarios, Table 3: Zone Merging Scenarios (Continued)

Page 40 highlights

Zoning Concepts Zone Merging Scenarios Following are the various Zone Merge scenarios. The "Expected Results" column gives the user an idea of how to do successful merges quickly. The table also gives good guidelines of what to do to avoid merge problems. Table 3: Zone Merging Scenarios Description Switch A has a defined configuration. Switch B does not have a defined configuration. Switch A has a defined and enabled configuration. Switch B has a defined configuration but no effective configuration. Switch A and Switch B have the same defined configuration. Neither have an enabled configuration. Switch A and Switch B have the same defined and enabled configuration. Switch A does not have a defined configuration. Switch B with a defined configuration. Switch A defined: cfg1: zone1: ali1; ali2 effective: none defined: cfg1 zone1: ali1; ali2 effective: cfg1: defined: cfg1 zone1: ali1; ali2 effective: none defined: cfg1 zone1: ali1; ali2 effective: cfg1: defined: none effective: none Switch B defined: none effective: none defined: cfg1 zone1: ali1; ali2 effective: none defined: cfg1 zone1: ali1; ali2 effective: none defined: cfg1 zone1: ali1; ali2 effective: cfg1: defined:cfg1 zone1: ali1; ali2 effective: none Expected Results Configuration from Switch A to propagate throughout the fabric in an inactive state, since the configuration is not enabled. Configuration from Switch A to propagate throughout the fabric. No change (clean merge). No change (clean merge). Switch A will absorb the configuration from the fabric. 40 Zoning Version 3.1.x/4.1.x User Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104

Zoning Concepts
40
Zoning Version 3.1.x/4.1.x User Guide
Zone Merging Scenarios
Following are the various Zone Merge scenarios. The “Expected Results” column
gives the user an idea of how to do successful merges quickly. The table also gives
good guidelines of what to do to avoid merge problems.
Table 3:
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:
cfg1:
zone1: ali1; ali2
effective: none
defined: none
effective: none
Configuration from
Switch A
to propagate
throughout the fabric in
an inactive state, since
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.
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 with a
defined
configuration.
defined: none
effective: none
defined:cfg1
zone1: ali1; ali2
effective: none
Switch A
will absorb the
configuration from the
fabric.