home

Supported platforms

Getting startedOverviewArchitectureSupported platformsRelease notesWhite papers
Getting startedOverviewArchitectureSupported platformsRelease notesWhite papers

Vyatta documentation

Learn how to install, configure, and operate the Vyatta Network Operating System (Vyatta NOS) and Orchestrator, which help drive our virtual networking and physical platforms portfolio.

Show On this page:

thumbnailSupported platforms

Connecting Guests in a Service Chain

Configuring service chaining by using cross-connect

Consider a scenario in which you have two guest VM1 and VM2, as illustrated in the following network diagram. These guest can be any services such as vNAT, vFW, vDPI, and so on.

The following list presents the components of the topology.

  • dp0p0s20f1 and dp0p0s2f0 are the ingress and egress interfaces, respectively, for vCPE or vhost.

  • vhost0 and vhost1 are the virtual interfaces for VM1.
    Note: eth1(vm1) and eth0(vm2) should be in the same subnet because vhost1and vhost2 are associated to the bridge.
  • vhost2 and vhost3 are the virtual interfaces for VM2.
  • dp0vhost0 and dp0p0s20f2 are in cross-connect.
  • dp0vhost1 and dp0vhost2 are in cross-connect.
  • dp0vhost2 and dp0vhost1.
Figure 1. Service chaining by using cross-connect

In the topology, to perform service chaining between VM1 and VM2, the cross-connect is applied between dp0vhost0 and dp0p0s20f1, dp0vhost1 and vhost dp0vhost2, and dp0vhost2 and vhost dp0vhost1. All the packets that are received on dp0p0s20f1 are forwarded to dp0vhost0 and the traffic that is received on dp0vhost1 is forwarded to dp0vhost2.

Table 1. Configuring service chaining by using cross-connect
Steps Commands

Configure cross-connect. 

vyatta@vyatta# set interfaces vhost dp0p0s20f1 xconnect dataplane dp0vhost0
vyatta@vyatta# set interfaces vhost dp0vhost0 xconnect dataplane dp0p0s20f1

vyatta@vyatta# set interfaces vhost dp0vhost1 xconnect vhost dp0vhost2
vyatta@vyatta# set interfaces vhost dp0vhost2 xconnect vhost dp0vhost1

Commit the configuration. 

vyatta@vyatta# commit

Save the configuration. 

vyatta@vyatta# save

Last updated: May 7, 2021