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 
ContentIndex
  

No index entries found.

Related Documentation

    Features Supported in This Release

    • Administration Portal—Contrail Service Orchestration now includes an Administration Portal that you can use to perform administrative tasks for the Cloud CPE Centralized Deployment Model, such as:
      • Configuring the virtualized infrastructure manager (VIM).
      • Configuring points of presence (POPs).
      • Configuring the element management system (EMS) for the VNFs.
      • Configuring resources and virtual networks used by Network Service Orchestrator and Contrail Cloud Platform for orchestrating network services.
      • Adding a new customer, adding an administrator at the customer enterprise who activates and manages network services, and adding customer sites.
      • Allocating network services to customers.
    • Direct Access to the Internet from Sites—You can now configure direct access to the Internet for sites in a customer’s network. Sites can also connect to the Internet through the customer’s VPN. Sites can connect to the Internet through either or both of these topologies. You can activate network services on any connection in these topologies.
    • Support for multiple VIMs—The Cloud CPE Centralized Deployment Model now supports multiple VIMs to enable use of a dedicated VIM in a specific regional POP. This feature optimizes performance and enables scaling of the deployment model. A single instance of Contrail OpenStack, as part of a dedicated Contrail Cloud Reference Architecture (CCRA) installation, provides the VIM for the region, and all VIMs share a single OpenStack Keystone in the central POP. Contrail Service Orchestration in the central POP the provides management and orchestration for all regions of the network and communicates with the OpenStack Keystone. You configure multiple VIMs with the Cloud CPE Centralized Deployment Model installer and its associated configuration file.
    • Support for Contrail Service Orchestration high availabilty—You can install the Cloud CPE Centralized Deployment Model with high availability for Contrail Service Orchestration. This installation includes two Contrail Service Orchestration nodes on different servers in the central CCRA. Each of these nodes hosts instances of the Contrail Service Orchestration components and if a component on the primary node fails, the corresponding component on the secondary nodes takes over. Contrail Service Orchestration high availability provides resiliency for the graphical user interfaces (GUIs), APIs, and the NFV management and orchestration (MANO) processes. You can still use a non-redundant Contrail Service Orchestration configuration if you prefer. in either case, Contrail Service Orchestration in the central POP the provides management and orchestration of network services in all regional POPs.
    • Deployment on a Contrail OpenStack instance configured for high availability—The installer for the Cloud CPE Centralized Deployment Model now enables installation of the deployment model on a Contrail OpenStack instance configured for high availability. This configuration includes three redundant Contrail configure and control nodes in a CCRA, and provides resiliency for VIMs, VNFs, and network services.
    • Support for new VNFs—The Cloud CPE Centralized Deployment Model now supports the Cisco Cloud Services Router 1000V Series (CSR-1000V) firewall VNF.
    • Monitoring network services in Customer Portal—End users can now monitor information about active network services in their network by linking directly to Service and Infrastructure Monitor from Customer Portal.
    • Configuration of VNFs in Network Service Designer and Customer Portal—The graphical user interface (GUI) for configuring VNFs has changed and you can now configure additional settings for some VNFs.
    • Configuration of Syslog servers for vSRX VNF instances—You can now configure Syslog servers for vSRX VNFs instances in Network Service Designer and Customer Portal.
    • Introduction of the MX Series router as a physical network element (PNE)—The Cloud CPE Centralized Deployment Model now supports the MX Series router as a PNE. Configuration of the PNE in Contrail Service Orchestration simplifies provisioning of the physical device through automation. Combining provisioning and configuration for PNEs and VNFs provides end-to-end automation in network configuration workflows. You configure the PNE in Administration Portal.
    • VNF resiliency—If a network service becomes unavailable due to a connectivity issue with a VNF, Network Service Orchestrator maintains existing instances of the network service in end users’ networks and initiates recreation of the VNFs. During this recovery process, the end user cannot activate the network service on additional network links. When the problem is resolved, normal operation resumes and end users can activate the network service on additional network links.

    Tested Hardware and Software

    The Cloud CPE Centralized Deployment Model has been tested with:

    Table 1: Network Devices Tested in the Cloud CPE Centralized Deployment Model

    Function

    Device

    Model

    Quantity

    Gateway router

    Juniper Networks MX Series 3D Universal Edge Router

    MX80-48T router with
    two 10 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

    Servers

    See Table 2

    See Table 2

    See Table 2

    Table 2: Specification of Servers Tested for Cloud CPE Centralized Deployment Model

    Function

    Model

    Quantity

    Base server

    QuantaPlex T41S-2U 4-Node
    server with 2.5-inch drive bay

    At least 2, up to 5

    CPU

    E5-2670 v2

    2

    Memory

    256 GB DDR4 2133 MHz

    (16 GB DIMMs—slots fully populated)

    16

    Hard disk drive

    2.5 -inch 1 TB SATA Enterprise

    5

    Solid state drive

    Intel DC S3700 series 400 GB SATA

    1

    Controller card

    Large scale integration (LSI) SAS controller 9200-8e card

    1

    Interface card

    Dual-port 10 GE SFP+ transceiver OCP mezzanine card

    1

    Interface card

    Dual-port 1 GE mezzanine card

    1

    Power supply unit (PSU)

    1600 W high-efficiency redundant power supply

    2

    Table 3: Software Used in Cloud CPE Centralized Deployment Model

    Function

    Software and Version

    Operating system for servers and nodes

    One of the following:

    • Ubuntu 14.04 LTS
    • Ubuntu 14.04.1 LTS

    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

    Operating system for Junos Space Virtual Appliance

    Junos Space Network Management Platform Release 15.1R1

    Software-defined networking (SDN)

    Contrail Release 2.21

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

    OpenStack Juno

    Network Functions Virtualization (NFV)

    Contrail Service Orchestration Release 1.5

    Minimum Hardware and Software Requirements for the Servers and VMs

    The Cloud CPE Centralized Deployment Model runs on commercial off-the-shelf (COTS) x86 servers. When obtaining servers for the Cloud CPE Centralized Deployment Model, 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.

    Table 4 shows the required hardware specification for servers you use in the Cloud CPE Centralized Deployment Model.

    Table 4: Minimum Hardware Requirements for Servers in Cloud CPE Centralized Deployment Model

    Function

    Requirement

    Quantity

    Base server

    x86 server with 4 nodes

    At least 2, up to 5

    CPUs

    Type Intel Sandybridge, such as Intel Xeon E5-2670v2 @ 2.5 Ghz

    2

    Memory

    256 GB per server

    Hard disk drive (HDD)

    1 TB, Serial Advanced Technology Attachment (SATA) or Serial Attached SCSI (SAS)

    5

    Solid state drive (SSD)

    200 GB

    1 or more

    Data and Control interface

    10 Gigabit Ethernet (GE) interface on PCIe adaptor or mezzanine card

    2

    Management Interface

    1 GE interface

    2

    Out-of-Band Interface

    Intelligent Platform Management Interface (IPMI)

    1

    Table 5 lists the software requirements for the servers.

    Table 5: Software Requirements for Cloud CPE Centralized Deployment Model

    Description

    Version

    Operating system for servers and nodes

    One of the following:

    • Ubuntu 14.04 LTS
    • Ubuntu 14.04.1 LTS

    Operating system for VMs

    Ubuntu 14.04.2 LTS

    Hypervisor on Contrail Service Orchestration node

    Contrail Release 2.21 with OpenStack (Juno), or VMware ESXi Version 5.5.0

    VMs on Contrail Service Orchestration node

    If you use the KVM hypervisor on the Contrail Service Orchestration node, you can use the provisioning tool to create VMs.

    See Table 6 and Table 7.

    Additional software (only required for Contrail Service Orchestration node)

    Secure File Transfer Protocol (SFTP)

    Additional requirements

    • Disable DHCP servers on the subnet on which you install the Cloud CPE Centralized Deployment Model. The installer deploys and configures DHCP servers.
    • Caution: Do not install MySQL software on the VM that you use for the Service and Infrastructure Monitor. The installer deploys and configures MySQL servers in this VM. If the VM already contains My SQL software, the installer may not set up the VM correctly.

    Table 6: Details of VMs on the Contrail Service Orchestration Node for a Non-Redundant Configuration

    Name of VM

    Components That Installer Places in VM

    Resources Required

    Ports to Open

    csp-ui-vm

    • Administration Portal
    • Customer Portal
    • Network Service Designer
    • Notification Engine
    • Service and Infrastructure Monitor Client
    • 4 vCPUs
    • 16 GB RAM
    • 300 GB hard disk storage

    Note: Open these ports for all VMs on the Contrail Service Orchestration node.

    • 80
    • 2181
    • 3306
    • 4505
    • 4506
    • 5000
    • 5044
    • 5432
    • 5601
    • 5671
    • 5672
    • 6543
    • 8006
    • 8016
    • 8080
    • 8082
    • 8090
    • 8091
    • 8092
    • 8888
    • 9160
    • 9200
    • 9300
    • 9788
    • 10002
    • 35357

    csp-ms-vm

    • Cloud CPE Tenant, Site and Service Manager
    • Identity and Access Manager
    • Notification Engine
    • Network Service Orchestrator
    • Server Sent Event
    • Service and Infrastructure Monitor Client
    • VNF Manager
    • Filebeat
    • 8 vCPUs
    • 32 GB RAM
    • 300 GB hard disk storage

    Open the ports listed for the csp-ui-vm VM.

    csp-elk-vm

    • Kibana
    • Logstash
    • 4 vCPUs
    • 24 GB RAM
    • 300 GB hard disk storage

    Open the ports listed for the csp-ui-vm VM.

    csp-infra1-vm

    • Cassandra
    • Elastic Search
    • Load Balancer
    • 4 vCPUs
    • 32 GB RAM
    • 300 GB hard disk storage

    Open the ports listed for the csp-ui-vm VM.

    csp-infra2-vm

    • Zookeeper
    • RabbitMQ
    • Redis
    • 4 vCPUs
    • 32 GB RAM
    • 300 GB hard disk storage

    Open the ports listed for the csp-ui-vm VM.

    csp-simcontroller-vm

    • Service and Infrastructure Monitor Controller
    • Device Connectivity
    • Service and Infrastructure Monitor Client
    • 4 vCPUs
    • 32 GB RAM
    • 300 GB hard disk storage

    Open the ports listed for the csp-ui-vm VM.

    csp-sim-vm

    Service and Infrastructure Monitor

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

    Caution: Make sure that MySQL software is not installed in the VM for Service and Infrastructure Monitor. When you install the Cloud CPE Centralized Deployment Model, the installer deploys and configures MySQL servers in this VM. If the VM already contains MySQL software, the installer may not set up the VM correctly.

    Open the ports listed for the csp-ui-vm VM.

    csp-space-vm

    Junos Space Virtual Appliance and database

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

    Open the ports listed for the csp-ui-vm VM.

    Table 7 shows complete details about the VMs required on the Contrail Service Orchestration nodes on server 1 and server 2 for a redundant Contrail Service Orchestration configuration.

    Table 7: Details of VMs on Contrail Service Orchestration Nodes for a Redundant Configuration

    Components That Installer Places in VM

    Distribution of VMs

    Resources Required for Each VM

    Ports to Open

    • Administration Portal
    • Customer Portal
    • Network Service Designer
    • Service and Infrastructure Monitor Client

    1 per Contrail Service Orchestration node

    • csp-ui-vm1 on cso-host1
    • csp-ui-vm2 on cso-host2
    • 4 vCPUs
    • 16 GB RAM
    • 300 GB hard disk storage

    Note: Open these ports for all VMs on the Contrail Service Orchestration node.

    • 80
    • 2181
    • 3306
    • 4505
    • 4506
    • 5000
    • 5044
    • 5432
    • 5601
    • 5671
    • 5672
    • 6543
    • 8006
    • 8016
    • 8080
    • 8082
    • 8090
    • 8091
    • 8092
    • 8888
    • 9160
    • 9200
    • 9300
    • 9788
    • 10002
    • 35357
    • Cloud CPE Tenant, Site and Service Manager
    • Identity and Access Manager
    • Notification Engine
    • Network Service Orchestrator
    • Server Sent Event
    • Service and Infrastructure Monitor Client
    • VNF Manager
    • Filebeat

    1 per Contrail Service Orchestration node:

    • csp-ms-vm1 on cso-host1
    • csp-ms-vm2 on cso-host2
    • 4 vCPUs
    • 32 GB RAM
    • 300 GB hard disk storage

    Open the ports listed for the csp-ui-vm VMs.

    • Cassandra
    • Elastic Search
    • Redis (csp-infra-vm1 only)
    • 2 on cso-host1:
      • csp-infra-vm1
      • csp-infra-vm3
    • 1 on cso-host2:
      • csp-infra-vm2
    • 3 vCPUs
    • 32 GB RAM
    • 300 GB hard disk storage

    Open the ports listed for the csp-ui-vm VMs.

    • Zookeeper
    • RabbitMQ (csp-infra-vm5 only)
    • 2 on cso-host2:
      • csp-infra-vm4
      • csp-infra-vm6
    • 1 on cso-host1:
      • csp-infra-vm5
    • 3 vCPUs
    • 32 GB RAM
    • 300 GB hard disk storage

    Open the ports listed for the csp-ui-vm VMs.

    Service and Infrastructure Monitor

    1 on cso-host1:

    • csp-sim-vm1 on cso-host1
    • 4 vCPUs
    • 16 GB RAM
    • 300 GB hard disk storage

    Caution: Make sure that MySQL software is not installed in the VM for Service and Infrastructure Monitor. When you install the Cloud CPE Centralized Deployment Model, the installer deploys and configures MySQL servers in this VM. If the VM already contains MySQL software, the installer may not set up the VM correctly.

    Open the ports listed for the csp-ui-vm VMs.

    Load Balancer

    csp-ha-vm on cso-host-1

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

    Open the ports listed for the csp-ui-vm VMs.

    • Logstash
    • Kibana

    1 per Contrail Service Orchestration node:

    • csp-elk-vm1 on cso-host1
    • csp-elk-vm2 on cso-host2
    • 3 vCPUs
    • 12 GB RAM
    • 300 GB hard disk storage

    Open the ports listed for the csp-ui-vm VMs.

    • Service and Infrastructure Monitor Controller
    • Device Connectivity
    • Service and Infrastructure Monitor Client

    1 per Contrail Service Orchestration node:

    • csp-simcontroller-vm1 on cso-host1
    • csp-simcontroller-vm2 on cso-host2
    • 4 vCPUs
    • 32 GB RAM
    • 300 GB hard disk storage

    Open the ports listed for the csp-ui-vm VMs.

    Junos Space Virtual Appliance

    1 per Contrail Service Orchestration node:

    • csp-space-vm1 on cso-host1
    • csp-space-vm2 on cso-host2
    • 4 vCPUs
    • 12 GB RAM
    • 300 GB hard disk storage

    Open the ports listed for the csp-ui-vm VMs.

    Junos Space database

    1 per Contrail Service Orchestration node:

    • csp-mysql-vm1 on cso-host1
    • csp-mysql-vm2 on cso-host2
    • 4 vCPUs
    • 12 GB RAM
    • 300 GB hard disk storage

    Open the ports listed for the csp-ui-vm VMs.

    Table 8 lists the requirements for the VM for the installer. You need to create this VM on the Contrail Service Orchestration node if you create and configure the Contrail Service Orchestration VMs manually. You must create and configure the VMs manually if you use a supported hypervisor other than KVM on the on the Contrail Service Orchestration node. In addition, if you want to use VMs that you already created, you must configure them manually.

    If you use the provisioning tool to create and configure the VMs, you deploy the installer directly on the Contrail Service Orchestration node. You can use the provisioning tool if you use the KVM hypervisor on a Contrail Service Orchestration node.

    Table 8: Requirements for Installer VM

    Name of VM

    Resources Required

    Ports to Open

    csp-dt-vm

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

    Open the ports listed for the csp-ui-vm VM in Table 6.

    Accessing GUIs

    Access to the GUIs for the Cloud CPE Centralized Deployment Model depends on whether you use a non-redundant or a redundant Contrail Service Orchestration Installation. Table 9 shows the URLs and login credentials for the GUIs for a non-redundant Contrail Service Orchestration installation.

    Table 9: Access Details for the GUIs in a Non-Redundant Contrail Service Orchestration Installation

    GUI

    URL

    Login Credentials

    Administration Portal

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

    where:

    ui-vm-IP-Address—IP address of the VM that contains the GUI components

    For example:

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

    OpenStack Keystone username and password

    Note: You can view these settings on the Contrail configure and control node in the files /etc/contrail/keystonerc and /etc/contrail/openstackrc.

    Customer Portal

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

    where:

    ui-vm-IP-Address—IP address of the VM that contains the GUI components

    For example:

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

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

    Kibana

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

    where:

    elk-vm-IP-Address—IP address of the VM that contains Kibana

    For example:

    http://192.0.2.2:5601

    No login credentials.

    Network Service Director

    http://ui-vm-IP-Address/nsd-ui/index.html

    where:

    ui-vm-IP-Address—IP address of the VM that contains the GUI components

    For example:

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

    OpenStack Keystone username and password

    Note: You can view these settings on the Contrail configure and control node in the files /etc/contrail/keystonerc and /etc/contrail/openstackrc.

    Service and Infrastructure Monitor

    http://sim-cluster-vm-IP-Address/icingaweb2

    where:

    sim-cluster-vm-IP-Address—IP address of the VM that contains Service and Infrastructure Monitor

    For example:

    http://192.0.2.3/icingaweb2

    • username—icinga
    • password—csoJuniper

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

    Table 10: Access Details for the GUIs in a Redundant Contrail Service Orchestration Installation

    GUI

    URL

    Login Credentials

    Administration Portal

    http://ha-vm-IP-Address/admin-portal-ui/index.html

    where:

    ha-vm-IP-Address—IP address of the VM that contains the Load Balancer

    For example:

    http://192.0.2.5/admin-portal-ui/index.html

    OpenStack Keystone username and password

    Note: You can view these settings on the Contrail configure and control node in the files /etc/contrail/keystonerc and /etc/contrail/openstackrc.

    Customer Portal

    http://ha-vm-IP-Address/self-care-portal-ui/index.html

    where:

    ha-vm-IP-Address—IP address of the VM that contains the Load Balancer

    For example:

    http://192.0.2.5/self-care-portal-ui/index.html

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

    Kibana

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

    where:

    ha-vm-IP-Address—IP address of the VM that contains the Load Balancer

    For example:

    http://192.0.2.5:5601

    No login credentials

    Network Service Director

    http://ha-vm-IP-Address/self-care-portal-ui/index.html

    where:

    ha-vm-IP-Address—IP address of the VM that contains the Load Balancer

    For example:

    http://192.0.2.5/nsd-ui/index.html

    OpenStack Keystone username and password

    Note: You can view these settings on the Contrail configure and control node in the files /etc/contrail/keystonerc and /etc/contrail/openstackrc.

    Service and Infrastructure Monitor

    http://ha-vm-IP-Address/icingaweb2

    where:

    ha-vm-IP-Address—IP address of the VM that contains the Load Balancer

    For example:

    http://192.0.2.5/icingaweb2

    • username—icinga
    • password—csoJuniper

    Licensing

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

    Cloud CPE Centralized Deployment Model licensing includes licenses for Contrail Service Orchestration and Contrail Cloud Platform. The Cloud CPE Centralized Deployment Model licenses are based on VNF capacity, which also determines the number of separate Junos Space Network Management Platform licenses required. See Table 11.

    Table 11: Cloud CPE Centralized Deployment Model Licenses

    Number of VNFs Supported

    Number of Contrail Cloud Platform Licenses Included

    Number of Junos Space Network Management Platform Licenses Required

    2000

    1

    2

    10,000

    5

    8

    25,000

    13

    18

    50,000

    25

    34

    Individual Contrail Service Orchestration licenses and Contrail Cloud Platform licenses can be purchased separately. Contrail Service Orchestration licenses are also based on VNF capacity.

    You will also need licenses for the MX Series router, EX Series switch, and QFX Series switch.

    Modified: 2016-06-02