59
Setting up FactoryTalk system availability Chapter 14
Rockwell Automation Publication VIEWSE-UM006K-EN-E
353
A server with this status
Has these characteristics
Synchronizing with standby
The server becoming the Active server is synchronizing with its Standby partner.
After restarting, for example, an Active server will try to get a copy of the Standby
server’s state information, before going into service. This ensures that the latest
state information is used.
If the Standby server is unavailable, or if it fails during synchronization, the Active
server will go into service without its partner’s latest state information.
Synchronized - ready to be Active
The server becoming the Active server has finished synchronizing with its partner,
and is ready to become active.
Synchronizing with active
The server becoming the Standby server is synchronizing with its Active partner.
After restarting, for example, a Standby server will try to get a copy of the Active
server’
s state information, before becoming standby. This ensures that the latest
state information is used.
If the Active server is unavailable, or if it fails during synchronization, the Standby
server will become standby without its partner’s latest state info
rmation.
Synchronized - ready to be Standby
The server becoming the Standby server has finished synchronizing with its
partner, and is ready to become standby.
Active (Can’t reach partner)
The server is ready to provide service to clients, but its partner is not ready or
cannot be located.
This state is also shown if the Active server’s partner has not been defined.
Standby
The Standby server is ready to accept client connections and provide service to
clients, in the event that the Active server fails.
If the Active server fails, the Standby server’s status will change to Active (Can’t
reach partner) and the Standby server will provide service to connected clients.
Not configured
A secondary server is not configured.
What happens if a non-redundant HMI server fails
An Active, non-redundant HMI server might fail due to any of the following
conditions:
The HMI server is shut down with its host computer, from the Start
menu.
The HMI server is disconnected from the network. For information
about how the system monitors network connections, see Monitoring
network client and server connections on page 378.
The HMI server is found to be unhealthy, because an essential service
has stopped functioning.
The HMI server’
s host computer has a power failure.
When an HMI server fails, if the server is not set up with redundancy, it is
taken out of service. Within 5 seconds, Diagnostic messages are logged at
connected client computers, notifying operators of the failure.
Clients that were connected when the failure occurred will continue to run,
using a local cache of directory information.
RasterEdge Product Renewal and Update 4. Order email. Our support team will send you the purchase link. HTML5 Viewer for .NET; XDoc.Windows Viewer for .NET; XDoc.Converter for .NET; XDoc.PDF for .NET;
convert excel to pdf with hyperlinks; add hyperlinks pdf file
47
Chapter 14 Setting up FactoryTalk system availability
354
Rockwell Automation Publication VIEWSE-UM006K-EN-E
However, any data or services the failed HMI server provides, such as HMI
tag values, derived tags, command processing, or data logging, will be
unavailable.
For example, graphic objects connected to HMI tags in the server’s database
will show in outline form.
If connected clients are receiving data from other HMI or data servers, that
service will not be interrupted.
When the failed HMI server is restored, all connected clients in the system
can resume receiving data from the server, without having to be restarted.
The FactoryTalk Directory centralizes access to application resources and
components, such as graphic displays and tags, for all FactoryTalk products
participating in a control system.
The FactoryTalk Network Directory (also called the Network Directory)
manages FactoryTalk View SE network distributed applications, and
network station applications. All of the client and server computers
participating in a given network distributed application, or network station
application must point at the same Network Directory.
In the FactoryTalk Directory Server Location Utility, you can view the
current status of the Network Directory server:
(connected) means that all FactoryTalk products and components
participating in a FactoryTalk system, located on the current computer,
are connected to and communicating with the Network Directory
server computer.
(read-only) means that FactoryTalk system participants on the current
computer are disconnected from the Network Directory server and are
retrieving information from a local cache.
(unknown) means that the connection status is temporarily unknown,
for example, because the system is starting up and waiting to determine
which server is active, or is unable to determine the current status.
To check the status of the Network Directory server:
1. Select Start > All Programs > Rockwell Software > FactoryTalk
Tools > Specify FactoryTalk Directory Location.
2. You are prompted to log on to FactoryTalk. Type your name and
password, and then click OK.
To use the FactoryTalk Directory Server Location Utility, you must log
on as a user with administrative privileges at the Network Directory
and in Windows, on the computer where the utility is running.
Monitoring the
status of the
Network Directory
server
37
Setting up FactoryTalk system availability Chapter 14
Rockwell Automation Publication VIEWSE-UM006K-EN-E
355
3. In the FactoryTalk Directory Server Location Utility, look for the
status of the Network Directory server beside the label, Computer
hosting directory server:
What happens if the Network Directory server is
unavailable
The Network Directory server cannot be made redundant. Instead, if the
Network Directory becomes unavailable while client computers are
connected to an application, the clients continue to run, using a local cache of
directory information.
There is no need to restart previously connected clients; they will continue to
resolve tag addresses, read and write tag values, acknowledge alarms, and
open graphic displays, even if the tags and displays the clients require were
never used before.
While the Network Directory is unavailable, you cannot modify the structure
of any dependent application.
For example, you cannot add areas or servers to the application, create new
security accounts, or change system security policies.
When the Network Directory is available again, all dependent clients in the
system resume using the directory automatically.
The more protection you provide, the more dependable the entire control
system will be, in the event any hardware or software component fails.
The level of system availability increases with the number of redundant
system components. To protect against:
Programmable controller failures, make programmable controllers
redundant. For example, you can set up redundancy for Rockwell
Automation Logix5000 controllers.
Programmable controller network failures, install redundant
programmable controller networks, such as a Rockwell Automation’s
ControlNet network.
Redundancy as part
of a system
availability strategy
32
Chapter 14 Setting up FactoryTalk system availability
356
Rockwell Automation Publication VIEWSE-UM006K-EN-E
Information network failures, install a redundant Ethernet network
with a backup domain controller, network cables, and network
interface cards.
Host computer hardware failures, provide backup computers to host
application software such as FactoryTalk View SE.
FactoryTalk software failures, set up redundant FactoryTalk
View SE and RSLinx Enterprise application servers.
Planning the layout of a redundant system
The servers you can use in a FactoryTalk View SE network distributed
application are separate entities, which means they can be hosted on any
computer on the network.
However, when designing a redundant control system, you should keep in
mind the system requirements that apply to different types of servers.
For example, to support FactoryTalk Network Directory availability, it is
recommended that you run the directory server on a computer that you plan
to keep running.
This could be the same computer used to host a FactoryTalk View SE Server,
or a Rockwell Automation Device Server (RSLinx Enterprise).
Note: Do not run the FactoryTalk Network Directory on the same
computer as a Windows domain controller.
Example: An application with two redundant HMI server pairs
In its simplest form, a redundant FactoryTalk View SE application might
consist of one pair of redundant FactoryTalk View SE Servers (also called
HMI servers), and one pair of redundant RSLinx Enterprise servers.
In this example, two redundant server computer pairs host primary and
secondary HMI servers, and RSLinx Enterprise data servers.
30
Setting up FactoryTalk system availability Chapter 14
Rockwell Automation Publication VIEWSE-UM006K-EN-E
357
Tip:
The FactoryTalk Network Directory (on the first primary
computer in the following illustration) cannot be made
redundant. For information about what happens when
the Network Directory fails, see What happens if the
Network Directory server is unavailable on page 83.
Only one application server of any type, whether it’s a primary or secondary
server, can run on a single host computer. When designing a control system,
observe this and the other limits described in "About FactoryTalk View SE
system limits," next.
The overall design of the control system will ultimately depend on the
application’s size and computing needs, and on the level of redundancy
required to support the entire system.
For information about setting up redundancy for devices, networks, and other
types of servers the system might use, see the documentation for the specific
hardware or software.
About FactoryTalk View SE system limits
In a network distributed application, a single application server computer that
meets the recommended requirements could host all of the following:
One FactoryTalk View SE Server
One RSLinx Enterprise data server. (Optionally, you can enable
RSLinx Enterprise to distribute device-based FactoryTalk Alarms and
Events.)
One OPC-DA server (RSLinx Classic or some other OPC data server)
46
Chapter 14 Setting up FactoryTalk system availability
358
Rockwell Automation Publication VIEWSE-UM006K-EN-E
One FactoryTalk Tag Alarm and Event Server
The FactoryTalk Network Directory
However, if the network distributed application requires more HMI, data, or
alarm and event servers, it is recommended that you use multiple host
computers to distribute the load.
Tip: If you plan to deploy a network distributed application
that uses more than two servers (or two pairs of
redundant servers) and 20 clients, it is recommended
that you contact your local Rockwell Automation Sales
office for architectural assistance. For information about
setting up redundant FactoryTalk View SE Servers, see
Setting up FactoryTalk system availability on page 349 in
the
FactoryTalk View Site Edition User’s Guide
.
For information about hardware and operating system requirements that
might affect your application, see the FactoryTalk View Site Edition
Installation Guide.
FactoryTalk View SE redundant component limits
For best results when running redundant FactoryTalk View SE components
in a network distributed application, observe these limits:
50 is the maximum number of FactoryTalk View SE Clients that can
have simultaneous access to a network distributed application.
10 is the maximum number of redundant FactoryTalk View SE Servers
that can be used in a network distributed application. (Each
redundant server consists of a pair of primary and secondary servers.)
1 is the maximum number of redundant FactoryTalk View SE Servers
that can be hosted on a single computer.
Note: You might use one computer to host multiple HMI servers
while developing an application. When deploying the
application, however, ensure the primary and secondary HMI
servers in redundant pairs are hosted on separate computers.
For information about FactoryTalk View SE platform requirements that
might affect the design of a redundant system, see the FactoryTalk View Site
Edition Installation Guide.
For information about limits and requirements that apply to redundant data
servers (RSLinx Enterprise, RSLinx Classic, or another OPC-DA server), see
the product documentation.
34
Setting up FactoryTalk system availability Chapter 14
Rockwell Automation Publication VIEWSE-UM006K-EN-E
359
Activating FactoryTalk View SE in a redundant
system
To further maximize the availability of HMI data in a redundant FactoryTalk
system, ensure that FactoryTalk View SE software components can obtain
the necessary activations.
The FactoryTalk View SE Server software must be installed and activated on
the primary and the secondary HMI server in a redundant pair.
To ensure that HMI servers and FactoryTalk View SE Clients can always
obtain activation, it is recommended that activation be provided locally, on
server and client host computers.
For more information about activating FactoryTalk View software, see the
FactoryTalk View Site Edition Installation Guide.
For information about activating data servers, including RSLinx Enterprise
and RSLinx Classic, see the product documentation.
Tip: The FactoryTalk Network Directory is part of the
integrated FactoryTalk architecture.
Setting up redundant servers in FactoryTalk View
SE
You can specify an alternate server for any FactoryTalk View SE Server
(also called the HMI server), FactoryTalk Alarms and Events server, RSLinx
Enterprise server, or OPC data server (including RSLinx Classic) in a
network distributed application.
In FactoryTalk View SE, the alternate (or backup) server in a redundant
server pair is called the secondary server.
Summary of steps
In FactoryTalk View Studio, after you develop and test the network
distributed application, do the following for any type of application server
you want to make redundant:
1. Install and activate the necessary software on the secondary computer.
For information about installing the FactoryTalk View SE software,
see the FactoryTalk View Site Edition Installation Guide.
39
Chapter 14 Setting up FactoryTalk system availability
360
Rockwell Automation Publication VIEWSE-UM006K-EN-E
2. In Windows Explorer, copy any necessary files from the primary
server computer to the secondary server computer.
3. On the secondary server computer, specify the location of the
FactoryTalk Network Directory.
4.
In the primary server’s Properties dialog box, set up redundancy
options, and specify the name of the secondary server computer.
5. Ensure that data on the primary and secondary servers is identical:
For HMI servers, you can manually replicate changes from the
primary to the secondary server. For details, see Replicate changes
to the secondary HMI server on page 364.
For data servers, settings for topics and networks, for example,
must be identical. For information about setting this up, see the
product documentation.
For specific information about setting up redundancy for HMI servers, see
"Setting up a redundant HMI server pair" next.
These are the steps involved in setting up a redundant FactoryTalk View
SE Server (also called an HMI server), in a FactoryTalk View SE network
distributed application:
1. On the secondary server computer:
Install and activate the FactoryTalk View SE Server software. For
details, see the FactoryTalk View Site Edition Installation Guide.
Specify the location of the Network Directory for the application.
For details, see Setting up the FactoryTalk Directory on page 77.
Copy the primary HMI server’s project files to the secondary
server computer. For details, see Copy HMI project files to the
secondary computer on page 362.
2. On the primary sever computer:
Setting up a
redundant HMI
server pair
Documents you may be interested
Documents you may be interested
