Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Server & Application Monitor (SAM) > SAM 6.5 Administrator Guide > Troubleshooting SAM > Troubleshooting a WMI Node issue in SAM

Troubleshooting a WMI Node issue in SAM

Table of contents
No headers

Updated: 3-9-2017

The following conditions must be met before you can proceed troubleshooting WMI nodes:

  • The node has successfully been added via WMI.
  • WMI is working properly on the remote server.
  • The Hardware Monitoring Agent software is installed on the remote server and running.

When ready, use Wbemtest.exe to troubleshoot WMI:

  1. Open wbemtest.exe, usually located at C:\Windows\System32\wbem\wbemtest.exe.
  2. Connect from the problematic node (either the SAM server or the additional poller server) to the remote server using wbemtest.exe.
  3. Click Connect. In the Namespace field enter:
    • For IBM and HP enter: \\RemoteServerIpAddress\root
    • For Dell enter: \\RemoteServerIpAddress\root\cimv2
      File:Success_Center/Reusable_content_-_InfoDev/SAM_Admin_Guide_Reuse/SAM-Admin-MT/0V0/0Q0/connect9.png
  4. Enter administrator credentials and click Connect.
  5. Once connected, click Query from the main screen. The Query dialog appears.
  6. Enter: select * from __Namespace
    File:Success_Center/Reusable_content_-_InfoDev/SAM_Admin_Guide_Reuse/SAM-Admin-MT/0V0/0Q0/connectq.png
  7. Replace Namespace with the following:
    • For HP nodes, replace Namespace with HPQ
    • For Dell nodes, replace Namespace with Dell
    • For IBM nodes, replace Namespace with IBMSD
  8. If the proper Namespace is found, connect to this Namespace.
    • \\RemoteServerIpAddress\root\IBMSD for IBM.
    • \\RemoteServerIpAddress\root\HPQ for HP.
    • \\RemoteServerIpAddress\root\cimv2\Dell for Dell.
      File:Success_Center/Reusable_content_-_InfoDev/SAM_Admin_Guide_Reuse/SAM-Admin-MT/0V0/0Q0/wmit.png
  9. Run a Query for specific information: Select Manufacturer, Model, SerialNumber from CIM_Chassis
  10. If the test was not successful, re-install the platform or Hardware Monitoring Agent software on the remote server with the latest release.
 
Last modified

Tags

Classifications

Public