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

    • Support for single and multiple POPs with one VIM—You can deploy the Cloud CPE Centralized Deployment Model in one or more POPs. The deployment model supports one virtualized infrastructure manager (VIM) for all POPs.
    • Fully integrated and tested hardware and software—The Cloud CPE Centralized Deployment Model uses the Contrail Cloud Reference Architecture (CCRA) to support the service provider’s cloud. The CCRA consists of network devices, servers, and the Contrail Cloud Platform software. The Contrail Service Orchestration software is installed on a server in the CCRA to complete the Cloud CPE Centralized Deployment Model. See Table 1 through Table 3 for details of the hardware and software used and tested in the Cloud CPE Centralized Deployment Model.
    • Automated deployment of the software components—We provide an installer that you use with a configuration file to deploy the software components of the Cloud CPE Centralized Deployment Model. You provide values specific to your network environment in the configuration file.
    • Automated creation of configuration of VMs for the software components—We provide a provisioning tool that creates and configures the required VMs if you use the KVM hypervisor on the Contrail Service Orchestration node, on that node.
    • VNF support—The Cloud CPE Centralized Deployment Model supports the following VNFs, which are directly managed by VNF Manager and installed in the VNF catalog:
      • Carrier-Grade Network Address Translation (CGNAT), Firewall, Unified Threat Management (UTM), and a demonstration version of Deep Packet Inspection (DPI) through vSRX.
      • NAT and Firewall through the LxCIPTable VNF. This third-party VNF is free and operates in Linux Containers in the Linux kernel.
    • Creation, design, and delivery of network services—You can perform these tasks with the Network Services Designer GUI or its APIs:
      • Create requests for new network services.
      • Design customized network services for your customers.
      • Design new standard network services that you can offer to all your customers.
      • Update existing network services.
      • Publish services to the network service catalog.
      • Manage network services that you are designing or have published to the network catalog.
      • Configure settings for the network service, such as NAT and firewall policies.
    • Management of customers—You manage enterprises and sites through the Cloud CPE Tenant, Site and Service Manager APIs or the Administration CLI. For example, you can:
      • Create and delete an NFV Infrastructure point-of-presence (N-POP)—In this case, an entity that represents a location in the enterprise customer’s network where a network function is implemented as a VNF.
      • Create, define, and delete a tenant—An entity that represents the customer’s organization and includes all sites.
      • Create, define, and delete sites.
      • Deliver network services.
      • Terminate network services .
      • View the status and statistics for network services.
    • Management of customers’ staff—You manage administrators and other staff who work for your customers through the Identity and Access Manager APIs or the Administration CLI. You can:
      • Create administrators and other users for an organization and its individual sites.
      • Assign roles to users.
      • Delete users.
    • Customer management of sites and network services—Customers can use Customer Portal to view a visual topology of their networks and perform the following management tasks:
      • Activate and deactivate sites in the network.
      • Add a site-specific network service between a site and the VPN.
      • Add a customer-specific network service between the VPN and the Internet.
      • Configure network services.
      • Disable and remove network services on a connection.
      • Replace a network service on a connection with another network service.
    • Monitoring of key performance indicators—You monitor and troubleshoot the Cloud CPE Centralized Deployment Model through Service and Infrastructure Monitor, which provides both a quick visual display of the Cloud CPE Centralized Deployment Model status and more detailed lists of event messages. With Service and Infrastructure Monitor, you can view information about:
      • Physical servers.
      • VMs that host software components.
      • Network services and their component VNFs.
      • VMs that host the component VNFs.
    • Logging for Contrail Service Orchestration—You can view a visual display of data in the log files through the Kibana software for:
      • Cloud CPE Tenant, Site and Service Manager
      • Identity and Access Manager
      • Network Service Orchestrator
      • VNF Manager
    • Element management system—The Junos Space Virtual Appliance provides an element management system (EMS) for the vSRX and the MX Series router in the Cloud CPE Centralized Deployment Model. You can either use a standalone Junos Space Virtual Appliance or a Junos Space cluster, which provides redundancy and contributes to high availability of VNFs. The Junos Space cluster consists of two virtual appliances, each with its own database.
    • High availability of software components—Service and Infrastructure Monitor tracks critical conditions for software components and restarts the components if necessary. Two instances of Service and Infrastructure Monitor on the Contrail Service Orchestrator provide redundancy and high availability for tracking critical conditions.
    • High availability of VNFs—VNFs recover or restart if an issue on a compute node other than the one associated with the VNF affects the VNF operation. EMS redundancy also contributes to high availability of VNFs.

    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:

    • Forty eight 10/100/1000 GE interfaces
    • Four built-in 10 GE SFP interfaces

    1

    Data switch

    Juniper Networks QFX Series Switch

    QFX 5100-48S-AFI switch with:

    • Forty eight SFP+ interfaces
    • Six QSFP+ interfaces

    1

    Servers

    Quanta QuantaPlex T41S-2U

    2U 4-Node server

    See Table 2

    At least 2, up to 5

    The Cloud CPE Centralized Deployment Model was tested on servers with the specifications shown in Table 2.

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

    Function

    Model

    Quantity

    Base server

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

    At least 2, up to 5

    CPU

    E5-2670 v3

    2

    Memory

    256 GB DDR4 2133 MHz

    (16 GB DIMMs—slots fully populated)

    16

    Hard disk drive

    2.5" 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+ 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

    Ubuntu 14.04.02 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 2.21

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

    OpenStack Icehouse

    Network Functions Virtualization (NFV)

    Contrail Service Orchestration 1.0.1

    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

    Support of described functions

    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 server and VMs

    Ubuntu 14.04.02 LTS

    Hypervisor on Contrail Service Orchestration node

    Contrail 2.21 with OpenStack (Icehouse), 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

    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 shows complete details for the VMs required on the Contrail Service Orchestration node.

    Table 6: Software Requirements for VMs on Contrail Service Orchestration Node

    Applications Installer Places in VM

    Number of VMs

    Resources Required

    Ports to Open

    • Cloud CPE Tenant, Site and Service Manager
    • Identity and Access Manager
    • Logstash software
    • Network as a Service
    • Network Service Orchestrator
    • Server Sent Event
    • Service and Infrastructure Monitor Client
    • VNF Manager

    1

    • 8 vCPUs
    • 32 GB RAM
    • 200 GB hard disk storage
    • 80
    • 4505
    • 4506
    • 5000
    • 5601
    • 6543
    • 8006
    • 8016
    • 8090
    • 8091
    • 8092
    • 8888
    • 9200
    • 9300
    • 9788
    • 10002
    • Customer Portal
    • Kibana
    • Network Service Designer
    • Service and Infrastructure Monitor Client

    1

    • 4 vCPUs
    • 16 GB RAM
    • 200 GB hard disk storage
    • 80
    • 4505
    • 4506
    • 5000
    • 5601
    • 6543
    • 8006
    • 8016
    • 8090
    • 8091
    • 8092
    • 8888
    • 9200
    • 9300
    • 9788
    • 10002

    Junos Space Virtual Appliance

    • 1 (standalone virtual appliance)
    • 2 (Junos Space cluster for high availability)
    • 4 vCPUs
    • 16 GB RAM
    • 300 GB hard disk storage

    None

    Junos Space database (only required for Junos Space cluster for high availability)

    2

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

    None

    Custom Contrail

    1

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

    None

    • Service and Infrastructure Monitor Controller

      Load Balancer

    1

    • 4 vCPUs
    • 16 GB RAM
    • 100 GB hard disk storage
    • 80
    • 3306
    • 4505
    • 4506
    • 5432
    • 5601
    • 8888
    • 10002

    Service and Infrastructure Monitor

    2 (primary and secondary)

    • 4 vCPUs
    • 32 GB RAM
    • 200 GB hard disk storage
    • Caution: Make sure that MySQL software is not installed in the VM for 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.

    • 80
    • 3306
    • 4505
    • 4506
    • 5432
    • 5601
    • 8888
    • 10002

    Table 7 lists the requirements for the VM for the installer. You create this VM on a server that is separate from the Cloud CPE Centralized Deployment Model cluster, although on the same subnet.

    Table 7: Requirements for Installer VM

    Applications Installer Places in VM

    Number of VMs

    Resources Required

    Ports to Open

    Installer and Administration CLI

    1

    • 8 vCPUs
    • 8 GB RAM
    • 100 GB hard disk storage
    • 4505
    • 4506

    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 8.

    Table 8: 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-02-01