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

You might see error messages ANR1786W, ANR1787W, or ANR1788W when there is a problem with SAN discovery. The following three messages usually indicate that the HBAAPI library is not working in general:

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

If the result is that the server is unable to perform SAN discovery, go to the Support Portal to verify that the host bus adapter (HBA) driver is up-to-date and at a supported level.

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.

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 the firmware of device on the SAN, and the HBA driver, are at the appropriate levels. If the result is that the server is not able to perform SAN discovery, go to the Support Portal to verify that the HBA driver is up-to-date and at a supported level.

Tip: For IBM tape devices, make sure that the latest firmware is installed. Firmware before 4772 for IBM 3580 tape devices causes problems with Qlogic HBAAPI.

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.

Tip: For IBM tape devices, make sure that the latest firmware is installed. Firmware before 4772 for IBM 3580 tape devices causes problems with Qlogic HBAAPI.

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.

The HBAAPI wrapper libraries are in the same directory as the Tivoli® Storage Manager executable file (unless the full path is given as shown below). The following list shows the HBA wrapper files that are shipped with the server package (except on AIX® and Linux zSeries). Error message ANR1791W indicates that the HBAAPI wrapper file is either missing or might not be loaded by the Tivoli Storage Manager. Verify that the wrapper file is in the same directory as the Tivoli Storage Manager executable file. The HBAAPI wrapper library files are shown in the following list:

hbaapi.dll
/usr/lib/libhbaapi.a (provided by AIX with HBAAPI installation)
32-bit: libhbaapi32.so
64-bit: libhbaapi64.so
64-bit: libhbaapi64.so

The result is that the server is not able to perform SAN discovery.

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.

AIX, HP-UX, Linux, or Oracle Solaris systems (except on Linux zSeries) store their HBAAPI libraries in the location that is specified by the /etc/hba.conf file. Windows files are stored in the C:\winnt\system32 directory. The following examples are of vendor 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)

The result is that the server is not able to perform SAN discovery.

ANR1793W Tivoli Storage Manager SAN discovery is not supported on this platform or this version of OS

Error message ANR1793W is only displayed if the Tivoli Storage Manager attempts a SAN device mapping or device discovery operation on an unsupported operating system. The following operating systems are not currently supported by SAN device mapping or device discovery:

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.

The result is that the server is not able to perform SAN discovery.

ANR1794W Tivoli Storage Manager SAN discovery is disabled by options

Error message ANR1794W indicates that the SAN discovery on the server is disabled.

The SAN discovery can be disabled or enabled by issuing the following server commands:

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.

Another way to disable/enable SAN discovery is to put the following option in the dsmserv.opt file:

SANDISCOVERY OFF or SANDISCOVERY PASSIVE: These two commands can disable the SAN discovery.
SANDISCOVERY ON: This command enables the SAN discovery.

SANDISCOVERY is defaulted to ON.

Go to the Support Portal to verify the platform/HBA vendor/driver level support level before setting SANDISCOVERY ON to enable the SAN discovery.

AIX operating systems Linux operating systems Oracle Solaris operating systems 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 following are possible reasons for not finding information about the SAN:

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.

Perform the following tasks to find the SAN configuration information:

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

Due to problems in AIX HBAAPI code, the minimum fileset devices.common.IBM.fc.hba-api levels needed for successful SAN discovery are shown in the following list:

AIX52 - Need 5.2.0.50
AIX53 - Need 5.3.0.10

The server specified that the file set devices.common.IBM.fc.hba-api is at a level that is incompatible with Tivoli Storage Manager operations. Install the latest maintenance for this file set if you use SAN devices.

The result is that the server is not able to perform SAN discovery.