SAN device mapping errors
The errors that are most often generated during SAN device mapping can be related to SAN discovery, SAN device malfunction, libraries that are not valid, and other SAN-related issues.
ANR1745I: Unable to discover SAN devices. Function is busy.
This error message appears if there is another active SAN discovery.
The server is not able to perform SAN discovery. Try again after the other SAN discovery is completed.
ANR1786W, ANR1787W, or ANR1788W
- ANR1786W HBAAPI not able to get adapter name
- ANR1787W Not able to open adapter adaperName
- ANR1788W Not able to get the adapter attributes for adapterName
ANR1789W Get HBA target mapping failed
Error message ANR1789W is the most common HBAAPIn error on the SAN.
"Get HBA target mapping failed" means that the HBA encountered an error while gathering device mapping information by sending various SCSI commands.
ANR1790W SAN discovery failed
Error message ANR1790W is a general message that indicates that the HBAAPI function failed and cannot perform SAN discovery.
Verify that all SAN devices are working properly (for example, a SAN Data Gateway might be hung and might need rebooted). If all devices appear functional, verify that the firmware of device on the SAN, and the HBA driver, are at the appropriate levels.
ANR1791W HBAAPI wrapper library xxxxx failed to load or is missing
The HBAAPI wrapper library is used by the server to communicate with the SNIA HBAAPI.
- hbaapi.dll
- /usr/lib/libhbaapi.a (provided by AIX with HBAAPI installation)
- 32-bit: libhbaapi32.so
- 64-bit: libhbaapi64.so
- 64-bit: libhbaapi64.so
ANR1792W HBAAPI vendor library failed to load or is missing
Error message ANR1792W indicates that the vendor's library file failed to load. Verify the validity of the library files.
- C:\winnt\system32\qlsdm.dll (QlLogic's Windows file)
- /usr/lib/libHBAAPI.a (Emulex's AIX file)
- /usr/lib/libqlsdm.so (Qlogic's Linux file)
- /usr/lib/libemulexhbaapi.so (Emulex's Linux 32-bit file)
- /usr/lib64/libemulexhbaapi.so (Emulex's Linux 64-bit file)
- /usr/lib/libqlsdm.so (Qlogic's Oracle Solaris file)
- /opt/JNIsnia/Solaris/Jni/64bit/JniHbaLib.so (JNI's Oracle Solaris file)
ANR1793W Tivoli Storage Manager SAN discovery is not supported on this platform or this version of OS
- HP-UX
- 64-bit Windows 2003
- AIX versions that are not 52L or 53A. Support for SAN device mapping and device discovery on AIX requires either version 52L (fileset level of 5.2.0.50) or 53A (fileset level of 5.3.0.10) or higher.
ANR1794W Tivoli Storage Manager SAN discovery is disabled by options
Error message ANR1794W indicates that the SAN discovery on the server is disabled.
- setopt SANDISCOVERY OFF and setopt SANDISCOVERY PASSIVE
- These two commands disable the SAN discovery. The server is not able to correct the device path
automatically if the path was changed. This command only has to be issued one time.
The difference between the two commands is that SANDISCOVERY OFF polls the device and marks the inactive path offline. SANDISCOVERY PASSIVE does not poll the device and does not mark the inactive path offline.
- setopt SANDISCOVERY ON
- This command enables the SAN discovery. The SETOPT SANDISCOVERY ON command can be issued as many times as necessary.
- SANDISCOVERY OFF or SANDISCOVERY PASSIVE
- These two commands can disable the SAN discovery.
- SANDISCOVERY ON
- This command enables the SAN discovery.
Go to the Support Portal to verify the platform/HBA vendor/driver level support level before setting SANDISCOVERY ON to enable the SAN discovery.
To help with problem determination, you can use the dsmsanlist module to obtain information about devices on a storage area network (SAN). The dsmsanlist module is installed by default when the server or the storage agent is installed.
ANR2034E QUERY SAN: No match found using this criteria
Error message ANR2034E is issued when the server tries to collect configuration information for the SAN and finds nothing.
The result is that the server is unable to perform SAN discovery.
- The system or OS level is unsupported.
- This environment is not a SAN environment.
- There might be a problem with the SAN.
- HBAAPI might return the zero value of the number of HBAs on the system.
- HBAAPI might return the zero value of the number of devices on the system.
- Check the fibre-channel HBA driver and make sure that it is installed and enabled.
- Check the HBA driver level to make sure that it is up-to-date.
- Use the HBA vendor's utility to check for any reported fibre-channel link problems.
- Uninstall and then install the HBA driver. If there is an issue with the HBA configuration, device driver, or compatibility, sometimes uninstalling and reinstalling it corrects the problem.
- Check the fibre-channel cable connection to the HBA.
- Check the fibre-channel cable connection from the HBA to the SAN device (switch, data gateway, or other device).
- Check the Gigabit Inter-phase Converter (GBIC).
- On the SAN device (switch, data gateway, or other device) try a different target port. Sometimes the SAN devices might have a specific port failure.
- Halt the server, restart the system, and restart the server. If there were configuration changes in the SAN, sometimes the operating system, device driver, or HBA requires a system restart before they can communicate with the SAN.
- Recycle the destination port on the SAN device.
- Re-seat the HBA card.
- Replace the HBA.
ANR8226E Error detecting version of HBA-API library
Error message ANR8226E is only displayed for AIX.
The server attempted to determine the level of the devices.common.IBM.fc.hba-api fileset and encountered an error. Error message ANR8226E indicates that an error occurred while trying to detect the HBA-API libraryFileset version on AIX.
The result is that the server is not able to perform SAN discovery.
ANR8227E Fileset devices.common.IBM.fc.hba-api is not at the required level
- AIX52 - Need 5.2.0.50
- AIX53 - Need 5.3.0.10
The result is that the server is not able to perform SAN discovery.