Ports to open
To use NeoLoad with a firewall, it may prove necessary to open some ports on the network interface of the Controller, Load Generator, and Monitoring Agent. For more information, see Firewall.
Load Generators
Controller-to-Load Generator direction
Default port | Protocol | Configuration file |
---|---|---|
7100 or configured as explained in Add Load Generators | TCP |
Load Generator:
Controller:
|
Controller-to-Cloud Load Generator direction
Default port | Protocol |
---|---|
443 or configured as explained in Add Load Generators | TCP |
Use the automatic discovery function Controller-to-Load Generator Agent direction
Port | Protocol | Configuration file |
---|---|---|
1359 | UDP |
Load Generator:
Controller:
|
Monitoring Agents
Controller-to-Monitoring Agent direction
Port | Protocol | Configuration file |
---|---|---|
7200 | TCP |
Monitoring Agent:
Controller:
|
Use the automatic discover function Controller-to-Monitoring Agent direction
Port | Protocol | Configuration file |
---|---|---|
1358 | UDP |
Monitoring Agent:
Controller:
File Key |
Controller
Acknowledge incoming Agents - (UDP 1369 and UDP 1358)-t0-Controller direction
Port | Protocol | Configuration file |
---|---|---|
4569 | TCP |
Controller:
File Key |
Note: To use the automatic discovery function of the Load Generators and Monitoring Agents, it is necessary to open the suitable ports on the hosting machines and for the Controller. If the ports are not opened, the Load Generators and the Monitoring Agents must be added manually, as described in Manage the Load Generator Agent and Manage the Monitoring Agent.
Ports to open for applications hosted on Cloud services
The information about which ports to open for applications hosted on Cloud services strongly depends on the Service Providers used. For more information, refer to your Service Provider Documentation or Support.