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

Merge Conflicts, Splitting a Fabric

Get HP StorageWorks 16-EL - SAN Switch PDF manuals and user guides View all HP StorageWorks 16-EL manuals
Add to My Manuals
Save this manual to your list of manuals

Page 39 highlights

Zoning Concepts Merge Conflicts When a merge conflict is present, a merge will not take place and the ISL will segment. Below is a list of possible reasons for merge conflicts. Use the switchshow command to obtain additional information about possible merge conflicts, as many non-zone related configuration parameters may cause conflicts If the fabrics have different zone configuration data, the two sets of zone configuration data are merged if possible. If the zones cannot merge, the interswitch link (ISL) will be segmented. A merge is not possible if any of the following exist: Configuration mismatch Type mismatch Content mismatch Zoning is enabled in both fabrics, and the zone configurations that are enabled are different in each fabric. The name of a zone object in one fabric is used for a different type of a zone object in the other fabric. The definition of a zone object in one fabric is different from the definition of zone object with the same name in the other fabric. Note: If the order of zoneset members between two switches are not listed in the same order, the configuration is considered a mismatch, resulting in the switches being segmented in the fabric. For example: cfg1 = z1; z2 is different from cfg1 = z2; z1, even though members of the configuration are the same. If zoneset members between two switches have the same name defined in the configuration, make sure zoneset members listed are in the same order. Splitting a Fabric If the connections between two fabrics are no longer available, the fabric will segment into two separate fabrics. Each new fabric will retain the same zone configuration. If the connections between two fabrics are replaced and no changes have been made to the zone configuration in either of the two fabrics, then the two fabrics are guaranteed to merge back into one single fabric. If any changes that cause a conflict have been made to either zone configuration, then the fabrics may segment. Zoning Version 3.1.x/4.1.x User Guide 39

  • 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
39
Zoning Version 3.1.x/4.1.x User Guide
Merge Conflicts
When a merge conflict is present, a merge will not take place and the ISL will
segment. Below is a list of possible reasons for merge conflicts.
Use the
switchshow
command to obtain additional information about possible
merge conflicts, as many non-zone related configuration parameters may cause
conflicts
If the fabrics have different zone configuration data, the two sets of zone
configuration data are merged if possible. If the zones cannot merge, the
interswitch link (ISL) will be segmented. A merge is not possible if any of the
following exist:
Note:
If the order of zoneset members between two switches are not listed in the same
order, the configuration is considered a mismatch, resulting in the switches being
segmented in the fabric. For example:
cfg1 = z1; z2
is different from
cfg1 = z2;
z1,
even though members of the configuration are the same. If zoneset members
between two switches have the same name defined in the configuration, make sure
zoneset members listed are in the same order.
Splitting a Fabric
If the connections between two fabrics are no longer available, the fabric will
segment into two separate fabrics. Each new fabric will retain the same zone
configuration.
If the connections between two fabrics are replaced and no changes have been
made to the zone configuration in either of the two fabrics, then the two fabrics are
guaranteed to merge back into one single fabric. If any changes that cause a
conflict have been made to either zone configuration, then the fabrics may
segment.
Configuration
mismatch
Zoning is enabled in both fabrics, and the zone
configurations that are enabled are different in each
fabric.
Type mismatch
The name of a zone object in one fabric is used for a
different type of a zone object in the other fabric.
Content mismatch
The definition of a zone object in one fabric is
different from the definition of zone object with the
same name in the other fabric.