Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Guide That Contains This Content
[+] Expand All
[-] Collapse All

Cloud CPE Solution Overview

The Juniper Networks Cloud CPE solution uses the Contrail Software Orchestration (CSO) software to transform traditional branch networks, offering opportunities for high flexibility of the network, rapid introduction of new services, automation of network administration, and cost savings. Based on the European Telecommunications Standards Institute (ETSI) standards for Network Functions Virtualization (NFV) management and orchestration (MANO), the solution can be implemented by service providers to provide network services for their customers or by Enterprise IT departments in a campus and branch environment. In this documentation, service providers and Enterprise IT departments are called service providers, and the consumers of their services are called customers.

The Cloud CPE solution offers the following implementations:

  • Hybrid WAN

    The hybrid WAN implementation offers end-to-end provisioning of Layer 4 through Layer 7 network services through an open, cloud-based architecture. The solution supports both Juniper Networks and third-party virtualized network functions (VNFs) that network providers use to create the network services. The following deployment models are available:

    • Cloud CPE Centralized Deployment Model (centralized deployment)

      In the centralized deployment, customers access network services in a service provider’s cloud. Sites that access network services in this way are called service edge sites in this documentation.

    • Cloud CPE Distributed Deployment Model (distributed deployment)

      In the distributed deployment, customers access network services on a CPE device, located at a customer’s site. These sites are called on-premise sites in this documentation.

    • A combined centralized and distributed deployment

      In this deployment, the network contains both service edge sites and on-premise sites. A customer can have both cloud sites and tenant sites; however, you cannot share a network service between the centralized and distributed deployments. If you require the same network service for the centralized deployment and the distributed deployment, you must create two identical network services with different names.

    You must consider several issues when choosing whether to employ one or both types of deployment. The centralized deployment offers a fast migration route, because you can replace a traditional CPE at a customer’s site with a simple Layer 3 network interface device (NID) to enable access to the network provider’s cloud. This deployment is the recommended model for sites that can accommodate network services—particularly security services—in the cloud.

    In contrast, the distributed deployment supports private hosting of network services on a CPE device at a customer’s site, and can be extended to offer software defined wide area networking (SD-WAN) capabilities. Implementing a combination network in which some sites use the centralized deployment and some sites use the distributed deployment provides appropriate access for different sites.

  • SD-WAN

    The SD-WAN implementation offers a flexible and automated way to route traffic through the cloud. Similar to a distributed deployment, this implementation uses CPE devices located at on-premise sites to connect to the LAN segments. On the WAN side, the CPE devices connect to a hub device in a hub-and-spoke VPN. Traffic travels from site-to-site and from each site to the Internet through a hub device. The CSO software uses SD-WAN policies and service-level agreement measurements to differentiate and route traffic for different applications.

One CSO installation can support a hybrid WAN and an SD-WAN implementation simultaneously. The same set of CPE devices can be used for the distributed deployment and the SD-WAN deployment. Alternatively, you can implement only the deployments that you need.

You can either use the Cloud CPE Solution as a turnkey implementation or connect to other operational support and business support systems (OSS/BSS) through northbound Representational State Transfer (REST) APIs.

Modified: 2017-10-26