Ether RM Web L2E Rel60 en

Reference Manual
Web-based Interface
Industrial ETHERNET (Gigabit) Switch
RS20/RS30/RS40, MS20/MS30, OCTOPUS
RM Web Technical Support

Release 6.0 07/2010 [email protected]
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.
© 2010Hirschmann 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 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-ac.de).
Printed in Germany
Hirschmann Automation and Control GmbH
Stuttgarter Str. 45-51
72654 Neckartenzlingen
Germany
Tel.: +49 1805 141538
Rel. 6.0 1-01-07/2010 – 14.7.10

Contents
About this Manual 7
Key 9
Opening the Web-based Interface 11
1 Basic Settings 15
1.1 System 16
1.2 Network 21
1.3 Software 23
1.3.1 View the software versions present on the device 23
1.3.2 TFTP Software Update 24
1.3.3 HTTP Software Update 24
1.3.4 Automatic software update by ACA 25
1.4 Port Configuration 26
1.5 Power over ETHERNET 28
1.6 Loading/Saving the Configuration 30
1.6.1 Loading the configuration 31
1.6.2 Saving the Configuration 31
1.6.3 URL 32
1.6.4 Deleting a configuration 32
1.6.5 Using the AutoConfiguration Adapter (ACA) 33
1.6.6 Canceling a configuration change 34
1.7 Restart 36
2 Security 39
2.1 Password / SNMPv3 access 40
2.2 SNMPv1/v2 Access Settings 42
2.3 Telnet/Web Access 45
2.3.1 Description of Telnet Access 46
2.3.2 Description of Web Access 46
2.4 Restricted Management Access 47
2.5 Port Security 50
Contents
3 Time 53
3.1 SNTP configuration 55
3.2 PTP (IEEE 1588) 59
3.2.1 PTP Global (MS20/MS30, PowerMICE, MACH 104,
MACH 1040) 60
3.2.2 PTP Version 1 (MS20/MS30, PowerMICE,
MACH 104, MACH 1040) 64
3.2.3 PTP Version 2 (BC) (MS20/MS30, PowerMICE,
MACH 104, MACH 1040) 66
3.2.4 PTP Version 2 (TC) (MS20/MS30, PowerMICE) 71
4 Switching 75
4.1 Switching Global 76
4.2 Filters for MAC addresses 80
4.3 Rate Limiter 82
4.3.1 Rate Limiter settings 82
4.4 Multicasts 85
4.4.1 IGMP (Internet Group Management Protocol) 85
4.5 VLAN 93
4.5.1 VLAN Global 93
4.5.2 Current VLAN 96
4.5.3 VLAN Static 98
4.5.4 VLAN Port 100
5 QoS/Priority 103
5.1 Global 104
5.2 Port Configuration 107
5.2.1 Entering the port priority 108
5.3 802.1D/p mapping 109
5.4 IP DSCP mapping 111
6 Redundancy 113
6.1 Ring Redundancy 114
6.1.1 Configuring the HIPER-Ring 116
6.1.2 Configuring the MRP-Ring 120
6.2 Ring/Network Coupling 123
6.2.1 Preparing a Ring/Network coupling 123
RM Web
4 Release 6.0 07/2010
Contents
6.3 Spanning Tree 130

6.3.1 Global 132
6.3.2 Port 138
7 Advanced 147
7.1 DHCP Relay Agent 148
7.2 Industrial Protocols 150
7.2.1 PROFINET IO 150
7.2.2 EtherNet/IP 152
7.3 Command Line 153
8 Diagnostics 155
8.1 Syslog 156
8.2 Event Log 161
8.3 Ports 162
8.3.1 Statistics table 162
8.3.2 Utilization 163
8.3.3 SFP modules 164
8.4 Topology Discovery 165
8.5 Port Mirroring 167
8.6 Device Status 169
8.7 Signal contact 172
8.7.1 Manual setting 172
8.7.2 Function monitoring 172
8.7.3 Device status 174
8.7.4 Configuring traps 174
8.8 Alarms (Traps) 176
8.9 Report 179
8.10 IP address conflict detection 181
8.11 Self Test 183
8.12 Service mode 184
8.12.1 Activating the service mode 185
RM Web L2E
Release 6.0 07/2010 5
Contents
8.12.2 Deactivating the service mode 186
A Appendix 189
B Readers’ Comments 197
C Index 199
D Further Support 203
RM Web
6 Release 6.0 07/2010
About this Manual
About this Manual
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

information on using the Command Line Interface to operate the individual
functions of the device.
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 “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 “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 or PROFINET IO.
The Network Management Software HiVision/Industrial HiVision provides

you with additional options for smooth configuration and monitoring:
X Configuration of multiple devices simultaneously.
X Graphical interface with network layouts.
X Auto-topology discovery.
X Event log.
X Event handling.
X Client / Server structure.
X Browser interface
X ActiveX control for SCADA integration
X SNMP/OPC gateway
RM Web L2E
Release 6.0 07/2010 7
About this Manual
RM Web
8 Release 6.0 07/2010
Key
Key
The designations used in this manual have the following meanings:
X List
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
Symbols used:
WLAN access point
Router with firewall
Switch with firewall
Router
Switch
Bridge
RM Web L2E
Release 6.0 07/2010 9
Key
Hub
A random computer
Configuration Computer
Server
PLC -
Programmable logic
controller
I/O -
Robot
RM Web
10 Release 6.0 07/2010
Opening the Web-based Interface
To open the Web-based interface, you need a Web browser (a program that
can read hypertext), for example Mozilla Firefox version 1 or later, or
Microsoft Internet Explorer version 6 or later.
Note: The Web-based interface uses Java software 6 (“Java™ Runtime

Environment Version 1.6.x”).
Install the software from the enclosed CD-ROM. To do this, you go to
“Additional Software”, select Java Runtime Environment and click on
“Installation”.
Figure 1: Installing Java
Start your Web browser.

Check that you have activated JavaScript and Java in your browser
settings.
Establish the connection by entering the IP address of the device which
you want to administer via the Web-based management in the address
field of the Web browser. Enter the address in the following form:
http://xxx.xxx.xxx.xxx
RM Web L2E
Release 6.0 07/2010 11
The login window appears on the screen.
Figure 2: Login window
Select the desired language.

In the drop-down menu "Login", you select
– user, to have read access, or
– admin, to have read and write access
to the device.
The password “public”, with which you have read access for the login
"user", is preset in the password field. If you wish to have write access to
the device, use the login "admin", select the contents of the password field
and overwrite it with the password “private” (default setting).
Click on OK.
The Web site of the device appears on the screen.
RM Web
12 Release 6.0 07/2010
Note: The changes you make in the dialogs will be copied to the device when
you click “Set”. Click “Reload” to update the display.
To save any changes made so that they will be retained after a power cycle
or reboot of the device use the save option on the "Load/Save" dialog (see
on page 30 “Loading/Saving the Configuration“)
Note: You can block your access to the device by entering an incorrect
configuration.
Activating the function “Cancel configuration change” in the “Load/Save”
dialog enables you to return automatically to the last configuration after a set
time period has elapsed. This gives you back your access to the device.
Figure 3: Website of the device with speech-bubble help
RM Web L2E
Release 6.0 07/2010 13
The menu section displays the menu items. By placing the mouse pointer in
the menu section and clicking the alternate mouse button you can use “Back”
to return to a menu item you have already selected, or “Forward” to jump to
a menu item you have already selected.
RM Web
14 Release 6.0 07/2010
Basic Settings
1 Basic Settings
The Basic Settings menu contains the dialogs, displays and tables for the
basic configuration:
X System
X Network
X Software
X Port configuration
X Power over Ethernet
X Load/Save
X Restart
RM Web L2E
Release 6.0 07/2010 15
Basic Settings 1.1 System
1.1 System
The “System“ submenu in the basic settings menu is structured as follows:
X Device Status
X System data
X Device view
X Reloading data
Figure 4: "System" Submenu
Device Status
This section of the website provides information on the device status and
the alarm states the device has detected.
RM Web
16 Release 6.0 07/2010
1 2 3
Figure 5: Device status and display of detected alarms

1 - Symbol indicates the Device Status
2 - Cause of the oldest existing alarm detected
3 - Time of the oldest existing alarm detected
System Data
This area of the website displays the system parameters of the device.
Here you can change
– the system name,
– the location description,
– the name of the contact person for this device,
– the availability of the media modules (see fig. 6)
– the temperature threshold values.
Name Meaning
Name System name of this device
Location Location of this device
Contact The contact for this device
Basic module Hardware version of the device
Media module 1 Hardware version of media module 1
Power supply (P1/P2) Status of power units (P1/P2)
Uptime Time that has elapsed since this device was last restarted.
Temperature Temperature of the device. Lower/upper temperature
threshold values. If the temperature goes outside this range,
the device generates an alarm.
Table 1: System Data
RM Web L2E
Release 6.0 07/2010 17
1 2 3
Figure 6: Availability of the media modules

1 - Module present
2 - Empty slot
3 - Module was removed. Click this check mark to define this slot as an
empty slot.
Device View
The device view shows the device with the current configuration. The
symbols underneath the device view represent the status of the individual
ports.
RM Web
18 Release 6.0 07/2010
Figure 7: Device View
Meaning of the symbols:
The port (10, 100 Mbit/s, 1, 10 Gbit/s) is enabled

and the connection is OK.
The port is disabled by the management

and it has a connection.
The port is disabled by the management

and it has no connection.
The port is in autonegotiation mode.
The port is in HDX mode.
The port is in RSTP discarding mode (100 Mbit/s).
The port is in routing mode (100 Mbit/s).
Updating
This area of the website at the bottom left displays the countdown time
until the applet requests the current data of this dialog again. Clicking the
"Reload" button calls the current dialog information immediately.
The applet polls the current data of the device automatically every
100 seconds.
RM Web L2E
Release 6.0 07/2010 19
Figure 8: Time until update
RM Web
20 Release 6.0 07/2010
Basic Settings 1.2 Network
1.2 Network
With the Basic settings:Network dialog you define the source from
which the device gets its IP parameters after starting, and you assign the IP
parameters and VLAN ID and configure the HiDiscovery access.
Figure 9: Network parameters dialog
Under “Mode”, you enter where the device gets its IP parameters:
X In the BOOTP mode, the configuration is via a BOOTP or DHCP
server on the basis of the MAC address of the device (see on page 30
“Loading/Saving the Configuration“).
X In the DHCP mode, the configuration is via a DHCP server on the
basis of the MAC address or the name of the device (see on page 30
“Loading/Saving the Configuration“).
X In the local mode the network parameters in the device memory are
used.
RM Web L2E
Release 6.0 07/2010 21
Basic Settings 1.2 Network
Enter the parameters on the right according to the selected mode.
You enter the name applicable to the DHCP protocol in the “Name” line in
the system dialog of the Web-based interface.
The “VLAN” frame enables you to assign a VLAN to the agent. If you enter
0 here as the VLAN ID (not included in the VLAN standard version), the
agent will then be accessible from all VLANs.
The HiDiscovery protocol allows you to allocate an IP address to the

device on the basis of its MAC address. Activate the HiDiscovery protocol
if you want to allocate an IP address to the device from your PC with the
enclosed HiDiscovery software (state on delivery: operation “on”, access
“read-write”).
RM Web
22 Release 6.0 07/2010
Basic Settings 1.3 Software
1.3 Software
The software dialog enables you display the software versions in the device
and to carry out a software update of the device via file selection, tftp or ACA.
Figure 10: Software dialog
1.3.1 View the software versions present on the

device
You can view:
X Stored Version
The software version stored in the flash memory.
RM Web L2E
Release 6.0 07/2010 23
X Running Version
The currently loaded software version.
X Backup Version
The previous software version stored in the flash memory.
1.3.2 TFTP Software Update

For a tftp update you need a tftp server on which the software to be loaded
is stored.
The URL identifies the path to the software stored on the tftp server. The URL
is in the format
tftp://IP address of the tftp server/path name/file name
(e.g. tftp://192.168.1.1/device/device.bin).
Click "tftp Update" to load the software from the tftp server to the device.
To start the new software after loading, cold start the device (see on page 36
“Restart“).
1.3.3 HTTP Software Update

For an HTTP software update (via a file selection window), the device
software must be on a data carrier that you can access via a file selection
window from your workstation.
In the file selection frame, click on “...”.
In the file selection window, select the device software (name type: *.bin,
e.g. device.bin) and click on “Open”.
Click on “Update” to transfer the software to the device.
The end of the update is indicated by one of the following messages:
X Update completed successfully.
X Update failed. Reason: incorrect file.
X Update failed. Reason: error when saving.
RM Web
24 Release 6.0 07/2010
X File not found (reason: file name not found or does not exist).
X Connection error (reason: path without file name).
After the update is completed successfully, you activate the new software:
Select the Basic settings: Restart dialog and perform a cold start.
In a cold start, the device reloads the software from the non-volatile
memory, restarts, and performs a self-test.
In your browser, click on “Reload” so that you can access the device again
after it is booted.
1.3.4 Automatic software update by ACA

The device also allows you to perform an automatic software update using
the ACA. You will find the relevant details in the document “Basic
Configuration User”, chapter “Automatic Software Update by ACA”.
RM Web L2E
Release 6.0 07/2010 25
Basic Settings 1.4 Port Configuration
1.4 Port Configuration
This configuration table allows you to configure each port of the device and
also display each port‘s current mode of operation (link state, bit rate (speed)
and duplex mode).
X In the “Name” column, you can enter a name for every port.
X In the “Ports on” column, you can switch on the port by selecting it here.
X In the “Propagate connection error” column, you can specify that a link
alarm will be forwarded to the device status and/or the the signal contact
is to be opened.
X In the “Automatic Configuration” column, you can activate the automatic
selection of the the operating mode (Autonegotiation) and the automatic
assigning of the connections (Auto cable crossing) of a TP port by
selecting the appropriate field. After the autonegotiation has been
switched on, it takes a few seconds for the operating mode to be set.
X In the “Manual Configuration” column, you set the operating mode for this
port. The choice of operating modes depends on the media module. The
possible operating modes are:
– 10 Mbit/s half duplex (HDX),
– 10 Mbit/s full duplex (FDX),
– 100 Mbit/s full duplex (FDX),
– 1000 Mbit/s full duplex (FDX) and
– 10 Gbit/s full duplex (FDX).
X The “Link/Current Operating Mode” column displays the current operating
mode and thereby also an existing connection.
X In the “Cable Crossing (Auto. Conf. off)” column, you assign the
connections of a TP port, if “Automatic Configuration” is deactivated for
this port. The possible settings are:
– enable: the device swaps the send and receive line pairs of the
TP cable for this port (MDIX).
– disable: the device does not swap the send and receive line pairs of
the TP cable for this port (MDI).
– unsupported: the port does not support this function (optical port,
TP SFP port).
X In the “Flow Control” column, you checkmark this port to specify that flow
control is active here. You also activate the global “Flow Control” switch
(see on page 76 “Switching Global“).
RM Web
26 Release 6.0 07/2010
Basic Settings 1.4 Port Configuration
Note: The active automatic configuration has priority over the manual
configuration.
Note: When you are using a redundancy function, you deactivate the flow
control on the participating ports. Default setting: flow control deactivated
globally and activated on all ports.
If the flow control and the redundancy function are active at the same time,
there is a risk of the redundancy failing.
Note: The following settings are required for the ring ports in a HIPER-Ring:
Port Type Bit Rate Autonegotiation Port Setting Duplex

(Automatic Configuration) Mode
Optical all off on full
TX 100 Mbit/s off on full
TX 1000 Mbit/s on on -
Table 2: Port Settings for Ring Ports
When you switch the DIP switch for the ring ports, the device sets the
required settings for the ring ports in the configuration table. The port, which
has been switched from a ring port to a normal port, is given the settings
Autonegotiation (automatic configuration) on and Port on. The settings
remain changeable for all ports.
RM Web L2E
Release 6.0 07/2010 27
Basic Settings 1.5 Power over ETHERNET
1.5 Power over ETHERNET
Devices with Power over ETHERNET (PoE) media modules or PoE ports
enable you to supply current to terminal devices such as IP phones via the
twisted-pair cable. PoE media modules and PoE ports support Power over
ETHERNET according to IEEE 802.3af.
On delivery, the Power over ETHERNET function is activated globally and at
all ports.
Nominal power for MS20/30, MACH 1000 and PowerMICE:

The device provides the nominal power for the sum of all PoE ports plus a
surplus. Because the PoE media module gets its PoE voltage externally, the
device does not know the possible nominal power.
The device therefore assumes a “nominal power” of 60 Watt per PoE media
module for now.
Nominal power for OCTOPUS 8M-PoE:

The device provides the nominal power for the sum of all PoE ports plus a
surplus. Because the device gets its PoE voltage externally, the device does
not know the possible nominal power.
The device therefore assumes a “nominal power” of 15 Watt per PoE port for
now.
With “Function on/off” you turn the PoE on or off.

With “Send Trap” you can get the device to send a trap in the following
cases:
– If a value exceeds/falls below the performance threshold.
– If the PoE supply voltage is switched on/off at at least one port.
Enter the power threshold in “Threshold”. When this value is exceeded/
not achieved, the device will send a trap, provided that “Send trap” is
enabled. For the power threshold you enter the power yielded as a
percentage of the nominal power.
“Nominal Power” displays the power that the device nominally provides
for all PoE ports together.
“Reserved Power” displays the maximum power that the device provides
to all the connected PoE devices together on the basis of their
classification.
“Delivered Power” shows how large the current power requirement is at
all PoE ports.
RM Web
28 Release 6.0 07/2010
Basic Settings 1.5 Power over ETHERNET
The difference between the "nominal" and "reserved" power indicates how
much power is still available to the free PoE ports.
In the “POE on” column, you can enable/disable PoE at this port.
The “Status” column indicates the PoE status of the port.
The “Class” column shows the class of the connected device:
ClassMaximum power delivered
0: 15.4 W = state on delivery
1: 4.0 W
2: 7.0 W
3: 15.4 W
4: Reserved, treat as class 0
The “Name” column indicates the name of the port, see
Basic settings:Port configuration.
Figure 11: Power over Ethernet dialog
RM Web L2E
Release 6.0 07/2010 29
Basic Settings 1.6 Loading/Saving the Configuration
1.6 Loading/Saving the

Configuration
With this dialog you can:

X load a configuration,
X save a configuration,
X enter a URL,
X restore the delivery configuration,
X use the ACA for configuring,
X cancel a configuration change.
Figure 12: Load/Save dialog
RM Web
30 Release 6.0 07/2010
1.6.1 Loading the configuration

In the “Load” frame, you have the option to
X load a configuration saved on the device,

X load a configuration stored under the specified URL,
X load a configuration stored on the specified URL and save it on the
device,
X load a configuration saved on the PC in binary format.
If you change the current configuration (for example, by switching a port off),
the Web-based interface changes the “load/save” symbol in the navigation
tree from a disk symbol to a yellow triangle. After saving the configuration,
the Web-based interface displays the “load/save” symbol as a disk again.
1.6.2 Saving the Configuration

In the “Save” frame, you have the option to
X save the current configuration on the device,

X save the current configuration in binary form in a file under the specified
URL,
X save the current configuration in binary form on the PC,
Note: The loading process started by DHCP/BOOTP (see “Network“ on

page 21) shows the selection of “from URL & save local” in the “Load” frame.
If you get an error message when saving a configuration, this could be due
to an active loading process. DHCP/BOOTP only finishes a loading process
when a valid configuration has been loaded. If DHCP/BOOTP does not find
a valid configuration, finish the loading process by loading the local
configuration in the “Load” frame.
RM Web L2E
Release 6.0 07/2010 31
If you change the current configuration (for example, by switching a port off),
the Web-based interface changes the “load/save” symbol in the navigation
tree from a disk symbol to a yellow triangle. After saving the configuration,
the Web-based interface displays the “load/save” symbol as a disk again.
After you have successfully saved the configuration on the device, the device
sends an alarm (trap) hmConfigurationSavedTrap together with the
information about the AutoConfiguration Adapter (ACA), if one is connected.
When you change the configuration for the first time after saving it, the device
sends a trap hmConfigurationChangedTrap.
1.6.3 URL
The URL identifies the path to the tftp server on which the configuration file
is to be stored. The URL is in the format: tftp://IP address of the tftp server/
path name/file name (e.g. tftp://192.168.1.100/device/
config.dat).
Note: The configuration file includes all configuration data, including the
passwords for accessing the device. Therefore pay attention to the access
rights on the tftp server.
1.6.4 Deleting a configuration

In the "Delete" frame, you have the option to
X Reset the current configuration to the state on delivery. The configuration

saved on the device is retained.
RM Web
32 Release 6.0 07/2010
X Reset the device to the state on delivery. After the next restart, the IP
address is also in the state on delivery.
1.6.5 Using the AutoConfiguration Adapter (ACA)

The ACAs are devices for saving the configuration data of a device. In the
case of a device failure, an ACA enables the configuration data to be
transferred easily by means of a substitute device of the same type.
Note: If you replace a device with DIP switches, please ensure that the DIP
switch settings are identical.
Storing the current configuration data in the ACA:

You have the option of transferring the current device configuration,
including the SNMP password, on the ACA and the flash memory in the
“Save” frame using the “to Switch / Save configuration” option.
Transferring the configuration data from the ACA:

When you restart with the ACA connected, the device adopts the
configuration data of the ACA and saves it permanently in the flash
memory. If the connected ACA does not contain any valid data, for
example, if the delivery state is unchanged, the device loads the data from
the flash memory.
Note: Before loading the configuration data from the ACA, the device
compares the password in the device with the password in the ACA
configuration data.
The device loads the configuration data if

X the admin password matches or
RM Web L2E
Release 6.0 07/2010 33
X there is no password saved locally or

X the local password is the original default password or
X no configuration is saved locally.
Status Meaning
notPresent No ACA present
ok The configuration data from the ACA and the device
match.
removed The ACA was removed after booting.
notInSync - The configuration data of the ACA and the device do
not match or only one file existsa,
or
- no configuration file is present on the ACA or on the
deviceb.
outOfMemory The local configuration data is too extensive to be
stored on the ACA.
wrongMachine The configuration data in the ACA originates from a
different device type and cannot be read or converted.
checksumErr The configuration data is damaged.
Table 3: ACA Status

a. In these cases, the ACA status is identical to the status “ACA not in
sync”, which sends “Not OK” to the signal contacts, and the device
status.
b. In this case, the ACA status (“notInSync”) deviates from the status
“ACA not in sync”, which sends “OK” to the signal contacts, and the
device status.
1.6.6 Canceling a configuration change
Function
If the function is activated and the connection to the device is interrupted
for longer than the time specified in the field “Period to undo while
connection is lost [s]”, the device then loads the last configuration saved.
Activate the function before you configure the device so that you will
then be reconnected if an incorrect configuration interrupts your
connection to the device.
RM Web
34 Release 6.0 07/2010
Enter the “Period to undo while the connection is lost [s]” in seconds.
Possible values: 10-600 seconds.
Default setting: 600 seconds.
Note: Deactivate the function after you have successfully saved the
configuration. In this way you prevent the device from reloading the
configuration after you close the web interface.
Watchdog IP address
“Watchdog IP address” shows you the IP address of the PC from which
you have activated the (watchdog) function. The device monitors the link
to the PC with this IP address, checking for interruptions.
RM Web L2E
Release 6.0 07/2010 35
Basic Settings 1.7 Restart
1.7 Restart
X initiate a cold start of the device. The device reloads the software from the
non-volatile memory, restarts, and performs a self-test.
In your browser, click on “Reload” so that you can access the device again
after it is booted.
X initiate a warm start of the device. In this case the device checks the
software in the volatile memory and restarts. If a warm start is not
possible, a cold start is automatically performed.
X reset the entries with the status “learned” in the filter table (MAC address
table).
X reset the ARP table.
The device maintains an ARP table internally.
If, for example, you assign a new IP address to a computer and
subsequently have problems setting up a connection to the device, you
then reset the ARP table.
X reset the port counters.
X delete the log file.
Note: During the restart, the device temporarily does not transfer any data,
and it cannot be accessed via the Web-based interface or other management
systems such as HiVision.
RM Web
36 Release 6.0 07/2010
Figure 13: Restart Dialog
RM Web L2E
Release 6.0 07/2010 37
RM Web
38 Release 6.0 07/2010
Security 1.7 Restart
2 Security
The “Security” menu contains the dialogs, displays and tables for configuring
the security settings:
X Password/SNMPv3 access
X SNMPv1/v2 access
X Telnet/Web access
X Restricted management access
X Port security
RM Web L2E
Release 6.0 07/2010 39
Security 2.1 Password / SNMPv3 access
2.1 Password / SNMPv3 access
This dialog gives you the option of changing the read and read/write
passwords for access to the device via the Web-based interface, via the CLI,
and via SNMPv3 (SNMP version 3). Please note that passwords are case-
sensitive.
Set different passwords for the read password and the read/write password
so that a user that only has read access (user name “user”) does not know,
or cannot guess, the password for read/write access (user name “admin”).
If you set identical passwords, when you attempt to write this data the device
reports a general error.
The Web-based interface and the user interface (CLI) use the same
passwords as SNMPv3 for the users “admin” and “user”.
Select “Modify read-only password (user)” to enter the read password.

Enter the new read password in the “New password” line and repeat your
entry in the “Please retype” line.
Select “Modify read-write password (admin)” to enter the read/write
password.
Enter the read/write password and repeat your entry.
Figure 14: Dialog Password/SNMP Access
RM Web
40 Release 6.0 07/2010
Security 2.1 Password / SNMPv3 access
Note: If you do not know a password with “read/write” access, you will not
have write access to the device.
Note: For security reasons, the device does not display the passwords.
Make a note of every change. You cannot access the device without a valid
password.
Note: For security reasons, SNMPv3 encrypts the password. With the
“SNMPv1” or “SNMPv2” setting in the dialog Security:SNMPv1/v2
access, the device transfers the password unencrypted, so that this can
also be read.
Note: Use between 5 and 32 characters for the password in SNMPv3, since
many applications do not accept shorter passwords.
Access via a Web browser or Telnet client can be blocked in a separate

dialog (see on page 45 “Telnet/Web Access“).
Access at IP address level is restricted in a separate dialog (see on page 42

“SNMPv1/v2 Access Settings“).
RM Web L2E
Release 6.0 07/2010 41
Security 2.2 SNMPv1/v2 Access Settings
2.2 SNMPv1/v2 Access Settings
With this dialog you can select access via SNMPv1 or SNMPv2. In the state
on delivery, both protocols are activated.
You can thus manage the device with HiVision and communicate with earlier
versions of SNMP.
Note: To be able to read and/or change the data in this dialog, log in to the
Web-based interface with the user name “admin” and the relevant password.
X In the “Index” column, you enter the sequential number to which the
access restriction applies.
X In the “Password” column, you enter the password with which a
management station may access the device via SNMPv1/v2 from the
specified address range. Please note that passwords are case-sensitive.
X In the “IP Address” column, you enter the IP address which may access
the device. No entry in this field, or the entry “0.0.0.0”, allows access to
this device from computers with any IP address. In this case, the only
access protection is the password.
X In the “IP Mask” column, much the same as with netmasks, you have the
option of selecting a group of IP addresses.
Example:
255.255.255.255: a single IP address
255.255.255.240 with IP address = 172.168.23.20:
the IP addresses 172.168.23.16 to 172.168.23.31.
RM Web
42 Release 6.0 07/2010
Binary notation of the mask 255.255.255.240:

1111 1111 1111 1111 1111 1111 1111 0000
mask bits
Binary notation of the IP address 172.168.23.20:
1010 1100 1010 1000 0001 0111 0001 0100
The binary representation of the mask with the IP address yields

an address range of:
1010 1100 1010 1000 0001 0111 0001 0000 bis
1010 1100 1010 1000 0001 0111 0001 1111
i.e.: 172.168.23.16 to 172.168.23.31
X In the “Access Mode” column, you specify whether this computer can
access the device with the read password (access mode “readOnly”) or
with the read/write password (access mode “readWrite”).
Note: The password for the “readOnly” access mode is the same as the
SNMPv3 password for read access. The password for the “readWrite”
access mode is the same as the SNMPv3 password for read/write
access. When you change one of the passwords, the device
automatically synchronizes the corresponding password for SNMPv3
(see on page 40 “Password / SNMPv3 access“).
X You can activate/deactivate this table entry in the “Active” column.
Note: If you have not activated any row, the device does not apply any
access restriction with regard to the IP addresses.
X The “Create entry” button enables you to create a new row in the table.
X With “Delete entry” you delete selected rows in the table.
Note: The row with the password currently in use cannot be deleted or
changed.
RM Web L2E
Release 6.0 07/2010 43
Figure 15: SNMPv1/v2 Access Dialog
RM Web
44 Release 6.0 07/2010
Security 2.3 Telnet/Web Access
2.3 Telnet/Web Access
This dialog allows you to switch off the Telnet server and the Web server on
the device.
Figure 16: Telnet/Web Access dialog
RM Web L2E
Release 6.0 07/2010 45
Security 2.3 Telnet/Web Access
2.3.1 Description of Telnet Access

The Telnet server of the device allows you to configure the device by using
the Command Line Interface (in-band). You can deactivate the Telnet server
if you do not want Telnet access to the device.
On delivery, the server is activated.
After the Telnet server has been deactivated, you will no longer be able to
access the device via a new Telnet connection. If a Telnet connection already
exists, it is kept.
Note: The Command Line Interface (out-of-band) and the

Security:Telnet/Web access dialog in the Web-based interface allow
you to reactivate the Telnet server.
2.3.2 Description of Web Access

The Web server of the device allows you to configure the device by using the
Web-based interface. Deactivate the Web server if you do not want the
device to be accessed from the Web.
On delivery, the server is activated.
After the Web server has been switched off, it is no longer possible to log in
via a Web browser. The login in the open browser window remains active.
Note: The Command Line Interface allows you to reactivate the Web server.
RM Web
46 Release 6.0 07/2010
Security 2.4 Restricted Management Access
2.4 Restricted Management

Access
This dialog allows you to differentiate (restrict) the management access to

the device based on IP address ranges and individual management services.
When you activate this function, you can only use the specified IP address
ranges to access the management services activated for these address
ranges. The device rejects other requests. You can create up to 16 entries in
the list, permit or forbid specific management access for each address range,
and activate or deactivate the individual entries separately.
The following management services support restricted management access:
X http
X snmp
X telnet
Note: The CLI access via the V.24 interface is excluded from the function
and cannot be restricted.
Note: You require the http service to start the Web-based interface in a
browser.
Afterwards, you require the snmp service to access the device with the Web-
based interface. When you start the Web-based interface outside the
browser, you only require snmp.
In the default setting, the restricted management access is deactivated. In

this case, anyone with the correct administrator logon data has access to all
management services.
If you have activated the function, and if there is at least one active entry
whose IP address range matches the request and for which the requested
management service is allowed, the device processes the request.
Otherwise the device rejects it.
RM Web L2E
Release 6.0 07/2010 47
In the state on delivery, the device provides you with a default entry with the
IP address 0.0.0.0, the netmask 0.0.0.0 and all the management services.
This allows access to all services from any IP address. This allows you full
access to the device, even if a restriction is activated, e.g. to initially configure
the function. You have the option to change or delete this entry.
When you create a new entry, this entry also has these preset properties.
Note: If you activate the function and no entry in the table permits your
current access, then you can no longer access the management of the
device once you write these settings to the device.
If no entry allows access, nobody has access to the device management.
In this case, use the CLI access via V.24 to access the management of the
device.
RM Web
48 Release 6.0 07/2010
Variable Meaning Possible values Default setting

Function Switches the function on and On, Off Off
off for the device.
Index Sequential number of the entry. 1 - 16 1 (the preset
When you delete an entry, this entry).
leaves a gap in the numbering.
When you create a new entry
with the Web-based interface,
the device fills the first gap.
IP Address Together with the netmask, Valid IPv4 address or 0.0.0.0 0.0.0.0
defines the network area for (for all newly
which this entry applies. created entries)
Netmask Together with the IP address, Valid IPv4 netmask or 0.0.0.0 0.0.0.0
defines the network area for (for all newly
which this entry applies. created entries)
HTTP Activates or deactivates the On, Off On
http service (Web server) for (for all newly
this entry. created entries)
SNMP Activates or deactivates the On, Off On
SNMP service (SNMP access) (for all newly
for this entry. created entries)
Telnet Activates or deactivates the On, Off On
Telnet service (Telnet access) (for all newly
for this entry. created entries)
SSH Activates or deactivates the On, Off On
SSH service (SSH access) for (for all newly
this entry. created entries)
Active Activates or deactivates the On, Off On
entire entry. (for all newly
created entries)
Table 4: Restricted Management Access
Note: An entry with an IP address of 0.0.0.0 together with a netmask of

0.0.0.0 applies for all IP addresses.
RM Web L2E
Release 6.0 07/2010 49
Security 2.5 Port Security
2.5 Port Security
The device allows you to configure each port so that unauthorized access is
prevented. Depending on your selection, the device checks the MAC
address or the IP address of the connected device.
In the “Configuration” frame, you set whether the port security works with
MAC or with IP addresses.
Name Meaning
MAC-Based Port Security Check source MAC address of the received data packet.
IP-Based Port Security Translate source IP address when entering in MAC address
and then check source MAC address of the received data
packet.
Table 5: Configuration of port security globally for all ports
Set individual parameters for each port in the port table.

Name Meaning
Module Module of the device on which the port is located.
Port Port to which this entry applies.
Port Status enabled: Port is switched on and transmitting.
disabled: Port is switched off and not transmitting.
The port is switched on if
- an authorized address accesses the port
or
- an unauthorized address attempts to access the port and
trapOnly or none is selected under “Action”.
The port is switched off if
- an unauthorized address attempts to access the port and
portDisable is selected under “Action”.
Table 6: Configuration of port security for a single port
RM Web
50 Release 6.0 07/2010
Name Meaning
Allowed MAC Addresses MAC addresses of the devices with which you allow data exchange
at this port.
The Web-based interface allows you to enter up to 10 MAC
addresses, each separated by a space. After each MAC address
you can enter a slash followed by a number identifying an address
area. This number, between 2 and 47, indicates the number of
relevant bits. Example:
00:80:63:01:02:00/40 stands for
00:80:63:01:02:00 to 00:80:63:01:02:FF
or
00:80:63:00:00:00/24 stands for
00:80:63:00:00:00 to 00:80:63:FF:FF:FF
If there is no entry, any number of devices can communicate via this
port.
Current MAC Address Shows the MAC address of the device from which the port last
received data. The Web-based interface allows you to copy an entry
from the “Current MAC Address” column into the “Allowed MAC
Addresses” column by dragging and dropping with the mouse
button.
Allowed IP Addresses IP addresses of the devices with which you allow data exchange at
this port.
The Web-based interface allows you to enter up to 10 IP addresses,
each separated by a space.
If there is no entry, any number of devices can communicate via this
port.
Action Action performed by the device after an unauthorized access:
– none: no action
– trapOnly: send alarm
– portDisable: disable the port with the corresponding entry in
the port configuration table (see on page 26 “Port
Configuration“) and send an alarm.
Table 6: Configuration of port security for a single port
Note: This entry in the port configuration table is part of the configuration
(see on page 30 “Loading/Saving the Configuration“) and is saved together
with the configuration.
Note: Prerequisites for the device to be able to send an alarm (trap) (see on
page 176 “Alarms (Traps)“):
– You have entered at least one recipient
– You have selected at least one recipient in the “Active” column
– In the “Selection” frame, you have selected “Port Security”
RM Web L2E
Release 6.0 07/2010 51
Figure 17: Port Security dialog
Note: The IP port security operates internally on layer 2. The device

internally translates an allowed IP address into an allowed MAC address
when you enter the IP address. An ARP request is used for this.
Prerequisites for the IP-based port security:
– The device with the allowed IP address supports ARP
– The device can be accessed while configuring IP port security
– The MAC address to which the IP address is assigned is unique and
remains unchanged after the IP address is entered.
If you have entered a router interface as the allowed IP address, all the
packets sent from this interface are considered allowed, since they contain
the same MAC source address.
If a connected device sends packets with the allowed IP address but a
different MAC address, it will not be allowed by the Switch. If you exchange
the device with the allowed IP address for a different one with the same IP
address, enter the IP address in the Switch again so that the Switch learns
the new MAC address.
RM Web
52 Release 6.0 07/2010
Time 2.5 Port Security
3 Time
With this dialog you can enter time-related settings independently of the time
synchronization protocol selected.
X The “IEEE/SNTP time” displays the time with reference to Universal Time
Coordinated (UTC).
The time displayed is the same worldwide. Local time differences are not
taken into account.
X The “System time” uses the “IEEE 1588 / SNTP time”, allowing for the
local time difference from “IEEE 1588 / SNTP time”.
“System time” = “IEEE 1588 / SNTP time” + “Local offset”.
X “Time source” displays the source of the following time data. The device
automatically selects the source with the greatest accuracy.
Possible sources are: local and sntp. The source is initially local. If
SNTP is activated and if the device receives a valid SNTP packet, the
device sets its time source to sntp.
With “Set time from PC”, the device takes the PC time as the system time
and calculates the IEEE 1588 / SNTP time using the local time difference.
“IEEE 1588 / SNTP time” = “System time” - “Local offset”
X The “Local Offset” is for displaying/entering the time difference between

the local time and the “IEEE 1588 / SNTP time”.
With “Set offset from PC”, the agent determines the time zone on your PC
and uses it to calculate the local time difference.
Note: When setting the time in zones with summer and winter times, make
an adjustment for the local offset, if applicable. The device can also get the
SNTP server IP address and the local offset from a DHCP server.
RM Web L2E
Release 6.0 07/2010 53
Time 2.5 Port Security
Interaction of PTP and SNTP

According to PTP (IEEE 1588) and SNTP, both protocols can exist in parallel
in the same network. However, since both protocols affect the system time of
the device, situations may occur in which the two protocols compete with
each other.
The PTP reference clock gets its time either via SNTP or from its own clock.
All other clocks favor the PTP time as the source.
Figure 18: Time Dialog
RM Web
54 Release 6.0 07/2010
Time 3.1 SNTP configuration
3.1 SNTP configuration
The Simple Network Time Protocol (SNTP) enables you to synchronize the
system time in your network.
The device supports the SNTP client and the SNTP server function.
The SNTP server makes the UTC (Universal Time Coordinated) available.
UTC is the time relating to the coordinated world time measurement. The
time displayed is the same worldwide. Local time differences are not taken
into account.
The SNTP client obtains the UTC from the SNTP server.
Note: For the most accurate system time distribution possible, only use
network components (routers, switches, hubs) which support SNTP in the
signal path between the SNTP server and the SNTP client.
Parameter Meaning Possible Values Default Setting

Function Switches the SNTP function on and On, Off Off
off globally.
Table 7: Switches SNTP on and off globally

SNTP Status Displays conditions such as “Server - -
cannot be reached”.
Table 8: SNTP Status
RM Web L2E
Release 6.0 07/2010 55
Parameter Meaning Possible ValuesDefault

Setting
Client Status Switches the SNTP client on and off. On, Off On
External server IP address of the SNTP server from which the Valid IPv4 address 0.0.0.0
address device periodically requests the system time.
Redundant IP address of the SNTP server from which the Valid IPv4 address 0.0.0.0
server address device periodically requests the system time if
it does not receive a response to a request
from the “External server address” within 0.5
seconds.
Server request Time interval at which the device requests 1 s - 3,600 s 30 s
interval SNTP packets
Accept SNTP Specifies whether the device accepts the On, Off On
Broadcasts system time from SNTP Broadcast/Multicast
packets that it receives.
Threshold for The device changes the time as soon as the 0 - 2.147.483.647 0
obtaining the deviation from the server time is above this (231-1)
UTC [ms] threshold in milliseconds. This reduces the
frequency of time changes.
Disable client Enable/disable further time synchronizations On, Off Off
after successful once the client, after its activation, has
synchronization synchronized its time with the server.
Note: If you have enabled PTP at the same

time, the SNTP client first collects 60 time
stamps before it deactivates itself. The device
thus determines the drift compensation for its
PTP clock. With the preset server request
interval, this takes about half an hour.
Table 9: Configuration SNTP Client
Note: If you are receiving the system time from an external/redundant server
address, switch off the reception of SNTP Broadcasts (see “Accept SNTP
Broadcasts”). You thus ensure that the device only takes the time from a
defined SNTP server.
RM Web
56 Release 6.0 07/2010
Parameter Meaning Possible Default

Values Setting
Server status Switches the SNTP server on and off. On, Off On
Anycast destination IP address, to which the SNTP server of the Valid IPv4 0.0.0.0
address device sends the SNTP packets (see address
table 11).
VLAN ID VLANs to which the device periodically 1
sends SNTP packets.
Anycast send interval Time interval at which the device sends 1 - 3,600 120
SNTP packets.
Disable Server at Enables/disables the SNTP server function if On, Off Off
local time source the status of the time source is local (see
Time dialog).
Table 10: Configuration SNTP Server
IP destination address Send SNTP packet to

0.0.0.0 Nobody
Unicast address (0.0.0.1 - 223.255.255.254) Unicast address
Multicast address (224.0.0.0 - 239.255.255.254), Multicast address
especially 224.0.1.1 (NTP address)
255.255.255.255 Broadcast address
Table 11: Destination address classes for SNTP packets
RM Web L2E
Release 6.0 07/2010 57
Figure 19: SNTP Dialog
RM Web
58 Release 6.0 07/2010
Time 3.2 PTP (IEEE 1588)
3.2 PTP (IEEE 1588)
Precise time management is required for running time-critical applications via

a LAN.
The IEEE 1588 standard with the Precision Time Protocol (PTP) describes a
procedure that assumes one clock is the most accurate and thus enables
precise synchronization of all clocks in a LAN.
For devices without a real-time (RT) module (module without timestamp

unit):
X enable/disable the PTP function in the PTP dialog.
X select PTP mode in the PTP dialog.
– Select v1-simple-mode if the reference clock uses PTP Version 1.
– Select v2-simple-mode if the reference clock uses PTP Version 2.
The following sections apply to devices with support of real-time (RT)

modules (modules with timestamp unit).
RM Web L2E
Release 6.0 07/2010 59
3.2.1 PTP Global (MS20/MS30, PowerMICE,

MACH 104, MACH 1040)
The table below helps you to select the PTP version and the PTP mode.
Version Mode Reference clock Device with PTP messages

used timestamp
Version 1 v1-simple-mode Version 1 No —
v1-boundary-clock Version 1 Yes Process
Version 2 v2-simple-mode Version 2 No —
v2-boundary-clock- Version 2 Yes Process
onestep
v2-boundary-clock- Version 2 Yes Process
twostep
v2-transparent-clock Version 2 Yes Forward
Table 12: Selecting the PTP version and the PTP mode
The PTP modes

- v1-boundary-clock,
- v2-boundary-clock-onestep,
- v2-boundary-clock-twostep and
- v2-transparent-clock
enable you to optimize the accuracy of the time.
You use these dialogs here
X Version 1
X Version 2 (Boundary Clock, BC)
X Version 2 Transparent Clock, (TC)
The PTP modes
- v1-simple-mode and
- v2-simple-mode
allow you to use the plug-and-play start-up.
RM Web
60 Release 6.0 07/2010

Function on/off Enable/disable the PTP function On, Off
Off
Table 13: Function IEEE 1588/PTP
RM Web L2E
Release 6.0 07/2010 61

PTP version/ Version and mode of the local clock. v1-boundary-
mode Boundary Clock function based on v1-boundary-clock clock
IEEE1588-2002 (PTPv1).
Support for PTPv1 without special v1-simple-mode
hardware. The device synchronizes
itself with received PTPv1
messages. This mode does not
provide any other functions, such as
PTP management or runtime
measuring.
Select this mode if the device does
not have a timestamp unit
(RT module).
Boundary Clock function based on v2-boundary-clock-
IEEE1588-2008 (PTPv2). onestep
The one-step mode determines the
precise PTP time with 1 message.
This mode is available for MM23
and MM33 modules.
Boundary Clock function based on v2-boundary-clock-
IEEE1588-2008 (PTPv2). twostep
The two-step mode determines the
precise PTP time with 2 messages.
Transparent Clock (one-step) v2-transparent-clock
function based on IEEE1588-2008
(PTPv2).
This mode is available for MM23
and MM33 modules.
Support for PTPv2 without special v2-simple-mode
hardware. The device synchronizes
itself with received PTPv2
messages. This mode does not
provide any other functions, such as
PTP management or runtime
measuring.
Select this mode if the device does
not have a timestamp unit
(RT module).
Table 14: Configuration IEEE 1588/PTP
RM Web
62 Release 6.0 07/2010

Bottom Bottom PTP synchronization 0-999.999.999 30
synchronization threshold value, specified in
threshold [ns] nanoseconds. If the result of
(reference time - local time) is lower
than the value of the bottom PTP
synchronization threshold, then the
local clock is deemed as
synchronous with the reference
clock.
Top Top PTP synchronization threshold 31-1.000.000.000 5000
synchronization value, specified in nanoseconds. If
threshold [ns] the result of (reference time - local
time) is greater than the value of the
top PTP synchronization threshold,
then the local clock is deemed as
not being synchronous with the
reference clock.
Table 14: Configuration IEEE 1588/PTP

Is synchronized Local clock synchronized with true
reference clock; compare Bottom false
synchronization threshold
and Top synchronization
threshold.
Max Offset Total deviation of the local clock
absolute [ns] from the reference clock in
nanoseconds since the local clock
was last reset. The local clock is
reset with “Reinitialize” in this dialog
or by resetting the device.
Table 15: IEEE 1588/PTPStatus
RM Web L2E
Release 6.0 07/2010 63
3.2.2 PTP Version 1 (MS20/MS30, PowerMICE,

MACH 104, MACH 1040)
You select the PTP version you will use in the Time:PTP:Global dialog.
PTP Version 1, Global Settings

Sync Interval Period for sending synchronization - sec-1 sec-2
messages. - sec-2
Entered in seconds. - sec-8
- sec-16
- sec-64
Subdomain Name of the PTP subdomain to 1 to 16 ASCII _DFLT
name which the local clock belongs. characters, hex value
0x21 (!) through 0x7e
(~)
Preferred Defines the local clock as the true false
Master preferred master. If PTP does not false
find another preferred master, then
the local clock is used as the
grandmaster clock. If PTP finds
other preferred masters, then PTP
determines which of the preferred
masters is used as the grandmaster
clock.
Table 16: Function IEEE 1588/PTPv1

Offset to Master Deviation of the local clock from the
[ns] reference clock in nanoseconds.
Runtime to Single signal runtime between the
Master [ns] local device and reference clock in
nanoseconds.
Grandmaster MAC address of the grandmaster
UUID clock (Unique Universal Identifier).
Parent UUID MAC address of the master clock
with which the local time is directly
synchronized.
Clock Stratum Qualification of the local clock.
Clock identifier Clock properties (e.g accuracy,
epoch, etc.).
Table 17: Status IEEE 1588/PTPv1
RM Web
64 Release 6.0 07/2010
PTP Version 1, Port Settings

Module Module number
for modular devices, otherwise 1.
The table remains empty if the
device does not support the PTP
mode selected
PTP on Port sends/receives PTP on on
synchronization messages
Port blocks PTP synchronization off
messages.
PTP Burst on 2 to 8 synchronization runs take on off
place during the synchronization
interval. This enables faster
synchronization with a
correspondingly higher network
load.
One synchronization run is off
performed in a synchronization
interval.
PTP Status Port is in the initialization phase. initializing
A PTP protocol error was detected faulty
on this port.
PTP function is switched off at this disabled
port.
Port has not received any listening
information and is waiting for
synchronization messages.
Port is in PTP pre-master mode. pre-master
Port is in PTP master mode. master
Port is in PTP passive mode. passive
Port is in PTP uncalibrated mode. uncalibrated
Port is in PTP slave mode. slave
Table 18: Port dialog version 1
RM Web L2E
Release 6.0 07/2010 65
3.2.3 PTP Version 2 (BC) (MS20/MS30,

PowerMICE, MACH 104, MACH 1040)
PTP version 2 provides considerably more settings. These support
- faster reconfiguration of the PTP network than in PTP version 1
- greater precision in some environments.
Global

Priority 1 The clock with the lowest priority 1 0-255 128
becomes the reference clock
(grandmaster).
Priority 2 If all the relevant values for selecting 0-255 128
the reference clock are the same for
multiple devices, the clock with the
lowest priority 2 is selected as the
reference clock (grandmaster).
Domain number Assignment of the clock to a PTPv2 0-255 0
domain. Only clocks with the same
domain are synchronized.
Table 19: Function IEEE 1588/PTPv2 BC

Two Step Displays the clock mode of the No
device
v2-boundary-clock-onestep No
v2-boundary-clock-twostep Yes
Number of BCs Number of boundary clocks
to grandmaster between PTP reference clock and
this device
Offset to Master Deviation of the local clock from the
[ns] reference clock in nanoseconds.
Runtime to Single signal runtime between the
Master [ns] local device and the reference clock
in nanoseconds. The display
depends on the port setting
“Runtime measuring mechanism”.
Table 20: Status IEEE 1588/PTPv2 BC
RM Web
66 Release 6.0 07/2010

Clock identifier Own UUID (unique identification
number)
Parent port UUID of the direct master
identifier
Grandmaster UUID of the reference clock
identifier
Table 21: Identifiers

Priority 1 Display priority 1 of the current
reference clock.
Priority 2 Display priority 2 of the current
reference clock.
Class Class of the reference clock
Precision Estimated accuracy with regard to
UTC
Variance Variance as described in the
IEEE1588-2008 standard
Table 22: Grandmaster (reference clock)
RM Web L2E
Release 6.0 07/2010 67

Time source Source selected for own clock. atomicClock internalOsci
gps llator
terrestrialRadio
ptp
ntp
handset
other
internalOscillat
or
UTC Offset [s] Current difference between the PTP -2,147,483,648 to 34
time scale (see below) and the UTC. 2,147,483,647
UTC Offset valid Specifies whether value of UTC Yes, No No
offset is valid or not.
Time Traceable The device gets the time from a Yes, No
primary UTC reference, e.g. from an
NTP server.
Frequency The device gets the frequency from Yes, No
Traceable a primary UTC reference, e.g. NTP
server, GPS.
PTP Time Scale The device uses the PTP time scale. Yes, No
According to IEEE 1588, the PTP
time scale is the TAI atomic time
started on January 01, 1970. In
contrast to UTC, TAI does not use
leap seconds On January 01, 2010,
the difference between TAI and
UTC was +34 seconds.
Table 23: Properties of the Local Time
RM Web
68 Release 6.0 07/2010
Port

If the device does not support the
PTP mode selected, the table is
empty.
messages.
PTP Status Port is in the initialization phase. initializing
A PTP protocol error was detected faulty
on this port.
PTP function is switched off at this disabled
port.
Port has not received any listening
information and is waiting for
synchronization messages.
Port is in PTP pre-master mode. pre-master
Port is in PTP master mode. master
Port is in PTP uncalibrated mode. uncalibrated
Port is in PTP passive mode. passive
Port is in PTP slave mode. slave
E2E Runtime Displays in seconds the interval for 8
Measuring E2E (End-to-End) runtime
Interval measurements at this port. This is a
value for the device, assigned to
ports with the PTP status Slave by
the connected master. If the port
itself is the master, then the device
assigns the port the value 8 (state
on delivery).
P2P Runtime Measured P2P (Peer-to-Peer)
runtime. Prerequisite: you have
selected the P2P runtime measuring
mechanism.
Announce Interval of the messages for PTP 1, 2, 4, 8, 16 2
Interval topology discovery (selection of the
reference clock).
Select the same value for all devices
within a PTP domain.
Table 24: Port Dialog Version 2(BC)
RM Web L2E
Release 6.0 07/2010 69

Announce Announce interval timeout for PTP 2-10 3
Timeout topology discovery in number of
announce intervals.
The standard settings of announce
interval = 2 (2 per second) and
announce timeout = 3 lead to a
timeout of 3 x 2 seconds =
6 seconds.
Select the same value for all devices
within a PTP domain.
Sync Interval Interval in seconds for the 0.5; 1; 2 1
Runtime Mechanism for measuring the
Measuring message runtime.
Mechanism Enter the same mechanism for the
PTP device connected to this port.
The device itself does not generate E2E (End-to-End):
any messages in the runtime
measurement. A connected PTP
slave measures the runtime of the
entire transmission path to the
master.
The device itself measures the P2P (Peer-to-Peer)
runtime to all the connected PTP
devices. If a reconfiguration is
performed, this eliminates the need
to determine the runtime again.
The MICE media modules MM23
and MM33 support the P2P
mechanism.
No runtime determination. Disabled
P2P Runtime Interval for peer-to-peer runtime
Measuring measurements at this port.
Interval Prerequisite:
You have selected the P2P runtime
measuring mechanism on the
device itself and on the connected
PTP device.
Network Transport protocol for PTP 802.3 Ethernet, UDP/IPv4
Protocol messages. UDP/IPv4
RM Web
70 Release 6.0 07/2010

V1 Hardware Some devices from other auto, on, off auto
Compatibility manufacturers require PTP
messages of specific length.
If the UDP/IPv4 network protocol is
selected and the function is active,
the device extends the PTP
messages.
Asymmetry Correction of the runtime asymmetry
in ns. A runtime measurement value
of x ns corrupted by asymmetrical
transmission values corresponds to
an asymmetry of x·2 ns
3.2.4 PTP Version 2 (TC) (MS20/MS30,

PowerMICE)
In strongly cascaded networks in particular, the transparent clock (TC)
introduced in PTP Version 2 provides a noticeable increase in precision.
The combination with the P2P runtime mechanism (simultaneous runtime
measurement at all ports) enables “seamless” reconfiguration.
The following settings enable you to also use the TC for Unicast PTP
messages:
– Selecting the E2E mechanism
– Syntonize disabled
– PTP Management disabled.
RM Web L2E
Release 6.0 07/2010 71
PTP Version 2 (TC), Global Settings

Runtime Mechanism for measuring the
Measuring message runtime.
Mechanism Enter the same mechanism for the
PTP device connected to this port.
The device itself does not generate E2E (End-to-End):
any messages in the runtime
measurement. A connected PTP
slave measures the runtime of the
entire transmission path to the
master.
The device itself measures the P2P (peer-to-peer)
runtime to all the connected PTP
devices. If a reconfiguration is
performed, this eliminates the need
to determine the runtime again.
Primary Domain Assignment of the 0-225
clock to a PTPv2
domain.
Multi Domain TC corrects messages from all Yes Yes
Mode domains.
TC only corrects messages from the No
primary domain.
Network Network protocol for P2P and udplpv4 udplpv4
Protocol management messages. ieee8023
Syntonize Synchronize frequency. Yes No
No
PTP Activate/deactivate the PTP Yes Yes
Management management. No
To reduce the load on the device,
deactivate PTP Management and
Syntonize
- at high synchronization rates and
- in Unicast mode.
Table 25: Function IEEE 1588 / PTPv2 TC

Clock identifier UUID of the TC (transparent clock)
Current master If Syntonize is enabled, displays the
UUID of the master with which the
device synchronizes its frequency.
Table 26: Status IEEE 1588 / PTPv2 TC
RM Web
72 Release 6.0 07/2010
PTP Version 2 (TC), Port Settings

If the device does not support the
PTP mode selected, the table is
empty.
messages. The device does not
process any PTP messages it
receives at this port.
P2P Runtime Interval for peer-to-peer runtime
Measuring measurements at this port.
Interval Prerequisite:
You have selected the P2P runtime
measuring mechanism on the
device itself and on the connected
PTP device.
P2P Runtime Measured P2P (Peer-to-Peer)
runtime. Prerequisite: you have
selected the P2P runtime
measuring mechanism.
Asymmetry Correction of the runtime
asymmetry in ns. A runtime
measurement value of x ns
corrupted by asymmetrical
transmission values corresponds to
an asymmetry of x·2 ns
Table 27: Port Dialog Version 2(TC)
RM Web L2E
Release 6.0 07/2010 73
RM Web
74 Release 6.0 07/2010
Switching 3.2 PTP (IEEE 1588)
4 Switching
The switching menu contains the dialogs, displays and tables for configuring
the switching settings:
X Switching Global
X Filters for MAC Addresses
X Rate Limiter
X Multicasts
X VLAN
RM Web L2E
Release 6.0 07/2010 75
Switching 4.1 Switching Global
4.1 Switching Global
Variable Meaning Possible Values

MAC address Display the MAC address of the device
(read only)
Aging Time (s) Enter the Aging Time in seconds for 15-3.825 30
dynamic MAC address entries.
In connection with the router redundancy,
select a time ≥ 30 s.
Flow control Activate/deactivate the flow control On, Off Off
Note: When you are using a redundancy

function, you deactivate the flow control
on the participating ports. Default setting:
flow control deactivated globally and
activated on all ports.
If the flow control and the redundancy
function are active at the same time, there
is a risk of the redundancy failing.
Learning Activate/deactivate the learning of MAC On, Off On
addresses source addresses.
Frame size Set the maximum packet size (frame size) 1522, 1632 1522
in bytes.
Activate Enable/disable whether the device On, Off Off
Address detects whether it has repeatedly learned
Relearn the same MAC source addresses at
Detection different ports. This process very probably
indicates a loop situation in the network.
If the device detects this process, it
creates an entry in the log file and sends
an alarm (trap).
Table 28: Switching:Global dialog
RM Web
76 Release 6.0 07/2010
Variable Meaning Possible Values

Address Number of MAC addresses that are 1 - 1,024 1
Relearn learned at different ports within a checking
Threshold interval, so that if this number is
exceeded, the device sees this as a
relevant event. The interval for this check
is a few seconds.
Activate Duplex Enable/disable whether the device reports On, Off Off
Mismatch a duplex problem at a port for specific
Detection error events. This means that the duplex
mode of the port might not match that of
the remote port. If the device detects a
potential non-match, it creates an entry in
the event log and sends an alarm (trap).
To detect potential non-matches, the
device evaluates the error counters of the
port after the connection is set up, in the
context of the port settings (see table 29).
Table 28: Switching:Global dialog
The following table lists the duplex operating modes for TX ports together
with the possible error events. The terms in the table mean:
X Collisions: In half-duplex mode, collisions mean normal operation.
X Duplex problem: Duplex modes do not match.
X EMI: Electromagnetic interference.
X Network extension: The network extension too great, or too many hubs
are cascaded.
RM Web L2E
Release 6.0 07/2010 77
X Collisions, late collisions: In full-duplex mode, the port does not count
collisions or late collisions.
X CRC error: The device only evaluates these errors as duplex problems in
the manual full duplex mode.
No. Autonegotiati Current Detected error Evaluation of Possible causes

on duplex events (≥ 10) duplex
mode situation by
device
1 On Half duplex None OK
2 On Half duplex Collisions OK
3 On Half duplex Late collisions Duplex problem Duplex problem, EMI,
detected network extension
4 On Half duplex CRC error OK EMI
5 On Full duplex None OK
6 On Full duplex Collisions OK EMI
7 On Full duplex Late collisions OK EMI
8 On Full duplex CRC error OK EMI
9 Off Half duplex None OK
10 Off Half duplex Collisions OK
11 Off Half duplex Late collisions Duplex problem Duplex problem, EMI,
detected network extension
12 Off Half duplex CRC error OK EMI
13 Off Full duplex None OK
14 Off Full duplex Collisions OK EMI
15 Off Full duplex Late collisions OK EMI
16 Off Full duplex CRC error Duplex problem Duplex problem, EMI
detected
Table 29: Evaluation of non-matching of the duplex mode
RM Web
78 Release 6.0 07/2010
Figure 20: Dialog Switching Global
RM Web L2E
Release 6.0 07/2010 79
Switching 4.2 Filters for MAC addresses
4.2 Filters for MAC addresses
The filter table for MAC addresses is used to display and edit filters. Each row
represents one filter. Filters specify the way in which data packets are sent.
They are set automatically by the device (learned status) or manually. Data
packets whose destination address is entered in the table are sent from the
receiving port to the ports marked in the table. Data packets whose
destination address is not in the table are sent from the receiving port to all
other ports. The following conditions are possible:
X learned: The filter was created automatically by the device.
X invalid: With this status you delete a manually created filter.
X permanent: The filter is stored permanently in the device or on the URL
(see on page 30 “Loading/Saving the Configuration“).
X igmp: The filter was created by IGMP Snooping.
In the “Create” dialog (see buttons below), you can create new filters.
Figure 21: Filter Table dialog
RM Web
80 Release 6.0 07/2010
Switching 4.2 Filters for MAC addresses
Note: For Unicast addresses, the device allows you to include one or no
ports in a filter entry. Do not include any ports if you want to create a discard
filter entry.
Note: This filter table allows you to create up to 100 filter entries for Multicast
addresses.
RM Web L2E
Release 6.0 07/2010 81
Switching 4.3 Rate Limiter
4.3 Rate Limiter
The device can limit the rate of message traffic during periods of heavy traffic
flow.
Entering a limit rate for each port specifies the amount of traffic the device is
permitted to transmit and receive.
If the data load transmitted at this port exceeds the maximum load entered,
the device will discard the excess data at this port.
A global setting enables/disables the rate limiter function at all ports.
Note: The limiter functions work exclusively on layer 2 and serve the purpose
of limiting the effects of storms of those frame types (typically broadcasts)
that the Switch floods. The limiter function ignores any protocol information
of higher layers like IP or TCP. This may affect e.g., TCP traffic.
You can minimize this effects by:
X applying the limiter function only to particular frame types (e.g., to
broadcasts, multicasts and unicasts with an unlearned destination
address) and excluding unicasts with a learned destination address from
the limitation,
X using the egress limiter function instead of the ingress limiter function
because the former cooperates slightly better with TCP‘s flow control
(reason: frames buffered by the internal switching buffer),
X increasing the aging time for learned unicast destination addresses.
4.3.1 Rate Limiter settings

X "Ingress Limiter (kbit/s)" allows you to enable or disable the input limiting
function for all ports.
RM Web
82 Release 6.0 07/2010
X "Egress Limiter (Pkt/s)" allows you to enable or disable the broadcast

output limiter function at all ports.
X "Egress Limiter (kbit/s)" allows you to enable or disable the output limiter
function for all packet types at all ports.
Setting options per port:

X "Ingress Packet Types" allows you to select the packet type for which the
limit is to apply:
X All, limits the total inbound data volume at this port.
X BC, limits the broadcast packets received at this port.
X BC + MC, limits broadcast packets and Multicast packets received at
this port.
X BC + MC + uUC, limits broadcast packets, Multicast packets, and
unknown Unicast packets received at this port.
X Ingress Limiter Rate for the inbound packet type selected:
X = 0, no ingress limit at this port.
X > 0, maximum inbound traffic rate in kbit/s that can be received at this
port.
X Egress Limiter Rate for broadcast packets:
X = 0, no rate limit for outbound broadcast packets at this port.
X > 0, maximum number of outbound broadcasts per second that can be
sent at this port.
X Egress Limiter Rate for the entire data stream:
X = 0, no rate limit for outbound data stream at this port.
X > 0, maximum outbound transmission rate in kbit/s sent at this port.
RM Web L2E
Release 6.0 07/2010 83
Figure 22: Rate Limiter Dialog
RM Web
84 Release 6.0 07/2010
Switching 4.4 Multicasts
4.4 Multicasts
4.4.1 IGMP (Internet Group Management Protocol)

With this dialog you can
X activate/deactivate the IGMP Snooping protocol,
X configure the IGMP Snooping protocol globally and per port.
Figure 23: IGMP Snooping dialog
Operation
In this frame you can:
RM Web L2E
Release 6.0 07/2010 85
X activate/deactivate the IGMP Snooping protocol.
Parameter Meaning Value range Default setting

Function Activate/deactivate IGMP Snooping On, Off Off
globally for the device.
If IGMP Snooping is switched off:
X the device does not evaluate
Query and Report packets
received, and
X it sends (floods) received data
packets with a Multicast address
as the destination address to all
ports.
Table 30: IGMP Snooping, global function
IGMP Querier and IGMP Settings

With these frames you can enter global settings for the IGMP settings and
the IGMP Querier function.
Prerequisite: The IGMP Snooping function is activated globally.
RM Web
86 Release 6.0 07/2010

IGMP Querier
IGMP Querier Switch query function on/off on/off off
enabled
Protocol Version Select IGMP version 1, 2 or 3. 1, 2, 3 2
Send Interval Enter the interval at which the switch 2-3599 sa 125 s
sends query packets.
All IGMP-capable terminal devices
respond to a query with a report
message, thus generating a network
load.
IGMP settings
Current querier IP
Display the IP address of the router/
address switch that contains the query function.
Max. Response Enter the time within which the Protocol Version 10 s
Time Multicast group members respond to a - 1,2: 1-25 sa
query. - 3: 1-3598 sa
The Multicast group members select
random values within the response
time for their response, so that all the
Multicast group members do not
respond to the query at the same time.
Group Membership Enter the period for which a dynamic 3-3600 sa 260 s
Interval Multicast group remains entered in the
device if it does not receive any report
messages.
Table 31: IGMP Querier and IGMP settings

a.) Note the connection between the parameters Max. Response Time,
Send Interval and Group Membership Interval, (see table 32)
The parameters
– Max. Response Time,
– Send Interval and
– Group Membership Interval
have a relationship to each other:
Max. Response Time < Send Interval < Group Membership
Interval.
If you enter values that contradict this relationship, the device then
replaces these values with a default value or with the last valid values.
RM Web L2E
Release 6.0 07/2010 87
Parameter Protocol Value range Default setting

Version
Max. Response Time, 1, 2 1-25 seconds 10 seconds
3 1-3,598 seconds
Send Interval 1, 2, 3 2-3,599 seconds 125 seconds
Group Membership Interval 1, 2, 3 3-3,600 seconds 260 seconds
Table 32: Value range for

- Max. Response Time
- Send Interval
- Group Membership Interval
For “Send Interval” and “Max. Response Time”,

– select a large value if you want to reduce the load on your network and
can accept the resulting longer switching times,
– select a small value if you require short switching times and can accept
the resulting network load.
Multicasts
In this frame you specify how the device transmits packets with
X unknown MAC/IP Multicast address not learned with IGMP Snooping
X known MAC/IP Multicast address learned with IGMP Snooping.
Prerequisite: The IGMP Snooping function is activated globally.
RM Web
88 Release 6.0 07/2010

Unknown Multicasts
X Send to Query Ports: Send to Query Send to All
The device sends the packets Ports, Send to Ports
with an unknown MAC/IP All Ports,
Multicast address to all query Discard
ports.
X Send to All Ports:
The device sends the packets
with an unknown MAC/IP
Multicast address to all ports.
X Discard:
The device discards all packets
with an unknown MAC/IP
Multicast address.
Known Multicasts
X Send to query and Send to query Send to
registered ports: and registered registered ports
The device sends the packets ports, send to
with a known MAC/IP Multicast registered
address to all query ports and ports
to registered ports.
The advantage of this is that it
works in most applications
without any additional
configuration.
Application:
“Flood and Prune” routing in
PIM-DM.
X Send to registered ports:
The device sends the packets
with a known MAC/IP Multicast
address to registered ports.
The advantage of this setting is
that it uses the available
bandwidth optimally through
direct distribution. It requires
additional port settings.
Application:
Routing protocol PIM-SM.
Table 33: Known and unknown Multicasts
Note: The way in which unlearned Multicast addresses are handled

also applies to the reserved addresses from the “Local Network Control
Block” (224.0.0.0 - 224.0.0.255). This can have an effect on higher-level
routing protocols.
RM Web L2E
Release 6.0 07/2010 89
Settings per Port (Table)

With this configuration table you can enter port-related IGMP settings.
RM Web
90 Release 6.0 07/2010

Port Module and port numbers to which this - -
entry applies.
IGMP Snooping on Switch IGMP on/off for each port. on, off on
Switching IGMP off at a port prevents
registration for this port.
Prerequisite: In the
Switching:Multicasts:IGMP
dialog, IGMP is enabled.
IGMP Forward All Switch the IGMP Snooping function on, off off
“Forward All” on/off.
With the IGMP Forward All setting,
the device sends to this port all data
packets with a Multicast address in the
destination address field.
Note: If a number of routers are

connected to a subnetwork, you must
use IGMP version 1 so that all the
routers receive all the IGMP reports.
Note: If you use IGMP version 1 in a

subnetwork, then you must also use
IGMP version 1 in the entire network.
IGMP Automatic Displays which ports the device has yes, no -
Query Port learned as query ports if automatic is
selected in “Static Query Port”.
Prerequisite: The IGMP Snooping
function is activated globally.
Static Query Port The device sends IGMP report enable, disable
messages to the ports at which it disable,
receives IGMP queries (default automatic
setting). This column allows you to also
send IGMP report messages to: other
selected ports (enable) or connected
Hirschmann devices (automatic).
Prerequisite: The IGMP Snooping
function is activated globally.
Learned Query Shows at which ports the device has yes, no -
Port received IGMP queries if “disable” is
selected in “Static Query Port”.
Table 34: Settings per port
RM Web L2E
Release 6.0 07/2010 91
Note: If the device is incorporated into a HIPER-Ring, you can use the
following settings to quickly reconfigure the network for data packets with
registered Multicast destination addresses after the ring is switched:
X Switch on the IGMP Snooping on the ring ports and globally, and
X activate “IGMP Forward All” per port on the ring ports.
RM Web
92 Release 6.0 07/2010
Switching 4.5 VLAN
4.5 VLAN
VLAN contains dialogs and attributes for configuring and monitoring the
VLAN function in accordance with the IEEE 802.1Q standard.
4.5.1 VLAN Global

X display VLAN parameters
X activate/deactivate the VLAN 0 transparent mode
X configure and display the learning mode
X reset the VLAN settings of the device to the original defaults.
Parameter Meaning
Max. VLAN ID Displays the largest possible VLAN ID (see on page 98 “VLAN Static“).
Max. supported Displays the maximum number of VLANs the device supports (see on
VLANs page 98 “VLAN Static“).
Number of VLANs Displays the number of configured VLANs (see on page 98 “VLAN Static“).
Table 35: VLAN display
Note: The device provides the VLAN with the ID 1. The VLAN with ID 1 is
always present.
RM Web L2E
Release 6.0 07/2010 93
Switching 4.5 VLAN

VLAN 0 When the VLAN 0 Transparent Mode On, Off Off
Transparent Mode is activated, the device accepts a
VLAN ID of 0 in the packet when it
receives it, regardless of the setting for
the port VLAN ID in the dialog (see on
page 100 “VLAN Port“).
Activate “VLAN 0 Transparent Mode”
to transmit packets with a priority TAG
without VLAN membership, i.e. with a
VLAN ID of 0.
Table 36: VLAN settings
Note: If you are using the GOOSE protocol in accordance with IEC61850-8-
1, you activate the “VLAN 0 transparent mode”. Thus the prioritizing
information remains in the data packet in accordance with IEEE802.1D/p
even when the device forwards the data packet.
This also applies to other protocols that use this prioritizing in accordance
with IEEE802.1D/p but that do not require any VLANs in accordance with
IEEE802.1Q.
Note: When using the “Transparent Mode” in this way, note the following:
X For RS20/RS30/RS40, MS20/MS30, RSR20/RSR30, MACH 100,
MACH 1000 and OCTOPUS:
In “Transparent mode”, the devices ignore the port VLAN ID set. Set the
VLAN membership of the ports of VLAN 1 to U (Untagged) or T (Tagged),
(see on page 98 “VLAN Static“).
RM Web
94 Release 6.0 07/2010
Switching 4.5 VLAN

Mode VLAN mode selection. Independent Independent
"Independent VLAN“ subdivides the VLAN, VLAN
forwarding database (see on page 80 “Filters Shared VLAN
for MAC addresses“) virtually into one
independent forwarding database per VLAN.
The device cannot assign data packets with a
destination address in another VLAN, and so
floods it to all ports of the VLAN.
Application area: Setting up identical
networks that use the same MAC addresses.
"Shared VLAN“ uses the same forwarding
database for all VLANs (see on page 80
“Filters for MAC addresses“). The device
cannot assign data packets with a destination
address in another VLAN, and so only
forwards them to the destination port if the
receiving port is also a member of the VLAN
group of the destination port.
Application area: In the case of overlapping
groups, the device can distribute directly
across VLANs, as long as the ports involved
belong to a VLAN that can be reached.
Changes to the mode are only taken over
after a warm start (see on page 36 “Restart“)
is performed on the device, and the changes
are then displayed in the line below under
“Status”.
Status Displays the current status. After a warm start Independent
(see on page 36 “Restart“) on the device, the VLAN,
device take the setting for the “Mode” into the Shared VLAN
status line.
Table 37: Settings and displays in the “Learning” frame
RM Web L2E
Release 6.0 07/2010 95
Switching 4.5 VLAN
Figure 24: VLAN Global dialog
4.5.2 Current VLAN

X display VLAN parameters
The Current VLAN table shows all

– manually configured VLANs
– VLANs configured via redundancy mechanisms
The Current VLAN table is only used for information purposes. You can make
changes to the entries in the VLAN:Static dialog.
RM Web
96 Release 6.0 07/2010
Switching 4.5 VLAN
Parameter Meaning Value range

VLAN ID Displays the ID of the VLAN.
Status Displays the VLAN status. other: This entry solely appears for
VLAN 1. The system provides VLAN 1.
VLAN 1 is always present.
permanent: A static entry made by you.
This entry is kept when the device is
restarted.
dynamic: This VLAN was created
dynamically via GVRP.
Time created Operating time (see “System
Data“) at which the VLAN was
created.
Ports x.x VLAN membership of the - Currently not a member
relevant port and handling of T Member of VLAN; send data packets with
the VLAN tag. tag.
U Member of the VLAN; send data packets
without tag (untagged).
F Membership forbidden, so no entry
possible via GVRP either.
Table 38: Current VLAN
Figure 25: Current VLAN dialog
RM Web L2E
Release 6.0 07/2010 97
Switching 4.5 VLAN
4.5.3 VLAN Static

X Create VLANs
X Assign names to VLANs
X Assign ports to VLANs and configure them
X Delete VLANs

VLAN ID Displays the ID of up to 255 1-4.042
VLANs that are simultaneously
possible.
Name Enter the name of your choice Maximum 32 characters VLAN 1: default
for this VLAN.
Status Displays the VLAN status. active: Entry is active
activated
notInService: Entry is
deactivated
Ports x.x Select the membership of the -: currently not a VLAN 1: U,
ports to the VLANs. member (GVRP new VLANs: -
allowed).
T: Member of the VLAN;
send data packets with
tag (tagged).
U: Member of the VLAN;
send data packets
without tag (untagged).
F: Membership
forbidden, so no entry
possible via GVRP
either.
Table 39: VLAN Static dialog
RM Web
98 Release 6.0 07/2010
Switching 4.5 VLAN
Figure 26: VLAN Static Dialog
Note: When configuring the VLAN, the management station must maintain
access to the device after the VLAN configuration is saved.
You achieve this by connecting the management station to a port with the
VLAN ID 1. The device transmits the data of the management station in
VLAN 1.
Note: The device automatically creates VLANs for MRP rings. The MRP ring
function prevents the deletion of these VLANs.
Note: Note the tagging settings for ports (see table 40) that are part of a
redundant Ring or the Ring/network coupling.
RM Web L2E
Release 6.0 07/2010 99
Switching 4.5 VLAN
Redundancy VLAN membership

HIPER-Ring VLAN 1 U
MRP-Ring any
Ring/Network coupling VLAN 1 U
Table 40: Required VLAN settings of ports that are part of redundant Rings or Ring/
Network coupling.
Note: In a redundant ring with VLANs, you should only operate devices
whose software version supports VLANs:
X RS2 xx/xx (from rel. 7.00)
X RS2-16M
X RS20, RS30, RS40 (with software variants L2E, L2P)
X MICE (from rel. 3.0)
X PowerMICE
X MS20, MS30
X RSR20, RSR30
X MACH 100
X MACH 1000
X MACH 4000
X MACH 3000 (from Rel. 3.3),
X OCTOPUS
4.5.4 VLAN Port

RM Web
100 Release 6.0 07/2010
Switching 4.5 VLAN
X assign ports to VLANs

X define the Acceptable Frame Type
X activate/deactivate Ingress Filtering
Parameter Meaning Possible Default Setting

Values
Module Module of the device on which the port
is located.
Port VLAN ID Specifies the VLAN to which the port All allowed 1
assigns a received untagged data VLAN IDs
packet.
Acceptable Frame Specifies whether the port may also - admitAll admitAll
Types receive untagged data packets. -
admitOnlyVla
nTagged
Ingress Filtering Specifies whether the port evaluates on, off off
the received tags.
Table 41: VLAN Port dialog
Note: Note the following:

X HIPER-Ring
Select the port VLAN ID 1 for the ring ports and deactivate “Ingress
Filtering”.
X MRP-Ring
– If the MRP-Ring configuration (see on page 120 “Configuring the
MRP-Ring“) is not assigned to a VLAN, select the port VLAN ID 1.
– If the MRP-Ring configuration (see on page 120 “Configuring the
MRP-Ring“) is assigned to a VLAN, the device automatically performs
the VLAN configuration for this port.
X Network/Ring coupling
Select the VLAN ID 1 for the coupling and partner coupling ports and
deactivate “Ingress Filtering”.
RM Web L2E
Release 6.0 07/2010 101
Switching 4.5 VLAN
Figure 27: VLAN Port dialog
RM Web
102 Release 6.0 07/2010
QoS/Priority 4.5 VLAN
5 QoS/Priority
The device enables you to set

X how it evaluates the QoS/prioritizing information of incoming data
packets:
X VLAN priority based on IEEE 802.1Q/ 802.1D (Layer 2)
X Type of Service (ToS) or DiffServ (DSCP) for IP packets (Layer 3)
X which QoS/prioritizing information it writes to outgoing data packets
(e.g. priority for management packets, port priority).
The QoS/Priority menu contains the dialogs, displays and tables for
configuring the QoS/priority settings:
X Global
X Port configuration
X IEEE 802.1D/p mapping
X IP DSCP mapping
RM Web L2E
Release 6.0 07/2010 103
QoS/Priority 5.1 Global
5.1 Global

X enter the VLAN priority for management packets in the range 0 to 7
(default setting: 0).
In order for you to have full access to the management of the device, even
when there is a high network load, the device enables you to prioritize
management packets.
In prioritizing management packets (SNMP, Telnet, etc.), the device
sends the management packets with priority information.
Note the assignment of the VLAN priority to the traffic class (see table 45).
X enter the IP-DSCP value for management packets in the range 0 to 63
(default setting: 0 (be/cs0)).
In order for you to have full access to the management of the device, even
when there is a high network load, the device enables you to prioritize
management packets.
In prioritizing management packets (SNMP, Telnet, etc.), the device
sends the management packets with priority information.
Note the assignment of the IP-DSCP value to the traffic class (see
table 46).
Note: Certain DSCP values have DSCP names, such as be/cs0 to cs7
(class selector) or af11 to af43 (assured forwarding) and ef (expedited
forwarding).
X display the maximum number of queues possible per port.

The device supports 4 (8 for MACH 4000, MACH 104, MACH 1040 and
PowerMICE) priority queues (traffic classes in compliance with IEEE
802.1D).
X select the trust mode globally. You use this to specify how the device
handles received data packets that contain priority information.
X “untrusted”:
The device ignores the priority information in the packet and always
assigns the packets the port priority of the receiving port.
RM Web
104 Release 6.0 07/2010
X “trustDot1p”:
The device prioritizes received packets that contain VLAN tag
information according to this information (assigning them to a traffic
class - see “802.1D/p mapping“).
The device prioritizes received packets that do not contain any tag
information (assigning them to a traffic class - see “Entering the port
priority“) according to the port priority of the receiving port .
X “trustIpDscp”:
The device prioritizes received IP packets (assigning them to a traffic
class - see “IP DSCP mapping“) according to their DSCP value.
The device prioritizes received packets that are not IP packets
(assigning them to a traffic class - see “Entering the port priority“)
according to the port priority of the receiving port .
For received IP packets:
The device also performs VLAN priority remarking.
In VLAN priority remarking, the device modifies the VLAN priority of
the IP packets if the packets are to be sent with a VLAN tag (see on
page 98 “VLAN Static“).
Based on the traffic class to which the IP packet was assigned (see
above), the device assigns the new VLAN priority to the IP packet in
accordance with table 42.
Example: A received IP packet with a DSCP value of 32 (cs4) is
assigned to traffic class 2 (default setting). The packet was received at
a port with port priority 2. Based on table 42, the VLAN priority is set to
4.
Traffic class New VLAN priority New VLAN priority

when receiving port when receiving port
has an even port priority has an odd port priority
0 0 1
1 2 3
2 4 5
3 6 7
Table 42: VLAN priority remarking
RM Web L2E
Release 6.0 07/2010 105
Figure 28: Global dialog
RM Web
106 Release 6.0 07/2010
QoS/Priority 5.2 Port Configuration
5.2 Port Configuration
This dialog allows you to configure the ports. You can:

X assign a port priority to a port,
Parameter Meaning
Port priority Enter the port priority.
Table 43: Port configuration table
Figure 29: Port configuration dialog
RM Web L2E
Release 6.0 07/2010 107
QoS/Priority 5.2 Port Configuration
5.2.1 Entering the port priority

Double-click a cell in the “Port priority” column and enter the priority (0-7).
According to the priority entered, the device assigns the data packets that
it receives at this port to a traffic class (see table 44).
Prerequisite:
setting in the Global:Trust Mode dialog: untrusted (see on
page 104 “Global“) or
setting in the Global:Trust Mode dialog:trustDot1p(see on
page 104 “Global“) and the data packets do not contain a VLAN tag or
setting in Global:Trust Mode dialog: trustIpDscp(see on
page 104 “Global“) and the data packets are not IP packets.
Port priority Traffic class (default setting) IEEE 802.1D traffic type
0 1 Best effort (default)
1 0 Background
2 0 Standard
3 1 Excellent effort (business critical)
4 2 Controlled load (streaming multimedia)
5 2 Video, < 100 ms of latency and jitter
6 3 Voice, < 10 ms of latency and jitter
7 3 Network control reserved traffic
Table 44: Assigning the port priority to the 4 traffic classes
RM Web
108 Release 6.0 07/2010
QoS/Priority 5.3 802.1D/p mapping
5.3 802.1D/p mapping
The 802.1D/p mapping dialog allows you to assign a traffic class to every
VLAN priority.
Figure 30: 802.1D/p Mapping dialog
Enter the desired value from 0 to 3 in the Traffic Class field for every
VLAN priority.
RM Web L2E
Release 6.0 07/2010 109
QoS/Priority 5.3 802.1D/p mapping
Port priority Traffic class (default setting) IEEE 802.1D traffic type
0 1 Best effort (default)
1 0 Background
2 0 Standard
3 1 Excellent effort (business critical)
4 2 Controlled load (streaming multimedia)
5 2 Video, < 100 ms of latency and jitter
6 3 Voice, < 10 ms of latency and jitter
7 3 Network control reserved traffic
Table 45: Assigning the VLAN priority to the 4 traffic classes
Note: Network protocols and redundancy mechanisms use the highest traffic
class 3. Therefore, select other traffic classes for application data.
RM Web
110 Release 6.0 07/2010
QoS/Priority 5.4 IP DSCP mapping
5.4 IP DSCP mapping
The IP DSCP mapping table allows you to assign a traffic class to every
DSCP value.
Enter the desired value from 0 to 3 in the Traffic Class field for every
DSCP value (0-63).
Figure 31: IP DSCP mapping table
The different DSCP values get the device to employ a different forwarding
behavior, namely Per-Hop Behavior (PHB).
PHB classes:
X Class Selector (CS0-CS7): For reasons of compatibility to TOS/IP
Precedence
X Expedited Forwarding (EF): Premium service.
Reduced delay, jitter + packet loss (RFC 2598)
RM Web L2E
Release 6.0 07/2010 111
QoS/Priority 5.4 IP DSCP mapping
X Assured Forwarding (AF): Provides a differentiated schema for handling

different data traffic (RFC 2597).
X Default Forwarding/Best Effort: No particular prioritizing.
DSCP value DSCP name Traffic class

(default setting)
0 Best Effort /CS0 1
1-7 1
8 CS1 0
9,11,13,15 0
10,12,14 AF11,AF12,AF13 0
16 CS2 0
17,19,21,23 0
18,20,22 AF21,AF22,AF23 0
24 CS3 1
25,27,29,31 1
26,28,30 AF31,AF32,AF33 1
32 CS4 2
33,35,37,39 2
34,36,38 AF41,AF42,AF43 2
40 CS5 2
41,42,43,44,45,47 2
46 EF 2
48 CS6 3
49-55 3
56 CS7 3
57-63 3
Table 46: Mapping the DSCP values onto the traffic classes
RM Web
112 Release 6.0 07/2010
Redundancy 5.4 IP DSCP mapping
6 Redundancy
Under Redundancy you will find the dialogs and views for configuring and
monitoring the redundancy functions:
X Ring Redundancy
X Ring/Network coupling
X Spanning Tree
RM Web L2E
Release 6.0 07/2010 113
Redundancy 6.1 Ring Redundancy
6.1 Ring Redundancy
The concept of the Ring Redundancy enables the construction of high-

availability, ring-shaped network structures.
If a section is down, the ring structure of a
X HIPER-(HIGH PERFORMANCE REDUNDANCY) Ring with up to 50
devices typically transforms back to a line structure within 80 ms (possible
settings: standard/accelerated).
X MRP (Media Redundancy Protocol) Ring (IEC 62439) of up to 50 devices
typically transforms back to a line structure within 80 ms (adjustable to
max. 200 ms/500 ms).
With the help of the Ring Manager (RM) function of a device, you can connect
both ends of a backbone in a line structure to form a redundant ring.
X Within a HIPER-Ring, you can use any combination of the following
devices:
– RS2-./.
– RS2-16M
– RS2-4R
– RS20, RS30, RS40
– RSR20, RSR30
– OCTOPUS
– MICE
– MS20, MS30
– PowerMICE
– MACH 100
– MACH 1000
– MACH 3000
– MACH 4000
X Within an MRP-Ring, you can use devices that support the MRP protocol
based on IEC62439.
X Within a Fast HIPER-Ring, you can use any combination of the following
devices:
– RSR20, RSR30
– MACH 1000
Depending on the device model, the Ring Redundancy dialog allows you to:
X Select one of the available Ring Redundancy versions, or change it.
X Display an overview of the current Ring Redundancy configuration.
RM Web
114 Release 6.0 07/2010
X Create new Ring Redundancies.

X Configure existing Ring Redundancies.
X Enable/disable the Ring Manager function.
X Receive Ring information.
X Delete the Ring Redundancy.
Note: Enabled Ring Redundancy methods on a device are mutually

exclusive at any one time. When changing to another Ring Redundancy
method, deactivate the function for the time being.
Parameter Meaning
Version Select the Ring Redundancy version you want to use:
HIPER-Ring
MRP
Default setting is HIPER-Ring
Ring port No. In a ring, every device has 2 neighbors. Define 2 ports as ring ports to which the
neighboring devices are connected.
Module Module identifier of the ports used as ring ports
Port Port identifier of the ports used as ring ports
Operation Value depends on the Ring Redundancy version used. Described in the
following sections for the corresponding Ring Redundancy version.
Table 47: Ring Redundancy basic configuration
RM Web L2E
Release 6.0 07/2010 115
6.1.1 Configuring the HIPER-Ring

For the ring ports, select the following basic settings in the Basic
Settings:Port Configuration dialog:

Note: Configure all the devices of the HIPER-Ring individually. Before you
connect the redundant line, you must complete the configuration of all the
devices of the HIPER-Ring. You thus avoid loops during the configuration
phase.
Note: As an alternative to using software to configure the HIPER-Ring, with

devices RS20/30/40 and MS20/30 you can also use DIP switches to enter a
number of settings on the devices. You can also use a DIP switch to enter a
setting for whether the configuration via DIP switch or the configuration via
software has priority. The state on delivery is “Software Configuration”. You
will find details on the DIP switches in the “Installation” user manual.
RM Web
116 Release 6.0 07/2010
Parameter Meaning
Ring port X.X operation Display in “Operation” field:
active: This port is switched on and has a link.
inactive: This port is switched off or it has no link.
Redundancy Manager Status information, no input possible:
Status (Ring Manager) Active (redundant line): the redundant line was closed
because a data line or a network component within the ring is
down.
Inactive: the redundant ring is open, and all data lines and
network components are working.
Ring Recovery If you are using one or multiple lines with 1,000 MBit/s twisted pair
ports in the ring manager, you have the option of accelerating the
reconfiguration time for when connections are interrupted.
In the ring manager, select the desired value for the test packet
timeout for which the ring manager waits after sending a test
packet before it evaluates the test packet as lost.
X Standard: test packet timeout 480 ms
X Accelerated: test packet timeout 280 ms
Note: Settings in the “Ring Recovery” frame are only effective for
devices that are ring managers, and they are only meaningful if at
least one line in the ring consists of a 1,000 MBit/s twisted pair line.
Information If the device is a ring manager: The displays in this frame mean:
“Redundancy working”: When a component of the ring is down, the
redundant line takes over the function of the failed line.
“Configuration failure”: You have configured the function
incorrectly, or there is no ring port connection.
Table 49: HIPER-Ring configuration
RM Web L2E
Release 6.0 07/2010 117
Figure 32: Selecting ring redundancy, entering ring ports, enabling/disabling ring
manager and selecting ring recovery.
Note: Deactivate the Spanning Tree protocol (STP) for the ports connected
to the redundant ring, because the Spanning Tree and the Ring Redundancy
work with different reaction times (Redundancy:Spanning Tree:Port).
If you used the DIP switch to activate the HIPER-Ring function, STP is
automatically switched off.
Note: If you have configured VLANs, note the VLAN configuration of the ring
ports.
In the configuration of the HIPER-Ring, you select for the ring ports
– VLAN ID 1 and
– VLAN membership Untagged in the static VLAN table
RM Web
118 Release 6.0 07/2010
Note: When activating the HIPER-Ring function, the device sets the
corresponding settings for the pre-defined ring ports in the configuration table
(transmission rate and mode). If the HIPER-Ring function is switched off, the
ports, which are changed back into normal ports, keep the ring port settings.
Independently of the DIP switch setting, you can still change the port settings
via the software.
RM Web L2E
Release 6.0 07/2010 119
6.1.2 Configuring the MRP-Ring

To configure an MRP-Ring, you set up the network to meet your demands.
For the ring ports, select the following basic settings in the Basic

Note: Configure all the devices of the MRP-Ring individually. Before you
connect the redundant line, you must have completed the configuration of all
the devices of the MRP-Ring. You thus avoid loops during the configuration
phase.
Parameter Meaning
Ring port X.X Display in “Operation” field:
operation forwarding: This port is switched on and has a link.
blocked: This port is blocked and has a link.
disabled: This port is switched off.
not connected: This port has no link.
Configuration Deactivate the advanced mode if a device in the ring does not support the
Redundancy advanced mode for fast switching times. Otherwise you activate the advanced
Manager mode.
(Ring
Manager)
Note: All Hirschmann devices that support the MRP-Ring also support the
advanced mode.
Operation When you have configured all the parameters for the MRP-Ring, you switch the
operation on with this setting. When you have configured all the devices in the
MRP-Ring, you close the redundant line.
Table 51: MRP-Ring configuration
RM Web
120 Release 6.0 07/2010
Parameter Meaning
Ring For the device for which you have activated the ring manager, select the value
Recovery 200 ms if the stability of the ring meets the requirements of your network.
Otherwise select 500 ms.
Note: Settings in the “Ring Recovery” frame are only effective for devices that
are ring managers.
VLAN ID If you have configured VLANs, you select
VLAN ID 0 here if you do not want to assign the MRP-Ring configuration to a
VLAN. Note the VLAN configuration of the ring ports: Select for VLAN ID 1 and
VLAN membership U in the static VLAN table for the ring ports.
VLAN ID > 0 if you want to assign the MRP-Ring configuration to this VLAN.
Select this VLAN ID in the MRP-Ring configuration for all devices in this MRP-
Ring. Note the VLAN configuration of the ring ports: For all ring ports in this MRP-
Ring, select this corresponding VLAN ID and the VLAN membership T in the
static VLAN table.
“Redundancy working”: When a component of the ring is down, the redundant
line takes over the function of the failed line.
“Configuration failure”: You have configured the function incorrectly, or there is
no ring port connection.
Table 51: MRP-Ring configuration
Figure 33: Selecting MRP-Ring version, entering ring ports and enabling/disabling
ring manager
RM Web L2E
Release 6.0 07/2010 121
Note: For all devices in an MRP-Ring, activate the MRP compatibility in the
Redundancy:Spanning Tree:Global dialog if you want to use RSTP in
the MRP-Ring. If this is not possible, perhaps because individual devices do
not support the MRP compatibility, you deactivate the Spanning Tree
protocol at the ports connected to the MRP-Ring. Spanning Tree and Ring
Redundancy affect each other.
Note: If you combine RSTP with an MRP-Ring, set the bridges in the MRP-
Ring to a better (numerically lower) RSTP bridge priority than those in the
connected RSTP network. Thus you avoid a connection interruption if
connections in the MRP-Ring become inoperable.
RM Web
122 Release 6.0 07/2010
Redundancy 6.2 Ring/Network Coupling
6.2 Ring/Network Coupling

X display an overview of the existing Ring/Network coupling,
X configure a Ring/Network coupling,
X switch a Ring/Network coupling on/off,
X create a new Ring/Network coupling, and
X Delete Ring/Network couplings
6.2.1 Preparing a Ring/Network coupling
STAND-BY switch
All devices have a STAND-BY switch, with which you can define the role
of the device within a Ring/Network coupling.
Depending on the device type, this switch is a DIP switch on the devices,
or else it is exclusively a software setting (Redundancy:Ring/Network
Coupling dialog). By setting this switch, you define whether the device
has the main coupling or the redundant coupling role within a Ring/
Network coupling. You will find details on the DIP switches in the
“Installation” user manual.
Note: Depending on the model, the devices have a DIP switch, with which
you can choose between the software configuration and the DIP switch
configuration. When you set the DIP switches so that the software
configuration is selected, the DIP switches are effectively deactivated.
RM Web L2E
Release 6.0 07/2010 123
Device type STAND-BY switch type

RS2-./. DIP switch
RS2-16M DIP switch
RS20/RS30/RS40 Selectable: DIP switch and software setting
MS20/MS30 Selectable: DIP switch and software setting
Table 52: Overview of the STAND-BY switch types
Depending on the device and model, set the STAND-BY switch in

accordance with the following table:
Device with Choice of main coupling or redundant coupling

DIP switch On “STAND-BY” DIP switch
DIP switch/software switch According to the option selected
option - on “STAND-BY” DIP switch or in the
- Redundancy:Ring/Network Coupling dialog, by making
selection in “Select configuration”.
Note: These devices have a DIP switch, with which you can choose
between the software configuration and the DIP switch
configuration. You can find details on the DIP switches in the User
Manual Installation.
Software switch In the Redundancy:Ring/Network Coupling dialog
Table 53: Setting the STAND-BY switch
Figure 34: Software configuration of the STAND-BY switch
RM Web
124 Release 6.0 07/2010
Depending on the STAND-BY DIP switch position, the dialog displays

those configurations that are not possible as grayed-out. If you want to
select one of these grayed-out configurations, change the STAND-BY
DIP switch on the device to the other position.
One-Switch coupling
On the device set the 'STAND BY' dip switch to the ON position or use the
software configuration to assign the redundancy function to it.
Two-Switch coupling
Assign the device in the redundant line the DIP switch setting “STAND-
BY”, or use the software configuration to assign the redundancy function
to it.
Note: For reasons of redundancy reliability, do not use Rapid Spanning

Tree and Ring/Network Coupling in combination.
RM Web L2E
Release 6.0 07/2010 125
Ring/Network Coupling dialog
Parameter Meaning
Selecting the Depending on your local conditions, select “One-Switch coupling”,
configuration “Two-Switch coupling, Slave”, “Two-Switch coupling, Master”, “Two-
Switch coupling with control line, Slave” or “Two-Switch coupling with
control line, Master”. These options are presented as buttons from left
to right.
Depending on the device type (see table 52), you make this setting:
– only using DIP switches
– only using software
– using DIP switch and software
You will find details on the DIP switches on the devices in the
“Installation” user manual.
– For devices configured only using DIP switches, you use these
switches to make the settings. In this case, the buttons in the dialog
are only for display purposes.
– For devices without DIP switches, you only use the software to
make settings. You can select the configuration using the buttons.
– For devices that can be configured using DIP switches and
software, you can activate or deactivate the DIP switches. If you
have activated the DIP switches, you cannot overwrite the DIP
switch settings using the software - settings that cannot be selected
using the software are grayed-out in the dialog.
To configure using the software, select the relevant Ring/Network
coupling constellation by pressing the corresponding button.
Coupling port This is the port to which you have connected a redundant connection.
Note: Configure the coupling port and the ring ports, if there are any
ring ports, on different ports.
Note: To avoid continuous loops, the device sets the port status of the
coupling port to “off” if you switch off the function or change the
configuration while the connections are operating at these ports.
Port mode - active You have switched the port on.
- stand-by The port is in stand-by mode.
Port state - active: You have switched the port on.
- stand-by: The port is in stand-by mode.
- not connected: You have not connected the port.
Partner coupling port This is the port at which the partner has made its connection. It is only
possible or necessary to enter a port here if “One-Switch coupling” is
being set up.
Note: Configure the partner coupling port and the ring ports, if there are
any ring ports, on different ports.
IP Address If you have selected “Two-Switch coupling”, the IP address of the
partner is displayed here if you have already started operating the
partner in the network.
Control port This is the port to which you connect the control line.
Table 54: Ring/Network Coupling dialog
RM Web
126 Release 6.0 07/2010
Parameter Meaning
Operation Here you switch the Ring/Network coupling for this device on or off
“Redundancy working”: When a component of the ring is down, the
redundant line takes over the function of the failed line.
“Configuration failure”: You have configured the function incorrectly, or
there is no ring port connection.
Redundancy Mode With the “Redundant Ring/Network Coupling” setting, either the main
line or the redundant line is active. Both lines are never active
simultaneously.
With the “Extended Redundancy” setting, the main line and the
redundant line are simultaneously active if a problem is detected in the
connection line between the devices in the connected (i.e., the remote)
network. During the reconfiguration period, package duplications may
possibly occur. Therefore, only select this setting if your application
detects package duplications.
Coupling Mode Here you define whether the constellation you are configuring is a
coupling of redundancy rings (HIPER-Ring, MRP-Ring), or network
segments.
Table 54: Ring/Network Coupling dialog
The following tables show the selection options and default settings for
the ports used in the Ring/Network coupling.
Device Partner coupling port Coupling port

RS2-./. Not possible Not possible
RS2-16M All ports (default setting: port 2) All ports (default setting: port 1)
RS20, RS30, All ports (default setting: port 1.3) All ports (default setting: port 1.4)
RS40
OCTOPUS All ports (default setting: port 1.3) All ports (default setting: port 1.4)
MICE All ports (default setting: port 1.3) All ports (default setting: port 1.4)
PowerMICE All ports (default setting: port 1.3) All ports (default setting: port 1.4)
MS20 All ports (default setting: port 1.3) All ports (default setting: port 1.4)
MS30 All ports (default setting: port 2.3) All ports (default setting: port 2.4)
RSR20/30 All ports (default setting: port 1.3) All ports (default setting: port 1.4)
MACH 100 All ports (default setting: port 1.3) All ports (default setting: port 1.4)
MACH 3000 All ports All ports
Table 55: Port assignment for one-Switch coupling
RM Web L2E
Release 6.0 07/2010 127
Device Coupling port

RS2-./. Not possible
RS2-16M Adjustable for all ports (default setting: port 1)
RS20, RS30, RS40 Adjustable for all ports (default setting: port 1.4)
OCTOPUS Adjustable for all ports (default setting: port 1.4)
MICE Adjustable for all ports (default setting: port 1.4)
PowerMICE Adjustable for all ports (default setting: port 1.4)
MS20 Adjustable for all ports (default setting: port 1.4)
MS30 Adjustable for all ports (default setting: port 2.4)
RSR20/30 Adjustable for all ports (default setting: port 1.4)
MACH 100 Adjustable for all ports (default setting: port 1.4)
MACH 3000 Adjustable for all ports
Table 56: Port assignment for the redundant coupling (two-Switch coupling)
Device Coupling port Control port

RS2-./. Port 1 Stand-by port (can only be combined
with RS2-../.. )
RS2-16M Adjustable for all ports Adjustable for all ports
(default setting: port 1) (default setting: port 2)
RS20, RS30, Adjustable for all ports Adjustable for all ports
RS40 (default setting: port 1.4) (default setting: port 1.3)
OCTOPUS Adjustable for all ports Adjustable for all ports
(default setting: port 1.4) (default setting: port 1.3)
MICE Adjustable for all ports Adjustable for all ports
PowerMICE Adjustable for all ports Adjustable for all ports
MS20 Adjustable for all ports Adjustable for all ports
MS30 Adjustable for all ports Adjustable for all ports
RSR20/RSR30 Adjustable for all ports Adjustable for all ports
MACH 100 Adjustable for all ports Adjustable for all ports
Table 57: Port assignment for the redundant coupling (two-Switch coupling with
control line)
RM Web
128 Release 6.0 07/2010
Note: For the coupling ports, select the following settings in the Basic
– Port: on
– Automatic configuration (autonegotiation):
on for twisted-pair connections
– Manual configuration: 100 Mbit/s FDX, 1 Gbit/s FDX or 10 Gbit/s FDX
for glass fiber connections, depending on the port’s capabilities
Note: If you have configured VLANS, note the VLAN configuration of the
coupling and partner coupling ports.
In the Ring/Network Coupling configuration, select for the coupling and
partner coupling ports
– VLAN ID 1 and “Ingress Filtering” disabled in the port table and
– VLAN membership U in the static VLAN table.
Note: If you are operating the Ring Manager and two-Switch coupling
functions at the same time, there is the possibility of creating a loop.
RM Web L2E
Release 6.0 07/2010 129
Redundancy 6.3 Spanning Tree
6.3 Spanning Tree
Under Spanning Tree you will find the dialogs and views for configuring and
monitoring the Spanning Tree function in accordance with the IEEE 802.1w
(Rapid Spanning Tree, RSTP) standard.
Note: The Spanning Tree Protocol is a protocol for MAC bridges. For this
reason, the following description employs the term bridge for Switch.
Introduction
Local networks are getting bigger and bigger. This applies to both the
geographical expansion and the number of network participants. Therefore,
it is advantageous to use multiple bridges, for example:
X to reduce the network load in sub-areas,
X to set up redundant connections and
X to overcome distance limitations.
However, using multiple bridges with multiple redundant connections

between the subnetworks can lead to loops and thus the total failure of the
network. In order to avoid this, you can use Spanning Tree. Spanning Tree
enables loop-free switching through the systematic deactivation of redundant
connections. Redundancy ensures the systematic reactivation of individual
connections as needed.
Rapid Spanning Tree Protocol (RSTP)

RSTP is a further development of the Spanning Tree Protocol (STP) and is
compatible with it. If a connection or a bridge fails, the STP required a
maximum of 30 seconds to reconfigure. This is no longer acceptable in time-
sensitive applications. RSTP achieves average reconfiguration times of less
than a second. When you use RSTP in a ring topology with 10 to 20 devices,
you can even achieve reconfiguration times in the order of milliseconds.
RM Web
130 Release 6.0 07/2010
Note: RSTP reduces a layer 2 network topology with redundant paths into a
tree structure (Spanning Tree) that does not contain any more redundant
paths. One of the Switches takes over the role of the root bridge here. The
maximum number of devices permitted in a branch (from the root bridge to
the tip of the branch) is specified by the variable Max Age for the current root
bridge. The preset value for Max Age is 20, which can be increased up to 40.
If the device working as the root fails and another device takes over its
function, the Max Age setting of the new root bridge determines the
maximum number of devices allowed in a branch.
Note: When coupling network segments to an MRP-Ring and activating the

MRP compatibility, note this special condition: If the root bridge is within the
MRP-Ring, the devices within the MRP-Ring count as a single virtual device
when calculating the length of the branch.
Note: The RSTP standard dictates that all the devices within a network work
with the (Rapid) Spanning Tree Algorithm. If STP and RSTP are used at the
same time, the advantages of faster reconfiguration with RSTP are lost.
A device that only supports RSTP works together with MSTP devices by not
assigning an MST region to itself, but rather the CST (Common Spanning
Tree).
Note: By changing the IEEE 802.1D-2004 standard for RSTP, the Standards
Commission reduced the maximum value for the “Hello Time” from 10 s to
2 s. When you update the Switch software from a release before 5.0 to
release 5.0 or higher, the new software release automatically reduces the
locally entered “Hello Time” values that are greater than 2 s to 2 s.
If the device is not the RSTP root, “Hello Time” values greater than 2 s can
remain valid, depending on the software release of the root device.
Note: The following text uses the term Spanning Tree (STP) to describe
settings or behavior that applies to STP, RSTP or MSTP.
RM Web L2E
Release 6.0 07/2010 131
6.3.1 Global
X switch the Spanning Tree Protocol on/off
X display bridge-related information on the Spanning Tree Protocol
X configure bridge-related parameters of the Spanning Tree Protocol
X set bridge-related additional functions
X display the parameters of the root bridge and
X display bridge-related topology information.
Note: Rapid Spanning Tree is activated on the device by default, and it

automatically begins exploding the existing topology into a tree structure. If
you have deactivated RSTP on individual devices, you avoid loops during the
configuration phase.
The following tables show the selection options and default settings, and
information on the global Spanning Tress settings for the bridge.

Frame Switches the Spanning Tree function for On, On
„Function“ this device “On” or “Off”. Off
If you switch off the Spanning Tree for a
device globally, the device floods the
Spanning Tree packets received like
normal Multicast packets to the ports.
Thus the device behaves transparently
with regard to Spanning Tree packets.
Table 58: Global Spanning Tree settings, basic function
RM Web
132 Release 6.0 07/2010
In the “Protocol Configuration / Information” frame you can configure the

following values and read information.

Column Information and configuration
„Bridge“ parameters of the local device
Bridge ID The local Bridge ID, made up of the local
(read only) priority and its own MAC address.
The format is
ppppp / mm mm mm mm mm mm,
with: ppppp: priority (decimal) and
mm: the respective byte of the MAC
address (hexadecimal).
Priority Sets the local bridge priority. 0 ≤ n * 4,096 ≤ 32,768
The bridge priority and its own MAC 61,440
address make up this separate Bridge
ID. The device with the best (numerically
lowest) priority becomes the root device.
Define the root device by assigning the
device the best (numerically lowest)
priority in the Bridge ID among all the
devices in the network.
Note that you may only enter multiples of
4,096 for this value.
Hello Time Sets the Hello Time. 1-2 2
The local Hello Time is the time in
seconds between the sending of two
configuration messages (Hello packets).
If the local device is the root, the other
devices in the entire network take over this
value. Otherwise the local device uses the
value of the root bridge in the “Root”
column on the right.
Table 59: Global Spanning Tree settings, local bridge parameters
RM Web L2E
Release 6.0 07/2010 133

Forward Sets the Forward Delay parameter. 4 - 30 s 15 s
Delay In the previous STP protocol, the Forward See the note
Delay parameter was used to delay the following this table.
status change between the statuses
disabled, discarding, learning,
forwarding. Since the introduction of
RSTP, this parameter only has a
subordinate role, because the RSTP
bridges negotiate the status change
without any specified delay.
Max Age Sets the Max Age parameter. 6 - 40 s 20 s
In the previous STP protocol, the Max Age See the note
parameter was used to specify the validity following this table.
of STP BPDUs in seconds. For RSTP,
Max Age signifies the maximum
permissible branch length (number of
devices to the root bridge).
TX Hold Sets the HX Hold Count parameter. 1 - 40 10
Count The TX Hold Count parameter specifies (based on RSTP
the maximum number of BPDUs that a standard: 1 - 10)
port may send per second. If more BPDUs
are waiting to be sent, the device rejects
the remaining ones. When the global Hello
Time has elapsed, the device sends all the
currently waiting BPDUs until the
maximum number is reached again.
RM Web
134 Release 6.0 07/2010

MRP Switches the MRP compatibility on/off. On, Off
compatibility
MRP compatibility enables RSTP to be Off
used within an MRP-Ring and when
coupling RSTP segments to an MRP-
Ring. The prerequisite is that all devices in
the MRP-Ring must support MRP
compatibility.
If you combine RSTP with an MRP-Ring,
set the bridges in the MRP-Ring to a better
(numerically lower) RSTP bridge priority
than those in the connected RSTP
network. Thus you avoid a connection
interruption if connections in the MRP-
Ring become inoperable.
BPDU Guard Switches the BPDU Guard function on/off. On, Off
If BPDU Guard is switched on, the device Off
automatically activates the function for
edge ports (with the setting “Admin Edge
Port” true).
When such a port receives any STP-
BPDU, the device sets the port status
“BPDU Guard Effect” to true and the
transmission status of the port to
discarding(see table 64).
Thus the device protects your network at
terminal device ports from attacks with
STP-BPDUs that try to change the
topology.
Note: The parameters Forward Delay and Max Age have the following
relationship:
Forward Delay ≥ (Max Age/2) + 1
If you enter values that contradict this relationship, the device then replaces
these values with the last valid values or the default value.
RM Web L2E
Release 6.0 07/2010 135
Parameter Meaning Possible Values Default

Setting
Column Information on the device that is currently
„Root“ the root bridge
Bridge ID The Bridge ID of the current root bridge.
The format is
ppppp / mm mm mm mm mm mm,
with: ppppp: priority (decimal) and mm: the
respective byte of the MAC address (hexadecimal).
Priority The Priority of the current root bridge. 0 ≤ n*4096 ≤ 32768
61440
Hello Time The Hello Time of the current root bridge. 1-2 2
Forward The Forward Delay of the current root bridge. 4 - 30 s 30 s
Delay
Max Age The Max Age of the current root bridge. 6 - 40 s 20 s
Table 60: Global Spanning Tree settings, root bridge information
Parameter Meaning Value range

Column „Topology“ Spanning Tree topology information
Bridge is root If the local device is currently the root bridge, Selected, not
the device displays this box as selected. If selected.
the device is not the root bridge, it is
displayed as empty.
Root Port The port of the device from which the current Valid port ID or 0.
path leads to the root bridge. 0: the local
bridge is the root.
Root path costs Path costs from the root port of the device to 0-200,000,000
the current root bridge of the entire layer 2
network. 0: the local bridge is the root.
Topology changes Counts how often the device has put a port
into the Forwarding status via Spanning
Tree since it was started.
Time since last change Time since the last topology change.
Table 61: Global Spanning Tree settings, topology information
RM Web
136 Release 6.0 07/2010
If you have activated the “MRP Compatibility” function, the device displays
the “Information” frame with additional information on MRP compatibility:

Information If you have activated the MRP Message with bridge -
compatibility (RSTP over MRP) and one of ID or empty.
the participating devices has detected a
configuration problem, the device displays
“Conflict with bridge pppp /
mm mm mm mm mm”. During normal
operation, this field is empty.
Table 62: Global Spanning Tree settings, Information frame
Figure 35: Dialog Spanning Tree, Global
RM Web L2E
Release 6.0 07/2010 137
6.3.2 Port
Note: Deactivate the Spanning Tree protocol for the ports connected to a
HIPER-Ring, Fast HIPER-Ring, or Ring/Network coupling, because
Spanning Tree and Ring Redundancy or Ring/Network coupling affect each
other.
Activate the MRP compatibility in an MRP-Ring if you want to use RSTP and
MRP in combination.
If you combine RSTP with an MRP-Ring, set the bridges in the MRP-Ring to
a better (numerically lower) RSTP bridge priority than those in the connected
RSTP network. Thus you avoid a connection interruption if connections in the
MRP-Ring become inoperable.
If you use the device in a Multiple Spanning Tree (MSTP) environment, the
device participates exclusively in the Common Spanning Tree Instance
(CST). This manual chapter also uses the expression Global MST Instance
for the CST.
RM Web
138 Release 6.0 07/2010

Setting
Tab „CIST“ Port configuration and information
on the global MSTI (IST) and the
CST.
STP active Here you can switch Spanning Tree On, Off On
on or off for this port. If Spanning
Tree is activated globally and
switched off at one port, this port
does not send STP-BPDUs and
drops any STP-BPDUs received.
Note: If you want to use other

layer 2 redundancy protocols such
as HIPER-Ring or Ring/Network
coupling in parallel with Spanning
Tree, make sure you switch off the
ports participating in these protocols
in this dialog for Spanning Tree.
Otherwise the redundancy can fail
or loops can result.
Port status (read Displays the STP port status with discarding, learning, -
only) regard to the global MSTI (IST). forwarding, disabled,
manualForwarding,
notParticipate
Port role (read Displays the STP port role with root, alternate, -
only) regard to the global MSTI (IST). designated, backup,
master, disabled
Port path costs Enter the path costs with regard to 0 - 200,000,000 0
the global MSTI (IST) to indicate (automati
preference for redundant paths. If cally)
the value is 0, the Switch
automatically calculates the path
costs for the global MSTI (IST)
depending on the transmission rate.
Port priority Here you enter the port priority (the 16 ≤ n·16 ≤ 240 128
four highest bits of the port ID) with
regard to the global MSTI (IST) as a
decimal number of the highest byte
of the port ID.
Table 63: Port-related STP settings and displays, CIST
RM Web L2E
Release 6.0 07/2010 139

Setting
Received bridge Displays the remote bridge ID from Bridge ID -
ID (read only) which this port last received an STP- (format ppppp /
BPDU. mm mm mm mm mm mm)
In the stable condition (no topology
change), this is usually the
designated bridge ID, as only its port
has the role “designated” and thus
sends BPDUs.
Received port Displays the port ID at the remote Port ID, -
ID (read only) bridge from which this port last format pn nn,
received an STP-BPDU. with p: port priority / 16,
In the stable condition (no topology nnn: port No., (both
change), this is usually the hexadecimal)
designated port of the designated
bridge, as only its port sends
BPDUs.
Received path Displays the path costs of the 0-200,000,000 -
costs (read only) remote bridge from its root port to
the CIST root bridge.
Admin Edge Activate this setting when a terminal active (box selected), inactiv
Port device is connected to the port. inactive (box empty) e
Then the port immediately has the
forwarding status after a link is set
up, without first going through the
STP statuses. If the port still
receives an STP-BPDU, the device
blocks the port and clarifies its STP
port role. In the process, the port
can switch to a different status, e.g.
forwarding, discarding,
learning.
Deactivate the setting when the port
is connected to a bridge. After a link
is set up, the port then goes through
the STP statuses first before taking
on the forwarding status, if
applicable.
This setting applies to all MSTIs.
RM Web
140 Release 6.0 07/2010

Setting
Auto Edge Port The Auto Edge Port setting is only active (box selected), active
considered when the Admin Edge inactive (box empty)
Port parameter is deactivated.
If Auto Edge Port is active, after a
link is set up the device sets the port
to the forwarding status after
1.5 · Hello Time (in the default
setting 3 s).
If Auto Edge Port is deactivated, the
device waits for 2 · Forward
Delay instead (in the default setting
30 s).
This setting applies to all MSTIs.
Oper Edge Port The “Oper Edge Port” condition is true, false -
(read only) true if no STP-BPDUs have been
received, i.e. a terminal device is
connected. It is false if STP-
BPDUs have been received, i.e. a
bridge is connected.
This condition applies to all MSTIs.
Actual point-to- The “Actual point-to-point” condition true, false
point (read only) is true if this port has a full duplex
connection to an STP device, is determined from duplex
otherwise it is false (e.g. if a hub is mode:
connected). FDX: true
The point-to-point connection HDX: false
makes a direct connection between
2 RSTP devices. The direct,
decentralized communication
between the two bridges results in a
short reconfiguration time.
This condition applies to all MSTIs.
RM Web L2E
Release 6.0 07/2010 141
Figure 36: STP Port dialog, CIST tab
RM Web
142 Release 6.0 07/2010

Setting
Tab „Guards“ Protective settings for the ports.
Root Guard The “Root Guard” setting is only relevant for active (box inactiv
edge ports (ports with the “Admin Edge Port” selected), e
setting true). inactive (box
If such a port receives an STP-BPDU with empty)
better path information on the root that what
the device knows, the device discards the
BPDU and sets the port status to
discarding, instead of assigning the port the
STP port role root.
Thus the device protects your network from
attacks with STP-BPDUs that try to change the
topology, and from incorrect configurations.
If there are no STP-BPDUs with better path
information on the root, the device resets the
transmission status of the port according to the
port role.
Note: The “Root Guard” and “Loop Guard”

settings are mutually exclusive. If you activate
one setting when the other is already active,
the device switches off the other one.
TCN Guard If the “TCN Guard” setting is active (TCN: active (box inactiv
Topology Change Notification) the port ignores selected), e
the topology change flag in the STP-BPDUs inactive (box
that is reporting a topology change. empty)
Thus the device protects your network from
attacks with STP-BPDUs that try to change the
topology, and from incorrect configurations.
If the “TCN Guard” setting is inactive, the
device follows the protocol in reacting to the
STP-BPDUs received.
Note: If the received BPDU contains other

information apart from the topology change
flag that causes a topology change (e.g. better
path information on the root than that known
by the device), the device processes this
information.
Table 64: Port-related STP settings and displays, guards
RM Web L2E
Release 6.0 07/2010 143

Setting
Loop Guard The “Loop Guard” setting is only meaningful active (box inactiv
for ports with the STP role alternate, selected), e
backup or root. If the “Loop Guard” setting is inactive (box
active and the port has not received any STP- empty)
BPDUs for a while, the device sets the port to
the discarding condition (port sends no
more data).
The device also sets the port to what is known
as the “loop status”. This is displayed in the
“Loop Status” column.
The device thus prevents a potential loop if no
more STP-BPDUs are received if, for example,
STP is switched off on the remote device, or
the link only fails in the receiving direction.
When the port receives BPDUs again, the
device resets the loop status of the port to
false, and the transmission status of the port
according to the port role.
If the “Loop Guard” setting is inactive,
however, the device sets the port to the
forwarding status when STP-BPDUs have
not been received.
Note: The “Root Guard” and “Loop Guard”

settings are mutually exclusive. If you activate
one setting when the other is already active,
the device switches off the other one.
Loop Status Display the status of the Loop Status. true, false -
(read only) The device sets the loop status of the port to
true if the “Loop Guard” setting is active at
the port and the port is not receiving any more
STP-BPDUs.
Here the device leaves the port in the
discarding transmission status, to prevent a
potential loop.
When the port receives STP-BPDUs again,
the device resets the loop status to false.
Transitions to Counts how often the device has set the port 0 - 4,294,967,295 0
Loop Status to the loop status (“Loop Status” column (232-1)
(read only) true).
RM Web
144 Release 6.0 07/2010

Setting
Transitions from Counts how often the device has set the port 0 - 4,294,967,295 0
Loop Status out of the loop status (“Loop Status” column (232-1)
true).
BPDU Guard The “BPDU Guard Effect” status is only true, false -
Effect (read only) relevant for edge ports (ports with the “Admin
Edge Port” status true), and only if the
“BPDU Guard” global function is active (see
table 59).
When such a port receives any random STP-
BPDU, the device sets the port's “BPDU Guard
Effect” status to true and its transmission
status to discarding.
Thus the device protects your network at
terminal device ports from attacks with STP-
BPDUs that try to change the topology.
To return the port to a normal transmitting
status from the locked status, break and
reconnect the link, or switch the “Admin Edge
Port” port setting off and on again.
Figure 37: STP Port dialog, Guards tab
RM Web L2E
Release 6.0 07/2010 145
RM Web
146 Release 6.0 07/2010
Advanced 6.3 Spanning Tree
7 Advanced
The menu contains the dialogs, displays and tables for:

X DHCP Relay Agent
X Industry Protocols
X Command Line
RM Web L2E
Release 6.0 07/2010 147
Advanced 7.1 DHCP Relay Agent
7.1 DHCP Relay Agent
This dialog allows you to configure the DHCP relay agent.
Enter the DHCP server IP address.

If one DHCP server is not available, you can enter up to 3 additional
DHCP server IP addresses so that the device can change to another
DHCP server.
With Option 82, a DHCP relay agent which receives a DHCP request
adds an “Option 82” field to the request, as long as the request received
does not already have such a field.
When the function is switched off, the device will forward attached “Option
82” fields, but it will not add any on. Under “Type”, you specify the format
in which the device recognition of this device is entered in the “Option 82”
field by the DHCP relay agent.
The options are:
– IP address
– MAC Address (state on delivery)
– System name (client ID)
– Other (freely definable ID, which you can specify in the following rows).
“Remote ID entry for DHCP server” shows you the value which you enter
when configuring your DHCP server. “Type display” shows the device
recognition in the selected form.
X The “Circuit ID” column shows you the value which you enter when
configuring your DHCP server. The “Circuit ID” contains the port number
and the ID of the VLAN from which the DHCP has been received.
Example of a configuration of your DHCP server:

Type: mac
DHCP server for RemoteID entry: 00 06 00 80 63 00 06 1E
Circuit ID: B3 06 00 00 01 00 01 01
This results in the entry for the “Hardware address” in the DHCP server:
B306000001000101000600806300061E
In the “Option 82 on” column, you can switch this function on/off for each
port.
RM Web
148 Release 6.0 07/2010
Advanced 7.1 DHCP Relay Agent
In the “Hirschmann Device” column, you mark the ports to which a

Hirschmann device is connected.
Figure 38: DHCP Relay Agent dialog
RM Web L2E
Release 6.0 07/2010 149
Advanced 7.2 Industrial Protocols
7.2 Industrial Protocols
The “Industry Protocols” menu allows you to

X configure the PROFINET IO protocol as well as
X the EtherNet/IP protocol.
Detailed information on industrial protocols and PLC configuration is

contained in the User Manual "Industrial Protocols“.
7.2.1 PROFINET IO
This dialog allows you to configure the PROFINET IO protocol. To integrate
this in a control system, perform the following steps.
General settings:
In the Basic Settings:Network dialog, check whether Local is
selected in the “Mode” frame (see on page 21 “Network“).
In the Switching:VLAN:Global dialog, check whether “VLAN 0
Transparent Mode” is selected (see on page 93 “VLAN Global“).
Note: Exclude a combination of the VLAN 0 Transparent mode and the

use of MSTP (Multiple Spanning Tree).
Configure the alarm settings and the threshold values for the alarms you
want to monitor (see on page 169 “Device Status“).
Global PROFINET IO settings:

Switch on the function by selecting “ProfinetIO”.
Click on “Download GSDML File” to load the GSDML file onto your PC.
RM Web
150 Release 6.0 07/2010
PROFINET IO Port settings:

Select the port for which you want to set the DCP mode in detail, and in
the column DCP Mode, select
– none:
The device sends received DCP frames. However, the CPU does not
process them yet, it still generates DPC frames. The port does not
send any DCP frames which were received at another port.
– ingress:
The device sends received DCP frames. The CPU processes received
DCP frames from this port, but does not generate any. The port does
not send any DCP frames which were received at another port.
– egress:
The device sends received DCP frames. The CPU ignores frames
received from this port and generates them as needed.
– both:
The device sends received DCP frames. The CPU processes received
frames and generates them as needed.
The default setting is both.
Note: If you connect 2 switches which are to reside in separate DCP

domains, on both switches you set the DCP mode of the involved
ports to “none” or “ingress”. This ensures that neither of the switches
receives or forwards DCP frames.
Select the port for which you want to set its PHY module to the fast start
mode, and select from the following in the column Fast Start Up:
- disable to set the normal start mode,
- enable to set the fast start mode.
Note: The setting enable only becomes effective if the automatic

configuration of the port (Autoneg) is switched off (see on page 26
“Port Configuration“).
The default setting is disable. If a port does not support the fast start
mode, the device will show unsupported in this column.
Settings for the PLC:

Configure the PLC as described in the “Industry Protocols” user manual.
RM Web L2E
Release 6.0 07/2010 151
7.2.2 EtherNet/IP
This dialog allows you to activate the EtherNet/IP protocol. To integrate this
in a control system, perform the following steps.
General settings:
In the Switching:Multicasts:IGMP dialog, check whether IGMP
Snooping is activated (see on page 85 “IGMP (Internet Group
Management Protocol)“).
Global EtherNet/IP settings:

Activate the function in the “EtherNet/IP” frame; the default setting is off.
Click on “Download EDS File” to load the EDS file onto your PC.
Settings for the PLC:

Configure the PLC as described in the “Industry Protocols” user manual.
RM Web
152 Release 6.0 07/2010
Advanced 7.3 Command Line
7.3 Command Line
This window enables you to access the Command Line Interface (CLI) using
the Web interface.
You will find detailed information on CLI in the “Command Line Interface”
reference manual.
RM Web L2E
Release 6.0 07/2010 153
Advanced 7.3 Command Line
RM Web
154 Release 6.0 07/2010
Diagnostics 7.3 Command Line
8 Diagnostics
The diagnosis menu contains the following tables and dialogs:

X Syslog
X Event Log
X Ports (statistics, utilization, SFP modules)
X Topology Discovery
X Port Mirroring
X Device Status
X Signal Contact
X Alarms (Traps)
X Report (log file, system information)
X IP Address Conflict Detection
X Self Test
X Service Mode
In service situations, they provide the technician with the necessary

information for diagnosis.
RM Web L2E
Release 6.0 07/2010 155
Diagnostics 8.1 Syslog
8.1 Syslog
The “Syslog” dialog enables you to additionally send to one or more syslog
servers, the events that the device writes to its event log. You can switch the
function on or off, and you can manage a list of up to 8 syslog server entries.
You also have the option to specify that the device informs various syslog
servers, depending on the minimum “level to report” of the event.
Additionally, you can also send the SNMP requests to the device as events
to one or more syslog servers. Here you have the option of treating GET and
SET requests separately, and of assigning a “level to report” to the requests
to be logged.
Note: You will find the actual events that the device has logged in the “Event
Log” dialog (see on page 161 “Event Log“) and in the log file (see on
page 179 “Report“), a HTML page with the title “Event Log”.
The device evaluates SNMP requests as events if you have activated “Log
SNMP Set/Get Request” (see table 66).
RM Web
156 Release 6.0 07/2010

Setting
Frame Switches the syslog function for this On, Off
„Function“ device “On” or “Off” Off
Frame „SNMP Settings for sending SNMP requests to
Logging“ the device as events to the list of syslog
servers.
Log SNMP Creates events for the syslog for SNMP active, inactive
Get Requests. Get requests with the specified “level to inactive
report”.
Level to Report (for Specifies the level for which the device debug, notice
logs of SNMP Get creates the event “SNMP Get Request informational,
Requests) received” for the list of the syslog notice, warning,
servers. error, critical,
alert, emergency
Table 65: Syslog and SNMP Logging settings

Log SNMP Creates events for the syslog for SNMP active, inactive
Set Requests. Set requests with the specified “level to inactive
report”.
Level to Report (for Specifies the level for which the device debug, notice
logs of SNMP Set creates the event “SNMP Set Request informational,
Requests) received” for the list of the syslog notice, warning,
servers. error, critical,
alert, emergency
RM Web L2E
Release 6.0 07/2010 157

Setting
Syslog server
entries
Index Sequential number of the syslog server 1-8 -
entry in the table.
When you delete an entry, this leaves a
gap in the numbering. When you create
a new entry, the device fills the first gap.
IP address Address of a syslog server to which the Valid IPv4 address 0.0.0.0
device sends its log entries.
Port UDP port at which your syslog server 1 - 65.535 514
receives entries.
Minimum level to Minimum level to report for an event for debug, critical
report the device to sent a log entry for it to this informational,
syslog server. notice, warning,
error, critical,
alert, emergency
Active Activate or deactivate the current active (box active
syslog server entry in the table. selected), inactive
(box empty)
Table 66: Syslog server entries

Setting
Buttons
“Write” button Click on “Write” to temporarily save the -
data.
Note: If you have entered an IP

address different to 0.0.0.0 for a newly
created syslog server entry, after the
entry is written the device activates it
automatically. Click on “Load” for the
device to update the display.
“Create” button Creates a new syslog server entry in -
the list.
“Delete” button Deletes the selected syslog server -
entry/entries from the list.
Table 67: Syslog entries, buttons
RM Web
158 Release 6.0 07/2010
Note: When you activate the logging of SNMP requests, the device sends
these as events with the preset level to report notice to the list of syslog
servers. The preset minimum level to report for a syslog server entry is
critical.
To send SNMP requests to a syslog server, you have a number of options to
change the default settings. Select the ones that meet your requirements
best.
X Set the level to report for which the device creates SNMP requests as
events to warning or error and change the minimum level to report for
a syslog entry for one or more syslog servers to the same value.
You also have the option of creating a separate syslog server entry for
this.
X Only set the level to report for SNMP requests to critical or higher.
The device then sends SNMP requests as events with the level to report
critical or higher to the syslog servers.
X Only set the minimum level to report for one or more syslog server entries
to notice or lower. Then it may happen that the device sends a large
number of events to the syslog servers.
RM Web L2E
Release 6.0 07/2010 159
Figure 39: Syslog dialog
RM Web
160 Release 6.0 07/2010
Diagnostics 8.2 Event Log
8.2 Event Log
The table lists the logged events with a time stamp.

The “Load” button allows you to update the content of the event log, and with
the “Delete” button you delete the content of the event log.
Figure 40: Event log table
You have the option to also send the logged events to one or more syslog
servers (see on page 156 “Syslog“).
RM Web L2E
Release 6.0 07/2010 161
Diagnostics 8.3 Ports
8.3 Ports
The port menu contains displays and tables for the individual ports:
X Statistics table
X Utilization
X SFP Modules
8.3.1 Statistics table

This table shows you the contents of various event counters. In the Restart
menu item, you can reset all the event counters to zero using "Warm start",
"Cold start" or "Reset port counter".
The packet counters add up the events sent and the events received.
Figure 41: Port statistics table
RM Web
162 Release 6.0 07/2010
8.3.2 Utilization
This table displays the network load of the individual ports.
In the “Upper Threshold[%]” column you enter the upper threshold value for
network load. If this threshold value is exceeded, the device sets a check
mark in the “Alarm” field.
In the “Lower Threshold [%]” column you enter the lower threshold value for
network load. If the current load falls below this threshold value, the device
removes the check mark previously set.
Figure 42: Network load dialog
RM Web L2E
Release 6.0 07/2010 163
8.3.3 SFP modules

The SFP status display allows you to look at the current SFP module
connections and their properties. The properties include:
Parameter Meaning
Module type Type of SFP module, e.g. M-SFP-SX/LC
Supported Shows whether the media module supports the SFP module.
Temperature in Celsius Shows the operating temperature of the SFP
Tx Power in mW Shows the transmission power in mW
Rx Power in mW Shows the receiver power in mW
Receiver power status Shows the power level of the received signal.
– good receiver power
– limited receiver power
– insufficient receiver power
Table 68: SFP Modules dialog
Figure 43: SFP Modules dialog
RM Web
164 Release 6.0 07/2010
Diagnostics 8.4 Topology Discovery
8.4 Topology Discovery
This dialog allows you to switch on/off the topology discovery function
(LLDP). The topology table shows you the collected information for
neighboring devices. This information enables the network management
station to map the structure of your network.
The option "Show LLDP entries exclusively" allows you to reduce the number
of table entries. In this case, the topology table hides entries from devices
without active LLDP support.
Figure 44: Topology discovery
If several devices are connected to one port, for example via a hub, the table
will contain one line for each connected device.
RM Web L2E
Release 6.0 07/2010 165
Diagnostics 8.4 Topology Discovery
When devices both with and without an active topology discovery function
are connected to a port, the topology table hides the devices without active
topology discovery.
If only devices without active topology discovery are connected to a port, the
table will contain one line for this port to represent all devices. This line
contains the number of connected devices
MAC addresses of devices that the topology table hides for the sake of
clarity, are located in the address table (FDB), (see on page 80 “Filters for
MAC addresses“).
RM Web
166 Release 6.0 07/2010
Diagnostics 8.5 Port Mirroring
8.5 Port Mirroring
The port mirroring function enables you to review the data traffic at up to 8
ports of the device for diagnostic purposes. The device additionally forwards
(mirrors) the data for these ports to another port. This process is also called
port mirroring.
The ports to be reviewed are known as source ports. The port to which the
data to be reviewed is copied is called the destination port. You can only use
physical ports as source or destination ports.
In port mirroring, the device copies valid incoming and outgoing data packets
of the source port to the destination port. The device does not affect the data
traffic at the source ports during port mirroring.
A management tool connected at the destination port, e.g. an RMON probe,
can thus monitor the data traffic of the source ports in the sending and
receiving directions.
The destination port forwards all data to be sent.
On the devices PowerMICE, MACH 104, MACH 1040 and MACH 4000, the
destination port blocks received data, on all other devices, the destinations
port also forwards received data.
Select the source ports whose data traffic you want to review from the list
of physical ports by checkmarking the relevant boxes.
You can select a maximum of 8 source ports. Ports that cannot be
selected are displayed as inactive by the device, e.g. the port currently
being used as the destination port, or if you have already selected 8 ports.
Default setting: no source ports.
Select the destination port to which you have connected your
management tool from the list element in the “Destination Port” frame.
The device does not display ports that cannot be selected in the list, e.g.
the ports currently being used as source ports. Default setting: port 0.0
(no destination port).
Select “On” in the “Function” frame to switch on the function. Default
setting: “Off”.
The “Reset configuration” button in the dialog allows you to reset all the port
mirroring settings of the device to the state on delivery.
RM Web L2E
Release 6.0 07/2010 167
Diagnostics 8.5 Port Mirroring
Note: When port mirroring is active, the specified destination port is used
solely for reviewing, and does not participate in the normal data traffic.
Figure 45: Port Mirroring dialog
RM Web
168 Release 6.0 07/2010
Diagnostics 8.6 Device Status
8.6 Device Status
The device status provides an overview of the overall condition of the device.
Many process visualization systems record the device status for a device in
order to present its condition in graphic form.
Figure 46: Device State dialog (for PowerMICE)
In the "Monitoring" field, you select the events you want to monitor.
To monitor the temperature, you set the temperature thresholds in the
Basics:System dialog at the end of the system data.
RM Web L2E
Release 6.0 07/2010 169
The events which can be selected are:
Name Meaning
Power supply ... Monitor/ignore supply voltage(s).
Temperature Monitor/ignore temperature thresholds set (see on page 16 “System“) for
temperatures that are too high/too low
Module removal Monitor/ignore the removal of a module (for modular devices).
ACA removal Monitor/ignore the removal of the ACA.
ACA not in sync Monitor/ignore the non-matching of the configuration in the device and on
the ACAa
Connection error Monitor/ignore the link status (Ok or inoperable) of at least one port.
The reporting of the link status can be masked for each port by the
management (see on page 26 “Port Configuration“). Link status is not
monitored in the state on delivery.
Ring Redundancy Monitor/ignore the redundancy failing (for the HIPER-Ring, only in ring
manager operation).
On delivery, ring redundancy is not monitored.
Note: If the device is a normal ring member and not a ring manager, it
doesn't report anything for the HIPER-Ring; for the Fast HIPER-Ring and
for MRP it only reports local configuration problems.
Ring/Network Monitor/ignore the redundant coupling failing.
coupling On delivery, no monitoring of the redundant coupling is set.
For two-Switch coupling with control line, the slave additionally reports
the following conditions:
– Incorrect link status of the control line
– Partner device is also a slave (in standby mode).
Note: In two-Switch coupling, both Switches must have found their

respective partners.
Table 69: Device Status

a. The configurations are non-matching if only one file exists or the two files do not have the
same content.
Select "Generate Trap" in the "Trap Configuration" field to activate the

sending of a trap if the device state changes.
RM Web
170 Release 6.0 07/2010
Note: With a non-redundant voltage supply, the device reports the absence
of a supply voltage. If you do not want this message to be displayed, feed the
supply voltage over both inputs or switch off the monitoring (see on page 172
“Signal contact“).
RM Web L2E
Release 6.0 07/2010 171
Diagnostics 8.7 Signal contact
8.7 Signal contact
The signal contacts are used for

X controlling external devices by manually setting the signal contacts,
X monitoring the functions of the device,
X reporting the device state of the device.
8.7.1 Manual setting

Select the tab page "Alarm 1" or "Alarm 2" (for devices with two signal
contacts).
In the "Signal contact mode" field, you select the "Manual setting" mode.
With this mode you can control this signal contact remotely.
Select "Opened" in the "Manual setting" frame to open the contact.
Select "Closed" in the "Manual setting" frame to close the contact.
Application options:
X Simulation of an error during SPS monitoring.
X Remote control of a device via SNMP, such as switching on a camera.
8.7.2 Function monitoring

Select the tab “Signal contact 1” or “Signal contact 2” (for devices with two
signal contacts).
RM Web
172 Release 6.0 07/2010
In the “Mode Signal contact” box, you select the “Monitoring correct
operation” mode. In this mode, the signal contacts monitor the functions
of the device, thus enabling remote diagnosis.
A break in contact is reported via the potential-free signal contact (relay
contact, closed circuit).
X Loss of the supply voltage 1/2 (either of the external voltage supply or of
the internal voltage).1 Select “Monitor” for the respective power supply if
the signal contact shall report the loss of the power supply voltage, or of
the internal voltage that is generated from the external power supply.
X One of the temperature thresholds has been exceeded (see on page 17
“System Data“). Select “Monitor” for the temperature if the signal contact
should report an impermissible temperature.
X Removing a module. Select “Monitor” for removing modules if the signal
contact is to report the removal of a module (for modular devices).
X The removal of the ACA. Select “Monitor” for ACA removal if the signal
contact is to report the removal of an ACA (for devices which support the
ACA).
X Non-matching of the configuration in the device and on the ACA2. Select
“Monitor” ACA not in sync if the signal contact is to report the non-
matching of the configuration (for devices which support ACA).
X The inoperable link status of at least one port. The reporting of the link
status can be masked via the management for each port in the device.
Link status is not monitored in the state on delivery. Select “Monitor” for
bad connections if the signal contact is to report an inoperative link status
for at least one port.
X If the device is part of a redundant ring: the elimination of the reserve
redundancy (i.e. the redundancy function did actually switch on), (see on
page 114 “Ring Redundancy“). Select “Monitor” for the ring redundancy if
the signal contact is to report the elimination of the reserve redundancy in
the redundant ring.
Default setting: no monitoring.
1. You can install additional power supplies in a MACH4000 device, which

the device reports as P3-1, P3-2, P4-1 and P4-2 in its user interfaces. You
will find details on the power supplies in the document Installation Guide.
2. The configurations are non-matching if only one file exists or the two files
do not have the same content.
RM Web L2E
Release 6.0 07/2010 173
Note: If the device is a normal ring member and not a ring manager, it
doesn't report anything for the HIPER-Ring; for the Fast HIPER-Ring
and for MRP it only reports local configuration problems.
X The elimination of the reserve redundancy for the ring/network coupling

(i.e. the redundancy function did actually switch on). Select “Monitor” for
the ring/network coupling if the signal contact is to report the elimination
of the reserve redundancy for the ring/network coupling (see on page 123
“Preparing a Ring/Network coupling“).
Default setting: no monitoring.
Note: In two-Switch coupling, both Switches must have found their

respective partners.
8.7.3 Device status

Select the tab page “Alarm 1” or “Alarm 2” (for devices with two signal
contacts).
In the “Mode Signal Contact” field, you select the “Device status” mode.
In this mode, the signal contact monitors the device status (see on
page 169 “Device Status“) and thereby offers remote diagnosis.
The device status “Error detected” (see on page 169 “Device Status“) is
reported by means of a break in the contact via the potential-free signal
contact (relay contact, closed circuit).
8.7.4 Configuring traps

Select generate Trap, if the device is to create a trap as soon as the
position of a signal contact changes when function monitoring is active.
RM Web
174 Release 6.0 07/2010
Figure 47: Signal contact dialog
RM Web L2E
Release 6.0 07/2010 175
Diagnostics 8.8 Alarms (Traps)
8.8 Alarms (Traps)
This dialog allows you to determine which events trigger an alarm (trap) and
where these alarms should be sent.
Select "Create entry“.

In the "Address“ column, enter the IP address of the management station
to which the traps should be sent.
In the "Active“ column, you mark the entries which should be taken into
account when traps are sent.
In the "Selection“ frame, select the trap categories from which you want
to send traps.
RM Web
176 Release 6.0 07/2010
The events which can be selected are:
Name Meaning
Authentication The device has rejected an unauthorized access attempt (see on page 42
“SNMPv1/v2 Access Settings“).
Link Up/Down At one port of the device, the link to another device has been established/
interrupted.
Spanning Tree The topology of the Rapid Spanning Tree has changed.
Chassis Summarizes the following events:
– The status of a supply voltage has changed (see the System dialog).
– The status of the signal contact has changed.
To take this event into account, you activate “Create trap when status
changes” in the Diagnostics:Signal Contact 1/2 dialog.
– A media module has been added or removed (only for modular devices).
- The AutoConfiguration Adapter(ACA), has been added or removed.
- The configuration on the AutoConfiguration Adapter(ACA) does not match
that in the device.
– The temperature thresholds have been exceeded/not reached.
– The receiver power status of a port with an SFP module has changed (see
dialog Dialog:Ports:SFP Modules).
– The configuration has been successfully saved in the device and in the
AutoConfiguration Adapter(ACA), if present.
– The configuration has been changed for the first time after being saved in
the device.
Redundancy The redundancy status of the ring redundancy (redundant line active/
inactive) or (for devices that support redundant ring/network coupling) the
redundant ring/network coupling (redundancy exists) has changed.
Port security On one port a data packet has been received from an unauthorized terminal
device (see the Port Security dialog).
Table 70: Trap categories
RM Web L2E
Release 6.0 07/2010 177
Figure 48: Alarms Dialog
RM Web
178 Release 6.0 07/2010
Diagnostics 8.9 Report
8.9 Report
The following reports are available for the diagnostics:

X Log file.
The log file is an HTML file in which the device writes important device-
internal events.
X System information.
The system information is an HTML file containing system-relevant data.
Note: You have the option to also send the logged events to one or more
syslog servers (see on page 156 “Syslog“).
The following buttons are available:

X Download Switch-Dump.
This button allows you to download system information as files in a ZIP
archive (see table 71).
Select the directory in which you want to save the switch dump.
Click “Save”.
The device creates the file name of the switch dumps automatically in the
format <IP address>_<system name>.zip, e.g. for a device of the type
PowerMICE: “10.0.1.112_PowerMICE-517A80.zip”.
X Download JAR file.

This button allows you to download the applet of the Web-based interface
as a JAR file. Then you have the option to start the applet outside of a
browser.
This facilitates the device administration even when you have disabled its
web server for security reasons.
Select the directory in which you want to save the applet.
Click “Save”.
RM Web L2E
Release 6.0 07/2010 179
Diagnostics 8.9 Report
The device creates the file name of the applet automatically in the format
<device type><software variant><software version)>_<software revision
of applet>.jar, e.g. for a device of type PowerMICE with software variant
L3P: “pmL3P06000_00.jar”.
File Name Format Comments

Log file event_log.html HTML
System information systemInfo.html HTML
Event log traplog.txt Text
Device configuration (binary) switch.cfg, powermice.cfg Binary File name depends
or .mach.cfg on device type.
Internal memory extract for dump.hmd Binary
the manufacturer to improve
the product
Exception log exception_log.html HTML
Output of CLI commandsa: clicommands.txt Text
– show running-configb
– show port all
– show sysinfo
– show mac-address-table
– show mac-filter-table
igmpsnooping
Table 71: Files in switch dump archive

a: Prerequisite: a Telnet connection is available.
b: Prerequisite: you are logged in as a user with write access.
RM Web
180 Release 6.0 07/2010
Diagnostics 8.10 IP address conflict detection
8.10 IP address conflict detection
This dialog allows you to detect address conflicts the device is having with its
own IP address and rectify them (Address Conflict Detection, ACD).
Select IP address conflict detection on/off under “Status” or select the

mode (see table 72).
Mode Meaning
enable Enables active and passive detection.
disable Disables the function
activeDetectionOnly Enables active detection only. After connecting to a network or after an
IP address has been configured, the device immediately checks whether
its IP address already exists within the network.
If the IP address already exists, the device will return to the previous
configuration, if possible, and make another attempt after 15 seconds.
This prevents the device from connecting to the network with a duplicate
IP address.
passiveOnly Enables passive detection only. The device listens passively on the
network to determine whether its IP address already exists. If it detects a
duplicate IP address, it will initially defend its address by employing the
ACD mechanism and sending out gratuitous ARPs. If the remote device
does not disconnect from the network, the management interface of the
local device will then disconnect from the network. Every 15 seconds, it
will poll the network to determine if there is still an address conflict. If there
isn't, it will connect back to the network.
Table 72: Possible address conflict operation modes
X In the table the device logs IP address conflicts with its

IP address.
For each conflict the device logs:
X the time
X the conflicting IP address
X the MAC address of the device with which the IP address conflicted.
For each IP address, the device logs a line with the last conflict that
occurred.
You can delete this table by restarting the device.
RM Web L2E
Release 6.0 07/2010 181
Diagnostics 8.10 IP address conflict detection
Figure 49: IP Address Conflict Detection dialog
RM Web
182 Release 6.0 07/2010
Diagnostics 8.11 Self Test
8.11 Self Test

X activate/deactivate the RAM test for a cold start of the device.
Deactivating the RAM test cuts the booting time for a cold start of the
device.
X allow or disable a restart due to an undefined software or hardware state.
Figure 50: Self-test dialog
RM Web L2E
Release 6.0 07/2010 183
Diagnostics 8.12 Service mode
8.12 Service mode
The following devices support the service mode:

RS20/RS30/RS40 and MS20/MS30.
The service mode enables you to divide the device into 2 transmission areas.
You can thus, for example, perform test or service configurations in the field
area of a network while the ongoing operation continues in the backbone
area.
The device specifies the two transmission areas via the HIPER-Ring ports:
transmission area 1 only includes the HIPER-Ring ports of the device, while
all other ports belong to transmission area 2. When the service mode is
activated, the device creates a new VLAN in which all the ports of
transmission area 2 are members. You use the redundant supply voltage
(see below) to activate the service mode. You can view the configuration of
the newly created VLAN in the dialogs under Switching/VLAN, but the device
does not allow these entries to be changed, in order to keep the service
configuration.
By generating the VLAN, the device
X resets the port VLAN IDs for all the ports of this VLAN to the new VLAN ID
X deactivates GVRP at all ports of this VLAN. The device thus prevents
GVRP from dynamically changing the service mode port settings.
X activates “ingress filtering” at all ports of this VLAN. Thus the device only
transmits packets when the input and output ports belong to this VLAN.
RM Web
184 Release 6.0 07/2010
8.12.1 Activating the service mode

Prerequisites:
– HIPER-Ring ports are defined (HIPER-Ring or MRP-Ring).
– The supply voltage is redundant at P1 and P2.
Note: If there is no redundant voltage when activating the service mode (by
clicking on “Set” - see below), the switch immediately creates the 2 switching
areas. Depending on the settings already entered, this may interrupt your
communication to the switch.
Select the Diagnostics:Service Mode dialog.

Activate “Mode”.
Enter a number other than 0 or 1 in the “VLAN” field. Enter a VLAN ID for
a new VLAN in order to keep the settings for existing VLANs.
Click “Set”. The device outputs the following system message:
If you have verified that your communication with the Switch will not be
interrupted, click “OK” to activate the service mode.
The device will indicate in all dialogs that the service mode is activated.
RM Web L2E
Release 6.0 07/2010 185
Figure 51: Service Mode dialog - mode activated
Deactivate the redundant supply voltage.

The service mode is now activated, which the device indicates with a
checkmark in the “Status” field.
Note: Deactivate the service mode (see below) when saving the device
configuration (dialog: Basics:Load/Save:Save:On the Switch).
8.12.2 Deactivating the service mode

Reactivate the redundant voltage.
The service mode is now deactivated.
Select the Diagnostics:Service Mode dialog.
RM Web
186 Release 6.0 07/2010
Deactivate “Mode”.
Click “Set” to deactivate the service mode so that the device will no longer
switch to the service mode if the redundant voltage supply is lost.
Note: After the service mode is deactivated, the device takes on its previous
settings again.
Figure 52: Service Mode dialog - mode deactivated
RM Web L2E
Release 6.0 07/2010 187
RM Web
188 Release 6.0 07/2010
Appendix 8.12 Service mode
A Appendix
RM Web L2E
Release 6.0 07/2010 189
Appendix A.1 Technical Data
A.1 Technical Data
Switching
Size of MAC address table 8,000 (16,000 for PowerMICE and
(incl. static filters) MACH 4000)
Max. number of statically configured MAC 100
address filters
Max. number of MAC address filters learnable 512
via GMRP/IGMP Snooping
Max. length of over-long packets (from rel. 1,632 bytes
03.0.00)
VLAN
VLAN ID 1 to 4,042
Number of VLANs max. 255 simultaneously per device
max. 255 simultaneously per port
Number of VLANs in GMRP in VLAN 1 max. 255 simultaneously per device
max. 255 simultaneously per port
RM Web
190 Release 6.0 07/2010
Appendix A.2 List of RFCs
A.2 List of RFCs
RFC 768 (UDP)

RFC 783 (TFTP)
RFC 791 (IP)
RFC 792 (ICMP)
RFC 793 (TCP)
RFC 826 (ARP)
RFC 854 (Telnet)
RFC 855 (Telnet Option)
RFC 951 (BOOTP)
RFC 1112 (IGMPv1)
RFC 1157 (SNMPv1)
RFC 1155 (SMIv1)
RFC 1212 (Concise MIB Definitions)
RFC 1213 (MIB2)
RFC 1493 (Dot1d)
RFC 1542 (BOOTP-Extensions)
RFC 1643 (Ethernet-like -MIB)
RFC 1757 (RMON)
RFC 1769 (SNTP)
RFC 1867 (Form-Based File Upload in HTML)
RFC 1901 (Community based SNMP v2)
RFC 1905 (Protocol Operations for SNMP v2)
RFC 1906 (Transport Mappings for SNMP v2)
RFC 1907 (Management Information Base for SNMP v2)
RFC 1908 (Coexistence between SNMP v1 and SNMP v2)
RFC 1945 (HTTP/1.0)
RFC 2068 (HTTP/1.1 protocol as updated by draft-ietf-http-v11-spec-rev-03)
RFC 2131 (DHCP)
RFC 2132 (DHCP-Options)
RFC 2233 (The Interfaces Group MIB using SMI v2)
RFC 2236 (IGMPv2)
RFC 2246 (The TLS Protocol, Version 1.0)
RFC 2271 (SNMP Framework MIB)
RFC 2346 (AES Ciphersuites for Transport Layer Security)
RFC 2365 (Administratively Scoped Boundaries)
RFC 2570 (Introduction to SNMP v3)
RFC 2571 (Architecture for Describing SNMP Management Frameworks)
RFC 2572 (Message Processing and Dispatching for SNMP)
RFC 2573 (SNMP v3 Applications)
RM Web L2E
Release 6.0 07/2010 191
Appendix A.2 List of RFCs
RFC 2574 (User Based Security Model for SNMP v3)

RFC 2575 (View Based Access Control Model for SNMP)
RFC 2576 (Coexistence between SNMP v1, v2 & v3)
RFC 2578 (SMI v2)
RFC 2579 (Textual Conventions for SMI v2)
RFC 2580 (Conformance statements for SMI v2)
RFC 2613 (SMON)
RFC 2618 (RADIUS Authentication Client MIB)
RFC 2620 (RADIUS Accounting MIB)
RFC 2674 (Dot1p/Q)
RFC 2818 (HTTP over TLS)
RFC 2851 (Internet Addresses MIB)
RFC 2865 (RADIUS Client)
RFC 2866 (RADIUS Accounting)
RFC 2868 (RADIUS Attributes for Tunnel Protocol Support)
RFC 2869 (RADIUS Extensions)
RFC 2869bis (RADIUS support for EAP)
RFC 2933 (IGMP MIB)
RFC 3164 (The BSD Syslog Protocol)
RFC 3376 (IGMPv3)
RM Web
192 Release 6.0 07/2010
Appendix A.3 Underlying IEEE Standards
A.3 Underlying IEEE Standards
IEEE 802.1AB Topology Discovery (LLDP)

IEEE 802.1af Power over Ethernet
IEEE 802.1D Switching, GARP, GMRP, Spanning Tree
(Supported via 802.1S implementation)
IEEE 802.1D-1998, Media access control (MAC) bridges (includes IEEE 802.1p Priority
IEEE 802.1D-2004 and Dynamic Multicast Filtering, GARP, GMRP, Spanning Tree)
IEEE 802.1Q-1998 Virtual Bridged Local Area Networks
(VLAN Tagging, Port-Based VLANs, GVRP)
IEEE 802.1w-2001 Rapid Reconfiguration (RSTP)
IEEE 802.1X Port Authentication
IEEE 802.3-2002 Ethernet
IEEE 802.3ac VLAN Tagging
IEEE 802.3x Flow Control
RM Web L2E
Release 6.0 07/2010 193
Appendix A.4 Underlying IEC Norms
A.4 Underlying IEC Norms
IEC 62439 High availability automation networks; especially: Chap. 5,

MRP – Media Redundancy Protocol based on a ring topology
RM Web
194 Release 6.0 07/2010
Appendix A.5 Copyright of Integrated Software
A.5 Copyright of Integrated

Software
A.5.1 Bouncy Castle Crypto APIs (Java)

The Legion Of The Bouncy Castle
Copyright (c) 2000 - 2004 The Legion Of The Bouncy Castle
(http://www.bouncycastle.org)
Permission is hereby granted, free of charge, to any person obtaining a copy

of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
of the Software, and to permit persons to whom the Software is furnished to
do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY

KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF
CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.
RM Web L2E
Release 6.0 07/2010 195
Appendix A.5 Copyright of Integrated Software
A.5.2 Broadcom Corporation

(c) Copyright 1999-2007 Broadcom Corporation. All Rights Reserved.
RM Web
196 Release 6.0 07/2010
Readers’ Comments A.5 Copyright of Integrated Software
B Readers’ Comments
What is your opinion of this manual? Your assessment of this manual:

We are always striving to provide as
comprehensive a description of our
product as possible, as well as
important information that will ensure
trouble-free operation. Your
comments and suggestions help us
to further improve the quality of our
documentation.
Very good Good Satisfactory Mediocr Poor
e
Precise description O O O O O
Readability O O O O O
Understandability O O O O O
Examples O O O O O
Structure O O O O O
Completeness O O O O O
Graphics O O O O O
Drawings O O O O O
Tables O O O O O
Did you discover any errors in this
manual?
If so, on what page?
RM Web
Release 6.0 07/2010 197
Readers’ Comments A.5 Copyright of Integrated Software
Suggestions for improvement and

additional information:
General comments:
Sender:
Company / Department:
Name / Telephone number:
Street:
Zip code / City:
E-mail:
Date / Signature:
Dear User, Department AED

Stuttgarter Str. 45-51
Please fill out and return this page
72654 Neckartenzlingen
X as a fax to the number +49
(0)7127/14-1600 or
X by mail to
Hirschmann Automation and
Control GmbH
RM Web
198 Release 6.0 07/2010
Index A.5 Copyright of Integrated Software
C Index
A F
ACA 30, 177, 177, 177 FAQ 203
Accept SNTP Broadcast 56 Filters for MAC addresses 80
Acceptable Frame Types 101 Firmware update 23
Access with Web-based interface, password Forward Delay 134, 136
40
ACD 181 G
Address Conflict Detection 181 General 15
Advanced 147 Grandmaster 67
AF 112
Aging Time 76 H
Alarm 176 Hello Time 133, 136
Assured Forwarding 112 HIPER-Ring 100
Auto Configuration Adapter, 177 HIPER-Ring (source for alarms) 177
AutoConfiguration Adapter 177 HiVision 7
B I
BPDU Guard 135 IGMP Querier 86
Broadcast Limiter Settings 82 IGMP settings 86
IGMP Snooping 86
C Independent VLAN 95
Cable crossing 26 Industry Protocols 150
Class Selector 111 Industry protocols 7
CLI 153 Ingress Filtering 101
CLI access, password 40 IP DSCP mapping 103, 111
Clock 59 IP-DSCP value 104
Cold start (after software update) 24
Coldstart 36 J
Command Line Interface 153 Java 11
Configuring the HIPER-Ring 116 Java Runtime Environment 11
Configuring the MRP-Ring 120 JavaScript 11
Current VLAN dialog 96
L
D Link State (Port) 26
Device status 169 LLDP 165
DHCP Option 82 148 Login 12
DHCP Relay Agent 148
DHCP relay agent 148 M
Diagnose 155 Max Age 134, 136
Differentiated management access 47 Media module (for modular devices) 177
DiffServ 103 Multicasts 85
DIP switch 116
DSCP 103 N
Network Management Software 7
E NTP 55
EF 111
EtherNet/IP 152 O
Event log 161 One-Switch coupling 125
Expedited Forwarding 111 Option 82 148
RM Web
Release 6.0 07/2010 199
P Ring structure 114

Password 12, 41 Ring/Network Coupling 123
Password for access with Web-based Ring/Network coupling 100, 113, 170
interface 40 Ring/Network coupling (source for alarms)
Password for CLI access 40 177
Password for SNMPv3 access 40 Ringport 116
Per-Hop-Behavior (PHB) 111 RMON probe 167
Port configuration 26, 107 Root bridge 131
Port configuration (QoS/priority) 107 RSTP 130
Port Mirroring 167
Port priority 107, 108 S
Port security (IP-/MAC-based) 50 Security 39
Port security (source for alarms) 51 Self-test 183
Port State (Link) 26 Service Mode 184
Port Statistics 162 Set 13
Port VLAN ID 101 SFP Module (source for alarms) 177
Ports 162 SFP Modules 164
Power over ETHERNET 28 SFP status display 164
Precedence 111 Shared VLAN 95
Precision Time Protocol 59 Signal contact 172
Priority queue 104 Signal contact (source for alarm) 177
PROFINET IO 7, 150 SNMP logging 156
PROFINET IO (DCP mode per port) 151 SNMPv1/v2 access settings 42
PROFINET IO; PHY Fast Startup per Port SNMPv3 access, password 40
151 SNTP 55
PTP 59 SNTP Broadcasts 56
SNTP client 55
Q SNTP server 55
QoS/Priority 103 Software update 23
Spanning Tree 130
R Statistics table 162
RAM test 183 STP 130
Rapid Spanning Tree 130 Supply voltage 177
Rapid Spanning Tree Port Protocol 138 Switching 75
Rate Limiter 82 Switching Global Dialog 76
Rate Limiter Settings 82 Symbol 9
Read access 12 Syslog 156
Reboot 36 System time 56
Receiver power status 177
Redundancy functions 113 T
Redundancy Manager 114 Technical questions 203
Redundant 114, 130 Temperature (device) 17
Redundant coupling 100, 100, 113, 170 Temperature (SFPs) 164
Reference clock 67 Time 53
Report 179 Time management 59
Request interval (SNTP) 56, 56 Timestamp unit 59
Restart 36 Topology 165
Restore default settings 30 ToS 103
Restore state on delivery 30 Training courses 203
RFC 191 Trap 176
Ring 114 Trust mode 104
Ring Manager 114 TrustIpDscp 105
Ring Redundancy 113 Two-switch coupling 125
Ring Redundancy basic configuration 115 Two-Switch coupling with control line 125
RM Web
200 Release 6.0 07/2010
TX Hold Count 134

Type of Service 103
t
trustDot1p (global trust mode) 105
trustIpDscp (global trust mode) 105
U
Universal Time Coordinated 55
Untrusted (global trust mode) 104
UTC 55
V
VLAN 93
VLAN (HIPER-Ring settings) 118
VLAN and GOOSE Protocol 94
VLAN and redundancy rings 101
VLAN Global dialog 93
VLAN ID (network parameter of the device)
21
VLAN Mapping 103
VLAN mapping 109
VLAN mode 95
VLAN Port dialog 100
VLAN priority 103
VLAN priority 104
VLAN Static dialog 98
W
Web-based interface 11
Web-based management 11
Website 12
Write access 12
RM Web
Release 6.0 07/2010 201
Further Support A.5 Copyright of Integrated Software
D Further Support
Technical Questions and Training Courses

In the event of technical queries, please contact your local Hirschmann
distributor or Hirschmann office.
You can find the addresses of our distributors on the Internet:
www.hirschmann-ac.com.
Our support line is also at your disposal:

X Tel. +49 1805 14-1538
X Fax +49 7127 14-1551
Answers to Frequently Asked Questions can be found on the Hirschmann

internet site (www.hirschmann-ac.com) at the end of the product sites in
the FAQ category.
The current training courses to technology and products can be found
under http://www.hicomcenter.com.
Hirschmann Competence Center

In the long term, excellent products alone do not guarantee a successful
customer relationship. Only comprehensive service makes a difference
worldwide. In the current global competition scenario, the Hirschmann
Competence Center is ahead of its competitors on three counts with its
complete range of innovative services:
X Consulting incorporates comprehensive technical advice, from system
evaluation through network planning to project planing.
X Training offers you an introduction to the basics, product briefing and
user training with certification.
X Support ranges from the first installation through the standby service
to maintenance concepts.
With the Hirschmann Competence Center, you have decided against

making any compromises. Our client-customized package leaves you
free to choose the service components you want to use.
Internet:
http://www.hicomcenter.com.
RM Web L2E
Release 6.0 07/2010 203
Further Support A.5 Copyright of Integrated Software
RM Web
204 Release 6.0 07/2010

Ether RM Web L2E Rel60 en

Uploaded by

Document Information

Original Description:

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

Ether RM Web L2E Rel60 en

Uploaded by

Copyright:

Available Formats

Reference Manual

RM Web Technical Support

© 2010Hirschmann Automation and Control GmbH

Rel. 6.0 1-01-07/2010 – 14.7.10

About this Manual 7

Opening the Web-based Interface 11

6.3 Spanning Tree 130

8.12.2 Deactivating the service mode 186

B Readers’ Comments 197

D Further Support 203

About this Manual

The "Web-based Interface" reference manual contains detailed information

The "Command Line Interface" reference manual contains detailed

The “Installation” user manual contains a device description, safety

The Network Management Software HiVision/Industrial HiVision provides

The designations used in this manual have the following meanings:

WLAN access point

Router with firewall

Switch with firewall

Opening the Web-based Interface

Note: The Web-based interface uses Java software 6 (“Java™ Runtime

Figure 1: Installing Java

Start your Web browser.

The login window appears on the screen.

Figure 2: Login window

Select the desired language.

The Web site of the device appears on the screen.

Figure 3: Website of the device with speech-bubble help

The “System“ submenu in the basic settings menu is structured as follows:

Figure 4: "System" Submenu

Figure 5: Device status and display of detected alarms

Table 1: System Data

Figure 6: Availability of the media modules

Figure 7: Device View

Meaning of the symbols:

The port (10, 100 Mbit/s, 1, 10 Gbit/s) is enabled

The port is disabled by the management

The port is disabled by the management

The port is in autonegotiation mode.

The port is in HDX mode.

The port is in RSTP discarding mode (100 Mbit/s).

The port is in routing mode (100 Mbit/s).

Figure 8: Time until update

Figure 9: Network parameters dialog

Enter the parameters on the right according to the selected mode.

The HiDiscovery protocol allows you to allocate an IP address to the

Figure 10: Software dialog

1.3.1 View the software versions present on the

1.3.2 TFTP Software Update

1.3.3 HTTP Software Update

1.3.4 Automatic software update by ACA

1.4 Port Configuration

Port Type Bit Rate Autonegotiation Port Setting Duplex

Table 2: Port Settings for Ring Ports

1.5 Power over ETHERNET

Nominal power for MS20/30, MACH 1000 and PowerMICE:

Nominal power for OCTOPUS 8M-PoE:

With “Function on/off” you turn the PoE on or off.

Figure 11: Power over Ethernet dialog

1.6 Loading/Saving the

With this dialog you can:

Figure 12: Load/Save dialog

Storing the current configuration data in the ACA:

Transferring the configuration data from the ACA: