Ethernet Ip

EtherNet/IP Embedded Switch TechnologyLinear and Device-level Ring Topologies

Catalog Numbers 1756-EN2TR, 1783-ETAP, 1783-ETAP1F, 1783-ETAP2F, 1734-AENTR, 1738-AENTR, 1732E

Application Guide

Important User InformationSolid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (publication SGI-1.1 available from your local Rockwell Automation sales office or online at http://www.rockwellautomation.com/literature/) describes some important differences between solid state equipment and hard-wired electromechanical devices. Because of this difference, and also because of the wide variety of uses for solid state equipment, all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable.

In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment.

The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams.

No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this manual.

Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited.

Throughout this manual, when necessary, we use notes to make you aware of safety considerations.

Allen-Bradley, ArmorBlock, ArmorPoint, CompactLogix, ControlLogix, POINT I/O, Rockwell Automation, RSLinx, RSLogix, and TechConnect are trademarks of Rockwell Automation, Inc.

Trademarks not belonging to Rockwell Automation are property of their respective companies.

WARNINGIdentifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal injury or death, property damage, or economic loss.

IMPORTANT Identifies information that is critical for successful application and understanding of the product.

ATTENTIONIdentifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence

SHOCK HAZARDLabels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be present.

BURN HAZARDLabels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous temperatures.

http://literature.rockwellautomation.com/idc/groups/literature/documents/in/sgi-in001_-en-p.pdfhttp://www.rockwellautomation.com/literature/

Summary of Changes

Introduction This release of this document contains new and updated information. To find new and updated information, look for change bars, as shown next to this paragraph.

Updated Information The document has been changed to provide the most accurate and common topologies currently available with a DLR application. Refer to Common Network Topologies on page 65, for more information.3Publication ENET-AP005C-EN-P - May 2010 3

Summary of ChangesNotes:4 Publication ENET-AP005C-EN-P - May 2010

Table of ContentsPreface Purpose of This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Who Should Use This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 1EtherNet/IP Embedded Switch Technology Overview

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9EtherNet/IP Embedded Switch Technology. . . . . . . . . . . . . . . . . . . . 10

Linear Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Device-level Ring (DLR) Network . . . . . . . . . . . . . . . . . . . . . . . . . 11

Rockwell Automation Products with EmbeddedSwitch Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Features Common to Products with EmbeddedSwitch Technology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

DLR Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Supervisor Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Ring Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

DLR Network Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Number of Nodes on a DLR Network. . . . . . . . . . . . . . . . . . . . . . . . . 19DLR Network Fault Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 2Construct and Configure a Device-level Ring Network

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Install Devices on a DLR Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Configure Supervisor Nodes on a DLR Network . . . . . . . . . . . . . . . . 22

Configure a Ring Supervisor in RSLogix 5000 Programming Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Enable Ring Supervisor in RSLogix 5000Programming Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Configure and Enable a Ring Supervisor in RSLinx Classic Communication Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Complete the Physical Connections of the Network . . . . . . . . . . . . . . 33Verify Supervisor Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Chapter 3Monitor a DLR Network Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Methods to Monitor a DLR Network. . . . . . . . . . . . . . . . . . . . . . . . . . 35RSLogix 5000 Programming Software Status Pages . . . . . . . . . . . 36RSLinx Communication Software Status Pages . . . . . . . . . . . . . . . 36Device Web Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Programmatically Through the Use of a MSG Instruction . . . . . . 36

Monitor Status Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37RSLogix 5000 Programming Software Status Pages . . . . . . . . . . . 37RSLinx Communication Software. . . . . . . . . . . . . . . . . . . . . . . . . . 38

Monitor Device Web Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Monitor Diagnostics via MSG Instructions . . . . . . . . . . . . . . . . . . . . . 42Example Use of MSG Instruction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Use Specific Values on the Configuration Tab . . . . . . . . . . . . . . . 445Publication ENET-AP005C-EN-P - May 2010 5

Table of ContentsRetrieve All Ring Diagnostic Information . . . . . . . . . . . . . . . . . . . 45Request the Ring Participant List . . . . . . . . . . . . . . . . . . . . . . . . . . 47Enable and Configure a Ring Supervisor . . . . . . . . . . . . . . . . . . . . 48

Chapter 4Troubleshoot a Linear or DLR Network

General Solutions for Linear or DLR Networks . . . . . . . . . . . . . . . . . 49Specific Issues on Your DLR or Linear Network . . . . . . . . . . . . . 50

Chapter 5Additional 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F EtherNet/IP Tap Features

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Use DIP Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Internet Group Management Protocol (IGMP) Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

IGMP Snooping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58IGMP Querier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Device Port Debugging Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Replace a 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2FTap on the Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Port Buffer Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Chapter 6Common Network Topologies Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Standalone Linear Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Standalone DLR Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Expanding Beyond Simple Linear or DLR Networks . . . . . . . . . . 68

Appendix ANetwork Usage Guidelines and Recommendations

Appendix BNetwork Recovery Performance

Index6 Publication ENET-AP005C-EN-P - May 2010

Preface

Purpose of This Manual This manual describes how to install, configure and maintain linear and Device-level Ring (DLR) networks using Rockwell Automation EtherNet/IP devices with embedded switch technology.

Who Should Use This Publication

You should use this manual if you develop applications that use EtherNet/IP devices with the embedded switch technology.

You should also understand:

general EtherNet/IP networking concepts. RSLogix 5000 programming software. RSLinx Classic programming software.7Publication ENET-AP005C-EN-P - May 2010 7

4 8 Publication ENET-AP005C-EN-P - May 2010

9Publication ENET-AP005C-EN-P - May 2010 9

Chapter 1

EtherNet/IP Embedded Switch Technology Overview

Introduction Multiple topics affect your understanding of EtherNet/IP embedded switch technology.

Prior to the introduction of products with embedded switch technology, the traditional EtherNet/IP network topology has been a star, where end devices are connected and communicate with each other via a switch. The diagram below shows an EtherNet/IP star configuration.

Example EtherNet/IP Star Topology

The EtherNet/IP embedded switch technology offers alternative network topologies for interconnecting EtherNet/IP devices by embedding switches into the end devices themselves.

Topic Page

EtherNet/IP Embedded Switch Technology 10

Rockwell Automation Products with Embedded Switch Technology 12

DLR Network Elements 15

DLR Network Operation 18

Number of Nodes on a DLR Network 19

DLR Network Fault Management 19

Chapter 1 EtherNet/IP Embedded Switch Technology OverviewEtherNet/IP Embedded Switch Technology

Embedded switch technology is designed to enable end devices to form linear and ring network topologies.

Linear Network

A linear network is a collection of devices that are daisy-chained together. The EtherNet/IP embedded switch technology allows this topology to be implemented at the device level. No additional switches are required.

The graphic below shows an example of a linear network.

Example Linear Network

These are the primary advantages of a linear network.

The network simplifies installation and reduces wiring and installation costs.

The network requires no special software configuration. Embedded switch products offer improved CIP Sync application

performance on linear networks.

The primary disadvantage of a linear network is that any break of the cable disconnects all devices downstream from the break from the rest of the network.

IMPORTANT Products with EtherNet/IP embedded switch technology have two ports to connect to a linear or DLR network in a single subnet.

You cannot use these ports as two Network Interface Cards (NICs) connected to two different subnets.10 Publication ENET-AP005C-EN-P - May 2010

EtherNet/IP Embedded Switch Technology Overview Chapter 1Device-level Ring (DLR) Network

A DLR network is a single-fault tolerant ring network intended for the interconnection of automation devices. This topology is also implemented at the device level. No additional switches are required.

The graphic below shows an example of a DLR network.

Example DLR Network

The advantages of the DLR network include:

simple installation. resilience to a single point of failure on the network. fast recovery time when a single fault occurs on the network.

The primary disadvantage of the DLR topology is the additional effort required to set up and use the network as compared to a linear or star network.

IMPORTANT Products with EtherNet/IP embedded switch technology have two ports to connect to a linear or DLR network in a single subnet.

You cannot use these ports as two Network Interface Cards (NICs) connected to two different subnets.Publication ENET-AP005C-EN-P - May 2010 11

Chapter 1 EtherNet/IP Embedded Switch Technology OverviewRockwell Automation Products with Embedded Switch Technology

The current Rockwell Automation products that you can use to construct a DLR or linear network include:

1756-EN2TR ControlLogix EtherNet/IP 2-port module - Allows ControlLogix controllers, I/O modules and communication modules to connect to the DLR or linear network.

1783 EtherNet/IP taps - Allow devices that do not support embedded switch technology to connect to a linear or a DLR network. Each tap uses a device port on the front of the tap to connect to devices that do not support the embedded switch technology to connect to linear or DLR networks. The taps have two network ports to connect to linear or DLR networks.

The network ports used to connect to linear or DLR networks are different for each type of tap. The following table describes the types of taps used with each tap:

The primary advantages of using fiber-optic networks are the availability of increased distances between network nodes and greater noise immunity on the network.

For an example of a 1783-ETAP tap using both the device port and network ports to connect a device that does not support embedded switch technology to a DLR network see graphic Example DLR Network on page 11.

1734-AENTR, POINT I/O 2-port Ethernet adapter - Allows POINT I/O modules to connect to the DLR or linear network.

1738-AENTR, ArmorPoint 2-port Ethernet adapter - Allows ArmorPoint I/O modules to connect to the DLR or linear network.

Cat. No. Network Ports Description

1783-ETAP 2 copper Two copper network ports connect the tap to copper linear or DLR networks.

1783-ETAP1F 1 copper

1 fiber

One copper network port connects the tap to a copper linear or DLR network, and one fiber-optic network port connects the tap to a fiber-optic linear or DLR network.

This tap is commonly used to connect a copper section with a fiber-optic section of the same network.

1783-ETAP2F 2 fiber Two fiber-optic network ports connect the tap to a fiber-optic linear or DLR network.12 Publication ENET-AP005C-EN-P - May 2010

EtherNet/IP Embedded Switch Technology Overview Chapter 1 Any 1732E ArmorBlock I/O EtherNet/IP modules with a catalog number ending in R, including: 1732E-IB16M12R 1732E-OB16M12R 1732E-16CFGM12R 1732E-IB16M12DR 1732E-OB16M12DR 1732E-8X8M12DR 1732E-IB16M12SOEDR

Features Common to Products with Embedded Switch Technology

The products described on page 12 have certain features in common.

Each product supports the management of network traffic to ensure timely delivery of critical data, that is, QoS and IGMP protocols are supported.

Each product is designed according to the ODVA specification for EtherNet/IP. Because of this design, third-party products may be designed, according to the ODVA specification, to operate on a DLR or linear network. To see the ODVA specification, go to:

http://www.odva.org/

For DLR networks, ring recovery time is less than 3 ms for a 50 node network. For more information about recovery time, see Network Recovery Performance on page 75.Publication ENET-AP005C-EN-P - May 2010 13

http://www.odva.org/

Chapter 1 EtherNet/IP Embedded Switch Technology Overview Each product supports an IEEE 1588 transparent clock for CIP motion and CIP Sync applications.

CIP Sync technology can be used in Logix control systems to synchronize clocks across a system operating on the EtherNet/IP network. This technology supports highly distributed applications that require such functions as timestamping, sequence of events recording, distributed motion control, and increased control coordination.

For example, with CIP Sync technology, a single ControlLogix controller can establish a master time and then, using ControlLogix Ethernet modules, propagate that time to all necessary devices on the network.

For more information on how to use CIP Synch technology, see the Integrated Architecture and CIP Sync Configuration Application Solution, publication IA-AP003.

Each of the products described on page 12 have two ports to connect to linear or DLR networks in a single subnet. You cannot use these ports as two network interface cards (NICs) connected to two different subnets.14 Publication ENET-AP005C-EN-P - May 2010

http://literature.rockwellautomation.com/idc/groups/literature/documents/ap/ia-ap003_-en-e.pdfhttp://literature.rockwellautomation.com/idc/groups/literature/documents/ap/ia-ap003_-en-e.pdfhttp://literature.rockwellautomation.com/idc/groups/literature/documents/ap/ia-ap003_-en-e.pdf

EtherNet/IP Embedded Switch Technology Overview Chapter 1DLR Network Elements A DLR network is made up of the following devices:

Supervisor Node Active Supervisor Node Back-up Supervisor Node (optional)

Ring Node

Each of these device types, and how they work in a DLR network, are described in the following sections. The graphics below show examples of devices connected to a DLR network with copper connections and with fiber-optic connections. In the second example, all devices are connected to the network via a 1783-ETAP2F EtherNet/IP tap.

Example DLR Networks

Active Supervisor Node Back-up Supervisor Node

Back-up Supervisor NodeRing Node

Ring Node Ring Node



Ring Node Ring Node

DLR Network with Copper Connections

DLR Network with fiber-optic ConnectionsPublication ENET-AP005C-EN-P - May 2010 15

Chapter 1 EtherNet/IP Embedded Switch Technology OverviewSupervisor Node

A DLR network requires at least one node to be configured as ring supervisor. Currently, several Rockwell Automation products support the ring supervisor functionality.

1756-EN2TR ControlLogix EtherNet/IP 2-port module

1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F EtherNet/IP tap

Active Ring Supervisor

When multiple nodes are enabled as supervisor, the node with the numerically highest precedence value becomes the active ring supervisor; the other nodes automatically become back-up supervisors.

The ring supervisor provides the following primary functions:

Verifies the integrity of the ring Reconfigures the ring to recover from a single fault Collects diagnostic information for the ring

IMPORTANT Out of the box, the supervisor-capable devices have their supervisor function disabled so they are ready to participate in either a linear/star network topology, or as a ring node on an existing DLR network.

In a DLR network, you must configure at least one of the supervisor-capable devices as the ring supervisor before physically closing the ring. If not, the DLR network will not work.16 Publication ENET-AP005C-EN-P - May 2010

EtherNet/IP Embedded Switch Technology Overview Chapter 1Back-up Supervisor Node

At any point in time, there will be only one active supervisor on a DLR network. However, we recommend that you can configure at least one other supervisor-capable node to act as a back-up supervisor. During normal operation, a back-up supervisor behaves like a ring node. If the active supervisor node operation is interrupted, for example, it experiences a power-cycle, the back-up supervisor with the next numerically highest precedence value becomes the active supervisor.

If multiple supervisors are configured with the same precedence value (the factory default value for all supervisor-capable devices is 0), the node with the numerically highest MAC address becomes the active supervisor.

We recommend that you:

configure at least one back-up supervisor.

configure your desired active ring supervisor with a numerically higher precedence value as compared to the back-up supervisors.

keep track of your networks supervisor-precedence values for all supervisor-enabled nodes.

For more information about how to configure a supervisor, see Construct and Configure a Device-level Ring Network on page 21.

Ring Node

A ring node is any node that operates on the network to process data that is transmitted over the network or to pass on the data to the next node on the network. When a fault occurs on the DLR network, these reconfigure themselves and relearn the network topology. Additionally, ring nodes can report fault locations to the active ring supervisor.

IMPORTANT While a back-up supervisor is not required on a DLR network, it is recommended that you configure at least one back up ring supervisor for your ring network.

IMPORTANT Do not connect non-DLR devices directly to the network. Non-DLR devices should be connected to the network through 1783-ETAP, 1783-ETAP1F, or 1783ETAP2F EtherNet/IP taps.Publication ENET-AP005C-EN-P - May 2010 17

Chapter 1 EtherNet/IP Embedded Switch Technology OverviewDLR Network Operation During normal network operation, an active ring supervisor uses beacon, and other DLR protocol frames to monitor the health of the network. Back-up supervisor nodes and ring nodes monitor the beacon frames to track ring transitions between Normal, that is, all links are working, and Faulted, that is, the ring is broken in at least one place, states.

You can configure two beacon-related parameters:

Beacon interval - Frequency at which the active ring supervisor transmits a beacon frame through both of its ring ports.

Beacon timeout - Amount of time that supervisor or ring nodes wait before timing out the reception of beacon frames and taking appropriate action.

These parameters impact Network Recovery Performance. For information on these performance times, see page 75. For information on how to set these parameters, see Construct and Configure a Device-level Ring Network on page 21.

During normal operation, one of the active supervisor nodes network ports is blocked for DLR protocol frames. However, the active supervisor node continues to send beacon frames out of both network ports to monitor network health. The graphic below shows the use of beacon frames sent from the active ring supervisor.

Normal DLR Network Operation

A second category of ring nodes, known as announce frame ring nodes, can be designed to participate in a DLR network. The active supervisor sends announce frames out one of its ports once per second or on detection of a ring fault. DLR networks with announce frame ring nodes have slightly longer recovery times than beacon frame nodes.

Active Ring Supervisor

Ring Node 1 Ring Node 2 Ring Node 3 Ring Node 4

Beacon Frame

Blocked Port

Beacon Frame

Control Traffic Control Traffic18 Publication ENET-AP005C-EN-P - May 2010

EtherNet/IP Embedded Switch Technology Overview Chapter 1Number of Nodes on a DLR Network

Rockwell Automation recommends that you use no more than 50 nodes on a single DLR or linear network. If your application requires more than 50 nodes, we recommend that you segment the nodes into separate, but linked, DLR networks.

With smaller networks:

there is better management of traffic on the network. the networks are easier to maintain. there is a lower likelihood of multiple faults.

Additionally, on a DLR network with more than 50 nodes, network recovery times from faults are higher than those listed in Network Recovery Performance on page 75.

DLR Network Fault Management

Your network may occasionally experience faults that prevent the normal transmission of data between nodes. Your DLR network can protect your application from interruptions resulting from a single fault. To maintain the resiliency of your ring, your application should monitor the health of the ring itself, as the ring may be faulted while all higher-level network functions, such as I/O connections, are operating normally.

You can obtain fault location information from the active supervisor. For more information on how to obtain fault location information, see Monitor a DLR Network on page 35.

After a fault occurs, the active supervisor reconfigures the network to continue sending data on the network.Publication ENET-AP005C-EN-P - May 2010 19

Chapter 1 EtherNet/IP Embedded Switch Technology OverviewThe following graphic shows the network configuration after a failure occurs, with the active ring supervisor passing traffic through both of its ports, thus, maintaining communication on the network.

Network Reconfiguration After FaultActive Ring Supervisor

Ring Node 1 Ring Node 2 Ring Node 3 Ring Node 4

Failure

Unblocked Port

Beacon Frame

Control and Other Traffic

Beacon Frame

Control and Other Traffic20 Publication ENET-AP005C-EN-P - May 2010

Chapter 2

Construct and Configure a Device-level Ring Network

Introduction Use this chapter to learn how to construct and configure a DLR network.

Install Devices on a DLR Network

The first step to configuring a DLR network is to connect all devices to the network. You should leave at least one connection unmade, that is, temporarily omit the physical connection between two nodes on the ring network, because the factory default settings of DLR devices are set to operate in linear/star mode or as ring nodes on existing DLR networks.

The graphic below shows an example of a new DLR network with one physical connection left open.

Example Device-level Ring Topology with One Connection Left Unmade

Topic Page

Install Devices on a DLR Network 21

Configure Supervisor Nodes on a DLR Network 22

Complete the Physical Connections of the Network 33

Verify Supervisor Configuration 34

IMPORTANT If you fully connect your DLR network without a supervisor configured, a network storm may result, rendering the network unusable until one link is disconnected and at least one supervisor is enabled.

Last physical connection is not made.21Publication ENET-AP005C-EN-P - May 2010 21

Chapter 2 Construct and Configure a Device-level Ring NetworkUse the installation instructions for each device to connect it to the network.

Configure Supervisor Nodes on a DLR Network

After you have installed your devices on the DLR network, you must configure at least one supervisor node. Ring nodes do not require any DLR network configuration.

Before you can complete a DLR network, that is, install your devices on the network and make all physical connections, you must configure and enable a ring supervisor in:

RSLogix 5000 programming software

or

RSLinx Classic communication software

This section shows how to use RSLogix 5000 programming software, beginning on page 23, and RSLinx Classic communication software, beginning on page 29, to configure and enable a ring supervisor.

Cat. No. Description Installation Instructions

1756-EN2TR ControlLogix EtherNet/IP Communication module

1756-IN612

1783-ETAP EtherNet/IP tap with copper interface 1783-IN007

1783-ETAP1F, 1783-ETAP2F

EtherNet/IP taps with fiber-optic interfaces 1783-IN008

1734-AENTR POINT I/O 2-port EtherNet/IP adapter 1734-IN040

1738-AENTR ArmorPoint 2-port EtherNet/IP adapter 1738-IN028

Multiple 1732E products (listed on page 12)

ArmorBlock I/O EtherNet/IP modules 1732E-IN003

TIP You can use DIP switch 3 on the 1783-ETAP (with firmware revision 2.x or later), 1783-ETAP1F or 1783-ETAP2F taps to enable the taps as ring supervisors instead of using using the software options described in this section.

For more information on how to use the DIP switches, see page 53.22 Publication ENET-AP005C-EN-P - May 2010

http://literature.rockwellautomation.com/idc/groups/literature/documents/in/1756-in612_-en-p.pdfhttp://literature.rockwellautomation.com/idc/groups/literature/documents/in/1783-in007_-en-p.pdfhttp://literature.rockwellautomation.com/idc/groups/literature/documents/in/1783-in008_-en-p.pdfhttp://literature.rockwellautomation.com/idc/groups/literature/documents/in/1734-in040_-en-p.pdfhttp://literature.rockwellautomation.com/idc/groups/literature/documents/in/1738-in028_-en-e.pdfhttp://literature.rockwellautomation.com/idc/groups/literature/documents/in/1738-in028_-en-e.pdfhttp://literature.rockwellautomation.com/idc/groups/literature/documents/in/1732e-in003_-en-p.pdf

Construct and Configure a Device-level Ring Network Chapter 2Configure a Ring Supervisor in RSLogix 5000 Programming Software

To configure the 1756-EN2TR module or the 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F taps as a ring supervisor, use the devices Add-on Profile (AOP) in RSLogix 5000 programming software, version 17.01.

IMPORTANT To download an AOP, go to: http://support.rockwellautomation.com/controlflash/LogixProfiler.asp

Depending on the firmware revision of your product, you must use a specific AOP version.

For both the 1756-EN2TR module and 1783-ETAP tap, make sure that the Major Revision configured on the General tab of the devices RSLogix 5000 programming software configuration matches the major revision of the physical module.

If the device configuration on the General tab does not match the physical module, the programming software alerts you to this mismatch when you attempt to configure the Internet Protocol, Port Configuration and Network tabs for that device.

Cat. No. Firmware Revision Required Add-On Profile Revision

1756-EN2TR 2.1(1)

(1) You can use the ControlFLASH Firmware Upgrade software to upgrade a 1756-EN2TR module from firmware revision 2.1 to 3.x or later.

1.x or later

3.x or later 2.x or later

1783-ETAP 1.1(2)

(2) You can use the ControlFLASH Firmware Upgrade software to upgrade a 1783-ETAP tap from firmware revision 1.1 to 2.x or later.

To download new firmware, go to: http://www.rockwellautomation.com/support/americas/index_en.html

If you upgrade the firmware revision on your module or tap, you must use the required AOP revision listed above for that revision. For example, if you upgrade your 1756-EN2TR module to firmware revision 3.x or later, you must use AOP revision 2.x or later in your RSLogix 5000 programming software.

Additionally, if you upgrade the firmware revision on your module or tap, you must also use the required RSLinx communication software for that firmware revision. For more information on which RSLinx communication software version is required for each firmware revision, see page 29.

1.x or later

2.x or later 2.x or later

1783-ETAP1F 2.x or later 2.x or later

1783-ETAP2FPublication ENET-AP005C-EN-P - May 2010 23

http://support.rockwellautomation.com/controlflash/LogixProfiler.asphttp://www.rockwellautomation.com/support/americas/index_en.html

Chapter 2 Construct and Configure a Device-level Ring NetworkTo configure a ring supervisor in RSLogix 5000 programming software, follow these steps.

1. Add the module to your project.

a. Right-click 1756 Backplane and choose New Module.

IMPORTANT The steps to configure a ring supervisor via software are basically the same for the 1756-EN2TR module and the 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F taps. This example shows how to configure the 1756-EN2TR module.

You only need to configure the 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F taps in your I/O Configuration if you plan to enable the tap as a ring supervisor. If you do not plan to use the tap as a ring supervisor, we recommend that you do not add it to your I/O Configuration.

Additionally, if you want to configure a 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F tap as a supervisor via software or with its DIP switchs, you must first assign it an IP address. The tap does not require an IP address if it is used as a ring node or has its supervisor function enabled by DIP switch

For more information on how to use a taps switch to configure it as a ring supervisor, see page 53.

a

24 Publication ENET-AP005C-EN-P - May 2010

Construct and Configure a Device-level Ring Network Chapter 2b. Select the module.c. Click OK.

2. Complete configuration information for the module in your RSLogix 5000 project.

The graphic below shows the I/O configuration for an example DLR network.

3. Download to your Logix controller.

4. Go online with the controller and leave it in Program mode.

b

c

Publication ENET-AP005C-EN-P - May 2010 25

Chapter 2 Construct and Configure a Device-level Ring NetworkEnable Ring Supervisor in RSLogix 5000 Programming Software

After you have added your 1756-EN2TR module or 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F taps to your RSLogix 5000 programming software project, you must enable the ring supervisor mode.

To enable the 1756-EN2TR module or 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F taps as a ring supervisor, follow these steps.

1. With your project online with the controller, double-click a supervisor-capable device in the I/O configuration tree.

IMPORTANT If you are using RSLogix 5000 programming software to configure your ring supervisor and monitor diagnostics on your DLR network, you must be online with your controller.

IMPORTANT The steps to enable a ring supervisor are basically the same for both the 1756-EN2TR module or 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F taps. This example shows how to do it for the 1756-EN2TR module.

Double-click the module.26 Publication ENET-AP005C-EN-P - May 2010

Construct and Configure a Device-level Ring Network Chapter 22. Click the Network tab to Enable Supervisor Mode.

Configuration takes effect immediately; you do not need to click Apply or OK.

3. Click the Advanced button on the Network tab.

4. Configure supervisor-related parameters, as shown in the screen shot below.

For these parameters, you must click Set after entering a value.

5. Click Set.

Click here to enable Supervisor Mode.

IMPORTANT For Beacon Interval, Beacon Timeout and Ring Protocol VLAN ID, we recommend that you use the default values.Publication ENET-AP005C-EN-P - May 2010 27

Chapter 2 Construct and Configure a Device-level Ring NetworkFunctionality Description Default Setting

Supervisor Precedence

You may configure a supervisor precedence number for each device configured as a ring supervisor. The highest possible supervisor precedence value is 255.

When multiple nodes are enabled as supervisor, the node with the highest precedence value is assigned as the active ring supervisor; the other nodes automatically become back-up supervisors.

We recommend that you: configure at least one back-up supervisor node. set your desired Active Ring Supervisor with a relatively high supervisor-precedence value

compared to the back-up node(s).

keep track of your networks supervisor-precedence values.


0

Beacon Interval Frequency of the active ring supervisor transmitting a beacon frame through both of its Ethernet ports. This parameter is user configurable for any time between 200S and 100mS.

For more information on how this parameter relates to network performance, see page 75.

400 S

Beacon Timeout The beacon timeout is amount of time nodes wait before timing out the reception of beacon frames and taking appropriate action. Supervisors support a range from 400S to 500mS.


1960 S

Ring Protocol VLAN ID

Reserved for future use. 028 Publication ENET-AP005C-EN-P - May 2010

Construct and Configure a Device-level Ring Network Chapter 2Configure and Enable a Ring Supervisor in RSLinx Classic Communication Software

You can configure and enable a ring supervisor for your DLR network through RSLinx Classic communication software.

IMPORTANT Depending on the firmware revision of your product, you must use specific versions of RSLinx communication software.

Cat. No. Firmware Revision Required RSLinx Commmunication Software Version

1756-EN2TR 2.1(1)

(1) You can use the ControlFLASH Firmware Upgrade software to upgrade a 1756-EN2TR module from firmware revision 2.1 to 3.x or later.

2.55 or later

3.x or later 2.56 or later

1783-ETAP 1.1(2)

(2) You can use the ControlFLASH Firmware Updgrade software to upgrade a 1783-ETAP tap from firmware revision 1.1 to 2.x or later.

To download new firmware, go to: http://www.rockwellautomation.com/support/americas/index_en.html

If you upgrade the firmware revision on your module or tap, you must use the required RSLinx communication software version listed above for that firmware revision. For example, if you upgrade your 1756-EN2TR module to firmware revision 3.x or later, you must use RSLinx communication software, version 2.56 or later.

Additionally, if you upgrade the firmware revision on your module or tap, you must also use the required AOP revision for that firmware revision. For more information about which AOP revision is required for each firmware revision, see page 23.

2.55 or later

2.x or later 2.56 or later

1783-ETAP1F 2.x or later 2.56 or later

1783-ETAP2FPublication ENET-AP005C-EN-P - May 2010 29

http://www.rockwellautomation.com/support/americas/index_en.html

Chapter 2 Construct and Configure a Device-level Ring NetworkThis example is for the 1783-ETAP tap. Follow these steps.

1. Launch RSLinx communication software.

2. Browse to the DLR network that you are setting up.

3. Access the supervisor-capable nodes properties.a. Right-click the node.b. Choose Module Configuration.

The General tab appears with information about the module.

TIP If you do not have the Electronic Data Sheet (EDS) file installed on the module configured to be the ring supervisor, it will appear with a question mark (?). To obtain and use the EDS file:

right-click the module and choose to upload the EDS file from the device.

or

download the EDS file from: http://www.rockwellautomation.com/resources/eds/

a

b


http://www.rockwellautomation.com/resources/eds/http://www.rockwellautomation.com/resources/eds/

Construct and Configure a Device-level Ring Network Chapter 24. Click the Network tab to Enable Supervisor Mode.

Configuration takes affect immediately; you do not need to click Apply or OK.

5. Click the Advanced button to configure supervisor-related parameters.

6. Click Set.

Click here to enable Supervisor Mode.

IMPORTANT For Beacon Interval, Beacon Timeout and Ring Protocol VLAN ID, we recommend that you only use the default values.Publication ENET-AP005C-EN-P - May 2010 31

Chapter 2 Construct and Configure a Device-level Ring NetworkFunctionality Description Default Setting

Supervisor Precedence

You may configure a supervisor precedence number for each device configured as a ring supervisor. The highest possible supervisor precedence value is 255.

When multiple nodes are enabled as supervisor, the node with the highest precedence value is assigned as the active ring supervisor; the other nodes automatically become back-up supervisors.

We recommend that you: configure at least one back-up supervisor node. set your desired Active Ring Supervisor with a relatively high supervisor-precedence value

compared to the back-up node(s).

keep track of your networks supervisor-precedence values.


0

Beacon Interval Frequency of the active ring supervisor transmitting a beacon frame through both of its Ethernet ports. This parameter is user configurable for any time between 200S and 100mS.


400 S

Beacon Timeout The beacon timeout is amount of time nodes wait before timing out the reception of beacon frames and taking appropriate action. Supervisors support a range from 400S to 500mS.


1960 S

Ring Protocol VLAN ID

Reserved for future use. 0

Enable IGMP Snooping

For more information on IGMP Snooping, see Additional 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F EtherNet/IP Tap Features on page 53.

Enabled

Enable IGMP Querier

For more information on IGMP Querier, see Additional 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F EtherNet/IP Tap Features on page 53.

Disabled

Enable Device Port Debugging Mode

For more information on Device Port Debugging Mode, see Additional 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F EtherNet/IP Tap Features on page 53.

Disabled32 Publication ENET-AP005C-EN-P - May 2010

Construct and Configure a Device-level Ring Network Chapter 2Complete the Physical Connections of the Network

After you configure and enable your ring supervisor nodes, you must complete the physical connection of your network to establish a complete and fully functioning DLR network.

The figure below shows an example DLR network with all physical connections complete.

Example Device-level Ring Topology with All Connections Complete

Last physical connection is made.Publication ENET-AP005C-EN-P - May 2010 33

Chapter 2 Construct and Configure a Device-level Ring NetworkVerify Supervisor Configuration

You can verify your configuration and overall DLR network status in either RSLogix 5000 programming software or RSLinx Classic communication software.

1. Access the supervisor nodes properties as shown previously in this chapter.

2. Click the Network tab.

3. Check the Network Topology and Network Status fields.

.

For a 1756-EN2TR module or the 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F taps, you can also verify the supervisor configuration through the modules diagnostic web pages. For more information on monitoring diagnostics via an EtherNet/IP modules web pages, see Monitor a DLR Network on page 35.

If there

the Network Topology = Linear/Star is no supervisor configured for the network.

the Network Topology = Ring is at least one node configured as a supervisor.

the Network Status = Normal are no faults on the network.

Check these fields.34 Publication ENET-AP005C-EN-P - May 2010

Chapter 3

Monitor a DLR Network

Introduction Use this chapter to learn how to monitor your DLR network.

Methods to Monitor a DLR Network

You can retrieve network diagnostic information from the ring supervisor-capable devices using the following:

RSLogix 5000 Programming Software Status Pages RSLinx Communication Software Status Pages Device Web Pages Programmatically Through the Use of a MSG Instruction

Topic Page

Methods to Monitor a DLR Network 35

Monitor Status Pages 37

Monitor Device Web Pages 41

Monitor Diagnostics via MSG Instructions 4235Publication ENET-AP005C-EN-P - May 2010 35

Chapter 3 Monitor a DLR NetworkRSLogix 5000 Programming Software Status Pages

You must use RSLogix 5000 programming software, version 17.01 or later and have installed the appropriate AOPs to use the softwares profile status pages.

RSLinx Communication Software Status Pages

To monitor the network with this method, you must use RSLinx communication software, version 2.55 or later.

Device Web Pages

The 1783-ETAP1F and 1783-ETAP2F taps support device web pages out-of-the-box.

The 1783-ETAP tap, firmware revision 1.1 does not support device web pages. If you upgrade the tap to firmware revision 2.1, you can use device web pages with the tap.

Programmatically Through the Use of a MSG Instruction

For more information on how to monitor your DLR network via MSG Instructions, see page 42.36 Publication ENET-AP005C-EN-P - May 2010

Monitor a DLR Network Chapter 3Monitor Status Pages Both RSLogix 5000 programming software and RSLinx Classic communication software offer status pages that you can use to monitor your networks performance.

RSLogix 5000 Programming Software Status Pages

You can monitor your networks diagnostic information through the RSLogix 5000 programming software when the software is online.

To monitor the network in RSLogix 5000 programming software, follow these steps.

1. Verify that your project is online.

2. Access the active supervisor nodes properties.a. Right-click the modules entry in the Controller Organizer.b. Click Properties.

3. Use the Network tab to monitor diagnostics.

a

b

Publication ENET-AP005C-EN-P - May 2010 37

Chapter 3 Monitor a DLR NetworkRSLinx Communication Software

To monitor the network in RSLinx communication software, follow these steps.

1. Click RSWho to browse the network.

2. Access the property pages for the active supervisor node.a. Open the driver that shows the nodes on your DLR network.b. Right-click the node for which you want to monitor performance.c. Click on the choice that you need to access.

Multiple choices appear.

These options are shown in the following sections.

a

b

c


Monitor a DLR Network Chapter 3Module Configuration

This series of tabs provides:

general information. connection information. module information. Internet protocol. port configuration. network information.

The example below shows a ring fault between nodes at IP addresses 10.88.80.21 and MAC ID 00-00-BC-02-48-D5.

There are multiple fields that you can use to monitor network diagnostics.

Field Definition

Network Topology Possible values here can be Linear or Ring.

Network Status Displays if the network is operating normally (Normal) or has experienced a fault (Ring Fault), as shown in the example screen above.

Active Ring Supervisor Displays the IP address or MAC address of the active ring supervisor.

Active Supervisor Precedence

For more information on this field, see Active Ring Supervisor on page 16.

Enable Ring Supervisor Configurable field that lets you to set the node as a ring supervisor.

Ring Faults Detected Number of faults detected on the network since the last module power cycle or counter reset.Publication ENET-AP005C-EN-P - May 2010 39

Chapter 3 Monitor a DLR NetworkSupervisor Status Displays whether this node is the active ring supervisor (Active), a back-up supervisor (Back-up), a ring node, or part of a linear network.

Last Active Node on Port 1

The last node the active ring supervisor can communicate with on Port 1. This value is an IP address or a MAC ID and remains latched until the Verify Fault Location button is clicked.


The last node the active ring supervisor can communicate with on Port 2. This value is an IP address or a MAC ID and remains latched until the Verify Fault Location button is clicked.

Status Displays whether a fault exists on the ring.

IMPORTANT If the Network Topology field = Ring and the Network Status field = Normal, the Last Active Node fields will display the last fault information even though it has been corrected.

To clear the last fault information from these fields, click Verify Fault Location. You may see a message informing you that the supervisor is no longer in fault mode and the fields will be cleared.

Field Definition40 Publication ENET-AP005C-EN-P - May 2010

Monitor a DLR Network Chapter 3Monitor Device Web Pages Another method to monitor network diagnostic information with supervisor-capable nodes is to use the modules diagnostic web pages.

For example, to access your 1756-EN2TR modules diagnostic web pages, follow these steps.

1. Open your web browser.

2. In the Address field, type your modules Internet Protocol (IP) address and press Enter.

You can use the links on the left-most navigation bar to see each available web page. The screen below shows Ring Statistics for a 1756-EN2TR module.

IMPORTANT A 1783-ETAP tap using firmware revision 1.1 does not support diagnostic web pages. You must upgrade the tap to firmware revision 2.x or later to use diagnostic web pages.

Keep in mind, though, that upgrading your 1783-ETAP tap to firmware revision 1.1 also requires that you upgrade your RSLinx communication software to version 2.56 or later.

Ethernet/IP Module Internet Protocol (IP) AddressPublication ENET-AP005C-EN-P - May 2010 41

Chapter 3 Monitor a DLR NetworkMonitor Diagnostics via MSG Instructions

You can also obtain network diagnostic information programmatically via MSG instructions in RSLogix 5000 programming software. For example, you can:

get all ring diagnostic information. get a ring participant list. get the active supervisor. clear rapid ring faults. verify a fault location. reset a fault counter. enable and configure a ring supervisor.

This information can be displayed on an HMI device or manipulated in your project code.

Example Use of MSG Instruction

This example describes how to retrieve diagnostic information from your DLR network. Follow these steps.

1. Enter a MSG instruction into your rung of logic.

2. Configure the MSG instruction to retrieve ring diagnostic information service, as shown in the following screen shots.

IMPORTANT Make sure the tag you create is sized appropriately to hold all of the data you are reading or writing.

For more information, see page 44.42 Publication ENET-AP005C-EN-P - May 2010

Monitor a DLR Network Chapter 33. Configure the MSG instructions communication path to point to the active supervisor node.

The path on the following screen is one example path.

Click here to browse to the active supervisor node in your project.

IMPORTANT When using the Custom Get_Attributes_All (01) service, if you point to an active supervisor node, you retrieve all of the attributes listed in Retrieve All Diagnostic Information Attribute Description on page 45.

If you point to a non-supervisor node, you retrieve only the Network Topology and Network Status attribute information.

If you point to backup supervisor node, you can retrieve the current active supervisors IP address.Publication ENET-AP005C-EN-P - May 2010 43

Chapter 3 Monitor a DLR NetworkUse Specific Values on the Configuration Tab

Use the values on the Configuration tab of your MSG instruction to perform specific services.

TIP Sample DLR network diagnostic application code, for example, Add-on Instruction or HMI faceplate graphics, is available on the Rockwell Automation Sample Code Library.

For more information about the Rockwell Automation Sample Code Library, see:

http://www.rockwellautomation.com/solutions/integratedarchitecture/resources5.html

Request Description Message Type

Service Type

Service Code (HEX)

Class (HEX)

Instance Attribute (HEX)

Source Element

Source Length (Bytes)

Destination Destination Length (bytes)

Retrieve All Ring Diagnostic Information

Information for this request is listed in Retrieve All Ring Diagnostic Information on page 45.

CIP Generic

Custom 1 47 1 NA Left blank 0 Tag 50

or

54(2)

Request Ring Participant List(1)

Information for this request is listed in Request the Ring Participant List on page 47.

CIP Generic

Get Attribute Single

e 47 1 9 NA NA Tag 10/node

Get Active Supervisor

Obtain the IP address and MAC ID of the active supervisor on the DLR network

CIP Generic

Get Attribute Single

e 47 1 a NA NA Tag 10

Acknowledge Rapid Ring Faults Condition

Request supervisor to resume normal operation after encountering a rapid ring fault condition

CIP Generic

Custom 4c 47 1 NA NA NA NA

Verify a Fault Location

Request supervisor to update Last Active Node values

CIP Generic

4b 47 1 NA NA NA NA NA

Reset the Ring Fault Counter

Reset the number of ring faults detected on the DLR network

CIP Generic

Set Attribute Single

10 47 1 5 Tag 2 NA NA

Enable and Configure a Ring Supervisor

Information for this request is listed in Enable and Configure a Ring Supervisor on page 48.

CIP Generic

Set Attribute Single

10 47 1 4 Tag 12 NA NA

(1) This request only works if there are fewer than 40 nodes on the network. If there are more nodes than will fit in a single message, an error will be returned.

(2) You can use a Destination Length of 54 bytes if you use firmware revision 3.x or later for the 1756-EN2TR module or firmware revision 2.x or later for the 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F taps.44 Publication ENET-AP005C-EN-P - May 2010

http://www.rockwellautomation.com/solutions/integratedarchitecture/resources5.html

Monitor a DLR Network Chapter 3Retrieve All Ring Diagnostic Information

When you perform the Retrieve All Ring Diagnostic Information request on an active supervisor, the MSG instruction returns the following information.

Retrieve All Diagnostic Information Attribute Description

Destination Tag Attribute Name Description Possible Values

SINT [0] Network Topology Current network topology mode

0 = Linear

1 = Ring

SINT [1] Network Status Current status of the network

0 = Normal

1 = Ring Fault

2 = Unexpected Loop Detected

3 = Partial Network Fault

4 = Rapid Fault/Restore Cycle

SINT [2] Ring Supervisor Status Ring supervisor active status flag

0 = Node is functioning as a backup

1 = Node is functioning as the active ring supervisor

2 = Node is functioning as a normal ring node

3 = Node is operating in a non-DLR topology

4 = Node cannot support the currently operating ring parameters, that is, Beacon Interval and/or Beacon Timeout

Ring Supervisor Config Ring Supervisor configuration parameters

SINT [3] Ring Supervisor Enable

Ring supervisor enable flag

0 = Node is configured as a normal ring node (default configuration)

1 = Node is configured as a ring supervisor

SINT [4] Ring Supervisor Precedence

Precedence value of a ring supervisor(2)

Valid value range = 0255

0 = Default value

SINT [5-8] Beacon Interval Duration of ring beacon interval

Valid value range = 200 s100 ms

Default = 400 s

SINT [9-12] Beacon Timeout Duration of ring beacon timeout

Value value range = 400 s500 ms

Default value = 1960 s

SINT [13-14] DLR VLAN ID Valid ID to use in ring protocol messages


Default value = 0

SINT [15-16] Ring Faults Count Number of ring faults since power up(2)Publication ENET-AP005C-EN-P - May 2010 45

Chapter 3 Monitor a DLR NetworkLast Active Node on Port 1

Last active node at the end of the chain through port 1 of the active ring supervisor during a ring fault

SINT [17-20] Device IP address(2) Any valid IP address value

A value = 0 indicates no IP address has been configured for the device.

SINT [21-26] Device MAC address(2)

Any valid Ethernet MAC address


Last active node at the end of the chain through port 2 of the active ring supervisor during a ring fault

SINT [27-30] Device IP address(2) Any valid IP address value


SINT [31-36] Device MAC address(2)


SINT [37-38] Ring Protocol Participants Count

Number of devices in the ring protocol participants list

Active Supervisor Address

IP and/or Ethernet MAC address of the active ring supervisor

SINT [39-42] Supervisor IP address Any valid IP address value


SINT [43-48] Supervisor MAC address


SINT [49] Active Supervisor Precedence

Precedence value of the active ring supervisor

SINT [50-53](1) Capability Flags Alerts you that the device is capable of operating as a supervisor and beacon-based ring node.

0x22

(1) This destination tag is available only with the 1756-EN2TR module, firmware revision 3.x or later, 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F taps, firmware revisions 2.x or later. If you are using the 1783-ETAP tap, firmware revision 1.x, your program does not include this destination tag.

(2) RSLogix 5000 programming software may display the value in this field as negative numbers. To better understand the value, we recommend you view it in HEX format.

Retrieve All Diagnostic Information Attribute Description

Destination Tag Attribute Name Description Possible Values46 Publication ENET-AP005C-EN-P - May 2010

Monitor a DLR Network Chapter 3Request the Ring Participant List

When you request the Ring Participant List service on your DLR network, the MSG instruction returns the following information.

Request the Ring Participant List Attribute Description

Destination Tag Attribute Name Description Possible Values

Ring Protocol Participants List(1)

List of devices participating in ring protocol

SINT [0-3] Device IP address(2), (3) Any valid IP address value


SINT [4-9] Device MAC address(3), (4)


(1) This attribute will return an array of the data shown, one entry for each node. The Ring Protocol Participants Count attribute determines the number entries.

(2) This tag displays only IP addresses for ring participants that have been configured with one. For example, you may have a 1783-ETAP tap connected to the network that has not been assigned an IP address. In that case, no address is shown for the 1783-ETAP tap.

(3) RSLogix 5000 programming software may display the value in this field as negative numbers. To better understand the value, we recommend you view it in HEX format.

(4) Unlike destination tag SINT [0-3], where IP addresses are displayed only for ring participants configured with an IP address, this tag displays MAC addresses for all ring participants because every ring participant has a MAC address.Publication ENET-AP005C-EN-P - May 2010 47

Chapter 3 Monitor a DLR NetworkEnable and Configure a Ring Supervisor

When you perform the Enable and Configure a Ring Supervisor request on a supervisor-capable device, configure the MSG instruction with the following information.

Enable and Configure a Ring Supervisor Attribute Description

Source Tag Attribute Name Description Possible Values

Ring Supervisor Config Ring Supervisor configuration parameters

SINT [0] Ring Supervisor Enable

Ring supervisor enable flag

0 = Node is configured as a normal ring node (default configuration)

1 = Node is configured as a ring supervisor

SINT [1] Ring Supervisor Precedence

Precedence value of a ring supervisor(1)


0 = Default value

SINT [2-5] Beacon Interval Duration of ring beacon interval

Valid value range = 200 s100000 s

Default = 400 s

SINT [6-9] Beacon Timeout Duration of ring beacon timeout(1)

Value value range = 400 s500000 s

Default value = 1960 s

SINT [10-11] DLR VLAN ID Valid ID to use in ring protocol messages(1)


Default value = 0

(1) RSLogix 5000 programming software may display the value in this field as negative numbers. To better understand the value, we recommend you view it in HEX format.48 Publication ENET-AP005C-EN-P - May 2010

Chapter 4

Troubleshoot a Linear or DLR Network

General Solutions for Linear or DLR Networks

Before you attempt to correct specific faults on your linear or DLR network, we recommend that you first take the following actions when a fault appears.

For a DLR network: verify that you have configured at least one node as a supervisor on

the network and that Network Topology = Ring. verify that all cables on the network are securely connected to each

device. verify that all devices that require an IP address have one assigned

correctly. check the Network Status field on the active supervisor nodes status

page to determine the fault type.

For a linear network: verify that none of the nodes are configured as a supervisor on

the network and that Network Topology = Linear.

If any nodes on a linear network are configured as a supervisor, it may impact communication to other devices connected to the network.

verify that all cables on the network are securely connected to each device.

verify that all devices that require an IP address have one assigned correctly.

If the fault is not cleared once you have completed the actions listed above, use the tables in the rest of this chapter to troubleshoot issues specific to a DLR network or a linear network.49Publication ENET-AP005C-EN-P - May 2010 49

Chapter 4 Troubleshoot a Linear or DLR NetworkSpecific Issues on Your DLR or Linear Network

Use the table below to troubleshoot possible specific issues on your DLR or linear network that are not solved by the actions described on the previous page.

Issue Description Solution

Supervisor Reports a Ring Fault

A link on the DLR network may be broken:

intentionally, for example, because you are adding or deleting nodes but have not made all physical connections to restore the set up of the network with/without the node.

unintentionally, for example, because a cable is broken or a device malfunctions.

When this fault occurs, the adjacent nodes to the faulted part of the network are displayed in the Ring Fault group and the Network Status field = Ring Fault.

The screen shot below shows the Ring Fault section with IP addresses appearing for the last active nodes. The faulted node is between nodes 10.88.80.115 and 10.88.80.208. If the IP address of either node is not available, the software will display the nodes MAC ID.

Once the fault is corrected, the ring is automatically restored, and the Network Status field returns to Normal.

Determine where the fault condition exists and correct it.

You may need to click the Refresh Communication link to update the Ring Fault information to determine where the fault condition exists.

Finally, you may want to use DevicePort Debugging Mode functionality on the 1783-ETAP tap to analyze a suspicious node.

For more information, refer to Device Port Debugging Mode on page 60.50 Publication ENET-AP005C-EN-P - May 2010

Troubleshoot a Linear or DLR Network Chapter 4Rapid Ring Fault When a Rapid Ring Fault occurs, the following events occur:

The active supervisor will block traffic on port 2, resulting in possible network segmentation, that is, some nodes may become unreachable.

The Link 2 status indicator on the active supervisor is off. As soon as the fault occurs, for both RSLogix 5000 programming software

and RSLinx communication software, the Status field = Rapid Fault/Restore Cycles.

Any of the following may cause a Rapid Ring Fault:

5 intentional disconnections/reconnections of a node from the network within 30 seconds

A duplex mismatch between two connected devices Electromagnetic noise on the network Unstable physical connections, such as intermittent connectors

Given the nature of a Rapid Ring Fault, the Last Active Node information may not be accurate when a Rapid Ring Fault condition is present

Multiple possible solutions exist.

For the disconnections and reconnections issue, no solution is required.

Clear the fault when you have reconnected the device to the network permanently.

For the duplex mismatch issue, reconfigure the duplex parameters to make sure they match between the devices.

For the electromagnetic noise issue, determine where the noise exists and eliminate it or use a protective shield in that location.

For the unstable connections issue, determine where they exist on the network and correct them.

Check the media counters for all devices on the network. The device with the highest media counter count is most likely causing the Rapid Ring Fault.

Remove devices from the network one by one. When you see the Rapid Ring Fault disappear after a device is removed, that device is causing the fault.

You may want to use DevicePort Debugging Mode functionality on the 1783-ETAP tap to analyze a suspicious node.

For more information, refer to Device Port Debugging Mode on page 60.

Finally, your Beacon Interval or Timeout configuration may not be appropriate for your network.

However, if you think you need to change these values, we recommend that you call Rockwell Automation technical support.

Once the fault is fixed, click Clear Fault.

Issue Description SolutionPublication ENET-AP005C-EN-P - May 2010 51

Chapter 4 Troubleshoot a Linear or DLR NetworkPartial Fault Condition

A partial network fault occurs when traffic is lost in only one direction on the network because a ring member is not forwarding beacons in both directions for some reason, such as because of a component failure.

The active ring supervisor detects a partial fault by monitoring the loss of Beacon frames on one port and the fault location appears in the Ring Fault section of the Network tab.

When a partial fault is detected, the active ring supervisor blocks traffic on one port. At this point, the ring is segmented due to the partial fault condition. The nodes adjacent to the faulted part of the network are displayed in the Ring Fault group with either IP addresses or MAC IDs for each node displayed.

When this fault occurs the Network Status field = Partial Fault Condition.

Once the fault is corrected, it automatically clears, and the Network Status field returns to Normal.

Determine where the fault condition exists and correct it.

Additionally, you may want to use DevicePort Debugging Mode functionality, also known as Port Mirroring, on a 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F tap to analyze a suspicious node.

For more information, refer to Device Port Debugging Mode on page 60.

Media Counter Errors or Collisions

The media counters screen displays the number of physical layer errors or collisions. The screen below indicates where to check for errors encountered. Error levels are displayed depending on what caused the error. For example, an Alignment Error is displayed in the Alignment Error field.

On a DLR network, it is not uncommon to see low levels of media counter errors. For example, if the network breaks, a low level of media counter errors appear. With a low level of media counter errors, the value typically does not continuously increase and often clears.

A high level of media counter errors typically continues to increase and does not clear. For example, there is a mismatchof speedbetween two linked nodes, a high level of media counter errors appears, steadily increasing and not clearing.

To access the RSLinx screen above, browse the network, right-click on the device, select Module Properties and click the Port Diagnostics tab.

Some example solutions include:

Check for a mismatch of speed and/or duplex between two linked nodes.

Verify that all cables on the network are securely connected to each device.

Check for electromagnetic noise on the network. If you find it, eliminate it or use a protective shield in that location.

Issue Description Solution52 Publication ENET-AP005C-EN-P - May 2010

Chapter 5

Additional 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F EtherNet/IP Tap Features

Introduction This chapter explains the additional features of the 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F EtherNet/IP tap.

Use DIP Switches Follow this procedure to set the DIP switches on your 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F tap.

Topic Page

Use DIP Switches 53

Internet Group Management Protocol (IGMP) Configuration Parameters

58

Device Port Debugging Mode 60

Replace a 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F Tap on the Network

62

Port Buffer Utilization 6353Publication ENET-AP005C-EN-P - May 2010 53

Chapter 5 Additional 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F EtherNet/IP Tap Features1. Move the switches to the desired position and power cycle the tap.

IMPORTANT Switch settings take effect only at power-up. If you change a taps switch settings after it is in operation, there is no change to the taps behavior until power is cycled to the tap.

Additionally, when you are setting the DIP swithes on your EtherNet/IP tap, you should consider the following:

If you are using a 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F tap in a linear network, make sure switch 3 is set to the Off position.

In many switch configurations, if switch 3 is set to the On position, the tap is automatically configured to be a ring supervisor. In a linear network, none of the nodes should be configured as a ring supervisor.

With regard to using switch 3 to automatically configure the tap to be a ring supervisor, the behavior described in table DIP Switch Settings and Results on page 55 applies for any 1783-ETAP1F or 1783-ETAP2F tap. However, the settings only cause the described power-up behavior for 1783-ETAP taps using firmware revision 2.x or later. If you set the switches as described on a 1783-ETAP tap with firmware revision 1.x, the described power-up behavior does not occur.

For more information, see page 55.54 Publication ENET-AP005C-EN-P - May 2010

Additional 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F EtherNet/IP Tap Features Chapter 52. Refer to graphic below and table on page 55 for DIP switch settings.DIP Switches

Off On

Switch 3

Switch 2

Switch 1

DIP Switch Settings and Results

Switch Power-up Behaviors for the 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F tap

1 2 3

Off Off Off The tap uses the Internet Protocol settings, that is, IP address, determined by one of the following:

- The RSLogix 5000 programming software configuration stored in the taps non-volatile storage (NVS) memory

- Factory default setting of 169.254.1.1

For other configuration settings, the tap uses what is stored in its NVS memory.

Off Off On The tap uses the Internet Protocol settings, that is, IP address, determined by one of the following:

- The RSLogix 5000 programming software configuration stored in the taps NVS memory- Factory default setting of 169.254.1.1

The tap is automatically configured to be a ring supervisor.

For other configuration settings, the tap uses what is stored in its NVS memory.(1)

On Off Off The tap uses the Internet Protocol settings, that is, IP address, determined by the BOOTP server.

For other configuration settings, the tap uses what is stored in its NVS memory.

On Off On The tap uses the Internet Protocol settings, that is, IP address, determined by the BOOTP server. The tap is automatically configured to be a ring supervisor.

For other configuration settings, the tap uses what is stored in its NVS memory.(1)

Off On Off The tap uses the Internet Protocol settings, that is, IP address, determined by the DHCP server. For other configuration settings, the tap uses what is stored in its NVS memory.

Off On On The tap uses the Internet Protocol settings, that is, IP address, determined by the DHCP server. The tap is automatically configured to be a ring supervisor.

For other configuration settings, the tap uses what is stored in its NVS memory.(1)Publication ENET-AP005C-EN-P - May 2010 55

Chapter 5 Additional 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F EtherNet/IP Tap Features3. Observe these guidelines when using the DIP switches:

Out-of-box, all three switches are in the Off position.

This is the software settable position. The tap uses either the default IP address or the IP address last programmed with RSLogix 5000 programming software.

When a switch is pushed to the left, it is in the Off position.

When a switch is pushed to the right, it is in the On position.

To select DHCP, move switch 2 to the On position.

To select BOOTP, move switch 1 to the On position.

On On Off The taps factory default settings are restored and then halted with the OK status indicator flashing red.

On On On The taps factory default settings are restored and then halted with the OK status indicator flashing red.

(1) These switch settings cause the described power-up/reset behavior for any 1783-ETAP1F or 1783-ETAP2F tap. However, the settings cause the described power-up/reset behavior only for 1783-ETAP taps using firmware revision 2.x or later. If you set the switches as described here on a 1783-ETAP tap with firmware revision 1.x, the described power-up/behavior does not occur.

DIP Switch Settings and Results

Switch Power-up Behaviors for the 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F tap

1 2 356 Publication ENET-AP005C-EN-P - May 2010

Additional 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F EtherNet/IP Tap Features Chapter 5 To enable ring supervisor function, move switch 3 to the On position. However, the change in tap behavior to operate as a ring supervisor only takes effect after the next tap power-cycle or reset.

To restore factory default settings, move the middle switch (switch 2 in the figure) and the switch closest to the tap front panel (switch 1 in the figure) both to the right, that is the On, position. For more information, see page 62.

When both the middle switch (switch 2 in the figure) and the switch closest to the tap front panel (switch 1 in the figure) are in the position, the tap resets all configuration settings stored in NVS to factory defaults, suspends operation, and the OK status indicator blinks red.

To resume normal operation, move the switches to the desired positions and cycle power to the module.

IMPORTANT For all 1783-ETAP1F and 1783-ETAP2F taps, the ring supervisor function is enabled when switch 3 is in the On position.

However, for the 1783-ETAP tap, the ring supervisor function is enabled when switch 3 is in the On position if the tap uses firmware revision 2.x or later. If you move switch 3 on a 1783-ETAP tap with firmware revision 1.x to the On position, the tap is not enabled as a ring supervisor.Publication ENET-AP005C-EN-P - May 2010 57

Chapter 5 Additional 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F EtherNet/IP Tap FeaturesInternet Group Management Protocol (IGMP) Configuration Parameters

The 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F taps support two Internet Group Management Protocol (IGMP) functions.

IGMP Snooping - Enabled by default IGMP Querier - Disabled by default

You can use either RSLogix 5000 programming software or RSLinx communication software to configure these parameters.

IGMP Snooping

This functionality is enabled by default in the 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F taps, and is commonly used to manage multicast traffic on the network. When in use, this functionality allows the tap to multicast data to only those devices that need the data rather than to all devices connected to the network.

The graphic below shows a ControlLogix controller receiving multicast data from I/O modules via a 1783-ETAP tap. The second ControlLogix controller does not receive unwanted multicast traffic.

IGMP Snooping

IMPORTANT For snooping to work, there must be a device present that is running a querier. Typically, the device is a router or a switch, such as the Stratix 6000, Stratix 8000, or Stratix 8300 managed switch.

1756-L63 Controller1756-EN2T

1756-EN2T1756 I/O Modules

Data Transmission

1783-ETAP Tap

1756-L63 Controller1756-EN2T58 Publication ENET-AP005C-EN-P - May 2010

Additional 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F EtherNet/IP Tap Features Chapter 5IGMP Querier

This functionality is disabled by default. The IGMP Querier functionality enables a 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F tap or switch, such as a Stratix managed switch, to send out a query to all devices on the network to determine what multicast addresses are of interest to a specific node or a group of nodes.

However, for all devices that you configure on the network with the IGMP Querier parameter enabled, you must also set an IP address other than the factory default value for those devices. If multiple devices on the network enable this functionality, only the node with the lowest IP address becomes the active IGMP Querier node.

IGMP Version

If you enable IGMP Querier, you must select a Querier Version. The default version is Version 2.

IMPORTANT You should enable the IGMP Querier functionality for at least one node on the network. The 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F taps, managed switches, and routers are examples of devices that support IGMP Querier functionality.

If you do not enable the IGMP Querier functionality for at least one node on the network, multicast traffic on the network may eventually create network performance issues.

Enable IGMP Querier here.

Select Querier Version here.Publication ENET-AP005C-EN-P - May 2010 59

Chapter 5 Additional 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F EtherNet/IP Tap FeaturesDevice Port Debugging Mode

This functionality is disabled by default. You can use Device Port Debugging mode, which is similar to port mirroring, to monitor data received on the 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F taps two network ports over the device port to a device, such as a personal computer running a protocol analyzer application for advanced network debugging or analysis.

When device port debugging is used on a 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F tap, the device connected to the 1783-ETAP taps front port receives all of the data traversing the ring (both directions).

When using the Device Port Debugging mode functionality, you insert the 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F tap, with the network analyzer connected to the device port, at the spot on the ring network where the node in question is located. The graphic below shows a 1783-ETAP tap inserted in the network.

Device Port Debugging Example Network

IMPORTANT This functionality should be used only when troubleshooting the network and not in normal network operation.

Personal Computer Analyzing Network Traffic

1783-ETAP Tap With Device Port Debugging Enabled

Break and insert60 Publication ENET-AP005C-EN-P - May 2010

Additional 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F EtherNet/IP Tap Features Chapter 5Combined total network bandwidth of the traffic received on the two 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F taps ports connected to the network should not exceed the taps device port capacity. The speed setting determines the device ports capacity.

You can configure the device port on a 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F tap to either of two speed settings:

100 Mbps - default setting 10 Mbps

If the bandwidth exceeds the capacity of the taps device port, some frames from the ring will be dropped before reaching the device port. These dropped frames do not impact the traffic on the rest of the DLR network.

The device port setting determines how much network traffic the 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F tap can handle before dropping frames. The circled section in the graphic below shows the Device Port Port Buffer Utilization. In this example the value is zero because a ring fault existson the network.Publication ENET-AP005C-EN-P - May 2010 61

Chapter 5 Additional 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F EtherNet/IP Tap FeaturesReplace a 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F Tap on the Network

There may be times when you need to replace a 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F tap on your network. In these instances, we recommend that you use a tap that is set to factory default settings. If you are unsure of a replacement tap's configuration, we recommend that you return the tap to its factory default configuration.

The following example shows how to return a 1783-ETAP tap to its factory default configuration. Follow these steps.

1. Power up the 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F tap with switches 1 and 2 set to On and switch 3 to Off as shown below.

2. Power off the tap.

3. Adjust the switches back to necessary setting to set the IP address. For more information on switch settings, see Use DIP Switches on page 53.

4. Power up the tap.

Switch 3

Switch 2

Switch 1

OFF ON62 Publication ENET-AP005C-EN-P - May 2010

Additional 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F EtherNet/IP Tap Features Chapter 5Port Buffer Utilization When you monitor the Port Buffer Utilization values on a 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F tap, you can monitor the values for:

Port 1. Port 2. Device Port.

You can monitor these fields from the Network tab for a 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F tap, as shown in the screen shot below.

If the values for any of these fields exceed 90% consistently, you should analyze and adjust your network design.

Do not use a single 1783-ETAP, 1783-ETAP1F, or 1783-ETAP2F tap to connect a large number, that is hundreds, of nodes on each port with a large amount of traffic flowing through this single tap. Doing so will significantly impact the taps ability to transmit the data between nodes.

We recommend that you connect a large number of devices by using managed switches. We also recommend that in your network design, you do not use more than 50 nodes on a single DLR network.

For more information on topology recommendations, see Common Network Topologies on page 65Publication ENET-AP005C-EN-P - May 2010 63

Chapter 5 Additional 1783-ETAP, 1783-ETAP1F, and 1783-ETAP2F EtherNet/IP Tap FeaturesNotes:64 Publication ENET-AP005C-EN-P - May 2010

Chapter 6

Common Network Topologies

Introduction Multiple common network topology combinations are shown in this chapter.

The intention of this chapter is to offer you a series of common topologies. Your use of these networks/topologies is not limited to these examples.

Topic Page

Standalone DLR Networks 67

Expanding Beyond Simple Linear or DLR Networks 68

Connecting to External Switches 68

Working with STP, RSTP, or MSTP 69

Working with Other Rings (Resilient Ethernet Protocol) 70

Other Non-device-level Ring Redundant Media Topologies 7165Publication ENET-AP005C-EN-P - May 2010 65

Chapter 6 Common Network TopologiesStandalone Linear Networks

The graphics below show two example standalone linear networks. We recommend that you do not use more than 50 nodes on a single linear network.

The example graphic uses Rockwell Automation products that support embedded switch technology, including 1783-ETAP taps, to construct a copper linear network.

The example graphic uses Rockwell Automation products that support embedded switch technology, including 1783-ETAP and 1783-ETAP1F taps, to connect copper and fiber-optic sections of a linear network.

1783-ETAP1F

Connection to fiber-optic section of the linear network

1783-ETAP66 Publication ENET-AP005C-EN-P - May 2010

Common Network Topologies Chapter 6Standalone DLR Networks

The graphics below show two standalone DLR networks. We recommend that you do not use more than 50 nodes on a single DLR network.

The example graphic shows how to use Rockwell Automation products that support embedded switch technology, including 1783-ETAP taps to construct a copper DLR network.

The example graphic shows how to use 1783-ETAP2F taps to connect Rockwell Automation products to a fiber-optic DLR network.



Ring Node Ring Node

DLR Network with Copper Connections



Ring Node Ring Node

DLR Network with fiber-optic ConnectionsPublication ENET-AP005C-EN-P - May 2010 67

Chapter 6 Common Network TopologiesExpanding Beyond Simple Linear or DLR Networks

This section shows the following topologies:

Connecting to External Switches Working with STP, RSTP, or MSTP Working with Other Rings (Resilient Ethernet Protocol) Other Non-device-level Ring Redundant Media Topologies

Connecting to External Switches

In this example, the 1783-ETAP taps on the DLR network can be connected to managed or unmanaged switches with star or linear topologies. Make sure you segment your network properly and limit the traffic sent between 1783-ETAP taps. For example limit the traffic from network A to network B.

To monitor how much the network traffic is using of a 1783-ETAP taps port capacity, check the Port Buffer Utilization values. For more information on Port Buffer Utilization, see page 63.

1783-ETAP

1783-ETAP

DLR Network

Stratix 2000

1783-ETAP

1783-ETAP

Network A Network B

Network C Network D

Stratix 2000

Stratix 2000

Stratix 2000

1738-AENT 1738-AENT1756-EN2T

1756-EN2T 1756-EN2T

1734-AENT

1734-AENT 1734-AENT68 Publication ENET-AP005C-EN-P - May 2010

Common Network Topologies Chapter 6Working with STP, RSTP, or MSTP

In this example, the managed switches that are used must support Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP) or Multiple Spanning Tree Protocol (MSTP) and have that protocol enabled.

If a fault

Date post:	28-Apr-2017
Category:	Documents
Upload:	victor-de-la-torre
View:	235 times
Download:	1 times

Ethernet Ip

Documents