BRCD Edge Loop Detection DP PDF

53-1003490-01
September 2014
Brocade Edge Loop

Detection (ELD)
Deployment Guide
2014, Brocade Communications Systems, Inc. All Rights Reserved.
Brocade, the B-wing symbol, Brocade Assurance, ADX, AnyIO, DCX, Fabric OS, FastIron, HyperEdge, ICX, MLX, MyBrocade, NetIron,
OpenScript, VCS, VDX, and Vyatta are registered trademarks, and The Effortless Network and the On-Demand Data Center are trademarks
of Brocade Communications Systems, Inc., in the United States and in other countries. Other brands and product names mentioned may be
trademarks of others.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any
equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document
at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be
currently available. Contact a Brocade sales office for information on feature and product availability. Export of technical data contained in
this document may require an export license from the United States government.
The authors and Brocade Communications Systems, Inc. assume no liability or responsibility to any person or entity with respect to the
accuracy of this document or any loss, cost, liability, or damages arising from the information contained herein or the computer programs that
accompany it.
The product described by this document may contain open source software covered by the GNU General Public License or other open
source license agreements. To find out which open source software is included in Brocade products, view the licensing terms applicable to
the open source software, and obtain a copy of the programming source code, please visit http://www.brocade.com/support/oscd.
Contents
Brocade Edge Loop Detection (ELD) Deployment Guide..............................................................5
Preface..............................................................................................................5
ELD Configuration.............................................................................................5
Configuring the Access Interface.......................................................... 6
Configuring Port Channels and Multiple Instances............................... 7
ELD Port-Priority Configuration...........................................................10
ELD Hello-Interval Configuration.........................................................12
ELD PDU RX Limit Configuration........................................................12
ELD Shutdown Time Configuration.....................................................13
Loop Detection and Removal..........................................................................14
Port Channel Configuration.................................................................15
Viewing ELD Counters........................................................................ 15
Loop Detection.................................................................................... 16
Post Loop Interface State....................................................................18
Post Loop ELD State...........................................................................19
Brocade Edge Loop Detection (ELD) Deployment Guide

53-1003490-01

53-1003490-01

Copyright Statement.................................................................................................... 0
Preface..............................................................................................................................5
ELD Configuration.............................................................................................................5
Loop Detection and Removal..........................................................................................14
Preface
This document is a deployment guide for implementing Edge Loop Detection in a Brocade VCS fabric.
ELD allows better utilization of network capacity without sacrificing reliability or increasing design
complexity.
This document is written for technology decision-makers, architects, systems engineers, NOC
engineers and other experts responsible for network upgrades and migration. It provides step-by-step
procedures and examples to perform and verify ELD configuration. For design considerations, refer to
the Edge Loop Detection Design Guide.
It is assumed that the reader is familiar with establishing console access and entering commands using
the Brocade CLI. For information about the Brocade CLI, refer to theNetwork OS Administration Guide.
Document History
Date
Version
Description
September 2014
Initial version for NOS versions up to

Release 5.0.0.
ELD Configuration
This section describes the configuration required to implement ELD. Figure 1 illustrates the topology of
the example used for this configuration:

53-1003490-01
Configuring the Access Interface
FIGURE 1 Enabling ELD on a Physical Interface
In this example, a server is connected to the VCS fabric edge, through a physical interface (Ten 6/2/1)
on 8770_RB6.
Configuring the Access Interface

This section describes the basic configuration of ELD on a VCS edge access interface. The
configuration switchport access vlan <> designates this interface as untagged. The configuration
edge-loop-detection vlan < > specifies the VLAN where ELD is enabled.
NOTE
The interface must be a member of the VLAN to enable ELD on the interface.
Configuring ELD on a Physical Interface (Untagged)

8770_RB6# show running-config interface TenGigabitEthernet 6/2/1
interface TenGigabitEthernet 6/2/1
fabric isl enable
fabric trunk enable
switchport
switchport mode access
switchport access vlan 928 <-Access VLAN = Untagged
edge-loop-detection vlan 928 <-ELD enabled on VLAN 928
spanning-tree shutdown
no shutdown
After applying this configuration, the show command displays interface ELD information that indicates
the following:
Number of ELD instances on the interface.

VLAN where ELD is enabled.
ELD priority, which determines the interface to bring down in event of a bi-directional loop.
Protocol status: UP indicates that the protocol is active.

53-1003490-01
Configuring Port Channels and Multiple Instances
Verifying ELD on a Physical Interface (Untagged)

8770_RB6# show edge-loop-detection interface tengigabitethernet 6/2/1
Number of eld instances: 1 <- instance count for this interface = 1 (enabled on one
VLAN only)
Enabled on VLANs:
928 <_VLAN matches configured ELD VLAN
Priority:
128 <- Default ELD interface priority
Protocol status:
UP <-Indicates ELD protocol is active
Auto enable in:
Never <-Indicates that interface will NOT be re-enabled
automatically if brought down by ELD
Packet Statistics:
vlan
sent
rcvd
928
3405238
0 <-TX/RX ELD counters (0 received and incrementing
of TX counters is verified below)
8770_RB6# show edge-loop-detection interface tengigabitethernet 6/2/1
Number of eld instances: 1
Enabled on VLANs:
928
Priority:
128
Protocol status:
UP
Auto enable in:
Never
Packet Statistics:
vlan
sent
928
3405884
consecutive outputs
rcvd
0 <- Transmit count of ELD frames incrementing on
Configuring Port Channels and Multiple Instances

The following section describes the required ELD configuration for port channel interfaces spanning
multiple VDX switches (vLAG).
FIGURE 2 Port Channel Example
The configuration of this example, shown in Figure 2 is as follows:

Port Channel 79 spans Rbridge 7 (6740-RB7) and 8 (6740-RB8).
The vLAG designation identifies the port channel as spanning two or more physical nodes.
The * on the member port identifies it as the primary port, meaning it is the link member responsible
for forwarding multicast and broadcast frames.

53-1003490-01
To configure the port channels and enable ELD in the example deployment, complete the following
steps:
Procedure
Step 1: Configure the port channel on Rbridge 7.
6740-RB7# show port-channel 79
LACP Aggregator: Po 79 (vLAG) <-vLAG designation
Aggregator type: Standard
Ignore-split is enabled
Member rbridges:
rbridge-id: 7 (1) <-refers to physical rbridge 7
rbridge-id: 8 (1) <- refers to physical rbridge 8
Admin Key: 0079 - Oper Key 0079
Partner System ID - 0x0001,10-1f-74-78-c6-cf
Partner Oper Key 0031
Member ports on rbridge-id 7:
Link: Te 7/0/21 (0x7180A8014) sync: 1
* <-Primary LAG member
Step 2: Configure the port channel on Rbridge 8.

6740-RB8# show port-channel 79
LACP Aggregator: Po 79 (vLAG)
Aggregator type: Standard
Ignore-split is enabled
Member rbridges:
rbridge-id: 7 (1)
rbridge-id: 8 (1)
Admin Key: 0079 - Oper Key 0079
Partner System ID - 0x0001,10-1f-74-78-c6-cf
Partner Oper Key 0031
Member ports on rbridge-id 8:
Link: Te 8/0/21 (0x8180A8014) sync: 1
The port-channel configuration is shown below that includes ELD on all VLANs.
NOTE
The port channel and ELD configuration must be replicated on both rbridges in the vLAG.
The example shown here on Rbridge 7 and 8 indicates the following:
ELD is enabled on all VLANs configured on the Port Channel (18 VLANs in total)
Native VLAN 926 is untagged and has ELD enabled. ELD frames are sent untagged in this case.
Remaining VLANs (other than 926) are sent tagged.
Step 3: Configure ELD on the port channel on Rbridge 7.
6740-RB7# show running-config interface Port-channel 79
interface Port-channel 79
vlag ignore-split
switchport
switchport mode trunk
switchport trunk allowed vlan add 24,31,50-51,81,601-602,901,915,918-919,922,924926,932,946-947
no switchport trunk tag native-vlan
switchport trunk native-vlan 926
edge-loop-detection vlan
24,31,50-51,81,601-602,901,915,918-919,922,924-926,932,946-947
no shutdown
Step 4: Configure ELD on the port channel on Rbridge 8.

vlag ignore-split
switchport
switchport trunk allowed vlan add 24,31,50-51,81,601-602,901,915,918-919,922,924926,932,946-947

53-1003490-01
24,31,50-51,81,601-602,901,915,918-919,922,924-926,932,946-947
no shutdown
The ELD show commands indicate the following:

Number of ELD instances for Port Channel 79 is 18, matching the configuration above.
ELD transmit counts increase in consecutive show commands on Rbridge 7 only. Rbridge 7 has the
primary LAG member responsible for transmitting multicast and broadcast frames.
Rbridge 8 ELD Transmit count is 0 and not incrementing, as expected.
Protocol status shows UP.
Step 5: Verify ELD port channel configuration on Rbridge 7.
6740-RB7# show edge-loop-detection int port-channel 79
rbridgeid: 7
Enabled on VLANs:
24,31,50-51,81,601-602,901,915,918-919,922,924-926,932,946-947
Priority:
128
Protocol status:
UP
Auto enable in:
Never
Packet Statistics:
vlan
sent
24
647460
31
647460
50
647460
51
647460
81
647460
601
647460
602
647460
901
647460
915
647460
918
647460
919
647460
922
647460
924
647460
925
647460
926
647460
932
647460
946
647460
947
647460
rcvd
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
6740-RB7#
rbridgeid: 7
Enabled on VLANs:
24,31,50-51,81,601-602,901,915,918-919,922,924-926,932,946-947
Priority:
128
Protocol status:
UP
Auto enable in:
Never
Packet Statistics:
vlan
sent
24
651790
31
651790
50
651790
51
651790
81
651790
601
651790
602
651790
901
651790
915
651790
918
651790
919
651790
922
651790
924
651790
925
651790
926
651790
932
651790
946
651790
947
651790

53-1003490-01
rcvd
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
ELD Port-Priority Configuration
Step 6: Verify the ELD port channel configuration on Rbridge 8.

rbridgeid: 8
Enabled on VLANs:
24,31,50-51,81,601-602,901,915,918-919,922,924-926,932,946-947
Priority:
128
Protocol status:
UP
Auto enable in:
Never
Packet Statistics:
vlan
sent
24
0
31
0
50
0
51
0
81
0
601
0
602
0
901
0
915
0
918
0
919
0
922
0
924
0
925
0
926
0
932
0
946
0
947
0
rcvd
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
ELD Port-Priority Configuration

This section describes how to configure ELD priority on a port-channel that spans Rbridge 7 and 8.
NOTE
ELD priority is a per interface configuration parameter and in the case of port-channels that span 2 or
more physical nodes the ELD priority must be configured on all nodes in the port-channel to maintain
behavior consistency.
To configure ELD priority on a port-channel that spans Rbridge 7 and 8, complete the following steps:
Procedure
Step 1: Configure ELD port priority on Rbridge 7.
vlag ignore-split
switchport
switchport trunk allowed vlan add
24,31,50-51,81,601-602,901,915,918-919,922,924-926,932,946-947
edge-loop-detection port-priority 100 <- Configured non-default ELD priority
24,31,50-51,81,601-602,901,915,918-919,922,924-926,932,946-947
no shutdown
!
6740-RB7#
6740-RB7# show edge-loop-detection interface port-channel 79
rbridgeid: 7
Enabled on VLANs:
10

53-1003490-01
24,31,50-51,81,601-602,901,915,918-919,922,924-926,932,946-947
Priority:
100
<- Configured ELD priority
Protocol status:
UP
Auto enable in:
Never
Packet Statistics:
vlan
sent
24
800706
31
800706
50
800706
51
800706
81
800706
601
800706
602
800706
901
800706
915
800706
918
800706
919
800706
922
800706
924
800706
925
800706
926
800706
932
800706
946
800706
947
800706
rcvd
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
6740-RB7#
Step 2: Configure ELD port priority on Rbridge 8.

vlag ignore-split
description brbh1022-vc1
switchport
24,31,50-51,81,601-602,901,915,918-919,922,924-926,932,946-947
edge-loop-detection port-priority 100
24,31,50-51,81,601-602,901,915,918-919,922,924-926,932,946-947
no shutdown
!
rbridgeid: 8
Enabled on VLANs:
24,31,50-51,81,601-602,901,915,918-919,922,924-926,932,946-947
Priority:
100
Protocol status:
UP
Auto enable in:
Never
Packet Statistics:
vlan
sent
24
0
31
0
50
0
51
0
81
0
601
0
602
0
901
0
915
0
918
0
919
0
922
0
924
0
925
0
926
0
932
0
946
0
947
0

53-1003490-01
rcvd
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
11
ELD Hello-Interval Configuration
6740-RB8#
ELD Hello-Interval Configuration

This section describes the configuration of the ELD hello-interval for Rbridge 7 and 8.
NOTE
ELD hello-interval is a global configuration parameter per node and for consistent results is required to
be the same on all Rbridges that have member links in a given port channel.
Procedure
Step 1: Configure the ELD hello interval on Rbridge 8.
6740-RB8# conf t
Entering configuration mode terminal
6740-RB8(config)# protocol edge-loop-detection
6740-RB8(conf-eld)# hello-interval ?
Possible completions:
<100-5000>
Millisecond (Default: 1000)[100] <- Default of 1s
6740-RB8(conf-eld)# hello-interval 100
6740-RB8(conf-eld)#exit
6740-RB8# show running-config protocol edge-loop-detection
protocol edge-loop-detection
hello-interval 100
Step 2: Verify ELD hello interval on Rbridge 8.

6740-RB8# show edge-loop-detection globals
Edge-loop-detection global configuration values are as below:
PDU receive limit (packets):
Shutdown-time (minutes):
Hello-time (msec):
1
0
100
Step 3: Verify ELD hello interval on Rbridge 8.

Hello-time (msec):
1
0
100
ELD PDU RX Limit Configuration

This section describes the configuration of the ELD PDU-RX-LIMIT for Rbridge 7 and 8.
NOTE
ELD PDU-RX-LIMIT is a global configuration parameter per node and for consistent results is required
to be the same on all Rbridges that have member links in given port-channel.
To configure the ELD PDU-RX-LIMIT for Rbridge 7 and 8, complete the following steps:
12

53-1003490-01
ELD Shutdown Time Configuration
Procedure
Step 1: Configure the ELD PDU RX limit on Rbridge 7.
6740-RB7# conf t
6740-RB7(conf-eld)# pdu-rx-limit ?
<1-5>
Number (Default: 1)[1] <- Default
6740-RB7(conf-eld)# pdu-rx-limit 5
Step 2: Verify the ELD PDU RX limit on Rbridge 7.

protocol output
Hello-time (msec):
<- Configured value above reflected in global
0
100
Step 3: Configure the PDU RX limit on Rbridge 8.

6740-RB8# conf t
6740-RB8(conf-eld)# pdu-rx-limit 5
Step 4: Verify the ELD PDU RX limit on Rbridge 8.

protocol output
Hello-time (msec):
<- Configured value above reflected in global
0
100
ELD Shutdown Time Configuration

This section describes how to configure the ELD Shutdown Time for Rbridge 7 and 8.
NOTE
ELD Shutdown Time is a global configuration parameter per node and for consistent results should be
the same on all rbridges with member links in a given port channel.
To configure the ELD Shutdown Time for Rbridge 7 and 8, complete the following steps:
Procedure
Step 1: Configure ELD Shutdown Time on Rbridge 7.
6740-RB7# conf t
6740-RB7(conf-eld)# shutdown-time ?
<0, 10-1440>
Minute (Default: 0)[0]
<- default is 0 i.e. requires manual
intervention to re-enable after ELD disables an interface
6740-RB7(conf-eld)# shutdown-time 10
6740-RB7(conf-eld)#
Step 2: Verify ELD Shutdown Time on Rbridge 7.


53-1003490-01
13
Loop Detection and Removal

global output
Hello-time (msec):
5
10
<- Configured shutdown time reflected in the
100
Step 3: Configure ELD Shutdown Time on Rbridge 8.

6740-RB8# conf t
6740-RB8(conf-eld)# shutdown-time 10
6740-RB8(conf-eld)#
Step 4: Verify ELD Shutdown Time on Rbridge 8.

global output
Hello-time (msec):
5
10
<- Configured shutdown time reflected in the
100
Loop Detection and Removal

This document demonstrates the operation and configuration of ELD in a VCS fabric. The example
shown in Figure 2 on page 7 illustrates the example configuration. In this example, a Layer 2 loop will
be created between two port-channels (91 and 92) with ELD enabled on both.
As illustrated in Figure 1 on page 6, each port-channel is connected to a separate Layer 2 switch.
Overlapping VLANs are configured on both port channels and the corresponding switches. No loop
exists in the starting topology because both physical links in the port-channel are treated as a single
interface from the fabric forwarding point of view.
FIGURE 3 ELD Enabled on Port Channels
Port Channels 91 and 92, as shown in Figure 3 , each span two physical rbridges, as follows:
Physical ports for Port Channel 91 reside on Rbridge 1 and 2
Physical ports for Port Channel 92 reside on Rbridge 1 and 2
14

53-1003490-01
Port Channel Configuration
ELD is configured on both port-channels for all VLANs enabled, as shown in the output later in this
document.
Port Channel Configuration

In most cases, a Layer 2 loop formed at the edge of a VCS fabric is likely to be a physical loop affecting
all VLANs on a given interface. Therefore, only one ELD instance per interface is required for detection
and prevention of loops.
E nabling ELD on all the VLANs on a given interface is recommended when a loop can be created on a
specific VLAN without affecting the other VLANs. Certain network devices connected to the VCS edge,
such as Layer 2 switches or load balancers in a chassis based server with embedded Layer 2 switches,
may be subject to misconfiguration or link failure.
If ELD protection is required on all the VLANs for a given interface, the native VLAN must also be
included. In the configuration given below the native VLAN on the port hannels is 1 (default) and VLAN
1 is included in the list of ELD-enabled VLANs.
Configuring Port Channel 91 and 92 for ELD
Rbridge_1# show running-config interface Port-channel 91

vlag ignore-split
switchport
2-3,24,31,50,60,81,136,901,915,918-919,924-928,932,947,1005
switchport trunk tag native-vlan
edge-loop-detection vlan 1-3,24,31,50,60,81,136,901,915,918-919,924-928,932,947,1005
no shutdown
!
Rbridge_1# show running-config interface Port-channel 92
vlag ignore-split
switchport
2-3,24,31,50,60,81,136,901,915,918-919,924-928,932,947,1005
switchport trunk tag native-vlan
edge-loop-detection vlan 1-3,24,31,50,60,81,136,901,915,918-919,924-928,932,947,1005
spanning-tre
Viewing ELD Counters

Before a Layer 2 loop is created between Port Channels 91 and 92, the steady-state ELD counters on
both interfaces show incrementing transmit ELD counters. The ELD receive counter remains at zero (0)
in both cases, indicating that no ELD frames have been received.
Displaying ELD Statistics for Port Channel 91
Rbridge_1# show edge-loop-detection interface port-channel 91

rbridgeid: 1
Enabled on VLANs:
1-3,24,31,50,60,81,136,901,915,918-919,924-928,932,947,1005
Priority:
128 <- Default priority
Protocol status:
UP
Auto enable in:
Never
Packet Statistics:
vlan
sent
1
1529
2
1529
3
1529
24
1529
31
1529
50
1529

53-1003490-01
rcvd
0
0
0
0
0
0
15
Loop Detection
60
81
136
901
915
918
919
924
925
926
927
928
932
947
1529
1529
1529
1529
1529
1529
1529
1529
1529
1529
1529
1529
1529
1529
1529
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Displaying Statistics for Port Channel 92

rbridgeid: 1
Enabled on VLANs:
1-3,24,31,50,60,81,136,901,915,918-919,924-928,932,947,1005
Priority:
128 <- Default Priority
Protocol status:
UP
Auto enable in:
Never
Packet Statistics:
vlan
sent
1
2147
2
2147
3
2147
24
2147
31
2147
50
2147
60
2147
81
2147
136
2147
901
2147
915
2147
918
2147
919
2147
924
2147
925
2147
926
2147
927
2147
928
2147
932
2147
947
2147
1005
2147
rcvd
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Loop Detection
In the example shown in Figure 2 on page 7, a loop has been created between Port Channels 91 and
92 through misconfiguration of the attached network devices, linking Port Channel 91 and 92 together
on VLAN 918. The ELD protocol detects and breaks the loop. The sequence of events is as follows:
1. A Layer 2 interface is configured between Switch 1 and Switch 2 for VLAN 918.
2. Tagged VLAN 918 ELD frames from Port Channel 91 are forwarded from Switch 1 to Switch 2
(MCAST)
3. Tagged VLAN 918 ELD frames from Port Channel 92 are forwarded from Switch 2 to Switch 1
(MCAST)
4. Switch 2 floods the ELD frame from Port Channel 91 out all VLAN 918 interfaces, including the LAG
connected to Port Channel 92.
5. Switch 1 floods the ELD frame from Port Channel 92 out all VLAN 918 interfaces, including the LAG
connected to Port Channel 91.
6. Rbridge 1 Port Channel 92 receives ELD frame from Port Channel 91. ELD shuts Port Channel 92
on Rbridge 1 after comparing the priority in the ELD framesto interface priority. The default priorities
16

53-1003490-01
are used (128 on both), and in case of a tie, the lower interface number is given preference. As a
result, Port Channel 92 is disabled and Port Channel 91 remains up.
7. After step 6, one link remains up in Port Channel 92 on Rbridge 2. Steps 5 and 6 repeat on Rbridge
2. Note that this sequence depends on which Rbridge receives the first ELD frame. In the log
captures shown, the time stamps for the interface going down are the same as the ELD hello-interval
(100 ms) and the system console logs are shown with resolution in seconds.
8. ELD frames received on Port Channel 91 from Port Channel 92 do not trigger interface shutdown
because the received ELD frame has an equal port priority (default) and Port Channel 91 wins the tie
due to its lower interface number.
FIGURE 4 Loop Detection
The logs highlighted below indicate the following:

Rbridge_1: A loop is detected by ELD on Port Channel 92 VLAN 918.
Rbridge_1: Interface Port Channel 92 is shut down by the ELD protocol as a result of the loop
[ELD-1001].
Rbridge_2: A loop is detected by ELD on Port Channel 92 VLAN 918.
Rbridge_2: Interface Port Channel 92 is shut down by the ELD protocol as a result of the loop
[ELD-1001].
Displaying Rbridge_1 Logs
Rbridge_1# 2014/08/05-13:23:59, [ELD-1001], 135952, DCE, INFO, Rbridge_1, Interface

po92
is shut down by edge loop detection (ELD) for loop in VLAN 918.
2014/08/05-13:23:59, [NSM-1003], 135953, DCE, INFO, Rbridge_1, Interface Portchannel 92
is link down.
2014/08/05-13:23:59, [NSM-1002], 135954, DCE, INFO, Rbridge_1, Interface
TenGigabitEthernet 1/5/22 is protocol down.

53-1003490-01
17
Post Loop Interface State

TenGigabitEthernet 1/5/22 is link down.
2014/08/05-13:23:59, [NSM-1025], 135956, DCE, INFO, Rbridge_1, RBridge ID 1 has
left Portchannel 92. Port-channel has only RBridge ID 2 and is no longer a vLAG.
Displaying Rbridge 2 Logs
Rbridge_2# 2014/08/05-13:23:59, [NSM-1025], 56214, DCE, INFO, Rbridge_2, RBridge ID

1 has
left Port-channel 92. Port-channel has only RBridge ID 2 and is no longer a vLAG.
2014/08/05-13:23:59, [ELD-1001], 56215, DCE, INFO, Rbridge_2, Interface po92 is
shut down
by edge loop detection (ELD) for loop in VLAN 918.
2014/08/05-13:23:59, [NSM-1003], 56216, DCE, INFO, Rbridge_2, Interface Portchannel 92 is
link down.
TenGigabitEthernet
2/5/22 is protocol down.
TenGigabitEthernet
2/5/22 is link down.
Post Loop Interface State

After the Layer 2 loop has been detected and removed, the port channel interface states are shown
with line protocol down ("ELD disabled link") to differentiate the down state from an LACP or other
Layer 2 issue.
Displaying Rbridge 1 Interface State
Rbridge_1# show interface port-channel 92

Port-channel 92 is up, line protocol is down (ELD disabled link)
Hardware is AGGREGATE, address is 0027.f8df.e3f1
Current address is 0027.f8df.e3f1
Interface index (ifindex) is 671088732
Minimum number of links to bring Port-channel up is 1
MTU 2500 bytes
LineSpeed Actual
: Nil
Allowed Member Speed : 10000 Mbit
Flowcontrol rx: off, tx: off
Priority Tag disable
IPv6 RA Guard disable
Last clearing of show interface counters: 00:16:22
Queueing strategy: fifo
Receive Statistics:
60 packets, 7709 bytes
Unicasts: 0, Multicasts: 60, Broadcasts: 0
64-byte pkts: 0, Over 64-byte pkts: 1, Over 127-byte pkts: 59
Over 255-byte pkts: 0, Over 511-byte pkts: 0, Over 1023-byte pkts: 0
Over 1518-byte pkts(Jumbo): 0
Runts: 0, Jabbers: 0, CRC: 0, Overruns: 0
Errors: 0, Discards: 0
Transmit Statistics:
Underruns: 0
Rate info (interval 299 seconds):
Input 0.000000 Mbits/sec, 0 packets/sec, 0.00% of line-rate
Output 0.000000 Mbits/sec, 0 packets/sec, 0.00% of line-rate
Time since last interface status change: 00:03:34
Displaying Rbridge 2 Interface State
Rbridge_2# show interface port-channel 92

Port-channel 92 is up, line protocol is down (ELD disabled link)
Hardware is AGGREGATE, address is 0027.f8df.4985
Current address is 0027.f8df.4985
Interface index (ifindex) is 671088732
Minimum number of links to bring Port-channel up is 1
MTU 2500 bytes
LineSpeed Actual
: Nil
Allowed Member Speed : 10000 Mbit
Flowcontrol rx: off, tx: off
18

53-1003490-01
Post Loop ELD State
Priority Tag disable

IPv6 RA Guard disable
Last clearing of show interface counters: 00:15:42
Queueing strategy: fifo
Receive Statistics:
64-byte pkts: 0, Over 64-byte pkts: 91283, Over 127-byte pkts: 51
Over 255-byte pkts: 0, Over 511-byte pkts: 0, Over 1023-byte pkts: 0
Over 1518-byte pkts(Jumbo): 0
Runts: 0, Jabbers: 0, CRC: 0, Overruns: 0
Transmit Statistics:
Underruns: 0
Rate info (interval 299 seconds):
Input 0.000000 Mbits/sec, 0 packets/sec, 0.00% of line-rate
Output 0.000000 Mbits/sec, 0 packets/sec, 0.00% of line-rate
Time since last interface status change: 00:04:34
Post Loop ELD State

After the loop condition occurs, the ELD details for Port Channel 92 indicate the following:
Protocol status: Down due to ELD event on VLAN 918.
ELD received counter has incremented on VLAN 918, showing that an ELD frame was received on
this VLAN.
Rbridge_1 ELD Logs
Rbridge_1# show edge-loop-detection int port-channel 92

rbridgeid: 1
Enabled on VLANs:
1-3,24,31,50,60,81,136,901,915,918-919,924-928,932,947,1005
Priority:
128
Protocol status:
DOWN (due to eld on vlan 918)
Auto enable in:
Never
Packet Statistics:
vlan
sent
1
5549
2
5549
3
5549
24
5549
31
5549
50
5549
60
5549
81
5549
136
5549
901
5549
915
5549
918
5549
919
5549
924
5549
925
5549
926
5549
927
5549
928
5549
932
5549
947
5549
1005
5549
rcvd
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
Rbridge_2 ELD Logs

rbridgeid: 2
Enabled on VLANs:
1-3,24,31,50,60,81,136,901,915,918-919,924-928,932,947,1005
Priority:
128

53-1003490-01
19
Protocol status:
Auto enable in:
Packet Statistics:
vlan
sent
1
1
2
1
3
1
24
1
31
1
50
1
60
1
81
1
136
1
901
1
915
1
918
1
919
1
924
1
925
1
926
1
927
1
928
1
932
1
947
1
1005
1
20
DOWN (due to eld on vlan 918)

Never
rcvd
0
0
0
0
0
0
0
0
0
0
0
2
0
0
0
0
0
0
0
0
0

53-1003490-01

BRCD Edge Loop Detection DP PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BRCD Edge Loop Detection DP PDF

Uploaded by

Copyright:

Available Formats

53-1003490-01

Brocade Edge Loop

2014, Brocade Communications Systems, Inc. All Rights Reserved.

Brocade Edge Loop Detection (ELD) Deployment Guide

Brocade Edge Loop Detection (ELD) Deployment Guide

Brocade Edge Loop Detection (ELD) Deployment Guide

Initial version for NOS versions up to

Brocade Edge Loop Detection (ELD) Deployment Guide

Configuring the Access Interface

FIGURE 1 Enabling ELD on a Physical Interface

Configuring the Access Interface

Configuring ELD on a Physical Interface (Untagged)

Number of ELD instances on the interface.

Brocade Edge Loop Detection (ELD) Deployment Guide

Configuring Port Channels and Multiple Instances

Verifying ELD on a Physical Interface (Untagged)

Configuring Port Channels and Multiple Instances

The configuration of this example, shown in Figure 2 is as follows:

Brocade Edge Loop Detection (ELD) Deployment Guide

Brocade Edge Loop Detection (ELD) Deployment Guide

Step 2: Configure the port channel on Rbridge 8.

Step 4: Configure ELD on the port channel on Rbridge 8.

Brocade Edge Loop Detection (ELD) Deployment Guide

Brocade Edge Loop Detection (ELD) Deployment Guide

The ELD show commands indicate the following:

Brocade Edge Loop Detection (ELD) Deployment Guide

ELD Port-Priority Configuration

Step 6: Verify the ELD port channel configuration on Rbridge 8.

ELD Port-Priority Configuration

Brocade Edge Loop Detection (ELD) Deployment Guide

Brocade Edge Loop Detection (ELD) Deployment Guide

Step 2: Configure ELD port priority on Rbridge 8.

Brocade Edge Loop Detection (ELD) Deployment Guide

ELD Hello-Interval Configuration

ELD Hello-Interval Configuration

Step 2: Verify ELD hello interval on Rbridge 8.

Step 3: Verify ELD hello interval on Rbridge 8.

ELD PDU RX Limit Configuration

Brocade Edge Loop Detection (ELD) Deployment Guide

ELD Shutdown Time Configuration

Step 2: Verify the ELD PDU RX limit on Rbridge 7.

<- Configured value above reflected in global

Step 3: Configure the PDU RX limit on Rbridge 8.

Step 4: Verify the ELD PDU RX limit on Rbridge 8.

<- Configured value above reflected in global

ELD Shutdown Time Configuration

Step 2: Verify ELD Shutdown Time on Rbridge 7.

Brocade Edge Loop Detection (ELD) Deployment Guide

Loop Detection and Removal

PDU receive limit (packets):

<- Configured shutdown time reflected in the

Step 3: Configure ELD Shutdown Time on Rbridge 8.

Step 4: Verify ELD Shutdown Time on Rbridge 8.

<- Configured shutdown time reflected in the

Loop Detection and Removal

Brocade Edge Loop Detection (ELD) Deployment Guide

Port Channel Configuration

Port Channel Configuration

Rbridge_1# show running-config interface Port-channel 91

Viewing ELD Counters

Rbridge_1# show edge-loop-detection interface port-channel 91

Brocade Edge Loop Detection (ELD) Deployment Guide

Displaying Statistics for Port Channel 92