Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 

Related Documentation

    Features Supported in This Release

    • Support for 3 deployment models—You can use one Contrail Service Orchestration installation to manage the following deployments:
      • A centralized deployment only
      • A distributed deployment only
      • A centralized and a distributed deployment.

        In this case you cannot share POPs or network services between the centralized and distributed deployment. You must create separate POPs and network services for the centralized deployment and for the distributed deployment. You can use the same tenant with one POP in a distributed deployment and another POP in a centralized deployment.

    • Support for Contrail Service Orchestration high availability—You can now install Contrail Service Orchestration with high availability for infrastructure services and microservices in a production environment. If an infrastructure service or mixroservice fails, current operations for that service are not recovered; however, any new operations proceed as normal.
    • Support for use of SRX Series Services Gateway as a CPE device at a customer site—You can now use the following platforms as CPE devices for a distributed deployment:
      • SRX300 Series Services Gateway
      • SRX320 Series Services Gateway
      • SRX340 Series Services Gateway
      • SRX345 Series Services Gateway

      You add each SRX Series Services Gateway as a device to your Contrail Service Orchestration deployment and configure the tenant, site, and service in Administration Portal or the API.

      Customers at sites that use SRX Series Services Gateways must add the SRX Series Services Gateway configuration to Contrail Service Orchestration manually. To do so, the administrative user logs into the console of the device, copies the configuration from Customer Portal or the API, pastes it into the device console, and commits the configuration. The administrative user then activates the device from Customer Portal. Authentication of an SRX CPE device takes place through SSH.

    • Support for use of vSRX on an x86 server as a CPE device—You can now deliver vSRX network services using vSRX on an x86 server as a CPE device. The device can be located at a customer site or in the service provider cloud. In both cases, you configure the site in Contrail Service Orchestration as a on-premise site. Your customers must configure and activate vSRX CPE devices as they would SRX Series Services Gateways.
    • Support for advanced policy-based routing and associated monitoring—You can now configure advanced policy-based routing (ABPR) on the Internet links for a CPE device to classify outgoing traffic based on routing applications. APBR allows you to define flexible traffic-handling capabilities that offer granular control for forwarding packets based on application attributes. All CPE devices—NFX250 devices, SRX Series Services Gateways and vSRX instances—support this functionality.

      APBR involves classifying a session based on applications and applying the configured rules to reroute the traffic. In order to classify the applications, a deep packet inspection (DPI) engine is used. The DPI engine inspects the content of a traffic session to identify the application. The result of identification is cached in application system cache (ASC). For subsequent sessions, an ASC lookup determines the route of the packet according to a matching rule.

      You can also use IP monitoring on the WAN links to track the performance of APBR.

    • Support for Riverbed Steelhead VNF on NFX250 devices—You can now use the Riverbed Steelhead application as a VNF for WAN optimization on an NFX250 device.
    • Support for configuration of third-party devices—You can now specify custom parameters and corresponding values in Contrail Service Orchestration for a third-party device such as a PE router in a distributed deployment or an SDN gateway in a centralized deployment. You can use the custom properties for various purposes, such as logging and accounting. You specify the custom properties for a tenant or site through Administration Portal or the API. When Network Service Orchestrator activates a network service for the tenant or site, the customer properties are configured on the device.

    • Dedicated OpenStack Keystone for Contrail Service Orchestration in a centralized deployment—You can now configure a dedicated OpenStack Keystone for Contrail Service Orchestration in a centralized deployment. In previous releases, you used the Contrail OpenStack Keystone to authenticate Contrail Service Orchestration operations in a centralized deployment. This feature provides enhanced security for the service provider network because customers and Cloud CPE infrastructure components use separate OpenStack Keystone tokens.

      When you use this feature, you configure each VIM to include service profiles that specify settings to access to the infrastructure components. You also associate the service profile and VIM with each customer. If you configure a dedicated OpenStack Keystone for Contrail Service Orchestration, the login credentials are stored in the file /etc/keystone/keystone on the primary Contrail Service Orchestration server.

    • Management of licenses for physical and virtual devices—You can now use Contrail Service Orchestration to install and track licenses on physical and virtual devices that it manages. You can upload a license to Contrail Service Orchestration with Administration Portal or API calls. You can then use API calls to install the license on a device and to verify that the licenses are successfully installed. In addition, we provide an license installation tool to automate the process for using API calls to upload and install licenses to one device, a specific range of devices, or multiple devices. You can also use the tool to retrieve a license for a site or device.
    • Updates to Administration Portal—Administration Portal offers several new features:
      • Support for configuration of custom parameters and corresponding values on a third-party PE router that connects to CPE devices at customer sites.

        You configure these settings as custom properties for a tenant site.

      • Device profiles for SRX Series Services Gateways and vSRX implementations used as CPE devices.
      • Support for configuration of authorization and authentication of tenant administrators through a dedicated OpenStack Keystone deployment.
      • Support for uploading of VNF license files to Contrail Service Orchestration.
    • Updates to Customer Portal—Customer Portal offers several new features:
      • Enhancements to the startup wizard to simplify activation of sites that host CPE devices.
      • Enhancements to improve the management of CPE devices and their associated network services.
      • Support for use of SRX Series Services Gateways and vSRX as CPE devices.
        • Support for application based routing and associated monitoring for vSRX VNFs on CPE devices
        • Configuration of service polices for SRX Series Services Gateways.

    Node Servers and Servers Tested in the Cloud CPE Solution

    The Cloud CPE solution users commercial off-the-shelf (COTS) node servers or servers for both the centralized and distributed deployments for the following functions:

    • Contrail Service Orchestration central and regional servers
    • Contrail Analytics servers
    • Contrail Cloud Platform in the centralized deployment

    Table 2 lists the node servers and servers that have been tested for these functions in the Cloud CPE solution. You should use these specific node servers or servers for the Cloud CPE solution.

    Table 2: COTS Node Servers and Servers Tested in the Cloud CPE Solution

    Option

    Vendor

    Model

    Type

    1

    QuantaPlex

    T41S-2U 4-Node server

    Multinode server accepting 4 nodes

    2

    Supermicro

    SuperServer Model SYS-2028TPHC1TR-OTO-4

    Multinode server accepting 4 nodes

    3

    Dell

    PowerEdge R420 rack server

    1U rack-mounted server

    Software Tested for COTS Servers

    Table 3 shows the software that has been tested for the Cloud CPE solution. You must use these specific versions of the software when you implement the Cloud CPE solution.

    Table 3: Software Tested for the COTS Nodes and Servers

    Description

    Version

    Operating system for Contrail Cloud Platform nodes and servers

    Each of the following operating system has been tested:

    • Ubuntu 14.04 LTS
    • Ubuntu 14.04.1 LTS
    • Ubuntu 14.04.2 LTS

    Operating system for Contrail Service Orchestration servers and their VMs

    Ubuntu 14.04.2 LTS for Contrail Analytics host in a distributed deployment

    Ubuntu 14.04.5 LTS for all other servers and VMs

    Hypervisor on Contrail Service Orchestration servers

    • Centralized deployment: Contrail Release 3.0.2 with OpenStack (Liberty or Kilo), or VMware ESXi Version 5.5.0
    • Distributed deployment: KVM provided by the Ubuntu operating system on the server or VMware ESXi Version 5.5.0

    Additional software for Contrail Service Orchestration servers

    Secure File Transfer Protocol (SFTP)

    • Software defined networking (SDN) for a centralized deployment
    • Contrail Analytics

    Contrail Release 3.0.2 with OpenStack (Liberty or Kilo)

    Network Devices and Software Tested for the Contrail Cloud Platform (Centralized Deployment)

    The Contrail Cloud Platform has been tested with:

    • The network devices described in Table 4.
    • The software described in Table 5.

      You must use these specific versions of the software for the Cloud CPE Solution 2.1..

    Table 4: Network Devices Tested for the Contrail Cloud Platform

    Function

    Device

    Model

    Quantity

    SDN gateway router

    Juniper Networks MX Series 3D Universal Edge Router

    MX80-48T router with
    two 10 Gigabit Ethernet (GE) XFP optics

    1

    Management switch

    Juniper Networks EX Series Ethernet Switch

    EX3300-48T switch with:

    • 48 10/100/1000 GE interfaces
    • 4 built-in 10 GE SFP transceiver interfaces

    1

    Data switch

    Juniper Networks QFX Series Switch

    QFX 5100-48S-AFI switch with:

    • 48 SFP+ transceiver interfaces
    • 6 QSFP+ transceiver interfaces

    1

    Table 5: Software Tested in the Cloud CPE Centralized Deployment

    Function

    Software and Version

    Operating system for MX Series router

    Junos OS Release 14.2R3

    Operating system for EX Series switch

    Junos OS Release 12.3R10

    Operating system for QFX Series switch

    Junos OS Release 13.2X51-D38

    Hypervisor on Contrail Service Orchestration servers

    Contrail Release 3.0.2 with OpenStack (Liberty or Kilo), or VMware ESXi Version 5.5.0

    Element management system software

    EMS microservice

    Junos Space Network Management Platform Release 15.1R1 (for VNFs that require this product)

    • Software defined networking (SDN) for a centralized deployment
    • Contrail Analytics

    Contrail Release 3.0.2 with OpenStack (Liberty or Kilo)

    Virtualized infrastructure manager (VIM) and virtual machine (VM) orchestration

    OpenStack Liberty or Kilo

    Authentication and Authorization

    OpenStack Liberty or Kilo

    Network Functions Virtualization (NFV)

    Contrail Service Orchestration Release 2.1

    Network Devices and Software Tested for Use with CPE Devices (Distributed Deployment)

    The distributed deployment has been tested with:

    • The network devices described in Table 6.
    • The software described in Table 7.

      You must use these specific versions of the software when you implement the distributed deployment.

    Table 6: Network Devices Tested for the Distributed Deployment

    Function

    Device

    Model

    Quantity

    PE router and IPsec concentrator

    Juniper Networks MX Series 3D Universal Edge Router

    MX960 router with
    MS-MPC line card

    1 per POP

    SDN gateway for SD-WAN Edge

    Juniper Networks SRX Series Services Gateway

    SRX4200 Services Gateway

    1 per POP

    CPE device

    • NFX250 Series Network Services Platform
    • SRX Series Services Gateway
    • vSRX on an x86 server

    • NFX250-S1 device
    • NFX250-S2 device
    • SRX300 Services Gateway
    • SRX320 Services Gateway
    • SRX340 Services Gateway
    • SRX345 Services Gateway
    • vSRX 15.1X49D61

    1 per customer site

    Table 7: Software Tested in the Distributed Deployment

    Function

    Software and Version

    Hypervisor on Contrail Service Orchestration servers

    KVM provided by the Ubuntu operating system on the server or VMware ESXi Version 5.5.0

    Authentication and Authorization

    OpenStack Liberty or Kilo

    Network Functions Virtualization (NFV)

    Contrail Service Orchestration Release 2.1

    Contrail Analytics

    Contrail Release 3.0.2 with OpenStack (Liberty or Kilo)

    NFX Software

    Junos Configuration Release 15.1X53-D102

    Routing and Security for NFX250 device

    vSRX KVM Appliance MD5 SHA1 15.1X49-D61

    Operating system for vSRX used as a CPE device on an x86 server

    vSRX KVM Appliance MD5 SHA1 15.1X49-D61

    Operating system for SRX Series Services Gateway used as a CPE device

    15.1X49-D60

    Operating system for MX Series router used as PE router

    16.1R3.00

    Operating system for SRX Series Services Gateway used as an SDN WAN gateway

    15.1X49D65

    Minimum Hardware Requirements for the Cloud CPE Solution

    Table 2 lists the makes and models of node servers and servers that you can use in the Cloud CPE solution. When you obtain node servers and servers for the Cloud CPE Solution, we recommend that you:

    • Select hardware that was manufactured within the last year.
    • Ensure that you have active support contracts for servers so that you can upgrade to the latest firmware and BIOS versions.

    The number of node servers and servers that you require depends on whether you are installing a demo or a production environment.

    Table 8 shows the required hardware specifications for node servers and servers in a demo environment.

    Table 8: Demo Environment

    Function

    Option 1

    Option 2

    Option 3

    Node or Server Specification

    Storage

    Greater than 1 TB of one of the following types:

    • Serial Advanced Technology Attachment (SATA)
    • Serial Attached SCSI (SAS)
    • Solid-state drive (SSD)

    Greater than 1 TB of one of the following types:

    • SATA
    • SAS
    • SSD

    Greater than 1 TB of one of the following types:

    • SATA
    • SAS
    • SSD

    CPU

    One 64-bit dual processor, type Intel Sandybridge, such as Intel Xeon E5-2670v3 @ 2.5 Ghz or higher specification

    One 64-bit dual processor, type Intel Sandybridge, such as Intel Xeon E5-2670v3 @ 2.5 Ghz or higher specification

    One 64-bit dual processor, type Intel Sandybridge, such as Intel Xeon E5-2670v3 @ 2.5 Ghz or higher specification

    Network interface

    One Gigabit Ethernet (GE) or 10 GE interface

    One GE or 10 GE interface

    One GE or 10 GE interface

    Contrail Service Orchestration Servers (includes Contrail Analytics in a VM )

    Number of nodes or servers

    6

    3

    1

    vCPUs

    4

    8

    24

    RAM

    16 GB

    32 GB

    96 GB

    Contrail Cloud Platform for a Centralized Deployment

    Number of nodes or servers

    1

    1

    1

    vCPUs

    16

    16

    16

    RAM

    64 GB

    64 GB

    64 GB

    Table 9 shows the required hardware specifications for node servers and servers in a production environment.

    Table 9: Production Environment

    Server Function

    Values

    Node or Server Specification

    Storage

    Greater than 1 TB of one of the following types:

    • SATA
    • SAS
    • SSD

    CPU

    One 64-bit dual processor, type Intel Sandybridge, such as Intel Xeon E5-2670v3 @ 2.5 Ghz or higher specification

    Network interface

    One GE or 10 GE interface

    Contrail Service Orchestration Servers

    Number of nodes or servers for a non-HA environment

    2

    • 1 central server
    • 1 regional server

    Number of nodes or servers for an HA environment

    6

    • 3 central server
    • 3 regional server

    vCPUs

    48

    RAM

    256 GB

    Contrail Analytics Server for a Distributed Deployment

    Number of nodes or servers

    1

    vCPUs

    48

    RAM

    256 GB

    Contrail Cloud Platform for a Centralized Deployment

    Number of nodes or servers

    4–28

    • 3 nodes for Contrail controller and Contrail Analytics
    • 1–25 Contrail compute nodes

    vCPUs per node or server

    48

    RAM per node or server

    256 GB

    Software and VM Requirements

    You must use the software versions that were tested in the Cloud CPE solution. This section shows the VMs required for each type of environment.

    Table 10 shows complete details about the VMs required for a test environment.

    Table 10: Details of VMs for a Demo Environment

    Name of VM

    Components That Installer Places in VM

    Resources Required

    Ports to Open

    csp-installer-vm

    • 4 vCPUs
    • 32 GB RAM
    • 300 GB hard disk storage

    See Table 13.

    csp-central-infravm

    Third-party applications used as infrastructure services

    • 4 CPU
    • 16 GB RAM
    • 200 GB hard disk storage

    See Table 13.

    csp-central-msvm

    All microservices, including GUI applications, plus the following components:

    • HAProxy Configuration
    • ETCD
    • Kubemaster
    • Kubeminion
    • SIM client
    • 4 vCPUs
    • 16 GB RAM (Minimum requirement)
    • 200 GB hard disk storage

    See Table 13.

    csp-regional-infravm

    Third-party applications used as infrastructure services

    • 4 vCPUs
    • 16 GB RAM
    • 200 GB hard disk storage

    See Table 13.

    csp-regional-msvm

    All microservices, including GUI applications, plus the following components:

    • HAProxy Configuration
    • ETCD
    • Kubemaster
    • Kubeminion
    • SIM client
    • 4 vCPUs
    • 16 GB RAM
    • 200 GB hard disk storage

    See Table 13.

    csp-space-vm

    Junos Space Virtual Appliance and database—required only if you deploy virtualized network functions (VNFs) that use this EMS

    • 4 vCPUs
    • 16 GB RAM
    • 200 GB hard disk storage

    See Table 13.

    csp-contrail-analytics-vm

    For a distributed deployment, you install Contrail on this VM to make use of Contrail Analytics.

    For a centralized deployment, you can use the Contrail OpenStack in the Contrail Cloud Platform.

    • 4 vCPUs
    • 16 GB RAM
    • 200 GB hard disk storage

    See Table 13.

    Table 11 shows complete details about VMs and microservice collections required for a production environment without infrastructure services HA. The microservices are installed directly on the server.

    Table 11: Details of VMs and Microservice Collections for a Production Environment Without HA

    Name of VM or Microservice Collection

    VM or Microservice Collection

    Components That Installer Places in VM

    Resources Required

    Ports to Open

    csp-installer-vm

    VM

    • 4 vCPUs
    • 32 GB RAM
    • 300 GB hard disk storage

    See Table 13.

    csp-central-infravm

    VM

    Third -party applications used as infrastructure services

    • 8 vCPUs
    • 48 GB RAM
    • 500 GB hard disk storage

    See Table 13.

    csp-central-ms

    Microservice collection

    All microservices, including GUI applications, plus the following components:

    • HAProxy Configuration
    • ETCD
    • Kubemaster
    • Kubeminion
    • SIM client
    • 48 CPUs
    • 256 GB RAM

    See Table 13.

    csp-regional-infravm

    VM

    Third -party applications used as infrastructure services

    • 8 vCPUs
    • 48 GB RAM
    • 500 GB hard disk storage

    See Table 13.

    csp-regional-ms

    Microservice collection

    All microservices, including GUI applications, plus the following components:

    • HAProxy Configuration
    • ETCD
    • Kubemaster
    • Kubeminion
    • SIM client
    • 48 CPUs
    • 256 GB RAM

    See Table 13.

    csp-space-vm

    VM

    Junos Space Virtual Appliance and database—required only if you deploy VNFs that use this EMS

    • 4 vCPUs
    • 32 GB RAM
    • 300 GB hard disk storage

    See Table 13.

    csp-contrail-analytics-vm

    VM

    For a distributed deployment, you install Contrail OpenStack on this VM.

    For a centralized deployment, you can use Contrail OpenStack in the Contrail Cloud Platform for Contrail Analytics functionality.

    • 8 vCPUs
    • 32 GB RAM
    • 300 GB hard disk storage

    See Table 13.

    Table 12: Details of VMs and Microservice Collections for a Production Environment with HA

    Name of VM or Microservice Collection

    VM or Microservice Collection

    Components That Installer Places in VM

    Resources Required

    Ports to Open

    csp-installer-vm

    VM

    • 4 vCPUs
    • 32 GB RAM
    • 300 GB hard disk storage

    See Table 13.

    csp-central-infravm1

    VM

    Third -party applications used as infrastructure services

    • 6 vCPUs
    • 48 GB RAM
    • 500 GB hard disk storage

    See Table 13.

    csp-central-infravm2

    VM

    Third -party applications used as infrastructure services

    • 6 vCPUs
    • 48 GB RAM
    • 500 GB hard disk storage

    See Table 13.

    csp-central-infravm3

    VM

    Third -party applications used as infrastructure services

    • 6 vCPUs
    • 48 GB RAM
    • 500 GB hard disk storage

    See Table 13.

    csp-central-lbvm

    VM

    Load balancing applications

    • 6 vCPUs
    • 48 GB RAM
    • 300 GB hard disk storage

    See Table 13.

    csp-central-ms

    Microservice collection

    All microservices, including GUI applications, plus the following components:

    • HAProxy Configuration
    • ETCD
    • Kubemaster
    • Kubeminion
    • SIM client
    • 48 CPUs
    • 256 GB RAM

    See Table 13.

    csp-regional-infravm1

    VM

    Third -party applications used as infrastructure services

    • 6 vCPUs
    • 48 GB RAM
    • 500 GB hard disk storage

    See Table 13.

    csp-regional-infravm2

    VM

    Third -party applications used as infrastructure services

    • 6 vCPUs
    • 48 GB RAM
    • 500 GB hard disk storage

    See Table 13.

    csp-regional-infravm3

    VM

    Third -party applications used as infrastructure services

    • 6 vCPUs
    • 48 GB RAM
    • 500 GB hard disk storage

    See Table 13.

    csp-regional-ms

    Microservice collection

    All microservices, including GUI applications, plus the following components:

    • HAProxy Configuration
    • ETCD
    • Kubemaster
    • Kubeminion
    • SIM client
    • 48 CPUs
    • 256 GB RAM

    See Table 13.

    csp-regional-lbvm

    VM

    Load balancing applications

    • 6 vCPUs
    • 48 GB RAM
    • 300 GB hard disk storage

    See Table 13.

    csp-space-vm

    VM

    Junos Space Virtual Appliance and database—required only if you deploy VNFs that use this EMS

    • 4 vCPUs
    • 32 GB RAM
    • 300 GB hard disk storage

    See Table 13.

    csp-contrail-analytics-vm

    VM

    For a distributed deployment, the administrators install Contrail Service Orchestration ( contrail_analytics) on this VM.

    For a centralized deployment, you can use the Contrail OpenStack in the Contrail Cloud Platform.

    • 8 vCPUs
    • 32 GB RAM
    • 300 GB hard disk storage

    See Table 13.

    Table 13 shows the ports that you must open on all VMs in the Cloud CPE Solution.

    Table 13: Ports to Open on VMs in the Cloud CPE Solution

    53

    2379

    4194

    5665

    6379

    8082

    9042

    10255

    80 through 83

    2380

    5000

    5671

    6543

    8083

    9090

    15100

    443

    2888

    5044

    5672

    7804

    8085

    9093

    15672

    1414

    3306

    5432

    6000

    8006

    8086

    9160

    30000 through 32767

    1947

    3888

    5543

    6001

    8016

    8090

    9200

    35357

    2181

    4001

    5601

    6002

    8080

    8091

    10248

    Accessing GUIs

    Table 14 shows the URLs and login credentials for the GUIs for a non-redundant Contrail Service Orchestration installation.

    Table 14: Access Details for the GUIs

    GUI

    URL

    Login Credentials

    Administration Portal

    http://central-IP-Address:81/admin-portal-ui/index.html

    where:

    central-IP-Address—IP address of the server or VM that hosts the microservices for the central POP

    For example:

    http://192.0.2.1:81/admin-portal-ui/index.html

    OpenStack Keystone username and password

    The default username is cspadmin and the default password is passw0rd.

    Customer Portal

    http://central-IP-Address:82/self-care-portal-ui/index.html

    where:

    central-IP-Address—IP address of the server or VM that hosts the microservices for the central POP

    For example:

    http://192.0.2.1:82/self-care-portal-ui/index.html

    Specify the credentials when you create the Customer either In Administration Portal or with API calls.

    Kibana

    http://infra-vm-IP-Address:5601

    where:

    infra-vm-IP-Address—IP address of the VM that hosts the infrastructure services for a central or regional POP

    For example:

    http://192.0.2.2:5601

    Login credentials are not needed.

    Network Service Director

    http://central-IP-Address:83/nsd-ui/index.html

    where:

    central-IP-Address—IP address of the server or VM that hosts the microservices for the central POP

    For example:

    http://192.0.2.1:83/nsd-ui/index.html

    OpenStack Keystone username and password

    The default username is cspadmin and the default password is passw0rd.

    Service and Infrastructure Monitor

    http://central-IP-Address:1947/icingaweb2

    where:

    central-IP-Address—IP address of the server or VM that hosts the microservices for the central POP

    For example:

    http://192.0.2.1:1947/icingaweb2

    • username—icinga
    • password—csoJuniper

    VNFs Supported

    The Cloud CPE solution supports the Juniper Networks and third-party VNFs listed in Table 15.

    Table 15: VNFs Supported by the Cloud CPE Solution

    VNF Name

    Network Functions Supported

    Deployment Model Support

    Element Management System Support

    Juniper Networks vSRX

    • Network Address Translation
    • Demonstration version of Deep Packet Inspection (DPI)
    • Firewall
    • Unified Threat Management (UTM)
    • Centralized deployment
    • Distributed deployment supports firewall and UTM

    EMS microservice

    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)

    Firewall

    Centralized deployment

    Junos Space Network Management Platform

    Riverbed Steelhead

    WAN optimization

    Distributed deployment, NFX250 platform only

    EMS microservice

    Silver Peak VX

    WAN optimization

    Distributed deployment, NFX250 platform only

    EMS microservice

    Licensing

    You must have licenses to download and use the Juniper Networks Cloud CPE Solution. When you order licenses, you receive the information that you need to download and use the Cloud CPE Solution. If you did not order the licenses, contact your account team or Juniper Networks Customer Care for assistance.

    The Cloud CPE solution licensing model depends on whether you use a centralized or distributed deployment:

    • For a centralized deployment, you need licenses for Network Service Orchestrator and for Contrail Cloud Platform. You can either purchase both types of licenses in one Cloud CPE MANO package or you can purchase each type of license individually.

      You also need licenses for:

      • Junos OS software for the MX Series router, EX Series switch, and QFX Series switch in the Contrail Cloud Platform.
      • VNFs that you deploy.
      • (Optional) Licenses for Junos Space Network Management Platform, if you deploy VNFs that require this EMS.
    • For a distributed deployment, you need licenses for Network Service Orchestrator and for Network Service Controller.

      You also need licenses for the following items, depending on which you use in your deployment.

      • The vSRX application that provides the security gateway for the NFX250 device or the vSRX implementation used as a CPE device.
      • VNFs that you deploy.
      • Junos OS software for the MX Series router, including licenses for DHCP subscribers.
      • Junos OS software for the SRX Series Services Gateways.
    • For a combined centralized and distributed deployment, you need licenses for components for both types of deployment.

    Modified: 2017-02-07