Application Example  10/2016

Setting Up a Mesh Network

Based on “RSTP”
SCALANCE X

https://support.industry.siemens.com/cs/ww/en/view/109742120
 Warranty and Liability

Warranty and Liability

Note The Application Examples are not binding and do not claim to be complete regarding the
circuits shown, equipping and any eventuality. The Application Examples do not represent
customer-specific solutions. They are only intended to provide support for typical
applications. You are responsible for ensuring that the described products are used
correctly. These Application Examples do not relieve you of the responsibility to use safe
practices in application, installation, operation and maintenance. When using these
Application Examples, you recognize that we cannot be made liable for any
damage/claims beyond the liability clause described. We reserve the right to make
changes to these Application Examples at any time without prior notice. If there are any
deviations between the recommendations provided in these Application Examples and
other Siemens publications – e.g. Catalogs – the contents of the other documents have
priority.
We do not accept any liability for the information contained in this document.
Any claims against us – based on whatever legal reason – resulting from the use of
the examples, information, programs, engineering and performance data etc.,
described in this Application Example shall be excluded. Such an exclusion shall
not apply in the case of mandatory liability, e.g. under the German Product Liability
Act (“Produkthaftungsgesetz”), in case of intent, gross negligence, or injury of life,
body or health, guarantee for the quality of a product, fraudulent concealment of a
deficiency or breach of fundamental contractual obligations (“wesentliche
Vertragspflichten”). The damages for a breach of a substantial contractual
obligation are, however, limited to the foreseeable damage, typical for the type of
 Siemens AG 2016 All rights reserved

contract, except in the event of intent or gross negligence or injury to life, body or
health. The above provisions do not imply a change of the burden of proof to your
detriment.
Any form of duplication or distribution of these Application Examples or excerpts
hereof is prohibited without the expressed consent of Siemens AG.

Security Siemens provides products and solutions with industrial security functions that support the
informa- secure operation of plants, systems, machines and networks.
tion To protect plants, systems, machines and networks against cyber threats, it is necessary
to implement (and continuously maintain) a holistic, state-of-the-art industrial security
concept. Products and solutions from Siemens are only one part of such a concept.
The customer is responsible for preventing unauthorized access to the customer’s plants,
systems, machines and networks. Systems, machines and components should be
connected to the company network or the Internet only if and to the extent necessary and
if appropriate protective action (e.g., use of firewalls and network segmentation) was
taken.
In addition, Siemens’ recommendations regarding appropriate protective action should be
followed. For more information about industrial security, visit
http://www.siemens.com/industrialsecurity.
Siemens’ products and solutions undergo continuous development to make them even
more secure. Siemens strongly recommends to perform updates as they become
available and use only the latest product versions. Using versions that are out of date or
no longer supported can increase the risk of cyber threats.
To stay informed about product updates as they occur, subscribe to the Siemens
Industrial Security RSS feed at http://www.siemens.com/industrialsecurity.

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 2
 Table of Contents

Table of Contents
Warranty and Liability ................................................................................................. 2
1 Introduction ........................................................................................................ 4
1.1 Overview............................................................................................... 4
1.2 How RSTP works ................................................................................. 6
1.2.1 Mesh network structure ........................................................................ 6
1.2.2 Priorities and path costs ....................................................................... 8
1.2.3 Roles and tasks .................................................................................... 9
1.2.4 Port roles and states .......................................................................... 10
1.2.5 Steps for determining the RSTP topology .......................................... 11
1.3 Rules and recommendations ............................................................. 14
1.3.1 Guidelines for setting up..................................................................... 14
1.3.2 Notes on operation ............................................................................. 15
1.4 Components used .............................................................................. 16
2 Engineering ...................................................................................................... 17
2.1 Hardware configuration ...................................................................... 17
2.2 Configuration ...................................................................................... 18
2.2.1 Preparation and settings .................................................................... 18
2.2.2 Configuration of RSTP ....................................................................... 19
2.3 Commissioning ................................................................................... 23
2.4 Test..................................................................................................... 26
2.5 Diagnostics ......................................................................................... 29
 Siemens AG 2016 All rights reserved

3 Additional Connection Method ...................................................................... 30

4 Appendix .......................................................................................................... 31
4.1 Siemens Services ............................................................................... 31
4.2 Links and literature ............................................................................. 32
4.3 Change documentation ...................................................................... 32

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 3
 1 Introduction

1 Introduction
1.1 Overview
Requirement
Networking machine segments, plant parts and production islands and connecting
them to higher-level office networks are key elements of communication in Industry
4.0 machinery and plant engineering.
Today’s technologies for networking plant components and fully digitizing
processes allow a seamless infrastructure from the field level to the office/MES
level.
As a result, process and production data is not only available at the field level, but
also seamlessly transferred to cross-area EDP systems. In many automation
systems, operation and maintenance is mostly fully automated or remote controlled
from control centers without any operating staff on site.
Essential to this development is a reliable network tuned to industrial conditions to
ensure maximum security and availability.

Action
A stable, flexible and redundant data network must be implemented to meet the
requirements of Industry 4.0. This is achieved by designing the communication
 Siemens AG 2016 All rights reserved

networks with redundant physical connection paths between the network nodes.
Special media redundancy protocols ensure a loop-free network topology and
detection of communication interruptions.

Benefit
A redundant network structure provides the following benefit:
 A redundant structure significantly increases availability as the failure of
individual devices does not affect communication.
 Necessary maintenance and repair work can be carried out without being
pressured by time as it is not required to shut down the network.
 In the event of a network disturbance, fast network diagnostics is possible and
troubleshooting is accelerated.
 If an error occurs, a redundant structure reduces the costs caused by
downtimes.

Mesh paths as a possible solution

In the plant-level office network, mesh networks are the most common method to
compensate for interruptions in the network. It is characterized by:
 Detection of the network disturbance and self-healing of the network.
 Can be implemented for small and very large networks.
 Can be used in Gigabit networks.
 Standardized protocol enables communication between devices from different
manufacturers.
 Applicable to any network structure.

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 4
 1 Introduction

Application implementation
Using a specific sample configuration, this application example shows how the
“Rapid Spanning Tree Protocol” (RSTP) works. RSTP is a vendor-independent
redundancy protocol to increase network availability in mesh networks that ensures
loop-free communication. It is one of the most common redundancy protocols in
office networks.
RSTP operates at Layer 2 of the OSI model.
The example will have the following structure:
Figure 1-1

RSTP
 Siemens AG 2016 All rights reserved

Possible application
The redundancy solution used in this application example is particularly suited for
plant-level office networks with predominantly non-time-critical communication.
RSTP is vendor-independent, which makes it possible to use network components
from different manufacturers.
If an error occurs, the network – depending on its size and planning – is
reconfigured in a few seconds.

Note This solution allows you to use devices from different manufacturers. All devices
must support RSTP according to IEEE 802.1D-2004.

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 5
 1 Introduction

1.2 How RSTP works

The “Rapid Spanning Tree Protocol” is a further development of the “Spanning
Tree Protocol” that was significantly improved in terms of the reconfiguration time.
Its working principle can be compared to that of the “spanning tree”.

1.2.1 Mesh network structure

Physical structure
“Spanning Tree” protocols are based on a mesh network. This network structure is
characterized by the fact that each switch is connected to one or more other
switches. Therefore, there are several paths to the same destination.
Without a suitable redundancy protocol, loops would be created in the network:
Unlike IP packets, Ethernet frames have no maximum lifetime (time to live, TTL)
and therefore potentially travel in infinite circles; within a very short time, this
results in a network segment overload.
Figure 1-2
 Siemens AG 2016 All rights reserved

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 6
 1 Introduction

Logical structure
The task of “Spanning Tree” protocols is to ensure freedom from loops by disabling
redundant communication paths and paths that are currently not required.
To this end, the “spanning tree” sets up the physical network to form a logical tree
that contains only a single path to each terminal. This is implemented by blocking
selected ports of the network switches. Which ports are set to the
forwarding/blocked state – and, in conjunction with this, the selection of the
optimum path – is determined by so-called BPDUs (Bridge Protocol Data Units)
and path costs.
Figure 1-3
 Siemens AG 2016 All rights reserved

Connection disabled
by RSTP

Bridge Protocol Data Units

The frames with which RSTP switches exchange data and information about the
network state are called BPDUs (Bridge Protocol Data Units). As multicasts, they
are sent to the MAC address registered specifically for RSTP, “01-80-C2-00-00-
00”.
As soon as an RSTP switch is turned on, it cyclically sends BPDUs to the network
via its active RSTP ports, even if no topology changes have occurred. Therefore,
they simultaneously serve as a “hello” packet and show the other switches that it
can still be accessed.
Figure 1-4

Sending of BPDUs

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 7
 1 Introduction

1.2.2 Priorities and path costs

For the “spanning tree” method, determining the overall topology and creating a
tree structure is based on calculations. Defined connection costs and priority
statements form the basis for this.

Path costs
When creating the RSTP tree and therefore defining the paths via which
communication is allowed, the path costs play an important role.
The specification defines the following costs:
Table 1-1
Bandwidth Costs
10 Mbit/s 2000000
100 Mbit/s 200000
1 Gbit/s 20000
10 Gbit/s 2000
100 Gbit/s 200
1 Tbit/s 20
10 Tbit/s 2
 Siemens AG 2016 All rights reserved

For example, if both a 10 Mbit/s uplink and a 100 Mbit/s uplink lead to the same
destination, the 10 Mbit/s link will normally be blocked as a redundant path due to
the higher costs.

Note The path costs can also be defined manually, for example, to select a preferred
uplink at the same speed.

Bridge ID
Each RSTP switch is assigned a priority, the so-called “bridge ID”. It is composed
of a “bridge priority” that (in most cases) can be set and the switch’s own MAC
address.
In the device, the priority can be entered from 0 to 61440 in steps of 4096.
The “bridge ID” determines the selection of the “root bridge” – the tree’s reference
point.

Port ID
Aside from the “bridge ID”, priorities are also assigned to the individual ports of the
RSTP switch, the “port ID”. This ID is composed of a “port priority” that (in most
cases) can be set and the switch’s MAC address.
The “port ID” determines the selection of the port if several ports of the switch lead
to the same destination.

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 8
 1 Introduction

1.2.3 Roles and tasks

Each switch of an RSTP network is assigned a role.

Roles and tasks

To enable the “spanning tree” to calculate the overall topology and, based on the
result, create a tree structure, the “root bridge” is selected first. It is the reference
point for the entire “spanning tree” and calculates the paths and settings of the tree
in an RSTP network.
Only one switch performs this role. The “bridge ID” is used to determine which
switch is assigned the “root bridge” role.
The task of the other switches is to enable/disable ports depending on the settings.
In addition, they must inform the other switches of topology changes (e.g., line
failure caused by a link down on the port) or respond to the notifications from the
other switches. For this purpose, BPDUs contain, among other things, a “topology
change flag” and the state of the sending port.

Selection of the “root bridge”

The “root bridge” is selected undemocratically: The role is assigned to the device
with the lowest “bridge ID”.
Therefore, the “bridge priority” normally decides which switch becomes the “root
bridge”. If devices have the same priority, the lower MAC address decides.
 Siemens AG 2016 All rights reserved

To allow a “bridge ID” comparison between all switches, BPDUs occasionally

include the sender’s “bridge ID” but also the “root bridge’s” “bridge ID”.

Tip For the SCALANCE switches, the “bridge priority” can be set in Web Based
Management. This allows you to select a specific switch for the “root bridge” role.
A switch with a “bridge priority” of 0 will most likely become the “root bridge”,
unless another switch in the network also has this value. In this case, the MAC
address decides.

Note Even during operation, a “root bridge” is replaced when a switch with a better
“bridge ID” is connected. In this case, the entire RSTP network is reorganized.
As a result, network disturbances may occur.

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 9
 1 Introduction

1.2.4 Port roles and states

A switch port can have different roles and states.

Port states
Depending on the settings (therefore dynamic), RSTP switches must
enable/disable their ports to enable/disable specific communication paths.
Therefore, a switch port that supports RSTP can dynamically have different states.
The port’s behavior differs depending on the state:
 Discarding
The port receives and processes only BPDUs. No frames – neither data
frames nor BPDUs – are forwarded. The port is not part of the RSTP tree and
does not learn MAC addresses. The port is therefore passive.
 Learning
The port receives and processes only BPDUs. Data frames are discarded, but
BPDUs continue to be sent. The port is part of the RSTP tree and learns MAC
addresses. The port is passive; however, it is prepared for the active state.
 Forwarding
The port forwards all frames and is also part of the RSTP tree. It learns MAC
addresses. The port is active.
 Siemens AG 2016 All rights reserved

Port roles
The port’s role in RSTP determines the port’s state. The RSTP standard defines
four different roles for active RSTP ports and one role for connecting terminals:
 Root port
The switch port with the lowest path costs to the “root bridge” is the so-called
“root port”. This port always has the “forwarding” state.
Each switch must not have more than one connection to the “root bridge”. If
two ports of a switch have the same path costs to the “root bridge”, the higher-
level switches decide which path is enabled.
The only switch without a “root port” is the “root bridge” itself.
 Designated port
This port is the best and most cost-effective connection to a lower-level LAN
segment. This is decided by the path costs and the “port ID” of the respective
port.
Normally, all “root bridge” ports have the “designated port” role as they are
always in “forwarding” mode.
 Alternate port
A port that receives BPDUs from another switch that has a better connection to
the “root bridge” is called an “alternate port”. These ports always have the
“discarding” state to ensure freedom from loops in the network.
If a failure occurs, the port is an alternative to the “root bridge”.
 Backup port
A “backup port” is a port that receives BPDUs from its own switch. This
behavior occurs when RSTP is connected to a shared medium (e.g., a network
connected through a HUB).
 Edge port
Strictly speaking, the “edge port” is not an RSTP port role; it is, rather, a
“designated port” with a special function. It is used for connecting terminals. No
BPDUs are sent via “edge ports”; when a BPDU is received, the port loses its
edge state.

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 10
 1 Introduction

1.2.5 Steps for determining the RSTP topology

When the RSTP network is started for the first time, a new switch has been added
or the “root bridge” has failed, the “spanning tree” is recalculated. This is done in
three essential steps:
 Selection of the “root bridge”
 Selection of the “root ports”
 Selection of the “designated ports”

Selection of the root bridge

As soon as the RSTP switches are turned on, they first compare their “bridge IDs”.
The lower the “bridge priority”, the higher the chance of becoming the “root bridge”.
If the switches have the same “bridge priority”, the MAC address decides; the lower
one wins.
Figure 1-5

Bridge priority: Bridge priority:

8192 4096
“Root bridge”
 Siemens AG 2016 All rights reserved

Bridge priority: Bridge priority:

32768 32768

Note For the status of the RSTP switch, go to the “Information > Redundancy” menu
of its Web Based Management.

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 11
 1 Introduction

Selection of the root ports

Once the “root bridge” has been determined, the other switches determine the
most cost-effective path to the “root bridge”. The port with the lowest path costs to
the “root bridge” becomes the “root port” and is enabled accordingly. When ports
have the same costs, the lower “port ID” wins.
Figure 1-6
Root bridge

R R

Selection of the designated ports

 Siemens AG 2016 All rights reserved

In the next step, the switches determine the “designated port”. Using the BPDUs,
they determine the best connection to a lower-level LAN segment. If all
connections have identical path costs, the “port priority” decides or – if they have
the same priorities – the lowest MAC address decides which port is selected as the
“designated port”.
In the below example, all connections are set to 100 Mbit/s and all ports have the
same “port priority”. Therefore, the MAC address decides among the switches and
selects the “designated port”.
Figure 1-7

MAC address:
00-1B-1B-00-00-01 Root bridge
D
R D
D D D D

R R
D
MAC address: MAC address:
00-1B-1B-00-00-02 00-1B-1B-00-00-03

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 12
 1 Introduction

Depending on the connection, the other ports become the “alternate port”, “backup
port” or “edge port”.
Figure 1-8

Root bridge
A D
R D
D D D D

A R A R
D A

Note For SCALANCE switches, a blocked port is indicated by a flashing port LED.

Reconfiguration
 Siemens AG 2016 All rights reserved

When the network has been set up, the RSTP switches regularly exchange “hello”
BPDUs to check whether the neighboring switch is reachable. If a switch has not
received a BPDU after three times the hello time, it assumes a disconnect or defect
and triggers the recalculation of the network topology. A reconfiguration is also
triggered by adding a new switch or manual interventions such as changing
priorities.
Triggering the reconfiguration is initiated by the “topology change flag” in the
BPDU: All RSTP switches that have detected the change flood the network with the
“topology change” BPDUs and therefore cause all RSTP devices to clear their
internal MAC address tables and repopulate them after recalculating the topology.

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 13
 1 Introduction

1.3 Rules and recommendations

1.3.1 Guidelines for setting up

When using the redundancy protocol, the following applies:

Usable devices
“RSTP” conforms to the “Rapid Spanning Tree Protocol” according to IEEE
802.1D-2004.
The network may only consist of devices that support this function.
These devices include:
 All SCALANCE switches, except the switches of the X-200 (IRT) series
 External devices that support RSTP according to IEEE 802.1D-2004.

Tip The TIA Selection Tool enables you to filter products by features. This allows you
to quickly find suitable products for your use case.
http://siemens.de/tia-selection-tool

Setting up
The following conditions must be met for faultless operation with the RSTP
 Siemens AG 2016 All rights reserved

redundancy protocol:
 All switches must support RSTP and have RSTP enabled.
 STP and RSTP cannot be simultaneously used in a network. If a “spanning
tree” frame is detected on a switch port, this port reverts from RSTP to
“spanning tree”.
 In the network, any topology can be selected.
 The maximum number of switches in the RSTP network is 40.
 “RSTP Big Network Support” and Enhanced Rapid Spanning Tree (eRSTP)
based on RSTP allow the use of up to 80 switches in a ring topology.

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 14
 1 Introduction

1.3.2 Notes on operation

Selection of the root bridge

In large networks, RSTP calculations can be complex so that a high-performance
switch should perform the “root bridge” role.
The “root bridge” is determined based on the “bridge priority”. If more than one
switch has the same minimum bridge priority, the MAC address selects the “root
bridge”. The candidate with the lowest values wins. The MAC addresses of older
switches are often lower than the ones of their successors as many manufacturers
assign them in ascending order. This involves the risk of the oldest and potentially
weakest switch becoming the “root bridge”.
Therefore, it is recommended to set the “bridge priority” manually, i.e., to assign
this role to a specific switch.

Advance planning
If you have to design an entirely new RSTP network, the following questions should
be clarified in advance:
 How many switches do you want to integrate into the network?
 How important are very short failover times?
 Which topology do you want to use?
 Siemens AG 2016 All rights reserved

 Do you have to bridge longer distances?

Changes to the topology, for example, if a failure occurs or a new switch is added
or manual interventions always result in a recalculation of the RSTP network. The
duration of the recalculation is largely determined by the “root bridge’s” position in
the network, the number of switches connected in series and the networking
among the switches.
Therefore, well-conceived advance planning of a large RSTP is advisable to keep
the calculation time as short as possible.

RSTP parameters
To optimize response times in the event of topology changes or stability in
networks with a very large number of switches connected in series, the following
RSTP parameters can be modified:
 Bridge Hello Time: This parameter defines the interval between two “hello”
BPDUs sent cyclically by each RSTP switch.
 Bridge Forward Delay: An RSTP switch does not send new configuration
information immediately, but only after a delay that can be set here. This
ensures that the operation of the new topology does not start until all RSTP
switches have been provided with the necessary information.
 Bridge Max Age: This value defines the maximum “age” that a received BPDU
may have to be accepted as valid. This parameter therefore defines how
quickly the system responds to topology changes.
 Admin Path Cost: This parameter allows you to manually configure the path
costs. This allows you to prioritize connections regardless of the bandwidth.
Modifying these time values is recommended only if you have detailed knowledge
of the “Spanning Tree Protocol”.

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 15
 1 Introduction

1.4 Components used

This application example demonstrates the RSTP network with the following
components:
 4 x SCALANCE XB208 (MLFB: 6GK5208-0BA00-2AB2)
 1 x 24V power supply with cable connector and terminal block plug.
 1 x PC that has a web browser installed.
 The necessary network cables, TP cables (twisted pair) according to the IE FC
RJ45 standard for Industrial Ethernet.
 Siemens AG 2016 All rights reserved

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 16
 2 Engineering

2 Engineering
2.1 Hardware configuration
Overview
The following figure shows the components and their networking for the application
example.
Figure 2-1
XB208_2 XB208_1

RSTP
 Siemens AG 2016 All rights reserved

XB208_3 XB208_4

Networking
Connect the modules as shown below:
XB208_2 XB208_1

P1 P1

P2
RSTP

P2

P1 P1

XB208_3 XB208_4

Note Mesh the network only after the configuration. Otherwise, the creation of frame
loops may cause unwanted responses in the network.

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 17
 2 Engineering

2.2 Configuration
2.2.1 Preparation and settings

Resetting to factory default

If your modules are not straight from the factory, use the RESET button to reset all
of them to factory default.
To do this, press the SET button for at least 12 s. After this time has elapsed, the
device will be reset to factory default.

IP addresses
The modules are configured using Web Based Management.
Use, for example, the Primary Setup Tool (PST) to assign the IP address listed in
Table 2-1 to the SCALANCE X modules. PST is available as a free download (see
Chapter 4.2).
Table 2-1
Module IP address Subnet mask
XB208_1 192.168.0.1
XB208_2 192.168.0.2
XB208_3 192.168.0.3 255.255.255.0
 Siemens AG 2016 All rights reserved

XB208_4 192.168.0.4
PG/PC 192.168.0.250

Bridge priority
In this example, each RSTP switch is assigned a default “bridge priority”. This
allows you to see in advance which switch will be given the “root bridge” role.
The following table lists the “bridge priority” to be assigned and illustrates the
assigned role in RSTP.
Table 2-2
Module “Bridge priority” RSTP role
XB208_1 4096 “Root bridge”
XB208_2 8192 RSTP switch
XB208_3 32768 RSTP switch
XB208_4 32768 RSTP switch

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 18
 2 Engineering

Opening Web Based Management

Establish a network connection between the PC/PG and the SCALANCE modules.
The ping command allows you to check whether a connection has been
established.
In the address bar of the web browser, type the IP address of the device. If the
connection to the device is correct, the Web Based Management (WBM) Login
page is displayed.

1. To log in to the SCALANCE, use the following login data:

Name: admin
Password: admin

2. When you log in for the first time or after a reset to factory default, you are
prompted to change the password. Repeat the password to confirm it. The two
entered passwords must match.

3. Click the “Set Values” button to complete the operation and activate the new
password.

Result:
 Siemens AG 2016 All rights reserved

After successful login, the start page appears.

2.2.2 Configuration of RSTP

Overview
This chapter focuses on the configuration of an RSTP network and lists the
following configuration steps for each SCALANCE switch:
 Enabling RSTP
 Changing the “bridge priority”

Note These configuration steps are identical for all four SCALANCE switches used.
Only the “bridge priority” values differ.
The following guide is a configuration template for loop-free redundancy that
applies to all four SCALANCE switches.

Opening Web Based Management

Connect the PC/PG to a free port of the SCALANCE XB208 and use a web
browser to open its Web Based Management.
Enter the appropriate login data to log in.

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 19
 2 Engineering

Disabling ring redundancy

The PROFINET version of the SCALANCE XB208 has ring redundancy enabled by
factory default; it must be disabled before configuring RSTP.
Proceed as follows:
1. Go to the “Layer 2 > Ring Redundancy” menu.

2. Uncheck the “Ring Redundancy” check box to disable ring redundancy.

3. Apply the setting with “Set Values”.

 Siemens AG 2016 All rights reserved

Result:
The SCALANCE has been prepared for the RSTP configuration.

Note Disable ring redundancy of all other SCALANCE switches.

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 20
 2 Engineering

Enabling “Spanning Tree”

To set up redundancy based on “RSTP”, proceed as follows:
1. Go to the “Layer 2 > Spanning Tree” menu.

2. Check the “Spanning Tree” check box to enable redundancy. Make sure that
the protocol is set to “RSTP”.
 Siemens AG 2016 All rights reserved

3. Click “OK” to confirm the message.

Note:
“Passive Listening” is a proprietary Siemens solution that is required when
connecting an RSTP network to an HRP ring (see Chapter 3).

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 21
 2 Engineering

4. Click the “Set Values” button to apply the settings.

Setting the “bridge priority”

To set the “bridge priority” to a user-defined value, proceed as follows:
1. In the “Layer 2 > Spanning Tree” menu, go to the “ST General” tab.
 Siemens AG 2016 All rights reserved

2. In the “Bridge Priority” field, enter the value defined in advance for this
SCALANCE (see Table 2-2).

3. Click the “Set Values” button to apply the settings.

Result:
The SCALANCE has been prepared for use as an RSTP switch.

Note Use this guide to prepare all four SCALANCE switches for their use in the
network.

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 22
 2 Engineering

2.3 Commissioning
End topology
After configuring, the modules can be connected. Create a topology as shown
below:
Figure 2-2

XB208_2 XB208_1

P5 P5
P1 P1
P4
P3 P3
P2 RSTP P2 PG/PC

P2 P3 P2
P3
P1 P1
 Siemens AG 2016 All rights reserved

XB208_3 XB208_4

Roles and states

After setting up the mesh network, the “spanning tree” calculates the overall
topology and, based on the result, creates a tree structure.
To this end, the “root bridge” is selected first. It is the reference point for the entire
“spanning tree” and calculates the paths and settings of the tree in an RSTP
network.
In this example, the “bridge priority” was explicitly assigned so that the SCALANCE
“XB208_1”, due to the lower “bridge ID”, is assigned the role.
The state is noted accordingly and all ports are “designated ports” with the
“forwarding” state.
Figure 2-3

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 23
 2 Engineering

Now the other switches have the task of determining a “root port” and – depending
on the selection – enable or disable the other ports.
To this end, the SCALANCE “XB208_2” defines port 1 as the “root port” as it is the
port closest to the “root bridge”.
Figure 2-4

In the SCALANCE “XB208_3”, port 3 as the direct neighbor is the “root port”.
Figure 2-5
 Siemens AG 2016 All rights reserved

The SCALANCE “XB208_4”, however, uses port 2 as its “root port”.

Figure 2-6

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 24
 2 Engineering

The following figure illustrates the states and roles after calculating the topology.
Figure 2-7

XB208_1
XB208_2 Root bridge

A D
R D
E
D D DD PG/PC

A R AR
A D

XB208_3 XB208_4
 Siemens AG 2016 All rights reserved

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 25
 2 Engineering

2.4 Test
Healthy state
After completing the configuration and commissioning, you have set up a loop-free
network.
The RSTP switches block redundant paths and make the network appear as a tree
structure.
The following figure shows the topology in a healthy state:
Figure 2-8

XB208_1
XB208_2 Root bridge

PG/PC
 Siemens AG 2016 All rights reserved

XB208_3 XB208_4

Test scenario
The “RUGGEDCOM Ping” tool (see Chapter 4.2) is suitable to test whether RSTP
works correctly.
RUGGEDCOM PING is a high accuracy graphical ping tool. This handy utility can
send ICMP echo messages and process incoming responses with a granularity of
1 ms. Network administrators will be able to perform RSTP performance testing,
ping sweeps to automatically discover devices and capture outage durations for
devices.
Send a continuous ping to one of the SCALANCE switches to start the utility.

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 26
 2 Engineering

Errors in the network

To test redundancy, remove a(n) (unblocked) connection (e.g., between
SCALANCE “XB208_1” and SCALANCE “XB208_2”) to provoke a reorganization
of the network.
The following figure shows the topology in the event of a fault:
Figure 2-9

XB208_1
XB208_2 Root bridge

PG/PC
 Siemens AG 2016 All rights reserved

XB208_3 XB208_4
The affected devices detect a link down and send BPDUs with a “topology change”
flag to the network so that all RSTP devices clear their internal MAC address
tables.
The “root bridge” recalculates the network. The SCALANCE “XB208_2” has
changed its “root port” (port 5) and enabled the previously blocked path to the
SCALANCE “XB 208_1”:

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 27
 2 Engineering

Now the topology is as follows:

Figure 2-10

XB208_1
XB208_2 Root bridge

PG/PC

XB208_3 XB208_4
 Siemens AG 2016 All rights reserved

Result:
Recalculating the network requires a certain amount of time. After the
reconfiguration time, the continuous ping continues to run without any problems.
You can read the failover time with the aid of “RUGGEDCOM Ping”.

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 28
 2 Engineering

2.5 Diagnostics
On site
Ports that are currently blocked by RSTP have a flashing port LED on the
SCALANCE housing. The only switch in the network for which no port is blocked is
the “root bridge”.

Web Based Management

Web Based Management of the SCALANCE X modules allows you to retrieve
information about the device status regarding redundancy.
Go to the “Information > Redundancy” menu and select the “Spanning Tree” tab.

It provides information about

 the “Spanning Tree” mode
 the role of the device.
 the switch that performs the “root bridge” role
 the ports’ roles and states.
Figure 2-11
 Siemens AG 2016 All rights reserved

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 29
 3 Additional Connection Method

3 Additional Connection Method

Requirement
The plant-level office network that uses a mesh topology and RSTP is to be
redundantly connected to the main ring of the automation network. The aim of this
is to enable service engineers to access controllers and field devices at any time.
There is no requirement for a fast or deterministic failover time; however, existing
network components and the network structure must not be changed.

Implementation
This connection can be achieved through two stubs and two additional protocols,
“Passive Listening (PL)” and “Enhanced Passive Listening Compatibility (EPLC)”.
“Passive Listening” is a proprietary Siemens solution and ensures that the BPDUs
from the RSTP network are transparently forwarded by the ring nodes and return. If
this were not the case, loops would be created at the connecting point between
RSTP and the ring.
“Passive Listening” must therefore be enabled on all ring nodes.
“Enhanced Passive Listening Compatibility” is enabled on the two switches of the
connecting point that are in the RSTP network. This protocol is an extension of
“Passive Listening” and ensures faster failover if a stub between the RSTP network
 Siemens AG 2016 All rights reserved

and the ring fails.

Figure 3-1

PL

HRP
PL

PL
EPLC

RSTP

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 30
 4 Appendix

4 Appendix
4.1 Siemens Services
Industry Online Support
Do you have any questions or do you need support?
With Industry Online Support, our complete service and support know-how and
services are available to you 24/7.
Industry Online Support is the place to go to for information about our products,
solutions and services.
Product Information, Manuals, Downloads, FAQs and Application Examples – all
the information can be accessed with just a few clicks:
https://support.industry.siemens.com/ .

Technical Support
Siemens Industry’s Technical Support offers you fast and competent support for
any technical queries you may have, including numerous tailor-made offerings
ranging from basic support to custom support contracts.
You can use the web form below to send queries to Technical Support:
www.siemens.com/industry/supportrequest.
 Siemens AG 2016 All rights reserved

Service offer
Our service offer includes the following services:
 Product Training
 Plant Data Services
 Spare Part Services
 Repair Services
 Field & Maintenance Services
 Retrofit & Modernization Services
 Service Programs & Agreements
For detailed information about our service offer, please refer to the Service
Catalog:
https://support.industry.siemens.com/cs/sc

Industry Online Support app

The “Siemens Industry Online Support” app provides you with optimum support
while on the go. The app is available for Apple iOS, Android and Windows Phone.
https://support.industry.siemens.com/en/sc/2067

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 31
 4 Appendix

4.2 Links and literature

Table 4-1
No. Topic
\1\ Siemens Industry Online Support
https://support.industry.siemens.com
\2\ Download page of the entry
https://support.industry.siemens.com/cs/ww/en/view/109742120
\3\ SCALANCE XB-200 – Operating Instructions
https://support.industry.siemens.com/cs/ww/en/view/109476747
\4\ SCALANCE XB-200 Web Based Management – Configuration Manual
https://support.industry.siemens.com/cs/ww/en/view/109476752
\5\ SITRAIN courses:
Siemens Industrial Networks Education – Certification Program
https://sitrain.automation.siemens.com/DE/sitrain/LearningPathView.aspx?AppLang
=de&Ref=Catalog&CatalogRef=BAAAGHM&LPID=BAAAATS&RetUrl=https%3A%2
F%2Fsitrain.automation.siemens.com%2FDE%2Fsitrain%2FCatalogDetail.aspx%3
FdataKey%3DBAAAGHM
\6\ Primary Setup Tool
https://support.industry.siemens.com/cs/ww/en/view/19440762
\7\ RUGGEDCOM Ping
 Siemens AG 2016 All rights reserved

http://w3.siemens.com/mcms/industrial-communication/en/rugged-
communication/products/software/Pages/ping.aspx

4.3 Change documentation

Table 4-2
Version Date Modifications
V1.0 10/2016 First version

Redundancy_RSTP
Entry ID: 109742120, V1.0, 10/2016 32