Setting Up OVSDB on Juniper Networks Devices That Support the Dynamic Configuration of VXLANs

To implement the Open vSwitch Database (OVSDB) management protocol on a Juniper Networks device, you must configure a connection between the Juniper Networks device and a software-defined networking (SDN) controller using the Junos OS CLI.

All SDN controller connections are made on the management interface of the Juniper Networks device. This connection is secured by using the Secure Sockets Layer (SSL) protocol. The default port number for the connection is 6632.

You must also specify that each physical interface that is connected to a physical server is managed by OVSDB. By performing this configuration, you essentially disable the Juniper Networks device from learning about other Juniper Networks devices that function as hardware virtual tunnel endpoints (VTEPs) and the MAC addresses learned by the hardware VTEPs. Instead, this configuration enables OVSDB to learn about these elements.

Before setting up OVSDB on a Juniper Networks device, you must do the following:

Create an SSL private key and certificate, if they do not already exist, and install them in the /var/db/certs directory of the Juniper Networks device. See Creating and Installing an SSL Key and Certificate on a Juniper Networks Device for Connection with SDN Controllers.

To set up OVSDB on a Juniper Networks device:

Specify the IP address of the SDN controller.

Specify SSL as the protocol that secures the connection between the Juniper Networks device and the SDN controller.

Set the number of the port over which the connection to the SDN controller is made.

(Optional) Specify (in milliseconds) how long the connection can be inactive before an inactivity probe is sent.
(Optional) Specify (in milliseconds) how long the device must wait before it can try to connect to the SDN controller again if the previous attempt failed.
(Optional) Repeat Steps 1 through 5 to configure a connection to an additional SDN controller in the NSX environment.
Specify that each physical interface that is connected to a physical server is managed by OVSDB.
When specifying the interface-name, you do not need to include a logical unit number.
Complete the remaining configuration tasks, which are described in OVSDB and VXLAN Configuration Workflows for VMware NSX Environment).