continue to be sent to the Data Source if one of the PI Servers becomes unavailable for any reason. Data Source Points The following table identifies the points that are required to manage failover and the values used for each PI attribute. The following table explains each of the points required on the data source in more detail. 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 IFNode2. The interface on IF-Node1 monitors 0 and 31 / None this value to determine if the interface on Updated by the IFNode2 has become unresponsive. Interface on IF-Node2
continue to be sent to the Data Source if one of the PI Servers becomes unavailable for any reason. Data Source Points The following table identifies the points that are required to manage failover and the values used for each PI attribute. The following table explains each of the points required on the data source in more detail. 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 IFNode2. The interface on IF-Node1 monitors this value to determine if the interface on IFNode2 has become unresponsive. Values range between 0 and 31 / None Updated by the Interface on IF-Node2
PI_OPCInt_2.3.20.9.docx