Failover Control Points The following table describes the points that are required to manage failover. In Phase 2 failover, these points are located in a data file shared by the Primary and Backup interfaces. OSIsoft recommends that you locate the shared file on a dedicated server that has no other role in data collection. This avoids potential resource contention and processing degradation if your system monitors a large number of data points at a high frequency. Point Description Value / Default ActiveID Monitored by the interfaces to determine which From 0 to the highest interface is currently sending data to PI. interface failover ID ActiveID must be initialized so that when the number / None) interfaces read it for the first time, it is not an Updated by the error. redundant interfaces ActiveID can also be used to force failover. For Can be changed example, if the current Primary is IF-Node 1 and manually to initiate a ActiveID is 1, you can manually change manual failover ActiveID to 2. This causes the interface at to transition to the primary role and the interface at IFNode1 to transition to the backup role. Heartbeat 1 Updated periodically by the interface on Values range between IFNode1. The interface on IF-Node2 monitors 0 and 31 / None this value to determine if the interface on Updated by the IFNode1 has become unresponsive. interface on IF-Node1 Heartbeat 2 Updated periodically by the interface on Values range between The interface on IF-Node1 monitors this 0 and 31 / None value to determine if the interface on IF-Node2 Updated by the has become unresponsive. interface on IF-Node2 PI Tags The following tables list the required UniInt Failover Control PI tags, the values they will receive, and descriptions. Active_ID Tag Configuration Attributes ActiveID Tag <Intf>_ActiveID Compmax 0 ExDesc [UFO2_ActiveID] Location1 Match # in /id=# Location5 Optional, Time in min to wait for backup to collect data before failing over. Point Source Match x in /ps=x Point Type Int32 Shutdown 0 Step 1
Failover Control Points The following table describes the points that are required to manage failover. In Phase 2 failover, these points are located in a data file shared by the Primary and Backup interfaces. OSIsoft recommends that you locate the shared file on a dedicated server that has no other role in data collection. This avoids potential resource contention and processing degradation if your system monitors a large number of data points at a high frequency. Point Description Value / Default ActiveID Monitored by the interfaces to determine which interface is currently sending data to PI. ActiveID must be initialized so that when the interfaces read it for the first time, it is not an error. ActiveID can also be used to force failover. For example, if the current Primary is IF-Node 1 and ActiveID is 1, you can manually change ActiveID to 2. This causes the interface at to transition to the primary role and the interface at IFNode1 to transition to the backup role. From 0 to the highest interface failover ID number / None) Updated by the redundant interfaces Can be changed manually to initiate a manual failover Heartbeat 1 Updated periodically by the interface on IFNode1. The interface on IF-Node2 monitors this value to determine if the interface on IFNode1 has become unresponsive. Values range between 0 and 31 / None Updated by the interface on IF-Node1 Heartbeat 2 Updated periodically by the interface on The interface on IF-Node1 monitors this value to determine if the interface on IF-Node2 has become unresponsive. Values range between 0 and 31 / None Updated by the interface on IF-Node2 PI Tags The following tables list the required UniInt Failover Control PI tags, the values they will receive, and descriptions. Active_ID Tag Configuration Attributes ActiveID Tag <Intf>_ActiveID Compmax 0 ExDesc [UFO2_ActiveID] Location1 Match # in /id=# Location5 Optional, Time in min to wait for backup to collect data before failing over. Point Source Match x in /ps=x Point Type Int32 Shutdown 0 Step 1
PI_XML_1.5.1.114.docx