Failover capabilities

This adapter supports client failover, where two adapters are configured as part of a redundant failover group. If the primary adapter loses connection to the failover endpoint or data source, the secondary adapter will be promoted to the primary position to ensure constant and consistent data flow.

Failover logic

There are three client failover modes that the adapters can be configured to use:

• Cold

  In cold failover mode, the secondary adapter is configured but not started. After a failover event occurs, the secondary adapter is started, becomes the primary adapter, and begins to collect and egress data. For implementations that contain redundant DNP3 outstations, this is the recommended failover mode.

• Warm

  In warm failover mode, configured components for the secondary adapter instance start and connect to the data source but do not collect or egress data from the data source. After a failover event occurs, the secondary becomes the primary and begins to collect and egress data.

  Note: It is strongly recommended to only use warm failover mode in combination with redundant DNP3 outstations.

• Hot

  In hot failover mode, configured components for both the primary and secondary adapters collect and buffer data, but only the primary adapter egresses data to the data endpoint. Data from the secondary adapter instance egresses the buffered data to the endpoint when a failover event occurs, and the secondary adapter becomes the primary.

  Note: It is strongly recommended to only use hot failover mode in combination with redundant DNP3 outstations.

For more information about failover modes, failover scoring and configuring client-level failover, see Client failover.