Os Server - Siemens SIMATIC PCS 7 Function Manual

● Manual
● Operating Instructions
● Operating Instructions
● Operating Instructions
6.4

OS server

6.4.1 Failure, failover and restarting of 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 191)".
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), the message data (Alarm
● By changing the system tags "@RM_MASTER" and "@RM_MASTER_NAME" according
Fault-tolerant Process Control Systems (V8.0)
Function Manual, 03/2012, A5E02779471-02
SIMATIC; Communication with SIMATIC
Logging) and the user data (User Archives) with the archive data of the active OS server
when the failed server comes back online.
to the situation.
Failure, Switchover and Return of Fault-tolerant Components
SIMATIC NET; Industrial Ethernet Switches SCALANCE X-200
SIMATIC NET; Industrial Ethernet Switches SCALANCE X-300
SIMATIC NET; Industrial Ethernet Switches SCALANCE X-400
6.4 OS server
181