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

AVEVA™ System Platform

Communication

  • Last UpdatedAug 12, 2024
  • 1 minute read

Configure IP addressing

Make sure the DNS server is properly configured. All nodes in your Galaxy must be able to communicate with each other by using both IP address and Node Name, as configured in the Network Address option of the WinPlatform object.

If PCs in the Galaxy are using fixed IP addresses, then create a hosts file with the host name to IP Address mapping.

WinPlatform connection problems may result if computers cannot be accessed by both Hostname and IP address.

This is true no matter which type of Network Address you choose to use.

For example, assume two nodes in your Galaxy (host name: NodeA, IP address: 10.2.69.1; host name: NodeB, IP address: 10.2.69.2). NodeA must be able to ping NodeB with both "NodeB" and "10.2.69.2".

The reverse must also be true for NodeB pinging NodeA. Failure in either case, may result in the following: you may not be able to connect to a remote Galaxy Repository node from the IDE or deployment operations may fail.

Configure dual NICs

Use two Network Cards on a computer that hosts I/O Communication Drivers. Doing so provides load balancing and supports redundancy.

It is also good practice to place PLC communication on a dedicated (Control) network.

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