Troubleshooting and Limitations for Firewalls

Checking Connectivity

To run Vusers or monitor servers over a firewall, you must be able to establish a connection between the LoadRunner agent, MI Listener, and the Controller machine.

If you encounter connectivity problems after installing and configuring all the necessary components, check the table below for troubleshooting tips.

To check that the Firewall service was activated on the agent machine:

There should be a light on the right side of the LoadRunner Agent icon on the machine running/ monitoring Vusers over a firewall. If there is no light, this indicates that `FirewallServiceActive=1' is not set in the [FireWall] section of the Agent Settings. See Agent Configuration Settings Dialog Box.
To check that port 443 is open:

On the agent machine, open a Command Prompt window, and type the following:
telnet <MI_Listener_IP>443
For example: telnet 443
If port 443 is open, a new Telnet window will open. If port 443 is not open, contact your network administrator.
To check that port 443 is available:

If a web server is running on the MI Listener or Monitor-Over-Firewall machine, port 443 will not allow the access required by the listening and monitoring processes. Contact your network administrator to change the web server port.
To check connectivity between the agent and the MI Listener, when running the LoadRunner agent as a service:

If there is a red light on the right side of the LoadRunner Agent icon when running the LoadRunner agent as a service, do the following:
  • Check that port 443 is open. See the troubleshooting tip Troubleshooting and Limitations for Firewalls.

  • Check that the Agent Settings and Agent Configuration are correctly set. See Agent Configuration Settings Dialog Box.

  • Run the agent as a Process. Launch <Installation>\Launch_service\bin\magentproc.exe. If this works, this indicates an authentication issue with the Load Testing Agent Service. Browse to the Service > LoadRunner Agent Service, and change the properties of this service to System User Account or provide the user name and password of someone who has administrative privileges on this machine.

To check connectivity between the agent and the Controller, when monitoring over a firewall

  • Check that you entered the servers that you want to monitor in the Monitor Configuration dialog box. (See Monitor Configuration Dialog Box.)

  • Start the LoadRunner Agent Process on the Monitor-Over-Firewall machine. (See Configure the LoadRunner Agent)

  • On the Controller, enter the name of the Monitor-Over-Firewall machine in the Load Generators dialog box, and click Connect. After about a minute, data should start streaming in from the Monitor-Over-Firewall machine through the MI Listener to the Controller. (See Set Firewall Monitoring Preferences.)

  • If no data arrives at the Controller, try connecting the Controller to the MI Listener as if the Listener was used as a load generator. This will help identify the cause of the problem. Examine the log file on the Monitor-Over-Firewall machine by right-clicking the LoadRunner Agent icon. There should be no error messages.

  • Start the MI Listener, and then manually start the LoadRunner Agent Process by running <installation>\launch_service\bin\magnetproc.exe on the Monitor-Over-Firewall machine. Allow the Monitor-Over-Firewall machine sufficient time to connect to the MI Listener, then connect the Controller to the Monitor-Over-Firewall machine. If the LoadRunner Agent Process crashes, either restart the agent or reboot the Monitor Over Firewall machine.

Back to top

Windows Firewall Considerations

  • In most Windows environments, Windows Firewall is turned on by default. The firewall does not allow certain LoadRunner components to communicate with each other. The Windows firewall therefore needs to be turned off.

    Note: Turning off Windows Firewall increases the risk to your computer's security.

  • For each process that needs the firewall you can unblock the process by clicking the unblock button in the popup window that indicates that the program needs it, or by manually tuning the Windows firewall from the Exceptions tab.

Back to top

Linux LoadRunner Agent Menu

When you configure the Linux LoadRunner Agent, you must run agent_config to display the following menu:

For details, see Configure the LoadRunner Agent. If the menu does not display, type the following command to check if the M_LROOT environment variable is set:

Example: echo $M_LROOT

If M_LROOT is not set, do either of the following:

  1. Type sudo su - to inherit all environment variables of the current user.
  2. Type source <LoadGenerator_directory>/ to set all the Load Generator related environment variables after switching to root (i.e. "sudo su").

Note: This limitation occurs on Amazon cloud Linux machines, usually when you log in to the system using the special user named "ec2-user".

Back to top