LoadGen URLs in use
The following URLs are in use by all versions of LoadGen, which are installed on-premises:
- https://api.loadgen.cloud
- https://download.loadgen.cloud
- https://loadgen.azurewebsites.net
- https://loadgen.azureedge.net
- https://login.microsoftonline.com
- https://login.windows.net
- https://loadgencloud.b2clogin.com
Additional considerations for LoadGen Cloud
In LoadGen Cloud settings, under the General tab, you can find the URL for the Azure Key Vault assigned to your tenant. This Key Vault securely stores all sensitive information, such as credentials and access keys.
If you are using LoadGen Cloud Agents, they must be able to establish a direct connection to this Key Vault. To ensure seamless communication, it is essential to whitelist this URL in your firewall and security settings.
Why is whitelisting necessary?
- The Azure Key Vault is a critical security component that LoadGen uses to manage and retrieve encrypted credentials.
- Blocking access to the Key Vault can result in authentication failures and impact LoadGen Agent functionality.
- Allowing access ensures that LoadGen Cloud Agents can retrieve necessary secrets securely and without interruption.
If you experience connection issues with your LoadGen Agents, please verify that the required URLs, including the Azure Key Vault URL, are properly allowed within your network.
LoadGen Load and Performance Testing - On-Premises
In the LoadGen On-Premises edition, several TCP Ports must be allowed to send information from and to the LoadGen Director and LoadGen Agents.
|
TCP Port number
|
Description
|
|---|---|
|
1433
|
Communication between LoadGen Agents with SQL directly in case of not tunneling data through the LoadGen Director (read more about tunneling). By default, the LoadGen Agents will tunnel all data to the LoadGen Director, and the LoadGen Director will bulk copy data to SQL.
The LoadGen Analyzer also has a direct connection to the LoadGen SQL Database.
|
|
4840
|
Bi-directional. Used to send commands from the LoadGen Director to the LoadGen Agent. Also used internally on the LoadGen Agent and the different session launchers.
|
|
4841
|
Bi-directional. Used to send status information, measurements, and counters from the LoadGen Agent to the LoadGen Agent itself. Traffic stays on the same machine.
|
|
4850
|
Used to send commands from the LoadGen Director to the LoadGen Core Agent.
|
|
4851
|
Used to send status information and measurements from the LoadGen Core Agent to the LoadGen Director.
|
|
4852
|
Bi-directional. Used to send status information and measurements from the LoadGen Core Agent to the LoadGen WebRecorder. Traffic stays on the same machine. |
LoadGen Cloud Agent and Studio
|
TCP Port number
|
Description
|
|---|---|
|
TCP 443 (HTTPS)
|
LoadGen Cloud Agents will retrieve workloads and jobs from the LoadGen Cloud. LoadGen Cloud Agents will send UserAction results and Performance Counters to the LoadGen Cloud.
|
|
TCP 443 (HTTPS)
|
LoadGen Cloud Studio will retrieve workloads and target environment settings from the LoadGen Cloud. LoadGen Cloud Studio will save workloads in the LoadGen Cloud.
|
Collecting Performance Counters
|
TCP Port number
|
Description
|
|---|---|
|
TCP 135 (DCE/RPC Locator service)
TCP 139 (NetBIOS Session Service)
TCP 445 (Windows shares)
UDP 137
UDP 138
|
Used to retrieve Performance Counters from the LoadGen Director to a Systems under Test machine.
|
- Open a remote connection to the LoadGen Agent.
- Start PerfMon.exe.
- Press the Action menu and connect to another computer...
- Add the computer name (the same name as the one entered in the SUT Machine Name field).
- If you can now create a connection, you are good to go.