Monday, 2 June 2014

Monitoring Unix Resources through Controller

   There is no need for any Load Runner installation to be on a Unix/Linux Machine to be monitored.


However, the machine must have the default RSTAT daemon installed and running. The controller
establishes a UDP socket connection with the UNIX machine. It first communicates with port 111 on
the Unix machine and this port is then mapped to the dynamic port on which the rstatd is working.
The controller then queries rstatd and all communication takes place through this established UDP
socket connection.

Starting the rstatd process in Unix
To monitor UNIX resources, you must configure the rstatd daemon. Note that the rstatd daemon
might already be configured, because when a machine receives an rstatd request, the inetd on that
machine activates the rstatd automatically.

To verify whether the rstatd daemon is already configured:
The rup command reports various machine statistics, including rstatd configuration. Run the following
command to view the machine statistics:
>rup host

A remote host will only respond if it is running the rstatd daemon. If you do not receive a response, or if
you receive an error message, the rstatd daemon is not configured.

To configure the rstatd daemon:

 Run the command: su root
  • Go to /etc/inetd.conf and look for the rstatd row (it begins with the word rstatd). If it is commented
    out (with a #), remove the comment directive, and save the file. From the command line, run:
  • > kill -1 inet_pid 
  • where inet_pid is the pid of the inetd process. This instructs the inetd to rescan the /etc/inetd.conf
    file and register all daemons which are uncommented, including the rstatd daemon. 
  •  Run rup again.
If the command still does not indicate that the rstatd daemon is configured, contact your system
administrator.

Which port is rstatd daemon running on:
You can run a UNIX utility called rpcinfo and identify the rstatd's port number. By running
> rpcinfo -p
you will receive a list of all RPC servers registered in the host's portmapper, along with the port number.

No comments:

Post a Comment