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

HP Brocade 8/12c Brocade Fabric OS Troubleshooting and Diagnostics Guide v6.2. - Page 128

Syslogd configuration

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

Page 128 highlights

13 Syslogd configuration The portLogDump command output (trace) is a powerful tool that is used to troubleshoot fabric issues. The portLogDump output provides detailed information about the actions and communications within a fabric. By understanding the processes that are taking place in the fabric, issues can be identified and located. The portLogDump command displays the port log, showing a portion of the Fibre Channel payload and header (FC-PH). The header contains control and addressing information associated with the frame. The payload contains the information being transported by the frame and is determined by the higher-level service or FC_4 upper level protocol. There are many different payload formats based on the protocol. Because a portLogDump output is long, a truncated example is presented: brcd300:admin> portlogdump time task event port cmd args Fri Feb 22 20:29:12 2008 20:29:12.638 FCPH write 3 40 00fffffd,00fffffd,00000000,00000000,00000000 20:29:12.638 FCPH seq 3 28 00300000,00000000,000005f4,00020182,0000000 20:29:12.638 PORT Tx 3 40 02fffffd,00fffffd,09a5ffff,14000000 20:29:12.638 FCPH write 9 40 00fffffd,00fffffd,00000000,00000000,00000000 20:29:12.638 FCPH seq 9 28 00300000,00000000,000005f4,00020182,00000000 20:29:12.639 PORT Tx 9 40 02fffffd,00fffffd,09a6ffff,14000000 20:29:12.639 PORT Rx 3 0 c0fffffd,00fffffd,09a50304,00000001 20:29:12.640 PORT Rx 9 0 c0fffffd,00fffffd,09a60305,00000001 20:29:20.804 PORT Rx 9 40 02fffffd,00fffffd,0306ffff,14000000 20:29:20.805 PORT Tx 9 0 c0fffffd,00fffffd,030609a7,00000001 20:29:20.805 FCPH read 9 40 02fffffd,00fffffd,d1000000,00000000,030609a7 20:29:20.805 FCPH seq 9 28 22380000,030609a7,00000608,0000001c,00000000 20:29:20.805 PORT Rx 3 40 02fffffd,00fffffd,02eeffff,14000000 20:29:20.806 PORT Tx 3 0 c0fffffd,00fffffd,02ee09a8,00000001 20:29:20.806 FCPH read 3 40 02fffffd,00fffffd,d2000000,00000000,02ee09a8 20:29:20.806 FCPH seq 3 28 22380000,02ee09a8,00000608,0000001c,00000000 20:29:32.638 FCPH write 3 40 00fffffd,00fffffd,00000000,00000000,00000000 20:29:32.638 FCPH seq 3 28 00300000,00000000,000005f4,00020182,00000000 20:29:32.638 PORT Tx 3 40 02fffffd,00fffffd,09a9ffff,14000000 20:29:32.638 FCPH write 9 40 00fffffd,00fffffd,00000000,00000000, 00000000 20:29:32.638 FCPH seq 9 28 00300000,00000000,000005f4,00020182,00000000 20:29:32.639 PORT Tx 9 40 02fffffd,00fffffd,09aaffff,14000000 Syslogd configuration The system logging daemon (syslogd) is an IP-based service for logging system messages made available by default on Unix and Linux operating systems. It is available as a third-party application for Windows operating systems. Fabric OS can be configured to use a UNIX-style syslogd process to forward system events and error messages to log files on a remote host system. The host system can be running UNIX, Linux, or any other operating system that supports the standard syslogd functionality. Fabric OS supports UNIX local7 facilities (the default facility level is 7). Configuring for syslogd involves configuring the host, enabling syslogd on the switch, and, optionally, setting the facility level. 112 Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-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
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	17
In this chapter	17
Troubleshooting overview	17
Network time protocol	17
Most common problem areas	18
Questions for common symptoms	18
Gathering information for your switch support provider	21
Setting up your switch for FTP	21
Capturing a supportSave	22
Capturing a supportShow	22
Capturing output from a console	22
Capturing command output	23
Building a case for your switch support provider	23
Basic information	23
Detailed problem information	24
Gathering additional information	25
General Issues	27
In this chapter	27
Licensing issues	27
Time issues	27
Switch message logs	28
Checking fan components	29
Checking the switch temperature	29
Checking the power supply	30
Checking the temperature, fan, and power supply	30
Switch boot issues	30
Fibre Channel Router connectivity	31
Generate and route an ECHO	31
Route and statistical information	33
Performance issues	35
Third party applications	36
Connections Issues	37
In this chapter	37
Port initialization and FCP auto discovery process	37
Link issues	39
Connection problems	39
Checking the logical connection	39
Checking the name server (NS)	40
Link failures	41
Determining a successful negotiation	42
Checking for a loop initialization failure	42
Checking for a point-to-point initialization failure	43
Correcting a port that has come up in the wrong mode	43
Marginal links	44
Troubleshooting a marginal link	44
Device login issues	45
Pinpointing problems with device logins	47
Media-related issues	50
Testing a port’s external transmit and receive path	50
Testing a switch’s internal components	50
Testing components to and from the HBA	51
Segmented fabrics	51
Reconciling fabric parameters individually	52
Downloading a correct configuration	52
Reconciling a domain ID conflict	53
Configuration Issues	55
In this chapter	55
Configupload and download issues	55
Gathering additional information	57
Brocade configuration form	58
FirmwareDownload Errors	59
In this chapter	59
Blade troubleshooting tips	59
Firmware download issues	60
Troubleshooting firmwareDownload	62
Gathering additional information	62
USB error handling	62
Considerations for downgrading firmware	63
Preinstallation messages	63
Blade types	64
Firmware versions	64
IP settings	65
Platform	65
Port settings	67
Routing	68
Zoning	68
Security Issues	69
In this chapter	69
Password issues	69
Password recovery options	70
Device authentication issues	70
Protocol and certificate management issues	71
Gathering additional information	71
SNMP issues	72
Gathering additional information	72
FIPS issues	72
Virtual Fabrics	75
In this chapter	75
General Virtual Fabric troubleshooting	75
Fabric identification issues	76
Logical Fabric issues	76
Base switch issues	77
Logical switch issues	78
Switch configuration blade compatibility	79
Gathering additional information	80
ISL Trunking Issues	81
In this chapter	81
Link issues	81
Buffer credit issues	82
Zone Issues	83
In this chapter	83
Overview of corrective action	83
Verifying a fabric merge problem	83
Verifying a TI zone problem	83
Segmented fabrics	84
Zone conflicts	85
Correcting a fabric merge problem quickly	86
Changing the default zone access	87
Editing zone configuration members	87
Reordering the zone member list	88
Checking for Fibre Channel connectivity problems	88
Checking for zoning problems	89
Gathering additional information	90
FCIP Issues	91
In this chapter	91
FCIP tunnel issues	91
FCIP links	93
Gathering additional information	94
Port mirroring	95
Supported hardware	95
Port mirroring considerations	96
Port mirroring management	97
FTRACE concepts	98
Fibre Channel trace information	98
FICON Fabric Issues	105
In this chapter	105
FICON issues	105
Troubleshooting FICON	106
General information to gather for all cases	106
Identifying ports	107
Single-switch topology checklist	108
Cascade mode topology checklist	108
Gathering additional information	108
Troubleshooting FICON CUP	109
Troubleshooting FICON NPIV	110
iSCSI Issues	111
In this chapter	111
Connectivity	111
Zoning	113
Authentication	114
Working With Diagnostic Features	115
In this chapter	115
About Fabric OS diagnostics	115
Diagnostic information	115
Power-on self test	116
Disabling POST	118
Enabling POST	118
Switch status	118
Viewing the overall status of the switch	118
Displaying switch information	119
Displaying the uptime for a switch	120
Chassis-level diagnostics	120
Spinfab and porttest	121
Port information	121
Viewing the status of a port	121
Displaying the port statistics	122
Displaying a summary of port errors for a switch	123
Equipment status	124
Displaying the status of the fans	124
Displaying the status of a power supply	125
Displaying temperature status	125
System message log	126
Displaying the system message log, with no page breaks	126
Displaying the system message log one message at a time	126
Clearing the system message log	126
Port log	127
Viewing the port log	127
Syslogd configuration	128
Configuring the host	129
Configuring the switch	129
Automatic trace dump transfers	130
Specifying a remote server	131
Enabling the automatic transfer of trace dumps	131
Setting up periodic checking of the remote server	131
Saving comprehensive diagnostic files to the server	131
Diagnostic tests not supported by M-EOS 9.6.2 and FOS 6.0	132
Switch Type	133
Hexadecimal	135

Match case Limit results 1 per page

112

Fabric OS Troubleshooting and Diagnostics Guide

53-1001187-01

Syslogd configuration

The

portLogDump

command output (trace) is a powerful tool that is used to troubleshoot fabric

issues. The

portLogDump

output provides detailed information about the actions and

communications within a fabric. By understanding the processes that are taking place in the fabric,

issues can be identified and located.

The

portLogDump

command displays the port log, showing a portion of the Fibre Channel payload

and header (FC-PH). The header contains control and addressing information associated with the

frame. The payload contains the information being transported by the frame and is determined by

the higher-level service or FC_4 upper level protocol. There are many different payload formats

based on the protocol.

Because a

portLogDump

output is long, a truncated example is presented:

brcd300:admin> portlogdump

time

task

event

port cmd

args

-------------------------------------------------

Fri Feb 22 20:29:12 2008

20:29:12.638 FCPH

write

00fffffd,00fffffd,00000000,00000000,00000000

20:29:12.638 FCPH

seq

00300000,00000000,000005f4,00020182,0000000

20:29:12.638 PORT

02fffffd,00fffffd,09a5ffff,14000000

20:29:12.638 FCPH

write

00fffffd,00fffffd,00000000,00000000,00000000

20:29:12.638 FCPH

seq

00300000,00000000,000005f4,00020182,00000000

20:29:12.639 PORT

02fffffd,00fffffd,09a6ffff,14000000

20:29:12.639 PORT

c0fffffd,00fffffd,09a50304,00000001

20:29:12.640 PORT

c0fffffd,00fffffd,09a60305,00000001

20:29:20.804 PORT

02fffffd,00fffffd,0306ffff,14000000

20:29:20.805 PORT

c0fffffd,00fffffd,030609a7,00000001

20:29:20.805 FCPH

read

02fffffd,00fffffd,d1000000,00000000,030609a7

20:29:20.805 FCPH

seq

22380000,030609a7,00000608,0000001c,00000000

20:29:20.805 PORT

02fffffd,00fffffd,02eeffff,14000000

20:29:20.806 PORT

c0fffffd,00fffffd,02ee09a8,00000001

20:29:20.806 FCPH

read

02fffffd,00fffffd,d2000000,00000000,02ee09a8

20:29:20.806 FCPH

seq

22380000,02ee09a8,00000608,0000001c,00000000

20:29:32.638 FCPH

write

00fffffd,00fffffd,00000000,00000000,00000000

20:29:32.638 FCPH

seq

00300000,00000000,000005f4,00020182,00000000

20:29:32.638 PORT

02fffffd,00fffffd,09a9ffff,14000000

20:29:32.638 FCPH

write

40 00fffffd,00fffffd,00000000,00000000, 00000000

20:29:32.638 FCPH

seq

00300000,00000000,000005f4,00020182,00000000

20:29:32.639 PORT

02fffffd,00fffffd,09aaffff,14000000

Syslogd configuration

The system logging daemon (syslogd) is an IP-based service for logging system messages made

available by default on Unix and Linux operating systems. It is available as a third-party application

for Windows operating systems.

Fabric OS can be configured to use a UNIX-style syslogd process to forward system events and error

messages to log files on a remote host system. The host system can be running UNIX, Linux, or any

other operating system that supports the standard syslogd functionality.

Fabric OS supports UNIX local7 facilities (the default facility level is 7). Configuring for syslogd

involves configuring the host, enabling syslogd on the switch, and, optionally, setting the facility

level.