starlingx/docs
Code Issues Proposed changes
docs/doc/source/datanet/openstack/dynamic-vxlan.rst
Ron Stone f125a8b892 Remove spurious escapes (r8,dsR8) 
This change addresses a long-standing issue in rST documentation imported from XML.
That import process added backslash escapes in front of various characters. The three
most common being '(', ')', and '_'.
These instances are removed.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Id43a9337ffcd505ccbdf072d7b29afdb5d2c997e
2023-03-01 11:19:04 +00:00

3.7 KiB
Raw Blame History

Dynamic VXLAN

supports dynamic mode (learning) VXLAN implementation that has each vSwitch instance registered on the network for a particular IP multicast group, addresses, and endpoints that are populated based on neutron configuration data.

The IP multicast group, (for example, 239.1.1.1), is input when a new neutron data network is provisioned. The selection of the IP multicast group constraints flooding to only those nodes that have registered for the specified group. The IP multicast network can work in both a single subnet (that is, local Layer2 environment) or can span Layer3 segments in the customer network for more complex routing requirements but requires IP multicast enabled routers.

starlingx

In the dynamic mode, when a VM instance sends a packet to some destination node the implementation examines the destination MAC address to determine how to treat the packet. If the destination is known, a unicast packet is sent to the compute node hosting that VM instance. If the destination is unknown or the packet is a broadcast/multicast packet then a multicast packet is sent to all compute nodes. Once the destination VM instance receives the packet and responds to the initial source compute node, it learns that the VM is hosted from that compute node, and any future packets destined to that VM instance are unicasted to that compute node.

partner

Multicast Endpoint Distribution

starlingx

For broadcast and multicast packets originating from the VM instances implements head-end replication to clone and send a copy of the packet to each known compute node. This operation is expensive and will negatively impact performance if the network is experiencing high volume of broadcast or multicast packets.

partner

Workflow to Configure Dynamic VXLAN Data Networks

Use the following workflow to create dynamic data networks and add segmentation ranges using the .

  1. Create a VXLAN data network, see Adding Data Networks <adding-data-networks-using-the-cli>.
  2. Add segmentation ranges to dynamic (Multicast ) data networks, see Adding Segmentation Ranges Using the CLI <adding-segmentation-ranges-using-the-cli>.
  3. Configure the endpoint IP addresses of the compute nodes using the or the :

    • To configure static IP addresses for individual data interfaces, see:

      Adding a Static IP Address to a Data Interface <adding-a-static-ip-address-to-a-data-interface>

    • To assign IP addresses from predefined address pools, see:

      Using IP Address Pools for Data Interfaces <using-ip-address-pools-for-data-interfaces>

  4. Establish routes between the hosts, see Adding and Maintaining Routes for a VXLAN Network <adding-and-maintaining-routes-for-a-vxlan-network>.

For more information on the differences between the dynamic and static modes, see Differences Between Dynamic and Static VXLAN Modes <differences-between-dynamic-and-static-vxlan-modes>.