Default language.

Important This documentation space contains information about the SaaS version of BMC Helix Discovery. If you are using the on-premises version of BMC Helix Discovery, see BMC Helix Discovery 25.2 (On-Premises).

Troubleshooting storage scan failures


When you observe failures while scanning storage devices, use the troubleshooting steps described in this section to either resolve the problem or create a BMC Support case.

Issue symptoms

  • A scan of storage devices fails with the following error messages:
    • No Access (StorageDevice identification failure - no mac addresses)
    • Skipped (Device is an unsupported device)
  • A credential test fails with the error message, WBEM access via https failed.
  • The basic storage details are discovered but no information is found for disks, volumes, pools, capacity, or usage.

Issue scope

  • One or more devices fail with above mentioned errors.
  • Storage Device is not discovered or inferred.

Resolution

Perform the following steps to troubleshoot the failures in scanning storage devices:

Step 1: Verify the prerequisites

The prerequisites for full discovery of a storage system, and the relationships between them, are as follows:

  • Download the storage patterns from the BMC Electronic Product Distribution (EPD) site. After you upload and activate the patterns, you can see them in the Knowledge management tree view under Storage Systems.
  • To discover storage using management software, you must use:
  • To discover storage directly using the WBEM/SMI-S provider, use the WBEM credentials for the WBEM/SMI-S provider.
  • To discover NetApp storage using SNMP, you must use:
    • SNMP credentials valid for the storage device.
    • BMC Helix Discovery must be on a network that can access the NetApp management ports.

      IPv6 not supported in NetApp MIB

      IPv6 is not supported in the NetApp MIB, so the IPv6 virtual interfaces are not discovered.

  • To discover storage using SSH, you must use:
  • To discover and link storage consumers:
    • Credentials for accessing any host that is a consumer of the storage.
    • For hosts to be linked to storage, the HBA ID must be discovered.
  • The status code 404 message in the discovery log indicates there is no such page on this IP address. BMC Helix Discovery communicates with the management system, which it expects to be in <ip>/cimom.

Step 2: Check the connectivity with third party tools:

SNMPWalk: Perform this test when SNMP credentials are configured for storage discovery.

Do an snmpwalk to the device. See the examples below for SNMP version-dependent information:

SNMP v1:

/usr/tideway/snmp++/bin/snmpWalk x.x.x.x -v1 -Cpublic

SNMP V2c:

/usr/tideway/snmp++/bin/snmpWalk x.x.x.x -v2c -Cpublic

SNMP V3:

/usr/tideway/snmp++/bin/snmpWalk x.x.x.x '1.3.6.1.2.1.17.4.3.1' -v3 -snMyLogin -sl2 -authMD5 -uaMyPassword
/usr/tideway/snmp++/bin/snmpWalk x.x.x.x '1.3.6.1.2.1.17.4.3.1' -v3 -snMyLogin -sl3 -authSHA -ua'My$Password' -privDES -up'MyPrivateKey'

 The output can also be redirected to a file, for example:

/usr/tideway/snmp++/bin/snmpWalk x.x.x.x -v2c -Cpublic >> snmpwalk.txt

WBEM troubleshooting tool provided by Sentry Software: Perform this test when WBEM/SMI-S provider is configured for storage discovery:

  1. Download the appropriate troubleshooting tool from Sentry Software. In most cases this will be the generic WBEM Troubleshooting Tool.

  2. Copy it to a host (Windows, if possible) where "java -version" works and reports a version 1.6 or above.
  3. Run the following command to launch the troubleshooting tool:

    java -jar WBEM-Troubleshooting-Tool.jar
  4. Enter the host, login, password, and other details.
  5. Select the Platform, such as EMC, Dell, Fujitsu, and so on.
  6. Click Test Connection to run the queries and wait for the execution to end.
  7. To share the result, Click Save As, and send the resulting .txt file to Customer Support.

If the test connection fails, some WBEMException will appear in the results.If the problem persists, collect the discovery logs in debug mode. You can review the logs to identify the error messages. If this still does not resolve your problem, contact Customer Support, and provide the results of the tests in this procedure.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*