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

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

Resolving zoning conflicts, Correcting a fabric merge problem quickly, TABLE 13, ATTENTION, cfgClear

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

Page 78 highlights

Zoning TABLE 13 Commands for debugging zoning (continued) Command licenseShow switchShow zoneAdd zoneCreate zoneDelete zoneHelp zoneRemove zoneShow Function Displays current license keys and associated (licensed) products. Displays currently enabled configuration and any E_Port segmentations resulting from zone conflicts. Use to add a member to an existing zone. Use to create a zone. Before a zone becomes active, the cfgSave and cfgEnable commands must be used. Use to delete zones. Displays help information for zone commands. Use to remove zone member aliases from zone database. Displays zone information. For more information about setting up zoning on your switch, refer to the Fabric OS Administrator's Guide. ATTENTION The cfgClear command is a disruptive procedure. Resolving zoning conflicts When merging two fabrics, multiple zoning CLI sessions can be launched on the same switch, or on different switches. This section describes these situations and how they are automatically resolved. ∙ Dual-CLI sessions from the same switch : If you start a zone transaction from CLI-Session1 and then try to perform a zone modification from CLI-Session2, the CLI-Session2 zone transaction is not allowed due to CLI-Session2 not being the owner of the open transaction. If CLI-Session1 logs out, this ends the open transaction and aborts any current zone modifications. CLISession2 is then able to perform zone modifications. Therefore, the zone transaction locking mechanism works on a single switch from the CLI perspective and there is no dangling transaction. ∙ Dual-CLI sessions from different switches : If you start a CLI zone transaction on Switch1 and start another CLI zone transaction on Switch2, when committing the zone transaction from Switch1, the open zone transaction from Switch2 is aborted by Switch1. The following message is posted on Switch2 at the time of zone commit from Switch1: 2012/03/09-21:45:26, [ZONE-1027], 3285, FID 128, INFO, sw0, Zoning transaction aborted Zone Config update Received Correcting a fabric merge problem quickly Brocade recommends that if there are devices attached to the switches on which you need to perform these recovery steps, ensure that these switches are in DefZone NoAccess so as not to cause any RSCN storms and bog down the NameServer. 1. Determine which switches have the incorrect zoning configuration; then log in to the switches as admin. 2. Enter the switchDisable command on all problem switches. 3. Enter the cfgDisable command on each switch. 4. Enter the cfgClear command on each switch. 5. Enter the cfgSave command on each switch to commit the change. Brocade Fabric OS Troubleshooting and Diagnostics Guide 78 53-1004126-01

Section	Page
Brocade Fabric OS Troubleshooting and Diagnostics Guide	1
Preface	7
Document conventions	7
Text formatting conventions	7
Command syntax conventions	7
Notes, cautions, and warnings	8
Brocade resources	8
Contacting Brocade Technical Support	8
Brocade customers	8
Brocade OEM customers	9
Document feedback	9
About This Document	11
Supported hardware and software	11
Brocade Gen 5 (16-Gbps) fixed-port switches	11
Brocade Gen 5 (16-Gbps) DCX 8510 Directors	11
Brocade Gen 6 fixed-port switches	11
Brocade Gen 6 Directors	12
What's new in this document	12
Introduction	13
Troubleshooting overview	13
Network Time Protocol	13
Most common problem areas	13
Questions for common symptoms	14
Gathering information for your switch support provider	17
Setting up your switch for FTP	17
Using the supportSave command	17
Changing the supportSave timeout value	18
Capturing output from a console	18
Capturing command output	19
Building a case for your switch support provider	19
Basic information	19
Detailed problem information	20
Gathering additional information	21
General Troubleshooting	23
Licenses	23
Time	23
Frame Viewer	23
Switch message logs	24
Switch boot	25
Rolling Reboot Detection	25
Reboot classification	25
Restrictions	26
Collecting limited supportSave output on the Rolling Reboot Detection	27
FC-FC routing connectivity	27
Generating and routing an ECHO	27
Superping	29
Restrictions	31
Routing and statistical information	32
Performance issues	33
Connectivity	35
Port initialization and FCP auto-discovery process	35
Link issues	36
Connection problems	37
Checking the physical connection	37
Checking the logical connection	37
Checking the Name Server	38
Link failures	39
Determining a successful speed negotiation	39
Checking for a loop initialization failure	40
Checking for a point-to-point initialization failure	40
Correcting a port that has come up in the wrong mode	41
Marginal links	41
Troubleshooting a marginal link	42
Device login issues on Fabric switch	43
Pinpointing problems with device logins	44
Device login issues on Access Gateway	45
Media-related issues	46
Testing the external transmit and receive path of a port	46
Testing the internal components of a switch	46
Testing components to and from the HBA	47
Segmented fabrics	47
Reconciling fabric parameters individually	48
Downloading a correct configuration	48
Reconciling a domain ID conflict	48
Reconciling incompatible software features	50
Configuration	51
Configuration upload and download issues	51
Gathering additional information	53
Messages captured in the logs	54
Brocade configuration form	54
Firmware Download Errors	55
Blade troubleshooting tips	55
Firmware download issues	56
Troubleshooting with the firmwareDownload command	58
Gathering additional information	59
USB error handling	59
Considerations for downgrading firmware	59
Preinstallation messages	60
Blade types	61
Firmware versions	61
Platform	62
Routing	62
Security	63
Passwords	63
Password recovery options	63
Device authentication	64
Protocol and certificate management	64
Gathering additional information	65
SNMP	65
Gathering additional information	66
FIPS	66
Virtual Fabrics	67
General Virtual Fabrics troubleshooting	67
Fabric identification issues	68
Logical Fabric issues	68
Base switch issues	68
Logical switch issues	69
Switch configuration blade compatibility	71
Gathering additional information	71
ISL Trunking	73
Link issues	73
Buffer credit issues	74
Getting out of buffer-limited mode	74
Zoning	75
Overview of corrective action	75
Verifying a fabric merge problem	75
Verifying a TI zone problem	75
Segmented fabrics	76
Zone conflicts	77
Resolving zoning conflicts	78
Correcting a fabric merge problem quickly	78
Changing the default zone access	79
Editing zone configuration members	79
Reordering the zone member list	79
Checking for Fibre Channel connectivity problems	80
Checking for zoning problems	81
Gathering additional information	81
Diagnostic Features	83
Fabric OS diagnostics	83
Diagnostic information	83
Power-on self-test	84
Disabling POST	85
Enabling POST	85
Switch status	85
Viewing the overall status of the switch	86
Displaying switch information	86
Displaying the uptime for a switch	87
Using the spinFab and portTest commands	88
Debugging spinFab errors	88
Link errors	89
Tx/Rx errors	89
Clearing the error counters	90
Enabling a port	90
Disabling a port	90
Port information	90
Viewing the status of a port	90
Displaying the port statistics	91
Displaying a summary of port errors for a switch	92
Equipment status	93
Checking the temperature, fan, and power supply	93
Checking the status of the fans	94
Checking the status of a power supply	94
Checking temperature status	94
System message log	95
Displaying the system message log with no page breaks	95
Displaying the system message log one message at a time	95
Clearing the system message log	96
Port log	96
Viewing the port log	96
Syslogd configuration	97
Configuring the host	97
Configuring the switch	98
Specifying syslogd hosts	98
Setting the facility level	98
Removing a syslogd host from the list	99
Automatic trace dump transfers	99
Specifying a remote server	99
Enabling the automatic transfer of trace dumps	99
Setting up periodic checking of the remote server	99
Saving comprehensive diagnostic files to the server	100
Multiple trace dump files support	100
Auto FTP support	100
Trace dump support	101
Switch Type and Blade ID	103
Hexadecimal Conversion	105
Hexadecimal overview	105
Example conversion of the hexadecimal triplet Ox616000	105

Match case Limit results 1 per page

TABLE 13

Commands for debugging zoning (continued)

Command

Function

licenseShow

Displays current license keys and associated (licensed) products.

switchShow

Displays currently enabled configuration and any E_Port segmentations

resulting from zone conflicts.

zoneAdd

Use to add a member to an existing zone.

zoneCreate

Use to create a zone. Before a zone becomes active, the

cfgSave

and

cfgEnable

commands must be used.

zoneDelete

Use to delete zones.

zoneHelp

Displays help information for zone commands.

zoneRemove

Use to remove zone member aliases from zone database.

zoneShow

Displays zone information.

For more information about setting up zoning on your switch, refer to the

Fabric OS Administrator's Guide

ATTENTION

The

cfgClear

command is a disruptive procedure.

Resolving zoning conflicts

When merging two fabrics, multiple zoning CLI sessions can be launched on the same switch, or on different switches. This section

describes these situations and how they are automatically resolved.

∙

Dual-CLI sessions from the same switch

: If you start a zone transaction from CLI-Session1 and then try to perform a zone

modification from CLI-Session2, the CLI-Session2 zone transaction is not allowed due to CLI-Session2 not being the owner

of the open transaction. If CLI-Session1 logs out, this ends the open transaction and aborts any current zone modifications. CLI-

Session2 is then able to perform zone modifications. Therefore, the zone transaction locking mechanism works on a single

switch from the CLI perspective and there is no dangling transaction.

∙

Dual-CLI sessions from different switches

: If you start a CLI zone transaction on Switch1 and start another CLI zone transaction

on Switch2, when committing the zone transaction from Switch1, the open zone transaction from Switch2 is aborted by Switch1.

The following message is posted on Switch2 at the time of zone commit from Switch1:

2012/03/09-21:45:26, [ZONE-1027], 3285, FID 128, INFO, sw0, Zoning transaction aborted Zone Config

update Received

Correcting a fabric merge problem quickly

Brocade recommends that if there are devices attached to the switches on which you need to perform these recovery steps, ensure that

these switches are in DefZone NoAccess so as not to cause any RSCN storms and bog down the NameServer.

Determine which switches have the incorrect zoning configuration; then log in to the switches as admin.

Enter the

switchDisable

command on all problem switches.

Enter the

cfgDisable

command on each switch.

Enter the

cfgClear

command on each switch.

Enter the

cfgSave

command on each switch to commit the change.

Zoning

Brocade Fabric OS Troubleshooting and Diagnostics Guide

53-1004126-01