Home » Dell Manuals » Hubs & Switches » Dell Brocade 6520 » Manual Viewer

Dell Brocade 6520 Fabric OS Troubleshooting and Diagnostics Guide v7.1.0 - Page 91

Zone conflicts

Add to My Manuals
Save this manual to your list of manuals

Page 91 highlights

Zone conflicts 9 Symptom Symptom Symptom 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. 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. 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. 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 14 summarizes commands that are useful for debugging zoning issues. TABLE 14 Commands for debugging zoning Command Function aliCreate aliDelete cfgCreate cfgShow cfgDisable Use to create a zone alias. Use to delete a zone alias. Use to create a zone configuration. Displays zoning configuration. Disables the active (effective) configuration Fabric OS Troubleshooting and Diagnostics Guide 75 53-1002751-01

Section	Page
About This Document	11
How this document is organized	11
Supported hardware and software	12
What’s new in this document	12
Document conventions	13
Text formatting	13
Command syntax conventions	13
Command examples	13
Notes, cautions, and warnings	14
Key terms	14
Additional information	14
Brocade resources	14
Other industry resources	15
Getting technical help	15
Document feedback	16
Introduction	17
Troubleshooting overview	17
Network time protocol	17
Most common problem areas	18
Questions for common symptoms	18
Gathering information for your switch support provider	21
Setting up your switch for FTP	21
Capturing a supportSave	21
Capturing output from a console	22
Capturing command output	23
Building a case for your switch support provider	23
Basic information	23
Detailed problem information	24
Gathering additional information	25
General	27
Licenses	27
Time	27
Frame Viewer	28
Switch message logs	28
Switch boot	29
Rolling Reboot Detection	30
FC-FC routing connectivity	32
Generating and routing an ECHO	32
Superping	33
Route and statistical information	36
Performance issues	37
Connectivity	39
Port initialization and FCP auto-discovery process	39
Link issues	41
Connection problems	41
Checking the physical connection	41
Checking the logical connection	42
Checking the Name Server	42
Link failures	44
Determining a successful speed negotiation	44
Checking for a loop initialization failure	45
Checking for a point-to-point initialization failure	45
Correcting a port that has come up in the wrong mode	46
Marginal links	46
Troubleshooting a marginal link	47
Device login issues	49
Pinpointing problems with device logins	49
Media-related issues	51
Testing a port’s external transmit and receive path	52
Testing a switch’s internal components	52
Testing components to and from the HBA	52
Segmented fabrics	52
Reconciling fabric parameters individually	53
Downloading a correct configuration	54
Reconciling a domain ID conflict	54
Reconciling incompatible software features	55
Port mirroring	56
In-Order Delivery	56
Port mirroring considerations	56
Supported platforms	57
Maximum mirror connections	58
Configuring a port to be a mirror port	58
Adding a port mirror connection	58
Deleting a port mirror connection	59
Displaying port mirror connections	59
Configuration	61
Configuration upload and download issues	61
Gathering additional information	64
Brocade configuration form	64
Firmware Download Errors	67
Blade troubleshooting tips	67
Firmware download issues	68
Troubleshooting with the firmwareDownload command	70
Gathering additional information	71
USB error handling	71
Considerations for downgrading firmware	72
Preinstallation messages	72
Blade types	74
Firmware versions	74
Platform	75
Routing	75
Security	77
Passwords	77
Password recovery options	78
Device authentication	78
Protocol and certificate management	79
Gathering additional information	79
SNMP	80
Gathering additional information	80
FIPS	80
Virtual Fabrics	81
General Virtual Fabrics troubleshooting	81
Fabric identification issues	82
Logical Fabric issues	82
Base switch issues	83
Logical switch issues	84
Switch configuration blade compatibility	85
Gathering additional information	86
ISL Trunking	87
Link issues	87
Buffer credit issues	88
Getting out of buffer-limited mode	88
Zoning	89
Overview of corrective action	89
Verifying a fabric merge problem	89
Verifying a TI zone problem	89
Segmented fabrics	90
Zone conflicts	91
Correcting a fabric merge problem quickly	92
Changing the default zone access	93
Editing zone configuration members	93
Reordering the zone member list	93
Checking for Fibre Channel connectivity problems	94
Checking for zoning problems	95
Gathering additional information	96
Diagnostic Features	97
About Fabric OS diagnostics	97
Diagnostic information	97
Power-on self test	98
Disabling POST	100
Enabling POST	100
Switch status	100
Viewing the overall status of the switch	100
Displaying switch information	101
Displaying the uptime for a switch	102
Using the SpinFab and portTest commands	103
Debugging spinFab errors	104
Clearing the error counters	105
Enabling a port	105
Disabling a port	106
Diagnostic Port (D_Port)	106
Understanding D_Port	107
Supported topologies	109
Using D_Port without HBAs	111
Using D_Port with HBAs	113
Controlling testing	116
Example test scenarios and output	116
Port information	121
Viewing the status of a port	121
Displaying the port statistics	122
Displaying a summary of port errors for a switch	123
Equipment status	124
Checking the temperature, fan, and power supply	124
Checking the status of the fans	124
Checking the status of a power supply	125
Checking temperature status	125
System message log	126
Displaying the system message log, with no page breaks	126
Displaying the system message log one message at a time	127
Clearing the system message log	127
Port log	127
Viewing the port log	127
Syslogd configuration	129
Configuring the host	129
Configuring the switch	130
Automatic trace dump transfers	131
Specifying a remote server	131
Enabling the automatic transfer of trace dumps	131
Setting up periodic checking of the remote server	131
Saving comprehensive diagnostic files to the server	132
Switch Type and Blade ID	133
Hexadecimal Conversion	137
Example conversion of the hexadecimal triplet Ox616000	137
Decimal-to-hexadecimal conversion table	138

Match case Limit results 1 per page

Fabric OS Troubleshooting and Diagnostics Guide

53-1002751-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 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 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 14

summarizes commands that are useful for debugging zoning issues.

TABLE 14

Commands for debugging zoning

Command

Function

aliCreate

Use to create a zone alias.

aliDelete

Use to delete a zone alias.

cfgCreate

Use to create a zone configuration.

cfgShow

Displays zoning configuration.

cfgDisable

Disables the active (effective) configuration