Verifying the IBM Director Agent is Operating Properly

Workaround techniques to verify that the IBM Director Agent is operating properly.

Related Topics

Objective

Hardware Sentry KM for PATROL relies on the IBM Director Agent to monitor IBM xSeries servers. The IBM Director Agent not providing a status or sufficient details about certain components prevent Hardware Sentry KM for PATROL to monitor these elements.

This article provides workaround techniques to verify that the IBM Director Agent is operating properly.

Recommendation

When installing the IBM Director Agent it is always recommended to install the latest available version. An older version of the IBM Director Agent may not work properly on new server models.

Checking the availability of hardware data on Windows

On Windows, you can use the Windows Management Instrumentation Tester (wbemtest.exe) to communicate with the CIM server of the IBM Director Agent.

  1. Click Start > Run > type wbemtest > OK. Then click Connect

    Run WBEMTest
  2. In the first field displaying root\default, type \\servername\root, where ‹servername> is the name of the server you want to test:

    Enter\\Servername\root and credentials
  3. If the user does not have administrator rights to this server, enter a valid username and password for this server under the Credentials Section.
  4. Click Connect.

IBMSD Namespace Test

  1. On the main WMI Tester screen, click Query.
  2. In the Enter Query box, type: SELECT Name FROM __NAMESPACE

    SELECT NAME FROM __NAMESPACE
  3. Click Apply.
  4. Search list for: __NAMESPACE.Name=”IBMSD”

    __NAMESPACE.Name=”IBMSD”
  5. The test is successful if “BMSD” appears in the list.

Environment Sensor test

  1. In the Enter Query box, type: SELECT DeviceID,TempLocation FROM IBMPSG_TemperatureSensor
  2. Click Apply.
  3. Double click any of the instances to see if it has values.

ADAPTEC Namespace Test

  1. At the main WMI Tester screen, Click Connect…
  2. Where it says \\servername\root\ibmsd, change it to \\servername\root
  3. Click Connect.
  4. At the main WMI Tester screen, click Query.
  5. In the Enter Query box, type: SELECT Name FROM __NAMESPACE
  6. Click Apply.
  7. Search list for a __NAMESPACE.Name=”adpt”
  8. Click Close.

ADAPTEC CIM_DiskDrive Test

  1. At the main WMI Tester screen, Click Connect…
  2. Where it says \\servername\root, change it to \\servername\root\adpt
  3. Click Connect.
  4. At the main WMI Tester screen, click Query.
  5. In the Enter Query box, type: SELECT Name FROM CIM_DiskDrive
  6. Click Apply.
  7. You should see at least one object listed in the window. Click Close.
  8. Click Close.

LSI Namespace Test

  1. At the main WMI Tester screen, Click Connect…
  2. Where it says \\servername\root\ibmsd, change it to \\servername\root
  3. Click Connect.
  4. At the main WMI Tester screen, click Query.
  5. In the Enter Query box, type: SELECT Name FROM __NAMESPACE
  6. Click Apply.
  7. Search list for a __NAMESPACE.Name=”LSI_IR_1_2_0”
  8. Click Close.

LSI CIM_DiskDrive Test

  1. At the main WMI Tester screen, Click Connect…
  2. Where is says \\servername\root, change it to \\servername\root\LSI_IR_1_2_0
  3. Click Connect.
  4. At the main WMI Tester screen, click Query.
  5. In the Enter Query box, type: SELECT Name FROM CIM_DiskDrive
  6. Click Apply.
  7. You should see at least one object listed in the window. Click Close.
  8. Click Close.

Environment Sensor Test on Linux

At the command prompt of the server, run the following command to check the Voltage Sensors.

 /opt/ibm/icc/bin/cimcli ei -n root/ibmsd  "IBMPSG_VoltageSensor" 

For example

root@pyrrho3:~ #/opt/ibm/icc/bin/cimcli ei -n root/ibmsd "IBMPSG_VoltageSensor"
path= IBMPSG_VoltageSensor.CreationClassName="IBMPSG_VoltageSensor",DeviceID="CPU VCore:7f2a01f501f4601f201f4501f5c0",SystemCreationClassName="MSD_ComputerSystem",SystemName="pyrrho3.internal.
sentrysoftware.net"
//Instance of IBMPSG_VoltageSensor
instance of IBMPSG_VoltageSensor
{
InstanceID = NULL;
Caption = "Voltage Sensor";
Description = "An entity capable of measuring or reporting the CPU "
"VCore characteristics of a Computer System.";
ElementName = "CPU VCore";
Generation = NULL;
InstallDate = NULL;
Name = "CPU VCore";
OperationalStatus = {2};
StatusDescriptions = NULL;
Status = "OK";
HealthState = 5;
.
.
PossibleStates = {"Normal", "Warning", "Non-Critical", "Lower Non-Critical",
"Upper Non-Critical", "Critical", "Lower Critical", "Upper Critical",
"Fatal", "Lower Fatal", "Upper Fatal", "Unknown"};
CurrentState = "Normal";
.
.
CurrentReading = 1158;
NominalReading = NULL;
NormalMax = NULL;
.
.
LowerThresholdCritical = 702;
UpperThresholdCritical = 1602;
LowerThresholdFatal = 0;
UpperThresholdFatal = 0;
VoltageType = 0;
EventsEnabled = TRUE;
EventAutoClearEnabled = FALSE;
nodeID = 6;
};

Similarly, you can use the following command to verify the Temperature Sensors

 /opt/ibm/icc/bin/cimcli ei -n root/ibmsd  "IBMPSG_TemperatureSensor" 

Environmental information is not being collected

The environmental information is not being collected (Temperatures, Voltages, Fans, etc..) on servers running Windows or Linux OS.

With IPMI

First, check that the IPMI driver has been correctly installed and is properly working. Then, attempt a manual re-installation of the IBM Director Agent.  If IPMI is not installed/working, the installation procedure will prompt you with an error saying the IPMI stack is not working or installed.

On Linux the IPMI functionality can be verified by running the following commands:

#ipmitool fru
# ipmitool bmc info
# ipmitool sdr
# ipmitool sensor