Hirschmann RS20 series User manual

UM RedundConfig L2P
Release 8.0 05/2013
Technical Support
https://hirschmann-support.belden.eu.com
User Manual
Redundancy Configuration
Industrial ETHERNET (Gigabit-)Switch
RS20/RS30/RS40, MS20/MS30, OCTOPUS, PowerMICE,
RSR20/RSR30, MACH 100, MACH 1000, MACH 4000

The naming of copyrighted trademarks in this manual, even when not specially indicated, should
not be taken to mean that these names may be considered as free in the sense of the trademark
and tradename protection law and hence that they may be freely used by anyone.
© 2013 Hirschmann Automation and Control GmbH
Manuals and software are protected by copyright. All rights reserved. The copying, reproduction,
translation, conversion into any electronic medium or machine scannable form is not permitted,
either in whole or in part. An exception is the preparation of a backup copy of the software for
your own use. For devices with embedded software, the end-user license agreement on the
enclosed CD/DVD applies.
The performance features described here are binding only if they have been expressly agreed
when the contract was made. This document was produced by Hirschmann Automation and
Control GmbH according to the best of the company's knowledge. Hirschmann reserves the right
to change the contents of this document without prior notice. Hirschmann can give no guarantee
in respect of the correctness or accuracy of the information in this document.
Hirschmann can accept no responsibility for damages, resulting from the use of the network
components or the associated operating software. In addition, we refer to the conditions of use
specified in the license contract.
You can get the latest version of this manual on the Internet at the Hirschmann product site
(www.hirschmann.com).
Printed in Germany
Hirschmann Automation and Control GmbH
Stuttgarter Str. 45-51
72654 Neckartenzlingen
Germany
Tel.: [phone]
Rel. 8.0 - 05/2013 – 29.04.2013

Contents
UM RedundConfig L2P
Release 8.0 05/2013 3
Contents
About this Manual 5
Key 7
1 Introduction 9
1.1 Overview of Redundancy Topologies 10
1.2 Overview of Redundancy Protocols 12
2 Link Aggregation 15
2.1 Example of link aggregation 16
2.1.1 Creating and configuring the link aggregation 17
2.2 HIPER-Ring and Link Aggregation 22
3 Ring Redundancy 25
3.1 Example of a HIPER-Ring 28
3.1.1 Setting up and configuring the HIPER-Ring 30
3.2 Example of a MRP-Ring 34
3.3 Example of a Fast HIPER-Ring 40
4 Multiple Rings 45
4.1 Sub-Ring 46
4.1.1 Sub-Ring description 46
4.1.2 Sub-Ring example 50
4.1.3 Sub-Ring example configuration 53
5 Ring/Network Coupling 59
5.1 Variants of the ring/network coupling 60
5.2 Preparing a Ring/Network Coupling 62
5.2.1 STAND-BY switch 62
5.2.2 One-Switch coupling 65
5.2.3 Two-Switch coupling 71
5.2.4 Two-Switch Coupling with Control Line 79

Contents
4UM RedundConfig L2P
Release 8.0 05/2013
6 Spanning Tree 87
6.1 The Spanning Tree Protocol 89
6.1.1 The tasks of the STP 89
6.1.2 Bridge parameters 90
6.1.3 Bridge Identifier 90
6.1.4 Root Path Cost 91
6.1.5 Port Identifier 93
6.2 Rules for Creating the Tree Structure 94
6.2.1 Bridge information 94
6.2.2 Setting up the tree structure 94
6.3 Example of determining the root path 97
6.4 Example of manipulating the root path 99
6.5 Example of manipulating the tree structure 101
6.6 The Rapid Spanning Tree Protocol 102
6.6.1 Port roles 102
6.6.2 Port states 105
6.6.3 Spanning Tree Priority Vector 106
6.6.4 Fast reconfiguration 106
6.6.5 Configuring the Rapid Spanning Tree 107
6.7 Combining RSTP and MRP 116
6.7.1 Application example for the combination of RSTP and
MRP 118
A Readers’ Comments 121
B Index 123
C Further Support 125

About this Manual
UM RedundConfig L2P
Release 8.0 05/2013 5
About this Manual
The “Redundancy Configuration” user manual document contains the
information you require to select the suitable redundancy procedure and
configure it.
The “Basic Configuration” user manual contains the information you need to
start operating the device. It takes you step by step from the first startup
operation through to the basic settings for operation in your environment.
The “Installation” user manual contains a device description, safety
instructions, a description of the display, and the other information that you
need to install the device.
The “Industry Protocols” user manual describes how the device is connected
by means of a communication protocol commonly used in the industry, such
as EtherNet/IP and PROFINET IO.
The “Graphical User Interface” reference manual contains detailed
information on using the Graphical User Interface to operate the individual
functions of the device.
The “Command Line Interface” reference manual contains detailed
information on using the Command Line Interface to operate the individual
functions of the device.

About this Manual
6UM RedundConfig L2P
Release 8.0 05/2013
The Industrial HiVision Network Management Software provides you with
additional options for smooth configuration and monitoring:
Simultaneous configuration of multiple devices
Graphical user interface with network layout
Auto-topology discovery
Event log
Event handling
Client/server structure
Browser interface
ActiveX control for SCADA integration
SNMP/OPC gateway.

Key
UM RedundConfig L2P
Release 8.0 05/2013 7
Key
The designations used in this manual have the following meanings:
Symbols used:
List
Work step
Subheading
Link Cross-reference with link
Note: A note emphasizes an important fact or draws your attention to a dependency.
Courier ASCII representation in user interface
Execution in the Graphical User Interface
Execution in the Command Line Interface
WLAN access point
Router with firewall
Switch with firewall
Router
Switch

Key
8UM RedundConfig L2P
Release 8.0 05/2013
Bridge
Hub
A random computer
Configuration Computer
Server
PLC -
Programmable logic
controller
I/O -
Robot

Introduction
UM RedundConfig L2P
Release 8.0 05/2013 9
1 Introduction
The device contains a range of redundancy functions:
Link Aggregation
HIPER-Ring
MRP-Ring
Fast HIPER-Ring (RSR20, RSR30 and MACH 1000)
Sub-Ring (RSR20, RSR30 and MACH 1000)
Ring/Network coupling
Rapid Spanning Tree Algorithm (RSTP)

Introduction
10
1.1 Overview of Redundancy
Topologies
UM RedundConfig L2P
Release 8.0 05/2013
1.1 Overview of Redundancy
Topologies
To introduce redundancy onto layer 2 of a network, you first define which
network topology you require. Depending on the network topology selected,
you then choose from the redundancy protocols that can be used with this
network topology.
The following topologies are possible:
Network topology Possible redundancy
procedures
Comments
Tree structure
without loops
(cycle-free)
Only possible in
connection with
physical loops
-
Topology with 1
loop
RSTP
Ring Redundancy
Ring Redundancy procedures (HIPER-Ring, Fast
HIPER-Ring or MRP) provide shorter switching
times than RSTP.
Topology with 2
loops
RSTP
Ring Redundancy
Sub-Ring (RSR20,
RSR30, PowerMICE,
MACH 1000 and
MACH 4000)
Ring redundancy: a Basis-Ring with a Sub-Ring
or an MRP-Ring with an RSTP-Ring.
Topology with 3
non-nested loops
RSTP
Ring Redundancy
Sub-Ring (RSR20,
RSR30, PowerMICE,
MACH 1000 and
MACH 4000)
Ring coupling
The ring coupling provides particular support
when redundantly coupling a redundant ring to
another redundant ring, or to any structure that
only works with Hirschmann devices
Topology with
nested loops
RSTP
Sub-Ring (RSR20,
RSR30, PowerMICE,
MACH 1000 and
MACH 4000)
Ring coupling
Ring coupling only couples non-nested rings,
though these can couple local Sub-Rings.
Table 1: Overview of Redundancy Topologies

Introduction
UM RedundConfig L2P
Release 8.0 05/2013
1.1 Overview of Redundancy
Topologies
11
The Ring Redundancy Protocol MRP has particular properties to offer:
You have the option of nesting MRP-Rings. A coupled ring is known as a
Sub-Ring (see on page 46 “Sub-Ring”).
You have the option of coupling to MRP-Rings other ring structures that
work with RSTP (see on page 116 “Combining RSTP and MRP”).

Introduction
12
1.2 Overview of
Redundancy Protocols
UM RedundConfig L2P
Release 8.0 05/2013
1.2 Overview of
Redundancy Protocols
Redundancy
procedure
Network topology Switch-over time
RSTP Random structure typically < 1 s (STP < 30 s), up to < 30 s - depends
heavily on the number of devices
Note: Up to 79 devices possible, depending on topology and configuration. If
the default values (factory settings) are used, up to 39 devices are possible,
depending on the topology (see on page 87 “Spanning Tree”).
HIPER-Ring Ring typically 80 ms, up to < 500 ms or < 300 ms (selectable)
- the number of switches has a minimal effect on the
switch-over time
MRP-Ring Ring typically 80 ms, up to < 500 ms or < 200 ms (selectable)
- the number of switches has a minimal effect on the
switch over time
Note: In combination with RSTP in MRP compatibility mode, up to 39 devices
are possible, depending on the configuration. If the default values (factory
settings) for RSTP are being used, up to 19 devices are possible (see on
page 87 “Spanning Tree”).
Fast HIPER-
Ring (RSR20,
RSR30 and
MACH 1000)
Ring < 10 ms with 5 devices in ring.
With more than 5 devices, the switching time increases.
Sub-Ring
(RSR20,
RSR30,
PowerMICE,
MACH 1000
and
MACH 4000)
Ring segment
coupled to a primary
ring
typically 80 ms, up to < 500 ms or < 200 ms (selectable)
- the number of switches has a minimal effect on the
switch over time
Link
Aggregation
Coupling of network
segments via parallel
active lines with
dynamic load
distribution and line
redundancy
Table 2: Comparison of the redundancy procedures

Introduction
UM RedundConfig L2P
Release 8.0 05/2013
1.2 Overview of
Redundancy Protocols
13
Note: When you are using a redundancy function, you deactivate the flow
control on the participating device ports. If the flow control and the
redundancy function are active at the same time, there is a risk that the
redundancy function will not operate as intended.

Introduction
14
1.2 Overview of
Redundancy Protocols
UM RedundConfig L2P
Release 8.0 05/2013

Link Aggregation
UM RedundConfig L2P
Release 8.0 05/2013 15
2 Link Aggregation
The LACP (Link Aggregation Control Protocol based on IEEE 802.3ad) is a
network protocol for dynamically bundling physical network connections. The
added bandwidth of all connection lines is available for data transmission. In
the case of a connection breaking down, the remaining connections take
over the entire data transmission (redundancy). The load distribution
between the connection lines is performed automatically.
You configure a link aggregation by combining at least 2 existing parallel
redundant connection lines (known as a trunk) between two devices into one
logical connection. You can use link aggregation to combine up to 8
(optimally up to 4) connection lines between devices into a trunk.
Any combination of twisted pair and F/O cables can be used as the
connection lines of a trunk. Configure the connections so that the data rates
and the duplex settings of the related ports are matching.
The maximum that can exit a device are
– 2 trunks for rail devices with 4 ports,
– 4 trunks for rail and MICE devices with 8-10 ports,
– 7 trunks for all other devices.

Link Aggregation
16
2.1 Example of link aggregation
UM RedundConfig L2P
Release 8.0 05/2013
2.1 Example of link aggregation
In a network consisting of seven devices in a line topology, there are two
segments with a particularly large amount of data traffic. You therefore
decide to set up link aggregations in these segments. As well as dividing the
load over several lines, you also get increased reliability in these segments
through the redundant lines.
The link aggregation LATP (Link Aggregation Twisted Pair) consists of
3 twisted pair lines, and the link aggregation LAFO (Link Aggregation Fiber
Optic) consists of 2 glass fiber lines.
Figure 1: Example of link aggregation
NMS = Network Management Station
LATP = Link Aggregation Twisted Pair
LAFO = Link Aggregation Fiber Optic
The following example describes the configuration of the LATP link
aggregation. For this link aggregation, you provide three free twisted pair
ports at each of the two participating devices. (Connection: Module1 Port1 to
Port3).
3 x TP FDX
300 Mbit/s
2 x FO FDX
2 Gbit/s
10 km singlemode
NMS
LATP
LAFO

Link Aggregation
UM RedundConfig L2P
Release 8.0 05/2013
2.1 Example of link aggregation
17
2.1.1 Creating and configuring the
link aggregation
Note: A link aggregation connects exactly 2 devices.
You configure the link aggregation on each of the 2 devices involved. During
the configuration phase, you connect only one single connection line
between the devices. This is to avoid loops.
Under Basic Settings:Port Configuration, you configure all
three connections so that the transmission rate and the duplex settings of
the participating ports on both devices are matching.
Among the devices involved in a link aggregation, you define that device
that has the most devices between itself and the device to which the
configuration PC/(NMS network management station) is connected. You
begin the configuration at this device, otherwise the Link Aggregation
Control Protocol (LACP) can block ports and disconnect devices from the
network, so that they cannot be configured any more.
In the example below (see figure 2), you configure the link aggregation
first on device 3, then on device 2. If you accidentally disconnect device 3
from the network, you can access it again by selecting “Allow static link
aggregation” in the Redundancy: Link Aggregation dialog, or by
activating this option via the CLI.
Figure 2: Example: “Defining the first device”
NMS = Network Management Station
3 x TP FDX
300 Mbit/s
123
NMS

Link Aggregation
18
2.1 Example of link aggregation
UM RedundConfig L2P
Release 8.0 05/2013
Proceed as follows to configure a link aggregation from 3 twisted pair
lines on device 3:
Select the Redundancy:Link Aggregation (see figure 3)
dialog.
Figure 3: Creating the link aggregation
Select Allow static link aggregation if the partner device
does not support the Link Aggregation Control Protocol (LACP) (e.g.
MACH 3000).
Click “Create entry” to create a new link aggregation.
The Index column shows you the ID under which the device uses
a link aggregation (a trunk) as a virtual port. The device creates the
port in module 8, which does not physically exist, and the first link
aggregation then has the ID 8.1.
The Name column allows you to give this connection any name you
want. In this example, you give the new link aggregation the name
“LAPT”.
The Enabled column allows you to enable/disable a link
aggregation that has been set up. Leave the checkmark in the
“Enabled” column while you are using the link aggregation.

Link Aggregation
UM RedundConfig L2P
Release 8.0 05/2013
2.1 Example of link aggregation
19
Leave the checkmark in the Link Trap column if you want the
device to generate an alarm if all the connections of the link
aggregation are interrupted.
In the “STP Mode” column, you select
on if the link aggregation connection is connected to a Spanning
Tree,
off if no Spanning Tree is active, or if the link aggregation is a
segment of a HIPER-Ring.
“Type” shows whether you created this link aggregation manually
(Allow static link aggregation is selected), or whether it
was created dynamically using LACP (Allow static link
aggregation is not selected).
Note: If there are multiple connections between devices that support
LACP, and if Allow static link aggregation is nevertheless
selected, dynamic is still displayed, because in this case the
devices automatically switch to dynamic.
Figure 4: Link aggregation created and named.
Now assign to the ports participating in the link aggregation (ports
1.1, 1.2 and 1.3) the index of the link aggregation connection
LAPT (8.1). (see figure 5).

Link Aggregation
20
2.1 Example of link aggregation
UM RedundConfig L2P
Release 8.0 05/2013
Figure 5: Assigning ports to link aggregation
enable Switch to the privileged EXEC mode.
configure Switch to the Configuration mode.
link-aggregation LATP Create a new link aggregation with the name
LATP.
New link aggregation created. Slot/port is 8.1.
Interface 1/1 Configuration for port 1.1
addport 8/1 Assign port 1.1 to link aggregation 8.1.
Interface 1/2 Configuration for port 1.2
addport 8/1 Assign port 1.2 to link aggregation 8.1.
Interface 1/3 Configuration for port 1.3
addport 8/1 Assign port 1.3 to link aggregation 8.1.
exit Switch to the privileged EXEC mode.
show link-aggregation brief Show the parameters of all the link aggregations
created on the device.
Max. num. of LAGs: 7
Slot no. for LAGs: 8
Static Capability: Disabled
Logical Link-Aggr.
Interface Name Link State Mbr Ports Active Ports
---------- ---------- ------------ --------- -------------------
8/1 LATP Down 1/1,1/2, 1/3