Phoenix Contact FL SWITCH SMN 6TX/2POF-PN, FL SWITCH SMN 8TX-PN, FL SWITCH SMN 6TX/2FX, 2989501, 2989543 User Manual

User manual

Smart Managed Narrow Switch

Order No. —

2016-02-15

PHOENIX CONTACT 8089_en_03

Smart Managed Narrow Switch

UM EN FL SWITCH SMN 6TX/2POF-PN

03

—

Designation Version Order No.

FL SWITCH SMN 6TX/2POF-PN 2700290

FL SWITCH SMN 8TX-PN 2989501

FL SWITCH SMN 6TX/2FX 2989543

FL SWITCH SMN 6TX/2FX-SM 2989556

User manual

Designation:

Revision:

Order No.:

This user manual is valid for:

PHOENIX CONTACT

Please observe the following notes

User group of this manual

The use of products described in this manual is oriented exclusively to:
– Qualified electricians or persons instructed by them, who are familiar with applicable

standards and other regulations regarding electrical engineering and, in particular, the
relevant safety concepts.

– Qualified application programmers and software engineers, who are familiar with the

safety concepts of automation technology and applicable standards.

Explanation of symbols used and signal words

How to contact us

Internet Up-to-date information on Phoenix Contact products and our Terms and Conditions can be

found on the Internet at:

phoenixcontact.com

Make sure you always use the latest documentation.
It can be downloaded at:

phoenixcontact.net/products

Subsidiaries If there are any problems that cannot be solved using the documentation, please contact

your Phoenix Contact subsidiary.
Subsidiary contact information is available at

phoenixcontact.com.

Published by PHOENIX CONTACT GmbH & Co. KG

Flachsmarktstraße 8
32825 Blomberg
GERMANY

Should you have any suggestions or recommendations for improvement of the contents and
layout of our manuals, please send your comments to:

[e-mail]

This is the safety alert symbol. It is used to alert you to potential personal injury
hazards. Obey all safety measures that follow this symbol to avoid possible
injury or death.

There are three different categories of personal injury that are indicated with a
signal word.

DANGER This indicates a hazardous situation which, if not avoided, will

result in death or serious injury.

WARNING This indicates a hazardous situation which, if not avoided, could

result in death or serious injury.

CAUTION This indicates a hazardous situation which, if not avoided, could

result in minor or moderate injury.

This symbol together with the signal word NOTE and the accompanying text
alert the reader to a situation which may cause damage or malfunction to the
device, hardware/software, or surrounding property.

This symbol and the accompanying text provide the reader with additional
information or refer to detailed sources of information.

Please observe the following notes

PHOENIX CONTACT

General terms and conditions of use for technical documentation

Phoenix Contact reserves the right to alter, correct, and/or improve the technical
documentation and the products described in the technical documentation at its own
discretion and without giving prior notice, insofar as this is reasonable for the user. The
same applies to any technical changes that serve the purpose of technical progress.

The receipt of technical documentation (in particular user documentation) does not
constitute any further duty on the part of Phoenix Contact to furnish information on
modifications to products and/or technical documentation. You are responsible to verify the
suitability and intended use of the products in your specific application, in particular with
regard to observing the applicable standards and regulations. All information made
available in the technical data is supplied without any accompanying guarantee, whether
expressly mentioned, implied or tacitly assumed.

In general, the provisions of the current standard Terms and Conditions of Phoenix Contact
apply exclusively, in particular as concerns any warranty liability.

This manual, including all illustrations contained herein, is copyright protected. Any
changes to the contents or the publication of extracts of this document is prohibited.

Phoenix Contact reserves the right to register its own intellectual property rights for the
product identifications of Phoenix Contact products that are used here. Registration of such
intellectual property rights by third parties is prohibited.

Other product identifications may be afforded legal protection, even where they may not be
indicated as such.

8089_en_03 PHOENIX CONTACT 3

Table of contents

1 Smart Managed Narrow Switch .................................................................................................9

1.1 Features ................................................................................................................9

1.1.1 Dimensions of the SMN .......................................................................11

1.2 Status and diagnostics indicators ........................................................................13

1.2.1 Firmware versions and their functions ..................................................14

2 Mounting and installation .........................................................................................................15

2.1 Mounting and removing the SMN ........................................................................15

2.2 Installing the Smart Managed Narrow Switch ......................................................16

2.2.1 Connecting the 24 V DC supply voltage ...............................................16

2.2.2 Signal contact ......................................................................................17

2.2.3 Assignment of the RJ45 Ethernet connectors ......................................17

2.2.4 RS-232 interface for external management ..........................................18

2.3 Grounding............................................................................................................ 18

3 Startup and functions ...............................................................................................................19

3.1 Basic settings ......................................................................................................19

3.1.1 Delivery state/default settings ..............................................................19

3.2 Using Smart mode............................................................................................... 20

3.2.1 Activating Smart mode .........................................................................20

3.3 Frame switching ..................................................................................................22

3.3.1 Store and forward ................................................................................22

3.3.2 Multi-address function .......................................................................... 22

3.3.3 Learning addresses .............................................................................22

3.3.4 Prioritization .........................................................................................23

4 Configuration and diagnostics ..................................................................................................25

4.1 Making contact between the SMN and PC for initial configuration.......................25

4.1.1 Operation with static IP addresses .......................................................25

4.2 Web-based management (WBM) ........................................................................ 27

4.2.1 General function ................................................................................... 27

4.2.2 Requirements for the use of WBM .......................................................28

4.2.3 Functions/information in WBM .............................................................28

4.3 Simple Network Management Protocol (SNMP)..................................................47

4.3.1 General function ................................................................................... 47

4.3.2 Schematic view of SNMP management ............................................... 47

4.3.3 RFC 1213 MIB - MIB II .........................................................................51

4.3.4 RMON MIB (1.3.6.1.2.1.16) .................................................................58

4.3.5 Bridge MIB (1.3.6.1.2.1.17) ..................................................................64

4.3.6 pBridgeMIB (1.3.6.1.2.1.17.6) .............................................................. 66

4.3.7 qBridgeMIB (1.3.6.1.2.1.17.7) .............................................................. 67

4.3.8 rstp MIB (1.3.6.1.2.1.17.11) .................................................................70

4.3.9 IANAifType MIB (1.3.6.1.2.1.30) ..........................................................70

FL SWITCH SMN

4

PHOENIX CONTACT 8089_en_03

4.3.10 IF MIB (1.3.6.1.2.1.31) .........................................................................70

4.3.11 pnoRedundancy MIB 1.3.6.1.4.1.24686 ..............................................73

4.3.12 Private MIBs ......................................................................................... 74

4.4 Management via local RS-232 communication interface ................................... 103

4.4.1 General function ................................................................................. 103

4.4.2 User interface functions .....................................................................104

4.4.3 Starting with faulty software (firmware) ..............................................107

5 (Rapid) Spanning Tree ...........................................................................................................109

5.1 General function ................................................................................................109

5.2 (R)STP startup................................................................................................... 110

5.2.1 Enabling (R)STP on all switches involved ..........................................110

5.2.2 Connection failure - Example .............................................................118

5.2.3 Mixed operation of RSTP and STP ....................................................119

5.2.4 Topology detection of a Rapid Spanning Tree network (RSTP) .........119

5.2.5 Configuration notes for Rapid Spanning Tree ....................................122

6 Media Redundancy Protocol (MRP) ......................................................................................133

6.1 General function ................................................................................................133

6.2 MRP manager ...................................................................................................133

6.2.1 Network examples .............................................................................134

6.3 Enabling web pages for using MRP in WBM......................................................135

6.4 Configuration of MRP ........................................................................................136

6.4.1 MRP general ...................................................................................... 136

6.4.2 MRP configuration .............................................................................137

7 Multicast filtering ...................................................................................................................139

7.1 Basics................................................................................................................139

7.2 Enabling the web pages for multicast filtering in WBM.......................................139

7.3 Static multicast groups.......................................................................................139

7.3.1 “Current Multicast Groups” web page ................................................140

7.3.2 Creating static multicast groups .........................................................140

7.3.3 Procedure for creating a multicast group ............................................142

7.4 Dynamic multicast groups..................................................................................144

7.4.1 Internet Group Management Protocol (IGMP) .................................... 144

7.4.2 “General Multicast Configuration” web page ...................................... 146

8 Virtual Local Area Network (VLAN) ........................................................................................147

8.1 Basics................................................................................................................147

8.2 Enabling the VLAN web pages in web-based management ..............................147

8.2.1 Management VLAN ID .......................................................................147

8.2.2 Changing the management VLAN ID .................................................148

Table of contents

8089_en_03 PHOENIX CONTACT 5

8.3 General VLAN configuration .............................................................................. 148

8.4 Current VLANs ..................................................................................................149

8.4.1 Static VLANs ...................................................................................... 150

8.4.2 VLAN port configuration .....................................................................151

8.4.3 VLAN port configuration table ............................................................151

8.5 Setting up static VLANs ..................................................................................... 152

8.6 VLAN and (R)STP .............................................................................................153

9 Operation as a PROFINET device .........................................................................................155

9.1 Preparing the switch for PROFINET mode ........................................................155

9.2 Switch as a PROFINET device ..........................................................................156

9.2.1 Configuration in the engineering tool .................................................. 156

9.2.2 Configuring the switch as a PROFINET device ..................................157

9.2.3 Configuration via the engineering tool ................................................158

9.2.4 PROFINET flashing function ..............................................................159

9.2.5 Device naming ...................................................................................159

9.2.6 Operating in the PROFINET environment ..........................................159

9.3 PROFINET alarms.............................................................................................159

9.3.1 Alarms in WBM ..................................................................................160

9.4 Process data communication.............................................................................160

9.4.1 Control word .......................................................................................160

9.5 PDEV function description ................................................................................. 161

9.5.1 PROFINET stack and PDEV function ................................................. 162

10 Link Layer Discovery Protocol (LLDP) ...................................................................................163

10.1 Basics................................................................................................................163

10.2 Topology representation via an engineering tool ...............................................166

11 Technical data and ordering data ...........................................................................................167

11.1 Technical data ...................................................................................................167

11.2 Ordering data.....................................................................................................170

A Appendixes.............................................................................................................................173

A 1 List of figures .....................................................................................................173

B 2 List of tables ......................................................................................................177

FL SWITCH SMN

6

PHOENIX CONTACT 8089_en_03

Smart Managed Narrow Switch

8089_en_03 PHOENIX CONTACT 9

1 Smart Managed Narrow Switch

1.1 Features

The Smart Managed Narrow Switch (Smart Managed Narrow Switch - SMN) is an indus-
trial Ethernet switch, which is available in the following versions:

– Six Fast Ethernet ports in RJ45 format and two fiber optic ports in POF format (FL

SWITCH SMN 6TX/2POF-PN)

– Eight Fast Ethernet ports in RJ45 format

(FL SWITCH SMN 8TX-PN)

– Six Fast Ethernet ports in RJ45 format and two fiber optic ports in SC multi-mode format

(FL SWITCH SMN 6TX/2FX)

– Six Fast Ethernet ports in RJ45 format and two fiber optic ports in SC single-mode for-

mat (FL SWITCH SMN 6TX/2FX-SM)

Figure 1-1 Smart Managed Compact Switch (versions)

Future-proof networks for the highest demands

Maximum performance 10/100 Mbps on each RJ45 port, 100 Mbps for fiber optic ports

Maximum availability Maximum network availability

A device design that does not use a fan, the redundant power supply, and conformance with
all relevant industrial standards in terms of EMC, climate, mechanical load, etc. ensure the
highest possible level of availability.

Quick media redundancy Redundancy can be created with standards: the (Rapid) Spanning Tree Protocol or MRP

(Media Redundancy Protocol) ensure safe operation of the entire network regardless of to­pology, even in the event of a cable interrupt.

NOTE: By default upon delivery, the Smart Managed Compact Switch switch operates in
“PROFINET” mode.

Smart Managed Compact Switch

10

PHOENIX CONTACT 8089_en_03

All information Clear information

Two LEDs per port with switchable information ensure that you always have sufficient local
information. A web server and an SNMP agent are provided for diagnostics, maintenance,
and configuration via the network. A terminal access point can be used for on-site operation.

Port mirroring Port mirroring can be used to monitor data traffic on the network connections or as an im-

portant service function.

Features and fields of application of the Smart Managed Compact Switch

– Increased network performance by filtering data traffic:

- Local data traffic remains local.

- The data volume in network segments is reduced.
– Easy network expansion and network configuration.
– Coupling of copper segments with different transmission speeds.

Automatic detection of 10 Mbps or 100 Mbps data transmission speed with auto cross-

ing for the RJ45 ports.
– Flexible use of fiber optics in SCRJ format.
– Increased availability through the use of redundant transmission paths with the shortest

switch-over times using Rapid Spanning Tree and fast ring detection. Support of vari-

ous topologies and meshed structures as well as ring topologies with special ring de-

tection.
– Switch configuration using web-based management, SNMP or locally via an RS-232 in-

terface.
– Port mirroring.
– Topology detection using LLDP (Link Layer Discovery Protocol).
– Address assignment via BootP, DCP or statically.
– Media Redundancy Protocol (MRP) supported as a client or as the MRP master. The

MRP ring can thus be created using any SMN ports.
– Can be used in the PROFINET environment.
– Operating mode can be easily changed using Smart mode.
– POF port diagnostics.

Smart Managed Narrow Switch

8089_en_03 PHOENIX CONTACT 11

1.1.0.1 View of the SMN

Figure 1-2 View of the FL SWITCH SMN 6TX/2POF-PN

– Diagnostic/status indicators

Important information is displayed directly on the device. Each port has two LEDs. The

top LED always indicates the “LINK”, the display of the bottom LED is set with the func-

tion switch.
– MODE switch for LEDs and Smart mode

The MODE switch can be used to specify which information is displayed by the second

port-specific LED. The three LEDs below the switch indicate the selected mode. This

information is then displayed by all port-specific LEDs (see also example on page 14).

In addition, this button is used to set the switch to Smart mode (for details, see “Using

Smart mode” on page 20).
– Mini-DIN RS-232

RS-232 interface in Mini-DIN format for on-site configuration via the serial interface.
– Signal contact

The floating signal contact can be connected here via a 2-pos. COMBICON connector.
– Supply voltage connection

The supply voltage can be connected via the 4-pos. COMBICON connector (redundan-

cy is optional).

1.1.1 Dimensions of the SMN

Depth from top edge of DIN rail including MEM PLUG: 175 mm

Smart Managed Compact Switch

12

PHOENIX CONTACT 8089_en_03

Depth from top edge of DIN rail without MEM PLUG: 130 mm

Figure 1-3 Housing dimensions of the FL SWITCH SMN in millimeters

56 mm

133 mm

Smart Managed Narrow Switch

8089_en_03 PHOENIX CONTACT 13

1.2 Status and diagnostics indicators

Please not e that the meaning of the LEDs differs in Smart mode (see “Using Smart mode”
on page 20).

Des. Color Status Meaning

US1 Green On Supply voltage 1 within the tolerance range

Off Supply voltage 1 too low

US2 Green On Supply voltage 2 within the tolerance range

Off Supply voltage 2 too low

FAI L Red On Signal contact open, i.e., an error has occurred

Off Signal contact closed, i.e., an error has not occurred

A Link LED is located on the front of the SMN for each port

LNK

(Link)

Green On Link active

Off Link not active

An additional LED is located on the front of the SMN for each port. The function of the second LED (MODE) for each port
can be set using the MODE switch (see also example below). There are three options (during the boot process the mode
and port LEDs are permanently on):

ACT

(Activity)

Green On Transmitting/receiving telegrams

Off Not transmitting/receiving telegrams

SPD

(Speed)

Green ON (green) 100 Mbps

Off 10 Mbps if Link LED is active (for RJ45 ports only)

FD

(Duplex)

Green On Full duplex

Off Half duplex

FO

(Fiber Optic)

Orange Off The system reserve of the optical path is >2 dB

Flashing

0.5 Hz

The system reserve of the optical path is between 2 dB and 0 dB

Flashing

2 Hz

The system reserve of the optical path is <0 dB

On Diagnostic alarm

ACT/SPD/FD Yellow Flashing Switch is in Smart mode (see “Using Smart mode” on page 20)

Smart Managed Compact Switch

14

PHOENIX CONTACT 8089_en_03

Example:

In Figure 1-4, the LED indicators have the following meaning:

A: The MODE switch has been used to select duplex mode (FD); the mode LEDs now indi­cate that port 1 is in full duplex mode.

B: The switch has been used to select the data transmission speed (SPD); the mode LEDs
now indicate that port 1 is operating at 10 Mbps, port 2 is operating at 100 Mbps, port 3 is
operating at 100 Mbps, and port 4 is not operating at all.

Figure 1-4 Example of status indicators

1.2.1 Firmware versions and their functions

Firmware version 1.00 provides the standard switch functions.

MODE

ACT SPD FD

A

B

Mounting and installation

8089_en_03 PHOENIX CONTACT 15

2 Mounting and installation

2.1 Mounting and removing the SMN

Mount the SMN on a clean DIN rail according to DIN EN 50022 (e.g., NS 35 ... from Phoenix
Contact). To avoid contact resistance, only use clean, corrosion-free DIN rails. End brack­ets (E/NS 35N, Order No. 0800886) can be mounted to the right and left of the SMN to stop
the modules from slipping on the DIN rail.

Mounting:

1 Place the module onto the DIN rail from above (1). The upper holding keyway of the

module must be hooked onto the top edge of the DIN rail. Push the module from the

front towards the mounting surface (2).

Figure 2-1 Snapping the SMN onto the DIN rail

2 Once the module has been snapped on properly, check that it is fixed securely on the

DIN rail. Check whether the positive latch is facing upwards, i.e., snapped on correctly.

Removal:

1 Pull down the positive latch using a suitable tool (e.g., screwdriver). Then swivel the

bottom of the module away from the DIN rail slightly (1). Next, lift the module upwards

away from the DIN rail (2).

Figure 2-2 Removing the SMN

1

2

A

1

2

Smart Managed Compact Switch

16

PHOENIX CONTACT 8089_en_03

2.2 Installing the Smart Managed Narrow Switch

2.2.1 Connecting the 24 V DC supply voltage

The SMN is operated using a 24 V DC voltage, which is applied via COMBICON. If required,
the voltage can also be supplied redundantly (see Figure 2-4).

Figure 2-3 Supplying the SMN using one voltage source

Redundant 24 V DC supply

Figure 2-4 Supplying the SMN using two voltage sources

If redundant power supply monitoring is active (default setting), an error is indicated if only
one voltage is applied. A bridge between US1 and US2 prevents this error message.
However, it is also possible to deactivate monitoring in web-based management or via
SNMP.

OUT

24 V DC

US1

GND

US2

GND

R1

R2

In order to reset the SMN on power up, the power supply must be interrupted for at least
3 seconds.

OUT

24 V DC

US1

GND

US2

GND

R1

R2

Mounting and installation

8089_en_03 PHOENIX CONTACT 17

2.2.2 Signal contact

The switch has a floating signal contact. An error is indicated when the contact is opened.

Figure 2-5 Basic circuit diagram for the signal contact

The indicated error states are configured in web-based management or via SNMP. For a list
of error states that can be configured, please refer to Section ““Diagnostics, Alarm Contact”
Menu” on page 44.

2.2.3 Assignment of the RJ45 Ethernet connectors

In the event of a non-redundant voltage supply, the switch indicates the voltage supply
failure by opening the signal contact. This error message can be prevented by connecting
the supply voltage to both terminal blocks in parallel, as shown in Figure 2-3, or by deac­tivating redundant power supply monitoring in web-based management or via SNMP.

Table 2-1 Pin assignment of RJ45 connectors

Pin number 10Base-T / 10 Mbps 100Base-T / 100 Mbps

1 TD+ (transmit) TD+ (transmit)

2 TD- (transmit) TD- (transmit)

3 RD+ (receive) RD+ (receive)

4- -

5- -

6 RD- (receive) RD- (receive)

7- -

8- -

R1 R2

67842015

Smart Managed Compact Switch

18

PHOENIX CONTACT 8089_en_03

2.2.4 RS-232 interface for external management

The 6-pos. Mini-DIN socket provides a serial interface to connect a local management sta­tion. It enables the connection to the management interface (for an appropriate cable,
please refer to page 170) via a VT100 terminal or a PC with corresponding terminal emula­tion. Set the following transmission parameters:

Figure 2-6 Transmission parameters and assignment of the RS-232 interface

2.3 Grounding

All Factoryline devices must be grounded so that any possible interference is shielded from
the data telegram and discharged to ground potential.

A wire of at least 2.5 mm2 must be used for grounding. When mounting on a DIN rail, the
DIN rail must be connected to protective earth ground via grounding terminal blocks. The
module is connected to protective earth ground via the metal header.

Bits per second 38400
Data bits 8
Parity None
Stop bits 1
Flow control None

Grounding protects people and machines against hazardous voltages. To avoid these
dangers, as far as possible, correct grounding, taking the local conditions into account, is
vital.

12

34

56

TxD

RxD

res.

RTSCTS

RS-232 (V.24) interface

6151007

Startup and functions

8089_en_03 PHOENIX CONTACT 19

3 Startup and functions

3.1 Basic settings

3.1.1 Delivery state/default settings

By default upon delivery or after the system is reset to the default settings, the following
functions and properties are available:

– The password is: “private”
– All IP parameters are deleted. The switch has no valid IP parameters:

IP address: 0.0.0.0

Subnet mask: 0.0.0.0

Gateway: 0.0.0.0
– PROFINET is activated as the addressing mechanism.
– All available ports are activated with the following parameters:

- Autonegotiation

- Autocrossing
– All counters of the SNMP agent are deleted.
– The web server, SNMP agent, and RS-232 interface are active.
– Port mirroring, Rapid Spanning Tree, broadcast limiter, and MRP are deactivated.
– The alarm contact only opens in the event of non-redundant power supply.
– The transmission of SNMP traps is deactivated and the switch has no valid trap desti-

nation IP address.
– The aging time is set to 40 seconds.
– The WBM refresh interval is set to 30 seconds.
– The switch is in “PROFINET” mode.
– The transmission of SNMP traps is deactivated and the switch has no valid trap desti-

nation IP address.

The basic Ethernet functions do not have to be configured and are available when the
supply voltage is switched on.

The procedure for switching to the supported operating modes via Smart mode is de­scribed in Section “Using Smart mode” on page 20.

The aging time is set using the “dot1dTpAgingTime” MIB object (OID 1.3.6.1.2.1.17.4.2).
The available setting range is 10 to 825 seconds. For static configuration, an aging time
of 300 seconds is recommended.

Smart Managed Compact Switch

20

PHOENIX CONTACT 8089_en_03

3.2 Using Smart mode

Smart mode enables the user to change the operating mode of the switch without having
access the management interface.

The FL SWITCH SMN offers the following setting options via Smart mode:
– Reset to the default settings
– Set PROFINET mode
– Exit Smart mode without changes

3.2.1 Activating Smart mode

The mode button is used to call/exit Smart mode and to select the desired setting. The three
mode LEDs indicate the mode that is currently set and the mode which will apply when ex­iting Smart mode.

3.2.1.1 Calling Smart mode

• Following the switch boot phase, as soon as the three mode LEDs go out, press and

hold down the mode button for more than five seconds. If Smart mode is active, the

three LEDs will flash.

• When Smart mode is started, the switch is initially in the “Exit without changes” state.

3.2.1.2 Selecting the desired setting

• To select the various settings, press the mode button briefly and select the desired op-

erating mode.

3.2.1.3 Exiting Smart mode

• To exit, press and hold down the mode button for at least five seconds. The previously

selected operating mode is saved.

3.2.1.4 Possible operating modes in Smart mode

The FL SWITCH SMN supports the selection of the following operating modes in Smart
mode (see also example below):

Table 3-1 Operating modes in Smart mode

Mode ACT

LED 1

SPD

LED 2

FD

LED 3

Exit Smart mode without changes Off Off On

Reset to the default settings Off On Off

Set PROFINET mode Off On On

Startup and functions

8089_en_03 PHOENIX CONTACT 21

Example:

When the switch is in Smart mode, exiting Smart mode triggers the following action:

Example A: Resetting to the default settings

Example B: Setting PROFINET mode

Figure 3-1 Example of Smart mode

MODE

ACT SPD FD

A

B

Smart Managed Compact Switch

22

PHOENIX CONTACT 8089_en_03

3.3 Frame switching

The FL SWITCH SMN operates in store-and-forward mode. When receiving a data packet,
the switch analyzes the source and destination addresses. The switch stores up to 4000
MAC addresses in its address table with an adjustable aging time of 10 to 825 seconds.

3.3.1 Store and forward

All data telegrams received by the switch are stored and checked for validity. Invalid or
faulty data packets (>1522 bytes or CRC errors) and fragments (<64 bytes) are rejected.
Valid data telegrams are forwarded by the switch.

3.3.2 Multi-address function

The switch learns all the source addresses for each port. Only packets with:
– Unknown source addresses
– A source address for this port or
– A multicast/broadcast address

in the destination address field are forwarded via the relevant port. The switch can learn up
to 4000 addresses. This is important if more than one termination device is connected to
one or more ports. Several independent subnetworks can be connected to one switch.

3.3.3 Learning addresses

The FL SWITCH SMN independently learns the addresses for termination devices, which
are connected via this port, by evaluating the source addresses in the data telegrams. When
the FL SWITCH SMN receives a data telegram, it forwards this data telegram to only that
port that connects to the specified device (if the address could be learned beforehand).
The FL SWITCH SMN can learn up to 4000 addresses and store them in its table. The
switch monitors the age of the learned addresses. The switch automatically deletes from its
address table address entries that exceed a specific age (default: 40 seconds, adjustable
from 10 to 825 seconds, aging time).

All learned entries are deleted on a restart.
A link down deletes all the entries of the affected port.

A list of detected MAC addresses can be found in the MAC address table (see Section
““Diagnostics, Mac Address Table” menu” on page 46). The MAC address table can be
deleted via the “Clear” button.

The aging time is set using the “dot1dTpAgingTime” MIB object (OID 1.3.6.1.2.1.17.4.2).
The available setting range is 10 to 825 seconds. For static configuration, an aging time
of 300 seconds is recommended.

Startup and functions

8089_en_03 PHOENIX CONTACT 23

3.3.4 Prioritization

The switch supports four priority queues for adjusting the internal packet processing se­quence (traffic classes according to IEEE 802.1D). Data telegrams that are received are as­signed to these classes according to the priority of the data packet, which is specified in the
VLAN/prioritization tag:

– Data packets with the value “0” or “1” in the priority field are transmitted with the lowest

priority (default).
– Data packets with the value “2” or “3” in the priority field are transmitted with the second

lowest priority.
– Data packets with values between “4” and “5” in the priority field are transmitted with the

second highest priority by the switch.
– Data packets with values between “6” and “7” in the priority field are transmitted with the

highest priority by the switch.

Processing rules

The switch controller in the FL SWITCH SMN forwards received packets to one of the re­ceive queues according to the following decisions:

– BPDU packets are always assigned to the high-priority queue.
– Packets with VLAN/prioritization tag are forwarded according to the queues listed

above.
– All remaining data is assigned to the low-priority queue.

3.3.4.1 Class of Service (CoS)

Class of Service refers to a mechanism used to take into consideration the value of the pri­ority field (values 1 to 7) in VLAN data packets with a tag. The switch assigns the data
streams in various processing queues, depending on what priority information is contained
in the CoS tag. The switch supports four internal processing queues.

3.3.4.2 Quality of Service (QoS)

Quality of Service affects the forwarding and handling of data streams and results in individ­ual data streams being given differential treatment (usually preferential). QoS can be used,
e.g., to guarantee a transmission bandwidth for individual data streams. The switch uses
QoS in connection with prioritization (see CoS). The broadcast limiter can also be referred
to as a QoS function.

3.3.4.3 Flow control

Flow control can provide advantages during transmission in large network topologies in
which peak loads are to be expected. The switch supports flow control.

Smart Managed Compact Switch

24

PHOENIX CONTACT 8089_en_03

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 25

4 Configuration and diagnostics

The Smart Managed Nar row sw itch (SMN) of fers se veral user in terfa ces for acc es sing con ­figuration and diagnostic data. The preferred interfaces are the web interface and SNMP in­terface. These two interfaces can be used to make all necessary settings and request all in­formation.
Access via the RS-232 interface only enables access to basic information and supports
basic configura tio n. Howev er, t he RS- 232 int erfa ce also enables f ir mware up date v ia TFTP
in the event of faulty firm ware.

4.1 Making contact between the SMN and PC for initial
configuration

4.1.1 Operation with static IP addresses

To enable the SMN to be accessed using the desired IP address, make sure that the com­puter and the SMN are in the same IP subnetwork. To do this, for initial contact your com­puter must be configured so that contact is possible. The following screenshots were cre­ated under Windows XP Professional.

Settings a re no t aut omat ic all y sav ed p ermane nt ly. T he act i ve con figu ra tion can be s ave d
permanently by selecting “Save current configuration” on the “Configuration Manage­ment” web page. Additional saving options ar e also available via SNMP or RS-232.

Please note that the switch does not support supernetting or classless interdomain rou t­ing.

Smart Managed Compact Switch

26 PHOENIX CONTACT 8089_en_03

To set the IP parameters, open the Properties tab for your network adapter. Activate “Inter­net Protocol (TCP/IP)” and then click on “Properties”.

Figure 4-1 Properties dialog box for the network card

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 27

In the dialog box that opens, click the “Use the following IP address” radio button.

Figure4-2 “Internet Protocol (TCP/IP) Properties” dialog box

Enter the desi red IP addr ess of y our c ompu ter (not tha t o f t he SMN) i n the “I P a ddress ” fi eld
and the corresponding subnet mask. Close the dialog box with “OK”.

The device can now be accessed via a web browser. In the address line of your browser,
enter the IP address of the SMN in th e following format:

http://xxx.xxx.xxx.xxx

After entering the IP address in the browser, an overview page is displayed for the SMN
where no login is required.

After the correct user name and password have been entered, the device configuration
pages are loaded.

4.2 Web-based management (WBM)

4.2.1 General function

Online diagnostics The user-fri endly web-bas ed management i nterf ace can be us ed to manage th e switch f rom

anywhere in the net wor k using a standa rd brows er. Comp rehe nsive c onfi gura tion an d diag ­nostic functions are clearly displayed on a graphical user interface. Every user with a net-

Smart Managed Compact Switch

28 PHOENIX CONTACT 8089_en_03

work connection t o the device has read access to that device via a browser. A wide range
of information about the device itself, set parameters, and the operating state can be
viewed.

4.2.2 Requirements for the use of WBM

As the web server operates using the Hyper Text Transfer Protocol, a standard browser can
be used. Access is via the URL “http://IP address of the device”.
Example: http://172.16.29.112
For full operation of the web pages, the browser must support JavaScript 1.2 and Cascad­ing Style Sheets Level 1. We recommend the use of Microsoft Internet Explorer 6.0.

4.2.2.1 Structure of the web pages

The web pages are divided into four areas:
– Device type and device logo
– Device name (specified by the user) and loading time, to avoid mix-ups
– Navigation tree on the left-hand side
– Information tables on the right-hand side, which contain current device information

during runtime.

4.2.2.2 Password concept

After having ent ered t he v ali d password , no f urt her en try of th e pas sword is neces sary for a
period of 300 s (default). After this period of time has elapsed or aft er clicking on “Logout”,
the passwor d must be re-entered.

The concept is valid for the first ten users logged in simultaneously. All other users must
confirm ea ch co nfiguration modification by enteri ng the passwor d, u ntil less th an ten users
are logged in.

4.2.3 Functions/information in WBM

The navigation tree provides direct access to the following four areas:
– General Instructions

Basic information about WBM.

Modifications can only be made by entering the valid password. By default upon delivery,
the password is “p rivate”.

For security reasons, we recommend changing the existing password to a new one
known only to you.

WBM can only be called using a valid IP address. By default upon delivery, the switch has
no valid IP address.

Settings are n ot automat ical ly saved p ermanent ly. If the act ive conf igurati on has not been
saved, a flashing floppy disk icon appears in the top-right corner in WBM. The icon is
linked to the “Configuration Management” web page. The active configuration can be
saved permanently by selecting “Save current configuration” on this web page.

If the connec tion is interrupted during the transmission of web pages, a waiting time of
several minutes is required before the web interface can be accessed again.

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 29

– Device Information

General device information .

– General Configuration

Device configuration/device as a network device.

– Switch Station

Device-specific configuration and diagnostics.

4.2.3.1 General instructions

Figure4-3 “Information” web page for the SMN

General instructions

Contains a brief description of WBM and a navigation tree (site map), which is linked to
every page of WBM.

Smart Managed Compact Switch

30 PHOENIX CONTACT 8089_en_03

4.2.3.2 Device information

Figure 4-4 “Device Information” web page

“General” menu

Here, you will find a range of static information about the device and the manufacturer.

“Technical Data” menu

Here, you will find the most important technical data.

“Hardware Installation” menu

Here, you will find a connection diagram for connecting the redundant power supply and the
signal contact.

“Local Diagnostics” menu

Here, you will find a description of the meaning of the switchable diagnostics and status in­dicators.

“Serial Port” menu

Here, you will find the transmission parameters for serial communication.

4.2.3.3 General configuration

“IP Configuration” menu

This page displays the set IP parameters and addressing mechanism.

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 31

To change the IP parameters via WBM, “Static” must be selected.

Figure4-5 “IP Configuration” web page

IP address assignment

“PROFINET” is activated by default upon delivery. The switch waits for startup by a PROF­INET controller, which also assigns the IP addresses.

– Static Assignment

The switch can be accessed using the set IP address and does not send any kind of
requests for the receipt of IP parameters.

– Bootstrap Protocol (BootP)

The switch sen ds a maximum of three Boo tP requests after every res ta rt a nd r eceives
a BootP reply with IP parameters. If there is no BootP reply, the switch starts after the
third request without IP configuration.

“System Identification” menu

This menu is used to display or modify user-specific device data, e.g., location, device
name or function. This device data is also available in SNMP.

Figure4-6 “System Identification” menu

While the switch waits for an IP address to be assigned (maximum of three BootP re­quests) the mo de LED which has been selected via the mode button w ill also flash.

Modifications to the IP parameters only take effect once the configuration is saved and a
restart is then performed.

Smart Managed Compact Switch

32 PHOENIX CONTACT 8089_en_03

“SNMP Trap Configuration” menu

SNMP agent The “Sending traps” function can be globally enabled/disabled here.

Figure 4-7 “SNMP Trap Configuration” web page

Trap destination This part of the table is used to view or modify the IP addresses of the two trap receivers.

Trap configuration Sending of traps can be individually enabled/disabled here.

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 33

SNMP trap

Connection test

Once the “Sending traps” function has been activated and the trap managers have been de­fined using t he IP addresses, t est t rap s can now be sen t usi ng “ Exec ute” t o t est t he com mu ­nication pat h from the switch to the trap receiver.

“Software Update” menu

This page is u sed to view or modi fy the parameters for a s oft ware update and to trigger the
update.

Figure4-8 “Software Update” web page

A reset is not carried out automatically following a firmware update. The desired option
can be selected in WBM.

Please make su re th at t he “TF TP Ser ver” s ervic e prog ram i s acti vate d in th e Fa ctory Ma n­ager toolbar.

You can moni tor the download in the F actory Manager m essage window (25%, 50%,
75%, 100%). Always wait until all the LE Ds light up after approximately two minutes and
the device is available again after booting.

It is not ensured that all existing configu ration data will be retained after a firmware up­date/downgra de. Theref ore, pl ease check the confi guratio n settin gs or res et the dev ice to
the default delivery settings.

NOTE:

A voltage failure during a firmware update results in the destruction of the firmware on the
SMN. An update via TFTP is required, see “Starting with faulty soft ware (firmware)” on
page 107.

Smart Managed Compact Switch

34 PHOENIX CONTACT 8089_en_03

“Change Password” menu

Here, you can enter the existing password and then change it to a new one known only to
you. By default upon delivery, the password is “private” (please note that it is case-sensi­tive). For security reasons, the input fields do not display your password, but instead
“*******” is displayed.

Figure 4-9 “Change Password” web page

“User Interfaces” menu

The following actions can be performed here:
– Activating/deactivating the web server.
– Activating/deactivating the SNMP agent.
– Setting the refresh interval f or t he a uto mat i c updating of the web pages. Her e, y ou c an

also set the refresh interval for automatic updating of different web pages. If the interval
is set to “0”, the pages will no longer be updated.

Figure 4-10 “User Interfaces” web page

The password mus t be b et ween four and t wel ve cha ract er s l ong. Note t ha t the pa sswor d
is always transferred via the network in unencrypted format.

Forgotten your password?
Call the Pho en ix Con tact pho ne nu mber l iste d in t he Ap pend ix, m akin g sure you have the
device serial number and MAC add ress to hand.

Automatic updating of web pages is only possible when using Internet Explorer Version

5.5 or later.

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 35

“Operating Mode” menu

Operation as a
PROFINET device

In this menu, select whether the switch is to operate as a PROFINET device. For additional
information about operation as a PROFINET device, see Section 9 “Operation as a PROF ­INET device”.

Figure4-11 “Operating Mode” web page

“Configuration Management, General” menu

This table is used to view all parameters that are required to save the active configuration or
load a new configuration, and to modify them (by entering a valid password). It can also be
used to restart t he s yst em with the relevant configuration or to reset the SMN t o the default
state upon delivery.

Smart Managed Compact Switch

36 PHOENIX CONTACT 8089_en_03

Figure 4-12 “Configuration Management” web page

Possible states for “Status of current configuration”:

– The configuration has been modified but not saved (also indicated by the flashing flop-

py disk icon).
– Saving the current configuration.
– Th e current configuration is equal to the saved one in the non-volatile memory of the

switch.
– The current configuration was saved.

Save current

configuration

The active conf iguration together w ith t he cor resp on ding c onf igura tion name can be save d
here by entering a valid password.

Figure 4-13 “Save current configuration” web page

If the new configuration is not activated by a reset after a configuration download, the
“Save current configuration” command overwrites the previously loaded configuration
and instead saves the active configuration of the SMN.

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 37

Set default upon delivery This option can be used to reset the switch to its default settings (default upon delivery) by

entering a valid password.

Figure4-14 “Set default upon delivery” web page

Load the last stored con-

figuration

This option can be used to reactivate the last configuration stored on the device. All modifi­cations made to the configuratio n since it was last saved are lost.

Figure4-15 “Load the last stored configuration” web page

“Configuration Management, File Transfer” menu

Configuration file transfer This option can be used to save your device configuration on a PC or to operate the switch

using a stored configuration.

Figure4-16 “File Transfer” web pa g e

WBM can only be called using a valid IP address. Once the switch h as been reset to it s
default settings, it has no valid IP a ddress an d the addr ess ing mech anism is se t to BootP.

When a configuration is uploaded from the SMN to a PC, the last saved version is trans­mitted. Should you wish to transmit the active configuration, it is recommended that you
save it again beforehand (“Save current configuration” function).

When a configuration is downloaded from the PC to a SMN, the new configuration is only
activated once the switch has been reset.

The use of a configuration file does not affect an existing (“old”) password.

Smart Managed Compact Switch

38 PHOENIX CONTACT 8089_en_03

Device replacement

“Configuration Management, Memory Plug” menu

Memory plug

Figure 4-17 “Memory Plug” web page

Following a “host to device” file transfer, some configuration modifications will take effect
immediately, others wil l only take effect after a reset.
The SMN must be reset in order to ensure consistency.

Configuration using a configuration file is used when replacing devices. To duplicate de­vices using a configuration file, observe the following:

– Create a point-to-point connection between an SMN and the management station.
– Load the configuration file on the SMN.
– Reset the SMN.
– Adjust the IP parameters.
– Save the configuratio n (“Save current configuration” function) .
The duplicated sw it ch can now be operated i n th e network using the adjusted IP param-

eters.

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 39

Configuration comparison Here you can compare the configuration on the memory plug with the configuration in the

SMN memory. The result is displayed in text format.

Figure4-18 “Configuration comparison” web page

Clear memory plug Here, you can delete the memory plug by entering a valid password.

Figure4-19 “Clear Memory Plug” web page

4.2.3.4 Switch station

“Services” menu

Figure4-20 “File Transfer” web pa g e

Reboot To trigger a reboot via the web interface, enter a valid password. Save the configuration be-

forehand, so t hat configuration modifications are retained or can be activated via a restart.

If you replace a memory plug with another memory plug within a few seconds, the config­uratio n comparison mus t be updat ed manuall y.

Smart Managed Compact Switch

40 PHOENIX CONTACT 8089_en_03

“Ports, Port Table” menu

Overview of all available ports. Clicking on the relevant port number opens a port-specific
page (“Port Configuration”).

Figure 4-21 “Port Table” web page

“Ports, Port Configuration Table” menu

This menu provides an overview of the important configuration settings for all ports and also
offers t he option of set ting th e stat us, tra nsmission mo de, and lin k monito ring f unction f or al l
existing ports.

Figure 4-22 “Port Configuration Table” web page

When setting the transmi ssion mo d e, ma ke sure that the same setti ngs ha ve been made
at both ends of the connection. If the settings are not the same, this can result in increased
collisions or CRC errors and can adversely affect network performance.

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 41

“Ports, Port Configuration” menu

Offers individual configuration options for each port.

Figure4-23 “Port Configuration” web page

4.2.3.5 Using POF diagnostics

The following states can be displayed under “Transceiver status”:

– “POF-SCRJ Interface i s OK” ( The syste m reser ve is gre ater t han 2dB and is displ ayed

under “RX system reserve”.)
– “POF-SCRJ Interface t he syst em reser ve is l ow” (The s ystem r eserv e is les s than 2dB,

but greater th an 0 dB.)
– “POF-SCRJ Interface t he s yst em rese r ve is exha usted” (No sy st em r ese rve a vailabl e -

the received optical power is below the required minimum value.)

Smart Managed Compact Switch

42 PHOENIX CONTACT 8089_en_03

Figure 4-24 “Diagnostics” web page

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 43

“Ports, Port Statistics” menu

This menu provides detailed statistical information about the volume of data for each indi­vidual port. On this page, additional counter states can be set to zero for all ports.

Figure4-25 “Port Statistics” web page

Smart Managed Compact Switch

44 PHOENIX CONTACT 8089_en_03

“Ports, Port Mirroring” menu

Activation/deactivat ion and setting of port mirroring. Port mir roring is used to passively rea d
input or output data that is being transmitted via a selected port. To do this, a measuring in­strument (PC) is connected to the destination port, which records the data, yet mu st not it­self be activated.

Figure 4-26 “Port Mirroring” web page

“Diagnostics, Alarm Contact” Menu

Here, you can set whether and for which events the signal contact (alarm contact) is used.

Figure 4-27 “Alarm Contact” web page

WBM prevents the same ports from being set, i.e., the source port and destination port
must differ.

The port capa city i s calcul ated a ccordi ng to the set t r ansmissi on parame ters . Exampl e: A
source port is operated at 100 Mbps and reaches a capacity of 5%. The destination port
is operated at 10 Mbps. Therefore, with the same volume of data, the destination port
reaches a capacity of 50%.

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 45

“Diagnostics, Event Table” menu

Here, you will find a list of the latest important events. The list contains up to 200 entries.
From the 200th entry onwards the oldest entries are overwritten (FIFO principle - first in, first
out). If old entries are overwritten by new entries, a corresponding note is displayed under
the event table.

Figure4-28 “Event Table” web page

The “Clear” button can be used to delete entries in the event table.
The following events are listed in the event table:

– Event Table cleare d.
– Password has been changed.
– Password has not been changed successfully.
– Configuration has been saved.
– Th e configuration has been modified the first time after the last storin g.
– Configuration File Transfer successfully executed.
– Configuration File Transfer was not successfully executed.
– Firmware Update was successfully executed.
– Firmware Update was not successfully executed.
– Link up at port xy.
– Link down at port xy.
– Enabling port xy.
– Disabling port xy.
– RSTP enabled.
– RSTP disabled.
– RSTP topology changed.
– RSTP elected this switch as new root.
– Power Supply US1 lost.
– Power Supply US2 lost.
– P ower Supply US1 and US2 are connected now.
– LLDP Agent enabled.
– LLDP Agent disabled.
– LLDP recognized n ew neighbor at port xy.
– LLDP neighborhood information become obsolete at port xy.
– LLDP neighborhood information changed at port xy.
– MRP Client enabled/MRP disable.

Smart Managed Compact Switch

46 PHOENIX CONTACT 8089_en_03

– MR P Manager detects a loop failure enabled/MRP disable.
– MRP Ring failure detected/MRP Ring closed (OK).
– MRP Manager detects a closed loop.

“Diagnostics, Mac Address Table” menu

Here, you will find a list of which MAC address has been detected at which switch port, and
its VLAN ID. If no packets are received at a port for a duration longer than the aging time,
the entry is deleted.

Figure 4-29 “Mac Address Table” web page

The “Clear” button can be used to delet e entries in the MAC address table.

“LLDP General” menu

For information about LLDP, please refer to Section “Link Layer Discovery Protocol (LLDP)”
on page 163.

4.2.3.6 (Rapid) Spanning Tree

The Rapid/Spanning Tree Protocol (RSTP) is a standardized method (IEEE 802.1w/IEEE

802.1d). For information, please refer to Section 5 “(Rapid) Spanning Tree”.

4.2.3.7 Media Redundancy Protocol

The Media Redundancy Protocol is part of PROFINET standard IEC 61158 and is de­scribed in Section 6 “Media Redundancy Protocol (MRP)”.

“Broadcast Limiter” menu

The “Broadcast Limiter” function can be used to limit broadcast and multicast traffic to an
adjustable level in order to prevent a loss in performance on termination devices.

If the conf ig urab l e b andw i dth l imit is reached, further broad cast or mul t i cast p a ckets are re­jected. The set bandwidth applies for the incom ing data traffic of each individual port.

The following conf iguration options are provided via WEB and SNMP:
– Activation/deactivation of broadcast traffic limiting on all ports
– Activation/deactivation of multicast traffic limiting on all ports

The bandwidth is selected from a dro p-down list and is specified in kbps or Mbps.

Figure 4-30 “Broadcast Limiter” menu

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 47

4.3 Simple Network Management Protocol (SNMP)

4.3.1 General function

SNMP is a manufacturer-independent standard for Ethernet management. It defines com­mands for reading and writing information, and defines formats for error and status mes­sages. SNMP is also a structure d model th at consi sts of agen ts, thei r releva nt Manag ement
Information Base (MIB) and a manager. The manager is a software tool that is executed on
a network management station. The agents are located inside switches, BK modules, rout­ers, and other devices that support SNMP. The task of the agents is to collect and provide
data in the MIB. The mana ger r egu larl y req u ests a nd d i spl ays t his i n format ion. Th e dev ices
can be configured by writing data from the manager to the MIB. In the event of an emer­gency, the agents can also send messages (traps) directly to the manager.

4.3.2 Schematic view of SNMP management

Figure4-31 Schematic view of SNMP

All configuration modifications, which are to take effect after a SMN restart, must be saved
permanently us ing the “fl WorkFWCtrlConfS ave” object.

Smart Managed Compact Switch

48 PHOENIX CONTACT 8089_en_03

SNMP interface

All managed Factoryline components have an SNMP agent. This agent of an
FL SWITCH SMN manages Management Information Base II (MIB 2) according to RFC
1213, RMON MIB, Bridge MIB, If MIB, Etherlike MIB, Iana-address-family MIB, IANAifType
MIB, SNMPv2 MIB, SNMP-FRAMEWORK MIB, P Bridge MIB, Q Bridge MIB, RSTP MIB,
LLDP MIB, and private SNMP objects from Phoenix Contact (FL-SWI TCH-M MIB).

Network management stations, such a s a PC with Factory Man ager, can read and modify
configuration and diagnostic data from n etwork devices via t he Simple Network Manage­ment Protocol. In add ition, any SNMP tools or network manageme n t t ool s can be used to
access Factoryline products via SNMP. To do this, the MIBs supported by the relevant de­vice must be made available to the SNMP management tools.

On the one hand, these are globally valid MIBs, which are specified and described in RFCs
(Request for Comments). This includes, for example, MIB2 according to RFC1213, which
is supported by al l SNMP-compatibl e network devices. On the other hand, ma nufacturers
can specify their own SNMP objects, which are then assigned to a private manufacturer
area in the lar ge SNMP obj ect tre e. Manufactu rers are th en responsi ble for the ir own pri vate
(enterpr ise) area s, i.e. , they mu st ens ure that on ly one ob ject is a ssign ed to an obj ect ID ( ob­ject name and parameters) and can be published. If an object is no longer needed, it can be
labeled as “expired”, but it cannot be reused with other parameters under any circum­stances.

Phoenix Contac t provides notification of ASN1 SNMP objects by publishing their descrip­tions on the Internet.

Reading SNMP objects is not password-protected. However, a password is required for
read access in SNMP, but this is set to “public”, which is usual for network devices, and can­not be modified. By default upon delivery, the password for write access is “private” and can
be changed by the user.

Another benefit for the user is the option of sending traps using the Simple Network Man­agement Protocol.

Management Information Base (MIB)

Database which contains all the data (objects and variables) required for network manage­ment.

Agent

An agent is a sof tware tool which collects data from the network device on which it is in­stalled and transmits this data on request. Agents reside in all managed network compo­nents and transmit the values of specific settings and parameters to the management sta­tion. On a request of a manager or on the occurrence of a specific event, the agent transmits
the colle cted information to the management station.

Traps

Traps are spontaneous SNMP alarm or information messages that are sent by an SNMP­compatibl e de vice w hen spec ifi c even ts o ccur. Traps a re tr ansmi tted with ma ximum prio rit y
to various addresses, if required, and can then be displayed by the management station in
plain text. The IP a ddr esses that are to receive these trap s (trap target s/ receivers) must be
set by the user on the relevant device.

SNMP, the web interface, and the serial terminal all use the same password, which can
be changed by the user.

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 49

trapPasswd

trapFWHealth

trapFWConf

trapPowerSupply

trapRstpRingFailure

trapManagerConnection

OID 1.3.6.1.4.1.4346.11.11.3.0.1
Description Sent to the defined trap receivers on each modification or attempted modification of the de-

vice password an d con tains information a bout the status of the last modification or at ­tempted mod if ica tion .

OID 1.3.6.1.4.1.4346.11.11.3.0.2
Description Sent on each firmware-related modification and contains additional information about the

firmware status.

OID 1.3.6.1.4.1.4346.11.11.3.0.3
Description Sent each time the configuration is saved and informs the management station that the

configuration has been saved successfully.
This trap is sent in the event of configuration modifications (port name, port mode, device
name, IP address, trap receiver address, port mirroring, etc.), which are not yet saved per­manently. T he trap a lso provi des a wa rning tha t, if not sa ved per manentl y, the chang es wil l
be lost on a reset.

OID 1.3.6.1.4.1.4346.11.11.3.0.4
Description Sent each time the redundant power supply fails.

OID 1.3.6.1.4.1.4346.11.11.3.0.6
Description Sent in the event of a link interrupt i n the redundant RSTP ring.

OID 1.3.6.1.4.1.4346.11.11.3.0.99
Description Trap to test the connection between the SNMP age nt and the network management sta-

tion.

FL SWITCH SMN 6TX/2POF-PN / 8TX-PN

50

PHOENIX CONTACT 8089_en_03

4.3.2.1 Tree structure of the MIB

Figure 4-32 Tree structure of the MIB

1 system

2 interfaces

3 address translation

4 ip

5 icmp

6 tcp

7 udp

10 transmission

2 mgmt

1 mib-2

1 internet

1 iso

3 org

6 dod

4 private

1 enterprises

4346 phoenixContact

11 snmp

16 rmon

17 dot1dBridge

31 ifMib

8 egp

6 snmpV2

3 snmpModules

1 snmpMIB

30 ianaifType

5 security

0 std

8802 iso8802

1 ieee802dot1

1 ieee802dot1mibs

2 lldpMIB

6146b029

Not all devices support all object classes. If an unsupported object class is requested,
"not supported" is generated. If an attempt is made to modify an unsupported object class,
the message "badValue" is generated.

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 51

4.3.3 RFC 1213 MIB - MIB II

4.3.3.1 System group (1.3.6.1.2.1.1)

The system group has mandatory characters for all systems. It contains system-specific
objects. If an agent does not have a value for a variable, the response is a string with
length 0.

(1) system
– (1) sysDescr
– (2) sysObjectID
– (3) sysUpTime
– (4) sysContact
– (5) sysName
– (6) sysLocation
– (7) sysServices
– (8) sysORLastChange
– (9) sysORTable

sysDescr

sysObjectID

sysUpTime

OID 1.3.6.1.2.1.1.1.0

Syntax Octet string (size: 0 - 255)

Access Read

Description A textual description of the entry. The value should contain the full name and version num-

ber of:

- Type of system hardware

- Operation system software

- Network software
The description may only consist of ASCII characters that can be printed.

OID 1.3.6.1.2.1.1.2.0

Syntax Object identifier

Access Read

Description The authorization identification for the manufacturer of the network management subsys-

tem, which is integrated in this device. This value is located in the SMI enterprises subtree
(1.3.6.1.4.1) and describes which type of device is being managed. For example, if the
manufacturer "Phoenix Contact GmbH" is assigned subtree 1.3.6.1.4.1.4346, it can then
assign its bridge the identifier 1.3.6.1.4.1.4346.2.1.

OID 1.3.6.1.2.1.1.3.0

Syntax TimeTicks

Access Read

Description The time in hundredths of seconds since the last network management unit reset.

Smart Managed Compact Switch

52 PHOENIX CONTACT 8089_en_03

sysContact

sysName

sysLocation

sysServices

sysORLastChange

OID 1.3.6.1.2.1.1.4.0
Syntax Octet string (size: 0 - 255)
Access Read and write
Description The textual id enti fic ati on of t he con tact p er son for th ese man aged nod es and in form ati on

on how this person ca n be contacted.

OID 1.3.6.1.2.1.1.5.0
Syntax Octet string (size: 0 - 255)
Access Read and write
Description A name for this node assigned by the administrator. According to the agreement, this is

the fully qualifying name in the domain.

OID 1.3.6.1.2.1.1.6.0
Syntax Octet string (size: 0 - 255)
Access Read and write
Description The physical location of this node (e.g., “Hall 1, 3rd floor”).

OID 1.3.6.1.2.1.1.7.0
Syntax Integer (0 - 127)
Access Read
Description Indicates a number of services that this device offers. The value is the sum of several cal-

culations. For every layer of the OSI reference model, there is a calculation in the form of
(2

L-1

), where L indica tes the layer.
For example:
A node which primarily executes line routing functions has the value (2

3-1

) = 4.

A node which is a host and provides application services has the value (2

4-1

) + (2

7-1

) = 72.

OID 1.3.6.1.2.1. 1.8
Syntax TimeTicks
Access Read
Description Indicates the value of the sysUpTime during the last system modifica tion.

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 53

sysORTable

4.3.3.2 Interface group (1.3.6.1.2.1.2)

The interface g roup contains information about device interfaces.

4.3.3.3 Address translation group (1.3.6.1. 2.1.3)

The addres s translation group has mandatory characters for a ll systems. It contains infor­mation about the address assignment.

OID 1.3.6.1.2.1. 1.9
Syntax TimeTicks
Access Read
Description The table contains the following objects: sysORIndex, sysORID, sysORDescr, and sys-

ORUpTime.

(2) interfaces

-- (1) ifNumber

-- (2) ifTable

-- (1) if Entry

-- (1) ifIndex

-- (2) ifDescr

-- (3) ifType

-- (4) ifMtu

-- (5) ifSpeed

-- (6) ifPhy sAddress

-- (7) ifAdminStatus

-- (8) ifOperStatus

-- (9) ifLastChange

-- (10) ifInOctets

-- (11) ifInUcastPkts

-- (12) ifInNUcastPkts

-- (13) ifInDiscards

-- (14) ifInErrors

-- (15) ifInUnknownProtos

-- (16) ifOutOctets

-- (17) ifOutUcastPkts

-- (18) ifOutNUcastPkts

-- (19) ifOutDiscards

-- (20) ifOutErrors

-- (21) ifOutQLe n

-- (22) ifSpecific

(3) at

-- (1) atTable

-- (1) atEntry

-- (1) atIfIndex

-- (2) atPhysAddress

-- (3) atNetAddress

Smart Managed Compact Switch

54 PHOENIX CONTACT 8089_en_03

4.3.3.4 Internet protocol group (1.3.6.1.2.1.4)

The Internet protoco l group has manda tory characters for all systems. It contains informa­tion concerning IP switching.

(4) ip

-- (1) ipForwarding

-- (2) ipDefaultTTL

-- (3) ipInReceives

-- (4) ipInHdrErrors

-- (5) ipInAddrErrors

-- (6) ipForwDatagrams

-- (7) ipInUnknownProtos

-- (8) ipInDiscards

-- (9) ipInDelivers

-- (10) ipOutRequests

-- (11) ipOutDiscards

-- (12) ipO utNoRoutes

-- (13) ipReasmTimeout

-- (14) ipReasmReqds

-- (15) ipReasmOKs

-- (16) ipReas mFails

-- (17) ipFragOKs

-- (18) ipFragFails

-- (19) ipF ragCreates

-- (20) ipAddrTable

-- (1) ipAddrEntry

-- (1) ipAdEntAddr

-- (2) ipAdEntIfIndex

-- (3) ipAdEntNetMask

-- (4) ipAdEntBcastAddr

-- (5) ipAdEntReasmMaxSize

-- (21) ipR o uteTable

-- (1) ipRouteEntr y

-- (1) ipRouteDest

-- (2) ipRouteIfIndex

-- (3) ipRouteMetric1

-- (4) ipRouteMetric2

-- (5) ipRouteMetric3

-- (6) ipRouteMetric4

-- (7) ipRouteNextHop

-- (8) ipRouteType

-- (9) ipRouteProto

-- (10) ipRouteAge

-- (11) ipRouteMask

-- (12) ipRouteMetric5

-- (13) ipRouteInfo

-- (22) ipN etToMe diaTabl e

-- (1) ipNetToMediaEntry

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 55

4.3.3.5 ICMP group (1.3.6.1.2.1.5)

The Internet Control Message P rotocol group has mandatory characters for all systems. It
contains information about troubleshooting and control in Internet data traffic.

-- (1) ipNetToMediaIfIndex

-- (2) ipNetToMediaPhysAddress

-- (3) ipNetToMediaNetAddress

-- (4) ipNetToMediaType

-- (23) ipRoutingDiscards

(5) icmp

-- (1) icmpInMsgs

-- (2) icmpInErrors

-- (3) icmpInDestUnreachs

-- (4) icmpInTimeExcds

-- (5) icmpInParmProbs

-- (6) icmpInSrcQuenchs

-- (7) icmpInRedirects

-- (8) icmpInEchos

-- (9) icmpInEchoReps

-- (10) icmpInTi m es tamps

-- (11) icmpInTi m es tampRe ps

-- (12) icmpInAddrMasks

-- (13) icmpInAddrMaskReps

-- (14) icmpOutM s gs

-- (15) icmpOutE rrors

-- (16) icmpOutDestUnreachs

-- (17) icmpOutTimeExcds

-- (18) icmpOutParmPro bs

-- (19) icmpOutSrcQuenchs

-- (20) icm pOutRe directs

-- (21) icmpOutEchos

-- (22) icmpOutEchoRep s

-- (23) icmpOutTimestamps

-- (24) icmpOutTimestampReps

-- (25) icmpOutAddrMa sk s

-- (26) icmpOutAddrMa sk Reps

Smart Managed Compact Switch

56 PHOENIX CONTACT 8089_en_03

4.3.3.6 Transfer Control Protocol group (1.3.6.1.2.1.6)

The Transfer Control Protocol gro up has mandatory characters for all systems that imple­ment TCP. Instan ces of objects, which provide information about a specific TCP connec­tion, are valid as long as the connection is established.

4.3.3.7 User Datagram Protocol group (1.3.6.1.2.1.7)

The User Datagram Protocol group has mandatory characters for all systems that imple­ment UDP .

(6) tcp

-- (1) tcpRtoAlgorithm

-- (2) tcpRtoMin

-- (3) tcpRtoMax

-- (4) tcpMaxConn

-- (5) tcpActiveOpens

-- (6) tcpPassiveOpens

-- (7) tcpAttemptFails

-- (8) tcpEstabResets

-- (9) tcpCurrEstab

-- (10) tcp InSegs

-- (11) tcp OutSeg s

-- (12) tcpRetransSegs

-- (13) tcp C onnTabl e

-- (1) tcpConnEntry

-- (1) tcpConnState

-- (2) tcpConnLocalAddress

-- (3) tcpConnLocalPort

-- (4) tcpConnRemAddress

-- (5) tcpConnRemPort

-- (14) tcpInErrs

-- (15) tcpO utRsts

(7) udp

-- (1) udpInDatagrams

-- (2) udpNoPorts

-- (3) udpInErrors

-- (4) udpOutDatagrams

-- (5) udpTable

-- (1) udpEntry

-- (1) udpLocalAddress

-- (2) udpLocalPort

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 57

4.3.3.8 egp group (1.3.6.1.2.1.8)

4.3.3.9 Transmission group (1.3.6.1.2.1.10)

4.3.3.10 Simple Network Manage ment Protocol group (1.3.6.1.2.1.11)

The Simple Network Management Protocol group has mandatory characters for all sys­tems. In SNMP devices, which are optimized to support either a single agent or a single
manageme nt station, some of the listed objects will be written with the value “0”.

(8) egp

-- (1) egpInMsgs

-- (2) egpInErrors

-- (3) egpOutMsgs

-- (4) egpOutErrors

-- (5) egpNeighTable

-- (1) egpNeighEntry

-- (1) egpNeighState

-- (2) egpNeighAddr

-- (3) egpNeighAs

-- (4) egpNeighInMsgs

-- (5) egpNeighInErrs

-- (6) egpNeighOutMsgs

-- (7) egpNeighOutErrs

-- (8) egpNeighInErrMsgs

-- (9) egpNeighOutErrMsgs

-- (10) egpNeighStateUps

-- (11) egpNeighStateDowns

-- (12) egpNeighIntervalHello

-- (13) egpNeighIntervallPoll

-- (14) egpNeighMode

-- (15) egpNeighEventTrigger

-- (6) egpAs

(10) transmission

(11) snmp

-- (1) snmpInPkts

-- (2) snmpOutPkts

-- (3) snmpInBadVersions

-- (4) snmpInBadCommunityName

-- (5) snmpInBadCommunityUses

-- (6) snmpInASNParseErrs

-- (8) snmpInTooBigs

-- (9) snmpInNoSuchNames

-- (10) snmpIn Ba dValu es

-- (11) snmpInReadOnlys

-- (12) snmpInGenErrs

-- (13) sn m pInTot alReqVars

-- (14) sn m pInTot alSetVar s

-- (15) snmpInGetRequests

-- (16) sn m pInGet Nexts

Smart Managed Compact Switch

58 PHOENIX CONTACT 8089_en_03

4.3.4 RMON MIB (1.3.6.1.2.1.16)

This part of the MIB continuously provides the netwo rk management with up-to-date and
historical network component data. The configuration of alarm s and events controls the
evaluation of network component counters. Depending on the configuration, the result of
the evaluation is indicated to the management station by the agents using traps. The follow ­ing groups are supported:

– statistics
– history
– alarm
– hosts
– hostTopN
– matrix
– filter
– capture and event.

-- (17) snmpInSetRequests

-- (18) snmpInGetResponses

-- (19) sn m pInTraps

-- (20) snmpOutTooBigs

-- (21) sn m pOutNo SuchNames

-- (22) sn m pOutBadValues

-- (24) snmpOutGe nErrs

-- (25) snmpOutGetRequests

-- (26) snm pOutGetNexts

-- (27) snmpOutSetRequests

-- (28) snmpOutGetResponses

-- (29) sn m pOutTraps

-- (30) sn m pEnable A uthenT raps

-- (31) sn m pSilentDrops

-- (32) snmpProxyDrops

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 59

4.3.4.1 statistics (1.3.6.1.2.1.16.1)

This MIB group contains information about, e.g., the number of unicast, multicast or broad­cast telegra ms, t elegr am r at e a nd di st ribution or the nu mbe r of fa ult y te le grams c l ass ed ac­cording to the error type.

The statistics group contains information about the network load and quality.

4.3.4.2 history (1.3.6.1.2.1.16.2)

The history gr oup co ntains sta tis tical i nfor mat ion, whi ch c an be rea d an d repres ent ed, e. g.,
as a time curve.

(1) etherS ta ts T ab le

-- (1) etherStatsEntry

-- (1) etherStatsIndex

-- (2) etherStatsDataSource

-- (3) etherStatsDropEvents

-- (4) etherStatsOctets

-- (5) etherStatsPkts

-- (6) etherStatsBroadcastPkts

-- (7) etherStatsMultic astPkts

-- (8) etherStatsCRCAlignErrors

-- (9) etherStatsUndersizePkts

-- (10) etherStatsOversizePkts

-- (11) etherStatsFragments

-- (12) etherStatsJabbers

-- (13) etherStatsCollisions

-- (14) etherStatsPkts64Octets

-- (15) etherStatsPkts65to127Octets

-- (16) etherStatsPkts128to255Octets

-- (17) etherStatsPkts256to511Octets

-- (18) etherStatsPkts512to1023Octets

-- (19) etherStatsPkts1024to1518Octets

-- (20) etherStatsOwner

-- (21) etherStatsStatus

(1) historyCon tr olTa ble

-- (1) historyControlEntry

-- (1) historyControlIndex

-- (2) historyControlDataSource

-- (3) historyControlBucketsRequested

-- (4) historyControlBucketsGranted

-- (5) historyControlInterval

-- (6) historyControlOwner

-- (7) historyControlStatus

(2) etherh is to ry T abl e

-- (1) etherhistoryEntry

-- (1) etherHistoryIndex

-- (2) etherHistorySampleIndex

-- (3) etherHistoryIntervalStart

-- (4) etherHistoryDropEvents

-- (5) etherHistoryOctets

Smart Managed Compact Switch

60 PHOENIX CONTACT 8089_en_03

4.3.4.3 alarm (1.3.6.1.2.1.16.3)

The alarm group requests statistical values and compares them with the defined limit val­ues. If a value is above or below the limit value, an alarm and a trap are generated.

4.3.4.4 host s (1.3.6.1.2.1.16.4)

-- (6) etherHistoryPkts

-- (7) etherHistoryBroadcastPkts

-- (8) etherHistoryMulticastPkts

-- (9) etherHistoryCRCAlignErrors

-- (10) etherHistoryUndersizePkts

-- (11) etherHistoryOversizePkts

-- (12) etherHistoryFra gments

-- (13) etherHistoryJabbers

-- (14) etherHistoryCollisions

-- (15) etherHistoryUtilization

(1) alarmT ab le

-- (1) alarmEntry

-- (1) alarmIndex

-- (2) alarmInterval

-- (3) alarmVariable

-- (4) alarmSampleType

-- (5) alarmValue

-- (6) alarmStartupAlarm

-- (7) alarmRisingThreshold

-- (8) alarmFallingThreshold

-- (9) alarmRisingEventIndex

-- (10) alarmFallingEventIndex

-- (11) alarmOwner

-- (12) alarmStatus

(1) hostCon tr ol Ta ble

-- (1) hostControlEntry

-- (1) hostControlIndex

-- (2) hostControlDataSource

-- (3) hostControlTableSize

-- (4) hostControlLastDel eteTime

-- (5) hostControl Owner

-- (6) hostControlStatus

-- (2) hos tT able

-- (1) hostEntry

-- (1) hostAddress

-- (2) hostCreat ionOrder

-- (3) hostIndex

-- (4) hostInPkts

-- (5) hostOutPkts

-- (6) hostInOctets

-- (7) hostOutOctets

-- (8) hostOutErrors

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 61

4.3.4.5 hostTopN (1.3.6.1.2.1.16.5)

4.3.4.6 matrix (1.3.6.1.2.1.16.6)

-- (9) hostOutBroadcastPkts

-- (10) hostOutMulticastPkts

-- (3) hostT imeTable

-- (1) hostTimeEntry

-- (1) hostTimeAddress

-- (2) hostTimeCreationOrder

-- (3) hostTimeIndex

-- (4) hostTimeInPkts

-- (5) hostTimeOutPkts

-- (6) hostTimeInOctets

-- (7) hostTimeOutOctets

-- (8) hostTimeOutErrors

-- (9) hostTimeOutBroadcastPkts

-- (10) hostTimeOutMulticastPkts

(1) hostTo pN C ont r o lT abl e

-- (1) hostTopNControlEntry

-- (1) hostTopNControlIndex

-- (2) hostTopNHo stINdex

-- (3) hostTopNRateBase

-- (4) hostTopNTimeRemaining

-- (5) hostTopNDuration

-- (6) hostTopNRequestedSize

-- (7) hostTopNGrantedSize

-- (8) hostTopNStartTime

-- (9) hostTopNOwner

-- (10) hostTopNStatus

-- (2) hos tT opNTabl e

-- (1) hostTopNEntry

-- (1) hostTopNReport

-- (2) hostTopNIndex

-- (3) hostTopNAddress

-- (4) hostTopNRate

-- (1) martrixContro lTable

-- (1) matrixControlEntry

-- (1) matrixControlIndex

-- (2) matrixControlDataSource

-- (3) matrixControlTableSize

-- (4) matrixControlLastDeleteTime

-- (5) matrixControlOwner

-- (6) matrixControlSt atus

-- (2) matrixSDTable

-- (1) matrixSDEntry

-- (1) matrixSDSourceAddress

-- (2) matrixSDDestAddress

Smart Managed Compact Switch

62 PHOENIX CONTACT 8089_en_03

4.3.4.7 filter (1.3.6.1.2.1.16.7)

-- (3) matrixSDIndex

-- (4) matrixSDPkts

-- (5) matrixSDOctets

-- (6) matrixSDErrors

-- (3) matrixDSTable

-- (1) matrixDSEntry

-- (1) matrixDSSourceAddress

-- (2) matrixDSDestAddress

-- (3) matrixDSIndex

-- (4) matrixDSPkts

-- (5) matrixDSOctets

-- (6) matrixDSErrors

(1) filterTable

-- (1) filterEntry

-- (1) filterIndex

-- (2) filterChannelIndex

-- (3) filterPktDataOffset

-- (4) filterPktData

-- (5) filterPktDataMask

-- (6) filterPktDataNotMask

-- (7) filterPktStatus

-- (8) filterPktStatusMask

-- (9) filterPktStatusNotMask

-- (10) filterOwner

-- (11) filterStatus

(2) channelTa ble

-- (1) channelEntry

-- (1) channelIndex

-- (2) channelIfIndex

-- (3) channelAcceptTime

-- (4) channelDataControl

-- (5) channelTurnOnEventIndex

-- (6) channelTurnOffEventIndex

-- (7) channelEventIndex

-- (8) channelEven tStatus

-- (9) channelMatches

-- (10) channelDescription

-- (11) channelOwner

-- (12) channelStatus

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 63

4.3.4.8 capture (1.3.6.1.2.1.16.8)

4.3.4.9 event (1.3.6.1.2.1.16.9)

The event group controls the generation of traps when the alarms described above occur.

(1) bufferControlTa ble

-- (1) bufferControlEntry

-- (1) bufferControlIndex

-- (2) bufferControlChannelIndex

-- (3) bufferControlFullStatus

-- (4) bufferControlFullAction

-- (5) bufferControlCaptureSliceSize

-- (6) bufferControlDownloadSliceSize

-- (7) bufferControlDownloadOffset

-- (8) bufferControlMaxOctetsRequested

-- (9) bufferControlMaxOctetsGranted

-- (10) bufferCo ntrolCapturedPackets

-- (11) bufferControlTurnOnTime

-- (12) bufferControlOwner

-- (13) bufferControlStatus

(2) captur eBufferTa bl e

-- (1)captureBufferEntry

-- (1)captureBufferControlIndex

-- (2)captureBufferIndex

-- (3) captureBufferPacketID

-- (4) captureBufferPacketData

-- (5) captureBufferPacketLength

-- (6) captureBufferPacketTime

-- (7) captureBufferPacketStatus

(1) eventTa ble

-- (1) eventEntry

-- (1) eventIndex

-- (2) eventDescription

-- (3) eventType

-- (4) eventCommunity

-- (5) eventLastTimeSent

-- (6) eventOwner

-- (7) eventStatus

(2) logTable

-- (1) logEntry

-- (1) logEventIndex

-- (2) logIndex

-- (3) logTime

-- (4) logDescription

Smart Managed Compact Switch

64 PHOENIX CONTACT 8089_en_03

4.3.5 Bridge MIB (1.3.6.1.2.1.17)

4.3.5.1 dot1dBase (1.3.6.1.2.1.17.1)

The dot1dBase group contains bridge-specific information.

4.3.5.2 dot1dStp (1.3.6.1.2.1.17.2)

(1) dot1dBaseBridgeAddress
(2) dot1dB as e NumPorts
(3) dot1dBasePo rtT y pe
(4) dot1dBasePo rtT a bl e

-- dot1dBasePortEntry

-- (1) dot1dBasePort

-- (2) dot1dBasePortIfIndex

-- (3) dot1dBasePortPortCircuit

-- (4) dot1dBasePortDelayExceededDiscards

-- (5) dot1dBasePortMtuExceededDiscards

-- (1) dot1dStpProtocolSpecification

-- (2) dot1 dStpPrio rity

-- (3) dot1dStpTimeSinceTopologyChange

-- (4) dot1 dStpTopChanges

-- (5) dot1dStpDesignateRoot

-- (6) dot1dStpRootCost

-- (7) dot1dStpRootPort

-- (8) dot1 dStpMaxAge

-- (9) dot1dS tpHelloT im e

-- (10) dot1dStpHoldTime

-- (11) dot1dStpForwardDelay

-- (12) dot1dStpBridgeMaxAge

-- (13) dot1dStpBridgeHelloTime

-- (14) dot1dStpBridgeForwardDelay

-- (15) dot1dStpPortTable

-- (1) dot1dStpPortEntry

-- (1) dot1dStpPort

-- (2) dot1dStpPortPriority

-- (3) dot1dStpPortState

-- (4) dot1dStpPortEnable

-- (5) dot1dStpPortPathCost

-- (6) dot1dStpPortDesignatedRoot

-- (7) dot1dStpPortDesignatedCost

-- (8) dot1dStpPortDesignatedBridge

-- (9) dot1dStpPortDesignatedPort

-- (10) dot1dStpPortForwardTransitions

-- (11) dot1dStpPortPathCost32

-- (16) dot1dStpVersion

-- (17) dot1dStpTxHoldCount

-- (18) dot1dStpPathCostDefault

-- (19) dot1dStpExtPortTable

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 65

4.3.5.3 dot1dTp (1.3.6.1.2.1.17.4)

The dot1dTp group contains bridge-specific information.

4.3.5.4 dot1dStatic (1.3.6.1.2.1.17.5)

-- (1) dot1dStpExtPortEntry

-- (1) dot1dStpPortProtocolMigration

-- (2) dot1dStpPortAdminEdgePort

-- (3) dot1dStpPortOperEdgePort

-- (4) dot1dStpPortAdminPointToPoint

-- (5) dot1dStpPortOperPointToPoint

-- (6) dot1dStpPortAdminPathCost

(1) dot1dT pL e ar ne dE nt ry Di sc ards
(2) dot1dTpAgingTime
(3) dot1dT pF db T ab le

-- (1) dot1dTpFdbEntry

-- (1) dot1dTpFdbAddress

-- (2) dot1dTpFdbPort

-- (3) dot1dTpFdbStatus

(4) dot1dTpPortTable

-- dot1dTpPortEntry

-- (1) dot1dTpPort

-- (2) dot1dTpPortMaxInfo

-- (3) dot1dTpPortInFrames

-- (4) dot1dTpPortOutFrames

-- (5) dot1dTpPortInDiscards

(5) dot1dTpHCPortTable

-- dot1dTpHCPortEntry

-- (1) dot1dTpHCPortInFrames

-- (2) dot1dTpHCPortOutFrames

-- (3) dot1dTpHCPortInDiscards

(6) dot1dTpPortOverflowTable

-- dot1dTpPortOverflowEntry

-- (1) dot1dTpPortInOverflowFrames

-- (2) dot1dTpPortOutOverflowFrames

-- (3) dot1dTpPortInOverflowDiscards

-- (1) dot1 dStaticTable

-- (1) dot1dStaticEntry

-- (1) dot1dStaticAddress

-- (2) dot1dStaticReceivePort

-- (3) dot1dStaticAllowedToGoTo

Smart Managed Compact Switch

66 PHOENIX CONTACT 8089_en_03

4.3.6 pBridgeMIB (1.3.6.1.2.1.17.6)

4.3.6.1 pBridgeMIBObjects (1.3.6.1.2.1.17.6.1)

4.3.6.2 pBridgeConformance (1.3.6.1.2.1.17.6.2)

-- (1) dot1 dExtBa se

-- (1) dot1dDeviceCapabilities

-- (2) dot1dTrafficClassesEnabled

-- (3) dot1dGmrpStatus

-- (4) dot1dCapabilitiesTable

-- (1) dot1dCapabilitiesEntry

-- (1) dot1dPortCapabilities

-- (2) dot1dPriority

-- (1) dot1dPortPriorityTable

-- (1) dot1dPortPriorityEntry

-- (1) dot1dPortDefaultUserPriority

-- (2) dot1dPortNumTrafficClasses

-- (2) dot1dUserPriorityRegenTable

-- (1) dot1dUserPri orityRegenTable

-- (1) dot1dUserPriority

-- (2) dot1dRegenUserPriority

-- (3) dot1dTrafficClassTable

-- (1) dot1dTrafficClassEntry

-- (1) dot1dTrafficClassPriority

-- (2) dot1dTrafficClass

-- (4) dot1dPortOutboundAccessPriorityTable

-- (1) dot1dPortOutboundAccessPriorityEntry

-- (1) dot1dPortOutboundAccessPriority

-- (3) dot1 dGarp

-- (1) dot1dPortGarpTable

-- (1) dot1dPortGarpEntry

-- (1) dot1dPortGarpJoinTime

-- (2) dot1dPortGarpLeaveTime

-- (3) dot1dPortGarpLeaveAllTime

-- (4) dot1 dGmrp

-- (1) dot1dPortGmrpTable

-- (1) dot1dPortGmrpEntry

-- (1) dot1dPortGmrpStatus

-- (2) dot1dPortGmrpFailedRegistrations

-- (3) dot1dPortGmrpLastPduOrigin

-- (1) pBridgeGroups

-- (1) pBridgeExtCapGroup

-- (2) pBridgeDeviceGmrpGroup

-- (3) pBridgeDevicePriorityGroup

-- (4) pBridgeDefaultPriorityGroup

-- (5) pBridgeRegentPriorityGroup

-- (6) pBridgePriorityGroup

-- (7) pBrid geAccessPriorityGroup

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 67

4.3.7 qBridgeMIB (1.3.6.1.2.1.17.7)

4.3.7.1 qBridgeMIBO bj ec t s (1.3. 6. 1. 2. 1. 17 .7 .1 )

-- (8) pBridgePortGarpGroup

-- (9) pBridgePortGmrpGroup

-- (10) pBridgeHCPortGroup

-- (11) pBridgePortOverflowGrou p

-- (2) pBridgeCompliances

-- (1) pBridgeCompliance

-- (1) dot1qBase

-- (1) dot1qVLANVersionNumber

-- (2) dot1qMaxVLANId

-- (3) dot1qMaxSupportedVLANs

-- (4) dot1qNumVLANs

-- (5) dot1qGvrpStatus

-- (2) dot1qTp

-- (1) dot1qFdbTable

-- (1) dot1qFdbEntry

-- (1) dot1qFdbId

-- (2) dot1qFdbDynamicCount

-- (2) dot1qTpFdbTable

-- (1) dot1qTpFdbEntry

-- (1) dot1qTpFdbAddress

-- (2) dot1qTpFdbPort

-- (3) dot1qTpFdbStatus

-- (3) dot1qTpGroupTable

-- (1) dot1qTpGroupEntry

-- (1) dot1qTpGro upAddress

-- (2) dot1qTpGroupEgressPorts

-- (3) dot1qTpGroupLearnt

-- (4) dot1qFor wardAllTable

-- (1) dot1qForwardAllEntry

-- (1) dot1qForwardAllPorts

-- (2) dot1qForwardAllStaticPorts

-- (3) dot1qForwardAllForbiddenPorts

-- (5) dot1qForwardUnregisteredTable

-- (1) dot1qForwardUnregisteredEntry

-- (1) dot1qForwardUnregisteredPorts

-- (2) dot1qForwardUnregisteredStaticPorts

-- (3) dot1qForwardUnregisteredForbiddenPorts

-- (3) dot1qStatic

-- (1) dot1qStaticUnicastTable

-- (1) dot1qStaticUnicastEntry

-- (1) dot1qStaticUnicastAddress

-- (2) dot1qStaticUnicastReceivePort

-- (3) dot1qStaticUnicastAllowedToGoTo

-- (4) dot1qStaticUnicastStatus

Smart Managed Compact Switch

68 PHOENIX CONTACT 8089_en_03

-- (2) dot1qStaticMulticastTable

-- (1) dot1qStaticMulticastEntry

-- (1) dot1qStaticMulticastAddress

-- (2) dot1qStaticMulticastReceivePort

-- (3) dot1qStaticMulticastStaticEgressPorts

-- (4) dot1qStaticMulticastForbiddenEgressPorts

-- (5) dot1qStaticMulticastStatus

-- (4) dot1qVLAN

-- (1) dot1qVLANNumDeletes

-- (2) dot1qVLANCurrentTable

-- (1) dot1qVLANCurrentEntry

-- (1) dot1qVLANTimeMark

-- (2) dot1qVLANIndex

-- (3) dot1qVLANFdbId

-- (4) dot1qVLANCurrentEgressPorts

-- (5) dot1qVLANCurrentUntaggedPorts

-- (6) dot1qVLANStatus

-- (7) dot1qVLANCreationTime

-- (3) dot1qVLANStaticTable

-- (1) dot1qVLANStaticEntry

-- (1) dot1qVLANStaticName

-- (2) dot1qVLANStaticEgressPorts

-- (3) dot1qVLANForbiddenEgressPorts

-- (4) dot1qVLANStaticUntaggedPorts

-- (5) dot1qVLANStaticRowStatus

-- (4) dot1qNextFreeLocalVLANIndex

-- (5) dot1qPortVLANTable

-- (1) dot1qPortVLANEntry

-- (1) dot1qPvid

-- (2) dot1qPortAcceptableFrameTypes

-- (3) dot1qPortIngressFiltering

-- (4) dot1qPortGvrpStatus

-- (5) dot1qPortGvrpFailedRegistrations

-- (6) dot1qPortGvrpLastPduOrigin

-- (6) dot1qPortVLANSt atisticsTable

-- (1) dot1qPortVLANStatisticsEntry

-- (1) dot1qTpVLANPortInFrames

-- (2) dot1qTpVLANPortOutFrames

-- (3) dot1qTpVLANPortInDiscards

-- (4) dot1qTpVLANPortInOverflowFrames

-- (5) dot1qTpVLANPortOutOverflowFrames

-- (6) dot1qTpVLANPortInOverflowDiscards

-- (7) dot1qPortVLANHCStatisticsTable

-- (1) dot1qPortVLANHCStatisticsEntry

-- (1) dot1qPortVLANHCInFrames

-- (2) dot1qPortVLANHCOutFrames

-- (3) dot1qPortVLANHCIn Discards

-- (8) dot1qLearningConstraintsTable

-- (1) dot1qLearningConstraintsEntry

-- (1) dot1qConstraintVLAN

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 69

4.3.7.2 qBridgeConformance (1.3.6.1.2.1.17.7.2)

4.3.7.3 dot1dConformance (1.3.6.1.2.1.17.7.3)

-- (2) dot1qConstraintSet

-- (3) dot1qConstraintType

-- (4) dot1qConstraintStatus

-- (9) dot1qCon straintSetDefault

-- (10) dot1qConstraintTypeDefault

-- (1) qBridgeGroups

-- (1) qBridgeBaseGroup

-- (2) qBridgeFdbUnicastGroup

-- (3) qBridgeFdbMulticastGroup

-- (4) qBridgeServiceRequirementsGroup

-- (5) qBridgeFdbStaticGroup

-- (6) qBridgeVLANGroup

-- (7) qBridgeVLANStaticGroup

-- (8) qBridgePortGroup

-- (9) qBridgeVLANStatisticsGroup

-- (10) qBridgeVLANStatisticsOverflowGroup

-- (11) qBridgeVLANHCStatisticsGroup

-- (12) qBridgeLearningConstraintsGroup

-- (13) qBridgeLearningConstraintDefaultGroup

-- (2) qBridgeCompliances

-- (1) qBridgeCompliance

-- (1) dot1dGroups

-- (1) dot1dBaseBridgeGroup

-- (2) dot1BasePortGroup

-- (3) dot1dStpBridgeGroup

-- (4) dot1dStpPortGroup2

-- (5) dot1dStpPortGroup3

-- (6) dot1dTpBridgeGroup

-- (7) dot1dTpSdbGroup

-- (8) dot1dTpGroup

-- (9) dot1dStaticGroup

-- (10) dot1dNotificationGroup

-- (2) dot1dCompliances

-- (1) BridgeCompliances1493

-- (2) BridgeCompliances4188

Smart Managed Compact Switch

70 PHOENIX CONTACT 8089_en_03

4.3.8 rstp MIB (1.3.6.1.2. 1.17.11)

4.3.8.1 rstp Conformance (1.3.6.1.2.1.17.11.1)

rstp Groups (1.3.6.1.2.1.17.11.1.1)

rstp Compliance Groups (1.3.6.1.2.1.17.11.1.2)

4.3.9 IANAifType MIB (1.3.6.1.2.1.30)

The IANAifType MIB defines the “ifTable” in MIB II. See “Interface group (1.3.6.1.2.1.2)” on
page 53.

4.3.10 IF MIB (1.3 .6.1.2.1.31)

4.3.10.1 ifMIBObj ect s (1. 3. 6. 1. 2. 1. 31 .1 )

-- (1) rstpBridgeGroups

-- (2) rstpDefaultPathCostGroup

-- (3) rstpPortGroup

-- (1) rstpCompliance

-- (1) ifXTable

-- (1) ifXEntry

-- (1) ifName

-- (2) ifInMulticastPkts

-- (3) ifInBroadcastPkts

-- (4) ifOutMulticastPkts

-- (5) ifOutBroadcastPkts

-- (6) ifHCInOctets

-- (7) ifHCInUcastPkts

-- (8) ifHCInMulticastPkts

-- (9) ifHCInBroadcastPkts

-- (10) ifHCOutOctets

-- (11) ifHCOutUcastPkts

-- (12) ifHCOutMulticastPkts

-- (13) ifHCOutBroadcastPkts

-- (14) ifLinkUpDownTrapEnable

-- (15) ifHighSpeed

-- (16) ifPromiscuousMode

-- (17) ifConnectorPresent

-- (18) ifAlias

-- (19) ifCounterDiscontinuityTime

-- (2) ifStackTable

-- (1) ifStackEntry

-- (1) ifStackHigherLayer

-- (2) ifStackLowerLayer

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 71

4.3.10.2 ifConformance (1.3.6.1.2.1.31.2)

4.3.10.3 etherMIBObjects (1.3.6.1.2.1.32.1)

-- (3) ifStackStatus

-- (3) ifTestTable

-- (1) ifTestEntry

-- (1) ifTestID

-- (2) ifTestStatus

-- (3) ifTestType

-- (4) ifTestResult

-- (5) ifTestCode

-- (6) ifTestOwner

-- (4) ifRcvAddressTable

-- (1) ifRcvAddressEntry

-- (1) ifRcvAddres sAddress

-- (2) ifRcvAddressStatus

-- (3) ifRcvAddressType

-- (5) ifTableLastChange

-- (6) ifStackLastChange

-- (1) ifGroups

-- (1) ifGeneralGroup

-- (2) ifFixedLengthGroup

-- (3) ifHCFixedLengthGroup

-- (4) ifPacketGroup

-- (5) ifHCPacketGroup

-- (6) ifVHCPacketGroup

-- (7) ifRcvAddressGroup

-- (8) ifTestGroup

-- (9) ifStackGroup

-- (10) ifGeneralInformationGroup

-- (11) ifStackGroup2

-- (12) ifOldObjectsGroup

-- (13) ifCounterDiscontinuityGroup

-- (2) ifCompliances

-- (1) ifCompliance

-- (2) ifCompliance2

-- (1) etherConformance

-- (1) etherGroups

-- (1) etherStatsGroup

-- (2) etherCollisionTableGroup

-- (3) etherStats100BbsGroup

-- (4) etherStatsBaseGroup

-- (5) etherStatsL owSpeedGroup

-- (6) etherStatsHighSpeedGroup

-- (7) etherDuplexGroup

-- (8) etherControlGroup

Smart Managed Compact Switch

72 PHOENIX CONTACT 8089_en_03

4.3.10.4 lldpMIB (1.0.8802.1.1.2)

-- (9) etherControlPauseGroup

-- (1) etherCompliances

-- (1) etherCompliances

-- (2) ether100MbsCompliance

-- (3) dot3Compliance

(1) lldpObjects

-- (1) lldpConfiguration

-- (1) lldpMessageTxInterval

-- (2) lldpMessageTxHoldMultiplier

-- (2) lldpStatistics

-- (3) lldpLocalSystemData

-- (1) lldpLocChassisIdSubType

-- (2) lldpLocChassisId

-- (3) lldpLocSysName

-- (4) lldpLocSysDesc

-- (5) lldpLocSysCapSupported

-- (6) lldpLocSysCapEnabled

-- (7) lldpLocPortTable

-- (1) lldpLocPortMum

-- (2) lldpLocPortIdSubtype

-- (3) lldpLocPortId

-- (4) lldpLocPortDesc

-- (8) lldpLocManAddrTable

-- (1) lldpLocManAddrSubtype

-- (2) lldpLocManAddr

-- (3) lldpLocManAddrLen

-- (4) lldpLocManAddrIfSubtype

-- (5) lldpLocManAddrIfId

-- (6) lldpLocManAddrOID

-- (4) lldpRemoteSystemsData

-- (1) lldpRemTable

-- (1) lldpRemTimeMark

-- (2) lldpRemLocalPortNum

-- (3) lldpRemIndex

-- (4) lldpRemChassisType

-- (5) lldpRemChassisId

-- (6) lldpRemPortIdSubtype

-- (7) lldpRemPortId

-- (8) lldpRemPortDesc

-- (9) lldpRemS ysName

-- (10) lldpRemSys Desc

-- (11) lldpRemSysCapSupported

-- (12) lldpRemSysCapEnabled

-- (2) lldpRemManAddrTable

-- (1) lldpRemAddrSubSubtype

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 73

4.3.11 pnoRedundancy MIB 1.3.6.1.4.1.24686

-- (2) lldpRemManAddr

-- (3) lldpRemManAddrIfSubtype

-- (4) lldpRemManAddrIfId

-- (5) lldpRemManAddrOID

-- (5) lldpConformance

(1) pnoMRPDomainTable

-- (1) pnoMRPDomainEntry

-- (1) pnoMRPDomainIndex

-- (2) pnoMRPDomainUuid

-- (3) pnoMRPDomainName

-- (4) pnoMRPDomainAdminRole

-- (5) pnoMRPDomainOperRole

-- (6) pnoMRPDomainManagerPriority

-- (7) pnoMRPDomainRingPort1

-- (8) pnoMRPDomainRingPort1State

-- (9) pnoMRPDomainRingPort2

-- (10)pnoMRPDomainRi ngPort2State

-- (11) pnoMRPDomainState

-- (12) pnoMRPDomainError

-- (13) pnoMRPDomainRi ngOpenCount

-- (14) pnoMRPDomainLastRingOpenChange

-- (15) pnoMRPDomainRoundTripDelayMax

-- (16) pnoMRPDomainRoundTripDelayMin

-- (17) pnoMRPDomainResetRoundTripDelays

Smart Managed Compact Switch

74 PHOENIX CONTACT 8089_en_03

4.3.12 Private MIBs

The private MIBs for the SMN from Phoenix Contact can be found under object ID

1.3.6.1.4.1.4346. The SMN MIB contains the following groups:
– pxcModules (OID = 1.3.6.1.4.1.4346.1),
– pxcGlobal (OID = 1.3.6.1.4.1.4346.2)
– pxcFactoryLine (OID = 1.3.6.1.4.1.4346.11)

MIB tree

The private MIB from Phoenix Contact is integrated in the MIB tree as follows (see red ar­row).

Figure 4-33 MIB tree

4.3.12.1 pxcModules OID = 1.3.6.1.4.1.4346.1

flMSwitchMModule

OID 1.3.6.1.4.1.4346.1.8

The object contains information about the manufacturer.

4.3.12.2 pxcGlobal OID = 1.3.6.1.4.1.4346.2

pxcBasic

OID 1.3.6.1.4.1.4346.2.1

All configuration modifications, which are to take effect after a SMN restart, must be saved
permanently us ing the “fl WorkFWCtrlConfS ave” object.

The aging tim e (default: 4 0 seconds) is no t set using th e private MIBs, i nstead it is set us­ing the “dot1dTpAgingTime” MIB object (OID 1.3.6.1.2.1.17.4.2). The available setting
range is 10 to 825 seconds.

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 75

pxcBasicName

OID 1.3.6.1.4.1.4346.2.1.1
Syntax Display string

Access Read

Description Contains the manufacturer's name: Phoenix Contact GmbH & Co. KG.

pxcBasicDescr

OID 1.3.6.1.4.1.4346.2.1.2

Syntax Display string
Access Read

Description Contains the manufacturer's name and address:

Phoenix Co ntact GmbH & Co. KG, D-32823 Bl omberg.

pxcBasicURL

OID 1.3.6.1.4.1.4346.2.1.3

Syntax Display string
Access Read

Description Contains the manufacturer's web address:

http://www.phoenixcontact.com.

4.3.12.3 p xcFactoryLine OID = 1.3.6.1.4.1.4346.1 1

flGlobal

OID 1.3.6.1.4.1.4346.11.1

flBasic

OID 1.3.6.1.4.1.4346.11.1.1

flBasicName

OID 1.3.6.1.4.1.4346.11.1.1.1
Syntax Display string

Access Read

Description Contains the name of the product group:

Factoryline.

Smart Managed Compact Switch

76 PHOENIX CONTACT 8089_en_03

flBasicDescr

OID 1.3.6.1.4.1.4346.11.1.1.2
Syntax Display s tring

Access Read

Description Contains a brief description of the product group:

Ethernet Installation System.

flBasicURL

OID 1.3.6.1.4.1.4346.11.1.1.3
Syntax Display s tring

Access Read

Description Contains a specific URL f or th e product group:

www.factoryline.de.

flBasicCompCapacity

OID 1.3.6.1.4.1.4346.11.1.1.4

Syntax Integer32 (1... 1024)
Access Read

Descript ion Contains the number of different components that can be managed with this device.

flComponents

OID 1.3.6.1.4.1.4346.11.1.2

flComponentsTable

OID 1.3.6.1.4.1.4346.11.1.2.1

flComponentsTableEntry

OID 1.3.6.1.4.1.4346.11.1.2.1.1
Syntax
Access
Description Generates a table with descriptions for components in the “Factoryline” product group,

which can be managed by this management unit.
flComponentsIndex
OID 1.3.6.1.4.1.4346.11.1.2.1.1.1
Syntax Integer32 (1... 1024)
Access Read

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 77

flWorkDevice

OID 1.3.6.1.4.1.4346.11.11

flWorkBasic

OID 1.3.6.1.4.1.4346.11.11.1

flWorkBasicName

Description Identifies the components for which this entry contains information.
flComponentsName
OID 1.3.6.1.4.1.4346.11.1.2.1.1.2
Syntax Display string
Access Read
Description Contains the designation of the component.
flComponentsDescr
OID 1.3.6.1.4.1.4346.11.1.2.1.1.3
Syntax Display string
Access Read
Description Contains a brief description of the component.
flComponentsURL
OID 1.3.6.1.4.1.4346.11.1.2.1.1.4
Syntax Display string
Access Read
Description Contains the URL of a Phoenix Contact website with additional information about the com-

ponent.
flComponentsOrderNumber
OID 1.3.6.1.4.1.4346.11.1.2.1.1.5
Syntax Display string
Access Read
Description Contains the order number of the component.

OID 1.3.6.1.4.1.4346.11.11.1.1
Syntax Display string
Access Read and write
Description Contains the device name (corresponds to “sysName” from MIB2), which the user as-

signed to the device.

Check this ent r y following a fi r mware update, i t may have been over wri t te n wi t h
default values.

Smart Managed Compact Switch

78 PHOENIX CONTACT 8089_en_03

flWorkBasicDescr

flWorkBasicURL

flWorkBasicSerialNumber

flWorkBasicHWRevision

flWorkBasicPowerStat

OID 1.3.6.1.4.1.4346.11.11.1.2
Syntax Display string
Access Read and write
Description Contains a short description (corresponds to “sysDescr” from MIB2), which the user as-

signed to this component.

Check this ent r y following a fi r mware update, i t may have been over wri t te n wi t h
default values.

OID 1.3.6.1.4.1.4346.11.11.1.3
Syntax Display string
Access Read
Description Contains the URL of the device-specific web page for WBM in the form of the currently set

IP address.

OID 1.3.6.1.4.1.4346.11.11.1.4
Syntax Octet string (12)
Access Read
Description Contains the serial number of the device.

OID 1.3.6.1.4.1.4346.11.11.1.5
Syntax Octet string (4)
Access Read
Description Contains the hardware version of the device.

OID 1.3.6.1.4.1.4346.11.11.1.6
Syntax Integer32 (1... 1024)
Access Read
Description Contains status information about the connected supply voltages:

- Unknown1

- Supply voltage 1 OK3

- Supply voltage 2 OK4

- Supply voltage 1 and 2 OK5

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 79

flWorkBasicCompMaxCapacity

flWorkBasicCompCapacity

flWorkComponents

OID 1.3.6.1.4.1.4346.11.11.2

flWorkComponentsTable

OID 1.3.6.1.4.1.4346.11.11.2.1

flWorkComponentsEntry

OID 1.3.6.1.4.1.4346.11.11.1.11
Syntax Integer32 (1... 1024)
Access Read
Description Contains the maximum number of interfaces that can be connected in theory.

OID 1.3.6.1.4.1.4346.11.11.1.12
Syntax Integer32 (1... 1024)
Access Read
Description Contains the number of interfaces actually connected.

OID 1.3.6.1.4.1.4346.11.11.2.1.1
Description Generates a table with the available interface modules of this switch station.
flWorkComponentsIndex
OID 1.3.6.1.4.1.4346.11.11.2.1.1.1
Syntax Integer32 (1... 1024)
Access Read
Description Indicates the selected interface number, for which this entry contains information.
flWorkComponentsOID
OID 1.3.6.1.4.1.4346.11.11.2.1.1.2
Syntax OBJECT IDENTIFIER
Access Read
Description This OID indicates the corresponding entry in flWorkComponentsEntry.
flWorkComponentsURL
OID 1.3.6.1.4.1.4346.11.11.2.1.1.3
Syntax Display string
Access Read
Description Contains the IP address of the switch.
flWorkComponentsDevSign
OID 1.3.6.1.4.1.4346.11.11.2.1.1.4

Smart Managed Compact Switch

80 PHOENIX CONTACT 8089_en_03

flWorkTraps

OID 1.3.6.1.4.1.4346.11.11.3

flWorkTrapsDelemeter

OID 1.3.6.1.4.1.4346.11.11.3.0

trapPasswdAccess

trapFWHealth

trapFWConf

trapPowerSupply

trapRstpRingFailure

Syntax Integer (0... 24)
Access Read
Description Contains the designation of the interface module.

OID 1.3.6.1.4.1.4346.11.11.3.0.1
Description Sent to the defined trap receivers on each modification or attempted modification of the de-

vice password an d con tains information a bout the status of the last modification or at -

tempted mod if ica tion .

OID 1.3.6.1.4.1.4346.11.11.3.0.2
Desc ription Sent to the diagnostic display on each firmware-related modification and contains addi-

tional information about the firmware status.

OID 1.3.6.1.4.1.4346.11.11.3.0.3
Description Sent each time the configuration is saved and informs the management station that the

configuration has been saved successfully.

This trap is sent in the event of configuration modifications (port name, port mode, device

name, IP address, trap receiver address, port mirroring, etc.), which are not yet saved per-

manently. The t rap therefore provides a warning that, if not saved permanently, the

changes will be lost on a reset.

The “flWorkNetIfParamAssignment” object must be set to static (1), otherwise
objects cannot be written.

OID 1.3.6.1.4.1.4346.11.11.3.0.4
Description Sent each time the redundant power supply fails.

OID 1.3.6.1.4.1.4346.11.11.3.0.6
Description Sent in the event of a link interrupt in the redundant RSTP ring.

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 81

trapManagerConnection

flWorkNet

OID 1.3.6.1.4.1.4346.11.11.4

flWorkNetlfParameter

OID 1.3.6.1.4.1.4346.11.11.4.1

flWorkNetIfParamPhyAddress

flWorkNetIfParamIPAddress

flWorkNetIfParamSubnetmask

flWorkNetIfParamGwIpAddress

OID 1.3.6.1.4.1.4346.11.11.3.0.99
Description This trap is used to test the connection between the device and trap manager.

OID 1.3.6.1.4.1.4346.11.11.4.1.1
Syntax MacAddress
Access Read
Description Contains the MAC address of the switch.

OID 1.3.6.1.4.1.4346.11.11.4.1.2
Syntax IpAddress
Access Read and write
Description Contains the current IP address of the SMN. Changes only take effect once the “flWor-

kNetIfParamSave” object has been executed.

The “flWorkNetIfParamAssignment” object must be set to static (1), otherwise
objects cannot be written.

OID 1.3.6.1.4.1.4346.11.11.4.1.3
Syntax IpAddress
Access Read and write
Description Contains the current subnet mask of the SMN. Changes only take effect once the “flWor-

kNetIfParamSave” object has been executed.

The “flWorkNetIfParamAssignment” object must be set to static (1), otherwise
objects cannot be written.

OID 1.3.6.1.4.1.4346.11.11.4.1.4

Smart Managed Compact Switch

82 PHOENIX CONTACT 8089_en_03

flWorkNetIfParamStatus

flWorkNetIfParamSave

Syntax IpAddress
Access Read and write
Description Contains the IP address of the current default gateway/router of the SMN. Changes only

take effect once the “flWorkNetIfParamSave” object has been executed.

The “flWorkNetIfParamAssignment” object must be set to static (1), otherwise
objects cannot be written.

OID 1.3.6.1.4.1.4346.11.11.4.1.5
Syntax Integer32 (1... 1024)
Access Read
Description Indicates whether IP parameters were modified but not saved:

No change 1

Address setting modified, but not yet activated2

Address settings must be saved permanently using the
“flWorkFWCtrlConfSave” object.

OID 1.3.6.1.4.1.4346.11.11.4.1.6
Syntax Integer
Access Read and write
Description Provides the option of saving modified IP parameters or undoing the modifications:

Undo modification1

Activate modification2

Address settings must be saved permanently using the
“flWorkFWCtrlConfSave” object.

Configuration and diagnostics

8089_en_03 PHOENIX CONTACT 83

flWorkNetIfParamAssignment

flWorkNetIfParamManagementVlanId

flWorkNetPort

OID 1.3.6.1.4.1.4346.11.11.4.2

flWorkNetPortCapacity

flWorkNetPortTable

OID 1.3.6.1.4.1.4346.11.11.4.2.2

flWorkNetPortEntry

OID 1.3.6.1.4.1.4346.11.11.4.1.7
Syntax Integer
Access Read and write
Description Provides the option of modifying the assignment mechanism for IP parameters.

Static IP address1

Assignment via BootP (default)2

Modifications to the assignment mechanism also affect the management func­tions via the web interface and via RS-232.

Modifications to the assignment me chanism on BootP (2) or DCP (4) are only
activated after a restart of the SMN.

Address settings must be saved permanently using the
“flWorkFWCtrlConfSave” object.

OID 1.3.6.1.4.1.4346.11.11.4.1.8
Syntax Integer32 (1... 4094)
Access Read and write
Description If the switch is operated in “Tagging ” VLAN mode, this object indicates in which VLAN

(VLAN ID) the management agent is located.

OID 1.3.6.1.4.1.4346.11.11.4.2.1
Syntax Integer32 (1... 1024)
Access Read
Description Contains the number of available ports depending on the configuration of the MMS.

OID 1.3.6.1.4.1.4346.11.11.4.2.2.1
Description Generates a table with a detailed description o f the port configuration.
flWorkNetPortIndex
OID 1.3.6.1.4.1.4346.11.11.4.2.2.1.1
Syntax Integer32 (1... 1024)

Smart Managed Compact Switch

84 PHOENIX CONTACT 8089_en_03

Access Read
Description Specifies the port number of the selected port.
flWorkNetPortLinkState
OID 1.3.6.1.4.1.4346.11.11.4.2.2.1.2
Syntax Integer
Access Read
Description Indicates the port status:

Connected 1

Not connected2

farEndFault3
flWorkNetPortSpeed
OID 1.3.6.1.4.1.4346.11.11.4.2.2.1.3
Syntax Gauge32
Access Read
Description Contains the data transmission speed of the selected port in bps.
flWorkNetPortDuplexMode
OID 1.3.6.1.4.1.4346.11.11.4.2.2.1.4
Syntax Integer
Access Read
Description Contains the duplex mode of the selected port:

No link0

Full duplex1

Half duplex2
flWorkNetPortNegotiation
OID 1.3.6.1.4.1.4346.11.11.4.2.2.1.5
Syntax Integer
Access Read
Description Contains the duplex mode of the selected port:

Automatic1

Manual2
flWorkNetPortName
OID 1.3.6.1.4.1.4346.11.11.4.2.2.1.6
Syntax Octet string (0 ... 16)
Access Read and write
Description Contains the “name” of the port, e.g., “Robot 1”.
flWorkNetPortEnable
OID 1.3.6.1.4.1.4346.11.11.4.2.2.1.7
Syntax Integer
Access Read and write
Description Here you can disable the port:

Port disabled1

Port enabled2

(Rapid) Spanning Tree

8089_en_03 PHOENIX CONTACT 109

5 (Rapid) Spanning Tree

5.1 General function

Loops The Rapid/Spanning Tree Protocol (RSTP) is a standardized method (IEEE 802.1w/IEEE

802.1d) that enables the use of Ethernet networks with redundant data paths . Ethernet net -

works with redundant data paths form a meshed topology with initially impermissible loops.

Due to these loops, data packets can circulate endlessly within the network and can also be

duplicated. As a consequence, the network is usually overloaded due to circulating data

packets, and communicati on is interru pted. The meshed structure is therefore replaced by

a logical, deterministic path with a tree structure without loops using the Spanning Tree al-

gorithm. In t he event of dat a pat h f ail ure, some of the p r ev iousl y d i sconnected connections

are reconnected to ensure uninterrupted network operation.

IEEE 802. 1w RSTP prevents the long timer-controlled switch-over times of STP.

Example:

In the follow ing network topology, (six) redundant paths have been created to en sure ac-

cess to all network devices in the event of a data path failure. These redundant paths are

impermissible loops. The Spanning Tree Protocol automatically transforms this topology

into a tree by disconnecting selected ports. In this context, one of the switches is assigned

the role of the root of the tree. From this root, all other switches can be accessed via a single

data path.

Figure5-1 Possible tree structure with Spanning Tree

Smart Managed Compact Switch

110 PHOENIX CONTACT 8089_en_03

5.2 (R)STP startup

Startup consists of two parts that must be executed in the spe cified order:

1 Enable (R) STP on all switche s that are to be oper ate d as active (R)STP component s in

the network.

2 Connect the switches to form a meshed topology.

5.2.1 Enabling (R)STP on all switches involved

(R)STP can be activated via web-based management, via the SNMP interface or via the se-

rial interface.

Now switch to the “Switch Station” menu on the “(R)STP General” page. Here, you will find

various information about the Spanning Tree configuration.

Figure 5-2 “(R)STP General” web page

The web page displays the parameters with which the switch is currently operating.

(R)STP configuration

It is sufficient to set the “Rapid Spanning Tree Status” to “Enable” in order to start (R)STP

using defa ult sett ings. Pr iority val ues ca n be speci fied for t he switch. The bri dge and backu p

root can be specified via these priority values.

Only multiples of 4096 are permitted. The desired value can be entered in the “Priority” field.

The value will be rounded automatically to the next multiple of 409 6. Once you have con-

firmed the modification by entering your password, the initialization mechanism is started.

Redundant connecti ons can now be created.

Only create the meshed topology after activating (R)STP.

While learning the network topology, the switch temporarily does not par ticipate in net­work communication.

(Rapid) Spanning Tree

8089_en_03 PHOENIX CONTACT 111

Figure5-3 “(R)STP Configuration” web page

Large tree support

If RSTP is operated using the default values, it is suitable for up to seven switches along the

relevant path (see Figure 5-17 on page130 and Figure5-18 on page 131 as an example of

the relevant path). The RSTP protocol would the re fore be po ssible in a ring topology for up

to 15 switches.

The “Large Tree Suppor t” opt ion makes th e ring topology su itable for 28switches along the

relevant path if RSTP is used. The “Large Tree Support” option could provide an RSTP ring

topology with up to 57 devices. When using “Large Tree Support”, please note the following:

– In the large tree support RSTP topology, donot use devices that do not support large

tree support.
– Enable the “Large Tree Support” option on all devices.
– If RSTP is to be activated as the redundancy mechanism in an existing network with

more than seven sw itches along th e relevan t path, t hen the “Large Tre e Support” option

must first be enabled on all devices.
– It is recommended tha t “La rg e Tree Suppor t” is not acti vated i n networ ks wi th les s than

seven switches along the relevant path.

Maximum age of STP information

The parameter is set by the root switch and used by all switches in the ring. The parameter
is sent to make sure that each switch in the network has a constant value, against which the
age of the saved configuration is tested.

The “Maximum Age of STP Information”, “Hello Time”, and “Forward Delay” fields have the
same meaning as for STP. These values are used when this switch becomes a root. The
values currently used can be found under “(R)STP General”.

Hello time

Specifies the time interval within which the root bridge regularly reports to the other bridges
via BPDU.

Smart Managed Compact Switch

112 PHOENIX CONTACT 8089_en_03

Forward delay

The forward delay value indicates how long the switches are to wait in order for the port state
in STP mode to change from “Discarding” to “Listeni ng” and from “Listening” to “Learning”
(2 x forward delay).

(R)STP port table

Figure 5-4 “(R)STP Port Table” web page

Oper edge port

All ports that do n ot receive any (R)STP BPDUs (e.g., termination device ports) become
edge ports, i.e., ports that go to the “Forwarding” state immediately after restart. All ports
that do not r ecei ve any ( R)STP BP DUs ( e.g., t ermin ati on dev ice por ts) b ecome edg e po rts,
i.e., ports that go to the “Forw arding” state immediately after resta rt.

Protocol

Indicates the redundancy protocol used.

(R)STP state

Indicates the current (R)STP state of the relevant port.
Possib l e st ates:

– “Forw ard in g”

The port is integrated in the active topology and forwards data.
– “Discarding”

The port does not take part in data transmission.
– “Learning”

The port does not take part in data transmission of the acti ve topology , however, MAC

addresses are learned .
– B loc kin g/D is ca rdin g

The port has a link, but has been set to the “Discarding” state by RSTP.

The “Max Age of STP”, “Hello Time”, and “Forward Delay” parameters are optimized by
default upon delivery. They should not be modified.

(Rapid) Spanning Tree

8089_en_03 PHOENIX CONTACT 113

(R)STP port configuration table

Figure5-5 “(R)STP Port Configuration Table” web page

An overview of the main settings for ea ch port is provided here.

5.2.1.1 (R)STP port configuration

This page displays the valid (R)STP configuration settings for the selected port.
If termination devices or subne tworks are connected without RSTP or STP via a port, it is

recommended that the “Admin Edge Port” be set to “Edge Port”. In this way, a link modifica­tion at this port does not result in a topology modification.

5.2.1.2 Switch/port ID

The validity of switches and ports is determined according to priority vectors.

Modifications of properties can result in complete reconfiguration of (Rapid) Spanning
Tree.

It is recommended that a suitable root switch and a backup root switch are specified using
corresponding priority assignment.

Smart Managed Compact Switch

114 PHOENIX CONTACT 8089_en_03

Bridge identifier

A switch ID consists of eight bytes as an unsigned integer value. When comparing two
switch IDs, the one with the lowest numeric value is of higher, i.e., “bett er”, priority.

The first two bytes contain the priority.
The last six bytes contain the MAC address and thus ensure the uniqueness of the switch
ID in the event of identical priority values.

The switch with the lowest numerical swi tch ID becomes the root. It is recommende d that
the root port and alter nate port are specified using the priority.

Port identifier

The port ID consists of four bits for the port priority and twelve bits for the port number. The
port ID is interpreted as an unsigned integer value . When comparing two port IDs, the one
with the lowest numeric value is of higher, i.e., “better”, priority.

Figure 5-6 “(R)STP Port Configuration” web page

Port number

Indicates the number of the port currently selected.

(Rapid) Spanning Tree

8089_en_03 PHOENIX CONTACT 115

Port name

Indicates the name of the port.

STP port state

Indicates the status in which this port takes part in STP.

Operational ed ge port

Indicates whether this port is operated as an edge port.

Admin edge port

Here, you can specify whether this port is to be operated as an edge port (default setting),
if possible.

Priority

Indicates the priority set for this port (default 128). Due to backward compatibility with STP,
priority values can be set that are not configurable in RSTP.

Admin path cost

Indicates the path cost set for this port. A path cost equal to “0” activates the cost calculation
according to the t ransmission speed (10Mbps = 2000000; 100 Mbps = 200000; 1000 Mbps
= 20000).

Path cost

Indicates t he path cost used for this port.

Forward transitions

Indicates how often the port switches from the “Discarding” state to the “Forwarding” state.
Additional parameters provide informat ion about the network pat hs in a stable topology that

are used by the BPDU telegrams.

Designated root

Root bridge for this Spanning Tree.

Designated bri dge

The switch from which the port receives the best BPDUs. The value is based on the priority
value in hex and the MAC address.

Designated port

Port via which the BPDUs are sent from the designated bridge. The value is based on the
port priority (2 digits) and the port number.

Designated cost

Indicates the path cost of this segment to the root switch.

Protocol compatibility

Figure5-7 P roto col co mp atibility

Smart Managed Compact Switch

116 PHOENIX CONTACT 8089_en_03

If a port receives STP BPDUs, it switches automatically to STP mode. Automatic switching
to (R)STP mode does not take place. Switching to (R)ST P mode can only be forced via
“ForceRstp” or via a restart.

(Rapid) Spanning Tree

8089_en_03 PHOENIX CONTACT 117

RSTP fast ring detection

The “RSTP F ast Ri ng Detec tion ” func tion can be act ivated o n the “RSTP Con figu ration ” web
page (see page111).

This function speeds up the switch-over to a redundant path in the event of an error and pro­vides easy diagnostics. RSTP fast ring detection provides each ring with an ID. This ID is
made known to each switch in the relevant ring. A switch can belong to several different
rings at the same time.

Structure of the ring ID The ring ID consists of the port number of the blocking port and the MAC address of the cor-

responding switch. Advantages of the ring ID:
– Easier to identify redundant paths and locate blocking ports.
– P ossible to check whether the desired topology corresponds to the actual topology.

Figure5-8 RSTP ring table

Information in WBM The following informa tion is displayed on the web page (and via SNMP):

Local ring ports
These two ports of this switch belong to the ring that is listed (ring ID).

Blocking port
This port deliberately breaks the loop.

Ring detection states The following states can occur for ring detection:

– Not Ready - Ring detection has not yet been completed.
– OK - Ring detection has b een co mpl eted and q ui ck swi tch -over i s pos si ble i n the ev ent

of an error.
– Broken - The ring is broken on this branch in the direction of the root switch.
– Failed on Port A - The ring was broken on this switch at p ort A.

The “Fast Ring Detection” function is only performed for connections with 10 Mbps or
100 Mbps.

A blocking port does not receive LLDP BPDUs , but does send LLDP BPDUs.

In the event of a link failu re in the ring, the “trapRstpRingFailure” trap is sent.

Smart Managed Compact Switch

118 PHOENIX CONTACT 8089_en_03

When using RSTP fast ring detection, please note the following:
– For RSTP fast ring detection, do not use devices that do not support this function.
– Enable RSTP fast ring detection on all devices.
– All data paths must be in full duplex mode.

5.2.2 Connection failure - Example

The following diagram illustrates an RSTP ring with six switches, where switch 1 is the root.
The ring extends over port 1 and port 2 for each switch. On switch 4, the loop is broken by
a blocking port.

If a cable interrupt occurs at the point indicated by the star, this produces the following en­tries on the “RSTP Fast Ring Detection” web page:

Switch 3 - Failed on Port A
Switch 4 - Broken
In addition, switch 3 would also generate the “flWorkLinkFailure” trap, as long as the send -

ing of traps is not disabled.

Figure 5-9 Connection failure with RSTP ring detection

If the “Broken” or “Fai led” stat us last s for longe r than 60 second s, it is no l onger displ ayed
after the next topology modification, since these rings no longer exist.

(Rapid) Spanning Tree

8089_en_03 PHOENIX CONTACT 119

5.2.3 Mixed operation of RSTP an d STP

If a device with STP support is in tegrated into the network, only switch ports that rece ive
STP BPDUs are set to STP mode. All other ports that receive RSTP BPDUs remain in RSTP
mode.

5.2.4 Topology detectio n of a Rapi d Spannin g Tree network

(RSTP)

(Rapid) Spanning Tree sw itc he s continual ly exchange informa tion about the network t opol­ogy using special messages (BPDUs - Bridge Protocol Data Units). In this way the switches
“learn” the current network t opology and - based on this informat ion - make the follow ing de ­cisions:

– Which switch is selected as the root switch
– Wh ich data paths are disabled

If a switch is started using the (Rapid) Spanning Tree Protocol, it first expects to be the root
switch. However, no data communication is possible during the startup phase until the cur­rent network t opolog y has bee n learned and un til the d ecisi ons descr ibe d above hav e been
made. Therefore loops in the network startup phase which could occur because no data
path is interrupted, are prevented.

5.2.4.1 Topology modification

A topology modification can be triggered by the following:
– Adding a data path
– F ailure of a d ata path
– Ad ding a spanning tree switch, or
– Failure of a Spanning Tree switch

A topology modification is automat ically detected and the ne twork is reconfigured so that
another tree i s cre ated a nd all the d ev ices in t his t ree c an be a cces sed. Du rin g this pr ocess ,
loops do not even occur temporarily.

If sending of traps was not deact ivated, two traps ar e ge nerated:
– newRoot (OID: 1.3.6.1.2.1.17.0.1)
– topologyChange (OID 1.3.6.1.2.1.17.0.2)

5.2.4.2 Interrupted data paths and port states

The described data path interruption by the Spanning Tree Protocol is created by discon­necting individual ports that no longer forward any data packets. A port can have the follow­ing states:

– Learning
– Forwarding
– Blocking/Discarding
– Disabled (link down or disconnected by the user)

The current port states are shown in the web interface.

Smart Managed Compact Switch

120 PHOENIX CONTACT 8089_en_03

The properties of the various port states are shown in the table below.

The sequence of the five port states defined in the Spanning Tree Protocol cannot be as­signed freely. The following diagram illustrates the possible sequence of the port states.

Figure 5-10 Sequence of the possible port states in STP

After device startup and, i f necessary, also du ring topology modification , a port runs through
the stat es in the following order:

Learning ® Forwardi ng
or
Disabled® Blocking/Discarding
Due to the edge property of ports, they switch to “Forwarding” immediately. In the second

case, the port generates a data path interruption in order to suppress loops accordingly.

5.2.4.3 Fast forwarding

If the Spanning Tree Protocol is deactivated at a port, the corresponding port is in “Fast For­warding” mode.

A fast forwarding port
– Ign ores all BPDUs that are r eceiv ed at this port.
– Does not send any BPDUs.
– Switches to the “Forwarding” state immediately after establishing the data link. Termi-

nation devices connected to this port can be accessed immediately.
“Port STP Status” in WBM on the “ STP Port Configuration” page must be set to “Disabled”

to activate fast forwarding.

Table5-1 Properties of the port states

Receiving and evaluating

BPDUs (learning the

topology)

Learning the MAC

addresses of connected

devices and creating the

switching table

Forwarding data packets

(normal switching function)

Disabled
Blocking/Discarding X
Learning X X
Forwarding X X X

At least one port in the “Forwarding” state is at a data path between two spanning tree
switches so that the data path can be integrated into the network.

(Rapid) Spanning Tree

8089_en_03 PHOENIX CONTACT 121

Frame duplication Due to the f ast switch-over times of RSTP, frames may be duplicated and the order of

frames may be changed.

5.2.4.4 Enabling via serial interface

Establish a connection to the switch. The procedure is described in Section “Management
via local RS-232 communication interface” on page 103. Set “Spanning Tree, Enabled” on
the following page in the “Redundancy” field and select “Save”.

Figure5-11 Activating Rapid Spanning Tree

Smart Managed Compact Switch

122 PHOENIX CONTACT 8089_en_03

5.2.5 Configuration notes for Rapid Spanning Tree

In contrast to the Spanning Tree method, the Rapid Spanning Tree method supports event­controlled actions that are no longer triggered based on a timer.

If one line fails (link down), the Rapid Spanning Tree method can respond more quickly to
this failure and thus the switch-over time can be kept low.

– For short switch-over times, structure your network in such a way that a maximum of

seven switches are located in a cascade up to the roo t switch. The switch-over times

can range from 100 ms to 2 s.
– Use priority assignment to specify a central switch as the root.
– It is also recommended t o assign a switch as th e b ackup root.
– For short switch-over times, all switches in the redundant topology should support the

Rapid Spanning Tree Protocol and no hubs should be used.

5.2.5.1 Connecting the switches to form a meshed topology

Having activated (Rapid) Spanning Tree for all switches, you can create a meshed topology
with redundant data paths. Any data links can now be created without taking loops into con­sideration. Loops can even be added on purpose in order to create redundant links.

In this context, a data path between spanning tree switches can be
– A direct connection.
– A connection via one or more addit ional switches that do not support Spanning Tree.

– A c onnection via one or more hubs that do not support Spanning Tree.
Furthermore, a data path can consist of a connection of a spanning tree switch to

– A termination device.
– A network segment in which no loops may occur, which consists of several infrastruc-

ture components (hubs or switches) without Spanning Tree support.
For the last two da ta path options, no specific precautionary measures are necessary. If

necessary, you can use the “Fast Forwarding” option for the respective ports (see Section
“Fast forwarding” on page 120).
For the first three cases, the following rules must be observed:

– Rule 1: Spanning Tree transparency for all infrastructure components

All infrastructu re components used in your network that do not actively support Span-

ning Tree must be transpa rent for Spa nning Tree m essages ( BPDUs) and must forwar d

all BPDUs to all ports without modifying them. When Spanning Tree is disabled, the

switch is transparent for B PDUs.

A link down or link up must be detected at the switch so that the RSTP switches can detect
a line fail ure and a rest ored line mor e quickl y. Ple ase ta ke into c onsider ation, in p artic ular,
paths where media convert ers are used. It might be poss ible that media converters offer
setting options to transmit the link status of the fiber optic side to the twisted-pair side.

If a link down i s not detect ed a t t he sw i tch because the cable int er r upt i s between the me ­dia converters, and no link down is forced at the switch, timer-based detection is activat­ed, which may result in longer switch-over times.

If Spanning Tree is not supp or t ed by all o f the switches u sed , the reconfigu r at i on ti me for
Spanning Tre e is extended by the aging time of the switches without Spa nning Tree sup­port.

(Rapid) Spanning Tree

8089_en_03 PHOENIX CONTACT 123

– Rule 2: At least one active Spanning Tree component per loop

An active Spanning Tree component supports the Spanning Tree Protocol, sends/re-

ceives and eva luates BPDUs, and sets its ports to the relevant STP states.

Each loop in a n et work m u st have at least one ac tive Spanni ng Tr ee component to d is -

integrate the loop.

Example:

Figure5-12 Example topology

The loops in the ex ample topol ogy illustra ted are dis abled by acti ve RSTP componen ts. The
example topology contains th ree rings; the root and the backup root are component s in
each of the three rings. The three rings do n ot affect one another; a modification to the to­pology in one ring does not affect the topology of the other two rings.

– Rule 3: No more than ten active Spanning Tree components in the t opology

when using the Spanning Tree default setting

The ability to disi ntegr a te a ny t opo logy to form a tree without loops requ ires a complex

protocol that w orks wit h severa l variabl e timer s. These v ariable t imers are dimensi oned

using the default values recommended by the IEEE standard so that a topology with a

maximum of ten ac tive Spannin g Tree co mp onents always results in a st able network.

When using large tr ee, plea se note the f ol lowing (s ee also Section “ Large tree supp ort”

on page111):

– In the large tree support RSTP topology,only use devices thatsupport large tree.

– Enable the “Large Tree Support” option on all devices.

– If RSTP is to be act ivated as the redun dancy mechanism in an existing network

with more than seven switches along the relevant path, then the “Large Tree Sup­port” option must first be enabled on all de vices.

– It is recommended that “Larg e Tr ee Su pport” is not acti va te d in net wor ks wit h l ess

than seven switches along the relevant path.

Smart Managed Compact Switch

124 PHOENIX CONTACT 8089_en_03

5.2.5.2 Example topologies

5.2.5.3 Redundant coupling of network segments

In this example, two network segments are connected via redundant data paths. Two RSTP
components have ports in the “Blocking/Discarding” state (highlighted in gray). This is suf­ficient to operate the network.

Figure 5-13 Redundant coupling of network segments