Contrail Configuration for Juniper Networks Devices That Function as Hardware VTEPs

When extending a Contrail topology to include physical servers that are connected to a Juniper Networks switch that supports the Open vSwitch Database (OVSDB) management protocol and Virtual Extensible LANs (VXLANs), you must perform the following tasks in the Contrail Web user interface:

For each OVSDB-managed VXLAN that you plan to implement on the Juniper Networks switch, configure an equivalent virtual network. Also configure a logical interface to associate with the virtual network.
Configure a physical router, which enables the Contrail controller to recognize the Juniper Networks device as a hardware virtual tunnel endpoint (VTEP).

This topic provides a high-level summary of the tasks that you must perform to configure a virtual network, logical interface, and physical router. Although you can create these virtual entities in either the Contrail Web user interface or in the Contrail REST API, this topic only describes how to perform the tasks in the Contrail Web user interface. Also, this topic does not include a complete procedure for each task. Rather, it includes key configuration details for ensuring the correct configuration of the virtual entities so that they function properly with their counterparts in the physical network.

For more information about performing the tasks described in this topic, see Creating a Virtual Network and Using TOR Switches and OVSDB to Extend the Contrail Cluster to Other Instances.

This topic describes the following tasks:

Creating a Virtual Network

For each OVSDB-managed VXLAN that you plan to implement on a Juniper Networks switch, configure an equivalent virtual network in the Contrail Web user interface.

Table 1 provides key configuration details to keep in mind when you configure a virtual network.

Table 1: Key Configuration Details for Creating a Virtual Network in the Contrail Web User Interface
Contrail Web User Interface Navigation	Configuration Field	Configuration Details
Configure > Networking > Networks	VXLAN Identifier in Advanced Options	In the Contrail Web user interface, you can configure a VXLAN identifier mode so that VXLAN identifiers are either automatically configured or user configured. We recommend setting this mode to user configured, which enables you to initially configure a VXLAN identifier and modify it later if needed. In a Junos OS environment, a VXLAN identifier is also known as a `VXLAN network identifier (VNI)`.

Creating a Logical Interface

In the Contrail Web user interface, you must create a logical interface for each virtual network that you created.

Before you start this task, you must complete the configurations of the following entities:

The OVSDB-managed physical interfaces on the Juniper Networks device. For information about configuring OVSDB-managed interfaces on Juniper Networks devices that support the dynamic configuration of VXLANs, see Setting Up OVSDB on Juniper Networks Devices That Support the Dynamic Configuration of VXLANs.
The virtual network with which you want to associate the logical interface.

Table 2 provides a summary of key configuration details to keep in mind when you configure a logical interface.

Table 2: Key Configuration Details for Creating a Logical Interface in the Contrail Web User Interface
Contrail Web User Interface Navigation	Configuration Field	Configuration Details
Configure > Physical Devices > Interfaces	Type	Select `Logical`.
	Name	When you specify a logical interface name, use the same naming convention for configuring a logical interface in the Junos OS CLI. A sample logical interface name is ge-1/0/0.10.
	Parent	Select an OVSDB-managed physical interface that is configured on the Juniper Networks device.
	Logical Interface Type	Select `L2 Server`.
	VLAN ID	If you want the logical interface to handle untagged packets, specify `0`. If you want the logical interface to handle tagged packets, specify `3` through `4000`. Note: VLAN IDs 1, 2, and 4094 are reserved. As a result, you must not specify these VLAN IDs.
	Virtual Network	Select the virtual network with which you want to associate the logical interface.

Creating a Physical Router

In the Contrail Web user interface, you must create a physical router, which enables the Contrail controller to recognize a Juniper Networks switch as a hardware VTEP.

Before you start this task, you must complete the following configurations:

On the Juniper Networks switch, configure a hostname for the switch (set system host-name hostname), an IP address for the management interface (set interfaces management-interface-name unit 0 family inet address ip-address/destination prefix), and an IP address for the loopback interface (set interfaces lo0 unit 0 family inet address ip-address/destination prefix). Also, set the loopback interface as the interface that identifies the switch as the hardware VTEP (set vtep-source interface lo0.0).
Configure one or more virtual networks with which you want to associate the Juniper Networks switch.

Table 3 provides a summary of key configuration details to keep in mind when you configure a physical router.

Table 3: Key Configuration Details for Creating a Physical Router in the Contrail Web User Interface
Contrail Web User Interface Navigation	Configuration Field	Configuration Details
Configure > Physical Devices > Physical Routers	Name	Specify the hostname that you configured on the Juniper Network switch.
	Management IP	Specify the IP address of the management interface on the Juniper Networks switch. The connection with the Contrail controller is made over this interface.
	VTEP address	Specify the IP address of the loopback interface on the Juniper Networks switch.
	Virtual Network	Specify one or more virtual networks that serve as counterparts to the OVSDB-managed VXLANs that the Juniper Networks switch automatically configures.

ON THIS PAGE

Contrail Configuration for Juniper Networks Devices That Function as Hardware VTEPs

Creating a Virtual Network

Creating a Logical Interface

Creating a Physical Router