Dell Brocade G620 Brocade 8.0.1 Fabric OS Troubleshooting and Diagnostics Guid - Page 77

Zone conflicts, commands on one of the ISL ports that connects the fabrics. This causes a merge

Page 77 highlights

Zoning Symptom Probable cause and recommended action Fabric segmentation is caused by a "type mismatch". 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 Probable cause and recommended action Fabric segmentation is caused by a "content mismatch". 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, then enter the cfgSave command followed by the portDisable and portEnable commands on one of the ISL ports that connects the fabrics. This causes a merge, making the fabric consistent with the correct configuration. ATTENTION Be careful using the cfgClear command because it deletes the defined configuration. Table 13 summarizes commands that are useful for debugging zoning issues. TABLE 13 Commands for debugging zoning Command aliAdd aliCreate aliDelete aliRemove aliShow cfgAdd cfgCreate cfgClear cfgRemove cfgShow cfgSize cfgDelete cfgDisable cfgEnable cfgSave cfgTransAbort cfgTransShow defZone Function Use to add members to a zone alias. Use to create a zone alias. Use to delete a zone alias. Use to remove members from a zone alias. Use to display zone aliases. Use to add zone members to a zone configuration. Use to create a zone configuration. Use to clear the zoning database. Use to remove zone members from a zone configuration. Displays zoning configuration. Use to display the zone database size. Use to delete the zone configuration. Disables the active (effective) configuration Use to enable and activate (make effective) the specified configuration. Use to save changes to the zone configuration database. Use to abort the current zoning transaction without committing it. Use to display the ID of the current zoning transaction. Sets the default zone access mode to No Access, initializes a zoning transaction (if one is not already in progress), and creates the reserved zoning objects. Brocade Fabric OS Troubleshooting and Diagnostics Guide 53-1004126-01 77

  • 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

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, then enter the
cfgSave
command followed by the
portDisable
and
portEnable
commands on one of the ISL ports that connects the fabrics. This causes a merge, making the fabric consistent with the
correct configuration.
ATTENTION
Be careful using the
cfgClear
command because it deletes the defined configuration.
Table 13
summarizes commands that are useful for debugging zoning issues.
TABLE 13
Commands for debugging zoning
Command
Function
aliAdd
Use to add members to a zone alias.
aliCreate
Use to create a zone alias.
aliDelete
Use to delete a zone alias.
aliRemove
Use to remove members from a zone alias.
aliShow
Use to display zone aliases.
cfgAdd
Use to add zone members to a zone configuration.
cfgCreate
Use to create a zone configuration.
cfgClear
Use to clear the zoning database.
cfgRemove
Use to remove zone members from a zone configuration.
cfgShow
Displays zoning configuration.
cfgSize
Use to display the zone database size.
cfgDelete
Use to delete the zone configuration.
cfgDisable
Disables the active (effective) configuration
cfgEnable
Use to enable and activate (make effective) the specified configuration.
cfgSave
Use to save changes to the zone configuration database.
cfgTransAbort
Use to abort the current zoning transaction without committing it.
cfgTransShow
Use to display the ID of the current zoning transaction.
defZone
Sets the default zone access mode to No Access, initializes a zoning
transaction (if one is not already in progress), and creates the reserved
zoning objects.
Zoning
Brocade Fabric OS Troubleshooting and Diagnostics Guide
53-1004126-01
77