STP Deployment Solutions for Loop Prevention
On an M-LAG network, configure the Spanning Tree Protocol (STP) before network deployment to prevent loops caused by common faults. For details about the fault scenarios and deployment solutions, see Figure 2-2 and Table 2-2.
No. |
Fault Scenario |
Deployment Solution |
Command Reference |
---|---|---|---|
1 |
Multi-level M-LAG interconnection is deployed in dual-homed mode. When cables are incorrectly connected, packets passing through the peer-link form a loop. |
|
|
2 |
When a new device is added to an STP network, the device may dynamically preempt the STP root, causing STP network flapping. |
|
|
3 |
When a spine or server leaf node is attacked by BPDUs, it clears MAC address entries of other devices. Frequent flapping increases the CPU load and causes a large number of instantaneous flood packets. |
Enable TC BPDU attack defense on spine nodes, server leaf nodes, and DCI leaf nodes. This protects the devices from frequently deleting MAC address entries and ARP entries, avoiding over-burden. |
stp tc-protection |
4 |
Servers, firewalls, LBs, and routers do not support STP and do not need to participate in STP calculation. When the physical status of an interface changes, the convergence performance is poor because the peer device cannot send BPDU packets. |
Configure the interfaces on the spine and server leaf nodes that are connected to firewalls, LBs, servers, routers, and other hardware security devices as STP edge interfaces and deploy BPDU attack defense. |
stp edged-port enable stp bpdu-protection |
5 |
All interfaces on a switch are added to VLAN 1 by default. When a new device is added, a loop occurs between the added interfaces and the peer-link due to configuration or manual operations. |
Configure the peer-link and all physical and logical links to reject packets from VLAN 1. |
port vlan exclude 1 undo port trunk allow-pass vlan 1 |