LoadRunner monitoring Linux and Windows methods __linux

think this article is considered very comprehensive, the source of the article is not very clear, thank the author to share.

PS: Monitoring Windows Server needs to turn on server computer Browser, server, remote Registry, remote Procedure call (RPC) Locator, remote Procedure Call (RPC) five services.

first, monitor the Windows System:

　　1, monitoring the connection before the preparation work

1 into the monitored Windows System, open the following two services remote Procedure call (RPC) and Remote Registry service (start-) run input services.msc, open the corresponding service.

2 on a monitored Windows machine: Right-click on My Computer, select Admin-> shared folder-> share this shared folder with C $ (if not manually added).

3 in the installation of LR machine, start-"run, input \ is monitored machine ip\c$ then enter the Administrator account number and password, if you can see the monitor machine C disk, it means that you have the machine administrator permissions, you can use LR to connect." (LR to connect to the Windows machine for monitoring to have an administrator account and password to do.) ）

Question: In the implementation of step 3, the input \ is monitored by the machine ip\c$, the presence of the administrator can not access the monitoring system (if the use of this method with LR monitoring, will be prompted: "No Network Path"), the phenomenon is that the user name input box is gray, And the default user is guest.

Workaround: This is a security policy setting issue (Administrative Tools-> Local Security Policy-> security options-> "Network access: Sharing and security mode for local accounts"). By default, XP access mode is "Guest only" way, if you access it, of course, fixed for guest to visit, and the Guest account does not have the right to monitor, so to change the mode of access to "classic" mode, so you can log in as the administrator. After the modification, perform step 3 again, enter the administrator username and password, you can access the monitored machine C disk.

If that doesn't work (which may be caused by other problems), it has to take another approach. On the server's machine, with the "performance logs and Alerts" under Windows with a new monitor log (management tools-) Performance log and alert, the log is configured to monitor the server's CPU, memory, Disk and other counters. Of course, this method is not to be monitored with LR.

　　2. The steps of monitoring windows with LR

In controller, in the Windows Resources window, right-click the mouse to select Add measurements, add the IP address of the monitored windows, select the owning system, and then select the metrics you want to monitor to start monitoring.

　　second, monitor Linux

　　1 Preparation Work

There are two ways to verify that the RSTATD daemon is configured on the server:

① uses the RUP command, which is used to report various statistical information about the computer, including RSTATD configuration information. Using the command Rup 10.130.61.203, here 10.130.61.203 is the IP of the Linux/unix server to monitor, if the command returns relevant statistics. Indicates that the RSTATD daemon is configured and activated, if no meaningful statistics are returned, or if an error report occurs, the RSTATD daemon has not been configured or has a problem.

② Use Find command

#find/-name rpc.rstatd, which is used to find RPC.RSTATD files in the system and, if not, the system does not have the RSTATD daemon installed.

If the RSTATD program is not installed on the server (Linux is not installed in general), you need to download a package to have this service, the package name is rpc.rstatd-4.0.1.tar.gz. This is a source code, need to compile, download and install RSTATD (can be downloaded at http://sourceforge.net/projects/rstatd<wbr> this address)

After downloading, start the installation process as follows:

TAR-XZVF rpc.rstatd-4.0.1.tar.gz CD RPC.RSTATD-4.0.1/ ./configure-Configuration Actions make-for compilation Make install-start Installation rpc.rstatd-Start RSTATD Process

2 after the installation is completed, configure the rstatd target daemon xinetd, its main configuration file is/etc/xinetd.conf, which contains some basic information as follows:

# # xinetd.conf # # Copyright (c) 1998-2001 SuSE GmbH Nuernb ERG, Germany. # Copyright (c) 2002 SuSE Linux AG, Nuernberg, Germany. # Defaults { Log_type = file/var/log/xinetd.log Log_on_success = HOST EXIT DURATION Log_on_failure = HO ST attempt #only_from = localhost Instances = the CPS = ten # # The specification Of an interface are interesting, if we are on a firewall. # For example, if you are want to provide services from a internal # network interface, your may specify your internal interfaces. # # interface = 127.0.0.1 } Includedir/etc/xinetd.d

What we need to modify here is/etc/xinetd.d/three conf files rlogin,rsh,rexec These three configuration files, dozen of these three files disable = Yes are changed to disable = no (disabled used in the default {} to prohibit clothing or set the # Default:off to on this means that the three services above are started by default when the xinetd is started.

Description: In my own configuration, no disable = yes this, I will change the # Default:off to: Default:on, after the reboot (cd/etc/init.d/./xinetd restart) through Netstat-an |grep 514 View, no return. Then I manually add disable = No to the last line in three files, restart xinetd, and then use Netstat-an |grep 514 to see the TCP 0 0 0.0.0.0:514 0.0.0.0:* the result, Indicates that the RSH server has started.

As long as the process on the Linux machine is guaranteed to have RSTATD and xinetd these two services can be monitored with LR.

　　Two little tips:

① Check to start: Rsh server listens for TCP 514.

[Root@mg04 root]# Netstat-an |grep 514

TCP 0 0 0.0.0.0:514 0.0.0.0:* LISTEN

If you can see 514 in the Listening instructions The RSH server has started.

② check whether to start: rstatd

Enter command: rpcinfo-p

If you see a message similar to the following:

Program Version Protocol port

100001 5 UDP 937 RSTATD

100001 4 UDP 937 RSTATD

100001 3 UDP 937 RSTATD

100001 2 UDP 937 RSTATD

100001 1 UDP 937 RSTATD

That means the RSTATD service is started, (and it can be replaced with PS ax, of course).

③ Restart Xinetd Method:

The following operations are SUSE Linux:

cd/etc/init.d/

./xinetd Restart

See some places on the Internet that use the following command:

# Service XINETD Reload

#/sbin/service xinetd Rstart

I don't know what the system is for.

④ install rsh, and rsh-server two service pack methods

A. Uninstall rsh

# rpm–q rsh----------View version number

# RPM-E Version number---------Uninstall the version.

b Installation

# RPM–IVH rsh-0.17-14.i386.rpm rsh-server-0.17-14.i386.rpm

⑤ When starting RPC.RSTATD, the error "Cannot register service:RPC:Unable to Receive;errno = Ction refused".

The workaround is as follows:

#/ETC/INIT.D./portmap start

#/ETC/INIT.D./nfs start

Then start the rpc.rstatd again.

Finally, in controller, drag and drop UNIX resources into the right window, right-click the mouse to select Add measurements, add the IP address of the monitored Linux, and then select the metrics you want to monitor.

　third, monitoring Unix

LR monitoring Unix,unix First start a RSTATD service

Here's how to start the RSTATD service in an IBM AIX system:

1. Use Telnet to log in to the AIX system as the root user

2. At the command prompt, enter: vi/etc/inetd.conf

3, find rstatd, find

#rstatd sunrpc_udp UDP wait root/usr/sbin/rpc.rstatd rstatd 100001 1-3

4. Remove the #

5.: Wq Save the change result

6. At the command prompt, enter: refresh–s inetd restart the service.

This allows you to monitor the performance of your AIX system using LoadRunner.

Note: After editing the inetd.conf on an HP UNIX system, the restart INETD service requires input inetd-c

Rup commands can also be used on UNIX to see if the RSTATD program is configured and activated

If the RSTATD program has been run, restart, first view the process Ps-ef |grep inet, and then kill the process, and then refresh–s inetd to restart.