Emulex Driver for Windows and HBAnyware Situations
Table 15: Emulex Driver for Windows and HBAnyware Situations
Situation | Resolution |
|
| |
|
|
|
|
|
|
|
|
|
|
lputilnt Installs, but HBAnyware Does Not. | Perform the installation tasks in the following order: |
|
| |
When you run setupapps.exe, lputilnt installs | 1. Install the driver (see the Installation section of the Storport |
|
| |
but HBAnyware does not. You have | User Manual). |
|
| |
attempted to manually install the utilities for | 2. Install the utilities (see the Installation section of the |
|
| |
the driver before manually installing the driver |
|
| ||
Storport User Manual). |
|
| ||
|
|
|
| |
|
|
|
|
|
Emulex Driver for Solaris LPFC and HBAnyware Situations | ||||
Table 16: Emulex Driver for Solaris LPFC and HBAnyware Situations | ||||
|
|
|
| |
Situation |
| Resolution |
| |
|
|
|
| |
|
|
|
| |
The HBAnyware Utility Appears on |
| To prevent the HBAnyware utility from appearing on remote |
| |
Remote Servers in the SAN. |
| 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 |
| This is actually a symptom of two different problems. |
| |
servers via the Security Configurator or |
| • New Keys Were Generated While Servers Were Offline |
| |
the HBAnyware utility. |
| • Security Removed While Servers Were Offline |
| |
|
| See Table 22 on page 147 for details regarding these |
| |
|
| problems. |
| |
|
|
| ||
Emulex Driver for Linux and HBAnyware Situations | ||||
Table 17: Emulex Driver for Linux and HBAnyware Situations | ||||
|
| |||
Situation |
| Resolution |
| |
|
|
|
| |
|
|
|
| |
If a SAN configuration has 256 targets |
| Unload and reload the driver to reset available target IDs. |
| |
mapped by the lpfc driver, any additional |
| Ensure that the SAN configuration is correct prior to reloading |
| |
added targets do not get a target ID |
| the driver. This will clear the driver’s consistent binding table |
| |
mapping by the driver and cause target |
| and free target IDs for new target nodes. |
| |
discovery to fail. Removing targets or |
|
|
|
|
reinitializing the link does not solve the |
|
|
|
|
problem. |
|
|
|
|
|
|
|
|
|
The HBAnyware Utility User Manual | Page 138 |
