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.
- 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.
- One or more devices fail with above mentioned errors.
- Storage Device is not discovered or inferred.
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:
Credentials for accessing the storage manager host.
WBEM credentials for the storage manager.
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 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:
SSH credentials valid for the storage device.
Several commands need sudo privileges. Ensure that you enable sudo. For details, see the Prerequisites section of EMC Isilon Storage Systems (via SSH) .
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.
status code 404message in the discovery log indicates there is no such page on this IP address. BMC Discovery communicates with the management system, which it expects to be in
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:
/usr/tideway/snmp++/bin/snmpWalk x.x.x.x -v1 -Cpublic
/usr/tideway/snmp++/bin/snmpWalk x.x.x.x -v2c -Cpublic
/usr/tideway/snmp++/bin/snmpWalk x.x.x.x '18.104.22.168.22.214.171.124.3.1' -v3 -snMyLogin -sl2 -authMD5 -uaMyPassword /usr/tideway/snmp++/bin/snmpWalk x.x.x.x '126.96.36.199.188.8.131.52.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:
- Download the appropriate troubleshooting tool from Sentry Software . In most cases this will be the generic WBEM Troubleshooting Tool.
- Copy it to a host (Windows, if possible) where "java -version" works and reports a version 1.6 or above.
Run the following command to launch the troubleshooting tool:
java -jar WBEM-Troubleshooting-Tool.jar
- Enter the host, login, password, and other details.
- Select the Platform, such as EMC, Dell, Fujitsu, and so on.
- Click Test Connection to run the queries and wait for the execution to end.
- 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.
In some cases, it may not be possible to use the graphical WBEM troubleshooting tool. Therefore, a command line tool is provided. Perform the following steps:
- Download the command line tool from here .
- Upload the file to the Discovery appliance in the same directory as the java binary, for example
/usr/tideway/jdk/jdk1.8.0_192_64/bin. This is to avoid the error,
Unable to access jarfile MS_HW_WBEMCLI.jar.
Note that root access is required to access this directory:
[root@myaddm]# ls -la /usr/tideway/jdk/jdk1.8.0_192_64 drwxr-xr-x. 2 root root 4096 Feb 13 13:37 bin
The syntax to run the command and see the usage notes is:
[tideway@myaddm bin]$ ./java -jar MS_HW_WBEMCLI.jar java -jar SEN_WBEMCLI /host:<host> /port:<port> /protocol:<protocol> /username:<username> /password:<password> /namespace:<namespace> /query:<query> /timeout:<timeout>
By default, the values for port, protocol, and namespace are:
/port:5989(On some IBM devices, i.e. DS8000 series, the port may be 6989. Use telnet to make sure it can connect.)
/namespace:root/<something>(EMC: root/emc, root/emc/celerra; IBM:root/ibm; HP: root/hpq, root/eva; Dell Compellent: root/compellent; Hitachi: root/hitachi/smis, root/smis/current; Huawei:root/huawei etc)
If there is doubt about the namespace, run the graphical WBEM troubleshooting tool on a local PC to check it out. For example, if
EMC CLARiiON/Symmetrix is chosen as the platform, the tool provides the corresponding namespace, which is
Note that this also provides the fields to be used in the query:
SELECT CreationClassName,Tag,ElementName,Model,Manufacturer,SerialNumber,EMCSerialNumber,__Path FROM EMC_ArrayChassis
This information can be found in the corresponding storage pattern or logs as well.
Example: Suppose the Discovery logs showed some WBEM queries that failed, and provided this information when the log is in debug:
140614264321792: 2018-11-27 12:35:34,326: discovery.device: INFO: Host_i::wbemEnumInstances() for 192.168.xxx.xxx 140614264321792: 2018-11-27 12:35:34,326: discovery.base: DEBUG: wbemEnumInstances() - class EMC_ArrayChassis, ['CreationClassName', 'EMCSerialNumber', 'ElementName', 'Manufacturer', 'Model', 'SerialNumber', 'Tag'], False, root/emc
The relevant values are:
- Query fields:
['CreationClassName', 'EMCSerialNumber', 'ElementName', 'Manufacturer', 'Model', 'SerialNumber', 'Tag']
The following is the command to run:
./java -jar MS_HW_WBEMCLI.jar /host:<hostname> /port:5989 /protocol:https /username:admin /password:xxxxx /namespace:root/emc /query:"SELECT CreationClassName, EMCSerialNumber,ElementName,Manufacturer,Model,SerialNumber, Tag FROM EMC_ArrayChassis" /timeout:120
The result may look like this:
[tideway@myaddm bin]$ ./java -jar MS_HW_WBEMCLI.jar /host:vmax /port:5989 /protocol:https /username:admin /password:#1Password /namespace:root/emc /query:"SELECT CreationClassName, EMCSerialNumber,ElementName,Manufacturer,Model,SerialNumber, Tag FROM EMC_ArrayChassis" /timeout:120 <MatsyaResponse>0,0,1.253,104</MatsyaResponse> SUCCESS Symm_ArrayChassis;;000297800620;EMC Corporation;VMAX250F;000297800620;SYMMETRIX-+-000297800620;
If the expected result does not appear, the storage pattern may not work, and it may be necessary to engage the manufacturer’s support team.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.
Log in or register to comment.