Understanding How to Manually Configure OVSDB-Managed VXLANs

 

The Juniper Networks Junos operating system (Junos OS) implementation of the Open vSwitch Database (OVSDB) management protocol provides a means through which VMware NSX controllers and Juniper Networks devices that support OVSDB can communicate.

In a Junos OS environment, the concept of an OVSDB-managed Layer 2 broadcast domain in which data flows are limited to that domain is known as a VXLAN. In an NSX environment, the same concept is known as a logical switch. Understanding the different terminology in turn enables you to better understand the configuration tasks required for setting up OVSDB-managed VXLANs.

The following sections explain what you need to do to configure OVSDB-managed VXLANs properly for each Juniper Networks device that supports OVSDB and VXLAN:

Understanding How to Manually Configure OVSDB-Managed VXLANs On Juniper Networks Devices

For each VXLAN that you plan to implement, you must first configure a logical switch, using NSX Manager or the NSX API. Based on the name and the VXLAN network identifier (VNI) that you specify, NSX automatically generates a universally unique identifier (UUID) for the logical switch. You must retain the UUID of the logical switch for later use.

Next, on the Juniper Networks device, you must manually configure the corresponding VXLAN, including the same VNI specified for the logical switch, using the Junos OS CLI. For the name of the VXLAN, you must specify the UUID for the logical switch.

When configuring a logical switch and a corresponding VXLAN, it is important that the UUID and VNI in both configurations are the same. If these elements are not the same, the logical switch and VXLAN cannot become operational, which means they cannot exchange MAC addresses learned in the NSX and Junos OS environments, respectively.

Table 1 provides a summary of the procedure that you must perform for each OVSDB-managed VXLAN on each Juniper Networks device, where to get more information about the configuration task, and the configuration statements that you must use to configure the VXLAN.

Table 1: Summary of Configuration Tasks for Manually Configuring An OVSDB-Managed VXLAN

Juniper Networks Device That Supports OVSDB and VXLAN

Configure Logical Switch, Using NSX Manager or the NSX API?

Where to Find More Configuration Information

Manually Configure Corresponding VXLAN on Juniper Networks Device?

Junos OS Statement to Configure the OVSDB-Managed VXLAN

Where to Find More Configuration Information

MX Series routers

Yes

See the documentation that accompanies NSX Manager or the NSX API.

Yes

ovsdb-managed statement in the [edit bridge-domains domain-name vxlan] hierarchy.

For the name of the VXLAN, specify the UUID for the logical switch configured in NSX Manager or in the NSX API.

Configuring OVSDB-Managed VXLANs

EX9200 switch

Yes

See the documentation that accompanies NSX Manager or the NSX API.

Yes

ovsdb-managed statement in the [edit vlans vlan-name vxlan] hierarchy.

For the name of the VXLAN, specify the UUID for the logical switch configured in NSX Manager or in the NSX API.

Configuring OVSDB-Managed VXLANs

Related Documentation