HP Brocade 4Gb SAN Switch for HP BladeSystem p-Class - Manual (Page 200)

200 Troubleshooting
7. Optionally, to rule out cabling issues:
a. Insert a new cable in to the suspected marginal port.
b. Issue 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 performs correctly in that it rejects the
login of additional users (even if they enter correct user name and password information).
However, in this limited example, the Track Change feature reports this event inaccurately to the system
message log; it appears 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.
For information regarding enabling and disabling Track Changes (TC), see ” Tracking and controlling
switch changes ” on page 35.
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:
The HP FCP auto discovery process enables private storage devices that accept PRLI to communicate in a
fabric.
If device probing is enabled, the embedded port PLOGIs and attempts a PRLI into the device to retrieve
information to enter into the Name Server. This enables private devices that do not FLOGI but accept PRLI
to be entered in the Name Server and receive full fabric citizenship. Private devices that accept PRLI
represent a majority of storage targets. Private hosts require the QuickLoop feature, which is not available
in Fabric OS v4.0.0 or later.
A fabric-capable device implicitly registers information with Name Server during a FLOGI. These devices
typically register information with the Name Server before querying for a device list. The embedded port
still PLOGIs and attempts PRLI with these devices.
• 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_Port Fabric Loop port. This port connects both public and private loop devices.
• G_Port Generic port. This port acts a transition port for non-loop fabric capable devices (E_Port
/ F_Port).
• E_Port Expansion port. This port type is assigned to ISL links.
• F_Port Fabric port. This port is assigned to fabric capable devices.