Rockwell Automation FactoryTalk Historian SE 3.0 H2H Interface User Guide - Manual (Page 85)

FactoryTalk Historian To Historian Interface User Guide 79
Step Description
5. Test the configuration.
After configuring the shared file and the interface and Historian tags, the interface should
be ready to run.
See Troubleshooting UniInt Failover for help resolving Failover issues.
1. Start the primary interface interactively without buffering.
2. Verify a successful interface start by reviewing the pipc.log file. The log
file will contain messages that indicate the failover state of the interface. A
successful start with only a single interface copy running will be indicated by
an informational message stating “UniInt failover: Interface in
the
“Primary” state and actively sending data to
Historian. Backup interface not available. ” If the interface has
failed to start, an error message will appear in the log file. For details relating
to informational and error messages, refer to the
Messages section below.
3. Verify data on the Historian Server using available Historian tools.

The Active ID control tag on the Historian Server must be set to the
value of the running copy of the interface as defined by the
/UFO_ID
startup command-line parameter.

The Heartbeat control tag on the Historian Server must be changing
values at a rate specified by the
/UFO_Interval startup command-
line parameter.
4. Stop the primary interface.
5. Start the backup interface interactively without buffering. Notice that this copy
will become the primary because the other copy is stopped.
6. Repeat steps 2, 3, and 4.
7. Stop the backup interface.
8. Start buffering.
9. Start the primary interface interactively.
10. Once the primary interface has successfully started and is collecting data,
start the backup interface interactively.
11. Verify that both copies of the interface are running in a failover configuration.

Review the pipc.log file for the copy of the interface that was started
first. The log file will contain messages that indicate the failover state of
the interface. The state of this interface must have changed as
indicated with an informational message stating “UniInt failover:
Interface in the “Primary” state and actively sending
data to Historian. Backup interface available.
” If the
interface has not changed to this state, browse the log file for error
messages. For details relating to informational and error messages,
refer to the
Messages section below.

Review the pipc.log file for the copy of the interface that was started
last. The log file will contain messages that indicate the failover state of
the interface. A successful start of the interface will be indicated by an
informational message stating “UniInt failover: Interface in
the “Backup” state.
” If the interface has failed to start, an error
message will appear in the log file. For details relating to informational
and error messages, refer to the
Messages section below.
12. Verify data on the Historian Server using available Historian tools.

The Active ID control tag on the Historian Server must be set to the
value of the running copy of the interface that was started first as