Topology 4C diagram

The following diagram shows the achievable performance envelope for Topology 4C when built with the prescribed servers, hardware resources, software, and data flows.

Note: Only small amounts of PI to CONNECT transfer data are acceptable when the PI to CONNECT Agent is loaded on the Data Archive node.

Topology 4C: PI data flows

1. Inbound Data Flowing to PI Data Archive - TCP port 5450 (Clients)

2. PI Data Archive Collective Node Traffic

3. PI Server Requests Flowing to MS SQL Server - TCP port 1433 (SQL), UDP port 1434 (SQL)

4. PI Analysis Service, Notifications Flowing to PI Server - TCP ports 5450 (PINET-Data Archive), 5457 (PINET-AF).

   Note: Requests to PI AF across port 5457 are proxied through NLB; all others are direct connections through the indicated port.

5. Windows Failover Cluster Traffic to Shared Storage - TCP port 3343, UDP port 3343

6. PI Vision Requests Flowing to MS SQL Server - TCP port 1433 (SQL), UDP port 1434 (SQL)

7. PI Client Requests Flowing to PI Analysis Service and PI Notifications - TCP port 5463 (PINET-Analysis), 5468 (PINET-Notifications)

8. PI Vision and Web API Requests Flowing to PI Server - TCP ports 5450 (PINET-Data Archive), 5457 (PINET-AF)

   Note: Requests to PI AF across port 5457 are proxied through NLB; all others are direct connections through the indicated port.

9. PI Client Requests Flowing to PI Server - TCP ports 5450 (PINET-Data Archive), 5457 (PINET-AF), 5464 (SQLDAS-HTTP/SOAP), 5465 (SQLDAS-net.tcp)

   Note: Requests to PI AF across port 5457 are proxied through NLB; all others are direct connections through the indicated port.

10. PI Web Clients Requests Flowing to NLB and Proxied to Web Servers - TCP ports 80 (HTTP), 443 (HTTPS)

11. PI to CONNECT data transferred to AVEVA Data Hub - TCP port 443 (HTTPS) outbound to PI to Data Hub gateway. Data Hub gateway URL varies based on Data Hub namespace region

12. Adapter OMF Requests Flowing to NLB and Proxied to Web API servers - TCP ports 80 (HTTP), 443 (HTTPS)