How do I determine if the VigilEnt Security Agent for Unix is running? (NETIQKB31474)

goal
How do I determine if the VigilEnt Security Agent for Unix is running?

goal
Is the VigilEnt Security Agent for Unix running?

goal
Is the Agent running?

goal
How do I know if the Agent is running?

fact
VigilEnt Security Agent for Unix 2.x

fact
VigilEnt Security Agent for Unix 3.x

fact
VigilEnt Security Agent for Unix 4.0

fact
VigilEnt Security Agent for Unix 5.0

fix

To determine if the agent is running, open a session with the remote host and verify that uagent and uvserv are listening on the correct ports?the port numbers must match the settings in VigilEnt Security Manager. The default port for uagent is 2620, the default port for uvserv is 1622, and the default port for the VigilEnt Security Service module is 1621.

Use on of the following commands to check the ports settings on the remote host:

• lsof
• netstat

Use lsof if it is available. It returns more information than netstat.

To determine if lsof is on the host with which you are working, at the prompt, run which lsof. If lsof is available, run the following command:

lsof -i | egrep '1622|2620'

The following response tells you that uagen and uvserv are ready and listening on the default ports:

uagent 844 root 4u IPv4 1390 TCP *:2620 (LISTEN)
uvserv 846 root 4uI Pv4 1855 TCP *:1622 (LISTEN)

If lsof is not on the host you are working with, use netstat, which will verify listening on the port, but may not identify which service is listening. Responses may vary for different Unix and Linux distributions?look for the key word LISTEN in the response for ports 1622 and 2620. Type the following netstat command:

netstat -an | egrep '1622|2620'

An affirmative response in Linux may look something like this:

tcp 0 0 0.0.0.0:1622 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2620 0.0.0.0:* LISTEN

An affirmative response in Sun Solaris may look something like this:

*.2620 *.* 0 0 24576 0 LISTEN
*.1622 *.* 0 0 24576 0 LISTEN

Formerly known as NETIQKB31474