rovide high SLAs on top of resources and tools that were not planned to do SO. For example, existing overlay solu- tions are not aware of the underlay network and its limitations and are hence vulnerable to reduced service levels due to traffic dynam- ics. In addition, cloud provisioning was designed with compute opti- mization in mind, whereas VNFs are often bandwidth- rather than compute-constrained. Finally, the industry has not yet come up with NFV-specific SLA monitoring and verification tools that would give customers the assurances and make them trust the lean and dynamic distributed systems with carrying production size loads. Cloudification of the vCPE solution brings three important advantages: Cost-effective management and agility: By cloudifying vCPE, we decouple provisioning and VNF onboarding, which is complex and slow today, due to the local provisioning of the physical enterprise site. This semimanual provisioning may be frequent and dependent on many access network factors, including changing demands of the enterprise. In the cloudified solution, the vCPE capacity of all the enterprise sites is in the distributed carrier cloud, for example, the provider point of presence (POP) sites. High performance at scale: By cloudifying vCPE, we only need to orchestrate resources per POP for the average demand of the 5 SDN and NFV in 5G enterprise sites connected to that POP. This includes also Internet peering capacity and related NAT functions. We also do not need to explicitly orchestrate for geo redundant vCPE capacity. This can lead to significant (some estimates are up to 4x) savings in vCPE resources. High availability: By cloudifying vCPE, we can have faster recovery from vCPE failures. Traffic to failed components is distributed to cloudified resources avoiding sharp hits and potential domino col- lapses in case of POP or rack failures. To achieve the goals of cloudification with scalable, dynamic, and efficient operations, we must have the following: Network underlay awareness: If the demand is ran