In the LoadGen On-Premises edition, there are several TCP Ports that 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
|
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
|
Used to send status information, measurements, and counters from the LoadGen Agent to the LoadGen Agent itself and to the LoadGen Director.
|
|
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.
|
|
8000
|
Used to install the LoadGen Agent and retrieve status from the LoadGen Agent to LoadGen Director (bi-directional).
|
LoadGen Cloud Agent and Studio
The LoadGen Cloud Agent and the LoadGen Cloud Studio are only using HTTPS traffic, initiated from the LoadGen Cloud Agent and Studio. The LoadGen Cloud backend cannot control LoadGen Agents directly, whatsoever.
|
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 setting from the LoadGen Cloud. LoadGen Cloud Studio will save workloads in the LoadGen Cloud.
|
Collecting Performance Counters
In the LoadGen On-Premises edition as well as the Cloud editions it is possible to retrieve Performance Counters from a remote machine (Systems Under Test - SUT machines). For remote collecting Performance Counters, these Firewall ports must be opened.
|
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.
|
If you are not sure if you are allowed to retrieve Performance Counters perform the following actions:
- Open a remote connection to the LoadGen Agent.
- Start PerfMon.exe.
- Press the menu Action and Connect to another computer...
- Add the computer name (the same name as entered in the SUT Machine Name field).
- If you can now create a connection you are good to go.