Known issues 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, the 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.
Check
|
Action
|
---|---|
Make sure the firewall service is activated on the agent machine. |
On the machine running/monitoring Vusers over a firewall, the LoadRunner Agent icon should display a red light icon . If the icon does not have a light icon, it means FirewallServiceActive=1 is not set in the [FireWall] section of the Agent Settings. See Agent Configuration Settings dialog box. |
Make sure port 443 is open.
|
On the agent machine, open a Command Prompt window, and enter: If port 443 is open, a new Telnet window opens. If port 443 is not open, contact your network administrator. |
Make sure port 443 is available.
|
If a web server is running on the MI Listener or MOFW machine, port 443 does not allow the access required by the listening and monitoring processes. Contact your network administrator to change the web server port. |
Confirm connectivity between the agent and the MI Listener when running the LoadRunner Agent as a service.
|
If the LoadRunner Agent icon has a red light when running the LoadRunner Agent as a service, do the following:
|
Confirm connectivity between the LoadRunner Agent and Controller when monitoring over a firewall.
|
|
Windows firewall considerations
In most Windows environments, Windows firewall is turned on by default. The firewall prevents certain LoadRunner Professional components from communicating 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 Windows 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 configuring the Windows firewall in the Exceptions tab.
Linux LoadRunner Agent menu
To configure the Linux LoadRunner Agent, run the agent_config script. For details, see Configure the LoadRunner Agent over firewalls. If the menu does not display, type the following command to check if the M_LROOT environment variable is set:
echo $M_LROOT
If M_LROOT is not set, do either of the following:
- Type
sudo su -
to inherit all environment variables of the current user. - Type
source <LoadGenerator_directory>/env.sh
to set all the Load Generator related environment variables after switching to root (that is, "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".