Professional Documents
Culture Documents
FTHSE v2 1 (CPR9 SR1) Interface Redundancy Configuration Guide
FTHSE v2 1 (CPR9 SR1) Interface Redundancy Configuration Guide
The scope of this document is FTLD interface redundancy only. However, as a rule, FTLD interface
redundancy is combined with RSLinx Enterprise data server redundancy to create a redundant data
server/interface pair. Additionally, the redundant data server/interface pair is often combined with controller
redundancy and server redundancy (a.k.a. “a collective”) to provide a robust solution for mission critical data
collection applications. For more information on configuring the other redundant components, refer to:
• controller redundancy: ControlLogix Redundancy System User Manual
• data server redundancy: FactoryTalk Online Help
• Historian SE collective: Historian SE v2.1 Installation and Configuration Guide (Chapter 9 –
Configure A Collective)
Related Documentation
The following related documents provide additional information which you may find of interest:
• Historian SE v2.1 Installation and Configuration Guide
• Answer ID 61952 - FactoryTalk Historian SE v2.1 (CPR9 SR1) Collective Configuration Guide
• Historian SE v2.1 Introduction to PI System Management
• Historian SE v2.1 High Availability Advanced User's Guide
• Historian SE v2.1 High Availability and Replication Guide
HOST01 HOST02
Network FTD FT Historian Server
FT Activation Server
File Server
HOST04 HOST05
FTLD Interface FTLD Interface
(Primary) (Backup)
Data Server Data Server
PACs
(Primary) (Backup)
The reader must substitute actual host names where applicable when applying this document.
Note: A DNS Server is not shown, but Host Name Resolution must be available via a DNS Server
(or properly configured Host files on each computer).
Revision History
• Revision 1.1 (June 2009): Minor corrections.
• Revision 1.0 (May 2009): Initial release for v2.1 (CPR9 SR1).
On the Network FactoryTalk Directory computer (HOST01), perform the following steps:
1. Install FactoryTalk Services Platform CPR9 SR1
2. Install FactoryTalk Activation Server. Obtain and install Historian SE Server activation files.
Note: The installation and configuration of activation can be postponed because the Historian
Server will run without activation for a grace period of 7 days.
On the FactoryTalk Historian SE server computer (HOST02), perform the following steps:
1. Install FactoryTalk Services Platform (FTSP) CPR9 SR1 and specify the FTD Server Location as
HOST01
2. Install FactoryTalk Activation Client and configure for activation from HOST01
3. Install FactoryTalk Historian SE Server, selecting setup type FactoryTalk Historian SE Server
Installation:
On both the primary and Backup interface computers (HOST04 + HOST05), perform the following steps:
1. Install FactoryTalk Services Platform (FTSP) CPR9 SR1 and specify the FTD Server Location as
HOST01
2. Install RSLinx Enterprise (or other Data Server)
3. Install FactoryTalk Historian SE, selecting setup type FactoryTalk Historian SE Live Data
Interface Installation:
1. On the primary interface computer (HOST04) launch the FactoryTalk Administration Console, select the
Network directory, and create:
• a FT Application (e.g., “MyFTApp”)
• an Area (e.g., “MyArea”)
• a Rockwell Automation Device Server (RSLinx Enterprise) on HOST04 with the redundant
Backup server on HOST05
• a shortcut (e.g., “SC1”) in RSLinx Enterprise pointing to the data source (e.g., ControlLogix) on
the Primary and Backup device servers.
2. Using the Rockwell Software Data Client, verify that you can browse to the tags in the data source and
put them on scan.
1. On the Historian SE Server (HOST02), launch the FactoryTalk Administration Console and select
Network.
2. In the Explorer window, expand the System folder then the Connections folder and then right-click on
the Historical Data folder and select New Historian Server Connection as shown below:
Note: In addition to the Historian Server on HOST02, this step also automatically created an instance of
the FactoryTalk Live Data (FTLD) interface on HOST02.
4. Click Finish.
5. This local instance of the FTLD interface cannot be utilized in a fault tolerant environment, so right click
on this instance of the interface and select “Delete” to remove it:
3. On the Network FTD computer (HOST01), use Windows Explorer to create a folder for the shared file
required by the redundant interfaces.
4. In “My Computer”, go to the C: drive, right-click and create a New Folder named FTH_Shared. Right-
click on this folder and select Sharing and Security…:
6. Click the Permissions button and give Everyone rights to Full Control, Change and Read:
7. Click OK on the Permissions and Sharing dialog boxes to save and close them. Also, close My
Computer.
1. On the primary interface computer (HOST04), launch the FactoryTalk Administration Console and select
Network.
2. Right-click on this Historian SE Server created in the previous section and select New Data Collection
Interface:
3. In the “Data Collection Interface Properties” window, change the “Computer hosting the interface”
option from the Historian SE Server (HOST02) to the primary interface computer (HOST04). Note: Do
NOT start the interface. Verify that the Startup type is “Automatic” and click Apply.
4. Click the Launch Interface Configuration Utility button to open the Interface Configuration Utility
(ICU). Select the Interface FTLD1 (FTLDINT1) > Host2:
6. After the Server entry (HOST02) has been added, click the checkbox next to the server name to verify
connectivity to the server. Once verified, right click on the entry for the interface computer (HOST04)
and select remove selected server. This entry is not needed as there is not an instance of Historian SE
server running locally.
1. On the primary interface computer (HOST04), select Tools > Buffering. The default on a new FTLD
Interface is for buffering to be disabled. Select the option to Enable buffering with PI Buffer
Subsystem.
2. Acknowledge the warning message and select Buffered Servers from the left hand pane. From the
Buffering to collective/server drop down box, select the entry for the Historian SE server (HOST02).
3. Click the Apply button to save the changes and OK to close the dialog.
Note: Unlike the primary interface, the backup interface is created initially using the Interface Configuration
Utility (ICU) - not the FactoryTalk Administration Console.
1. On the backup interface computer (HOST05), select Start > All Programs > Rockwell Software >
FactoryTalk Historian SE > Interface Configuration Utility to open the ICU.
2. Select SDK Connections under the Interface menu. This will open the PI Connection Manager dialog.
Select Add Server under the Server menu to open the Add Server dialog box. Enter the name of the
Historian SE server (HOST02) in the “Network Node” field and click OK. It is not necessary to enter a
password or change the default user name.
7. When ICU creates the interface, it will prompt for a server to associate the interface with. Select the
Historian SE computer (HOST02) from the list:
Note: The existing name is acceptable, but it should be changed to be consistent with the default name
of primary interface that was created with the FactoryTalk Administration Console.
9. Click Create in order to create the Windows service for the instance of the interface.
1. While remaining on the backup interface (HOST05), repeat the steps in the section entitled ‘Configure
Buffering on the Primary FTLD Interface’.
1. Return to the primary interface computer (HOST04) and the Interface Configuration Utility (ICU). If
you closed the ICU and need to re-launch it, be sure to select FTLD1 (FTLDInt1) > HOST02 using the
Interface list menu.
2. Select the UniInt-Failover sub-category in the left hand pane. Configure the dialog as shown below:
5. Click OK and then right-click on the tag area again and select Create Points (UFO Phase 2):
6. Click the Apply button at the bottom of the dialog box (but do not click the Close button).
1. Open the Services MSC (Start > All Programs Administrative Tools > Services). Double-click the
FTLD1 Service and select the LogOn tab.
2. Select This account and enter interactive user credentials that have access to the “FTH_Shared” folder
on the Network FTD (HOST01):
3. Click OK to close the FTLD1 properties dialog. You should receive a confirmation dialog.
4. Return to the ICU and start the FTLD1 interface using the toolbar icon:
7. This should open a command window showing indicating that the UniInt Failover is successfully
initialized and that the Primary is sending data to PI and “Backup interface not available”:
1. Return to the backup interface computer (HOST05) and the Interface Configuration Utility (ICU). If you
closed the ICU and need to re-launch it, be sure to select FTLDInt1 > HOST02 using the Interface list
menu.
2. Select the UniInt-Failover sub-category in the left hand pane. Configure the dialog as shown below:
Note: In the area below where you identified the Failover ID numbers, the status tags have already been
created. The status tags apply to both the primary and the backup interface.
3. Click the Apply button at the bottom of the dialog box (but do not click the Close button).
1. Open the Services MSC (Start > All Programs Administrative Tools > Services). Double-click the
FTLD1 Service and select the LogOn tab.
2. Select This account and enter interactive user credentials that have access to the “FTH_Shared” folder
on the Network FTD (HOST01):
3. Click OK to close the FTLD1 properties dialog. You should receive a confirmation dialog.
4. Return to the ICU and start the FTLD1 interface using the toolbar icon:
7. This should open a command window showing indicating that the UniInt Failover is successfully
initialized:
1. Using the server computer (HOST02) open the System Management Tools (SMT).
2. Select the HOST02 Server and Current Values plug-in under the Data category:
4. Click Select All and OK to add the 7 status tags to the Current Values view:
6. Verify that the fail over control tags report numeric values as shown and that the
FTLDInt1_UFO2_State_1 tag has a value of “Primary” and that the FTLDInt1_UFO2_State_2 tag has a
value of “Backup”:
7. Lastly create the desired Historian tags using either FactoryTalk Administration console or Excel. Verify
that data is collected for these points and that data collection continues after restarting the current
primary interface several times. Note: To monitor and control the status of both FTLD interfaces, use
the Interface List plug-in under the Interfaces category: