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

Dell Brocade 5100 Brocade 7.3.0 Fabric OS Troubleshooting and Diagnostics Guid - Page 71

Troubleshooting with the firmwareDownload command, Gathering additional information

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

Page 71 highlights

Troubleshooting with the firmwareDownload command 5 Troubleshooting with the firmwareDownload command A network diagnostic script and preinstallation check is a part of the firmware download procedure. The script and preinstallation check performs troubleshooting and automatically checks for any blocking conditions. If the firmware download fails, refer to the Fabric OS Message Reference for details about error messages. Also refer to, "Considerations for downgrading firmware" on page 56. ATTENTION Do not run mixed firmware versions on CPs. If a firmware download fails in a director, the firmwareDownload command synchronizes the firmware on the two partitions of each CP by starting a firmware commit operation. Wait at least 15 minutes for this commit operation to complete before attempting another firmware download. If the firmware download fails in a director or enterprise-class platform, the CPs may end up with different versions of firmware and are unable to achieve HA synchronization between the two blades. In such cases, issue the firmwareDownload -s command on the standby CP; the single mode (-s) option allows you to upgrade the firmware on the standby CP to match the firmware version running on the active CP. This situation can also occur during a CP replacement in which the replacement CP has a lower firmware version. HA should be disabled and the firmware should be updated on the replacement CP before any other operations are considered. Then reissue the firmwareDownload command to download the desired firmware version to both CPs. For example, if CP0 is running Fabric OS v7.1.0 on the primary and secondary partitions, and CP1 is running Fabric OS v7.2.0 on the primary and secondary partitions, then synchronize them by issuing the firmwareDownload command. NOTE Some of the messages include error codes (as shown in the following example). These error codes are for internal use only and you can disregard them. Port configuration with EX ports enabled along with trunking for port(s) 63, use the portCfgEXPort, portCfgVEXPort, and portCfgTrunkPort commands to remedy this. Verify blade is ENABLED. (error 3) Gathering additional information You should follow these best practices for firmware download before you start the procedure: • Keep all session logs. • Enter the supportSave or the supportShow command before and after entering the firmwareDownload command. • If a problem persists, package together all of the information (the Telnet session logs and serial console logs, output from the supportSave command) for your switch support provider. Make sure you identify what information was gathered before and after issuing the firmwareDownload command. Fabric OS Troubleshooting and Diagnostics Guide 55 53-1003141-01

Section	Page
About This Document	11
How this document is organized	11
Supported hardware and software	12
What’s new in this document	13
Document conventions	13
Text formatting	13
Command syntax conventions	13
Command examples	14
Notes, cautions, and warnings	14
Key terms	14
Additional information	15
Brocade resources	15
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
Using the supportSave command	21
Capturing output from a console	23
Capturing command output	23
Building a case for your switch support provider	23
Basic information	23
Detailed problem information	24
Gathering additional information	26
General Troubleshooting	27
Licenses	27
Time	27
Frame Viewer	28
Switch message logs	28
Switch boot	30
Rolling Reboot Detection	30
FC-FC routing connectivity	32
Generating and routing an ECHO	32
Superping	34
Routing and statistical information	37
Performance issues	38
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	43
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 the external transmit and receive path of a port	52
Testing the internal components of a switch	52
Testing components to and from the HBA	52
Segmented fabrics	53
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	59
Adding a port mirror connection	59
Deleting a port mirror connection	59
Displaying port mirror connections	60
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	71
Gathering additional information	71
USB error handling	72
Considerations for downgrading firmware	72
Preinstallation messages	72
Blade types	75
Firmware versions	75
Platform	76
Routing	76
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
Resolving zoning conflicts	92
Correcting a fabric merge problem quickly	93
Changing the default zone access	93
Editing zone configuration members	93
Reordering the zone member list	94
Checking for Fibre Channel connectivity problems	94
Checking for zoning problems	95
Gathering additional information	96
Diagnostic Features	97
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	101
Displaying switch information	101
Displaying the uptime for a switch	103
Using the spinFab and portTest commands	103
Debugging spinFab errors	104
Clearing the error counters	105
Enabling a port	106
Disabling a port	106
Port information	106
Viewing the status of a port	106
Displaying the port statistics	107
Displaying a summary of port errors for a switch	108
Equipment status	109
Checking the temperature, fan, and power supply	110
Checking the status of the fans	110
Checking the status of a power supply	110
Checking temperature status	111
System message log	111
Displaying the system message log with no page breaks	112
Displaying the system message log one message at a time	112
Clearing the system message log	112
Port log	112
Viewing the port log	113
Syslogd configuration	114
Configuring the host	115
Configuring the switch	115
Automatic trace dump transfers	116
Specifying a remote server	117
Enabling the automatic transfer of trace dumps	117
Setting up periodic checking of the remote server	117
Saving comprehensive diagnostic files to the server	117
Switch Type and Blade ID	119
Hexadecimal Conversion	123
Hexadecimal overview	123
Example conversion of the hexadecimal triplet Ox616000	123
Decimal-to-hexadecimal conversion table	124

Match case Limit results 1 per page

Fabric OS Troubleshooting and Diagnostics Guide

53-1003141-01

Troubleshooting with the firmwareDownload command

A network diagnostic script and preinstallation check is a part of the firmware download procedure.

The script and preinstallation check performs troubleshooting and automatically checks for any

blocking conditions. If the firmware download fails, refer to the

Fabric OS Message Reference

for

details about error messages. Also refer to,

“Considerations for downgrading firmware”

page 56.

ATTENTION

Do not run mixed firmware versions on CPs.

If a firmware download fails in a director, the

firmwareDownload

command synchronizes the

firmware on the two partitions of each CP by starting a firmware commit operation. Wait

at least

minutes for this commit operation to complete before attempting another firmware download.

If the firmware download fails in a director or enterprise-class platform, the CPs may end up with

different versions of firmware and are unable to achieve HA synchronization between the two

blades. In such cases, issue the

firmwareDownload -s

command on the standby CP; the single

mode (

-s

) option allows you to upgrade the firmware on the standby CP to match the firmware

version running on the active CP. This situation can also occur during a CP replacement in which

the replacement CP has a lower firmware version. HA should be disabled and the firmware should

be updated on the replacement CP before any other operations are considered.

Then reissue the

firmwareDownload

command to download the desired firmware version to both

CPs. For example, if CP0 is running Fabric OS v7.1.0 on the primary and secondary partitions, and

CP1 is running Fabric OS v7.2.0 on the primary and secondary partitions, then synchronize them by

issuing the

firmwareDownload

command.

NOTE

Some of the messages include error codes (as shown in the following example). These error codes

are for internal use only and you can disregard them.

Port configuration with EX ports enabled along with trunking for port(s) 63, use

the portCfgEXPort, portCfgVEXPort, and portCfgTrunkPort commands to remedy this.

Verify blade is ENABLED. (error 3)

Gathering additional information

You should follow these best practices for firmware download before you start the procedure:

•

Keep all session logs.

•

Enter the

supportSave

or the

supportShow

command

before and after

entering the

firmwareDownload

command.

•

If a problem persists, package together all of the information (the Telnet session logs and serial

console logs, output from the

supportSave

command) for your switch support provider. Make

sure you identify what information was gathered before and after issuing the

firmwareDownload

command.