Home » HP Manuals » Storage Devices » HP StorageWorks 1606 » Manual Viewer

HP StorageWorks 1606 Brocade Fabric OS Troubleshooting and Diagnostics Guide v - Page 59

Gathering additional information, USB error handling, Considerations for downgrading firmware

View all HP StorageWorks 1606 manuals

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

Page 59 highlights

USB error handling 5 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 The following table outlines how the USB device handles errors under specific scenarios and details what actions you should take after the error occurs. TABLE 9 USB error handling Scenario under which download fails Error handling Action An access error occurs during firmwaredownload because the removal of the USB device, or USB device hardware failure, etc. USB device is not enabled. Firmwaredownload will timeout and commit will be started to repair the partitions of the CPUs that are affected. See previous table for details. None. Firmwaredownload will fail with Enable the USB device using the an error message usbStorage -e command and retry firmwaredownload. Considerations for downgrading firmware The pre-installation check of the firmwareDownload command detects all of the blocking conditions that can prevent a successful downgrade, and warns you about all these conditions. The error messages displayed by the firmwareDownload command states the blocking conditions and the corresponding commands to correct them. You must address all of these blocking conditions before proceeding. Refer to the Fabric OS Administrator's Guide for more information regarding individual features and commands. To avoid failure of a firmware downgrade, verify the firmware you are downgrading to supports all the blades in the chassis, and that the switch, blades, or chassis supports all the features you are currently using. If not, you will need to disable or remove those features that are not supported. Preinstallation messages The messages in this section are displayed if an exception case is encountered during firmware download. The following example shows feature-related messages that you may see if you were upgrading from v6.1.0 to v6.3.0: Cannot upgrade directly to 6.3. Please upgrade to 6.2 first and then upgrade to 6.3. Fabric OS Troubleshoot and Diagnostics Guide 45 53-1001340-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
Command syntax conventions	11
Command examples	12
Notes, cautions, and warnings	12
Key terms	12
Additional information	13
Brocade resources	13
Other industry resources	13
Getting technical help	13
Document feedback	14
Introduction to Troubleshooting	15
In this chapter	15
Troubleshooting overview	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	19
Capturing output from a console	20
Capturing command output	20
Building a case for your switch support provider	20
Basic information	21
Detailed problem information	22
Gathering additional information	23
General Issues	25
In this chapter	25
Licensing issues	25
Time issues	25
Switch message logs	26
Switch boot issues	27
FC-FC Routing connectivity	27
Generate and route an ECHO	27
Route and statistical information	29
Performance issues	31
Connectivity Issues	33
In this chapter	33
Port initialization and FCP auto discovery process	33
Link issues	35
Connection problems	35
Checking the physical connection	35
Checking the logical connection	36
Checking the Name Server (NS)	36
Link failures	38
Determining a successful speed negotiation	38
Checking for a loop initialization failure	39
Checking for a point-to-point initialization failure	39
Correcting a port that has come up in the wrong mode	40
Marginal links	40
Troubleshooting a marginal link	41
Device login issues	43
Pinpointing problems with device logins	43
Media-related issues	45
Testing a port’s external transmit and receive path	46
Testing a switch’s internal components	46
Testing components to and from the HBA	46
Segmented fabrics	47
Reconciling fabric parameters individually	47
Downloading a correct configuration	48
Reconciling a domain ID conflict	48
Configuration Issues	51
In this chapter	51
Configupload and download issues	51
Gathering additional information	53
Brocade configuration form	54
FirmwareDownload Errors	55
In this chapter	55
Blade troubleshooting tips	55
Firmware download issues	56
Troubleshooting firmwareDownload	58
Gathering additional information	59
USB error handling	59
Considerations for downgrading firmware	59
Preinstallation messages	59
Blade types	60
Firmware versions	61
Platform	61
Routing	62
Security Issues	63
In this chapter	63
Password issues	63
Password recovery options	64
Device authentication issues	64
Protocol and certificate management issues	65
Gathering additional information	65
SNMP issues	66
Gathering additional information	66
FIPS issues	66
Virtual Fabrics	69
In this chapter	69
General Virtual Fabric troubleshooting	69
Fabric identification issues	70
Logical Fabric issues	70
Base switch issues	71
Logical switch issues	72
Switch configuration blade compatibility	73
Gathering additional information	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
Verifying a TI zone problem	77
Segmented fabrics	78
Zone conflicts	79
Correcting a fabric merge problem quickly	80
Changing the default zone access	81
Editing zone configuration members	81
Reordering the zone member list	81
Checking for Fibre Channel connectivity problems	82
Checking for zoning problems	83
Gathering additional information	84
iSCSI Issues	85
In this chapter	85
Connectivity	85
Zoning	87
Authentication	88
Working With Diagnostic Features	89
In this chapter	89
About Fabric OS diagnostics	89
Diagnostic information	89
Power-on self test	90
Disabling POST	92
Enabling POST	92
Switch status	92
Viewing the overall status of the switch	92
Displaying switch information	93
Displaying the uptime for a switch	94
SpinFab and portTest	94
Port information	95
Viewing the status of a port	95
Displaying the port statistics	96
Displaying a summary of port errors for a switch	97
Equipment status	98
Checking the temperature, fan, and power supply	98
Checking the status of the fans	99
Checking the status of a power supply	99
Checking temperature status	100
System message log	100
Displaying the system message log, with no page breaks	101
Displaying the system message log one message at a time	101
Clearing the system message log	101
Port log	101
Viewing the port log	101
Syslogd configuration	103
Configuring the host	103
Configuring the switch	103
Automatic trace dump transfers	104
Specifying a remote server	105
Enabling the automatic transfer of trace dumps	105
Setting up periodic checking of the remote server	105
Saving comprehensive diagnostic files to the server	105
Switch Type	107
Hexadecimal	109

Match case Limit results 1 per page

Fabric OS Troubleshoot and Diagnostics Guide

53-1001340-01

USB error handling

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

The following table outlines how the USB device handles errors under specific scenarios and

details what actions you should take after the error occurs.

Considerations for downgrading firmware

The pre-installation check of the

firmwareDownload

command detects all of the blocking

conditions that can prevent a successful downgrade, and warns you about all these conditions. The

error messages displayed by the

firmwareDownload

command states the blocking conditions and

the corresponding commands to correct them. You must address all of these blocking conditions

before proceeding. Refer to the

Fabric OS Administrator’s Guide

for more information regarding

individual features and commands.

To avoid failure of a firmware downgrade, verify the firmware you are downgrading to supports all

the blades in the chassis, and that the switch, blades, or chassis supports all the features you are

currently using. If not, you will need to disable or remove those features that are not supported.

Preinstallation messages

The messages in this section are displayed if an exception case is encountered during firmware

download. The following example shows feature-related messages that you may see if you were

upgrading from v6.1.0 to v6.3.0:

Cannot upgrade directly to 6.3. Please upgrade to 6.2 first and then upgrade

to 6.3.

TABLE 9

USB error handling

Scenario under which download fails

Error handling

Action

An access error occurs during

firmwaredownload because the

removal of the USB device, or USB

device hardware failure, etc.

Firmwaredownload will timeout

and commit will be started to

repair the partitions of the CPUs

that are affected. See previous

table for details.

None.

USB device is not enabled.

Firmwaredownload will fail with

an error message

Enable the USB device using the

usbStorage -e

command and retry

firmwaredownload.