Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


vEPC Detailed Design


Figure 1 is an example of a VM and networking design of the vEPC that is small sized and of compact mode and includes both the mobility management entity (MME) and Service Provider Gateway mobile content core (MCC).

Figure 1: vEPC VM and Networking
vEPC VM and Networking

This illustration describes a set of VMs and networks for the vEPC. This deployment comprises multiple networks. These networks include not just virtual networks but loopback addresses that represent the various Gi and Gn network contexts. In addition to this, there are various health checks created as described in Health Check Object on the ports that are advertising these loopback addresses. This ensures that if the port goes down, the health check fails and the routes are withdrawn from that port. This guarantees that there is no silent packet drop of traffic. Another feature used in the topology is network policy. Because each virtual network, by default, cannot talk to each other, you must allow networks to talk to each other through a network policy. Network Policy is described in Creating a Network Policy with Juniper Networks Contrail.

Juniper Professional Services will be provided access to the heat templates to deploy Affirmed and vSRX workloads on Contrail Cloud 10.0. These are the tenant workloads that comprise the end-to-end mobility solution. Review the heat templates for each respective network and VMs to understand what and where the OpenStack and Contrail components are in this solution.