Redundancy Options
To access the configuration of the redundancy options, select the "Options..." command from the "Configuration" menu and select the "Redundancy" tab on the displayed dialog box.
Activation
This group defines the operation of the software in redundant mode.
Active with station
Check this box to activate the redundant mode with the station defined in the adjacent field (name of the network computer operating in redundancy with the local station). This name can be entered directly in the field or selected from the active computers of the network by clicking on the adjacent button .
The redundant station can also be designated by its IP address.
Main Station
This check box is used to define the operation of the two stations in redundancy. The main station is the station that will be active when both stations will operate normally. For the redundant mode to work correctly, one of the 2 stations must be defined as the main station (option checked) and the other station as secondary station (option not checked).
Local Id
This drop-down list displays the station identifier (1 or 2) for local data in redundant mode. This identifier makes it possible to designate in the XML configuration files the station to which a local data belongs. A XML configuration file contains all the data defined for each of the redundant computers, whether these data are defined as redundant or local to one of the computers.
This identifier should not normally be changed. It is automatically defined during the first configuration of the redundant stations, the station initially defined as the main station takes the identifier 1, the station defined as secondary station taking the identifier 2.
In case of bad configuration (same identifier on both stations), it can however be modified by clicking on the button on the right of the list, then by selecting the desired identifier in the list.
Redundancy switching
Choose from this list the selection mode of the active/inactive station in redundancy:
- Automatic : by default, the station defined as "Main Station" is active (it handles calls). In the event of a failure (acquisition or call media fault, depending on the options), the main station becomes inactive and the secondary station automatically becomes active.
- Manual synchronized : The selection of the active station (the one managing the calls) is controlled from an external application (supervision) via the Alert OPC server ("System.AlertLock") or its API ("_AlertLockAlarm" function). When a station is activated, the redundant station is automatically deactivated, and vice versa.
- Manual not synchronized : The selection of the active station (the one managing the calls) is controlled from an external application (supervision) via the Alert OPC server ("System.AlertLock") or its API ("_AlertLockAlarm" function). No synchronization is performed (both stations can be simultaneously active or inactive).
TCP/IP port
This field defines the port number used for TCP/IP exchanges between the 2 redundant stations. This number must be changed only if the default port (2495) is already used by another application on one of the 2 redundant stations.
The selected TCP/IP port is also the one that will be used for exchanges with client stations.
Distributed calls
When this option is selected, calls are distributed between the 2 stations. If the main station has no available port for the type of call to be made, it automatically delegates the call to the other extension.
When this operation mode is chosen, it is not necessary to switch from one station to another.
Trace
Check this option to display a trace window of the IP frames exchanged.
Remote station supervision
This group defines the polling cycle parameters for the remote station.
Network polling cycle
This parameter defines the polling period of the remote station. A TCP/IP link control is performed every time this timer expires.
Timeout on response
This parameter defines the waited time for responses in protocol exchanges.
Automatic synchronization
This group defines the synchronization options for the redundant stations and allows or disables the synchronization of alarms, acknowledgments and configuration on the 2 stations.
Synchronization on connection with the redundant station
When this option is checked, the configuration of the remote station (declared as redundant) is automatically synchronized with the redundant station when the network connection is established with this station.
If this option is not checked, and if the "Redundancy.SavingRedundantChanges" option is validated (default configuration), the modifications made on the local workstation that could not be transmitted to the redundant workstation (redundant workstation stopped or network connection failure) are automatically saved and forwarded automatically to the redundant station when the network connection with the redundant station is restored. These changes are saved if the software is stopped on the local computer ("itemchanges.xml" file).
Synchronization on most recent configuration
When this option is checked, the dates of modification of synchronized data between the redundant stations are compared to determine the values to be retained for synchronization. This option is particularly useful during automatic synchronization on connection with the redundant station when the configuration of the 2 stations is likely to have been modified on each of the stations.
Alarm status synchronization
Alarms detected on one station are automatically transmitted to the other station.
When the monitored application is redundant, this option is not necessary since the alarms are transmitted to each of the stations by their respective instances of the redundant application. However, this option can be used to increase the redundancy performance insofar as it allows to be able to process alarms coming from the other station in the event of simultaneous failure of the links on a station and of communication ports on the other station.
This option can be redefined at the level of each data server and each tag.
Acknowledgment synchronization
The call and alarm acknowledgments on one station are automatically transmitted to the other station.
When this option is enabled, alarm masks and unmasks are also synchronized.
Call synchronization
The status of the call progress on the active station is automatically transmitted to the other station.
Schedule synchronization
Any modification of the group's on-call schedule is automatically transmitted to the other station.
On call management synchronization
Any changes in the organization of the on-call duty (operators, groups, teams, derogation, etc.) is automatically transmitted to the other station.
Supervision synchronization
Any changes to the list of tags to be monitored are automatically transmitted to the other station. The tags declared as local (non-redundant) are not transmitted.
Programmed call synchronization
Any changes to programmed calls and synchronization calls with remote stations are automatically transmitted to the other station.
Parameter synchronization
Any modification of the operating parameters is automatically transmitted to the other station: alarm parameters, call parameters, vocal server configuration (messages and parameters).
Report synchronization
Any changes to the reports in the logbook are automatically transmitted to the other station.
Stop synchronization then restart after
Select this option to suspend the automatic synchronization of the stations (during a maintenance operation, for example).
For an automatic reactivation of the synchronization after a given time, enter the time corresponding to the desired synchronization suspension time in the adjacent field.
Manual synchronization
The synchronizations defined in this group will only be performed on demand, by clicking on the "Send" button to send the local configuration to the remote station, or on the "Receive" button to retrieve the configuration from the remote station.
Icon synchronization
Selection of the synchronization of the icons defined in the tree of the main screen.
Script synchronization
Selection of the synchronization of scripts and settings of Message Processor.