Users Guide

The NSX controller communicates with an OS10 VTEP using the OVSDB management protocol over a Secure Sockets Layer (SSL)
connection. Establishing the communication between the controller and VTEP involves generating the SSL certicate at a VTEP and
copying the certicate to the NSX controller. After SSL authentication, a secure connection over SSL is established between the controller
and the VTEP. The VTEP then receives and processes the conguration data from the controller.
Controller-provisioned VXLAN: Manual conguration
You must manually congure the underlay network using the OS10 CLI:
• Congure the L3 protocol used for underlay routing. Underlay reachability to VTEP peers is learned using the congured routing
protocol.
• Congure the loopback interface in the default VRF that is used as the VTEP source IP address for controller-based provisioning.
• Assign the VTEP interfaces to be managed by the controller.
Controller-provisioned VXLAN: Automatic provisioning
The controller automatically provisions:
• L2 overlay network
• VXLAN virtual networks, including remote VTEP source addresses
• Local access ports in a virtual network
An OS10 VTEP sends the addition or deletion of server MAC addresses at the VXLAN access port to the NSX controller using the
OVSDB protocol. The controller then propagates the information to VTEP peers. The VTEPs program their forwarding tables
accordingly.
Congure controller-provisioned VXLAN
To congure the NSX controller, follow these steps on each OS10 VTEP:
1 Congure the source interface used for controller-based VXLAN provisioning. Assign an IPv4 address to a loopback interface. Assign
the loopback interface to an NVE instance. The loopback interface must belong to the default VRF. For detailed information, see the
Congure source IP address on VTEP.
906
VXLAN