This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Enterprise
Community Forums Switches
VXLAN Centralized Gateway...

VXLAN Centralized Gateway Deployment

Latest reply: Oct 29, 2018 09:07:28 931 15 9 0
display all floors #1

 

1.The leaf and spine nodes set up full-mesh connections. At least two spine nodes need to be deployed on the network, which back up each other and implement load balancing. Forwarding paths are established between leaf nodes through Layer 3 routing. Normally, ECMP paths exist between leaf nodes.

2.The spine and leaf nodes all function as VTEPs.

3.A leaf node only completes Layer 2 traffic forwarding. It maps the VLAN tag of user packets to a VNI, encapsulates the packets in VXLAN packets, and forwards them to the destination node in the local bridge domain.

4.A spine node acts as a centralized Layer 3 gateway to decapsulate VXLAN packets and forward them based on Layer 3 routes, enabling communication between bridge domains on the network and communication with external networks.

BGP EVPN acts as the VXLAN control plane to provide the following functions:

 

 

packet format

n  DA: specifies the destination MAC address of the outer packet. The value is the MAC address of the next-hop router in unicast forwarding, and is a multicast MAC address in multicast replication.

n  SA: specifies the source MAC address of the outer packet. The value is the MAC address of each routing device that sends the VXLAN packet.

n  DIP: specifies the IP address of the destination NVE.

n  SIP: specifies the IP address of the source NVE.

n  UDP Dest Port: specifies the destination UDP port number reserved for VXLAN. The default value is 4789.

n  UDP Source Port: The value is dynamically generated based on the hash result of data flows.

n  VXLAN I flag: The value must be set to 1, indicating that the VNI field is valid.

n  VXLAN VNI: is a 24-bit value that identifies virtual networks. The maximum value is 16M.

n  Original Ethernet Frame: As recommended in the standard, the VLAN tag of the original packet is removed after VXLAN encapsulation. Even if the VLAN tag is not removed, the egress NVE forwards the packet based on only the VNI (the VLAN of the original packet is ignored).

 

  • x
  • convention：

Helpful (9) Favorite(0) Share Report
yjhd
Created Oct 27, 2018 06:39:00 Helpful(1) Helpful(1)

very helpful:
UDP Source Port: The value is dynamically generated based on the hash result of data flows.
VXLAN I flag: The value must be set to 1, indicating that the VNI field is valid.
n VXLAN VNI: is a 24-bit value that identifies virtual networks. The maximum value is 16M.
n Original Ethernet Frame: As recommended in the standard, the VLAN tag of the original packet is removed after VXLAN encapsulation. Even if the VLAN tag is not removed, the egress NVE forwards the packet based on only the VNI (the VLAN of the original packet is ignored).
  • x
  • convention：
Torrent
Created Oct 27, 2018 06:42:19 Helpful(0) Helpful(0)

The active-dull-client enable command enables the function of preventing terminals from entering energy-saving mode.

The undo active-dull-client enable command disables the function.

By default, the function of preventing terminals from entering energy-saving mode is disabled.

This post was last edited by Torrent at 2018-10-31 06:28.
  • x
  • convention：
littlestone
Created Oct 27, 2018 06:45:00 Helpful(0) Helpful(0)

After switches are connected using stack links and set up a stack, they form a stack domain. Multiple stacks can be deployed on a network to support various applications. These stacks are identified by their domain IDs.

 

 Stack member ID

 

Stack member IDs are used to identify and manage member switches in a stack. Each member switch in a stack has a unique member ID. This post was last edited by littlestone at 2018-10-31 05:43.
  • x
  • convention：
SupperRobin
Created Oct 27, 2018 06:50:18 Helpful(0) Helpful(0)

Thanks for you share about this which is very useful for my daily work.
And now i can easy to check the ISSUE if i face any issue about this.before this i aways do not know how to deal with them,and wasted a lot of time to serch this.Thanks agin for you selfless Sharing, Hope you can aways work like this.:):):)
  • x
  • convention：
wanglei259
Created Oct 27, 2018 07:33:13 Helpful(0) Helpful(0)

Thanks for your sharing ,which is a wonderful guidance, i really interested in this article, which is useful for us and improvement product technology and become to a professional engineer .
I hope that you can insist post new kownlege and skills, i will alawys keep an eye on your sharing.
  • x
  • convention：
Our kingdom is young,our stories are not yet legends.
Finn92
Created Oct 27, 2018 07:41:22 Helpful(0) Helpful(0)

if you can share more information about the development in detail ,that's great .

I am very interested for this sharing , which is very helpful to our daily work. I have the similar problems in my daily troubleshooting, but I do not know how to deal with them. Now I have a clear idea. Thank you very much for your post. Hope you can update continue like this , thank you very much .

This post was last edited by Finn92 at 2018-10-31 09:04.
  • x
  • convention：
SupperRobin
Created Oct 27, 2018 07:41:47 Helpful(0) Helpful(0)

In an all-active gateway scenario where the overlay network is an IPv6 network, multiple gateways advertise routes of the same subnet to the upper-layer routing device so that the upper-layer routing device has equal-cost routes to the specified network segment. Traffic from the upper-layer routing device is sent to a gateway through an equal-cost route. If there is no ND entry of the destination host on the gateway, ND packets are flooded and traffic is discarded.
To ensure correct traffic forwarding, all-active gateways must synchronize ND entries. That is, when any host in the subnet where a gateway is deployed goes online, all gateways learn the ND entry of the host. The working mechanism is as follows:

This post was last edited by SupperRobin at 2018-10-31 06:21.
  • x
  • convention：
No.9527
Created Oct 27, 2018 08:08:59 Helpful(0) Helpful(0)

In centralized VXLAN gateway deployment in static mode, the control plane is responsible for VXLAN tunnel establishment and dynamic MAC address learning; the forwarding plane is responsible for intra-subnet known unicast packet forwarding, intra-subnet BUM (Broadcast&Unknown-unicast&Multicast) packet forwarding, and inter-subnet packet forwarding.

Deploying centralized VXLAN gateways in static mode involves heavy workload and is inflexible, and therefore is inapplicable to large-scale networks. As such, deploying centralized VXLAN gateways using BGP EVPN is recommended.

This post was last edited by No.9527 at 2018-10-31 03:32.
  • x
  • convention：
faysalji
Created Oct 27, 2018 17:27:06 Helpful(0) Helpful(0)

Hey thanks for sharing
  • x
  • convention：
If you think my post/reply is useful, please click the Helpful button and flag my post as a BEST ANSWER. Thanks
12
Back to list

Comment

Reply
Advanced
B Color Image Link Quote Code Smilies
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
Huawei Website Support About Huawei Privacy Terms of Use
Huawei Enterprise Huawei Carrier Forum Training & Certification

Copyright © 2019 Huawei Technologies Co., Ltd. All rights reserved.

APP