5.8

Table Of Contents
Starting nmap V. 3.00 ( www.insecure.org/nmap/ )
Host {agent-machine} ({ip-address}) appears to be up good.
Initiating Connect() Scan against {agent-machine} ({ip-address})
Adding open port 26542/tcp
The Connect() Scan took 0 seconds to scan 1 ports.
Interesting ports on {agent-machine} ({ip-address})
Port State Service
26542/tcp open unknown
Nmap run completed 1 IP address (1 host up) scanned in 0 seconds
n (Optional) Install top on the Agent machine, and monitor to determine if the listener starts when you
telnet to the Agent port: telnet
agent-machine
26542
See "Monitor Processes with the top Utility" on page 74
As telnet runs, you should see the CsiAgentListener process appear and disappear in the top
display.
Collections Return No Data
Sometimes the UNIX Agent machine is reachable but does not return data when you perform a collection.
There are many reasons why this might happen, and you need to consider a variety of factors before
choosing a solution. The following sections explain the circumstances that might arise and the areas in
which you need to look.
Agent Processes Have Not Started
To verify that Agent processes are running, do the following. You might see other processes such as gawk
or zip depending on when you run the commands.
n To show all Agent processes, type ps –ef | grep CMAgent | grep –v grep
n (Optional) Install top on the Agent machine, and monitor the processes.
See "Monitor Processes with the top Utility" on page 74.
Agent Processes
n These processes appear when the Agent is running.
/opt/CMAgent/ECMu/3.0/bin/Agent
/opt/CMAgent/CFC/1.0/bin/CsiListenerWorkerDaemon
Because Red Hat Enterprise 2.1 reports all threads in a process, and not just the process itself, Red Hat
might display many instances of the processes. On other platforms, you see only one Agent and
CsiListenerWorkerDaemon.
n Each time the Collector sends a message to the Agent, the following process is started by (x)inetd.
/opt/CMAgent/CFC/3.0/bin/CsiAgentListener
n On Linux, AIX, and HPUX you see the following external Birdstep lock manager. The external lock
manager does not appear on Solaris, which uses an internal lock manager.
/opt/CMAgent/ThirdParty/1.0/bin/lm
On Linux, an lm process is always running for the status manager (SM) database when Agent is
VCM UNIX Agent
VMware, Inc.
73