If you are using a network firewall or host-based firewall (e.g. iptables), you may need to change your firewall configuration to open ports that the CDP uses for network communication.
R1Soft Licensing Server Network Ports | CDP Server Web Interface Network Ports | API Server Network Ports | CDP Agent Network Ports | CDP Data Center Console Network Ports | MySQL Ports
R1Soft Licensing Server Network Ports
Input:
- allow TCP established from activation.r1soft.com port 443 to CDP Server port range 1024-65535
Output:
- allow TCP from CDP Server port range 1024-65535 to activation.r1soft.com port 443
Note - Online activation requires the computer with R1Soft CDP installed to connect directly to https://activation.r1soft.com:443. Read more in Activating CDP Enterprise Edition.
CDP Server Web Interface Network Ports
Input:
- allow TCP from any port to CDP Server port 80
- allow TCP from any port to CDP Server port 443
Output:
- allow TCP established from CDP Server port 80 to any port range 1024-65535
- allow TCP established from CDP Server port 443 to any port range 1024-65535
Notes - To access your CDP Server's web interface, you will need to allow network traffic to the CDP Servers IP on TCP port 80 for HTTP traffic, and or TCP port 443 for HTTPS traffic.
- HTTP and HTTPS ports are configurable. "80" and "443" are the default values. If you change the ports, do not forget to change your firewall configuration to reflect the changes. Read more in Configuring CDP Server Ports.
API Server Network Ports
Input:
- allow TCP from any port to CDP Server port 9080
- allow TCP from any port to CDP Server port 9443
Output:
- allow TCP established from CDP Server port 9080 to any port range 1024-65535
- allow TCP established from CDP Server port 9443 to any port range 1024-65535
Notes - To access the API server, you will need to allow network traffic to the CDP Servers IP on TCP port 9080 for HTTP traffic, and or TCP port 9443 for HTTPS traffic.
- HTTP and HTTPS ports are configurable. "9080" and "9443" are the default values. If you change the ports, do not forget to change your firewall configuration to reflect the changes. Read more in Configuring API Server Options.
CDP Agent Network Ports
CDP Agent to CDP Server, CDP Server to CDP Agent
Input:
- allow TCP established from any port 1167 to CDP Server port range 1024-65535
Output:
- allow TCP from CDP Server port range 1024-65535 to any port 1167
Notes - You will need to allow your CDP Server to open connections to each one of your CDP Agents on TCP port 1167.
- The Agent port is configurable. "1167" is the default value. If you change the ports, do not forget to change your firewall configuration to reflect the changes. Read more in Configuring CDP Agent Port.
CDP Data Center Console Network Ports
Input:
- allow TCP from any to CDP Server port 8080
- allow TCP from any to CDP Server port 7443
Output:
- allow TCP established from CDP Server port 8080 to any port range 1024-65535
- allow TCP established from CDP Server port 7443 to any port range 1024-65535
Notes - You will need to allow your Data Center Console to open connections to each one of your CDP Server on TCP port 8080 for HTTP traffic, and or TCP port 7443 for HTTPS traffic.
- The Data Center Console ports are configurable. "8080" and "7443" are the default value. If you change the ports, do not forget to change your firewall configuration to reflect the changes. Read more in Configuring Data Center Console.
Scheme description
- Default Ports shown.
- Blue dashed lines are external apps/access.
- Orange solid lines are used in DCC to CDP communication.
- Ports in DCC and CDP boxes may be configured on a server by server basis.
- Ports in DCC/CDP Messages are for all servers.
- Initial DCC/CDP registration is on the CDP SOAP port.
- All updates, including initially showing the CDP in the DCC CDP Server list, are on the DCC/CDP Messages ports.
MySQL Ports
Customers with both 3.14 Server and Agent can use localhost for their MySQL instance hostname. It means, MySQL instance always comes from localhost.
The CDP Server will not connect directly to MySQL and instead connect to MySQL through the agent connection.
Labels: