User manual HP, model HP 41B 4Gb 1-port PCIe Fibre Channel Host Bus Adapter

Manafacture: HP
File size: 153.08 kb
File name:

Language of manual:

Free link for this manual available at the bottom of the page

Other manuals for this model:

Media Storage - HP 41B 4Gb 1-port PCIe Fibre Channel Host Bus Adapter (1.25 mb)

Media Storage - HP 41B 4Gb 1-port PCIe Fibre Channel Host Bus Adapter (301.79 kb)

Media Storage - HP 41B 4Gb 1-port PCIe Fibre Channel Host Bus Adapter (2.03 mb)

Media Storage - HP 41B 4Gb 1-port PCIe Fibre Channel Host Bus Adapter (843.46 kb)

Show all

manual abstract

Manual rescan
When a server conﬁgured with MultiPulse ﬁrst boots, MultiPulse automatically recognizes up to four
physical paths and associates them with the same virtual device. However, after the initial conﬁguration,
MultiPulse does not recognize a new physical path that comes online to an already conﬁgured LUN.
To enable MultiPulse to recognize the new physical path, you must perform a manual rescan using
the hp_rescan utility.
To manual y rescan:
1. Ensure that the fibreutils RPM is instal ed on your system.
2. Enter the following command:
hp_rescan –a
New default per LUN queue depth
For new installations, the default per LUN queue depth for Emulex HBAs on Linux systems has been
changed to 16. Note that this affects new installations only, and does not affect upgrades. For upgrades,
the current setting for queue depth is retained.
Restrictions
This section describes MultiPulse restrictions.
• MultiPulse does not support older ﬁrmware on HP storage arrays. These storage arrays are
known as active-passive storage arrays since not all paths are active on the fabric at the same
time. These arrays include:
• MSA1000 and MSA1500 running 4.x or 5.x ﬁrmware
• EVA3000 and EVA5000 running VCS 3.x
• If using MultiPulse 2.1.x, you can have a maximum of four physical paths to a LUN. More than
four paths can cause improper failure.
• If using MultiPulse 2.2.x, you can have a maximum of eight physical paths to a LUN. More
than eight paths can cause improper failure.
• MultiPulse can coexist with multipathing products such as QLogic® failover driver, Secure Path, or
Device Mapper. However, note that MultiPulse only works with Emulex-based HBAs; it will not
conﬁgure multiple paths for other HBAs in the system.
• When using MultiPulse with SUSE Linux systems in Boot from SAN conﬁgurations, HP recommends
that you use the Udev utility to ensure that your system successfully boots. For detailed information
about this procedure, see "Using the Udev utility with SUSE Linux systems" in the Booting
Itanium Linux systems from a storage area network application notes, available on the website
ht p://h18006.www1.hp.com/storage/saninfrastructure.html.
• XP LUNs presented to Linux hosts must start with LUN 0.
• HP recommends that you implement zoning with HBA, as described in the HP StorageWorks SAN
design reference guide, available on the websiteht p://h18006.www1.hp.com/products/
storageworks/san/documentation.html
• HBAnyware:
• Emulex HBAs may not appear in HBAnyware due to a conﬂict between library entries in
/etc/hba.conf. After installing HBAnyware, run the following script from the HP driver
kit to correct the problem:
/opt/hp/hp-lpfc/remove_lpfc_hbaconf_entry.sh
MultiPulse failover driver for Linux application notes
7