5.8

Table Of Contents
Collector Cannot Contact the Agent
When the Collector cannot contact the Agent machine, look at the following on the Collector server.
n Try an nslookup of the Agent.
If it fails, edit the etc\hosts file on the Collector to map the Agent machine name to its IP address.
n From a command prompt on the Collector, ping the Agent machine by name or IP address.
n Try to telnet or ssh to the Agent.
On Windows, you can install the Putty application to open a UNIX console session to another machine.
Agent is Unresponsive
To make sure that the Agent is enabled and listening, look at the following items on the Agent machine.
n Check /opt/CMAgent/data/db/PDS/CertStore to make sure that the Collector certificate is
installed.
n Check that the Collector PEM certificate was pushed to CSI_ManageCertificateStore.
Use the same commands from "Collector Certificates" on page 70, but change –iz –f to –l.
n Check the file in /var/log/messages (Linux) or /var/adm/messages (Solaris) to see if (x)inetd
reported any errors when it was reconfigured to enable the Agent.
n Modify /opt/CMAgent/ECMu/1.0/scripts/inetd-agent, and add –b immediately before -u.
Try to contact the Agent again, and check /var/log/messages (Linux) or /var/adm/messages
(Solaris) for entries that are reported by CsiAgentListener.
n Check /var/log/messages (Linux) or /var/adm/messages (Solaris) for entries that show the csi-
agent process starting.
The messages might only appear if the machine is set up to log the message type.
n Copy /var/log/CSI/log/DebugEvent_Default.dbe to the Collector, and examine its contents
using the Debug Event Viewer.
n On Linux, type netstat –l | grep csi-agent
The command should return tcp 0 0 :csi-agent *: LISTEN
n On Solaris, type netstat –a | grep csi-agent
The command should return .csi-agent *. 0 0 0 0 LISTEN
n You can use a machine that has nmap installed, usually Linux, to determineif the port is open to the
network.
The command nmap –sT –v –p 26542
agent-machine
returns a result similar to the following.
VCM Troubleshooting Guide
72
VMware, Inc.