Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

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

    Cloud CPE Solution Overview

    The Juniper Networks Cloud CPE solution transforms 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 Cloud CPE solution 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 solution can be implemented by service providers to provide network services for branch offices 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 solution offers the following deployment models:

    • 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 cloud 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 cloud 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.

    Service providers 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 offers 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. In this case, the deployments use a central orchestration and management implementation and can share customers. You must, however, create separate network services for each deployment.

    Modified: 2017-02-08