Allowing port 6600 for Execution server and Agent server communications

book

Article ID: 36458

calendar_today

Updated On:

Products

CA Release Automation - Release Operations Center (Nolio) CA Release Automation - DataManagement Server (Nolio)

Issue/Introduction

Question: 

If an execution server and agent server are separated by a firewall, is it enough to open outbound connections from the execution server to the agent server on port 6600? Or are both outbound and inbound connections from execution server to the agent server on port 6600 required?

Answer: 

For execution server and agent server communications, port 6600 will need to be open for both inbound and outbound connections.

SourceProtocolTargetTarget PortReason
Execution ServerTCP/SSLAgent6600Default port for file transfer during a process.
AgentTCP/SSLExecution Server6600Transfer of process results back to the Execution Server at end of execution.


Additional Information:

The additional ports below may also need to be opened between execution servers and agent servers depending on your needs.

SourceProtocolTargetTarget PortReason
AgentTCP/SSLExecution Server6900If an Agent is installed on the Execution Server, CA recommends to open up traffic from all Agent to the Execution Servers on 6900 (default port). In this case, all Agent to Execution Servers on 6600 requires bidirectionally be enabled.
Execution ServerTCP/SSLAgent135 and 445Remote Agent installation on Windows platforms.
Execution ServerTCP/SSLAgent22Remote Agent installation on Unix via SSH.


Note: All port numbers are configurable. All source ports are random.

Environment

Release: NOLNAC99000-5.5-Nolio-Automation Center
Component: