Inaccurate Information In The System Message Log; Recognizing The Port Initialization And Fcp Auto Discovery Process - HP AE370A - Brocade 4Gb SAN Switch 4/12 Administrator's Manual

5. You will need an adapter to run the loopback test for the SFP. Otherwise, run the portloopbacktest
on the marginal port using the loopback mode lb=5. Refer to the Fabric OS Command Reference
Manual for additional information.
Loopback mode
1
2
5
7
8
9
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 by inserting a new cable in to the suspected marginal port.
8. 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.
Refer to "Tracking and controlling switch
disabling track changes (TC).

Recognizing the port initialization and FCP auto discovery process

The steps in the port initialization process represent a protocol used to discover the type of connected
device and establish the port type. The possible port types are as follows:
U_Port—Universal FC port. This port type is the base Fibre Channel port type and all unidentified, or
•
uninitiated ports are listed as U_Ports.
• FL_PortFabric Loop port—This port connects both public and private loop devices.
• G_PortGeneric port—This port acts a transition port for non-loop fabric capable devices (E_Port /
F_Port).
• E_PortExpansion port—This port type is assigned to ISL links.
• F_PortFabric port—This port is assigned to fabric capable devices.
• EX_Port—A type of E_Port that connects a Fibre Channel router to an edge fabric. From the point of
view of a switch in an edge fabric, an EX_Port appears as a normal E_Port. It follows applicable Fibre
Channel standards as other E_Ports. However, the router terminates EX_Ports rather than allowing
different fabrics to merge as would happen on a switch with regular E_Ports.
300 Troubleshooting
Description
Port Loopback (loopback plugs)
External (SERDES) loopback
Internal (parallel) loopback (indicates no external
equipment)
Back-end bypass & port loopback
Back-end bypass & SERDES loopback
Back-end bypass & internal loopback
changes" on page 48 for information regarding enabling and