Troubleshooting Data Service Probe Implementations

This article describes how to troubleshoot the various aspects of Data Service Probe implementations.
This article describes how to troubleshoot the various aspects of Data Service Probe implementations.
Log Files
The Data Service Probe contains log files that you can use to troubleshoot problems with the probe. If you need to report an issue when using the probe, as a best practice, we recommend attaching the log files to tickets that you open.
You can find the log files in the following directories:
Windows Operating Systems
Linux Operating Systems
 When size of the log file exceeds approximately 10 MB, the Data Service renames the log file (for example, server-1.log) and then creates a new log file named server.log. 
Troubleshooting CIM Server Behavior
Consider the following best practices that you can use to troubleshoot Data Service Probe implementations with CIM server.
  • CIM Server (CFZCIM) relies on RMF, RMFGAT, and GPMSERVE. Verify that all of these tasks are running without error and that CFZCIM is running without error.
  • Errors that relate to an Empty DDS indicate that CIM cannot get data from RMF. Verify that all RMF processes such as RMF, RMFGAT, and GPMSERVE are running and that they do not contains any security errors.
  • Verify that the GPMSERVE passticket exists and all security is defined as per the RMF installation instructions.
  • Verify that RMF_CIM_HOST and RMF_CIM_PORT in /etc/wbem/cimserver.env are not set to invalid values.  When commented out, CIM will dynamically find the RMF port.
  • When CIM is running in a sysplex and CIM is configured to find RMF dynamically, CIM may try to connect to the wrong instance of RMF after an IPL.  If encountering connection issues in a sysplex, do the following:
    • Update /etc/wbem/cimserver.env to set RMF_CIM_HOST and RMF_CIM_PORT for each CIM instance to the local RMF hostname and port.
    • Verify that all RMF tasks and CIM are started on the correct system in Sysview.
  • If the probe queries the CIM server when it is in the process of starting, the CIM server can shut down quickly after start up, and without error. As a best practice, we recommend that you start the CIM server before you configure the probe to collect data.
  • If further debugging is required, you can enable trace logging for CIM server by following these steps:
    1. Modify /etc/wbem/cimserver.env to uncomment trace logging:
    2. Restart CIM.
    3. Run "cimcli ei IBMz_CEC" in USS and check the logging in /tmp/wbemosbase.trc and /tmp/wbemosmonitoring.trc.
    4. After debugging is complete, comment out the trace logging values in cimserver.env to improve CIM performance.
Troubleshooting AT-TLS
  • If CFZCIM contains the message “CFZ12568E: ATTLS is not active for TCP-IP stack the CIM server is using for HTTPS connections. Communication not secured. Connection closed.”, then the policy for the HTTPS port is not being run.  Verify that the CIM policy in PAGENT is running on the TCPIP stack where CFZCIM is enabled.
  • When the policy is being used, but the connection to CIM is not working, enable trace logging on the policy by modifying Trace to 255. The trace messages will print to the TCPIP output.
    TTLSGroupAction grp_StartUp
    TTLSEnabled On
    Trace 255
    For information about return codes for trace logging and AT-TLS debugging, see the following articles on the IBM Knowledge Center: