Votes - 0, Average rating: 0
(
)
)
|
Other manuals for this model:
manual abstract
•
Private Loop and Public Loop topology configuration support for Fibre Channel mezzanine
adapters
Private Loop and Public Loop topology configurations are not supported for Fibre Channel
mezzanine adapters on HP Integrity Blade servers in combination with the Fibre Channel (FC)
Pass Thru I/O Interconnect modules. These configurations can result in servers losing connection
to the Storage Area Network (SAN) during mezzanine adapter initialization, and SAN boot
may fail in such configurations.
It is strongly recommended that customers not use loop topology configurations for mezzanine
adapters in conjunction with FC Pass Thru I/O interconnect modules. Customers are advised
to use Point-to-Point Fabric topology configuration with mezzanine adapters.
For additional information, please refer to HP Customer Advisory Document c02985353.
•
Adding a new path to a LUN seen through FibrChanl-01 (fcd) driver can cause IOs pending
with the driver for the LUN to stop for R_A_TOV period
R_A_TOV stands for Resource Allocation Time Out Value (refer to FC-FS-3 21.3.5 for details).
The default value of R_A_TOV is 10 seconds.
On an 11iv3 host, when I/Os are in progress to a LUN and a new LUN path is added, the
mass storage stack issues a “abort-task-set” SCSI Task Management request on all existing
paths to the LUN. This causes the underlying FibrChanl-01 (fcd) driver to abort all I/Os to the
LUN. The new path addition completes only after all the aborted I/Os and the SCSI Task
Management request are returned by the underlying FibrChanl-01 (fcd) driver.
In aborting an I/O that is active with a Fibre Channel target device, the FibrChan-01 (fcd)
driver must wait for a period equal to the value of R_A_TOV before returning the I/O with
aborted status to the mass storage stack. This means the new path addition and subsequent
retry of I/O is delayed for a period equal to the value of R_A_TOV. This could result in
applications that access the LUN experiencing I/O timeouts during new LUN path addition.
Note that any I/Os that are not active with the Fibre Channel target are aborted immediately
by the driver. To avoid a R_A_TOV delay and possible IO timeout scenarios it is necessary
to ensure that there are no IOs pending to the LUN at the time of new LUN path addition. It
may be necessary to temporarily suspend application(s) using the LUN in order to stop all IOs
to LUN for the duration of the new LUN path addition.
•
EFI boot fails when connected to an Arbitrated Loop device
This applies to HP 8Gb and 4Gb Dual Port QLogic Mezzanine HBAs (part numbers
451871–B21 and 403619–B21). The solution is to set the HBA Connection Mode of the
adapter port to Loop Preferred, Otherwise Point to Point, by using the drvcfg
-s command at the EFI shell prompt:
1.
To view the QLogic driver handle information, type Shell> drivers at the EFI shell
prompt; a list of drivers is displayed.
2.
Write down the driver handle associated with the HP Fibre Channel Driver. The
first column, labeled DRV, lists the driver handles. There may be one or more driver
instances listed. Select the DRV corresponding to the adapter port connected to the
Arbitrated Loop device.
3.
Enter the drvcfg
20 (your driver handle may be different): Shell> drvcfg 20. Take note of the controller
handle number inside the brackets, labeled as Ctlr[] .
4.
Enter the drvcfg -s
Driver Configuration Main Menu will be displayed.
5.
Under NVRAM Parameters section, press 1 to select Edit Adapter Settings
option.
6.
Press 7 to select the Connection Option.
7.
Press 3 to select Loop Preferred, Otherwise Point to Point option.
Known problems and limitations
9
...
Network Equipment - HP-UX 11i v3 I/O Cards (311.96 kb)