Brocade Fabric OS Troubleshooting and Diagnostics Guide v6.2.0 (53-1001187-01, April 2009)

Fabric OS Troubleshooting and Diagnostics Guide 69

53-1001187-01

Zone conflicts

Symptom Zone conflict appears in logs and fabric is segmented.

Probable cause and recommended action

This issue is usually caused by incompatible zoning configurations. Verify the following are true:

• The effective cfg (zone set) on each end of the segmented ISL is identical.

• Any zone object with the same name has 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 the 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 newer switches that have 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, then enter the cfgSave command 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.