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

AVEVA Enterprise SCADA

TABLE OF CONTENTS

Configure TCPListener for failover support

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedApr 24, 2025
  • 2 minute read

To enable the TCPListener to continue forwarding network traffic from the production system to the testing system in the event of a failover, you must adapt the TCPListener configuration files (TCPListener.xml) to filter packages to both the Hot and Standby servers from the source system.

To configure TCPListener for failover support

  1. Complete all steps in Auto configuration or Manual configuration.

  2. Copy the <Filter> section and paste it again directly below the first <Filter> section.

  3. Rename the TCPListener.xml file created through the steps in Auto configuration to TCPListener-hot.xml.

  4. Make a copy of the TCPListener-hot.xml file, and rename the copy TCPListener-standby.xml.

  5. Open the TCPListener-standby.xml file.

  6. Enter the correct IP addresses:

    • xxx.xxx.xxx.xxx represents the IP address of the connection's terminal server.

    • yyy.yyy.yyy.yyy represents the IP address of the first RealTime server.

    • yyy.yyy.yyy.zzz represents the IP address of the second RealTime server.

      Note: In the example Above, there is only one connection configured for TCPListener. In a real-world situation, there would be many connections, and hence many <WriteInterface> nodes. Each <WriteInterface> node would have two <Filter> nodes.

  7. Save the file.

    This file now has two filter sections per remote. This allows TCPListener to look at the packages from a remote, even if the remote is communicating with a RealTime server or another server.

  8. Save the merged file as TCPListener.xml.