Home » HP Manuals » Servers » HP Brocade 8/12c » Manual Viewer

HP Brocade 8/12c Brocade Fabric OS Troubleshooting and Diagnostics Guide - Sup - Page 75

Troubleshooting the firmwareDownload command, Gathering additional information, USB error handling

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

Page 75 highlights

Troubleshooting the firmwareDownload command 5 Troubleshooting the firmwareDownload command 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, refer to the Fabric OS Message Reference for details about error messages. Also see, "Considerations for downgrading firmware" on page 56. 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 v6.3.0 on the primary and secondary partitions, and CP1 is running v7.0.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. USB error handling Table 11 outlines how the USB device handles errors under specific scenarios and details what actions you should take after the error occurs. Fabric OS Troubleshooting and Diagnostics Guide 55 53-1002150-02

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

Match case Limit results 1 per page

Fabric OS Troubleshooting and Diagnostics Guide

53-1002150-02

Troubleshooting the firmwareDownload command

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, refer to the

Fabric OS Message Reference

for

details about error messages. Also see,

“Considerations for downgrading firmware”

on page 56.

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 v6.3.0 on the primary and secondary partitions, and CP1 is

running v7.0.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.

USB error handling

Table 11

outlines how the USB device handles errors under specific scenarios and details what

actions you should take after the error occurs.