Instructions on LR monitoring for Windows and Linux

For instructions on LR monitoring for Windows and Linux-Linux Enterprise applications-Linux server applications, see the following for details. I. windows

1. Monitor preparations before connection

First, make sure that the following two services are enabled for the monitored windows System: Remote Procedure Call (RPC) and Remote Registry Service (the Service will not be started here)

On the monitored WINDOWS Server, right-click my computer and choose manage> shared folder. The shared folder C $ is required. (If you do not manually add the folder)

Then ensure that you run the program on the host where LR is installed. enter \ IP address of the monitored MACHINE \ C $ and then enter the Administrator account and password. If you can see the C drive of the monitored machine, it means you have obtained the Administrator permission of the machine, you can use LR to connect.

Note: LR requires an administrator account and password to connect to a WINDOWS Server for monitoring,

2. Use LR to monitor windows

(This is not detailed here. You only need to right-click the window and choose Add Measurements)

Ii. Linux

1. Preparations

First, you must have the rstatd daemon to monitor Linux. In some Linux versions, it may be rpc. the rstatd name is different here, and its functions are the same. To monitor linux, it is not just rpc. the rstatd Daemon must ensure that the three rlogin, rsh, and rexec services are on your LINUX machines. for different linux versions, you can use rpm-qa | grep rsh

Check whether the package of rsh is installed.

In general, linux downloads a package to provide this service. The package name is rpc.rstatd-4.0.1.tar.gz. This is a source code and needs to be compiled,

Download and install rstatd

Tar-ivh rpc.rstatd-4.0.1.tar.gz
./Configure --- Configuration
Make --- compile
Make install --- install
Rpc. rstatd --- start the rstatd Process

The target daemon for rstatd configuration is xinetd, and its main configuration file is/etc/xinetd. conf.

Only basic information

# Simple configuration file for xinetd
#
# Some ults, and include/etc/xinetd. d/

Ults
{
Instances = 60
Log_type = SYSLOG authpriv
Log_on_success = HOST PID
Log_on_failure = HOST
Cps = 25 30
}

Includedir/etc/xinetd. d

The content is not mentioned here! For more information, see/etc/xinetd. the three conf files rlogin, rsh, and rexec under d, change disable = yes in the three files to disable = no (disabled is used in the default {} to disable the Service)

Or set # default: off To on, which means that the above three services are started by default when xinetd is started! (Because ps ax does not seem to be able to see whether the three processes rlogin, rsh, and rexec are enabled, use default: on, because the two services, rstatd and xinetd, are started in ps ax)

Then, you can use LR to monitor the processes on Linux machines with the rstatd and xinetd services.

TIPS:

Check whether the rsh server is enabled. The rsh server listening and TCP are 514.
[Root @ mg04 root] # netstat-an | grep 514
Tcp 0 0 0.0.0.0: 514 0.0.0.0: * LISTEN
If 514 is displayed, the rsh server has been started.

Check whether the instance is started: rstatd

Enter the command: rpcinfo-p

If you can see

Program version protocol port

* ***** Udp 741 rstatd

It indicates that the rstatd service has been started. (Of course, ps ax can be used here)