Hirschmann RS20 series Owner's manual

Redundanz L2P
Release 5.0 04/09
Technische Unterstützung
[email protected]
User Manual
Redundancy Configuration
Industrial ETHERNET (Gigabit) Switch
RS20/RS30/RS40, MS20/MS30, OCTOPUS, Power MICE,
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.
© 2009 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 en-
closed CD applies.
The performance features described here are binding only if they have been expressly guaran-
teed in the contract. This publication has been created by Hirschmann Automation and Control
GmbH according to the best of our knowledge. Hirschmann reserves the right to change the con-
tents of this manual without prior notice. Hirschmann can give no guarantee in respect of the
correctness or accuracy of the details in this publication.
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.
Printed in Germany
Hirschmann Automation and Control GmbH
Stuttgarter Str. 45-51
72654 Neckartenzlingen
Germany
Tel.: [phone]
Rel. 5.0-01-0409 – 30.4.09

Content
Redundanz L2P
Release 5.0 04/09 3
Content
Content 3
About this Manual 5
Key 6
1 Introduction 9
1.1 Overview of Redundancy Procedure 10
2 Link Aggregation 11
2.1 Example of link aggregation 12
2.1.1 Creating and configuring the link aggregation 13
2.2 HIPER-Ring and link aggregation 18
3 Ring Redundancy 21
3.1 Example of HIPER-Ring 24
3.1.1 Setting up and configuring the HIPER-Ring 26
3.2 Example of MRP-Ring 30
3.3 Example of Fast HIPER-Ring 35
4 Sub-Ring (RSR20, RSR30, MACH1000) 41
4.1 Example configuration 45
4.1.1 Example description 45
4.1.2 Sub-Ring configuration 48
5 Ring/Network coupling 53
5.1 Variants of the ring/network coupling 54
5.2 Preparing a Ring/Network coupling 56
5.2.1 STAND-BY switch 56
5.2.2 One-Switch coupling 59
5.2.3 Two-Switch coupling 65
5.2.4 Two-Switch coupling with control line 73

Content
4Redundanz L2P
Release 5.0 04/09
6 Rapid Spanning Tree 81
6.1 The Spanning Tree Protocol 83
6.1.1 The tasks of the STP 83
6.1.2 Bridge parameters 84
6.1.3 Bridge Identifier 84
6.1.4 Root Path Costs 85
6.1.5 Port Identifier 86
6.2 Rules for creating the tree structure 88
6.2.1 Bridge information 88
6.2.2 Setting up the tree structure 88
6.3 Example of specifying the root paths 90
6.4 Example of manipulating the root paths 92
6.5 Example of manipulating the tree structure 94
6.6 The Rapid Spanning Tree Protocol 95
6.6.1 Port roles 95
6.6.2 Port states 97
6.6.3 Spanning Tree Priority Vector 97
6.6.4 Fast reconfiguration 98
6.6.5 Configuring the Rapid Spanning Tree 99
6.7 Combination of RSTP and MRP 107
6.7.1 Application example for the combination of
RSTP and MRP 108
A Readers’ comments 111
B Index 113
C Further support 115

About this Manual
Redundanz L2P
Release 5.0 04/09 5
About this Manual
The “Redundancy Configuration” user manual contains all the information
you need to select a suitable redundancy procedure and configure it.
The “Basic Configuration” user manual contains all 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 instruc-
tions, a description of the display, and all the other information that you need
to install the device before you begin with the configuration of 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.
The "Web-based Interface" reference manual contains detailed information
on using the Web interface to operate the individual functions of the device.
The "Command Line Interface" reference manual contains detailed informa-
tion on using the Command Line Interface to operate the individual functions
of the device.
The Network Management Software HiVision/Industrial HiVision provides
you with additional options for smooth configuration and monitoring:
XConfiguration of multiple devices simultaneously.
XGraphical interface with network layouts.
XAuto-topology discovery.
XEvent log.
XEvent handling.
XClient / Server structure.
XBrowser interface
XActiveX control for SCADA integration
XSNMP/OPC gateway

Key
6Redundanz L2P
Release 5.0 04/09
Key
The designations used in this manual have the following meanings:
Symbols used:
XList
Work step
Subheading
Link Indicates a cross-reference with a stored link
Note: A note emphasizes an important fact or draws your
attention to a dependency.
Courier ASCII representation in user interface
Execution in the Web-based Interface user interface
Execution in the Command Line Interface user interface
Router with firewall
Switch with firewall
Router
Switch
Bridge
Hub

Key
Redundanz L2P
Release 5.0 04/09 7
A random computer
Configuration Computer
Server
PLC -
Programmable logic
controller
I/O -
Robot

Key
8Redundanz L2P
Release 5.0 04/09

Introduction
Redundanz L2P
Release 5.0 04/09 9
1 Introduction
The device contains a range of redundancy functions:
XLink Aggregation
XHIPER-Ring
XMRP-Ring
XFast HIPER-Ring (RSR20, RSR30 and MACH 1000)
XSub-Ring (RSR20, RSR30 and MACH 1000)
XRing/Network Coupling
XRapid Spanning Tree Algorithm (RSTP)

Introduction
10
1.1 Overview of Redundancy Procedure
Redundanz L2P
Release 5.0 04/09
1.1 Overview of
Redundancy Procedure
Note: Informations concerning the switching time you can find on the
Hirschmann internet site (www.hirschmann-ac.com) at the end of the product
site.
Redundancy
procedure
Network topology Switching 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 are being used, up to 39 devices are possible, depending on
the topology (see page 81).
HIPER-Ring Ring typically 80 ms, up to < 500 ms - practically indepen-
dently of the number of devices
MRP-Ring Ring typically 80 ms, up to < 500 ms - practically indepen-
dently of the number of devices
Note: In combination with RSTP in MRP compatibility mode, up to 39 devices
are possible, depending on the configuration. If the default values for RSTP are
being used, up to 19 devices are possible (see page 81).
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 and
MACH 1000)
Ring segment
coupled to basis ring
typically 80 ms, up to < 500 ms - practically indepen-
dently of the number of devices
Redundant
coupling
Coupling of network
segment/rings via a
main line and a
redundant line
typically 150 ms, up to < 500ms
Link
Aggregation
Coupling of network
segments via parallel
active lines with
dynamic load distri-
bution and line
redundancy
Table 1: Comparison of the redundancy procedures

Link Aggregation
Redundanz L2P
Release 5.0 04/09 11
2 Link Aggregation
There is link aggregation when there are at least two parallel redundant con-
nection lines (known as a trunk) between two devices, and these lines are
combined into one logical connection. You can use link aggregation to com-
bine up to 8 (optimally up to 4) connection lines between devices into a trunk.
The LACP (Link Aggregation Control Protocol based on IEEE 802.3ad) is a
network protocol for dynamically bundling physical network connections. The
complete 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 be-
tween the connection lines is effected dynamically.
Any combination of twisted pair and F/O cables can be used as the connec-
tion lines of a trunk. You configure all the connections so that the transmis-
sion speed 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
12
2.1 Example of link aggregation
Redundanz L2P
Release 5.0 04/09
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 between a number of lines, you also get increased redundancy 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 aggrega-
tion. 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
Redundanz L2P
Release 5.0 04/09
2.1 Example of link aggregation
13
2.1.1 Creating and configuring the
link aggregation
Note: A link aggregation always has exactly two devices.
You configure the link aggregation on each of the two devices involved. Dur-
ing the configuration phase, you connect a maximum of one connection line
between the devices. This is to avoid loops.
Under Basic Settings:Port Configuration, you configure all
three connections so that the transmission speed 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 fig. 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
14
2.1 Example of link aggregation
Redundanz L2P
Release 5.0 04/09
Proceed as follows to configure a link aggregation from 3 twisted pair
lines on device 3:
Select the Redundancy:Link Aggregation (see fig. 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 aggrega-
tion that has been set up. Leave the checkmark in the “Enabled”
column while you are using the link aggregation.
Leave the checkmark in the Link Trap column if you want the
device to generate an alarm if all the connections of the link aggre-
gation are interrupted.

Link Aggregation
Redundanz L2P
Release 5.0 04/09
2.1 Example of link aggregation
15
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 fig. 5).

Link Aggregation
16
2.1 Example of link aggregation
Redundanz L2P
Release 5.0 04/09
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

Link Aggregation
Redundanz L2P
Release 5.0 04/09
2.1 Example of link aggregation
17
Now you configure the partner device (device 2) in the same way.
After the configuration, you connect the other connection line(s) between
the devices.
Note: Exclude the combination of a link aggregation with the following
redundancy procedures:
XNetwork/Ring coupling
XMRP-Ring
XFast HIPER-Ring
XSub-Ring

Link Aggregation
18
2.2 HIPER-Ring and link aggregation
Redundanz L2P
Release 5.0 04/09
2.2 HIPER-Ring and
link aggregation
For Power MICE and MACH 4000:
To increase the security on particularly critical connections, you can combine
the HIPER-Ring (see on page 21 „Ring Redundancy“) and link aggregation
redundancy functions.
Figure 6: Example of a HIPER-Ring / link aggregation combination
RM = Ring Manager
A = link aggregation
B = HIPER-Ring
The above example shows a HIPER-Ring. One link aggregation forms a
segment of the ring. When all the connection lines of the link aggregation are
interrupted, the HIPER-Ring function activates the redundant line of the ring.
2 x TP FDX
400 Mbit/s
A
B
RM

Link Aggregation
Redundanz L2P
Release 5.0 04/09
2.2 HIPER-Ring and link aggregation
19
Note: If you want to use a link aggregation in a HIPER-Ring, you first
configure the link aggregation, then the HIPER-Ring. In the HIPER-Ring
dialog, you enter the index of the desired link aggregation as the value for the
module and the port. Make sure that the respective Ring port belongs to the
selected link aggregation.
Note: Deactivate RSTP when link aggregations are segments of a HIPER-
Ring.

Link Aggregation
20
2.2 HIPER-Ring and link aggregation
Redundanz L2P
Release 5.0 04/09