HP AM866A Brocade Troubleshooting and Diagnostics Guide v6.1.0 (53-1000853-01, - Page 78

Zone conflicts

Get HP AM866A - StorageWorks 8/8 Base SAN Switch PDF manuals and user guides
UPC - 884420064602
View all HP AM866A manuals
Add to My Manuals
Save this manual to your list of manuals

Page 78 highlights

8 Zone conflicts Symptom Zone conflict appears in logs and fabric is segmented. Probable cause and recommended action This issue is usually caused by an incompatible zoning configurations. Verify one of the following: • The effective cfg (zone set) on each end of the segmented ISL must be identical. • Any zone object with the same name must have the same entries in the same sequence. Symptom Fabric segmentation is caused by an "incompatible zone database". Probable cause and recommended action If fabric segmentation is caused by an "incompatible zone database," check following: • Whether the merge of the two fabrics resulted in the merged zone database exceeding the zone database size limitation. Different Fabric OS versions support different zone database sizes, for example pre-Fabric OS v5.2.0 supports 256 Kb and Fabric OS v5.2.0 and later support 1 Mb. • Whether any port number greater than 255 is configured in a port zone. Any pre-Fabric OS v5.2.0 switch will not merge with a newer switches with a port index greater than 255. Symptom Fabric segmentation is caused by a "configuration mismatch". Probable cause and recommended action Occurs when zoning is enabled in both fabrics and the zone configurations are different in each fabric. Symptom Fabric segmentation is caused by a "type mismatch". Probable cause and recommended action Occurs when the name of a zone object in one fabric is also used for a different type of zone object in the other fabric. A zone object is any device in a zone. Symptom Fabric segmentation is caused by a "content mismatch". Probable cause and recommended action Occurs when the definition in one fabric is different from the definition of a zone object with the same name in the other fabric. Zone conflicts Zone conflicts can be resolved by saving a configuration file with the configUpload command, examining the zoning information in the file, and performing a cut and paste operation so that the configuration information matches in the fabrics being merged. After examining the configuration file, you can choose to resolve zone conflicts by using the cfgDisable command followed by the cfgClear command on the incorrectly configured segmented fabric, followed by the portDisable and portEnable commands on one of the ISL ports that connects the fabrics. This will cause a merge, making the fabric consistent with the correct configuration. 64 Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-01

  • 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
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
64
Fabric OS Troubleshooting and Diagnostics Guide
53-1000853-01
Zone conflicts
8
Symptom
Zone conflict appears in logs and fabric is segmented.
Probable cause and recommended action
This issue is usually caused by an incompatible zoning configurations. Verify one of the following:
•
The effective
cfg
(zone set) on each end of the segmented ISL must be identical.
•
Any zone object with the same name must have the same entries in the same sequence.
Symptom
Fabric segmentation is caused by an “incompatible zone database”.
Probable cause and recommended action
If fabric segmentation is caused by an “incompatible zone database,” check following:
•
Whether the merge of the two fabrics resulted in the merged zone database exceeding the
zone database size limitation.
Different Fabric OS versions support different zone database sizes, for example pre-Fabric
OS v5.2.0 supports 256 Kb and Fabric OS v5.2.0 and later support 1 Mb.
•
Whether any port number greater than 255 is configured in a port zone.
Any pre-Fabric OS v5.2.0 switch will not merge with a newer switches with a port index
greater than 255.
Symptom
Fabric segmentation is caused by a “configuration mismatch”.
Probable cause and recommended action
Occurs when zoning is enabled in both fabrics and the zone configurations are different in each
fabric.
Symptom
Fabric segmentation is caused by a “type mismatch”.
Probable cause and recommended action
Occurs when the name of a zone object in one fabric is also used for a different type of zone object
in the other fabric. A zone object is any device in a zone
.
Symptom
Fabric segmentation is caused by a “content mismatch”.
Probable cause and recommended action
Occurs when the definition in one fabric is different from the definition of a zone object with the
same name in the other fabric.
Zone conflicts
Zone conflicts can be resolved by saving a configuration file with the
configUpload
command,
examining the zoning information in the file, and performing a cut and paste operation so that the
configuration information matches in the fabrics being merged.
After examining the configuration file, you can choose to resolve zone conflicts by using the
cfgDisable
command followed by the
cfgClear
command on the incorrectly configured segmented
fabric, followed by the
portDisable
and
portEnable
commands on one of the ISL ports that
connects the fabrics. This will cause a merge, making the fabric consistent with the correct
configuration.