Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Example: Configuring Service Chaining Using a Custom Bridge on NFX250 NextGen Devices

This example shows how to configure service chaining using a custom bridge.

Requirements

This example uses an NFX250 NextGen device running Junos OS Release 19.1R1.

Overview

The default system bridge is Open vSwitch (OVS). The OVS bridge is a VLAN-aware system bridge, which acts as the Network Functions Virtualization (NFV) backplane to which the VNFs and FPCs connect. However, you can choose to create a custom bridge based on your requirement. This example explains how to configure service chaining using a custom bridge.

Topology

This example uses the topology shown in Figure 1.

Figure 1: Service Chaining Using a Custom BridgeService Chaining Using a Custom Bridge

Configuration

Configuring VLANs and Creating the Custom Bridge

Step-by-Step Procedure

  1. Configure VLANs for the LAN-side interfaces:

  2. Create a custom bridge:

  3. Map the Layer 3 interface to the custom bridge:

Configuring the Layer 2 Datapath

Step-by-Step Procedure

  1. Configure the LAN-side front panel ports and add them to the LAN-side VLAN.

  2. Configure the internal-facing interfaces as trunk ports and add them to the LAN-side VLAN. The internal-facing interfaces are typically trunk ports as they must support traffic from multiple front panel ports and VLANs.

Configuring the Layer 3 Datapath

Step-by-Step Procedure

  1. Configure VLAN tagging on ge-1/0/0:

  2. Configure VLAN tagging on ge-1/0/2:

Configuring the VNF

Step-by-Step Procedure

Note:

This example uses a Layer 2 VNF.

  1. Launch the VNF:

  2. Specify the number of CPUs required for the VNF:

  3. Pin a virtual CPU to a physical CPU:

  4. Configure the vmhost instance:

  5. Create a VNF interface on the custom OVS bridge:

  6. Create a VNF interface on the OVS bridge:

  7. Specify the memory allocation for the VNF:

    Note:

    When a VNF interface is mapped to a custom bridge, you should restart the VNF for the mapping to take effect.

Verifying the Configuration

Verify the Control Plane Configuration

Purpose

Verify the control plane configuration:

Action

  • Verify that the VLANs are configured:

  • Verify the vmhost VLANs:

  • Verify that the VNF is operational. The State field shows Running for VNFs that are up.

    The Liveliness field of the VNF indicates whether the internal management IP address of the VNF is reachable from the Junos Control Plane (JCP).

    To view more details of the VNF:

Verifying the Data Plane Configuration

Purpose

Verify the data plane configuration.

Action

  • Verify the status of the Layer 2 (ge-0/0/x) and Layer 3 (ge-1/0/x) interfaces.

    For example:

  • Verify the status of the interfaces on the OVS and the custom bridge: