What is VXLAN Pool?
VXLAN Pool: A VXLAN pool is a collection of VXLAN networks established
based on VXLAN Tunnel Endpoints (VTEPs). The VNI of each VXLAN network in a VXLAN
pool must be unique.
- Before you can use a VXLAN network, create a VXLAN pool in advance.
- A VXLAN pool is only a collection of VXLAN networks and cannot be used to create L3 networks.
- VXLAN pool supports two types of SDN: software SDN and hardware SDN.
- Software SDN:
- The VNI range of a software-SDN VXLAN pool can be 1-16777214.
- Hosts in the cluster to which the software-SDN VXLAN pool is
attached must have an IP address as a VXLAN tunnel endpoint
(VTEP) in the specified CIDR.
- Generally, a VTEP corresponds to a NIC IP of a compute
node within a cluster. On the Cloud, you can configure a
VTEP according to its CIDR. For example,
- Assume that the NIC IP of a compute node is 10.12.0.8, the netmask 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 IP of the compute node is 172.20.12.13, the netmask 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 checked without checking physical L2 devices.
- Generally, a VTEP corresponds to a NIC IP of a compute
node within a cluster. On the Cloud, you can configure a
VTEP according to its CIDR. For example,
- Hardware SDN:
- Before you can create a hardware-SDN VXLAN pool, add an SDN controller to the Cloud in advance.
- The VNI range of a hardware-SDN VXLAN pool depends on the distributed vSwitch to which an SDN controller corresponds.
- The host NIC in the cluster to which the hardware-SDN VXLAN pool is attached must connect to a switch managed by the SDN controller.
- If you use VCFC to configure hardware SDN, configure the mapping between VLAN and VXLAN on VCFC in advance.
- Software SDN: