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

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

Firmware download issues

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

Page 56 highlights

Firmware Download Errors Symptom Probable cause and recommended action The AP blade is stuck in the "LOADING" state (issue slotShow to confirm). If the blade remains in the loading state for a significant period of time, the firmware download times out. Remove the blade and re-insert it. When it boots up, autoleveling is triggered and the firmware download is attempted again. Firmware download issues CAUTION After you start the firmware download process, do not enter any disruptive commands (such as reboot) that interrupt the process. The entire firmware download and commit process can take up to 30 minutes. If there is a problem, wait for the timeout (30 minutes for network problems) before issuing the firmwareDownload command again. Disrupting the process can render the switch inoperable and require you to seek help from your switch service provider. Do not disconnect the switch from power during the process because the switch could become inoperable when rebooted. The following symptoms describe common firmware download issues and their recommended actions. Symptom Probable cause and recommended action Firmware download times out. This can be caused by an excessively slow network. If it takes more than 30 minutes to download firmware on a switch, or on each CP in a director, the firmware download process times out. If a timeout occurs on a switch, the firmware download process synchronizes the two partitions on the switch by starting a firmware commit operation. If a timeout occurs in a director, the firmware download process synchronizes the firmware on the two partitions on the CP blades by starting a firmware commit operation on each CP. Wait at least 15 minutes for the commit operation to complete, then use the firmwareShow command to verify the partitions are synchronized. In some older versions of firmware, the firmware commit operation may not be started automatically on the switch (or on the standby CP in the director). In this case, you can enter the firmwareCommit command manually on the switch (or on the standby CP in the director) to synchronize the partitions. After the firmware commit operation completes, re-issue the firmwareDownload command to upgrade the system. Symptom Probable cause and recommended action Cannot upgrade directly to v8.0.1. If the switch is running Fabric OS v7.3.0 or earlier, you are not allowed to upgrade directly to v8.0.1 because of the "one-version" rule. Upgrade your switch to Fabric OS version v7.4.0 before upgrading to v8.0.1. The "oneversion" rule also applies to downgrading. Symptom Probable cause and recommended action Server is inaccessible or firmware path is invalid. NOTE The entire firmware directory must be loaded onto the USB device under the firmware directory prior to using the USB device for firmware download. Brocade Fabric OS Troubleshooting and Diagnostics Guide 56 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

Symptom

The AP blade is stuck in the "LOADING" state (issue

slotShow

to confirm).

Probable cause and recommended action

If the blade remains in the loading state for a significant period of time, the

firmware download times out. Remove the blade and re-insert it. When it

boots up, autoleveling is triggered and the firmware download is

attempted again.

Firmware download issues

CAUTION

After you start the firmware download process, do not enter any disruptive commands (such as reboot) that interrupt the

process. The entire firmware download and commit process can take up to 30 minutes. If there is a problem, wait for the time-

out (30 minutes for network problems) before issuing the firmwareDownload command again. Disrupting the process can

render the switch inoperable and require you to seek help from your switch service provider. Do not disconnect the switch from

power during the process because the switch could become inoperable when rebooted.

The following symptoms describe common firmware download issues and their recommended actions.

Symptom

Firmware download times out.

Probable cause and recommended action

This can be caused by an excessively slow network. If it takes more than

30 minutes to download firmware on a switch, or on each CP in a director,

the firmware download process times out. If a timeout occurs on a switch,

the firmware download process synchronizes the two partitions on the

switch by starting a firmware commit operation. If a timeout occurs in a

director, the firmware download process synchronizes the firmware on the

two partitions on the CP blades by starting a firmware commit operation

on each CP.

Wait at least 15 minutes for the commit operation to complete, then use

the

firmwareShow

command to verify the partitions are synchronized. In

some older versions of firmware, the firmware commit operation may not

be started automatically on the switch (or on the standby CP in the

director). In this case, you can enter the

firmwareCommit

command

manually on the switch (or on the standby CP in the director) to

synchronize the partitions. After the firmware commit operation

completes, re-issue the

firmwareDownload

command to upgrade the

system.

Symptom

Cannot upgrade directly to v8.0.1.

Probable cause and recommended action

If the switch is running Fabric OS v7.3.0 or earlier, you are not allowed to

upgrade directly to v8.0.1 because of the "one-version" rule. Upgrade your

switch to Fabric OS version v7.4.0 before upgrading to v8.0.1. The "one-

version" rule also applies to downgrading.

Symptom

Server is inaccessible or firmware path is invalid.

Probable cause and recommended action

NOTE

The entire firmware directory must be loaded onto the

USB device under the firmware directory prior to using

the USB device for firmware download.

Firmware Download Errors

Brocade Fabric OS Troubleshooting and Diagnostics Guide

53-1004126-01