Phoenix Contact FL SWITCH SMN 6TX/2POF-PN User Manual
  1. Manuals
  2. Brands
  3. Phoenix Contact Manuals
  4. Switch
  5. FL SWITCH SMN 6TX/2POF-PN
  6. User manual

Phoenix Contact FL SWITCH SMN 6TX/2POF-PN User Manual

Smart managed narrow switch
Hide thumbs
Table of Contents

Advertisement

Quick Links

Smart Managed Narrow Switch
User manual
Order No. —

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the FL SWITCH SMN 6TX/2POF-PN and is the answer not in the manual?

Questions and answers

Related Manuals for Phoenix Contact FL SWITCH SMN 6TX/2POF-PN

Summary of Contents for Phoenix Contact FL SWITCH SMN 6TX/2POF-PN

  • Page 1 Smart Managed Narrow Switch User manual Order No. —...

  • Page 2: User Manual

    User manual Smart Managed Narrow Switch 2016-02-15 Designation: UM EN FL SWITCH SMN 6TX/2POF-PN Revision: Order No.: — This user manual is valid for: Designation Version Order No. FL SWITCH SMN 6TX/2POF-PN 2700290 FL SWITCH SMN 8TX-PN 2989501 FL SWITCH SMN 6TX/2FX...
  • Page 3 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.
  • Page 4 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.
  • Page 5 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 8089_en_03 PHOENIX CONTACT...
  • Page 6 Internet Group Management Protocol (IGMP) ........144 7.4.2 “General Multicast Configuration” web page ........146 Virtual Local Area Network (VLAN) ..................147 Basics........................147 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 PHOENIX CONTACT 8089_en_03...
  • Page 7 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 Appendixes..........................173 List of figures .....................173 List of tables ......................177 8089_en_03 PHOENIX CONTACT...
  • Page 8 FL SWITCH SMN PHOENIX CONTACT 8089_en_03...
  • Page 9 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. 8089_en_03 PHOENIX CONTACT...
  • Page 10 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. PHOENIX CONTACT 8089_en_03...

  • Page 11: Dimensions Of The Smn

    Smart Managed Narrow Switch 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.
  • Page 12 Smart Managed Compact Switch Depth from top edge of DIN rail without MEM PLUG: 130 mm 56 mm 133 mm Figure 1-3 Housing dimensions of the FL SWITCH SMN in millimeters PHOENIX CONTACT 8089_en_03...

  • Page 13: Status And Diagnostics Indicators

    The system reserve of the optical path is between 2 dB and 0 dB 0.5 Hz Flashing The system reserve of the optical path is <0 dB 2 Hz Diagnostic alarm ACT/SPD/FD Yellow Flashing Switch is in Smart mode (see “Using Smart mode” on page 20) 8089_en_03 PHOENIX CONTACT...

  • Page 14: Firmware Versions And Their Functions

    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. MODE ACT SPD FD Figure 1-4 Example of status indicators 1.2.1 Firmware versions and their functions Firmware version 1.00 provides the standard switch functions. PHOENIX CONTACT 8089_en_03...

  • Page 15: Mounting And Removing The Smn

    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 8089_en_03 PHOENIX CONTACT...

  • Page 16: Installing The Smart Managed Narrow Switch

    24 V DC US1 GND US2 GND R1 R2 Figure 2-4 Supplying the SMN using two voltage sources In order to reset the SMN on power up, the power supply must be interrupted for at least 3 seconds. PHOENIX CONTACT 8089_en_03...

  • Page 17: Signal Contact

    Assignment of the RJ45 Ethernet connectors Table 2-1 Pin assignment of RJ45 connectors Pin number 10Base-T / 10 Mbps 100Base-T / 100 Mbps TD+ (transmit) TD+ (transmit) TD- (transmit) TD- (transmit) RD+ (receive) RD+ (receive) RD- (receive) RD- (receive) 8089_en_03 PHOENIX CONTACT...

  • Page 18: Rs-232 Interface For External Management

    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. PHOENIX CONTACT 8089_en_03...

  • Page 19: Basic Settings

    The transmission of SNMP traps is deactivated and the switch has no valid trap desti- nation IP address. 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. 8089_en_03 PHOENIX CONTACT...

  • Page 20: Using 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 LED 1 LED 2 LED 3 Exit Smart mode without changes Reset to the default settings Set PROFINET mode PHOENIX CONTACT 8089_en_03...
  • Page 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 MODE ACT SPD FD Figure 3-1 Example of Smart mode 8089_en_03 PHOENIX CONTACT...

  • Page 22: Frame Switching

    “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. PHOENIX CONTACT 8089_en_03...

  • Page 23: Prioritization

    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. 8089_en_03 PHOENIX CONTACT...
  • Page 24 Smart Managed Compact Switch PHOENIX CONTACT 8089_en_03...

  • Page 25: Making Contact Between The Smn And Pc For Initial Configuration

    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. Please note that the switch does not support supernetting or classless interdomain rout- ing. 8089_en_03 PHOENIX CONTACT...
  • Page 26 Smart Managed Compact Switch 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 PHOENIX CONTACT 8089_en_03...

  • Page 27: Web-Based Management (Wbm)

    The user-friendly web-based management interface can be used to manage the switch from anywhere in the network using a standard browser. Comprehensive configuration and diag- nostic functions are clearly displayed on a graphical user interface. Every user with a net- 8089_en_03 PHOENIX CONTACT...

  • Page 28: Requirements For The Use Of Wbm

    4.2.3 Functions/information in WBM The navigation tree provides direct access to the following four areas: – General Instructions Basic information about WBM. PHOENIX CONTACT 8089_en_03...
  • Page 29 Device-specific configuration and diagnostics. 4.2.3.1 General instructions Figure 4-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. 8089_en_03 PHOENIX CONTACT...
  • Page 30 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. PHOENIX CONTACT 8089_en_03...
  • Page 31 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. Figure 4-6 “System Identification” menu 8089_en_03 PHOENIX CONTACT...
  • Page 32 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. PHOENIX CONTACT 8089_en_03...
  • Page 33 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 software (firmware)” on page 107. 8089_en_03 PHOENIX CONTACT...
  • Page 34 The password must be between four and twelve characters long. Note that the password is always transferred via the network in unencrypted format. Forgotten your password? Call the Phoenix Contact phone number listed in the Appendix, making sure you have the device serial number and MAC address to hand. “User Interfaces” menu The following actions can be performed here: –...
  • Page 35 (by entering a valid password). It can also be used to restart the system with the relevant configuration or to reset the SMN to the default state upon delivery. 8089_en_03 PHOENIX CONTACT...
  • Page 36 “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. PHOENIX CONTACT 8089_en_03...
  • Page 37 (“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. 8089_en_03 PHOENIX CONTACT...
  • Page 38 – Save the configuration (“Save current configuration” function). The duplicated switch can now be operated in the network using the adjusted IP param- eters. “Configuration Management, Memory Plug” menu Memory plug Figure 4-17 “Memory Plug” web page PHOENIX CONTACT 8089_en_03...
  • Page 39 Figure 4-20 “File Transfer” web page Reboot To trigger a reboot via the web interface, enter a valid password. Save the configuration be- forehand, so that configuration modifications are retained or can be activated via a restart. 8089_en_03 PHOENIX CONTACT...
  • Page 40 This menu provides an overview of the important configuration settings for all ports and also offers the option of setting the status, transmission mode, and link monitoring function for all existing ports. Figure 4-22 “Port Configuration Table” web page PHOENIX CONTACT 8089_en_03...
  • Page 41 “POF-SCRJ Interface the system reserve is low” (The system reserve is less than 2 dB, but greater than 0 dB.) – “POF-SCRJ Interface the system reserve is exhausted” (No system reserve available - the received optical power is below the required minimum value.) 8089_en_03 PHOENIX CONTACT...
  • Page 42 Smart Managed Compact Switch Figure 4-24 “Diagnostics” web page PHOENIX CONTACT 8089_en_03...
  • Page 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. Figure 4-25 “Port Statistics” web page 8089_en_03 PHOENIX CONTACT...
  • Page 44 10 Mbps. Therefore, with the same volume of data, the destination port reaches a capacity of 50%. “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 PHOENIX CONTACT 8089_en_03...
  • Page 45 LLDP Agent enabled. – LLDP Agent disabled. – LLDP recognized new neighbor at port xy. – LLDP neighborhood information become obsolete at port xy. – LLDP neighborhood information changed at port xy. – MRP Client enabled/MRP disable. 8089_en_03 PHOENIX CONTACT...
  • Page 46 Activation/deactivation of broadcast traffic limiting on all ports – Activation/deactivation of multicast traffic limiting on all ports The bandwidth is selected from a drop-down list and is specified in kbps or Mbps. Figure 4-30 “Broadcast Limiter” menu PHOENIX CONTACT 8089_en_03...

  • Page 47: Schematic View Of Snmp Management

    (traps) directly to the manager. All configuration modifications, which are to take effect after a SMN restart, must be saved permanently using the “flWorkFWCtrlConfSave” object. 4.3.2 Schematic view of SNMP management Figure 4-31 Schematic view of SNMP 8089_en_03 PHOENIX CONTACT...
  • Page 48 “expired”, but it cannot be reused with other parameters under any circum- stances. Phoenix Contact 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-...
  • Page 49 Sent each time the redundant power supply fails. trapRstpRingFailure 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. trapManagerConnection 1.3.6.1.4.1.4346.11.11.3.0.99 Description Trap to test the connection between the SNMP agent and the network management sta- tion. 8089_en_03 PHOENIX CONTACT...
  • Page 50 FL SWITCH SMN 6TX/2POF-PN / 8TX-PN 4.3.2.1 Tree structure of the MIB 1 iso 3 org 0 std 8802 iso8802 6 dod 1 ieee802dot1 1 internet 1 ieee802dot1mibs 2 mgmt 4 private 6 snmpV2 2 lldpMIB 3 snmpModules 1 mib-2...

  • Page 51: Rfc 1213 Mib - Mib Ii

    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.
  • Page 52 A node which is a host and provides application services has the value (2 ) + (2 ) = 72. sysORLastChange 1.3.6.1.2.1.1.8 Syntax TimeTicks Access Read Description Indicates the value of the sysUpTime during the last system modification. PHOENIX CONTACT 8089_en_03...
  • Page 53 Address translation group (1.3.6.1.2.1.3) The address translation group has mandatory characters for all systems. It contains infor- mation about the address assignment. (3) at -- (1) atTable -- (1) atEntry -- (1) atIfIndex -- (2) atPhysAddress -- (3) atNetAddress 8089_en_03 PHOENIX CONTACT...
  • Page 54 -- (3) ipRouteMetric1 -- (4) ipRouteMetric2 -- (5) ipRouteMetric3 -- (6) ipRouteMetric4 -- (7) ipRouteNextHop -- (8) ipRouteType -- (9) ipRouteProto -- (10) ipRouteAge -- (11) ipRouteMask -- (12) ipRouteMetric5 -- (13) ipRouteInfo -- (22) ipNetToMediaTable -- (1) ipNetToMediaEntry PHOENIX CONTACT 8089_en_03...
  • Page 55 -- (14) icmpOutMsgs -- (15) icmpOutErrors -- (16) icmpOutDestUnreachs -- (17) icmpOutTimeExcds -- (18) icmpOutParmProbs -- (19) icmpOutSrcQuenchs -- (20) icmpOutRedirects -- (21) icmpOutEchos -- (22) icmpOutEchoReps -- (23) icmpOutTimestamps -- (24) icmpOutTimestampReps -- (25) icmpOutAddrMasks -- (26) icmpOutAddrMaskReps 8089_en_03 PHOENIX CONTACT...
  • Page 56 The User Datagram Protocol group has mandatory characters for all systems that imple- ment UDP. (7) udp -- (1) udpInDatagrams -- (2) udpNoPorts -- (3) udpInErrors -- (4) udpOutDatagrams -- (5) udpTable -- (1) udpEntry -- (1) udpLocalAddress -- (2) udpLocalPort PHOENIX CONTACT 8089_en_03...
  • Page 57 -- (3) snmpInBadVersions -- (4) snmpInBadCommunityName -- (5) snmpInBadCommunityUses -- (6) snmpInASNParseErrs -- (8) snmpInTooBigs -- (9) snmpInNoSuchNames -- (10) snmpInBadValues -- (11) snmpInReadOnlys -- (12) snmpInGenErrs -- (13) snmpInTotalReqVars -- (14) snmpInTotalSetVars -- (15) snmpInGetRequests -- (16) snmpInGetNexts 8089_en_03 PHOENIX CONTACT...
  • Page 58 The follow - ing groups are supported: – statistics – history – alarm – hosts – hostTopN – matrix – filter – capture and event. PHOENIX CONTACT 8089_en_03...
  • Page 59 -- (2) historyControlDataSource -- (3) historyControlBucketsRequested -- (4) historyControlBucketsGranted -- (5) historyControlInterval -- (6) historyControlOwner -- (7) historyControlStatus (2) etherhistoryTable -- (1) etherhistoryEntry -- (1) etherHistoryIndex -- (2) etherHistorySampleIndex -- (3) etherHistoryIntervalStart -- (4) etherHistoryDropEvents -- (5) etherHistoryOctets 8089_en_03 PHOENIX CONTACT...
  • Page 60 -- (4) hostControlLastDeleteTime -- (5) hostControlOwner -- (6) hostControlStatus -- (2) hostTable -- (1) hostEntry -- (1) hostAddress -- (2) hostCreationOrder -- (3) hostIndex -- (4) hostInPkts -- (5) hostOutPkts -- (6) hostInOctets -- (7) hostOutOctets -- (8) hostOutErrors PHOENIX CONTACT 8089_en_03...
  • Page 61 (1.3.6.1.2.1.16.6) -- (1) martrixControlTable -- (1) matrixControlEntry -- (1) matrixControlIndex -- (2) matrixControlDataSource -- (3) matrixControlTableSize -- (4) matrixControlLastDeleteTime -- (5) matrixControlOwner -- (6) matrixControlStatus -- (2) matrixSDTable -- (1) matrixSDEntry -- (1) matrixSDSourceAddress -- (2) matrixSDDestAddress 8089_en_03 PHOENIX CONTACT...
  • Page 62 -- (1) channelEntry -- (1) channelIndex -- (2) channelIfIndex -- (3) channelAcceptTime -- (4) channelDataControl -- (5) channelTurnOnEventIndex -- (6) channelTurnOffEventIndex -- (7) channelEventIndex -- (8) channelEventStatus -- (9) channelMatches -- (10) channelDescription -- (11) channelOwner -- (12) channelStatus PHOENIX CONTACT 8089_en_03...
  • Page 63 -- (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 8089_en_03 PHOENIX CONTACT...
  • Page 64 -- (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 PHOENIX CONTACT 8089_en_03...
  • Page 65 -- (2) dot1dTpHCPortOutFrames -- (3) dot1dTpHCPortInDiscards (6) dot1dTpPortOverflowTable -- dot1dTpPortOverflowEntry -- (1) dot1dTpPortInOverflowFrames -- (2) dot1dTpPortOutOverflowFrames -- (3) dot1dTpPortInOverflowDiscards 4.3.5.4 dot1dStatic (1.3.6.1.2.1.17.5) -- (1) dot1dStaticTable -- (1) dot1dStaticEntry -- (1) dot1dStaticAddress -- (2) dot1dStaticReceivePort -- (3) dot1dStaticAllowedToGoTo 8089_en_03 PHOENIX CONTACT...
  • Page 66 -- (1) dot1dPortGmrpEntry -- (1) dot1dPortGmrpStatus -- (2) dot1dPortGmrpFailedRegistrations -- (3) dot1dPortGmrpLastPduOrigin 4.3.6.2 pBridgeConformance (1.3.6.1.2.1.17.6.2) -- (1) pBridgeGroups -- (1) pBridgeExtCapGroup -- (2) pBridgeDeviceGmrpGroup -- (3) pBridgeDevicePriorityGroup -- (4) pBridgeDefaultPriorityGroup -- (5) pBridgeRegentPriorityGroup -- (6) pBridgePriorityGroup -- (7) pBridgeAccessPriorityGroup PHOENIX CONTACT 8089_en_03...
  • Page 67 -- (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 8089_en_03 PHOENIX CONTACT...
  • Page 68 -- (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 PHOENIX CONTACT 8089_en_03...
  • Page 69 -- (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 8089_en_03 PHOENIX CONTACT...
  • Page 70 -- (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 PHOENIX CONTACT 8089_en_03...
  • Page 71 -- (1) ifCompliance -- (2) ifCompliance2 4.3.10.3 etherMIBObjects (1.3.6.1.2.1.32.1) -- (1) etherConformance -- (1) etherGroups -- (1) etherStatsGroup -- (2) etherCollisionTableGroup -- (3) etherStats100BbsGroup -- (4) etherStatsBaseGroup -- (5) etherStatsLowSpeedGroup -- (6) etherStatsHighSpeedGroup -- (7) etherDuplexGroup -- (8) etherControlGroup 8089_en_03 PHOENIX CONTACT...
  • Page 72 -- (2) lldpRemLocalPortNum -- (3) lldpRemIndex -- (4) lldpRemChassisType -- (5) lldpRemChassisId -- (6) lldpRemPortIdSubtype -- (7) lldpRemPortId -- (8) lldpRemPortDesc -- (9) lldpRemSysName -- (10) lldpRemSysDesc -- (11) lldpRemSysCapSupported -- (12) lldpRemSysCapEnabled -- (2) lldpRemManAddrTable -- (1) lldpRemAddrSubSubtype PHOENIX CONTACT 8089_en_03...
  • Page 73 -- (5) pnoMRPDomainOperRole -- (6) pnoMRPDomainManagerPriority -- (7) pnoMRPDomainRingPort1 -- (8) pnoMRPDomainRingPort1State -- (9) pnoMRPDomainRingPort2 -- (10)pnoMRPDomainRingPort2State -- (11) pnoMRPDomainState -- (12) pnoMRPDomainError -- (13) pnoMRPDomainRingOpenCount -- (14) pnoMRPDomainLastRingOpenChange -- (15) pnoMRPDomainRoundTripDelayMax -- (16) pnoMRPDomainRoundTripDelayMin -- (17) pnoMRPDomainResetRoundTripDelays 8089_en_03 PHOENIX CONTACT...
  • Page 74 “dot1dTpAgingTime” MIB object (OID 1.3.6.1.2.1.17.4.2). The available setting range is 10 to 825 seconds. 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...
  • Page 75 Configuration and diagnostics pxcBasicName 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 1.3.6.1.4.1.4346.2.1.2 Syntax Display string Access Read Description Contains the manufacturer's name and address: Phoenix Contact GmbH & Co. KG, D-32823 Blomberg.
  • Page 76 1.3.6.1.4.1.4346.11.1.2 flComponentsTable 1.3.6.1.4.1.4346.11.1.2.1 flComponentsTableEntry 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 1.3.6.1.4.1.4346.11.1.2.1.1.1 Syntax Integer32 (1 ... 1024) Access Read PHOENIX CONTACT 8089_en_03...
  • Page 77 Description Contains a brief description of the component. flComponentsURL 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 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.
  • Page 78 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 PHOENIX CONTACT 8089_en_03...
  • Page 79 Indicates the selected interface number, for which this entry contains information. flWorkComponentsOID 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 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 1.3.6.1.4.1.4346.11.11.2.1.1.4 8089_en_03 PHOENIX CONTACT...
  • Page 80 The “flWorkNetIfParamAssignment” object must be set to static (1), otherwise objects cannot be written. trapPowerSupply 1.3.6.1.4.1.4346.11.11.3.0.4 Description Sent each time the redundant power supply fails. trapRstpRingFailure 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. PHOENIX CONTACT 8089_en_03...
  • Page 81 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. flWorkNetIfParamGwIpAddress 1.3.6.1.4.1.4346.11.11.4.1.4 8089_en_03 PHOENIX CONTACT...
  • Page 82 “flWorkFWCtrlConfSave” object. flWorkNetIfParamSave 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. PHOENIX CONTACT 8089_en_03...
  • Page 83 Description Contains the number of available ports depending on the configuration of the MMS. flWorkNetPortTable 1.3.6.1.4.1.4346.11.11.4.2.2 flWorkNetPortEntry 1.3.6.1.4.1.4346.11.11.4.2.2.1 Description Generates a table with a detailed description of the port configuration. flWorkNetPortIndex 1.3.6.1.4.1.4346.11.11.4.2.2.1.1 Syntax Integer32 (1 ... 1024) 8089_en_03 PHOENIX CONTACT...
  • Page 84 Octet string (0 ... 16) Access Read and write Description Contains the “name” of the port, e.g., “Robot 1”. flWorkNetPortEnable 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 PHOENIX CONTACT 8089_en_03...

  • Page 85: Rapid) Spanning Tree

    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. Figure 5-1 Possible tree structure with Spanning Tree 8089_en_03 PHOENIX CONTACT...

  • Page 86: R)Stp Startup

    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 4096. Once you have con- firmed the modification by entering your password, the initialization mechanism is started. Redundant connections can now be created. PHOENIX CONTACT 8089_en_03...
  • Page 87 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. 8089_en_03 PHOENIX CONTACT...
  • Page 88 – “Learning” The port does not take part in data transmission of the active topology, however, MAC addresses are learned. – Blocking/Discarding The port has a link, but has been set to the “Discarding” state by RSTP. PHOENIX CONTACT 8089_en_03...
  • Page 89 “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. 8089_en_03 PHOENIX CONTACT...
  • Page 90 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. PHOENIX CONTACT 8089_en_03...
  • Page 91 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 Figure 5-7 Protocol compatibility 8089_en_03 PHOENIX CONTACT...
  • Page 92 Smart Managed Compact Switch 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)STP mode can only be forced via “ForceRstp” or via a restart. PHOENIX CONTACT 8089_en_03...
  • Page 93 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 port A. In the event of a link failure in the ring, the “trapRstpRingFailure” trap is sent. 8089_en_03 PHOENIX CONTACT...

  • Page 94: Connection Failure - Example

    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 PHOENIX CONTACT 8089_en_03...

  • Page 95: Mixed Operation Of Rstp And Stp

    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. 8089_en_03 PHOENIX CONTACT...
  • Page 96 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. PHOENIX CONTACT 8089_en_03...
  • Page 97 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”. Figure 5-11 Activating Rapid Spanning Tree 8089_en_03 PHOENIX CONTACT...

  • Page 98: Configuration Notes For Rapid Spanning Tree

    All infrastructure components used in your network that do not actively support Span- ning Tree must be transparent for Spanning Tree messages (BPDUs) and must forward all BPDUs to all ports without modifying them. When Spanning Tree is disabled, the switch is transparent for BPDUs. PHOENIX CONTACT 8089_en_03...
  • Page 99 “Large Tree Sup- port” option must first be enabled on all devices. – It is recommended that “Large Tree Support” is not activated in networks with less than seven switches along the relevant path. 8089_en_03 PHOENIX CONTACT...
  • Page 100 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 PHOENIX CONTACT 8089_en_03...
  • Page 101 “path costs”. “High path costs” are associated with low-performance connections, e.g., 10 Mbps half du- plex, while “low path costs” are associated with connections with a high total transmission speed, e.g., 100 Mbps full duplex. 8089_en_03 PHOENIX CONTACT...
  • Page 102 ID is saved. – If the root ID and the costs are the same, the ID of the sender is checked. If the ID is lower than the switch's own ID, it is saved. PHOENIX CONTACT 8089_en_03...
  • Page 103 The port costs can be set according to two different standards, 802.1D (STP) or 801.1W (RSTP). If, in addition to Phoenix Contact devices, devices from other manufacturers are used, it is recommended that the port costs are set according to a uniform standard.
  • Page 104 The Spanning Tree protocol also must be deactivated at individual ports if two different net- work segments - both using Spanning Tree - are to be coupled via these ports without the two tree structures melting to a large Spanning Tree. PHOENIX CONTACT 8089_en_03...
  • Page 105 Additional infrastructure components are connected to the port. The corresponding network segment does not contain any loops. Additional infrastructure components are connected to the port, forming a Spanning Tree of their own. No additional redundant connections to this network segment are permitted. 8089_en_03 PHOENIX CONTACT...
  • Page 106 MaxAge ³ 2 × (HelloTime + 1 s) The value ((MaxAge / 2) - Hello Time) for a ring topology corresponds to the maximum num- ber of components with active Spanning Tree. Figure 5-17 Example 1 of the “relevant path” PHOENIX CONTACT 8089_en_03...
  • Page 107 No additional switches/bridges are connected to an edge port. Termination devices are connected to an edge port. An alternate port is a path to the root, which, however, did not become a root port. This means that this port is not part of the active topology. 8089_en_03 PHOENIX CONTACT...
  • Page 108 Smart Managed Compact Switch PHOENIX CONTACT 8089_en_03...

  • Page 109: Media Redundancy Protocol (Mrp)

    If a manager function module is removed during runtime, the MRP manager can no lon- ger be selected. – If a manager function module is removed while the MRP manager is active, the mode remains active until the device is restarted or is switched to another mode (MRP client, disabled). 8089_en_03 PHOENIX CONTACT...

  • Page 110: Network Examples

    Figure 6-1 Example of an MRP ring Make sure that the topology used does not contain an invalid mixture of RSTP and MRP, e.g., by additionally coupling two of the devices through an RSTP connection rendering them redundant. PHOENIX CONTACT 8089_en_03...

  • Page 111: Enabling Web Pages For Using Mrp In Wbm

    Activating “Redundancy” under “General Configuration, User Interfaces” does not acti- vate a redundancy mechanism. In the WBM menu, the “Media Redundancy” page - under which the function can be configured and activated - is enabled. 8089_en_03 PHOENIX CONTACT...

  • Page 112: Configuration Of Mrp

    Time of last topology modification – Ring port numbers and status of the ports (Forwarding or Blocking) Figure 6-4 “MRP General” web page for an MRP manager Figure 6-5 “MRP General” web page for an MRP client PHOENIX CONTACT 8089_en_03...

  • Page 113: Mrp Configuration

    WBM under “Switch, VLAN, Static VLAN”, can be used. The tag is only added to the MRP packet if the port to which the MRP packet is sent is operating in tagging mode. 8089_en_03 PHOENIX CONTACT...
  • Page 114 Smart Managed Compact Switch PHOENIX CONTACT 8089_en_03...

  • Page 115: Multicast Filtering

    Precise network documentation for path specification is required. – Possible redundant paths due to Spanning Tree must be taken into account during port assignment. – For network modifications and, during servicing or expansion, the multicast data paths must be restored. 8089_en_03 PHOENIX CONTACT...

  • Page 116: Current Multicast Groups" Web

    IP groups to the same MAC group. Avoid the use of IP groups that – Do not differ in the first and second byte from the right – Differ by 128 in the third byte from the right PHOENIX CONTACT 8089_en_03...
  • Page 117 Port assignment After entering a new group in the “Multicast Group Address” field, add the ports of the group members by selecting the corresponding checkboxes. Confirm by entering your password and clicking on “Apply”. 8089_en_03 PHOENIX CONTACT...

  • Page 118: Procedure For Creating A Multicast Group

    Create a group for every multicast application or for the multicast address used, and for each switch add the ports to which a device of the appropriate group is directly connected or via which the device can be accessed. PHOENIX CONTACT 8089_en_03...
  • Page 119 Switch 7 Port 1 Port 2 Port 3 Port 4 Port 5 Port 6 Port 7 Port 8 Please note that possible redundant paths resulting from Rapid Spanning Tree must be taken into consideration for multicast group creation. 8089_en_03 PHOENIX CONTACT...

  • Page 120: Dynamic Multicast Groups

    Dynamic multicast groups 7.4.1 Internet Group Management Protocol (IGMP) IGMP on Layer 3 The Internet Group Management Protocol describes a method for distributing information via multicast applications between routers and terminal devices at IP level (Layer 3). PHOENIX CONTACT 8089_en_03...
  • Page 121 IGMP snooping can only be used on Layer 2 if all terminal devices send IGMP messages. The IP stack of multicast-compatible terminal devices with applications linked to a multicast address automatically sends the relevant membership reports. IGMP snooping operates independently of the Internet Group Management Protocol (IGMP). 8089_en_03 PHOENIX CONTACT...

  • Page 122: General Multicast Configuration" Web

    IGMP query An MMS/MCS with activated query function actively sends queries at the “Query Interval” and evaluates the received reports. The MMS/MCS only sends IGMP query reports if IGMP snooping is enabled and only in the management VLAN. PHOENIX CONTACT 8089_en_03...

  • Page 123: Virtual Local Area Network (Vlan)

    Make sure that the switch is always managed in a VLAN that you can also access. VLAN ID 1 cannot be deleted and is thus always created on the switch. If you delete the VLAN in which the switch is managed, management is automatically switched to VLAN 1. 8089_en_03 PHOENIX CONTACT...

  • Page 124: Changing The Management Vlan Id

    The information about VLAN assignment from a tag that may be contained in the data packet is ignored. Figure 8-1 “General VLAN Configuration” menu The switch supports a maximum of 32 different VLANs. PHOENIX CONTACT 8089_en_03...

  • Page 125: Current Vlans

    When the maximum number of set up VLANs is reached, the following text appears below the key for the member states: “The switch supports only 32 VLANs! Further VLANs will be refused!” VLAN 1 is always created statically and all ports are added to it as untagged members. 8089_en_03 PHOENIX CONTACT...

  • Page 126: Static Vlans

    F = Forbidden Ports with the “Forbidden” status do not belong to the selected VLAN and cannot be added dynamically to this VLAN via GVRP. - = None Ports with “None” status are not integrated into the VLAN. PHOENIX CONTACT 8089_en_03...

  • Page 127: Vlan Port Configuration

    “VLAN Port Configuration” web page, where the settings can be modified. This table can be used to assign incoming packets to the created VLANs if the packets reached the port without a VLAN tag. 8089_en_03 PHOENIX CONTACT...

  • Page 128: Setting Up Static Vlans

    The port assignment (untagged) and PVID do not match. In order to set up a VLAN, the switches involved must be configured accordingly. In the fol- lowing example, data traffic is to be enabled in VLAN 5 between termination devices A and B. PHOENIX CONTACT 8089_en_03...

  • Page 129: Vlan And (R)Stp

    VLAN and (R)STP When using (R)STP and VLAN simultaneously, please note the following: – (R)STP is not based on VLANs. – (R)STP creates a loop-free topology in the form of a tree structure. 8089_en_03 PHOENIX CONTACT...
  • Page 130 This ensures that for every possible tree structure that can be generated by (R)STP, every VLAN can be accessed by every switch. An example configuration is illustrated in the following diagram: Figure 8-7 Typical configuration for VLAN and (R)STP PHOENIX CONTACT 8089_en_03...

  • Page 131: Operation As A Profinet Device

    The switch indicates that it is waiting for a valid IP configuration via DCP when the LED for the mode that is currently active flashes. The switch cannot be accessed via other network services such as ping at this time. 8089_en_03 PHOENIX CONTACT...

  • Page 132: Switch As A Profinet Device

    The switch can be operated as a PROFINET device if it is integrated under a controller in the bus configuration in the engineering tool. A GSD file and an FDCML file for integration can be downloaded at www.download.phoenixcontact.com. PHOENIX CONTACT 8089_en_03...

  • Page 133: Configuring The Switch As A Profinet Device

    Once all switches have been added to the bus configuration, the following settings must be made for the individual switches via the “Detail View” tab (device details): – The PROFINET device name must be checked and modified if necessary. 8089_en_03 PHOENIX CONTACT...

  • Page 134: Configuration Via The Engineering Tool

    Configuration via the engineering tool The universal parameter editor (UPE) can be used to configure the switch via the engineer- ing tool (PC Worx). – Activation/deactivation of PROFINET alarms – Configuration of port mode – Configuration of port state PHOENIX CONTACT 8089_en_03...

  • Page 135: Profinet Flashing Function

    Redundant power supply missing (management agent alarm) – MRP manager registered a ring interrupt (management agent alarm) – Interface module removed (slot-specific alarm) – Link monitoring (slot alarm for the relevant channel/port) All the alarms are deactivated when the device is started. 8089_en_03 PHOENIX CONTACT...

  • Page 136: Alarms In Wbm

    Assignment of the control word Action Status Byte 0 Byte 1 Link monitoring 0x01 Port or 0xFF 0x02 Port or 0xFF POF SCRJ diagnostics 0x03 Port or 0xFF 0x04 Port or 0xFF Power supply 0x05 0x00 0x06 0x00 PHOENIX CONTACT 8089_en_03...

  • Page 137: Pdev Function Description

    These submodules are represented in the Step7 engineering tool. PROFINET communica- tion enables information about the port speed, duplex mode, and the link status to be read. An engineering tool reads and then displays the neighbor and topology information via SNMP. 8089_en_03 PHOENIX CONTACT...

  • Page 138: Profinet Stack And Pdev Function

    FDCML file does not support PDEV at present). These files are used to describe the device function and can be imported into an engineer- ing tool. The PDEV function is only available in firmware version 2.2 or later. PHOENIX CONTACT 8089_en_03...

  • Page 139: Link Layer Discovery Protocol (Lldp)

    An SMN manages a maximum of 50 items of neighbor information, all other information is ignored. If several neighbors are displayed on one switch port, then at least one other switch/hub, which does not support or has not activated LLDP, is installed between this switch and the neighbor indicated. 8089_en_03 PHOENIX CONTACT...
  • Page 140 “Link Layer Discovery Protocol” web page The “Message Time To Live” is determined by multiplying the “Message Transmit Inter- val” with the “Message Transmit Hold Multiplier”. The “Message Transmit Hold Multiplier” can only be modified via SNMP. The default value is four. PHOENIX CONTACT 8089_en_03...
  • Page 141 Indicates the port number of the neighboring switch that is used to connect the neighbor to the local switch. If the neighbor is identified as a Phoenix Contact switch, the port number is implemented as a link to the “Port Configuration” web page for the neighbor.

  • Page 142: Topology Representation Via An Engineering Tool

    Smart Managed Compact Switch 10.2 Topology representation via an engineering tool The LLDP information can be represented as such or similarly in engineering tools. Figure 10-3 Topology representation PHOENIX CONTACT 8089_en_03...

  • Page 143: Technical Data And Ordering Data

    At 100 Mbps: 148800 pps Supported MIBs MIB II and private SNMP objects from Phoenix Contact Housing dimensions (width x height x depth) in mm 56 x 133 x 130 (depth from top edge of DIN rail) 56 x 133 x 175 (depth from top edge of DIN rail)

  • Page 144: Ethernet Interfaces

    100 Mbps, full duplex Wavelength 1310 nm Maximum transmission length 39 km fiberglass with F-G 9/125 µm 0.36 dB/km 35 km fiberglass with F-G 9/125 µm 0.4 dB/km 28 km fiberglass with F-G 9/125 µm 0.5 dB/km 0 PHOENIX CONTACT 8089_en_03...
  • Page 145 Test intensity 3, criterion A Additional certification RoHS EEE 2002/95/EC - WEEE 2002/96/EC Differences between this version and previous versions Rev. 00: First version Rev. 01: Integration of FL SWITCH SMN 8TX-PN Rev. 02: New firmware Rev. 03: New devices added 8089_en_03 PHOENIX CONTACT...

  • Page 146: Ordering Data

    Order designation Order No. Pcs./Pkt. Smart Managed Narrow Switch with six Fast Ethernet ports in RJ45 format FL SWITCH SMN 6TX/2POF-PN 2700290 and two SCRJ-POF ports, operating in “PROFINET” mode by default upon delivery Smart Managed Narrow Switch with eight Fast Ethernet ports in RJ45 format,...
  • Page 147 PROFINET installation guidelines, pre-assem- bled cable with connectors HOTLINE: If there are any problems that cannot be solved using this documentation, please call our hotline: + 49 - (0) 52 81 - 946 28 88 factoryline-service@phoenixcontact.com 8089_en_03 PHOENIX CONTACT...
  • Page 148 Smart Managed Compact Switch PHOENIX CONTACT 8089_en_03...
  • Page 149 Section 7 Table 7-1: Multicast port assignment on the switches ........143 Section 8 Section 9 Table 9-1: Assignment of the control word............160 Section 10 Table 10-1: Event table for LLDP................164 Section 11 Appendix A 8089_en_03 PHOENIX CONTACT...
  • Page 150 Smart Managed Compact Switch PHOENIX CONTACT 8089_en_03...

  • Page 151: List Of Figures

    Section 1 Figure 1-1: Smart Managed Compact Switch (versions) ......... 9 Figure 1-2: View of the FL SWITCH SMN 6TX/2POF-PN ........11 Figure 1-3: Housing dimensions of the FL SWITCH SMN in millimeters ....12 Figure 1-4: Example of status indicators ............... 14...
  • Page 152 “(R)STP Port Table” web page ............112 Figure 5-5: “(R)STP Port Configuration Table” web page ........113 Figure 5-6: “(R)STP Port Configuration” web page ..........114 Figure 5-7: Protocol compatibility ................ 115 Figure 5-8: RSTP ring table ................. 117 PHOENIX CONTACT 8089_en_03...
  • Page 153 “Vlan Port Configuration Table” menu ..........152 Figure 8-6: Example: Communication between termination devices via VLAN ... 153 Figure 8-7: Typical configuration for VLAN and (R)STP ........154 Section 9 Figure 9-1: “Operating Mode” web page ............. 156 8089_en_03 PHOENIX CONTACT...
  • Page 154 Figure 9-4: PROFINET alarms in WBM ............... 160 Section 10 Figure 10-1: “Link Layer Discovery Protocol” web page ........164 Figure 10-2: “LLDP Topology” web page .............. 165 Figure 10-3: Topology representation ..............166 Section 11 Appendix A PHOENIX CONTACT 8089_en_03...

This manual is also suitable for:

Fl switch smn 8tx-pnFl switch smn 6tx/2fx298950129895432989556Fl switch smn 6tx/2fx-sm ... Show all

Table of Contents