Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


VNFs Supported by the Contrail Service Orchestration Solutions


Contrail Service Orchestration (CSO) supports Juniper Networks and third-party VNFs listed in Table 1.

Table 1: VNFs Supported by Contrail Service Orchestration

VNF Name


Network Functions Supported

Deployment Model Support

Element Management System Support

Juniper Networks vSRX

vSRX KVM Appliance 15.1X49-D123

  • Network Address Translation (NAT)

  • Demonstration version of Deep Packet Inspection (DPI)

  • Firewall

  • Unified threat management (UTM)

  • Centralized deployment

  • Hybrid WAN and SD-WAN deployments supports NAT, firewall, and UTM.

Element Management System (EMS) microservice, which is included with CSO

LxCIPtable (a free, third party VNF based on Linux IP tables


  • NAT

  • Firewall

Centralized deployment

EMS microservice

Cisco Cloud Services Router 1000V Series (CSR-1000V)



Centralized deployment

Junos Space Network Management Platform

Riverbed SteelHead


WAN optimization

Hybrid WAN deployment–NFX250 and NFX150 platforms.

EMS microservice




Hybrid WAN and SD-WAN deployments–NFX250 and NFX150 platforms.

EMS microservice

Single-legged Ubuntu



Hybrid WAN and SD-WAN deployments–NFX250 and NFX150 platforms.

EMS microservice

Immediately after installation, CSO does not contain any VNFs. You have to upload the VNFs to the CSO platform through the Administration Portal or through API calls.

You can use these VNFs in service chains and configure some settings for them in Network Service Designer. You can then view those network service configuration settings in the Administration Portal. Customers can also configure some settings for the VNFs in their network services through Customer Portal. VNF configuration settings that customers specify in the Customer Portal override VNF configuration settings specified in Network Service Designer.


Currently, SD-WAN deployments support only layer 2 (L2) service chains while Hybrid WAN deployments can support L2 and L3 service chains.