Error Messages; Action Codes And Recommended Actions; Diagnostic Error Message Formats; Error Message Tables - IBM totalstorage 326 User Reference

Error messages

Action codes and recommended actions

Table 30 shows the action codes and the recommended action for each action code
listed in Table 31 on page 166.

Diagnostic error message formats

If any port fails during a diagnostic test, it is marked BAD in the status display.
To retest a port that has been marked BAD, clear the port and set to OK using the
diagClearError (port#) command. This command clears the port status only and
does not clear the logs or change the port's condition. The diagClearError (port#)
command should only be used during diagnostic procedures to reset a bad port for
retest.
Some messages contain the following abbreviations:
v sb: Should be
v er: Bits in error
Note: If you run the portStatsShow command or the diagShow command before

Error message tables

Table 31 on page 166 shows the diagnostic error messages, their descriptions and
probable causes. Each message has an error number (ERR#xxxx) associated with
it.
The command is entered with the following parameters:
v firstPort specifies the first port of range of ports to dump
information. The default, if no operand is specified, is to print the
state of port 0. If only firstPort is specified, only the information
for firstPort is printed.
v lastPort specifies the last port of range of ports to dump
information. If firstPort is specified, but lastPort is not specified, it
defaults to printing firstPort only for the port-based commands
(portShow, portRegShow, portRouteShow).
v numLog specifies the number of lines of portLogDump to print: 0
means dump all lines (default); N means dump the last N lines;
<0 means skip portLogDump.
Table 30. Hub action codes
Action number Recommended action
1, 3, 4 Replace the hub.
2 Further diagnostic action required. Failure can be system board,
GBIC, embedded optic, or cable. This is typically the result of
running a wrap test. The tests should be run again after swapping
cables and GBICs to determine cause. It is unlikely that the system
board is at fault as most system board failures cause a POST
failure.
running a test, errors may appear as a result of the normal synchronization
process. These errors should be addressed if the number of errors found
increases when running the portStatsShow command again.
Appendix E. Setup procedures and diagnostics for the Fibre Channel Hub
165