HP StorageWorks Fabric OS 6.x administrator guide (5697-7344, March 2008)

322 Troubleshooting
6. Check the results of the loopback test and proceed as follows:
• If the loopback test failed, the port is bad. Replace the port blade.
• If the loopback test did not fail, the SFP was bad.
7. Optionally, to rule out cabling issues:
a. Insert a new cable in the suspected marginal port.
b. Enter the portErrShow command to determine if a problem still exists.
•If the portErrShow output displays a normal number of generated errors, the issue is solved.
•If the portErrShow output still displays a high number of generated errors, follow the
troubleshooting procedures for the Host or Storage device.
Inaccurate information in the system message log
In rare instances, events gathered by the track change feature can report inaccurate information to the
system message log.
For example, a user enters a correct user name and password, but the login was rejected because the
maximum number of users had been reached. However, when looking at the system message log, the login
was reported as successful.
If the maximum number of switch users has been reached, the switch will still perform correctly in that it will
reject the login of additional users (even if they enter correct user name and password information).
However, in this limited example, the Track Change feature will report this event inaccurately to the system
message log; it will appear that the login was successful. This scenario only occurs when the maximum
number of users has been reached; otherwise, the login information displayed in the system message log
should reflect reality.
See ”Tracking and controlling switch changes” on page 28 for information regarding enabling and
disabling track changes (TC).
Tracing Fibre Channel information
Frame Trace or FTRACE records user-defined messages and events on the Brocade FR4-18i and the 7500.
The portconfig command uses the ftrace option to capture trace information on a per FCIP tunnel
basis. You can configure up to eight FCIP tunnels on a single physical GE port. FTRACE is subject to the
same FCIP tunnel limitations, such as tunnel disruption, port of switch disable or enable, and reboot
requirements.
Tracing every FICON event affects performance. To avoid this, the default trace mask is set to
0x80000C7b. For troubleshooting, you should set the trace mask to 0-0xFFFFFFFF. The following table
describes the configurable FTRACE parameters.
8 Back-end bypass & SERDES loopback
9 Back-end bypass & internal loopback
Table 73 Loopback modes
Loopback mode Description
Table 74 FTRACE configurable parameters
Parameter Default Range Syntax
Auto check Out False T/F Boolean
Buffers 0 0-8 Integer
Display Mask 0xFFFF FFFF 0-0xFFFFFFFF Integer
Enable False T/F Boolean
Post Percentage 5 0-100 Integer