Filter
Top Products
The HBAnyware Utility User Manual Page 138
Emulex Driver for Windows and HBAnyware Situations
Emulex Driver for Solaris LPFC and HBAnyware Situations
Emulex Driver for Linux and HBAnyware Situations
Table 15: Emulex Driver for Windows and HBAnyware Situations
Situation Resolution
lputilnt Installs, but HBAnyware Does Not.
When you run setupapps.exe, lputilnt installs
but HBAnyware does not. You have
attempted to manually install the utilities for
the driver before manually installing the driver
Perform the installation tasks in the following order:
1. Install the driver (see the Installation section of the Storport
User Manual).
2. Install the utilities (see the Installation section of the
Storport User Manual).
Table 16: Emulex Driver for Solaris LPFC and HBAnyware Situations
Situation Resolution
The HBAnyware Utility Appears on
Remote Servers in the SAN.
To prevent the HBAnyware utility from appearing on remote
servers in the SAN, disable the elxhbamgr process:
1. Navigate to /opt/hbanyware.
2. Run ./stop_hbanyware to stop both the elxhbamgr and
elxdiscovery processes.
3. Run ./start_elxhbamgr and ./start_elxdiscovery to restart
both processes.
Disabling this service or process prevents the local servers from
being seen remotely.
Cannot access formerly accessible
servers via the Security Configurator or
the HBAnyware utility.
This is actually a symptom of two different problems.
• New Keys Were Generated While Servers Were Offline
• Security Removed While Servers Were Offline
See Table 22 on page 147 for details regarding these
problems.
Table 17: 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 reloading
the driver. This will clear the driver’s consistent binding table
and free target IDs for new target nodes.