Redundancy B

Preface
Open Source Software
Table of Contents
SICAM Redundancy Overview 1

SICAM PAS Redundancy in SICAM PAS 2
V8.14 Setting up Redundancy 3
Operating Redundancy 4
Redundancy Sample Configurations 5
PRP Network Redundancy 6
Literature
Index
E50417-H8976-C441-B9
NOTE
i For your own safety, observe the warnings and safety instructions contained in this document, if available.
Disclaimer of Liability Copyright

Subject to changes and errors. The information given in Copyright © Siemens 2019. All rights reserved.
this document only contains general descriptions and/or The disclosure, duplication, distribution and editing of this
performance features which may not always specifically document, or utilization and communication of the content
reflect those described, or which may undergo modifica- are not permitted, unless authorized in writing. All rights,
tion in the course of further development of the products. including rights created by patent grant or registration of a
The requested performance features are binding only when utility model or a design, are reserved.
they are expressly agreed upon in the concluded contract.
Document version: E50417-H8976-C441-B9.00 Trademarks
Edition: 11.2019
SIPROTEC™, DIGSI™, SIGRA™, SIGUARD™, SAFIR™, SICAM™,
Version of the product described: V8.14 and MindSphere™ are trademarks of Siemens. Any unau-
thorized use is prohibited. All other designations in this
document may represent trademarks whose use by third
parties for their own purposes may violate the proprietary
rights of the owner.
Preface
Purpose of the Manual
This manual provides all necessary information to set up redundant SICAM PAS systems. The system adminis-
trator or system engineer should be able to set up redundant systems equipped with redundant interfaces or
devices and identify problems in redundant systems.
Target Audience
This manual is mainly intended for customers and their employees who are involved in the configuration and
parameterization of substation automation systems.
Scope
This manual is valid for SICAM PAS.
Normen
SICAM PAS has been developed in compliance with ISO 9001:2008 standard.
Additional Support
For questions about the system, contact your Siemens sales partner.
Customer Support Center

Our Customer Support Center provides a 24-hour service.
Siemens AG
Customer Support Center
Humboldtstrasse 59
90459 Nuremberg
Germany
E-mail: support.energy@siemens.com
Training Courses
Inquiries regarding individual training courses should be addressed to our Training Center:
Siemens AG Phone: +49 (911) 433-7415
Siemens Power Academy TD Fax: +49 (911) 433-7929
Humboldtstrasse 59 E-mail: poweracademy@siemens.com
90459 Nuremberg Internet: www.siemens.com/poweracademy
Germany
Notes on Safety
This document is not a complete index of all safety measures required for operation of the equipment (module
or device). However, it comprises important information that must be followed for personal safety, as well as
SICAM, SICAM PAS, Redundancy 3

E50417-H8976-C441-B9, Edition 11.2019
Preface
to avoid material damage. Information is highlighted and illustrated as follows according to the degree of
danger:
! DANGER
DANGER means that death or severe injury will result if the measures specified are not taken.
² Comply with all instructions, in order to avoid death or severe injuries.
! WARNING
WARNING means that death or severe injury may result if the measures specified are not taken.
² Comply with all instructions, in order to avoid death or severe injuries.
! CAUTION
CAUTION means that medium-severe or slight injuries can occur if the specified measures are not taken.
² Comply with all instructions, in order to avoid moderate or minor injuries.
NOTICE
NOTICE means that property damage can result if the measures specified are not taken.
² Comply with all instructions, in order to avoid property damage.
NOTE
i Important information about the product, product handling or a certain section of the documentation
which must be given attention.
Qualified Electrical Engineering Personnel

Only qualified electrical engineering personnel may commission and operate the equipment (module, device)
described in this document. Qualified electrical engineering personnel in the sense of this manual are people
who can demonstrate technical qualifications as electrical technicians. These persons may commission,
isolate, ground and label devices, systems and circuits according to the standards of safety engineering.
Proper Use
The equipment (device, module) may be used only for such applications as set out in the catalogs and the
technical description, and only in combination with third-party equipment recommended and approved by
Siemens.
Problem-free and safe operation of the product depends on the following:
• Proper transport
• Proper storage, setup and installation
• Proper operation and maintenance
4 SICAM, SICAM PAS, Redundancy

E50417-H8976-C441-B9, Edition 11.2019
Preface
When electrical equipment is operated, hazardous voltages are inevitably present in certain parts. If proper
action is not taken, death, severe injury or property damage can result:
• The equipment must be grounded at the grounding terminal before any connections are made.
• All circuit components connected to the power supply may be subject to dangerous voltage.
• Hazardous voltages may be present in equipment even after the supply voltage has been disconnected
(capacitors can still be charged).
• Operation of equipment with exposed current-transformer circuits is prohibited. Before disconnecting the
equipment, ensure that the current-transformer circuits are short-circuited.
• The limiting values stated in the document must not be exceeded. This must also be considered during
testing and commissioning.

E50417-H8976-C441-B9, Edition 11.2019
E50417-H8976-C441-B9, Edition 11.2019
Open Source Software
The product contains, among other things, Open Source Software developed by third parties. The Open
Source Software used in the product and the license agreements concerning this software can be found in the
Readme_OSS. These Open Source Software files are protected by copyright. Your compliance with those
license conditions will entitle you to use the Open Source Software as foreseen in the relevant license. In the
event of conflicts between Siemens license conditions and the Open Source Software license conditions, the
Open Source Software conditions shall prevail with respect to the Open Source Software portions of the soft-
ware. The Open Source Software is licensed royalty-free. Insofar as the applicable Open Source Software
License Conditions provide for it you can order the source code of the Open Source Software from your
Siemens sales contact – against payment of the shipping and handling charges – for a period of at least 3
years since purchase of the product. We are liable for the product including the Open Source Software
contained in it pursuant to the license conditions applicable to the product. Any liability for the Open Source
Software beyond the program flow intended for the product is explicitly excluded. Furthermore any liability
for defects resulting from modifications to the Open Source Software by you or third parties is excluded. We
do not provide any technical support for the product if it has been modified.

E50417-H8976-C441-B9, Edition 11.2019
E50417-H8976-C441-B9, Edition 11.2019
Table of Contents
Preface.......................................................................................................................................................... 3
Open Source Software..................................................................................................................................7
1 Redundancy Overview................................................................................................................................13
2 Redundancy in SICAM PAS..........................................................................................................................15

2.1 Redundancy in SICAM PAS.................................................................................................16
2.2 Redundancy Types............................................................................................................ 18
2.2.1 System Redundancy.....................................................................................................18
2.2.2 Interface Redundancy.................................................................................................. 19
2.2.3 Device Redundancy..................................................................................................... 20
2.2.4 Full Redundancy (Both System Redundancy and Interface Redundancy)........................20
2.2.5 Redundant Communication with a Control Center........................................................21
2.3 Basic Group.......................................................................................................................23
2.4 Switchover........................................................................................................................24
2.4.1 Computer and System Switchover................................................................................24
2.4.2 Switching over the Basic Group....................................................................................25
2.4.3 Interface Switchover....................................................................................................25
2.4.4 Device Switchover....................................................................................................... 25
2.4.5 Control Center Switchover........................................................................................... 25
2.4.6 Switchover for GOOSE Publisher and GOOSE Status Monitoring....................................25
2.4.7 Switchover Times........................................................................................................ 25
2.4.8 Prioritization of Connections........................................................................................ 26
2.5 Dependency......................................................................................................................27
3 Setting up Redundancy.............................................................................................................................. 31
3.1 Network Configuration for Redundant Systems..................................................................32
3.1.1 Network Configuration with 1 Teaming Adapter...........................................................32
3.1.2 Network Configuration with 2 Network Interface Cards................................................ 32
3.1.3 Network Configuration with Several Network Adapters................................................ 33
3.1.4 Configuration Steps..................................................................................................... 35
3.1.4.1 Changing the HOSTS File........................................................................................35
3.1.4.2 Changing the Order of the Network Adapters......................................................... 36
3.2 Setting up Redundant Interfaces........................................................................................38
3.3 Setting up System Redundancy......................................................................................... 41
3.3.1 Setting up System Redundancy.................................................................................... 41
3.3.2 Transferring the Configuration.....................................................................................42
3.4 Notes on the Setup of Additional SICAM PAS Components................................................. 45
3.4.1 SICAM PQ Analyzer, Incident Explorer.......................................................................... 45

E50417-H8976-C441-B9, Edition 11.2019
Table of Contents
3.4.2 SICAM PQ Analyzer...................................................................................................... 45

3.4.3 SICAM SCC.................................................................................................................. 46
3.4.4 SoftPLC....................................................................................................................... 46
4 Operating Redundancy...............................................................................................................................49
4.1 System Redundancy during Operation............................................................................... 50
4.2 System Redundancy Impact on Commands........................................................................52
4.3 Redundancy State in SICAM PAS UI – Operation................................................................. 53
4.4 System (System Switchover)............................................................................................. 55
4.5 Preferring an Interface (Interface Switchover)....................................................................58
4.6 SICAM PAS UI – Operation Client....................................................................................... 61
4.6.1 Starting and Stopping Data Links in Redundant Systems............................................... 62
4.6.2 Isolating Systems in SICAM PAS UI – Operation Client................................................... 63
5 Sample Configurations............................................................................................................................... 71
5.1 Overview.......................................................................................................................... 72
5.2 TCP/IP-Based Devices......................................................................................................... 74
5.2.1 Devices with TCP/IP-Based Communication...................................................................74
5.2.2 TCP/IP-Based Devices, Redundant System, Redundant Interfaces...................................74
5.2.3 Redundant TCP/IP-Based Devices, Redundant System....................................................75
5.3 Devices with Serial Communication................................................................................... 77
5.3.1 Serial Devices, Redundant Systems.............................................................................. 77
5.3.2 Serial Multi-Channel Devices, Redundant Systems........................................................ 78
5.3.3 Redundant Serial Single-Channel Devices, Redundant System.......................................78
5.3.4 Redundant Serial Multi-Channel Devices, Redundant System........................................ 79
5.4 Control Centers with TCP/IP-Based Communication............................................................ 80
5.4.1 Control Center via TCP/IP, Redundant Interfaces........................................................... 80
5.4.2 Control Center via TCP/IP, Redundant Systems..............................................................80
5.5 Control Centers with Serial Communication.......................................................................82
5.5.1 Serial Communication with Redundant System............................................................ 82
5.5.2 Serial Communication with Redundant Interface.......................................................... 82
5.5.3 Serial Single-Channel Communication with Redundant System.....................................83
5.5.4 Redundant Serial Communication with Redundant System........................................... 84
6 PRP Network Redundancy.......................................................................................................................... 85

6.1 What is PRP....................................................................................................................... 86
6.2 PRP System Structure........................................................................................................ 87
6.3 Terms Used in the Context of PRP...................................................................................... 88
6.4 PRP Components............................................................................................................... 90
6.4.1 PRP-Capable Switch (Oversized Frames)....................................................................... 90
6.4.2 PRP-Capable Network Card (Oversized Frames and Software Support).......................... 90
6.4.3 PRP Software (SIMATIC NET SOFTNET-IE RNA).............................................................. 90
6.4.4 SIPROTEC Devices........................................................................................................ 91
6.4.4.1 SIPROTEC 4 with PRP EN100 Module.......................................................................91
6.4.4.2 SIPROTEC 5 with Ethernet Module.......................................................................... 92
6.4.5 Redundancy Box (RedBox) / SIMATIC NET SCALANCE X204RNA EEC.............................. 92
6.5 Procedure for Setting up a PRP System...............................................................................94
6.5.1 Recommendations.......................................................................................................94

E50417-H8976-C441-B9, Edition 11.2019
Table of Contents
6.5.2 Setup Order to Be Observed.........................................................................................94

6.6 Sample Configuration....................................................................................................... 95
6.7 Diagnosis.......................................................................................................................... 96
6.7.1 SNMP / SICAM PAS Device Descriptions........................................................................ 96
6.7.2 SIPROTEC 4 with PRP EN100 Module............................................................................ 98
6.7.2.1 SNMP / SICAM PAS Device Descriptions................................................................... 98
6.7.2.2 EN100 Module PRP Homepage............................................................................... 98
6.7.3 SIPROTEC 5 with Ethernet Module................................................................................99
6.7.3.1 SNMP / SICAM PAS Device Description.................................................................... 99
6.7.3.2 Ethernet Module PRP Homepage............................................................................ 99
6.8 Frequently Occurring Problems and Troubleshooting....................................................... 101
Literature.................................................................................................................................................. 103
Index.........................................................................................................................................................105

E50417-H8976-C441-B9, Edition 11.2019
E50417-H8976-C441-B9, Edition 11.2019
1 Redundancy Overview
In complex systems such as power distribution systems, the failure of individual devices can cause unpredict-
able problems in operating processes. You can set up redundant SICAM PAS systems in order to minimize the
risk of failure in your stations.
The term redundancy designates the existence of functionally identical resources if these are not required for
trouble-free operation. In SICAM PAS, redundancy designates the existence of:
• 2 identically configured SICAM PAS systems
• Several communication paths between the SICAM PAS systems and the devices
• Redundantly set up devices
Hot Standby
Depending on the protocol, hot standby is supported for redundancy. If a device operates in hot standby
mode, the interface which controls the process has a complete process image of the device and can immedi-
ately take over the control of the device concerned. With all other protocols, a general interrogation must be
performed first in order to ensure that the interface has a process image.
Understanding Redundancy in SICAM PAS

In a SICAM PAS system, redundancy can be set up on different levels:
• System redundancy
The term system redundancy designates the existence of 2 Full Servers with identical functions
(including DIPs). One of the systems is the primary system and the other is the secondary system. If the
primary system (or parts thereof) fails, the secondary system takes over control.
[dw_System_redundancy, 2, en_US]
Figure 1-1 System Redundancy

E50417-H8976-C441-B9, Edition 11.2019
Redundancy Overview
• Interface redundancy
Interface redundancy supports the communication with other SICAM PAS components via redundant
communication links. If, for example, the SICAM PAS system cannot contact a device via the primary
interface, the system switches over to the secondary interface.
[dw_Interface_redundancy, 2, en_US]
Figure 1-2 Interface Redundancy
• Device redundancy
The term device redundancy designates that devices are designed redundantly (for example, 2 identical
bay controllers for the same primary process). The process can still be monitored and controlled even if
one device or the communication link to a device fails.
[dw_Device redundancy, 2, en_US]
Figure 1-3 Device Redundancy

For more information, refer to 2 Redundancy in SICAM PAS.
Configuring Redundancy
In SICAM PAS UI – Configuration, redundancy can be set up on the system level and the interface level.
For more information, refer to 3 Setting up Redundancy.
Operating Redundancy
If redundancy has been set up in a SICAM PAS system, you can view the status of a redundant SICAM PAS
system or of redundant interfaces in SICAM PAS UI – Operation. In addition, you can switch over redundant
systems and redundant interfaces: If this happens, the secondary system or secondary interface becomes
active.
For more information, refer to 4 Operating Redundancy.
Examples of Redundant Configurations

Depending on the redundantly designed components (for example, devices, communication paths, and
system) and their features, SICAM PAS enables a large number of redundant configurations.
For more information, refer to 5 Sample Configurations.

E50417-H8976-C441-B9, Edition 11.2019
2 Redundancy in SICAM PAS
Overview
This chapter provides background information on the implementation of redundancy in SICAM PAS.
2.1 Redundancy in SICAM PAS 16
2.2 Redundancy Types 18
2.3 Basic Group 23
2.4 Switchover 24
2.5 Dependency 27

E50417-H8976-C441-B9, Edition 11.2019
Redundancy in SICAM PAS
2.1 Redundancy in SICAM PAS

The term redundancy designates the existence of functionally identical resources - provided that these are
usually not required for trouble-free operation. In SICAM PAS, redundancy can be implemented on the
following levels:
• 2 functionally identical SICAM PAS systems (Full Server and DIPs)
• Functionally identical communication paths between the Full Server / DIP and the devices or control
centers
• Functionally identical devices
Definitions
The following terms are used in this manual:
• SICAM PAS system

A SICAM PAS system consists of a Full Server and up to 6 DIPs.
• Primary system
The SICAM PAS system which controls the process under normal conditions is referred to as the primary
system.
• Secondary system
The secondary system is a functionally identical system which ensures the communication with
connected devices and control centers in situations where a fault has occurred.
• Process controlling system / standby system

For more information, refer to Operating Modes of Redundant Systems, Page 18.
The term system redundancy designates the existence of 2 functionally identical SICAM PAS systems.
For more information, refer to 2.2.1 System Redundancy.
The term interface redundancy designates the existence of 2 communication paths to the devices or
higher-level systems.
For more information, refer to 2.2.2 Interface Redundancy.
The term device redundancy designates the existence of 2 functionally identical devices (each). Device
redundancy is implemented via interface redundancy: The SICAM PAS system perceives the devices as
one single device which is controlled via 2 separate interfaces.
For more information, refer to 2.2.3 Device Redundancy.
• Full redundancy
In SICAM PAS systems with full redundancy, both system redundancy and interface redundancy has
been configured.
For more information, refer to 2.2.4 Full Redundancy (Both System Redundancy and Interface Redun-
dancy).
• Switchover
The process during which the control of a device is transferred from one Master to another Master is
referred to as switchover. A switchover is initiated via an operator action if the communication path
which currently controls the process has failed or if serious problems (for example, failure of a hardware
component, or software error) have occurred.
For more information, refer to 2.4 Switchover.

E50417-H8976-C441-B9, Edition 11.2019
Legend
The following symbols are used in the diagrams in this manual:
Table 2-1 Symbols Used
Symbol Description
SICAM PAS computer (Full Server or DIP)
Network between SICAM PAS computers

For more information, refer to 3.1 Network Configuration for Redundant Systems.
Primary communication path between the SICAM PAS computers and the communica-
tion partners (devices and control centers)
Secondary communication path between the SICAM PAS computers and the communi-
cation partners (devices and control centers)
Fault
Device
Serial splitter
Network switch

E50417-H8976-C441-B9, Edition 11.2019
2.2 Redundancy Types

You can define the following redundancy types in SICAM PAS UI – Configuration:
• Full redundancy (including both system redundancy and interface redundancy)
2.2.1 System Redundancy
If there is a system redundancy, 2 functionally identical SICAM PAS systems (Full Servers and DIPs) are avail-
able in the substation. Both systems use the same configuration. Both systems are connected to the devices
and control centers via functionally identical communication links.
[dw_System_redundancy_FS, 2, en_US]
Figure 2-1 System Redundancy
Operating Modes of Redundant Systems

One system is the process controlling system and the other system is the standby system. Some centralized
processes are only active on the process controlling system. These processes are assigned to the basic group,
refer to 2.3 Basic Group.
The standby system can control the communication with control centers and devices (if, for example, the
communication between the process controlling system and the devices is disturbed).
Redundancy of DIPs
A SICAM PAS system consists of a Full Server and up to 6 DIPs. In redundant systems, the Full Server and the
DIPs are set up redundantly.
[dw_DIP_redundancy, 2, en_US]
Figure 2-2 Redundancy of DIPs (Redundant SICAM PAS system with 2 DIPs)

E50417-H8976-C441-B9, Edition 11.2019
Independent of the Full Server's redundancy status, a DIP can either control the process or be in standby
mode.
2.2.2 Interface Redundancy
The term interface redundancy designates that 2 functionally identical paths are available for communication
between the SICAM PAS system and the partner (device or control center).
[dw_Interface_redundancy, 2, en_US]
Figure 2-3 Interface Redundancy
Operating Modes of Redundant Interfaces

Depending on the protocol implementation in SICAM PAS, different communication modes exist:
• Active mode
The active Master controls the devices, receives messages from the device and forwards them to higher-
level applications.
• Standby mode
Master computers in standby mode actively communicate with the devices. In the same way as active
Masters, they receive messages from the device, maintain their own process image of the device and can
initiate general interrogations.
They do not send commands and do not forward received information to higher-level applications.
• Passive mode
Master computers in passive mode listen to the communication between the active application and the
device without transmitting data. They do not maintain their own process image of the device.
They do not start general interrogations, do not forward received information to higher-level applications
and do not send commands to substations.
• Inactive mode
Inactive Master computers do not receive data from the devices. They do not maintain a process image
of the device.
The following table provides a list of the protocols, which support standby mode and passive mode.
Table 2-2 Protocols with Standby Mode and Passive Mode
Protocol Standby mode Passive mode

IEC 60870-5-101 X X
IEC 60870-5-103 X X
IEC 60870-5-104 (SICAM MIC) X
IEC 61850 X
SNMP X
NOTE
i PROFINET IO Master does not support Interface redundancy.

E50417-H8976-C441-B9, Edition 11.2019
Dependent/Independent Mode
Depending on the communication properties of the devices and higher-level systems, redundant interfaces
can be set up in independent or dependent mode.
For more information, refer to 2.5 Dependency.
2.2.3 Device Redundancy
Device redundancy designates that 2 functionally identical devices perform the same task. The SICAM PAS
system perceives the redundant devices as one single device with 2 interfaces.
In SICAM PAS UI – Configuration, device redundancy is implemented as interface redundancy.
[dw_Device redundancy, 2, en_US]
Figure 2-4 Device Redundancy
2.2.4 Full Redundancy (Both System Redundancy and Interface Redundancy)
If system redundancy and interface redundancy have been activated, 4 functionally identical paths provide for
the communication between the SICAM PAS systems and the device. Each system is connected to the device
via 2 interfaces.
[dw_Full_redundancy, 2, en_US]
Figure 2-5 Full Redundancy, not for Communication via IEC 61850
Device redundancy designates that 2 functionally identical devices are connected to the SICAM PAS systems.

E50417-H8976-C441-B9, Edition 11.2019
[dw_Full_redundancy_with_redundant_device, 2, en_US]
Figure 2-6 Full Redundancy with Redundant Devices, not for Communication via IEC 61850
[dw_Full_redundancy_with_redundant_device_61850, 2, en_US]
Figure 2-7 Full Redundancy with Redundant Devices, Communication via IEC 61850
2.2.5 Redundant Communication with a Control Center
The communication to a control center can be set up redundantly. The configuration depends on the redun-
dancy type.
Redundant Communication in the Case of System Redundancy

If system redundancy has been activated, 2 systems are connected to the control center.
[dw_system_redundancy_CC, 2, en_US]
Figure 2-8 System Redundancy for Communication with the Control Center

E50417-H8976-C441-B9, Edition 11.2019
Redundant Communication in the Case of Interface Redundancy

If redundancy has been activated for the interface towards the control center, 2 communication paths are
available between the SICAM PAS system and the control center.
[dw_Interface_redundancy_CC, 2, en_US]
Figure 2-9 Redundancy of Interfaces towards the Control Center
Redundant Communication in the Case of Full Redundancy

If system redundancy and interface redundancy have been activated, 4 functionally identical paths exist for
communication between the SICAM PAS systems and the control center.
[dw_Full_redundancy CC, 2, en_US]
Figure 2-10 Interface and System Redundancy

E50417-H8976-C441-B9, Edition 11.2019
2.3 Basic Group
2.3 Basic Group

From the point of view of the Redundancy functionality, some components are combined to a group. If a fault
has occurred, the components of this group cannot be switched over individually. If a fault subject to switch-
over has occurred for one of these components, the entire basic group is switched over and becomes active on
the other computer.
This basic group is mainly defined by the central components:
• DSI Central Server
• Configuration database
• SoftPLC
• PAS applications
The following Master protocols belong to the basic group:
• PROFIBUS DP
• OPC Client
• SINAUT LSA ILSA

The following Slave protocols also belong to the basic group:
• Telegyr 8979 Slave
• CDT Slave
• OPC XML DA Server
• OPC Server

E50417-H8976-C441-B9, Edition 11.2019
2.4 Switchover
2.4 Switchover
A switchover is performed if the currently process controlling path for communication between the SICAM PAS
systems and the communication partner or an application is disturbed. Depending on the component
concerned and the fault which has occurred, the switchover takes place for a specific interface or application,
for the basic group or for the overall system.
A switchover is performed, for example, under the following conditions:
• Communication failure (cable break)
• If there is a device redundancy: failure of the primary device
• Hardware error in a SICAM PAS computer
• Manual switchover
2.4.1 Computer and System Switchover
A computer or the system is switched over if one of the following events has occurred:
• Failure of the process controlling SICAM PAS system
• Manual computer switchover
System Switchover Due to a Failure of the Process Controlling System

Both systems permanently exchange operating and process data. This ensures, for example, that both systems
maintain their own, complete process image of the overall system.
The system in standby mode realizes that the process controlling system has failed because it no longer replies
to requests. If this happens, the system in standby mode takes over the process control.
If the process controlling Full Server has failed, the Full Server in standby mode takes over the process and a
switchover takes place for connected DIPs.
If a DIP has failed, a switchover is only performed for this DIP. All computers which are not affected will remain
in their redundancy status.
Manual Switchover
A manual switchover is performed for a specific computer. This means that the redundancy status of Full
Servers and DIPs can be modified independently of each other.
During a manual computer switchover, all processes are switched over from the process controlling computer
to another computer.
The DIPs are not switched over during a manual system switchover. They can be switched over separately.
Switching over DIPs
• During a manual switchover of the Full Server, the DIPs are not switched over.
• The process controlling Full Server executes the required data exchange with those DIPs which still
control the process.
• If the process controlling Full Server fails, the DIPs are also switched over.
• DIPs can be manually switched over. This has no effect on the redundancy status of the Full Servers, and
the process controlling Full Server remains in this status.
Switching the Process Control Back

The process controlling computer remains active even if the previously process controlling computer is back in
operation.

E50417-H8976-C441-B9, Edition 11.2019
2.4 Switchover
2.4.2 Switching over the Basic Group
Communication errors of a protocol of the basis group result in a switchover of the entire basic group if the
communication with all devices of an interface is affected. If only the communication to one single device is
disturbed whereas the communication with other devices is still running, no switchover takes place. The basic
group is also switched over if a component of the basic group has failed.
2.4.3 Interface Switchover
An interface switchover takes place if the communication to a device is disturbed. If there is a communication
switchover, only the communication with the affected device is switched over.
An interface is switched over under the following conditions:
• Communication with one device disturbed
• Manual switchover
If the communication to a device is disturbed, an interface switchover takes place for the communication with
the affected device. The device-specific switchover is not possible if the interface is operated in dependent
mode or if the interface belongs to a protocol of the basic group.
The switchover can also be initiated by the user (manual switchover).
2.4.4 Device Switchover
A switchover between 2 devices takes place under the same conditions as an interface switchover. For the
SICAM PAS system, device redundancy is implemented as interface redundancy.
For more information, refer to 2.4.3 Interface Switchover.
2.4.5 Control Center Switchover
In the case of redundant communication with a control center, the switchover is initiated by the control
center. All interfaces can take over communication, but the control center must specify via which interface the
communication takes place.
2.4.6 Switchover for GOOSE Publisher and GOOSE Status Monitoring
In a redundant configuration only one GOOSE Publisher at a time sends data.

Since the receipt of GOOSE messages is not confirmed by the subscriber, an automatic switchover does not
take place for every possible error scenario. An automatic switchover only takes place for errors which can be
detected by the GOOSE Publisher, for example, the failure of the network card or a SICAM PAS computer.
Via a SoftPLC (Automation) the switchover of the GOOSE Publisher can be optimized project-specifically by
using status information (_OperReady, _ComFault).
In case of erroneous GOOSE status monitoring, a switchover does not takes place.
2.4.7 Switchover Times
The switchover times in response to faults depend on the fault detection time and the necessity of a computer
switchover. The detection time depends on the protocol and the configuration.
The following table indicates the detection times and switchover times for the SICAM PAS system.

E50417-H8976-C441-B9, Edition 11.2019
2.4 Switchover
Table 2-3 Detection Times and Switchover Times
Fault Detection time Switchover time

Cable break 0.5 s – 10 s < 250 ms (interface switchover)
Failure of a device (protocol- and configuration-
dependent)
Cable break 0.5 s – 10 s < 2 s (basic group switchover)
Failure of a device (protocol- and configuration-
(Basic group) dependent)
SICAM PAS software error <3s < 2 s (basic group switchover)
(Failure of a component of the
basic group)
Isolation (SICAM PAS hardware <3s < 2 s (computer switchover)
failure)
Manual computer switchover – <2s
Manual interface switchover – < 250 ms
2.4.8 Prioritization of Connections
If either system redundancy or interface redundancy has been activated, there are 2 possible communication
paths between the SICAM PAS systems and the devices. In the case of system redundancy, the connection to
the primary system is preferred. In the case of interface redundancy, the primary interface is preferred.
If both system redundancy and interface redundancy have been activated, there are 4 possible communication
paths between the SICAM PAS systems and the devices.
[dw_Priorities, 2, en_US]
Figure 2-11 Prioritization of Connections
Priorities for connections are assigned according to the following principle:

1 Primary system, primary connection
2 Secondary system, secondary connection
3 Primary system, secondary connection
4 Secondary system, primary connection
The order of prioritization is defined automatically and cannot be influenced. By means of cabling, you can
define which connections (or devices if there is a device redundancy) are operated with which priority.
You can prefer a connection, refer to 4.5 Preferring an Interface (Interface Switchover).

E50417-H8976-C441-B9, Edition 11.2019
2.5 Dependency
2.5 Dependency
Depending on the communication properties of the devices and higher-level systems, redundant interfaces
can be set up in independent or dependent mode.
If the communication partner can only communicate with one Master/Client (or Slave/Server) at the same time
– for example, protection devices with a serial interface – the interface must be parameterized in dependent
mode.
If the communication partner is equipped with 2 serial interfaces or if the communication partner supports
several Clients (or Servers), the independent mode can be defined in the SICAM PAS system.
In independent mode, only one device is switched over if a fault has occurred; in dependent mode, all devices
of an interface are switched over.
These modes define the switchover behavior of the SICAM PAS system for configurations in which several
devices are controlled via the same interface.
The following table indicates which protocols support the independent and dependent modes.
Protocol Independent mode Dependent mode
IEC 61850 Client MMS list X
GOOSE status monitoring X
IEC 61850 Server MMS list X
GOOSE publisher X
IEC 60870-5-101 X X
IEC 60870-5-103 X X
IEC 60870-5-104 X X1
DNP3 serial X X
DNP3i via TCP/IP X X
MODBUS serial X X
via TCP/IP X
PROFINET IO X
SNMP X
SIMEAS R X
SICAM Q80 X X
Dependent Mode
If devices are only equipped with one single interface, the communication in SICAM PAS UI – Configuration is
set up in dependent mode. The dependent mode ensures that 2 Master computers cannot communicate
simultaneously with the devices via the same communication link. The dependent mode is mainly applied for
serial configurations.
[dw_Dependent_mode, 2, en_US]
Figure 2-12 Configuration in Dependent Mode
1 Only for the Master protocol if system redundancy has been activated

E50417-H8976-C441-B9, Edition 11.2019
2.5 Dependency
In this mode, switchovers must take place for the specific interface. This means that a switchover is initiated
if the communication with the devices connected to this interface is disturbed. If this happens, the communi-
cation with all other devices is switched over.
[dw_Dependent_mode_switchover, 2, en_US]
Figure 2-13 Interface-Specific Switchover
If the communication with an individual device fails, no switchover takes place.
[dw_Dependent_mode_no_switchover, 2, en_US]
Figure 2-14 No Switchover if Faults are Detected on a Device
Independent Mode
If the devices support the communication with 2 Master computers (they are, for example, equipped with 2
serial interfaces), the interfaces can be set up in independent mode. In independent mode, all Master
computers can communicate with the devices without any communication conflicts occurring.
[dw_Independent_mode, 2, en_US]
Figure 2-15 Configuration in Independent Mode
In this mode, the communication can be switched over for a specific device on which a fault has occurred.

E50417-H8976-C441-B9, Edition 11.2019
2.5 Dependency
[dw_Independent_mode_switchover, 2, en_US]
Figure 2-16 Device-Specific Switchover

E50417-H8976-C441-B9, Edition 11.2019
E50417-H8976-C441-B9, Edition 11.2019
3 Setting up Redundancy
Overview
This chapter describes how to set up redundant systems and interfaces in SICAM PAS.
3.1 Network Configuration for Redundant Systems 32
3.2 Setting up Redundant Interfaces 38
3.3 Setting up System Redundancy 41
3.4 Notes on the Setup of Additional SICAM PAS Components 45

E50417-H8976-C441-B9, Edition 11.2019
Setting up Redundancy
3.1 Network Configuration for Redundant Systems

Redundant systems exchange process and system data among each other during operation. For this communi-
cation, they use a network adapter (to be specified).
A system adapter is a network adapter which manages the internal system communication between the
computers of a SICAM PAS system. A maximum number of 2 system adapters is supported.
At least 2 independent transmission routes are require for the redundant communication of 2 SICAM PAS
systems. Redundant communication can be implemented via:
• 1 teaming adapter or
• 2 Network interface cards (NIC)

The network adapter can be configured via SICAM PAS UI – Configuration on System level, General parame-
ters. For more information, refer to 3.3.1 Setting up System Redundancy.
As a prerequisite for system redundancy, all SICAM PAS computers must be located in the same domain and
the same user must be logged on. If you log on as a local user, you must use the same user name and the
same password on both systems.
3.1.1 Network Configuration with 1 Teaming Adapter
The teaming adapters are connected to a network via 2 switches. They ensure that one faulted network
component does not result in a failure of the entire communication.
The following figure shows the use of a teaming adapter for the system internal communication and the
communication to IEDs.
[dw_Network_configuration_teaming, 1, en_US]
Figure 3-1 System with 1 Teaming Adapter
3.1.2 Network Configuration with 2 Network Interface Cards
The SICAM PAS computers (Full Server and DIPs) are connected to a network via 2 network interface cards.
They ensure that one faulted network component does not result in a failure of the entire communication.

E50417-H8976-C441-B9, Edition 11.2019
[dw_Network_configuration_2_NIC, 1, en_US]
Figure 3-2 System with 2 Network Interface Cards
3.1.3 Network Configuration with Several Network Adapters
For network configurations with several network adapters, the networks must be set up in such a way that all
SICAM PAS computers (Full Servers and DIPs) communicate among each other via the same network.
If multiple network adapters are present, the redundant connection between the SICAM PAS computers can be
configured via these adapters. In this case, a teaming adapter is not absolutely necessary.
NOTE
i Both network cards, respectively their IP addresses, must not be in the same subnet.
Communication with the devices and higher-level systems can be set up via the same network or via a sepa-
rate network. The following network configurations are available:
• Communication via Network Switches, Page 33
• Communication via Crossover Cables (Optional), Page 35
Communication via Network Switches

You can interconnect the teaming adapters of the SICAM PAS computers via 2 network switches and connect
the devices to the SICAM PAS computers via the same network or via a separate network.

E50417-H8976-C441-B9, Edition 11.2019
For more information on connection to IED refer to:

3.1.1 Network Configuration with 1 Teaming Adapter and 3.1.2 Network Configuration with 2 Network Inter-
face Cards.
[dw_Network_configuration_teaming_2_switches, 1, en_US]
Figure 3-3 Network Configuration via 2 Network Switches
You can interconnect the network interface cards of the SICAM PAS computers via 2 network switches and
connect the devices with the SICAM PAS computers via the same network or via a separate network.
For more information on connection to IED refer to:
3.1.1 Network Configuration with 1 Teaming Adapter and 3.1.2 Network Configuration with 2 Network Inter-
face Cards.
[dw_Network_configuration_2_NIC_2_Switches, 1, en_US]
Figure 3-4 Network Configuration via 2 Network Interface Cards and 2 Network Switches

E50417-H8976-C441-B9, Edition 11.2019
Communication via Crossover Cables (Optional)

If you have defined a configuration without DIPs and only with serial connections, you can directly intercon-
nect the Full Servers using crossover cables.
[dw_Network_configuration_teaming_x-over, 1, en_US]
Figure 3-5 Network Configuration with Crossover Cables and Teaming Adapter
[dw_Network_configuration_2_NIC_x-over, 1, en_US]
Figure 3-6 Network Configuration with Crossover Cables and 2 Network Interface Cards
Read the notes concerning the setting of IP addresses in /4/ SICAM PAS/PQS, Configuration and Operation.
3.1.4 Configuration Steps
The following steps must be performed for the configuration of the network:
• Define which network adapter shall be used as system adapter (the system adapter is used for redun-
dant communication).
• Enter the IP addresses and network names of both systems in the HOSTS file of both systems.
• Define the order of the network adapters in the operating system.
3.1.4.1 Changing the HOSTS File

The HOSTS file includes the definitions for the assignment of IP addresses to computer names. The operating
system uses this file in order to read the IP addresses of other computers on the local level (if, for example, no
Domain name system is available in the network).
The IP addresses of the system adapters of both SICAM PAS systems must be entered in the HOSTS files of
both systems. The HOSTS file is located under the following path:
C:\WINDOWS\system32\drivers\etc\hosts
Here, you only enter the IP addresses of the system adapter for both Full Servers and all DIPs (and not the IP
addresses of other network adapters).

E50417-H8976-C441-B9, Edition 11.2019
# Copyright (c) 1993-1999 Microsoft Corp.

#
# This is a HOSTS sample file which is used by Microsoft TCP/IP
# for Windows 2000.
#
# This file includes the assignments of the IP addresses to the host names.
# Each entry must be written in a separate line. The IP address should be
# indicated in the first column, followed by the corresponding host name.
#
# The IP address and the host name must be separated by at least one blank.
#
# Additional comments (like in this file) can be inserted in individual
# lines or behind the computer name, but must be entered with the '#'
# character.
#
# Example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x Client host
127.0.0.1 local host
# Enter the IP addresses of all PAS computers, e.g.:
192.168.101.1 primary_full_server
192.168.100.1 primary_full_server
192.168.101.101 secondary_full_server
192.168.100.101 secondary_full_server
192.168.101.11 dip_primary
192.168.100.11 dip_primary
192.168.101.111 dip_secondary
192.168.100.111 dip_secondary
NOTE
i Windows 7 Professional and Windows Server 2008 do not allow to edit the HOSTS file directly within the
Windows directory.
If you use one of these operating systems, copy the HOSTS file to another directory (outside of the
Windows directory), for example to the Desktop. Edit the copied file there and save it to the Windows direc-
tory C:\WINNT\system32\drivers\etc\hosts, overwriting the existing file.
3.1.4.2 Changing the Order of the Network Adapters

You can determine the order of the network adapters in the operating system. If the operating system is to
transmit data via the network, it browses the list of network adapters. If the operating system finds a
connected network adapter, it tries to transmit the data. If the communication partner is not connected to this
network adapter, the operating system continues its search until the data has been transmitted.
You must change the order of the network adapters in such a way that the system adapters have top priority.
You will find these settings under Control Panel > Network Connections > Advanced > Advanced Settings.
When using 2 network interface cards, the priority of the cards must match the SICAM PAS configuration.

E50417-H8976-C441-B9, Edition 11.2019
[sc_Sequence_network_adapter, 1, en_US]
Figure 3-7 Order of the Network Adapters
Under Connections, select the system adapter and click the Shift up arrow until the system adapter is
displayed at the uppermost position.
Siemens recommends to restart the computer.

E50417-H8976-C441-B9, Edition 11.2019
3.2 Setting up Redundant Interfaces

To set up redundant interfaces:
² Insert the application in the SICAM PAS system.
² Insert an interface in the applicaten. This interface is the primary interface. Configure the interface.
[sc_Adding_interface_master, 1, en_US]
Figure 3-8 Setting up an Interface
² Activate Redundancy for the interface.
[sc_Activating_interface_redundancy, 1, en_US]
Figure 3-9 Activating Interface Redundancy

E50417-H8976-C441-B9, Edition 11.2019
² Define whether the interface is to operate in Independent mode or Dependent mode.

Not all protocols support both operating modes. SICAM PAS UI – Configuration displays an error if you
select a dependency mode, which is not supported, refer to 2.5 Dependency.
[sc_Selecting_dependence_independence, 1, en_US]
Figure 3-10 Selecting the Mode
² Configure the redundant interface.

Depending on the application, some parameters can only be set up for the primary interface (they also
apply to the redundant interface), whereas others can be separately defined for both interfaces.
[sc_Configuring_redundant_interface, 1, en_US]
Figure 3-11 Configuring a Redundant Interface
² Insert the devices.

E50417-H8976-C441-B9, Edition 11.2019
² Configure the parameters for the redundant interface on the device.
[sc_Configuring_redundant_interface_device, 1, en_US]
Figure 3-12 Configuring the Redundant Interface on the Device

E50417-H8976-C441-B9, Edition 11.2019
3.3 Setting up System Redundancy

Be aware of the following when setting up a redundant system:
• Make sure that both systems always use the same configuration.
If the runtime configurations differ in redundant systems, the non-process controlling system stops, and
system redundancy is therefore not available.
• If possible, use a separate computer for project configuration.

The non-process controlling system stops as soon as you change the configuration in one system. It only
becomes active again after you have transferred the changed configuration to the system.
• For IEC 61850 devices:

If you set up IEC 61850 devices using SCD files, you activate system redundancy and interface redun-
dancy before you import the SCD files. The SCD files describe the configuration of all instances of the
device.
• For other devices:

If possible, you first set up the system without redundancy and test it carefully before you activate redun-
dancy.
The number of possible error sources increases if there are redundant systems. The causes of errors can
be identified more conveniently in a non-redundant system.
• After the configuration has been modified, you transfer it to both systems.
For more information, refer to /4/ SICAM PAS/PQS, Configuration and Operation.
3.3.1 Setting up System Redundancy
To set up system redundancy:

² Activate Redundancy for the system.
[sc_Activating_system_redundancy, 1, en_US]
Figure 3-13 Activating System Redundancy

E50417-H8976-C441-B9, Edition 11.2019
² Adapt the configuration for the secondary system:

– Computer name
– IP addresses
The second IP address must remain empty. The doubling in the redundancy case is performed via the
teaming adapter.
If the physical connections are doubled via the teaming adapter, the IP address 2 must remain empty.
If the physical connections are doubled via 2 network interface cards, the IP address 2 must contain the
same data which has also been entered in the HOSTS files of the systems. For more information, refer to
3.1.4.1 Changing the HOSTS File.
[sc_Configuring_redundant_system, 1, en_US]
Figure 3-14 Setting up Parameters of the Redundant System
NOTE
i In SICAM PAS UI – Operation, the redundant system is displayed with the name which you have entered in
the Name field. The entry in the Computer name field is not displayed in this context.
² Check the configurations of the interfaces and devices which have already been set up.
Depending on the application, some parameters only need to be defined for the primary system (because
they are applied automatically to the secondary system), whereas others must be separately defined for
both systems.
3.3.2 Transferring the Configuration
As soon as the configuration has been completed, it must be transferred to both Full Servers.
NOTE
i No SICAM PAS UI – Configuration license is required for the following system configuration activity.
To transfer the configuration to a system:

² Start SICAM PAS UI – Operation on the Full Server.

E50417-H8976-C441-B9, Edition 11.2019
[sc_Transferring_configuration, 1, en_US]
Figure 3-15 Transferring the Configuration
² In the Status section, select the With database copy option.

² Click Update system.
The database is updated on the redundant Full Server.
The system update is logged in the Report.
If you update the system for the first time, you are prompted in the Report to restart the redundant Full Server
and all DIPs connected.
[sc_2_reporter_initial_update_system_redundant, 1, en_US]
Figure 3-16 Report - Initial System Update
If the system is updated after a change, the redundant Full Server and the DIPs are restarted automatically.

E50417-H8976-C441-B9, Edition 11.2019
[sc_4_reporter_2nd_update_system_redundant, 1, en_US]
Figure 3-17 Report - System Update after Database Changes
For more information, refer to /4/ SICAM PAS/PQS, Configuration and Operation.
If both systems have been updated to the new, redundant configuration, you can view the system's redun-
dancy status in SICAM PAS UI – Operation:
[sc_Redundant_System_in_UI_Operate, 1, en_US]
Figure 3-18 Redundant System in SICAM PAS UI – Operation
The symbols indicate the status of the systems:

Process controlling system
Standby system
The tree structure on the left-hand side shows the topology configured in SICAM PAS UI – Configuration. If you
select a topology element, the redundancy status of the element is displayed, refer to 4.3 Redundancy State in
SICAM PAS UI – Operation.

E50417-H8976-C441-B9, Edition 11.2019
3.4 Notes on the Setup of Additional SICAM PAS Components

The following paragraphs provide notes concerning the setup of additional SICAM PAS components for a
redundant SICAM PAS system:
• 3.4.1 SICAM PQ Analyzer, Incident Explorer
• 3.4.2 SICAM PQ Analyzer
• 3.4.3 SICAM SCC
• 3.4.4 SoftPLC
3.4.1 SICAM PQ Analyzer, Incident Explorer
Both redundant SICAM PAS computers call up fault records independently of each other, that is, from protec-
tion devices and SIMEAS R devices. They save these fault records in their archives. In the same way, PDR
records are created and archived by both SICAM PAS computers. This ensures that this data is saved in an
archive even if there is a failure of a SICAM PAS computer.
Since, however, no archive comparison takes place on this level, these archives can have different contents. In
order to obtain a complete, consistent archive, an archive computer can be used. Using the
SICAM PQ Collector on this computer, the SICAM PQ Analyzer retrieves the data from both SICAM PAS
computers and combines them in a (Collector) archive.
[dw_PQ_Incident_Explorer_in_redundant_system, 1, en_US]
Figure 3-19 Collecting Fault Records/PDRs in Redundant Systems
In order to perform the archiving procedure in a redundant manner as well, 2 archive computers can be used.
The SICAM PQ Collector, which is active on both computers, ensures that the (Collector) archives are
compared on this level.
For more information, refer to the /14/ SICAM PQ Analyzer, Incident Explorer.
3.4.2 SICAM PQ Analyzer
Contrary to fault records and PDR records, PQ data is subjected to extensive compression and evaluation func-
tions after their transmission from the PQ devices and archived with all results. In the context of a redundant
system configuration, archive gaps caused by computer failures – in contrast to fault records – do not remain
without retroactive effects. Different archive gaps in both computers would lead to different results with
regard to compression and evaluation in particular. To prevent this, PQ data in the redundant system is exclu-
sively collected, evaluated and archived by the primary SICAM PAS computer. If the primary SICAM PAS
computer fails, the PQ data remain in the PQ devices with a large memory capacity (of 1 to 2 GB). As soon as
the primary SICAM PAS computer is available again, the PQ data available will be called up and compressed,
evaluated and archived.

E50417-H8976-C441-B9, Edition 11.2019
Measuring gaps only occur if the primary SICAM PAS computer has been out of operation for a period which
exceeds the period during which the PQ devices can save the data.
[dw_PQ_Analyzer_in_redundant_system, 1, en_US]
Figure 3-20 SICAM PQ Analyzer in a Redundant SICAM PAS system
NOTE
i Project-specific specifications in the PQ Inspector view (for example, creation of measuring point groups)
must be performed on the (source) archive of the primary SICAM PAS computer. To do this, you must select
the primary SICAM PAS computer in the archive selection in the SICAM PQ Analyzer (on the archive
computer).
For more information, refer to the /14/ SICAM PQ Analyzer, Incident Explorer.
3.4.3 SICAM SCC
SICAM SCC always communicates with both SICAM PAS systems at the same time in order to prevent the risk
of an interruption of the process interfacing if there is a failure of a communication link. In the monitoring
direction, this approach ensures that messages and measured values from the process are actually transmitted
to SICAM SCC - independent of the Full Server from which the information originates. Commands from SICAM
SCC are always sent to one of the SICAM PAS systems.
Configuring Redundant SICAM PAS Systems in SICAM SCC

When configuring the communication, you must activate the redundant communication link in the WinCC
Explorer and enter the IP addresses of both the SICAM PAS Full Servers.
Configuring Redundant SICAM SCC Systems in SICAM PAS UI – Configuration

To configure a redundant SICAM SCC system, you must enter the IP addresses of both the SICAM SCC Servers
in SICAM PAS UI – Configuration.
The data in both SICAM SCC systems is therefore identical. This means that you can create the redundant
SICAM SCC system via the WinCC Project Duplicator without performing additional steps.
For more information, refer to /5/ SICAM SCC, Human Machine Interface SICAM SCC.
3.4.4 SoftPLC
Tags which are marked with the RETAIN key word are saved persistently by the SoftPLC. The persistent data of
the RETAIN tags is loaded during the system startup.
In a redundant system, both systems save the RETAIN data on the local computer. When the Standby system
starts up and the Master system is already in operation, the standby system accepts the values from the
Master system during start-up.

E50417-H8976-C441-B9, Edition 11.2019
The SoftPLC is active in the Standby system, but does not send any commands in the command direction and
does not forward any messages in the monitoring direction.
For more information, refer to /7/ SICAM PAS, Automation Blocks.

E50417-H8976-C441-B9, Edition 11.2019
E50417-H8976-C441-B9, Edition 11.2019
4 Operating Redundancy
Overview
In SICAM PAS UI – Operation, you can view the status of redundant interfaces and systems. Additionally, you
can switch over the preferred communication path.
SICAM PAS/PQS UI – Operation Client provides the functions of SICAM PAS/PQS UI – Operation from a local
computer or a remote computer with improved performance by an Internet browser.
4.1 System Redundancy during Operation 50
4.2 System Redundancy Impact on Commands 52
4.3 Redundancy State in SICAM PAS UI – Operation 53
4.4 System (System Switchover) 55
4.5 Preferring an Interface (Interface Switchover) 58
4.6 SICAM PAS UI – Operation Client 61

E50417-H8976-C441-B9, Edition 11.2019
4.1 System Redundancy during Operation

Adjusting Parameter Changes during Operation
Some operating parameters can be modified during operation. These parameters are saved in order to ensure
that they remain up to date after a system restart. These online parameters include:
• Bay blocking
• Telecontrol blocking
• Switching authority
• (Marker) commands in the SoftPLC (Automation)
• Data of the SoftPLC which is saved persistently

If both systems are in operation, these parameters are saved in both systems. If a system is not in operation
while the changes occur, the online parameters are adjusted during booting (for more information refer to the
following paragraph).
Redundant Systems during Booting

The diagram illustrates the process during booting:
[dw_Runtime_system, 1, en_US]
Figure 4-1 SICAM PAS System during Booting
While booting, a redundant system behaves as follows:
• The system checks whether the computer name of the partner system in the network can be read.
If no DNS is available in the network, the IP addresses of the Full Servers must be entered in the HOSTS
file of the Full Servers. For more information, refer to 3.1.4.1 Changing the HOSTS File.

E50417-H8976-C441-B9, Edition 11.2019
• The system tries to establish a connection to the partner system.

– After the connection to the partner system has been set up successfully, the system requests
the compatibility key of the partner system.
If the compatibility keys of both systems are identical, the system boots. It synchronizes its operating
state with the operating state of the partner system.
– If the compatibility keys of both systems are not identical, the system does not boot. The partner
system still remains active.
NOTE
i If possible, do not boot both Full Servers at the same time. Wait until one Full Server has booted completely
before you start the second Full Server.

E50417-H8976-C441-B9, Edition 11.2019
4.2 System Redundancy Impact on Commands
4.2 System Redundancy Impact on Commands

During the time from command request to command termination an event might occur, stopping the commu-
nication on the current connection and causing a switchover to the other communication connection.
Events Causing a Switchover
• Communication problem on the connection
• Device does not respond
• User sets preference for the other interface/connection
• User switches off the active interface
• User switches off the active device
• Active system fails
• Active interface fails

A switchover can only happen if the second connection is ready to take over.
If you identify a negative termination with additional cause within a switching sequence in SFC
(refer /7/ SICAM PAS, Automation Blocks, Chapter 11.3), you can:
• check if there was a switchover.
• check if the command was successful, regardless of the negative termination.
• wait some time (approx. the time for command execution) so that the new connection can start the
communication and get fully updated by its general interrogation.
Commands with feedback information
• check the feedback information for the command.

The command succeeded if it shows the new value. If not, resend it again, but watch any locking in the
device itself.
Commands without feedback information
• resend the command and watch the device reply.

E50417-H8976-C441-B9, Edition 11.2019
4.3 Redundancy State in SICAM PAS UI – Operation

To view the redundancy state of an object, open a system with redundancy (interface redundancy or system
redundancy) in SICAM PAS UI – Operation, select an object and open the Redundancy state section. If both
system redundancy and interface redundancy have been configured for an object, the redundancy state of all
4 communication partners is displayed.
[sc_Redundancy_state, 1, en_US]
Figure 4-2 Redundancy State in SICAM PAS UI – Operation
The icons to the left of the entries in the configuration tree show the current status of the individual data links.
• Click the arrow next to the project, a system, an application, or an interface in order to view subordinate
data links.
• Click the icon or the name of an entry in the tree structure in order to view details on the system status in
the Status section (that is, the right-hand window section).
Table 4-1 Status Displays
Icon Status display Color Explanation

Project folder Red The project configuration was changed while SICAM
PAS/PQS UI – Operation was displayed.
Incorrect compatibility key Yellow/ The parameterization of the application (for example,
black SoftPLC, exchanged IP address) does not match the
current SICAM PAS/PQS project.
Values invalid Yellow The connection currently does not provide valid
values.

E50417-H8976-C441-B9, Edition 11.2019

Starting Violet System start-up: The connection was activated by
SICAM PAS/PQS, but the device or system does not yet
respond.
Possible causes:
Temporary status: The component responds shortly
afterwards, and the connection is then active
(running).
The component has failed.
The component has been disabled on the hardware
side.
Stopping Violet The connection is being shut down.
The connection is deactivated, but the component
has not yet responded.
Temporary status, the connection is interrupted
shortly afterwards (stopped).
Starting Violet System start-up
(blocked) The connection is blocked by a bay/telecontrol block.
Stopping Violet The connection is being shut down.
Running Green The connection is active.
Stopped Blue The connection has stopped.
Running Green The connection is active.

Stopped Blue The connection is stopped.
Bay/telecontrol block Blue The bay block or telecontrol block is enabled.
(ON)
Bay/telecontrol block Blue The bay block or telecontrol block is disabled.
(OFF)
Table 4-2 Status Displays – Redundancy

Active Green One redundant component is active, the other
component is not active.
Active Green One redundant component is active and blocked by a
(blocked) bay or telecontrol block. The other component is inac-
tive.
Inactive Blue The connection of the redundant component is inac-
tive.
Inactive Blue The connection of the redundant component is inac-
(blocked) tive and blocked by a bay or telecontrol block.
Standby mode Violet The redundant component runs in standby mode.
Invalid state Red Both redundant components are turned to master or

run in standby mode concurrently.

E50417-H8976-C441-B9, Edition 11.2019
4.4 System (System Switchover)

If system redundancy has been activated, you can prefer a system. Protocols and applications will run pref-
erably on this system.
To prefer a system:
² Select the system node from the project tree.
[sc_Selecting_red_system_in_UI_operate, 1, en_US]
Figure 4-3 Selecting a System
² In the Redundancy state section, click Switching preferred system.

The Switch active system dialog opens.

E50417-H8976-C441-B9, Edition 11.2019
[sc_Dialog_switch_active_system, 1, en_US]
Figure 4-4 Switch Active System Dialog
² Select the preferred system on which you want the applications to run and click OK.
If no system has been selected, the primary system is preferred.
If possible, a switchover to the preferred system is performed.
[sc_System_switched_over, 1, en_US]
Figure 4-5 Successful Switchover of the Preferred System
If no faults have occurred, the system and the protocols are switched over. The setting is saved in the data-
base. The preference status is maintained during a system start.
For more information refer to 2.4.1 Computer and System Switchover.

E50417-H8976-C441-B9, Edition 11.2019
Removing the Preference

To remove the preference:
² Open the Switch active system dialog.
² Remove the checkmark for the preferred system and click OK.
[sc_Dialog_switch_active_system_no_selection, 1, en_US]
Figure 4-6 Removing the System Preference
If you remove the preference, the system and the protocols are not switched over.

E50417-H8976-C441-B9, Edition 11.2019
4.5 Preferring an Interface (Interface Switchover)

If system redundancy or interface redundancy has been activated for a certain interface, you can prefer one of
the interfaces. If possible, the communication link among the systems and devices is established via this inter-
face.
If the preferred interface has failed, a switchover to the interface with the next higher priority is performed.
For more information, refer to 2.4.8 Prioritization of Connections.
To prefer an interface:
² Select the interface from the project tree.
[sc_Selecting_red_interface_in_UI_operate, 1, en_US]
Figure 4-7 Selecting an Interface
² In the Redundancy state section, click Switching preferred interface.

The Switch active interface dialog opens. In the following screenshot, both System redundancy and
Interface have been activated. If only one of them is active, two interfaces are available.
The interfaces are displayed in their order of priority. For more information, refer to 2.4.8 Prioritization of
Connections.

E50417-H8976-C441-B9, Edition 11.2019
[sc_Dialog_switch_active_interface, 1, en_US]
Figure 4-8 Switch Active Interface Dialog
² Select the interface which you want to prefer and click OK.
If there are no problems with the preferred communication link, the communication switches over to the
preferred interface.
[sc_Interface_switched_over, 1, en_US]
Figure 4-9 Interface Switched over Successfully
If you prefer an interface, the preference is saved in the database. The preference status is maintained during
a system start.

E50417-H8976-C441-B9, Edition 11.2019
Removing the Preference

To remove the preference:
² Open the Switch active interface dialog.
² Remove the checkmark for the preferred interface and click OK.
[sc_Dialog_switch_active_interface_no_selection, 1, en_US]
Figure 4-10 Removing the Interface Preference

E50417-H8976-C441-B9, Edition 11.2019
4.6 SICAM PAS UI – Operation Client

SICAM PAS/PQS UI – Operation Client provides the functions of SICAM PAS/PQS UI – Operation from a local
computer or a remote computer with improved performance by an Internet browser.
[sc_Operation_Client_GOOSE, 1, en_US]
Figure 4-11 SICAM PAS UI – Operation Client
In the Redundancy state section, the preferred system or interface can be selected by using the Switching
preferred system and the Switching preferred interface respectively from the list box.
For more information on the SICAM PAS UI – Operation Client, refer to /4/ SICAM PAS/PQS, Configuration and
Operation.
Table 4-3 Menu Icons added to the Web Browser
Icon Command Explanation

Split window Displays the redundant systems side by side
Un-split window Displays the redundant system to which SICAM PAS/PQS UI – Opera-
tion Client is connected
About Displays the version of SICAM PAS/PQS UI – Operation Client
Help Opens the online help of SICAM PAS/PQS UI – Operation Client
The following GOOSE status indications are available in SICAM PAS/PQS UI – Operation Client only.
The icons to the right of the entries in the configuration tree show the current GOOSE status of the individual
data links.
• In order to view subordinate data links, click the arrow next to the application or an interface.
• In order to view details on the GOOSE list status, select the GOOSE status tab for the corresponding
device.

E50417-H8976-C441-B9, Edition 11.2019
Table 4-4 Status Displays – GOOSE Status Monitoring

GOOSE list working fine Green The GOOSE lists are periodically received from the
device within the defined time range (3x TTL).
Values of the system indications:
• SysGooseEna_[ListName] = 2
• SysGooseStat_[ListName] = 2
Starting Violet The connection was activated by SICAM PAS/PQS, but
the device or system does not yet respond.
GOOSE list disabled Blue The GOOSE list has been stopped by the user.
GOOSE list not received Red The GOOSE lists are enabled, but at least 1 GOOSE list
has not been received.
Values invalid Yellow The connection currently does not provide valid
values.
4.6.1 Starting and Stopping Data Links in Redundant Systems
Starting and Stopping Data Links in Redundant Systems

Starting and stopping data links at the interface or device level independently from each other is applicable in
SICAM PAS/PQS UI – Operation Client for the following protocols:
• IEC 60870-5-101 Master/Slave
• IEC 60870-5-103 Master
• IEC 60870-5-104 Master/Slave
• IEC 61850 Server/Client
• DNP3 Master/Slave
• Modbus Master/Slave
• PROFINET IO Master
• SIMEAS R Master
• SICAM Q80 Master
• SNMP Master
• SICAM MIC Master

To activate a data link:
² Select an inactive link at the application, interface, or device level in the configuration tree.
² Click Start for the required link in the Redundancy state section.

E50417-H8976-C441-B9, Edition 11.2019
[sc_Start_Oper_Client, 1, en_US]
Figure 4-12 Starting a Data Link in SICAM PAS UI – Operation Client in Redundant Systems
If you activate a link, all the communications to the level start.

To deactivate a data link:
² Select an active link in the configuration tree.
² Click Stop for the required link in the Redundancy state section.
If you deactivate a link, all the communications to the level stop.
4.6.2 Isolating Systems in SICAM PAS UI – Operation Client
With Isolate system in SICAM PAS UI – Operation Client you cancel the redundancy function. Thus you can
apply changes to the configuration of one computer while the other computer continues to perform the
runtime functionality.
To access both systems with SICAM PAS UI – Operation Client, you must validate the security certificates on
both computers. For more information, refer to /4/ SICAM PAS/PQS, Configuration and Operation.
The diagram illustrates the process of isolating systems.

E50417-H8976-C441-B9, Edition 11.2019
[dw_workflow_sicam-pas-ui, 2, en_US]
Figure 4-13 Isolating Systems in SICAM PAS UI – Operation Client
NOTE
i To perform the entire system isolation process with only short interruption of the runtime, select the
system displayed in the right-hand section as the preferred system (*) and then perform the changes to the
system shown in the left-hand section.

E50417-H8976-C441-B9, Edition 11.2019
The following example shows how to add a connection to a control center via IEC 60870-5-104 Slave for an
existing redundant configuration with IEC 61850 devices.
[sc_Isolating_system_00_start, 1, en_US]
Figure 4-14 Redundant System with IEC 61850 Devices
Proceed as follows to perform changes in the configuration of a redundant system:

²
Click the icon.
The SICAM PAS UI – Operation Client window splits into 2 sections displaying the configuration of the
process-controling system (right-hand side) and the standby system (left-hand side). The systems are
displayed in the same order as in SICAM PAS UI – Configuration. (The left/right-hand system in SICAM PAS
UI – Configuration is displayed on the left/right-hand section respectively.)
[sc_Isolating_system_01, 1, en_US]
Figure 4-15 Redundant Systems Displayed Side by Side

E50417-H8976-C441-B9, Edition 11.2019
NOTE
i Isolate system is only available on the standby system (left-hand side) for the Full Server on project level.
² Click Isolate system in the Status section.

You will be notified of the status of the systems.
[sc_Isolating_system_03_Isolation_completed, 1, en_US]
Figure 4-16 Isolated State
Both systems are isolated and operate independently. All the applications and DIPs on the left-hand system
(standby system) are stopped.
² In SICAM PAS UI – Configuration, modify the configuration of the left-hand system (standby system)
according to your preferences.
The configuration change is notified by .
[sc_Isolating_system_04_Project_configuration_changed, 1, en_US]
Figure 4-17 Configuration Change Indicated on the Left-Hand System (Standby System)
² Press F5 in SICAM PAS UI – Operation Client.

The browser window refreshes and displays the changes you have performed.

E50417-H8976-C441-B9, Edition 11.2019
[sc_Isolating_system_05_104_Slave_added, 1, en_US]
Figure 4-18 Changed Configuration (IEC 60870-5-104 Slave Added)
² Click Update system on the left-hand system.
[sc_Isolating_system_07_System_updated, 1, en_US]
Figure 4-19 Configuration of Left-Hand System Updated
Now the changed configuration can be tested. Depending on the test results, proceed as follows:
² To restore the existing configuration of the right-hand system, click Retrieve configuration on the left-
hand system.
- or -
² To import the changed configuration of left-hand system into the right-hand system, retrieve the config-
uration on the right-hand system.
You minimize the interruption time for the subsequent system update by stopping the connections on
the right-hand system and starting the connections on the left-hand system. In this case the left-hand
system takes control.
To keep the control on the left-hand system during the subsequent steps, set the Switching preferred
system to (None) on both systems.

E50417-H8976-C441-B9, Edition 11.2019
[sc_Isolating_system_08c_before_Retreive_configuration, 1, en_US]
Figure 4-20 Connections on Left-Hand System Activated, No Preferred System
² Click Retrieve configuration on the right-hand side.
[sc_Isolating_system_10_after_Retrieve_configuration, 1, en_US]
Figure 4-21 After Retrieve Configuration
² Click Retry.

E50417-H8976-C441-B9, Edition 11.2019
[sc_Isolating_system_11_Configuration_retrieved_F5, 1, en_US]
Figure 4-22 Configuration Retrieved
NOTE
i Reconnect systems is only enabled if the configurations of the redundant systems are identical.
² Click Reconnect systems.
[sc_Isolating_system_13_Systems_reconnected, 1, en_US]
Figure 4-23 Systems Reconnected
Both system are redundant. The left-hand system is the process-controling system and the right-hand system
is the standby system.
² Click .
The system on which you started isolating systems is displayed.

E50417-H8976-C441-B9, Edition 11.2019
[sc_Isolating_system_15_end, 1, en_US]
Figure 4-24 Redundant System with Control Center Connection
Dearchiving a Project Database

² You can dearchive a project in a system with a redundant configuration.
NOTE
i If you dearchive a project in a redundant configuration, the project is dearchived in both the systems. If the
systems are isolated, the project is dearchived in the system on which Dearchive is clicked.
While dearchiving a project in a redundant configuration, Reconnect systems should not be clicked.
For more information, refer to /4/ SICAM PAS/PQS, Configuration and Operation/9/ SICAM PAS, Redundancy.

E50417-H8976-C441-B9, Edition 11.2019
5 Sample Configurations
Overview
Based on examples, this chapter illustrates how to set up redundant systems and redundant devices.
5.1 Overview 72
5.2 TCP/IP-Based Devices 74
5.3 Devices with Serial Communication 77
5.4 Control Centers with TCP/IP-Based Communication 80
5.5 Control Centers with Serial Communication 82

E50417-H8976-C441-B9, Edition 11.2019
Sample Configurations
5.1 Overview
5.1 Overview
This chapter presents some examples of redundant configurations. The following tables indicate where you
can find the description for the corresponding requirements:
• Redundant systems
You set up a configuration with 2 redundant SICAM PAS systems.
• Redundant devices
The system to be configured has redundant devices.
• Redundant interfaces (for communication with the control center)

You use redundant interfaces for communication between the control center and the SICAM PAS system.
Devices with TCP/IP-Based Communication

For more information, refer to 5.2 TCP/IP-Based Devices.
Redundant Redundant Redundant Description
systems interfaces devices
For more information, refer to 5.2.1 Devices with
X – –
TCP/IP-Based Communication.
For more information, refer to 5.2.2 TCP/IP-Based
X X –
Devices, Redundant System, Redundant Interfaces.
For more information, refer to 5.2.3 Redundant
X – X
TCP/IP-Based Devices, Redundant System.
Devices with Serial Communication

For more information, refer to 5.3 Devices with Serial Communication.
Redundant Redundant Redundant Description
systems interfaces devices
For more information, refer to 5.3.1 Serial Devices,
X – –
Redundant Systems.
For moreinformation, refer to 5.3.2 Serial Multi-
X X –
Channel Devices, Redundant Systems.
For more information, refer to 5.3.3 Redundant Serial
X – X
Single-Channel Devices, Redundant System.
For more information, refer to 5.3.4 Redundant
X X X
Serial Multi-Channel Devices, Redundant System.
Control Centers with TCP/IP-Based Communication

For more information, refer to 5.4 Control Centers with TCP/IP-Based Communication.
Redundant Redundant Description
systems interfaces
For more information, refer to 5.4.1 Control Center via TCP/IP, Redun-
– X
dant Interfaces.
For more information, refer to 5.4.2 Control Center via TCP/IP, Redun-
X X
dant Systems.
Control Centers with Serial Communication

For more information refer to 5.5 Control Centers with Serial Communication.

E50417-H8976-C441-B9, Edition 11.2019
5.1 Overview
Redundant Redundant Description

systems interfaces
For more information refer to 5.5.1 Serial Communication with Redun-
X –
dant System.
For more information refer to 5.5.2 Serial Communication with Redun-
– X
dant Interface.
For more information refer to 5.5.3 Serial Single-Channel Communica-
tion with Redundant System.
X –
In this configuration, both SICAM PAS systems are connected to the
control center via a splitter.
For more information refer to 5.5.4 Redundant Serial Communication
X X
with Redundant System.

E50417-H8976-C441-B9, Edition 11.2019
5.2 TCP/IP-Based Devices

The following paragraphs describe how to set up redundant configurations with TCP/IP-based devices:
• 5.2.1 Devices with TCP/IP-Based Communication
• 5.2.2 TCP/IP-Based Devices, Redundant System, Redundant Interfaces
• 5.2.3 Redundant TCP/IP-Based Devices, Redundant System
5.2.1 Devices with TCP/IP-Based Communication
System Configuration
[dw_Example_61850_system_redundancy, 2, en_US]
Figure 5-1 Devices with TCP/IP-Based Communication
This configuration consists of the following components:
• 2 SICAM PAS systems
• TCP/IP-based devices
• 1 network via which both SICAM PAS systems are connected to the devices
Redundancy-Specific Settings
• System redundancy: activated
• Interface redundancy: deactivated
• Dependency: independent mode activated
5.2.2 TCP/IP-Based Devices, Redundant System, Redundant Interfaces
[dw_Example_61850_system_interface_redundancy, 2, en_US]

E50417-H8976-C441-B9, Edition 11.2019
• TCP/IP-based devices
• 2 separate networks, both SICAM PAS systems are connected with both networks
• Interface redundancy: activated

For the IEC 60870-5-104 protocol, we recommend the use of the dependent mode. This ensures that the
first redundant Master has an up-to-date process image.
NOTE
i This configuration is not supported by the IEC 61850 SCD import. Instead, use the system redundancy only
in connection with the PRP network redundancy.
5.2.3 Redundant TCP/IP-Based Devices, Redundant System
[dw_Example_61850_system_and_device_redundancy, 2, en_US]
Figure 5-2 Redundant TCP/IP-Based Devices, Redundant System
• Redundant TCP/IP-based devices
• 2 separate networks, both SICAM PAS systems are connected with both networks

For the IEC 60870-5-104 protocol, we recommend the use of the dependent mode. This ensures that the
first redundant Master has an up-to-date process image.

E50417-H8976-C441-B9, Edition 11.2019
SICMA PAS Systems in the Substation

This configuration is suitable for setting up a redundant communication with SICAM PAS systems in the
substation.
[dw_Example_61850_system_and_device_redundancy_redundant_PAS, 2, en_US]
Figure 5-3 Configuration with Redundant SICAM PAS systems in the Substation
NOTE
i Communication with the SICAM PAS systems in the substation can be realized via the IEC 60870-5-104
protocol.

E50417-H8976-C441-B9, Edition 11.2019
5.3 Devices with Serial Communication

The following paragraphs describe how to set up redundant configurations with serial devices:
• 5.3.1 Serial Devices, Redundant Systems
• 5.3.2 Serial Multi-Channel Devices, Redundant Systems
• 5.3.3 Redundant Serial Single-Channel Devices, Redundant System
• 5.3.4 Redundant Serial Multi-Channel Devices, Redundant System
5.3.1 Serial Devices, Redundant Systems
[dw_Example_serial_1-channel_system_redundancy, 2, en_US]
Figure 5-4 Serial Devices, Redundant Systems
• Serial devices
The devices are connected with both systems via a splitter.
• Dependency: dependent mode activated

E50417-H8976-C441-B9, Edition 11.2019
5.3.2 Serial Multi-Channel Devices, Redundant Systems
[dw_Example_serial_x-channel_system_redundancy, 2, en_US]
Figure 5-5 Serial Multi-Channel Devices, Redundant Systems
• Serial multi-channel devices
5.3.3 Redundant Serial Single-Channel Devices, Redundant System
[dw_Example_serial_1-channel_system_device_redundancy, 2, en_US]
Figure 5-6 Redundant Serial Devices, Redundant System

E50417-H8976-C441-B9, Edition 11.2019
• Redundant serial single-channel devices

The SICAM PAS systems are connected via 2 connections with 2 splitters each.
5.3.4 Redundant Serial Multi-Channel Devices, Redundant System
[dw_Example_serial_multichannel_system_device_redundancy, 2, en_US]
Figure 5-7 Redundant Serial Multi-Channel Devices, Redundant System
• Redundant serial multi-channel devices

E50417-H8976-C441-B9, Edition 11.2019
5.4 Control Centers with TCP/IP-Based Communication

The following paragraphs describe how to set up redundant configurations with TCP/IP-based control centers:
• 5.4.1 Control Center via TCP/IP, Redundant Interfaces
• 5.4.2 Control Center via TCP/IP, Redundant Systems
5.4.1 Control Center via TCP/IP, Redundant Interfaces
[dw_Example_CC_TCPIP_interface_redundancy, 2, en_US]
• 1 SICAM PAS system
• 1 control center
The control center is connected with the SICAM PAS system via 2 networks.
• System redundancy: deactivated
5.4.2 Control Center via TCP/IP, Redundant Systems
[dw_Example_CC_TCPIP_system_redundancy, 2, en_US]
Figure 5-8 Control Center via TCP/IP, Redundant Systems

E50417-H8976-C441-B9, Edition 11.2019
The control center is connected to both SICAM PAS systems via 2 networks. The network can be used for
communication among the SICAM PAS systems.
For more information, refer to 3.1 Network Configuration for Redundant Systems.

E50417-H8976-C441-B9, Edition 11.2019
5.5 Control Centers with Serial Communication

The following paragraphs describe how to set up redundant configurations with serial control centers:
• 5.5.1 Serial Communication with Redundant System
• 5.5.2 Serial Communication with Redundant Interface
• 5.5.3 Serial Single-Channel Communication with Redundant System
• 5.5.4 Redundant Serial Communication with Redundant System
5.5.1 Serial Communication with Redundant System
[dw_Example_CC_serial_system_redundancy, 2, en_US]
Figure 5-9 Serial Communication with Redundant System
The control center is connected with both SICAM PAS systems via a serial cable.
5.5.2 Serial Communication with Redundant Interface
[dw_Example_CC_seriell_interface_redundancy, 2, en_US]
Figure 5-10 Serial Communication with Redundant Interface

E50417-H8976-C441-B9, Edition 11.2019
• 1 SICAM PAS system
The control center is connected with the SICAM PAS system via 2 serial cables.
• System redundancy: deactivated
NOTE
i You can also define redundant communication between the control center and the SICAM PAS systems via
dual channel redundancy. For the control center, dual channel redundancy can be set up with the IEC
60870-5-101 and DNP3 protocols. In this case, interface redundancy is not available.
5.5.3 Serial Single-Channel Communication with Redundant System
[dw_Example_CC_seriell_system_redundancy_dependent, 2, en_US]
Figure 5-11 Serial Single-Channel Communication with Redundant System
The control center is connected with both SICAM PAS systems via a splitter.

E50417-H8976-C441-B9, Edition 11.2019
5.5.4 Redundant Serial Communication with Redundant System
[dw_Example_CC_serial_system_interface_redundancy, 2, en_US]
Figure 5-12 Redundant Serial Communication with Redundant System
The control center is connected to the SICAM PAS systems via 2 serial cables each.
NOTE
i You can also define redundant communication between the control center and the SICAM PAS systems via
dual channel redundancy. For the control center, dual channel redundancy can be set up with the IEC
60870-5-101 and DNP3 protocols. In this case, interface redundancy is not available.

E50417-H8976-C441-B9, Edition 11.2019
6 PRP Network Redundancy
Overview
This chapter provides you with an overview of the PRP standard and the used components. It also supports you
in the setup of a PRP system with SICAM components.
6.1 What is PRP 86
6.2 PRP System Structure 87
6.3 Terms Used in the Context of PRP 88
6.4 PRP Components 90
6.5 Procedure for Setting up a PRP System 94
6.6 Sample Configuration 95
6.7 Diagnosis 96
6.8 Frequently Occurring Problems and Troubleshooting 101

E50417-H8976-C441-B9, Edition 11.2019
PRP Network Redundancy
6.1 What is PRP
6.1 What is PRP

The Parallel Redundancy Protocol (PRP) is a redundancy protocol for Ethernet networks. It is standardized in
accordance with IEC 62439-32 (Industrial Communication Networks / High Availability Automation Networks,
Part 3) and overcomes the failure of a network component without interruption (shock-free), redundancy
switchover, and reconfiguration time.
PRP achieves redundancy with 2 physically independent networks (LAN A and LAN B). The redundant nodes in
the PRP network are connected to both networks via 2 integrated Ethernet ports. Both Ethernet ports have the
same MAC address and are contacted via the same IP address. PRP is thus a Layer-2 redundancy procedure.
Higher-level protocols, including TCP/IP and also network management protocols, can be operated via PRP in a
transparent manner without change.
A PRP device simultaneously sends its data packets with additional PRP control information in parallel via both
ports into the LAN A and LAN B networks. If no errors have occurred, both data packets are transmitted via the
separate networks and received (time-delayed) in the destination device on both ports. Via PRP duplicate filter
mechanisms, the first data packet arriving is forwarded to higher protocol layers. The second data packet,
which is principally identical apart from the PRP data, is discarded (duplicate discard). This ensures that a data
packet is received even if one of the 2 PRP networks is disturbed.
This procedure provides redundancy without switchover time. Thanks to the additional PRP information (for
example, Supervision Frame) in the data packets, the redundancy status of the PRP nodes in the network can
be continuously determined.
Via a RedBox (redundancy box), devices which do not support PRP can be redundantly connected to the PRP
network.
To this end, the RedBox is equipped with 2 ports for the connection to LAN A and LAN B and at least one port
for the connection of devices (VDANs) which, via the RedBox, communicate redundantly in the same way as
other PRP devices (DANs).
Non-PRP devices can also be connected to one single PRP network (LAN A or LAN B). In this case, however,
they can only communicate non-redundantly with devices in this network.
Advantages of PRP when compared to other media-redundancy protocols:
• No redundancy switchover required, uninterruptible, no loss of data packets
• The redundancy procedure is transparent for higher-level protocols, for example, no PRP-specific parame-
terization for SICAM PAS required.
• Periodic redundancy supervision via supervision frames possible

Disadvantages of PRP when compared to other media-redundancy protocols:
• The network hardware must be available twice; double network costs; however, no special PRP network
components are required (only oversized frames must be supported)
• PRP hardware/software for the nodes required
2 The IEC 62439-3 is currently under development and scheduled to be adopted in 2012.

E50417-H8976-C441-B9, Edition 11.2019
6.2 PRP System Structure
6.2 PRP System Structure

The following figure provides a simplified representation of a PRP system structure with 2 LAN A and LAN B
networks, the redundantly connected devices (as DAN or VDAN via a RedBox) and the devices connected non-
redundantly to one single network (SAN).
PRP Network with PRP Components
[dw_PRP_with_components, 2, en_US]
Figure 6-1 PRP System Structure with PRP Components
For explanations on the components and terms used for PRP, refer to 6.3 Terms Used in the Context of PRP.

E50417-H8976-C441-B9, Edition 11.2019
6.3 Terms Used in the Context of PRP

PRP-1 - Parallel Redundancy Protocol Version 1
For the presented environment (SICAM PAS with PRP software, SIPROTEC 4 or SIPROTEC 5 device with PRP
communication and RedBox), only Version 1 of the PRP standard is supported. In this document, the term PRP
always refers to Version PRP-1.
Node
In the PRP context, the term node always refers to a node connected to a PRP network. A node can be a DAN,
VDAN, or SAN.
Node Table
Table within a node with entries for each node in the PRP network with which information is exchanged. The
purpose of this table is to support the Duplicate discard algorithm. In addition, this table is used for moni-
toring the PRP network by indicating the nodes with their corresponding type (DAN or SAN) and state infor-
mation (for example, error status, number of packets sent and received, and number of packets received in
the wrong network). The Supervision Frame is also used, for example, in order to set up the Node Table.
The Node Table (referred to as Station table in SIMATIC NET SOFTNET-IE RNA) can be displayed and exported
for further analysis on the diagnostic user interface of the SIMATIC NET SOFTNET-IE RNA PRP PRP software.
LAN A / LAN B
The 2 redundant networks of a PRP network are referred to as LAN A and LAN B. The same MAC addresses and
the same IP addresses for each DAN exist in these networks. The 2 networks are independent of each other
(due to redundancy, for example, an independent power supply of the network components is also required)
and not directly connected to each other. Regarding performance and topology, the structure of the networks
should also be almost identical in order to avoid runtime differences (relief of the duplicate filter).
DAN - Double Attached Node

A redundantly connected PRP node which is redundantly linked to LAN A and LAN B via 2 integrated Ethernet
ports.
In order to operate a SIPROTEC 4 device as a DAN, an EN100 module, firmware version V4.10 or higher and
configured for PRP, is required.
For SIPROTEC 5 an electrical (ETH-BA-2EL) or optical (ETH-BB-2FO) Ethernet module, firmware V3 or higher, is
required.
By means of 2 suitable network cards and the SIMATIC NET SOFTNET-IE RNA, an industrial PC can be trans-
ferred into a DAN.
SAN - Single Attached Node

A SAN is a non-redundant node in the PRP network. It is only connected to one port to one network (LAN A or
LAN B). It can only communicate with nodes in the connected network.
Via a RedBox, devices with only one connection can be redundantly connected to the 2 LAN A and LAN B
networks.
In order to obtain symmetrical LAN A and LAN B networks, it is recommended to avoid SANs and to connect
the devices either via a RedBox or in a separate network without PRP support.
RedBox - Redundancy Box

The RedBox is used for the redundant connection of devices with only one interface to both the LAN A and
the LAN B PRP network. The RedBox is a DAN and operates as a proxy for the devices connected to it
(VDANs). The RedBox has its own IP address in order to be able to configure, manage, and monitor it.
The Redbox SIMATIC NET SCALANCE X204RNA EEC from Siemens can be used.

E50417-H8976-C441-B9, Edition 11.2019
VDAN - Virtual DAN

A node with only one interface which is redundantly connected to the 2 LAN A and LAN B networks via a Red-
Box. This ensures that all connected nodes can communicate with all nodes in the PRP network. Towards
other nodes, this node behaves like a DAN and is therefore referred to as Virtual DAN (VDAN).
Supervision Frame
Each DAN periodically sends a supervision frame for monitoring the integrity of the PRP network and
checking the presence of the individual nodes.
SIMATIC NET SOFTNET-IE RNA - SIMATIC NET SOFTNET Industrial Ethernet Redundant Network Access
This is the recommended PRP software which is used in order to transform a PC or a Station Unit with suitable
network cards into a DAN that communicates redundantly, for example, with SICAM PAS V7.00 or higher via
the PRP network.
Duplicate Discard
A duplicate filter for the 2 frames sent twice. Duplicate discard ensures that the double frames are filtered
out in the Link layer by means of the PRP information in the frame in order to relieve the higher protocol layers
and provide for improved redundancy monitoring. This procedure is compulsory in accordance with IEC
62439-3 standard. It is used for the SIPROTEC 4 devices, SIPROTEC 5 devices, and the RedBox SIMATIC NET
SCALANCE X204RNA EEC and corresponds to the default setting for the PRP software SIMATIC NET SOFTNET-IE
RNA.
Duplicate Accept
Duplicate accept ensures that the 2 frames received on the ports for LAN A and LAN B are forwarded to
higher protocol levels without filtering. It is assumed that the protocols and applications handle the double
frames correctly (for example, TCP) and automatically discard the second frame. This, however, increases the
system load for further processing. This method is not standard conform and is not supported.

E50417-H8976-C441-B9, Edition 11.2019
6.4 PRP Components
6.4 PRP Components

In terms of SICAM PAS, the following components are required in order to set up a PRP system, see Figure 6-1.
• PRP software (here: SIMATIC SOFTNET-IE RNA)
• PRP-capable network cards
• PRP-capable switch
• SIPROTEC 4 protection devices with PRP-capable communication module or SIPROTEC 5 protection

devices with PRP-capable EN100 communication module
• PRP-capable devices from third-party manufacturers
• RedBox (for example, SIMATIC NET SCALANCE X204RNA EEC)

Installation and commissioning in the recommended order are described in the following sections.
6.4.1 PRP-Capable Switch (Oversized Frames)
A PRP network can be set up with standard network components (switches and network cards).
Since PRP Ethernet frames contain additional information for PRP (for example, RCT = Redundancy Control
Trailer), these frames can reach a size of up to 1536 bytes. Thus, the frames can exceed the length defined for
an Ethernet frame according to IEEE802.3 standard.
Many network components can process these oversized frames. However, this is not standard conform, and
it cannot be assumed that all network components support oversized frames and behave correctly.
For this reason, PRP-certified switches which accept oversized Ethernet frames (of up to 1536 bytes) must be
used for PRP networks.
If oversized frames are not supported by the switch, the packets are ignored or deleted and thus not
forwarded.
6.4.2 PRP-Capable Network Card (Oversized Frames and Software Support)
The network cards used must also support oversized frames as otherwise this data is not forwarded via the
network card.
In addition, SOFTNET-IE RNA must support the used network cards. For proper operation of SIMATIC NET
SOFTNET-IE RNA, for example, the Siemens SIMATIC NET CP 1612 A2 and INTEL PRO/1000 PT network cards
are recommended. For a list of recommended network cards, refer to the operating instruction.
For each PRP network, 2 supported network cards for LAN A and LAN B are required (or one network card with
2 connections). In order to obtain a symmetric structure (for example, to relieve the duplicate filter) and to
obtain an identical parameterization, both network cards used should be identical.
The network interface cards that can be ordered for SICAM Station Unit V2.30 or higher have been successfully
tested for use with PRP (SIMATIC NET SOFTNET-IE RNA V8.2) and SICAM PAS PQS.
6.4.3 PRP Software (SIMATIC NET SOFTNET-IE RNA)
The PRP protocol for SICAM PAS and SICAM SCC is only released with SIMATIC NET SOFNET-IE RNA PRP (order
number: 6GK1711-1EW08-1AA0 or 6GK1711-1EW08-2AA0).).
For more information, for example, concerning prerequisites and installation, refer to the operating instruc-
tions of SIMATIC NET SOFTNET-IE RNA.
The operating instructions (of the software: Operating instructions SIMATIC NET, PG/PC - Industrial Ethernet,
SOFTNET-IE RNA V8.1) and more information on the SIMATIC NET SOFTNET-IE RNA software are available on
the product support Internet sites of Siemens Industry Automation and Drive Technologies:
http://support.automation.siemens.com/WW/view/en/48805093/130000
The following section provides a short description of the steps to be followed until commissioning.

E50417-H8976-C441-B9, Edition 11.2019
6.4 PRP Components
System prerequisites
The following SICAM versions have been released for operation with PRP:
• SICAM PAS/PQS V7.00 SP3 (HF2 for SNMP 64 bits) or higher
• SICAM PAS CC V7.00 or higher
• SICAM PQ Analyzer V2.00 or higher

For more information on supported network cards, refer to 6.4.2 PRP-Capable Network Card (Oversized
Frames and Software Support).
Installation and commissioning
• Integration of the network card(s)

One network card with 2 interfaces or 2 identical network cards (one interface per PRP network)
• Install and configure the driver and network cards according to the manufacturers’ instructions.
• Preparing the configuration for PRP

Name the links to the network cards in such a way that they can be assigned conveniently during the
subsequent PRP installation and configuration.
For example, the link to the network card to which LAN A is connected could be named PRP LAN A link. If
a computer is connected to several PRP networks, assign numbers to the individual PRP networks, for
example, PRP 1 LAN A link.
• Testing the 2 LAN A and LAN B networks

Setup of the 2 LAN A and LAN B PRP networks. The PRP nodes are already configured accordingly. For test
purposes, the PRP nodes are connected to the LAN A or LAN B network and thus to the corresponding
network card in the PRP computer. The networks are tested separately: Availability and proper func-
tioning of the nodes.
• Perform the installation according to Operating instructions SIMATIC NET, PG/PC - Industrial Ethernet,
SOFTNET-IE RNA V8.1
6.4.4 SIPROTEC Devices
SIPROTEC 4 and SIPROTEC 5 devices support PRP. For SIPROTEC 4 protection devices a PRP-capable EN100
Ethernet module is necessary, for SIPROTEC 5 protection devices a PRP-capable Ethernet module is necessary.
The differing configuration is shortly described below.
6.4.4.1 SIPROTEC 4 with PRP EN100 Module

With a Firmware version 4.20 or higher of the EN100 Ethernet module, SIPROTEC 4 devices equipped with a
communication module support communication via the PRP protocol. PRP can be used in the optical Ethernet
module EN100-O(LC) as well as EN100-O+ and EN100-E+.
For more information on installation and commissioning, refer to Readme for IEC 61850 Ethernet module
(EN100) firmware versions /28/.
The PRP support of the EN100 module requires a FPGA Version 515 or higher. The update is also described in
the mentioned readme document.
Be aware that all SIPROTEC 4 devices required for PRP must be upgraded to the PRP supporting Firmware
Version V4.20 (or higher) before their integration in the PRP network.
System prerequisites
In order to be able to take part in the PRP communication as a DAN, a SIPROTEC 4 device must be equipped
with an EN100 communication module.
To enable PRP communication, Firmware version 4.20 (or higher) and the appropriate FPGA update must be
loaded onto the module, refer to Readme for IEC 61850 Ethernet module (EN100) firmware versions /28/.

E50417-H8976-C441-B9, Edition 11.2019
6.4 PRP Components
Configuration
In DIGSI, PRP is configured via the EN100 module settings. If the parameter set of the device does not yet
support this parameter, you can select PRP via configuration with RSTP. To do so, set the Cost Style parameter
to -1 and Hello Time parameter to 1. The other parameters are irrelevant for the settings of this operation
mode. However, a Firmware version 4.20 or higher is required for the EN100 module.
In a newer version of DIGSI these values will be harmonized, refer to SIPROTEC 4, Ethernet Module EN100 for
IEC 61850 with electrical/optical 100 MBit Interface, manual EN100 EN (C53000-G1140-C167-13).
6.4.4.2 SIPROTEC 5 with Ethernet Module

SIPROTEC 5 devices with electrical (ETH-BA-2EL) or optical (ETH-BB-2FO) Ethernet modules with a Firmware
version V3 or higher support communication via PRP protocol.
System Requirements
To be able to participate as DAN on a PRP communication, a SIPROTEC 5 device hast o be equipped with an
electrical (ETH-BA-2EL) or optical (ETH-BB-2FO) Ethernet module with Firmware version V3 or higher.
Configuration
In DIGSI, PRP is configured via the Ethernet module settings.
[sc_DIGSI5_PRP_Settings, 1, en_US]
Figure 6-2 Selecting PRP as network-redundancy protocol
In the protocol settings of the module, the network-redundancy protocol must be set to PRP.
Further settings are not necessary for PRP operation.
For diagnosis it is recommended to additionally select the network protocols SNMP and Homepage
6.4.5 Redundancy Box (RedBox) / SIMATIC NET SCALANCE X204RNA EEC
For PRP, RedBoxes are available from different manufacturers. Siemens recommends using the SIMATIC NET
SCALANCE X204RNA EEC RedBox (order number: 6GK5204-0BS00-3LA3).
The following descriptions refer to the SIMATIC NET SCALANCE X204RNA EEC RedBox.
The operating instructions and more information on the SIMATIC NET SCALANCE X204RNA RedBox are avail-
able on the product support Internet sites of Siemens Industry Automation and Drive Technologies:
http://support.automation.siemens.com/WW/view/en/52323714/130000

E50417-H8976-C441-B9, Edition 11.2019
6.4 PRP Components
Configuration and Commissioning

The configuration of the RedBox and commissioning are described in detail in the operating instructions, refer
to Operating instructions of the RedBox SIMATIC NET Industrial Ethernet Switches SCALANCE X204RNA/
X204RNA EEC).
The configuration of the RedBox is not compulsory for mere PRP operation. However, in order to be able to
contact the RedBox via the network, for example, for configuration and diagnostic purposes, it must be
possible to address the RedBox specifically via an IP address in the corresponding subnetwork.
Configure the RedBox before integrating it into your system. In this case, you can simply perform the configu-
ration via an Ethernet direct link from the PC to the RedBox.

E50417-H8976-C441-B9, Edition 11.2019
6.5 Procedure for Setting up a PRP System
6.5 Procedure for Setting up a PRP System
6.5.1 Recommendations
• Symmetric networks
Make sure you set up and assign the 2 LAN A and LAN B PRP networks consistently (clear arrangement,
avoiding runtime differences which would have an impact on the duplicate filter). This applies to the
network topology and the switches used; confgure them identically in LAN A and LAN B. A unique identi-
fication of the 2 LAN A and LAN B PRP networks is recommended, for example, cables in different colors.
• Single Attached Nodes (SANs) must be avoided

Since SANs represent a one-sided burden on the network and thus make it asymmetric (see above), they
should be avoided if possible. In order to use several devices which do not support PRP, check whether it
is possible to set up a specific non-PRP network for these network nodes.
• Quantity framework
In order to prevent a network overload, Siemens recommends working with subnetworks with a
maximum of 180 devices per subnetwork.
6.5.2 Setup Order to Be Observed
Setting up a PRP System

Follow the step-by-step procedure for setting up a PRP system:
² Setup and create interconnections of the Ethernet switches.
² Configure the switches and check the settings. In particular, the oversized frames setting must be
observed in this context.
² Connect the PRP devices to one single network (LAN A) or deactivate LAN B.
² If necessary, update FPGA and EN100 module Firmware on the devices and adjust EN100 module param-
eters according to PRP.
² Test whether the devices have been correctly integrated in LAN A.
² Connect the PRP devices step by step to LAN B (or activate LAN B). During these actions, check after each
step if packages are received in the wrong network.
² Test the PRP functionality via the PRP settings, refer to 6.7 Diagnosis.
Incorporating the RedBoxes

To incorporate the RedBoxes, proceed in the same way as for the switches and normal PRP devices:
² Connect the RedBox to a PRP network (LAN A).
² Configure the RedBox and then the devices downstream of the RedBox.
² If the test for the availability of the devices was successful, connect the RedBox also to the second PRP
network.
Replacing PRP Devices

If PRP devices, for example, SIPROTEC 4 or 5 devices, must be replaced while the PRP system is running, make
sure that the PRP functionality has been activated before incorporation (for example, firmware updated) in
order to prevent an interconnection of the 2 LAN A and LAN B networks. Such an interconnection would result
in the consequences described above.

E50417-H8976-C441-B9, Edition 11.2019
6.6 Sample Configuration
6.6 Sample Configuration

The following simplified sample configuration is based on the recommendations, refer to 6.5.1 Recommenda-
tions.
[dw_prp_2_networks, 2, en_US]
Figure 6-3 Sample Configuration
The figure shows a computer with SICAM PAS which is connected to 2 PRP networks.
In order to use no more than 180 nodes per network, the PRP networks were distributed. The structure of the
networks is symmetric. SANs were avoided.
In this sample configuration, a temporary engineering computer is integrated in the PRP 2 LAN B network.
Non-PRP devices were redundantly connected via RedBoxes or linked as a separate non-PRP network.
In the sample configuration, 5 network cards are integrated in the computer, that is, 2 for each of the 2 PRP
networks and one for the non-redundant network.

E50417-H8976-C441-B9, Edition 11.2019
6.7 Diagnosis
6.7 Diagnosis
The components Ethernet module for SIPROTEC 5 and EN100 communication module for SIPROTEC 4,
SCALANCE X204 RNA RedBox and SIMATIC NET SOFTNET-IE RNA support the SNMP protocol.
The following section describes how to perform diagnosis via SNMP and how to use the protocol with SICAM
PAS device descriptions for monitoring.
In addition, the PRP software SIMATIC NET SOFTNET-IE RNA offers a diagnosis user interface for checking the
redundancy status, refer to Operating instructions SIMATIC NET, PG/PC - Industrial Ethernet, SOFTNET-IE RNA
V8.1.
6.7.1 SNMP / SICAM PAS Device Descriptions
SNMP (Simple Network Management Protocol) enables the monitoring of important PRP states via the
Ethernet network in order to detect errors.
The PRP standard defines (optional) SNMP objects described in a MIB (Management Information Base) file. The
SNMP MIB files of the Siemens PRP components are derived from this definition.
The SNMP MIB files, and also the device descriptions for SICAM PAS derived from them, are adapted to each
other.
For use with SICAM PAS, device descriptions were created from the MIB files. These device descriptions can be
imported into SICAM PAS UI – Configuration, Templates view, for use with the SNMP application.
In SICAM PAS, the SNMP values are requested and further processed via PAS telegrams. For this reason, only
SNMP values that can be mapped by the protocol information types available in SICAM PAS can be defined in
the PAS SNMP device descriptions. These are, for example, integer or counter values.
NOTE
i Strings (for example the manufacturer name) or MAC addresses cannot be requested with SICAM PAS via
SNMP.
In order to request all PRP-SNMP values, a separate MIB Browser is required.

E50417-H8976-C441-B9, Edition 11.2019
6.7 Diagnosis
[sc_PRP_SNMP, 1, en_US]
Figure 6-4 SNMP Values from the Device Description
The figure shows the PRP-SNMP values supported in SICAM PAS in the SICAM PAS UI – Configuration, Mapping
view (imported from the EN100_FW4_PRP.txt device description for EN100 modules).
The following values should be observed for PRP network monitoring:
Table 6-1 Important PRP SNMP Objects and their Significance
Value Significance Note

linkStatusA Status of the link to Network A/B Down (1) / up (2)
linkStatusB Both ports must be up
cntTotalSentA Number of frames sent via Network A/B These values must increase during
cntTotalSentB operation, but do not need to be
identical.
cntReceivedA Number of frames received via Interface These values must increase during
cntReceivedB A/B operation, but do not need to be
identical.

E50417-H8976-C441-B9, Edition 11.2019
6.7 Diagnosis
Value Significance Note

cntErrWrongLANA Number of frames received with the This value must be 0 during opera-
cntErrWrongLANB incorrect LAN identifier on Port A or B tion. Incorrectly connected nodes
can be identified with these values.
cntErrorsA Number of incorrectly received frames This counter must be 0 in fault-free
cntErrorsB on Interface A/B. operation.
The following SNMP MIB files and device descriptions are available for the PRP components required:
Table 6-2 SNMP Files and Device Descriptions
Component SNMP MIB File Device Template/Device Description File

SIPROTEC 4 EN100 IEC62439.mib Download from EN100_FW4_PRP.txt Installed with SICAM
communication module www.siprotec.de PAS V7.00 SP3 in the device description
folder: %PUBLICDOCUMENTS%Siemens
Energy\ SICAM PAS PQS\DeviceDescrip-
tions
SIPROTEC 5 Ethernet See SIPROTEC 4 See SIPROTEC 4
module
6.7.2 SIPROTEC 4 with PRP EN100 Module
6.7.2.1 SNMP / SICAM PAS Device Descriptions

For more information on SNMP and SICAM PAS device descriptions, refer to 6.7.1 SNMP / SICAM PAS Device
Descriptions.
6.7.2.2 EN100 Module PRP Homepage

The EN100 module makes available diagnostic pages via an incorporated web server call-up in the browser via
http://[IP address]/home).
The relevant PRP information can be requested via the HSR/PRP page (or directly via http://[IP address]/hsrprp).

E50417-H8976-C441-B9, Edition 11.2019
6.7 Diagnosis
[sc_EN100_PRP_Homepage, 1, en_US]
Figure 6-5 EN100 module PRP homepage
The following values are relevant for diagnostic purposes. Since the names on the diagnostic page differ from
the (SNMP) names defined in the standard, the corresponding name used in the standard is indicated in
brackets.
• LinkStatusChan1/2 (SNMP: linkStatusA/B) with the values UP or DOWN

• txPacketChan1/2 (SNMP: cntTotalSentA/B)
• rxPacketChan1/2 (SNMP: cntReceivedA/B)
• CorrectLanChan1/2 (SNMP: cntReceivedA/B)
• WrongLanChan1/2 (SNMP: cntErrWrongLANA)
The meanings of these values are described in Table 6-1.

In order to quickly realize how the values can change (whether e.g. packets are still transmitted in the wrong
PRP network), the values from the last 10 seconds are indicated additionally.
6.7.3 SIPROTEC 5 with Ethernet Module
6.7.3.1 SNMP / SICAM PAS Device Description

SIPROTEC 5 uses the same MIB as SIPROTEC 4, i.e. for SICAM PAS the same device descriptions can be used,
refer to 6.7.1 SNMP / SICAM PAS Device Descriptions.
6.7.3.2 Ethernet Module PRP Homepage

The Ethernet module makes available diagnostic pages via an incorporated Web server call-up in the browser
via http://[IP-Adresse]/home.
The relevant PRP information can be requested via Applications Diagnostic - PRP.

E50417-H8976-C441-B9, Edition 11.2019
6.7 Diagnosis
[sc_Ethernet_PRP_Homepage, 1, en_US]
Figure 6-6 Ethernet module PRP homepage
For the interpretation of these values, refer to the manual SIPROTEC 5 Communication Protocols, V7.30 and
higher (C53000-L1840-C055-2) or 6.7.2.2 EN100 Module PRP Homepage.

E50417-H8976-C441-B9, Edition 11.2019
6.8 Frequently Occurring Problems and Troubleshooting
6.8 Frequently Occurring Problems and Troubleshooting
Table 6-3 Problems and Troubleshooting
Fault Condition Potential Cause Troubleshooting

Packets in the wrong LAN are The connections to LAN A and LAN Check the device connections. The
detected during diagnosis (for B have been confused for at least incorrectly connected node may be
example, via the Web user inter- one node. located via the station table or
face, SNMP, Netview, or the station Netview.
table).
(SNMP: cntErrWrongLANA/B)
No communication via switch/ The switch or network card does Check and define the Oversized
network card possible not support Oversized Frames. Frames setting.
More packets are received via one Unequal distribution of the SANs in This state does not necessarily lead
LAN than via the other LAN the networks; asymmetrical to an error, but asymmetric
(SNMP: cntReceivedA/B) network networks should be avoided.
Faulty packets in the networks • A device sends faulty packets Stepwise localization of the source
of error by deactivating or
(SNMP: cntErrorsA/B) • Packets are falsified
replacing devices while monitoring
• Different PRP implementations the error values
or standards/procedures
No communication possible The 2 LAN A and LAN B PRP Check the switches, cables, and PRP
networks are connected. nodes. Only PRP nodes may be
connected to both networks (but,
for example, no SIPROTEC devices
with a non-PRP-capable EN100
module).
Different implementations of the Use only PRP components based on
PRP standard IEC 62439-3 PRP-1 standard.
Too many devices (nodes) in the Reduce number of devices in the
network network; divide number of devices
to additional network.

E50417-H8976-C441-B9, Edition 11.2019
E50417-H8976-C441-B9, Edition 11.2019
Literature
/1/ SICAM PAS, Overview

E50417-X8976-C431-C1
/2/ SICAM PQS, Overview
E50417-X8976-C464-C1
/3/ SICAM PAS/PQS, Installation
E50417-M8976-C432-C1
/4/ SICAM PAS/PQS, Configuration and Operation
E50417-P8976-C433-C2
/5/ SICAM SCC, Human Machine Interface SICAM SCC
E50417-H8976-C501-B3
/6/ SICAM Valpro, Measured/Metered Value Processing Utility SICAM Valpro
E50417-H8976-C479-A4
/7/ SICAM PAS, Automation Blocks
E50417-H8976-C436-B3
/8/ SICAM PAS/PQS, Security
E50417-H8976-C438-B5
/9/ SICAM PAS, Redundancy
E50417-H8976-C441-B9
/10/ SICAM PAS, Device Description
E50417-T8976-C437-A9
/11/ SICAM Station Unit V2.40
E50417-H8976-C381-A5
/12/ SICAM PQS, Fault Locator
E50417-H8976-C421-A9
/13/ SICAM PQ Analyzer
E50417-H8976-C397-C2
/14/ SICAM PQ Analyzer, Incident Explorer
E50417-H8976-C465-C2
/15/ SICAM PAS, CFE Test and Diagnosis
E50417-H8976-C425-A4
/16/ SIMEAS R PAR, Parameterization Tool
E50417-H1076-C439-B1
/17/ SIMEAS R, Manual Digital Fault and Power Quality Recorder
E50417-B1076-C209-A5
/18/ SIMEAS R-PMU, Manual Digital Fault Recorder
E50417-H1076-C360-A3
/19/ SIMEAS R-PMU, Maintenance Manual
E50417-H1074-C364-A2

E50417-H8976-C441-B9, Edition 11.2019
Literature
/20/ SICAM P850/P855 7KG85xx V2.60, Power Monitoring Device and Power Quality Recorder, Device Manual
E50417-C1040-C482-A7
/21/ SICAM Q100 7KG95xx V2.10, Power Monitoring Device and Class A Power Quality Recorder, Device Manual
E50417-H1040-C522-A6
/22/ SICAM Q200 7KG97 V2.40, Multifunctional Recorder, Device Manual
E50417-H1040-C606-A6
/23/ SIPROTEC 5 7KE85 V7.80 and later, Fault Recorder, Manual
C53000-G5040-C018-6
/24/ SICAM GridPass V1.30, Manual
E50417-H8940-C598-A4
/25/ SIMATIC HMI WinCC V7.5, WinCC Information System, System Manual
Printout of the online help, 09/2018, A5E46376856-AA

E50417-H8976-C441-B9, Edition 11.2019
Index
A E
Active mode 19 Examples
Archiving 42 Overview 72
Automation 50 Serial control centers 82
Serial devices 77
TCP/IP control centers 80
TCP/IP devices 74
B
Basic group
Description 23 F
Basic Group
switching over 25 Full redundancy 20
Bay blocking 50
Booting
redundant systems 50
H
HOSTS file 35
C
Communication modes 19
Configuration I
transferring 42
Control center Inactive mode 19
Examples (serial) 82 Independent mode 27
Examples (TCP/IP) 80 Interface
redundant communication 21 changing 58
Control centers Interface redundancy
switching over 25 setting up 38
Interface Redundancy
Description 19
Interfaces
D switching over 25
Isolating system
Dependency 27 Isolating system 66
Dependent mode 27 Reconnecting systems 69
Device Redundancy 20 Isolating systems 63
Devices Dearchiving a project 70
Examples (serial) 77 Runtime interruption 64
Examples (TCP/IP) 74
switching over 25
DIP
Redundancy 18 M
Mode
Dependency 27

E50417-H8976-C441-B9, Edition 11.2019
Index
Modes Description 18
Communication 19
T
N
Teaming adapter 32, 32
Network Telecontrol blocking 50
Changing the order 36
Configuration 32
HOSTS 35
Teaming adapter 32, 32 U
UI Operation
Redundancy 53
P UI Operation Client
Redundancy 61
Passive mode 19 Unarchiving 42
PQ Analyzer 45
Preference
System 55, 58
Prioritization 26
R
Redundancy
Changing the system 55
Impact on commands 52
operating 49
Operation 50
setting up 31
UI – Operation 53
UI Operation Client 61
Redundancy state 55
S
SoftPLC 46, 50
Standby mode 19
Switching authority 50
Switchover
Control centers 25
Devices 25
Interfaces 25
Overview 24
Prioritization 26
Response times 25
system 24
System
changing 55
switching over 24
System redundancy
during booting 50
setting up 41
System Redundancy

E50417-H8976-C441-B9, Edition 11.2019

Redundancy B

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Redundancy B

Uploaded by

Copyright:

Available Formats

Preface

Open Source Software

SICAM Redundancy Overview 1

Disclaimer of Liability Copyright

Purpose of the Manual

Customer Support Center

SICAM, SICAM PAS, Redundancy 3

Qualified Electrical Engineering Personnel

• Proper storage, setup and installation

• Proper operation and maintenance

4 SICAM, SICAM PAS, Redundancy

SICAM, SICAM PAS, Redundancy 5

SICAM, SICAM PAS, Redundancy 7

Open Source Software..................................................................................................................................7

2 Redundancy in SICAM PAS..........................................................................................................................15

SICAM, SICAM PAS, Redundancy 9

3.4.2 SICAM PQ Analyzer...................................................................................................... 45

6 PRP Network Redundancy.......................................................................................................................... 85

10 SICAM, SICAM PAS, Redundancy

6.5.2 Setup Order to Be Observed.........................................................................................94

SICAM, SICAM PAS, Redundancy 11

• 2 identically configured SICAM PAS systems

• Redundantly set up devices

Understanding Redundancy in SICAM PAS

Figure 1-1 System Redundancy

SICAM, SICAM PAS, Redundancy 13

Figure 1-2 Interface Redundancy

[dw_Device redundancy, 2, en_US]

Figure 1-3 Device Redundancy

Examples of Redundant Configurations

14 SICAM, SICAM PAS, Redundancy

SICAM, SICAM PAS, Redundancy 15

2.1 Redundancy in SICAM PAS

• 2 functionally identical SICAM PAS systems (Full Server and DIPs)

• Functionally identical devices

• SICAM PAS system

• Process controlling system / standby system

16 SICAM, SICAM PAS, Redundancy

Table 2-1 Symbols Used

Network between SICAM PAS computers

SICAM, SICAM PAS, Redundancy 17

2.2 Redundancy Types

• Full redundancy (including both system redundancy and interface redundancy)

2.2.1 System Redundancy

Figure 2-1 System Redundancy

Operating Modes of Redundant Systems

18 SICAM, SICAM PAS, Redundancy

2.2.2 Interface Redundancy

Figure 2-3 Interface Redundancy

Operating Modes of Redundant Interfaces

Table 2-2 Protocols with Standby Mode and Passive Mode

Protocol Standby mode Passive mode

i PROFINET IO Master does not support Interface redundancy.

SICAM, SICAM PAS, Redundancy 19

2.2.3 Device Redundancy

[dw_Device redundancy, 2, en_US]

Figure 2-4 Device Redundancy

2.2.4 Full Redundancy (Both System Redundancy and Interface Redundancy)

20 SICAM, SICAM PAS, Redundancy

2.2.5 Redundant Communication with a Control Center

Redundant Communication in the Case of System Redundancy

SICAM, SICAM PAS, Redundancy 21

Redundant Communication in the Case of Interface Redundancy