Configuring uniint failover, Start-up parameters – Rockwell Automation FactoryTalk Historian SE 3.0 UniInt Interface User Guide User Manual
Page 81

UniInt Interface User Manual
75
Configuring UniInt Failover
Start-Up Parameters
The following table lists the start-up parameters used by UniInt Failover. All of the
parameters are required expect the /UFO_Interval startup parameter. See the table below for
further explanation.
Parameter
Value
Description
Failover ID
Computer:
IF-Node1
/UFO_ID=1
The value is not required to be 1. The value
must be a positive, non-zero integer and
different from the failover ID of IF-Node2.
Failover ID
Computer:
IF-Node2
/UFO_ID=2
The value is not required to be 2. The value
must be a positive, non-zero integer and
different from the failover ID of IF-Node1.
Other Failover ID
Computer:
IF-Node1
/UFO_OtherID=2
The value is not required to be 2. The value
must be a positive, non-zero integer and equal
to the Failover ID configured for the interface on
IF-Node2.
Other Failover ID
Computer:
IF-Node2
/UFO_OtherID=1
The value is not required to be 1. The value
must be a positive, non-zero integer and equal
to the Failover ID configured for the interface on
IF-Node1.
Failover Update
Interval
Computer:
IF-Node1 and IF-
Node2
/UFO_Interval=n
Units for n:
milliseconds
Default:
1000
The Failover Update Interval specifies the rate
at which UniInt updates the Failover Heartbeat
tags as well as how often UniInt check on the
status of the other copy of the interface.
The /UFO_Interval is only used if the Failover
Control Input Historian tags are collected on an
unsolicited basis. If the Input Historian tags are
scanned, the Failover Update Interval is
determined by the scan class the tags are
associated with.
The value of n specifies the Update Interval in
milliseconds and must be the same on both
interface computers.
Host Historian Server
for Exceptions and
Historian tag updates
Computer:
IF-Node1
/Host=PrimaryPI
The value of the /host startup parameter
depends on the Historian Server configuration.
If the Historian Server is not part of a collective,
the value of /host must be identical on both
interface computers.
If the redundant interfaces are being configured