Votes - 0, Average rating: 0
(
)
)
|
Other manuals for this model:
manual abstract
1.
To view the Emulex 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 Emulex SCSI Pass Thru Driver. The
first column, labelled DRV, lists the driver handles.
3.
Enter the drvcfg -s
is 20 (your driver handle may be different): Shell> drvcfg -s 20. Information is
displayed, listing all of the HBAs in your system; your listing may vary, depending
upon how many HBAs are installed in your system.
4.
Using the arrow keys, locate the HBA that you want to configure, select (i.e., highlight)
the corresponding row, and press Enter.
5.
Select (highlight) the Setup Utility option and press Enter.
6.
Select (highlight) the Configure HBA Parameters option and press Enter.
7.
Select (highlight) the Force Link Speed option and press Enter.
8.
Select (highlight) the 2Gb/s link speed option from the list presented, and press Enter.
9.
After completing your selection, use the ESC key to exit the EFI configuration menus.
•
Configuring an alternate path on the same 2-port HBA as the primary path
On midrange and high end Integrity servers, if the primary and alternate boot devices are
on the same Fibre Channel HBA port, an attempt to manually boot from the alternate device
will fail.
For example, if your primary and alternate paths are set as follows:
Primary bootpath: 0/0/10/1/0/4/0.8.0.255.0.7.0
Alternate bootpath: 0/0/10/1/0/4/0.8.0.255.0.0.0
This will set the primary and alternate bootpaths, but you will only be able to boot from the
primary path.
Corrective action:The issue can be resolved by following one of the following scenarios:
— From the EFI shell: Manually issue the EFI shell command reconnect —r, before
attempting to boot from the alternate path.
— Online: Use the HP-UX setboot command to swap the primary and alternate boot
devices.
— Hardware configuration: Reconfigure by moving the alternate boot device to a different
HBA
•
Using ioscan with krm not running
When ioscan is run with the —fn or —Fn option, and the kernel resource monitor (krm) is
not running, there could be stale krm device files in the system, which would correspond
to different devices, including fclp, in ioscan output. This issue has no impact on the
functionality of the Fibre Channel port; however, ioscan output may be confusing. This
issue can impact any card accessible with ioscan, and is not specific to the cards supported
by the fclp driver.
Corrective action:The ioscan output can be returned to normal by either deleting the stale
krm device files, or by starting krm, which will recreate the device files.
Compatibility and installation requirements
This section describes the compatibility information and installation requirements for this release.
For specific installation instructions, refer to the installation guide specific to your to your
FibreChannel card.
8
...
Network Equipment - HP-UX 11i v2 I/O Cards (285.65 kb)