Application Scenarios for LBDT

Detecting Loopbacks on an Interface

Figure 1 shows a loopback on an interface of the Switch. During network deployment, incorrect fiber connection or high voltage damage on the interface causes loopbacks to occur between the Tx (transmit end) and Rx (receive end) ends of an interface. Packets sent from one interface are forwarded back to the same interface, resulting in possible traffic forwarding errors or MAC address flapping on the interface.

Figure 1 Detecting loopbacks on an interface

You can configure LBDT on the interface of the Switch to detect loopbacks. When detecting a loopback on the interface, the Switch reports a trap and records a log, and takes a preconfigured action (such as Shutdown, Block, No learning, or Quitvlan) on the interface to reduce the impact of the loopback on the Switch. When the Switch detects that the loopback is eliminated on the interface, the interface can be restored. However, the interface shut down cannot be restored.

Detecting a Loop on the Downstream Network or Device

Figure 2 shows two network examples whereas a loop is detected on a downstream network or device connected to the Switch. Packets sent from Interface1 that pass through the downstream network or device are sent back to Interface1.

Figure 2 Detecting a loop on the downstream network or device

You can configure LBDT on Interface1 of the Switch to detect whether a loop occurs on the downstream network or device. When detecting a loop on the downstream network or device, the Switch reports a trap and records a log, and takes a preconfigured action (such as Shutdown, Block, No learning, or Quitvlan) on the interface to reduce the impact of the loop on the Switch. When the Switch detects that the loop is eliminated on the downstream network or device, the interface can be restored. However, the interface shut down cannot be restored.

Detecting a Loop Between Two Device Interfaces

As shown in Figure 3, a loop occurs on the network where the Switch resides. Packets sent from Interface1 are forwarded by devices on other networks and looped back to Interface2.

Figure 3 Detecting a loop between two device interfaces

You can configure LBDT on Interface1 and Interface2 of the Switch to detect whether a loop occurs on the local network or between two device interfaces. When detecting a loop, the Switch reports a trap and records a log, and takes preconfigured actions (such as Shutdown, Block, No learning, or Quitvlan) on Interface1 and Interface2 to reduce the impact of the loop on the Switch. When the Switch detects that the loop is eliminated on the local network or between two interfaces, Interface1 or Interface2 can be restored. However, the interface shut down cannot be restored.

Automatically Detecting Loops in the VLAN Specified by the PVID on an Interface

The switch joins VLAN 1 by default, and the PVID of all interfaces is VLAN 1. When an interface changes from Down to Up, a loop may occur. You can configure the switch to automatically detect loops in the VLAN specified by the PVID on the interface. When a loop is detected, only an alarm is reported.

By default, the switch is configured to automatically detect loops in the VLAN specified by the PVID on an interface. You can run the loopback-detect auto disable command to disable automatic loop detection.

Automatically Detecting Loops in the VLAN Where MAC Address Flapping Is Detected

The device is enabled with MAC address flapping detection by default. When the device detects MAC address flapping in a VLAN, automatic LBDT is triggered to detect loops in the VLAN. The device sends LBDT packets in the VLAN specified in the MAC address flapping record to detect whether there are loops. If loops exist in the VLAN where MAC address flapping occurs, a trap is only sent by default. For a loop between two device interfaces, you can run the loopback-detect auto action command to configure an action.