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

HP Brocade 8/12c Fabric OS Troubleshooting and Diagnostics Guide v6.4.0 (53-10 - Page 28

Software Fault:Software Watchdog, Software Fault:Kernel Panic

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

Page 28 highlights

2 Switch boot issues • reboot • haFailover • fastBoot • firmwareDownload The RRD feature is activated and halts rebooting when an unexpected reboot reason is shown continuously in the reboot history within a certain period of time. The period of time is switch dependent. The following are considered unexpected reboots: • Reset A reset reboot may be caused by one of the following: - Power-cycle of the switch or CP. - Linux reboot command. - Hardware watchdog timeout. - Heartbeat loss related reboot. • Software Fault:Kernel Panic - If the system upon detecting an internal fatal error from which it cannot safely recover, generally it will output an error message to the console, dump a stack trace for debugging and then performs an automatic reboot. - After a kernel panic, the system may not have enough time to write the reboot reason causing the reboot reason to be empty. This is treated as an Unknown/reset case. • Software fault - Software Fault:Software Watchdog - Software Fault:ASSERT. • Software recovery failure This is an HA bootup related issue and happens when switch is unable to recover to a stable state. HASM log contains more detail and specific information on this type of failure, such as one of the following: - Failover recovery failed: This occurs when failover recovery failed and has to reboot the CP. - Failover when standby CP unready: Occurs when the active CP has to failover, but the standby CP is not ready to takeover mastership. - Failover when LS trans incomplete: Takes place when a logical switch transaction is incomplete. • Software bootup failure This is an HA bootup related issue and happens when a switch is unable to load the firmware to a usable state. HASM log contains more detail and specific information on this type of failure, such as one of the following: - System bring up timed out: The CP failed to come up within the time allotted. - LS configuration timed out and failed: Logical switch configuration failed and timed out. After RRD is activated, admin level permission is required to login enter the supportShow or supportSave command to collect a limited amount of data to resolve the issue. ATTENTION The limited supportSave used with the RRD feature does not support USB. 14 Fabric OS Troubleshooting and Diagnostics Guide 53-1001769-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	21
Building a case for your switch support provider	21
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
Rolling Reboot Detection	27
FC-FC routing connectivity	29
Generate and route an ECHO	29
Superping	31
Route and statistical information	34
Performance issues	35
Connectivity Issues	37
In this chapter	37
Port initialization and FCP auto discovery process	37
Link issues	39
Connection problems	39
Checking the physical connection	39
Checking the logical connection	40
Checking the Name Server (NS)	40
Link failures	42
Determining a successful speed negotiation	42
Checking for a loop initialization failure	43
Checking for a point-to-point initialization failure	43
Correcting a port that has come up in the wrong mode	44
Marginal links	44
Troubleshooting a marginal link	45
Device login issues	47
Pinpointing problems with device logins	47
Media-related issues	49
Testing a port’s external transmit and receive path	50
Testing a switch’s internal components	50
Testing components to and from the HBA	50
Segmented fabrics	51
Reconciling fabric parameters individually	52
Downloading a correct configuration	52
Reconciling a domain ID conflict	52
Reconciling incompatible software features	54
Port mirroring	54
In-Order Delivery	54
Port mirroring considerations	55
Supported platforms	56
Maximum mirror connections	56
Configuring a port to be a mirror port	57
Adding a port mirror connection	58
Deleting a port mirror connection	58
Displaying port mirror connections	59
Configuration Issues	61
In this chapter	61
Configupload and download issues	61
Gathering additional information	64
Brocade configuration form	65
FirmwareDownload Errors	67
In this chapter	67
Blade troubleshooting tips	67
Firmware download issues	68
Troubleshooting firmwareDownload	71
Gathering additional information	71
USB error handling	71
Considerations for downgrading firmware	72
Preinstallation messages	72
Blade types	74
Firmware versions	75
Platform	75
Routing	76
Security Issues	77
In this chapter	77
Password issues	77
Password recovery options	78
Device authentication issues	78
Protocol and certificate management issues	79
Gathering additional information	79
SNMP issues	80
Gathering additional information	80
FIPS issues	80
Virtual Fabrics	83
In this chapter	83
General Virtual Fabric troubleshooting	83
Fabric identification issues	84
Logical Fabric issues	84
Base switch issues	85
Logical switch issues	86
Switch configuration blade compatibility	87
Gathering additional information	88
ISL Trunking Issues	89
In this chapter	89
Link issues	89
Buffer credit issues	90
Zone Issues	91
In this chapter	91
Overview of corrective action	91
Verifying a fabric merge problem	91
Verifying a TI zone problem	91
Segmented fabrics	92
Zone conflicts	93
Correcting a fabric merge problem quickly	94
Changing the default zone access	95
Editing zone configuration members	95
Reordering the zone member list	95
Checking for Fibre Channel connectivity problems	96
Checking for zoning problems	97
Gathering additional information	98
Working With Diagnostic Features	99
In this chapter	99
About Fabric OS diagnostics	99
Diagnostic information	99
Power-on self test	100
Disabling POST	102
Enabling POST	102
Switch status	102
Viewing the overall status of the switch	102
Displaying switch information	103
Displaying the uptime for a switch	104
SpinFab and portTest	104
Debugging spinFab errors	105
Clearing the error counters	107
Enabling a port	107
Disabling a port	107
Port information	108
Viewing the status of a port	108
Displaying the port statistics	109
Displaying a summary of port errors for a switch	110
Equipment status	111
Checking the temperature, fan, and power supply	111
Checking the status of the fans	111
Checking the status of a power supply	112
Checking temperature status	112
System message log	113
Displaying the system message log, with no page breaks	113
Displaying the system message log one message at a time	114
Clearing the system message log	114
Port log	114
Viewing the port log	114
Syslogd configuration	116
Configuring the host	116
Configuring the switch	116
Automatic trace dump transfers	117
Specifying a remote server	118
Enabling the automatic transfer of trace dumps	118
Setting up periodic checking of the remote server	118
Saving comprehensive diagnostic files to the server	118
Switch Type and Blade ID	119
Hexadecimal	123
Example of hexadecimal triplet conversion	123

Match case Limit results 1 per page

Fabric OS Troubleshooting and Diagnostics Guide

53-1001769-01

Switch boot issues

•

reboot

•

haFailover

•

fastBoot

•

firmwareDownload

The RRD feature is activated and halts rebooting when an unexpected reboot reason is shown

continuously in the reboot history within a certain period of time. The period of time is switch

dependent. The following are considered unexpected reboots:

•

Reset

A reset reboot may be caused by one of the following:

Power-cycle of the switch or CP.

Linux reboot command.

Hardware watchdog timeout.

Heartbeat loss related reboot.

•

Software Fault:Kernel Panic

If the system upon detecting an internal fatal error from which it cannot safely recover,

generally it will output an error message to the console, dump a stack trace for debugging

and then performs an automatic reboot.

After a kernel panic, the system may not have enough time to write the reboot reason

causing the reboot reason to be empty. This is treated as an Unknown/reset case.

•

Software fault

Software Fault:Software Watchdog

Software Fault:ASSERT.

•

Software recovery failure

This is an HA bootup related issue and happens when switch is unable to recover to a stable

state. HASM log contains more detail and specific information on this type of failure, such as

one of the following:

Failover recovery failed: This occurs when failover recovery failed and has to reboot the CP.

Failover when standby CP unready: Occurs when the active CP has to failover, but the

standby CP is not ready to takeover mastership.

Failover when LS trans incomplete: Takes place when a logical switch transaction is

incomplete.

•

Software bootup failure

This is an HA bootup related issue and happens when a switch is unable to load the firmware

to a usable state. HASM log contains more detail and specific information on this type of

failure, such as one of the following:

System bring up timed out: The CP failed to come up within the time allotted.

LS configuration timed out and failed: Logical switch configuration failed and timed out.

After RRD is activated, admin level permission is required to login enter the

supportShow

supportSave

command to collect a limited amount of data to resolve the issue.

ATTENTION

The limited

supportSave

used with the RRD feature does not support USB.