HP A5158A Fibre Channel Adapter Release Notes, August 2003

HP A5158A Fibre Channel Adapter Driver Release Notes
Known Problems and Workarounds (11i v1.0, v1.5, v2.0)
Chapter 112
Workaround or Fix: The user application may set the errno value to 0 immediately
before the call to HBA_OpenAdapter(). If the call returns 0, the application can verify if
there is a change in the errno value. If the errno value remains 0, the API has not set the
errno value due to any one of the above listed error scenarios. Otherwise, the errno value
set by the API may be interpreted as given in the programmer’s guide.
Example code:
HBA _HANDLE adapter_handle;
errno = 0;
adapter_handle = HBA_OpenAdapter(adapter_name);
if (adapter_handle == 0)
{
if (errno == 0)
{
printf(“HBA_OpenAdapter() failed - Error cause not available\n”);
}else
{
printf(“HBA_OpenAdapter() failed - errno set to %d\n”, errno);
}
}else
{
printf(“HBA_OpenAdapter() returned a handle of %u\n”, adapter_handle);
}
5. The following is a description of a problem that occurs with the Brocade 2800 switch. It is
not a problem with the A5158A adapter or software. We document it here for A5158A
customers who use Brocade switches in Fabric mode in a Public Loop topology.
Problem: In Fabric mode, when multiple hosts are connected on the same switch using a
hub (especially two hosts), FLOGI gets timed out when a host changes from Point-to-Point
to a Loop topology. This problem occurs with Fabric mode only and not with QuickLoop.
Fix: Use the telnet command, portCfgLport, to lock the port in loop mode (L_Port) when
multiple hosts or targets are connected on a single switch port. This command insures
that nport_id addresses will not change during temporary transitions and will not cause
any subsequent FLOGI time-outs. This problem is fixed in Brocade firmware revision
V2.1.9d and later releases.
The portCfgLport command is clearly documented in the Brocade release notes for
V2.1.9d and in the Brocade Man pages.
Dependencies
The following dependencies are not A5158A adapter problems, but you may encounter them
during installation or when booting the system. Therefore, they are listed as dependencies.