its own System Management Multicast.

Doing this ensures that each SES cannot communicate with each other,
preventing duplicate SES alarms circulating the system.
To configure a different System Management Multicast for each cluster
1 Right click Node Administration.
2 Click Properties.
3 Select the Synchronized Repository Settings tab.
4 In the Settings Source box, select one of the machines.
5 Enable Override FTE / Heartbeat Multicast Address. Enabling this will make IP Multicast
Address
editable. The default IP Multicast Address is 1 above the FTE Multicast address, thus if the FTE Multicast
address is 224.0.0.107 then the default System Management Multicast address would be 224.0.0.108 as
shown in the diagram below.
6 In the IP Multicast Address box, enter a unique IP address. It is recommended that the first System
Management Multicast Address be 2 above the FTE Multicast Address and increment each subsequent
System Management Multicast Address by 1. It is not recommended to use the default System Management
Multicast address (1 above the FTE Multicast address) as new servers with SES will use it.
7 Click the Apply button. The Save Configuration window will display.
8 By default, all nodes/machines will be selected. Deselect all the nodes and then reselect the machines in the
cluster that you want within the System Management scope; thus you should select the servers, all connected
console stations and any other non-Experion nodes that have direct connection with the server/console
station. Failing to deselect other nodes will download the configured multicast address to those machines
and overwrite their existing multicast addresses.
9 As each cluster should have their own System Management Multicast address, repeat the instructions above
for every cluster.
Configuring the system for cluster-contained alarms
Once you have configured the system so that each cluster has its own System Management Multicast address, it
is very easy to set your system up for Cluster Contained SES Alarms so that SES alarms only circulate within
the cluster
CONFIGURING SYSTEM PERFORMANCE AND EVENT MONITORING
46 www.honeywell.com
To configure the system for cluster-contained alarms
1 Click Configure > System Hardware > Distributed Servers.
2 Click on the first distributed server (system number 2 onwards).
3 In the Configuration tab, in the Alarms and Data Subscription box select either Enable Data
Only or
Disable Both Alarm and Data.
Attention
If you select Enable Data Only, alarms from this distributed server will be disabled. If you select Disable both
Alarm and Data, both process data and alarms from this server will be disabled.
4 Repeat the above steps for all distributed servers.
Configuring the system for system-wide SES alarms
To enable System Wide Alarms you will need to configure distributed servers to send and receive both alarms
and process data.
To configure the system for system-wide alarms
1 Click on Configure > System Hardware > Distributed Servers.
2 Click on the first distributed server (system number 2 onwards).
3 In the Configuration tab, in the Alarms and Data Subscription combo box select Enable Both
Alarm and
Data.
4 Check that the Network tree has been enabled in the Asset Enable/Disable display from Configure >
Alarm Event Management > Alarm Enable/Disable.
5 Do this for all distributed servers.
Configuring Redirection Manager for different Server Management Multicast addresses
When a Redirection Connection is configured through System Management Display, HCI Name Service
Provider adds values to the local registry. It also replicates the values added to the registry to the other clusters
so the Redirection Connection will exist on external clusters.
When each cluster has different System Management Multicast addresses, HCI Name Service Provider is
unable to replicate the registry values outside of the multicast. This means that when you configure a
Redirection Connection the values will only be added to the local registry and not remote ones, meaning it will
only work within the cluster on which you configured it.
To configure Redirection Manager for different Server Management Multicast addresses
• Configure the same Redirection connection on each of the external clusters. Therefore, if you have three
clusters within your system and you configure a Redirection Connection on cluster A, you will need to
configure the same Redirection Connection on clusters B and C.
Configuring GUS Displays for different System Management Multicast addresses
Another area that does not get replicated properly is Aliases. Each machine in the system has a set of aliases to
represent different components on that machine. When a new component is added to the machine, it may add
more aliases to the existing alias list however different System Management Multicast addresses prevents the
new aliases from being replicated across the multicasts. As GUS displays relies on aliases this issue may affect
the behavior of GUS display operation.
Alias Generator enables you to select a machine on the network and add any of the aliases from that machine to
your local machine.
CONFIGURING SYSTEM PERFORMANCE AND EVENT MONITORING
47
To configure GUS displays for different System Management Multicast addresses
• Use Alias Generator to add the aliases from remote machines onto your local machine.
For instructions on Alias Generator, see the following topic in Knowledge Builder:
Experion > Configuration > System Management Configuration Guide > Generating a File using Alias
Generator.
Effects of different System Management Multicast addresses on HCI manager
HCI Name Service Provider scope works on the System Management Multicast address. Therefore when two
Name Service Providers are on the same multicast address, they can communicate with each other, when they
are on different multicast addresses they cannot. Configuring the system so that each cluster has its own System
Management Multicast address limits the scope of HCI Name Service Provider to cluster only. This affects
Redirection Manager configurations from being replicated across clusters and will also affect GUS displays
From

The Console Station provides direct access to process data and alarms and messages from Control Data Access
(CDA) sources such as Process Controllers, FIM, IOLIM, and ACE nodes. Each Console Station contains an
Experion CDA server to communicate directly with the CDA devices. This direct access provides a continuous
view of your process, even if the Experion server is unavailable.
After you configure the connection to the Experion server, the server database files are replicated to the Console
Station. This means that configuration of items such as process points is only done once. However, some
functionality such as reporting, history and events collection, and flexible point data are still provided by the
Experion server. Therefore whenever the Experion server is unavailable, this functionality is not available on
the Console Station.
A Console Station can also have clients connected to it. These clients are called Console Extension Stations. A
Console Extension Station connects to a Console Station in the same way a Flex Station connects to an
Experion server. A Console Extension Station has the same functionality as a Console Station.
A Console Station and Console Extension Station can operate in the following environments:
• Distributed system architecture
• Icon Series Console environment
• Multi-window environment
The following figure shows an example architecture including Console Stations.
Console Stations
Flex Stations
Process Controllers
ACE
Redundant
Servers
FTE
Console Extension Stations
If you have an Experion Station-TPS (ES-T) or an Experion Server-TPS (ESVT), see the Integrated Experion-
TPS Nodes (ES-T, ESVT, and ACE-T) User's Guide for more information about implementing these nodes.
Related topics
“Functionality available on Console Stations” on page 60
“Server wide settings” on page 135
Functionality available on Console Stations
The following functionality is always available on Console Stations regardless of the availability of the
Experion server:
• Data access from direct data sources such as Process Controllers and ACE nodes
• Notifications from direct sources
• Security restrictions, for example security levels and asset assignments
• Real-time trending of data from direct data sources such as Process Controllers
• Event journaling of Console Station events such as operator actions, for example, acknowledging alarms and
logging on
CONSOLE STATIONS AND CONSOLES
60 www.honeywell.com
• Display printing
• Backup and restore of the Console Station database
• 'Server-less' restart, whereby the Console Station can restart and begin communicating with process
controllers, without needing to connect to the Experion server.
You can check the status of a Console Station on the Console Station system status page.
CAUTION
To avoid synchronization issues while servers and Console Stations are offline, or while services are stopped,
avoid making Engineering changes to the system, such as adding controllers or changing tag names.
In addition, it is best practice to bring servers and Console Stations back online in the reverse order in which
they were taken offline. This also helps to reduce database-related synchronization issues.
Related topics
“About Console Station” on page 60
“What happens when the Experion server is unavailable” on page 61
“How server wide settings relate to Console Station” on page 62
“How global cache settings relate to Console Station” on page 63
“Console Station system status” on page 71
Engineering functionality not available on Console Stations
The following engineering functionality is not available on Console Stations and needs to be accessed via a Flex
Station.
• Controller configuration displays for the following controllers:
– 7800 Burner
– Allen-Bradley PLC5
– Bristol Babcock
– FSC
– Series 9000
– Safety Manager
– TDC 3000
– UDC
• HC900 and UMC800 set point program and recipe configuration for the following types of controllers:
– HC900/UMC800
– Micromax
– Series 9000
What happens when the Experion server is unavailable
When the Experion server becomes unavailable, for example during a server failover, an alarm is raised on the
Console Station to indicate that the Console Station is operating in a server unavailable mode. During this time,
the following functions on the Console Station are unavailable:
• History collection, assignment, retrieval and display
• Trend configuration
• Group configuration
• Chart visualization (Embedded CB Charts/Forms)
• Event and SOE Summary display
• Alarm and event printing
CONSOLE STATIONS AND CONSOLES
61
• Adding comments to alarms and events
• Report requests or report printing
• View or control of points and alarms from server connected controllers or other servers in a DSA
configuration
• External alarm notification from server connected controllers
• Configuration changes, for example server wide settings and asset assignment
• Engineering Tools configuration load/upload and snapshot save/restore
CAUTION
To avoid synchronization issues while servers and Console Stations are offline, or while services are stopped,
avoid making Engineering changes to the system, such as adding controllers or changing tag names.
In addition, it is best practice to bring servers and Console Stations back online in the reverse order in which they
were taken offline. This also helps to reduce database-related synchronization issues.
Limitations when performing Engineering operations from a Console Station and the server is shut down
The following table shows the limitations when the server is shut down and you perform Engineering operations
from a Console Station.
Engineering operations performed when servers were running
and the Console Station was shut down
Limitations on starting up console after servers are shut down
Load new points to the controller Checkpoint files on the Console Station will not be latest.
Restoring from this checkpoint file will not include the
newly loaded point.
Rename the point Alarms will be reported with the old point name instead of
newly renamed point.
Change Foundation Fieldbus Advanced Alarm configuration Foundation Fieldbus Advanced Alarm will be reported with
either old or empty conditions.
Delete controller Any active alarms on the deleted controller that appeared on
the console before shutting down will still appear to be in
alarm.
Once the server comes back online and the Console Station
synchronizes with the server, these active alarms from the
deleted controller will be removed from the console.
Related topics
“Functionality available on Console Stations” on page 60
How server wide settings relate to Console Station
The server wide settings that you can configure using the Server Wide Settings Station displays are applicable to
Flex Stations, Console Stations, and Console Extension Stations. When you add a Console Station to your
system, the server wide settings that have been defined on the server to which the Console Station is connected
are automatically applied operating properly.