Supported Platforms
Related Documentation
- MX Series
- Understanding How MX Series Router Cloud CPE Services Virtualize Customer Premises Equipment (CPE) Services
- MX Series Router Cloud CPE Services End-To-End Solution Architecture
- Managing MX Series Router Cloud CPE Services
- APIs for the Cloud CPE Selfcare Application for MX Series Routers
- Configuring the Common Configuration for MX Series Router Cloud CPE Services
MX Series Router Cloud CPE Services Common Configuration Overview
Using cCPE services on MX Series routers, each subscriber VPN site is represented by one VRF routing instance. VPN routes are stored in the VRF routing table and exported to remote sites through internal BGP (IBGP). VPN routes from remote sites received through IBGP are imported into the VRF table. The VRF export and import polices control how routes are passed between sites.
With full-featured Layer 2 and Layer 3 CPEs, the routing instance learns the VPN routes from the local VPN site through routing protocols or a static route. However, when you use cCPE services, the local site appears as a direct route in the Junos OS because hosts connect to the PE router directly through a Layer 2 switch. MX Series routers support direct routes in the VRF and export direct routes through BGP to remote sites.
cCPE services allow heterogeneous setup; sites using the cCPE services can coexist with sites using a full-featured Layer 3 CPE in the same VPN.
To use cCPE services, you must configure the MX Series router with a specific configuration. We refer to this configuration as the cCPE common configuration because it is required to run any cCPE services. The common configuration includes defining the physical access link to your subscriber sites; configuring the cCPE context, which is a VRF routing instance for all VPN services; and configuring a generic routing policy for advertising routes. The cCPE common configuration requires a Gigabit Ethernet interface be used as the access link to the subscriber site. The logical interface is configured for Layer 2 mode (vlan-bridge) encapsulation and integrated routing and bridging.
![]() | Note: Minimum hardware requirements—cCPE services require a minimum of an MX80 Series 3D Universal Edge Router with MPCs/MICs. |
![]() | Note: Configuration of MPLS and BGP between PE routers is not described here, because their configuration is the same as the configuration of traditional MPLS/BGP VPNs with a Layer 3 CPE. |
Related Documentation
- MX Series
- Understanding How MX Series Router Cloud CPE Services Virtualize Customer Premises Equipment (CPE) Services
- MX Series Router Cloud CPE Services End-To-End Solution Architecture
- Managing MX Series Router Cloud CPE Services
- APIs for the Cloud CPE Selfcare Application for MX Series Routers
- Configuring the Common Configuration for MX Series Router Cloud CPE Services
Modified: 2015-11-04
Supported Platforms
Related Documentation
- MX Series
- Understanding How MX Series Router Cloud CPE Services Virtualize Customer Premises Equipment (CPE) Services
- MX Series Router Cloud CPE Services End-To-End Solution Architecture
- Managing MX Series Router Cloud CPE Services
- APIs for the Cloud CPE Selfcare Application for MX Series Routers
- Configuring the Common Configuration for MX Series Router Cloud CPE Services