Troubleshooting the sensor

This topic describes common problems that occur with the Host storage sensor and presents solutions for those problems.

Commands fail because of insufficient privileges

Problem: Command failures occurred due to permissions denied errors and are recorded in the log files.
Solution: Verify that the commands that require privilege escalation are configured correctly.

Problem: The discovery takes a long time to run.
Solution: Check whether the StorageSensor sensor is enabled and disable it. If both sensors are enabled, some of the storages resources are discovered twice.

Problem: Host storage data is not discovered.
Solution: Verify that the vendor's host bus adapter (HBA) API library files are installed and configured correctly on the host system. Missing library files might be identified in the HostStorageSensor log file.

Problem: The worldwide port name (WWPN) and worldwide node name (WWNN) for an FC volume are not displayed.
Solution: TADDM uses the HBA API for FC volume discovery. The HBA API provides a mapping from the OS identification of a SCSI volume to the FC representation of the volume. The FC representation includes the WWPN of the port from the HBA that finds the volume. On multiport HBAs, there is no way to determine which port a SCSI volume applies to. This limitation is in the HBA API. The HBA API specification was updated to address this issue, but the change might not be implemented in all HBA API libraries. Ensure that the latest version of the HBA vendor's HBA API library is installed on the target host system. In summary, if the HBA API is unable to provide the mapping of a SCSI volume to its FC representation, then the WWPN and WWNN cannot be determined.

Problem: TADDM does not display the expected number of HBAs.
Solution: TADDM uses the HBA API for HBA discovery. For each adapter that the HBA API returns, TADDM creates an HBA model object. The adapters WWNN is used by TADDM to name the HBA. The number of adapters might not match the number of physical HBA cards that are installed in the host computer system, or the number of WWNNs returned by the basic system commands.; How the HBA API library interprets adapters and WWNNs are determined by the HBA vendor's, HBA API library implementation. For example, some vendors might represent a multiport HBA card that uses one adapter with one WWNN. Other vendors can represent a multiport HBA card that uses one adapter per port, with each adapter having its own unique WWNN.

Problem: The port type and port speed for an FC port are not displayed.
Solution: TADDM uses the HBA API for FC Port discovery. However, some HBA API libraries might not support these attributes, or the HBA vendor's HBA API library might need to be updated. Ensure that the latest version of the HBA API library is installed on the target host system. If the HBA API library cannot determine the port type and port speed, then these attributes are not displayed.

Problem: The SCSI bus, SCSI target, and SCSI LUN for an FC volume are not displayed or the correct values are not displayed.
Solution: TADDM uses the HBA API to discover SCSI information about an FC volume. However, some HBA API libraries might not support these attributes, or might not return the correct values for these attributes. To resolve this problem, the HBA vendor's HBA API library might need to be updated. Ensure that the latest version of the HBA API library is installed on the target host system. If the HBA API library cannot determine the SCSI information, then these attributes are not displayed or might display incorrect values.

Problem: The FC volume information is not displayed or does not display correct values.
Solution: TADDM uses the HBA API to discover information about an FC volume. However, if there is a problem with the HBA API library, TADDM might display incorrect values for some FC volume attributes. For example, block size. To resolve this problem, ensure that the latest version of the HBA API library is installed on the target host system and configured correctly. If the HBA API library is not configured correctly, FC volume attributes might not display or might display incorrect values.

Problem: When you are running HostStorageSensor on AIX LPARs, where the LPAR's configuration is attached to the BR8470 FCoE switch that runs FOS v6.4.3_dcb in Access Gateway mode, it leads to an unexpected behavior of systems that are connected to that FC switch.

Solution: It is a known FOS issue. To solve it, upgrade to FOS7.0.2e, or later.