Os Server; Failure, Switchover And Restarting Redundant Os Servers - Siemens Simatic PCS 7 Function Manual

7.4

OS server

7.4.1

Failure, switchover and restarting redundant OS servers

Introduction
This section describes the criteria by which the master/standby identification of an OS server
changes. Examples are given to illustrate how the system reacts to failures.
Note
Information on updating operator stations with redundant OS servers in runtime can be found
in "guidelines on updating a redundant OS in runtime (Page 217)".
Fault scenarios
● The project is not activated on the redundant OS partner server.
● The network connection from the OS server to the redundant OS partner is disrupted.
● The network connection to the OS clients is disrupted.
● The process connection to the AS is disrupted.
● The PC station is not operating correctly.
Reaction of WinCC redundancy to possible faults
WinCC redundancy can react to faults, errors or error messages in the following ways:
● By saving events and the time they occurred
● By synchronizing the archives of the process data (Tag Logging) and message data (Alarm
Logging) with the archive data of the active OS server when a failed OS server is recovered.
● By changing the system tags "@RM_MASTER" and "@RM_MASTER_NAME" according
to the situation.
● By automatically interconnecting the OS clients with the preferred server or with the
available OS server with master identification. The "@RM_SERVER_NAME" tag indicates
for an OS client the OS server to which this OS client is currently connected.
● By generating process control messages in the message list.
The fault scenarios listed above and the resulting reactions by WinCC Redundancy are
described in the following.
High Availability Process Control Systems (V9.0)
Function Manual, 05/2017, A5E39221836-AA
Failure, switchover and reintegration of high availability components
7.4 OS server
205