LAN (77) GLUE (78) WAN (1177)
PFE
This example uses the Packet Forwarding Engine’s front panel ports ge-0/2/0 and ge-0/2/1, and its internal-facing ports, sxe-0/0/0 and sxe-0/0/1. The internal NIC’s two ports (sxe0 and sxe1) are not configured directly; instead, they are abstracted at the host OS layer and configured as interfaces hsxe0 and hsxe1. The VMs use two interfaces each (ge-0/0/0 and ge-0/0/1).
These elements are generally separated into two parts: a “LAN side” and a “WAN side”.
As this example uses virtio, Linux bridges in the host OS provide NIC-to-VM and VM-to-VM connectivity. The bridges are not configured directly; instead, VLANs are used. When a VLAN is created, a bridge is automatically setup within the system.
This example is configured using the Juniper Device Manager (JDM) and Junos Control Plane (JCP). The key configuration elements include:
• The Packet Forwarding Engine’s front panel ports.
• The Packet Forwarding Engine’s internal-facing ports.
• A routing instance named host-os. The host-os routing instance is the CLI construct that provides the ability to configure host OS elements from the JDM.
• NIC ports. As these interfaces are not directly configurable, they are abstracted in the host OS. Using the JDM CLI, NIC interfaces (sxe ports) are configured in the host-os routing instance as “hsxe” interfaces.
• The VM interfaces. In the JDM, VNF interfaces must use the format eth#, where # is 2-11.
• VLANs, to provide bridging between the sxe and VM interfaces.
Configuration
This example describes how to configure service chaining using virtio.
• Configuring the Packet Forwarding Engine Interfaces on page 35
Configuring the Packet Forwarding Engine Interfaces CLI Quick
Configuration
To quickly configure the Packet Forwarding Engine interfaces, enter the following configuration statements from the JCP:
[edit]
user@jcp#
set vlans Vlan77 vlan-id 77
set interfaces ge-0/2/0.0 family ethernet-switching vlan member Vlan77 set interfaces sxe-0/0/0.0 family ethernet-switching interface-mode trunk set interfaces sxe-0/0/0.0 family ethernet-switching vlan member Vlan77 set vlans Vlan1177 vlan-id 1177
set interfaces ge-0/2/1.0 family ethernet-switching interface-mode trunk set interfaces ge-0/2/1.0 family ethernet-switching vlan member Vlan1177 set interfaces sxe-0/0/1.0 family ethernet-switching interface-mode trunk set interfaces sxe-0/0/1.0 family ethernet-switching vlan member Vlan1177
Step-by-Step Procedure
To configure the Packet Forwarding Engine interfaces:
1. Connect to the JCP.
user@jdm> ssh vjunos0 user@jcp> configure [edit]
user@jcp#
2. Configure a VLAN for the LAN-side interfaces.
user@jcp# set vlans Vlan77 vlan-id 77
3. Configure the Packet Forwarding Engine’s LAN-side front panel port and add it to the LAN-side VLAN.
The LAN-side port is typically an access port, but could be a trunk port if appropriate.
user@jcp# set interfaces ge-0/2/0.0 family ethernet-switching vlan member Vlan77
4. Configure the Packet Forwarding Engine’s LAN-side internal-facing interface as a trunk port and add it 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.
user@jcp# set interfaces sxe-0/0/0.0 family ethernet-switching interface-mode trunk user@jcp# set interfaces sxe-0/0/0.0 family ethernet-switching vlan member Vlan77
5. Configure a VLAN for the WAN-side interfaces.
user@jcp# set vlans Vlan1177 vlan-id 1177
6. Configure the Packet Forwarding Engine’s WAN-side front panel port as a trunk port and add it to the WAN-side VLAN.
The WAN-side front panel port is typically a trunk port, as it is likely to require the ability to support multiple VLANs.
Chapter 4: Service Chaining
user@jcp# set interfaces ge-0/2/1.0 family ethernet-switching interface-mode trunk user@jcp# set interfaces ge-0/2/1.0 family ethernet-switching vlan member Vlan1177
7. Configure the Packet Forwarding Engine’s WAN-side internal-facing interface as a trunk port and add it to the WAN-side VLAN.
The internal-facing interfaces are typically trunk ports, as they must support traffic from multiple front panel ports and VLANs.
user@jcp# set interfaces sxe-0/0/1.0 family ethernet-switching interface-mode trunk user@jcp# set interfaces sxe-0/0/1.0 family ethernet-switching vlan member Vlan1177
8. Commit the configuration and return to the JDM.
user@jcp# commit and-quit user@jcp> exit
user@jdm>
Results From configuration mode, confirm your configuration by entering the following show commands:
[edit]
Configuring the VNF Interfaces and Creating the Service Chain Step-by-Step
Procedure
Once you have completed the configuration on JCP, you need to:
1. Start the VNFs using the XML descriptor file, which has the virtio interfaces mapped to the corresponding Linux bridges on the Host OS.
2. Bring up the VM1 with one virtio interface on sxe0 Linux Bridge, and another interface on the Glue Bridge created on the Host OS.
3. Similarly bring up VM2 with one interface on sxe1 Linux Bridge, and another interface on the same Glue Bridge as that of VM1.
4. Finally, configure the IP addresses and static routes for each interface of the VMs as shown inFigure 12 on page 34.
Related Documentation
Understanding Service Chaining on Disaggregated Junos OS Platforms on page 31
•
• Disaggregated Junos OS VMs and Containers on page 6
• Understanding Virtio Usage on page 8