Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Operations Management Interface

Configure service TCP ports

  • Last UpdatedJul 26, 2024
  • 2 minute read

Important: As of AVEVA System Platform 2014 R2, there is no need to configure any TCP ports. All Platform Common Services communication is based on the Microsoft WCF shared port 808. This information is retained for existing applications built with a version of AVEVA System Platform prior to the 2014 R2 release that have been assigned custom port numbers.

On a node running an OPC UA server, you need to open two ports, one for the OPC UA server and one for the OPC UA discovery service, if configured. See the following table for more information about OPC UA port configuration.

The ASB Core Services, installed with PCS and started by the Watchdog Service, also use specific ports. The following table lists the default TCP ports assigned to the user-configurable PCS Services and the ports in use for the PCS Core Services.

  • The PCS Core Services port numbers should not be used to configure instances of user services.

  • The firewall must allow incoming connections to the ports in the following table for their corresponding services to function.

Service

Port Numbers in Use

User-configurable Services

ASBGRBrowsing Service

7500, 7501 (default)

See note following this table.

ASBMxDataProvider Service

3572 (default)

ASBAuthentication Service

7779 (default)

Event Service

3575 (default, configurable)

EventHistorization Service

3586 (default, configurable)

OPC UA Service

48031 (default, configurable)

Endpoint for Application Server OPC UA Server instance

OPC UA Discovery Service

4840

(OPC Foundation service - not an ASB service)

PCS Core Services-Not configurable

Local Discovery Server

9111

Primary Local Galaxy Server

9110

Secondary Local Galaxy Server

9210

Primary Cross Galaxy Server

9310

Secondary Cross Galaxy Server

9410

Galaxy Pairing

7085

Configuration Service

6332

Content Provider Service

6011

Deploy Agent Service

6533, 6633

Service Manager Service

6111, 6113

System Authentication Service

9876

aaServiceASBSoftwareUpdate

7587

Important: If a Galaxy Repository (GR) has more than one Galaxy, two additional ports must be opened to enable a remote GR to browse to each additional galaxy. For example, two galaxies would require ports 7500, 7501, 7502, and 7503 to be open. Three galaxies would require ports 7500-7505 to be open.

TitleResults for “How to create a CRG?”Also Available in