|
|
What ports are used by Sightline software? |
|
|
EDM and EAV both by default initiate connections to the Power Agents on port 1645. This port is also used by the AutoDiscover process.
Changing the Default Initial Communication Port:
If you want to change the initial communication port, you must change it in the Power Agent agent.xml. For EDM users, this port can be changed in the Hosts tab. For EAV, this port can be changed in the Advanced Settings dialog for a connection.
Setting the Call Back Port Range:
In EDM, the global call back port range is defined in the Systems Settings area. It can also be set per connection in the General Attributes tab of the connection.
In EAV, the call back port range is defined in the Enterprise/Firewall settings. This is a global setting and cannot be modified on a per connection basis as in EDM.
If you only want one port for call back, use the same port in the From and To settings. The call back port range cannot include the request port (typically 1645).
Inter Process Communication Ports:
Ports 8700, 8800 and 8900 are used for inter-process communication by the Power Agent processes. These are also configurable in the agent.xml
General information:
Q: What Protocol does the Sightline Software use?
A: The Sightline software leverages a proprietary TCP/IP protocol called TLC for communication between the Power Agents and the Expert Advisor / Vision (EA/V) and Sightline Enterprise Data Manager (EDM) Products
Q: How does the TLC protocol work?
A: The Sightline Power Agents contain a special process called a listener, which listen for connection requests on a particular port, similar to a web server. Sightline leverages a default TCP/IP port for this process, 1645, which can be modified if desired. Connection requests are made from either the EA/V or EDM products in order to download the performance data from the Power Agent. The application leverages a "callback" model, which means within the initial request, the EA/V or EDM product specify to the Power Agent a specific port for the data communication traffic. Once the initial handshake is complete, the Power Agent begins the data connection session back to the EA/V or EDM product via the port provided. By default, this is a random port provided by the operating system. The communication flow looks as follows:
EAV = Expert Advisor / Vision or EDM
PA = Power Agent
1. EAV [Random High Port] PA [1645]
2. PA [Random High Port] EAV[Callback Port]
In the example above, the connection shown in "1." is very short lived, terminating once step "2." is initiated. "2." Will stay open as long as the data connection is active within EA/V or EDM.
Q: If a firewall is used between the EA/V or EDM product and the Power Agent, what rules are necessary for the software to work properly.
A: In order for the Sightline software to work properly, the two communication sessions defined in FAQ 2. must be allowed. In the example above, firewall rules would be required to allow:
1. EAV must be allowed inbound access to PA via 1645.
2. PA must be allowed to outbound access to EAV.
The Sightline software provides several options to make these rules even more specific. First, the port which EA/V or EDM use when making the initial request can be defined. This is controlled via the "Request Port Range" setting. The "Callback Port" specified in "2." Can also be specified using the "Callback Port Range" settings. Finally, the "Random High Port" can be specified via the -f option in the connection settings. The combination of settings above give administrators the flexibility to control and tailor the firewall rules to their needs.
|
|
|
The user looked at the communications settings on the EDM Web interface and saw the TCP 1645 port was listed. Netstat also shows TCP 49174 and TCP 8700 in the agent.xml file.
The question arose ... what ports are used? Does the agent-to-EDM and agent-to-EAV communication go over only one TCP port and is it editable?
|
|