LoadRunner Remote Monitoring

Make sure that the following conditions are met:

1. Whether the firewall is on
2. Start running: Enter the monitored IP address and log on as the administrator.
3. enable monitoring-related services for the host to be monitored: mainly "Network DDE", "Remote Registry "...

 

 

1. Monitor preparations before connection

1) modify the access mode on the monitored WINXP host. The method is as follows: the security policy is at odds (Administrative Tools-> Local Security Policies-> Security Options-> "network access: local Account Sharing and security mode "). By default, the XP Access Method is "Guest only", so you access it, of course, it is fixed to access guest, And the Guest account has no monitoring permission, therefore, you need to change the access mode to the "classic" mode, so that you can log in as administrator.

Note: You must set a password. Otherwise, adding measurements in monitorconfiguration will still prompt you to reject logon.

2) ensure that the following three services are enabled for the monitored WINXP system: Remote Procedure Call (RPC), remote registry service, and Remote Registry. In the Remote Procedure Call (RPC) Locator logon option, enter the current host account and password, and then restart the service. Other service settings remain unchanged.

Note: you only need to enable the Remote Procedure Call (RPC) and remote registry services on the Internet. If you are not sure about the Windows version you are monitoring, Windows XP must enable the remote registry service.

3) Confirm that the machine on which the Controller is installed can connect to the monitored WINXP machine. If monitoring fails and LoadRunner cannot find the specified server, check whether the specified server is available. On the Controller or optimization console, type Ping <SERVER_NAME> (or IP) in the command line to ping the server.

4) after the verification can be connected normally, if there are other problems, you can refer to the following table to solve the problem:

Problem	Solution
Windows computers in other domains cannot be monitored, or access is denied ".	To obtain management permissions for remote computers, run the following command at a command prompt:   % Net use // <computer name>/User: [<domain>/<Remote Computer Name>]   Enter the password of the remote computer when prompted.
Unable to monitor NT/WIN 2000 computers (send an error message: "No computer name found" or "unable to connect to host ")	The NT/WIN 2000 computers to be monitored can only be monitored by users with administrator permissions. To allow non-administrator users to perform monitoring, you must grant users the read permission on specific files and registry entries (Microsoft technical instruction No. q158438 ). Perform the following steps:   A. Use a browser or file manager to grant users the read permission for the following items: % WINDIR %/system32/perfcxxx. dat   % WINDIR %/system32/perfhxxx. dat   XXX is the basic language ID of the system, For example, the English ID is 009. These files may Lost or damaged. If you have doubts about this, refer Install CD to extract these files.   B. Use regedt32 to grant the user the read permission for the following items: HKEY_LOCAL_MACHINE/software/Microsoft/Windows NT/CurrentVersion/Perflib And all the sub-items of the item.   C. Use regedt32 to grant at least the read permission to the following items: HKEY_LOCAL_MACHINE/system/CurrentControlSet/control/SecurePipeServers/winreg
Some Win 2000 counters cannot be monitored from the NT computer.	Run controller or optimization console on Windows 2000.
Some Windows Default counters are generated incorrectly.	Delete the problematic counter and use the "add measurement" dialog box to add the corresponding counter.
SQL Server 6.5 performance counters cannot be obtained from the monitored computer.	This is an error in SQL Server 6.5. Solution: Use regedt32 on the monitored computer to grant the user the permission to read the following registry entries:   HKEY_LOCAL_MACHINE/software/Microsoft/MSSQLServer   (Microsoft technical note No. q170394)
The selected measurement is not displayed in the figure.	Make sure that you have registered the display file and online.exe. To register the monitor DLL without fully installing it, run the set_mon.bat batch file in LoadRunner/bin.
When monitoring a Windows computer, no measurement is shown in the figure.	Check the built-in Windows performance monitor. If the monitor does not work properly, the communication settings may be incorrect.
When monitoring UNIX computers, no measurements are shown in the figure.	Make sure that rstatd is running on a Unix computer (see system resource monitoring ").
One of the following Web servers cannot be monitored: ms iis, Ms ASP, or ColdFusion	Refer to the above question "cannot monitor Windows computers ".
Unable to monitor WebLogic (JMX) Server	Open the <LoadRunner root folder>/DAT/monitors/weblogicmon. ini file and search: [Weblogicmonitor] Jvm1_javaw.exe Change javaw.exe to java.exe. A window containing tracing information is displayed.

5) confirm and open the shared file. First, on the monitored WINXP machine: Right-click my computer and choose "manage"> "shared folder"> "shared folder". The shared folder "C $" appears. This file may or may not exist. If not, you need to manually add it. Then, run on the machine where LR is installed, enter the IP address of the host to be monitored/C $, and then enter the Administrator account and password. If you can see the C drive of the machine to be monitored, it means that you have obtained the Administrator permission for the machine and can use lr to connect.

Note: Both steps must be performed. Otherwise, even if the shared file already exists but is not connected to the LR machine, it may not work properly.

2. Use lr to monitor windows

For detailed steps, see LoadRunner controller user's Guild> working with firewils> Monitoring over a firewall> Monitoring Server Monitor properties.