Hawkeye Ports for Automatic Endpoints
The following image displays information about the ports that are required for management and traffic for the probes/endpoints:
|
Description |
Port(s) |
Port or Port Range Modification Policy |
Protocol |
Directions |
Description |
|---|---|---|---|---|---|
|
Probes to Hawkeye server for node to node and mesh |
10117, 25025-25050 |
Not modifiable. |
TCP |
From probes to server(hardware and software). |
Mandatory for node to node and mesh testing. |
|
Probes to Hawkeye server for Real Services |
443 |
Modifiable with advanced configuration. |
TCP |
From probes to server(hardware probes only). |
Mandatory for advanced probes administration and real services executions. |
| Probes to Hawkeye server for Continuous Services |
10118 , 10119 |
Not modifiable |
TCP |
From probes to server(hardware and software). |
Mandatory for Continuous Services executions. |
|
Probe to probe management |
10115, 10116
|
Not modifiable. |
TCP AND UDP |
Probe to Probe, bidirectional or private to public only. 10116 port is opened by first probe (if private) to second public probe for second probe to send management packets to first probe. |
Mandatory for node to node and mesh testing. UDP port is only required for tests with synchronization (network KPI, any real time traffic). Direction is always private to public in case of mix in same pair. |
|
Probe to Probe traffic |
User defined |
Modifiable from administrator console in preferences. |
TCP |
From Probes to server. |
Default to AUTO which picks any port available on probes. Need to be enforced in Hawkeye configuration in case of FW between Probes. |
When the first endpoint is private as defined in Probe Management web page, the first endpoint will open port 10116 to the second endpoint so the second endpoint can use this port for sending test results (plus other management information) back to the first probe.