Vxlan loop prevention

Created: Oct 31, 2019 02:41:03Latest reply: Oct 31, 2019 02:47:34 99 2 1 1
  Rewarded Hi-coins: 0 (problem resolved)

Hello everyone,

How to prevent loops when a VXLAN tunnel is established between CE1 and CE3?

Topo

vxlan

1. The physical link between 1.CE1 and CE3 is an L3 layer link and carries other services.

2. CE1 and CE3 use VBDIF as the gateway.

3. CE1 and CE3 use the sub-interface of mode l2 to terminate the dot1q of the downlinks.


  • x
  • convention:

Featured Answers
Popeye_Wang
Admin Created Oct 31, 2019 02:47:34 Helpful(1) Helpful(1)

Hi Hobbit,

In a VXLAN packet, the VXLAN header is encapsulated in the IP header. Therefore, CE1 and CE2 use Layer 3 connection, which is similar to VPLS. The VPLS has a built-in split horizon that can against loop. VXLAN does not support loop preventionmanual intervention is required. To solve the problem, you can try the following steps:

1. The interfaces connecting CE1 and CE2 to CE3 are configured with only BD and VBDF interface addresses. and no VXLAN tunnel is established between CE1 and CE2. In this way, CE3 dual-homing access does not form a closed cycle network, and no loop exists. If the CE1 and CE need to be configured with VRRP, it is recommended that VRRP heartbeat packets be forwarded by the CE3.

2. If a VXLAN tunnel must be established between CE1 and CE2, you can configure M-LAG on CE1 and CE2 so that only one of the upstream dual-homing links of CE3 is activated, and the other is down without forwarding service traffic.

  • x
  • convention:

All Answers
Steelblue
Steelblue Created Oct 31, 2019 02:42:17 Helpful(0) Helpful(0)

The MAC-flapping function of the switch can be used to prevent loops or enable spanning tree.
  • x
  • convention:

Popeye_Wang
Popeye_Wang Admin Created Oct 31, 2019 02:47:34 Helpful(1) Helpful(1)

Hi Hobbit,

In a VXLAN packet, the VXLAN header is encapsulated in the IP header. Therefore, CE1 and CE2 use Layer 3 connection, which is similar to VPLS. The VPLS has a built-in split horizon that can against loop. VXLAN does not support loop preventionmanual intervention is required. To solve the problem, you can try the following steps:

1. The interfaces connecting CE1 and CE2 to CE3 are configured with only BD and VBDF interface addresses. and no VXLAN tunnel is established between CE1 and CE2. In this way, CE3 dual-homing access does not form a closed cycle network, and no loop exists. If the CE1 and CE need to be configured with VRRP, it is recommended that VRRP heartbeat packets be forwarded by the CE3.

2. If a VXLAN tunnel must be established between CE1 and CE2, you can configure M-LAG on CE1 and CE2 so that only one of the upstream dual-homing links of CE3 is activated, and the other is down without forwarding service traffic.

  • x
  • convention:

Comment

Reply
You need to log in to reply to the post Login | Register

Notice Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " Privacy."
If the attachment button is not available, update the Adobe Flash Player to the latest version!
Login and enjoy all the member benefits

Login and enjoy all the member benefits

Login