VXLAN Pool

A VXLAN Pool is a collection of VXLAN types that encapsulate packets with UDP. It is a large layer 2 network established over an IP network for a large-scale cloud computing center.
  • To use a VXLAN network, create a VXLAN Pool first.
  • A VXLAN Pool cannot be used to create an L3 network, and is only a collection of VXLAN networks.
  • A VXLAN Pool supports two types of SDN: software SDN and hardware SDN.
    • Software SDN:
      • The VNI range of a software SDN VXLAN Pool supports 1-16777214.
      • The CIDR IP address of a host that is attached to a cluster can serve as a VTEP (VXLAN tunnel endpoint).
        • Generally, a VTEP corresponds to an NIC IP address of a compute node within a cluster. On the Cloud, you can configure a VTEP according to its corresponding CIDR. For example,
          • Assume that the NIC IP address of a compute node is 10.12.0.8, the subnet mask is 255.0.0.0, and the gateway is 10.0.0.1. Then, the CIDR of the VTEP is 10.0.0.1/8.
          • Assume that the NIC of the compute node is 172.20.12.13, the subnet mask is 255.255.0.0, and the gateway is 172.20.0.1. Then, the CIDR of the VTEP is 172.20.0.1/16.
        • When a VXLAN Pool is attached to a cluster, the IP address that is associated to the VTEP will be looked up without checking physical L2 devices.
    • Hardware SDN:
      • An SDN controller needs to be added to the Cloud in advance.
      • The VNI range of a hardware SDN VXLAN Pool depends on a virtually distributed switch to which an SDN controller corresponds.
      • The NIC of a host that is attached to a cluster must connect to a switch managed by the SDN controller.
      • If you use VCFC to configure hardware SDN, verify that you configure the mapping between VLAN and VXLAN on VCFC in advance.

Create VXLAN Pool

In the navigation pane of the ZStack Private Cloud, choose Network Resource > L2 Network Resource > VXLAN Pool. On the VXLAN Pool page, click Create VXLAN Pool. On the displayed Create VXLAN Pool page, set the following parameters:
  • Name: Enter a name for the VXLAN Pool.
  • Description: Optional. Enter a description for the VXLAN Pool.
  • Type: Select a type for the VXLAN Pool, including software SDN and hardware SDN.
    • If you select the software SDN type, set the following parameters:
      • Start Vni: Enter a start ID for the VxlanNetwork. The start ID supports 1-16777214.
      • End Vni: Enter an end ID for the VxlanNetwork. The end ID supports 1-16777214, which must be larger than or equal to the Start VNI.
        Note: The Cloud will reserve the last two VNIs (16777215 and 16777216) for the system.
      • Cluster: Optional. Select the cluster to be attached.
        Note:
        • When you create a VXLAN Pool, you can attach it to a cluster. Or, you can attach it to the cluster after you create the VXLAN Pool.
        • When you attach the cluster, the compute node in the cluster must have a subnet IP address that is associated to the VTEP.
      • VTEP CIDR: Enter the CIDR to which the VTEP corresponds.
      You can create a VXLAN Pool with the software SDN type, as shown in Create Software SDN VXLAN Pool.
      Figure 1. Create Software SDN VXLAN Pool


    • If you select the hardware SDN type, set the following parameters:
      • SDN Controller: Add an SDN controller to the Cloud in advance.
      • Start Vni: Enter a start ID for the HardwareVxlanNetwork.
      • End Vni: Enter an end ID for the HardwareVxlanNetwork. This end ID must be larger or equal to the Start VNI.
        Note: The VNI range of a hardware SDN VXLAN Pool depends on a virtually distributed switch to which an SDN controller corresponds.
      • Cluster: Optional. Select a cluster to be attached.
        Note: When you create a VXLAN Pool, you can attach it to a cluster. Or, you can attach it to the cluster after you create the VXLAN Pool.
      • NIC: Enter an NIC for the host.
        Note: The NIC of a host that is attached to a cluster must connect to a switch managed by an SDN controller.
      You can create a VXLAN Pool with the hardware SDN type, as shown in Create Hardware SDN VXLAN Pool.
      Figure 2. Create Hardware SDN VXLAN Pool


You can create a VXLAN Pool with the software SDN type, as shown in Create VXLAN Pool.
Figure 3. Create VXLAN Pool


VXLAN Pool Operations

You can perform the following operations on a VXLAN Pool:
  • Change name: Change the name of the VXLAN Pool.
  • Change description: Change the description of the VXLAN Pool.
  • Attach cluster: Attach the VXLAN Pool to a cluster.
    • Software SDN VXLAN Pool: Specify a CIDR to which a VTEP corresponds. Make sure that the CIDR of each host in the cluster has the corresponding IP address. Or otherwise, you will fail to attach the VXLAN Pool to the cluster.
    • Hardware SDN VXLAN Pool: The NIC of a host that is attached to a cluster must connect to a switch managed by an SDN controller.
  • Detach cluster: Detach a cluster from the VXLAN Pool.
  • Delete: Delete the VXLAN Pool. If you delete the VXLAN Pool, its corresponding subresource VXLAN networks, associated L3 network, and VM NICs will be deleted as well.
  • Share: Share the VXLAN Pool to the specified regular account.
  • Recall: Recall the VXLAN Pool from the regular account. You can make this account invisible.
  • Share to all: Share the VXLAN Pool to all regular accounts.
  • Recall from all: Recall the VXLAN Pool from all regular accounts. You can make these accounts invisible.
  • Create VNI range: Create a VNI range to the VXLAN Pool.
  • Delete VNI range: Delete a VNI range from the VXLAN Pool.
  • Change VNI range name: Change the VNI range name of the current VXLAN Pool. Only a single operation is supported.
    Note:
    • Changing a VNI range name supports up to 255 characters. You can use special characters as needed.
    • Under one VXALN Pool, different VNI ranges can use the same VNI range name.
  • Create VXLAN network: Create a VXLAN network according to a VXLAN Pool. Each VXLAN network corresponds to a VNI in a VXLAN Pool.
  • Delete VXLAN network: Delete the VXLAN network. If you delete the VXLAN network, its corresponding subresource L3 network and VM NICs of the L3 network will be deleted as well.
  • Audit: Check the related operations of the VXLAN Pool.