Home » HP Manuals » Hubs & Switches » HP AM866A » Manual Viewer

HP AM866A Brocade Troubleshooting and Diagnostics Guide v6.1.0 (53-1000853-01, - Page 55

Troubleshooting firmwareDownload, Gathering additional information, Brocade DCX error handling

UPC - 884420064602

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

Page 55 highlights

Troubleshooting firmwareDownload 5 Troubleshooting firmwareDownload A network diagnostic script and preinstallation check is a part of the firmwareDownload procedure. The script and preinstallation check performs troubleshooting and automatically checks for any blocking conditions. If the firmware download fails, see the Fabric OS Message Reference for details about error messages. Also see, "Considerations for downgrading firmware" on page 44. 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. 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. Then re-issue the firmwareDownload command to download the desired firmware version to both CPs. For example, if CP0 is running v5.2.0 on the primary and secondary partitions, and CP1 is running v5.0.1 on the primary and secondary partition, then synchronize them by issuing the firmwareDownload command. See the Fabric OS Message Reference for detailed information about .plist-related error messages. For more information on any of the commands in the Recommended Action section, see the Fabric OS Command Reference. NOTE Some of the messages include error codes (as shown in the example below). These error codes are for internal use only and you can disregard them. Example: 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. Brocade DCX error handling If an error occurs in the middle of a firmware download, the command will make sure the two partitions of a CF card have the same version of firmware. However, the main CPU and co-CPU may have different versions of firmware. Table 9 describes error handling at different steps of the firmware download process and the required action you need to perform. Fabric OS Troubleshooting and Diagnostics Guide 41 53-1000853-01

Section	Page
Contents	3
About This Document	9
In this chapter	9
How this document is organized	9
Supported hardware and software	10
What’s new in this document	10
Document conventions	11
Text formatting	11
Notes, cautions, and warnings	11
Key terms	12
Additional information	12
Brocade resources	12
Other industry resources	12
Getting technical help	13
Document feedback	14
Introduction to Troubleshooting	15
In this chapter	15
About troubleshooting	15
Network time protocol	15
Most common problem areas	16
Questions for common symptoms	16
Gathering information for your switch support provider	19
Setting up your switch for FTP	19
Capturing a supportSave	20
Capturing a supportShow	20
Capturing output from a console	20
Capturing command output	20
Building a case for your switch support provider	21
Basic switch information	21
Detailed problem information	21
Gathering additional information	23
General Issues	25
In this chapter	25
Licensing issues	25
Switch Message Logs	25
Checking fan components	26
Checking the switch temperature	27
Checking the power supply	27
Checking the temperature, fan, and power supply	27
Fibre Channel Routing	27
Checking for Fibre Channel connectivity problems	28
Third party applications	29
Connections Issues	31
In this chapter	31
Port initialization and FCP auto discovery process	31
Link issues	33
Connection problems	33
Checking the logical connection	33
Checking the name server (NS)	34
Link failures	35
Determining a successful negotiation	36
Checking for a loop initialization failure	36
Checking for a point-to-point initialization failure	37
Correcting a port that has come up in the wrong mode	37
Marginal links	38
Troubleshooting a marginal link	38
Device login issues	39
Pinpointing problems with device logins	41
Media-related issues	43
Testing a port’s external transmit and receive path	44
Testing a switch’s internal components	44
Testing components to and from the HBA	44
Segmented fabrics	45
Reconciling fabric parameters individually	45
Downloading a correct configuration	46
Reconciling a domain ID conflict	46
Configuration Issues	47
In this chapter	47
Configupload and download issues	47
Gathering additional information	49
Brocade configuration form	50
FirmwareDownload Errors	51
In this chapter	51
Blade troubleshooting tips	51
Firmware download issues	52
Troubleshooting firmwareDownload	55
Gathering additional information	55
Brocade DCX error handling	55
USB error handling	58
Considerations for downgrading firmware	58
Preinstallation messages	58
Blade types	59
Firmware versions	61
IP settings	62
Platform	63
Port settings	65
Routing	68
Zoning	68
Security Issues	71
In this chapter	71
Password issues	71
Password recovery options	72
Protocol and certificate management issues	72
Gathering additional information	73
SNMP issues	74
Gathering additional information	74
FIPS issues	74
ISL Trunking Issues	75
In this chapter	75
Link issues	75
Buffer credit issues	76
Zone Issues	77
In this chapter	77
Overview of corrective action	77
Verifying a fabric merge problem	77
Segmented fabrics	77
Zone conflicts	78
Correcting a fabric merge problem quickly	79
Editing zone configuration members	80
Reordering the zone member list	80
Checking for Fibre Channel connectivity problems	80
Checking for zoning problems	82
Gathering additional information	82
FCIP Issues	83
In this chapter	83
FCIP tunnel issues	83
FCIP links	85
Gathering additional information	86
Port mirroring	86
Supported hardware	87
Port mirroring considerations	88
Port mirroring management	89
FTRACE concepts	90
Tracing Fibre Channel information	90
FICON Fabric Issues	93
In this chapter	93
FICON issues	93
Troubleshooting FICON	94
General information to gather for all cases	94
Identifying ports	95
Single-switch topology checklist	96
Cascade mode topology checklist	96
Gathering additional information	96
Troubleshooting FICON CUP	97
Troubleshooting FICON NPIV	99
iSCSI Issues	101
In this chapter	101
Connectivity	101
Zoning	103
Authentication	104
Working With Diagnostic Features	105
In this chapter	105
About Fabric OS diagnostics	105
Diagnostic information	106
Power-on self test	106
Switch status	108
Viewing the overall status of the switch	108
Displaying switch information	109
Displaying the uptime for a switch	109
Port information	110
Viewing the status of a port	110
Displaying the port statistics	111
Displaying a summary of port errors for a switch	112
Equipment status	113
Displaying the status of the fans	113
Displaying the status of a power supply	113
Displaying temperature status	114
System message log	114
Displaying the system message log, with no page breaks	114
Displaying the system message log one message at a time	114
Clearing the system message log	115
Port log	115
Viewing the port log	115
Syslogd configuration	116
Configuring the host	117
Configuring the switch	117
Automatic trace dump transfers	118
Specifying a remote server	119
Enabling the automatic transfer of trace dumps	119
Setting up periodic checking of the remote server	119
Saving comprehensive diagnostic files to the server	119
Diagnostic tests not supported by M-EOS 9.6.2 and FOS 6.0	120
Switch Type	121
Hexidecimal	123

Match case Limit results 1 per page

Fabric OS Troubleshooting and Diagnostics Guide

53-1000853-01

Troubleshooting firmwareDownload

A network diagnostic script and preinstallation check is a part of the

firmwareDownload

procedure.

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

blocking conditions. If the firmware download fails, see the

Fabric OS Message Reference

for

details about error messages. Also see,

“Considerations for downgrading firmware”

on page 44.

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. 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.

Then re-issue the

firmwareDownload

command to download the desired firmware version to both

CPs. For example, if CP0 is running v5.2.0 on the primary and secondary partitions, and CP1 is

running v5.0.1 on the primary and secondary partition, then synchronize them by issuing the

firmwareDownload

command.

See the

Fabric OS Message Reference

for detailed information about .plist-related error messages.

For more information on any of the commands in the Recommended Action section, see the

Fabric

OS Command Reference

NOTE

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

for internal use only and you can disregard them.

Example:

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.

Brocade DCX error handling

If an error occurs in the middle of a firmware download, the command will make sure the two

partitions of a CF card have the same version of firmware. However, the main CPU and co-CPU may

have different versions of firmware.

Table 9

describes error handling at different steps of the

firmware download process and the required action you need to perform.