+Disable Arp-Nd Suppression:: Optional. Don't suppress ARP or ND packets.
+ This is required if you use floating IPs in your guest VMs
+ (IP are MAC addresses are being moved between systems).
+
+Route-target import:: Optional. Allows you to import a list of external EVPN
+ route targets. Used for cross-DC or different EVPN network interconnects.
+
+MTU:: Because VXLAN encapsulation uses 50 bytes, the MTU needs to be 50 bytes
+ less than the maximal MTU of the outgoing physical interface.
+
+
+[[pvesdn_config_vnet]]
+VNets
+-----
+
+A `VNet` is, in its basic form, a Linux bridge that will be deployed locally on
+the node and used for virtual machine communication.
+
+The VNet configuration properties are:
+
+ID:: An 8 character ID to name and identify a VNet
+
+Alias:: Optional longer name, if the ID isn't enough
+
+Zone:: The associated zone for this VNet
+
+Tag:: The unique VLAN or VXLAN ID
+
+VLAN Aware:: Enable adding an extra VLAN tag in the virtual machine or
+container's vNIC configuration, to allow the guest OS to manage the VLAN's tag.
+
+[[pvesdn_config_subnet]]
+Subnets
+~~~~~~~~
+
+A subnetwork (subnet) allows you to define a specific IP network
+(IPv4 or IPv6). For each VNet, you can define one or more subnets.
+
+A subnet can be used to:
+
+* Restrict the IP addresses you can define on a specific VNet
+* Assign routes/gateways on a VNet in layer 3 zones
+* Enable SNAT on a VNet in layer 3 zones
+* Auto assign IPs on virtual guests (VM or CT) through IPAM plugins
+* DNS registration through DNS plugins
+
+If an IPAM server is associated with the subnet zone, the subnet prefix will be
+automatically registered in the IPAM.
+
+Subnet properties are:
+
+ID:: A CIDR network address, for example 10.0.0.0/8
+
+Gateway:: The IP address of the network's default gateway. On layer 3 zones
+ (Simple/EVPN plugins), it will be deployed on the VNet.
+
+SNAT:: Optional. Enable SNAT for layer 3 zones (Simple/EVPN plugins), for this
+ subnet. The subnet's source IP will be NATted to server's outgoing interface/IP.
+ On EVPN zones, this is only done on EVPN gateway-nodes.
+
+Dnszoneprefix:: Optional. Add a prefix to the domain registration, like
+<hostname>.prefix.<domain>
+
+[[pvesdn_config_controllers]]
+Controllers
+-----------
+
+Some zone types need an external controller to manage the VNet control-plane.
+Currently this is only required for the `bgp-evpn` zone plugin.