Brocade BigIron RX Series Configuration Guide - Manual (Page 641)

BigIron RX Series Configuration Guide 563
53-1002484-04
Port loop detection support in MCT
20
interface ve 100
ip address 1.1.1.2/24
!
!
cluster MRPRing 1
rbridge-id 2
session-vlan 4090
member-vlan 2
icl MRPRing ethernet 1/1
peer 1.1.1.1 rbridge-id 1 icl MRPRing
deploy
client client-1
rbridge-id 100
client-interface ethernet 1/3
deploy
!
end
----------------------------------------
Client switch
lag "1" dynamic id 1
ports ethernet 1/1 to 1/4
primary-port 1/1
deploy
port-name "ICL-to-Switch-1:1/3" ethernet 1/1
port-name "ICL-to-Switch-1:1/4" ethernet 1/2
port-name "ICL-to-Switch-2:1/3" ethernet 1/1
port-name "ICL-to-Switch-2:1/4" ethernet 1/2
!
end
Port loop detection support in MCT
In MCT, the Port Loop Detection (PLD) is a protocol used to detect the Layer 2 loops caused by
misconfiguration. When a loop is detected in the network, the PLD protocol disables the port on
which the looped packet is received to prevent packet storms. When a receiving port is disabled by
PLD, the port will be disabled permanently. To bring up the port again, you must enable the port
under the interface configuration. Optionally, you can configure the duration for which the port
must be down, after which the port will be enabled again.
PLD protocol runs in two different modes:
• Strict mode - With the loop detection configured under a physical port, the PLD protocol
disables a port if a packet is received back on the same interface from which the packet was
originally sent out.
• Loose mode - With the loop detection configured under a VLAN, the PLD protocol disables the
receiving port of packets originated from the same device as long as the receiving VLAN has
the loop detection configured.
Configuring port loop detection
The PLD protocol is disabled by default. The protocol can be enabled on a physical port (strict
mode) or VLAN (loose mode). To configure the loop detection for a physical port, enter commands
such as the following.