Emulex 3.3 Frozen Dessert Maker User Manual


 
The HBAnyware Utility User Manual Page 120
Emulex Driver for Linux and HBAnyware Situations
Table 14: Emulex Driver for Linux and HBAnyware Situations
Situation Resolution
If a SAN configuration has 256 targets
mapped by the lpfc driver, any additional
added targets do not get a target ID
mapping by the driver and cause target
discovery to fail. Removing targets or
reinitializing the link does not solve the
problem.
Unload and reload the driver to reset available target IDs.
Ensure that the SAN configuration is correct prior to rebooting
the driver. This will clear the driver’s consistent binding table
and free target IDs for new target nodes.
In some cases, after loading an OEM
supplied combined firmware/OpenBoot
image you will not be able to enable
BootBIOS from the lputil Boot BIOS
Maintenance menu.
Should you encounter this problem after
loading the OEM combined firmware/
OpenBoot image, follow the steps outlined in
the resolution.
1. Download the current OpenBoot only image for your adapter
from the Emulex web site.
2. Load the current OpenBoot only image following steps listed
in Updating BootBIOS section of this manual.
3. Run lputil, return to Boot BIOS Maintenance menu.
4. Enable BootBIOS.
rmmod fails to unload lpfc driver module
due to ERROR: Module lpfc is in use.
This message can appear when you attempt
to remove the driver and there is a Logical
Volume Group dependent on the driver.
Make the Logical Volume Group unavailable.
Type: lvchange -a n xxxxxxx
where xxxxxx is the Volume Group Name.
LP1005DC-CM2 reported as the
LP1050DC. When running lspci or kudzu
utilities, you may see the Emulex FC Host
Adapter LP1005DC-CM2 reported as the
Emulex FC Host Adapter LP1050DC for the
pci_id address f0a5. This is due to a delay in
getting the pci_id tables updated in the Red
Hat and SuSE distributions.
None at this time.
An lspci will show recent Emulex HBAs
as "unknown". This is because of the delay
of getting new product ID's into the Red Hat
and SuSE development cycle.
None at this time.
Slow targets or extended link faults on the
storage side may result in storage being
marked off-line by the mid-layer and
remaining off-line (not recovered) when
the link faults are corrected.
This version of the driver should eliminate this problem.
However, should you experience off-line device issues, increase
the SCSI command timeout to a value greater than or equal to
sixty seconds. Emulex also provides a script which addresses
this issue (for 2.6 kernels). To access the lun_change_state.sh
script, click http://www.emulex.com/support/linux/index.jsp, then
click the link to the appropriate driver, and click the Linux tools
link.