Full mesh MPLS VPN Deployment Guide

Hello, Community friends!

This post features a full mesh MPLS VPN deployment guide. Please have a look below for more information on the topic.

BACKGROUND INFORMATION

This model is also known as any-to-any VPN topology. It is the basic MPLS VPN. In this topology, all the PE can communicate directly with each other. Any PE can learn the other PE routing directly.

The topology is as per below figure.

Figure 1-1. VPN full-mesh topology                                              

As shown in the above figure, the PE1, PE2 and PE3 have the same VRF and can communicate with each other through the MPLS backbone network.

FULL-MESH SERVICE DEPLOYMENT

For the full-mesh VPN service deployment, we can refer to these steps as below:

• create the IP VPN-Instance;

• enable the IPv4 or IPv6 address family for the VPN instance. A VPN instance supports the IPv4 and IPv6 address families. You need to run the ipv4-family (VPN instance view) or ipv6-family (VPN instance view) command to enable the IPv4 or IPv6 address family based on the type of the protocol stack used to advertise VPN routes in the VPN instance;

• configure a Route Distinguisher (RD) for the IPv4 or IPv6 address family of the VPN instance. You are allowed to perform VPN configurations in the address family view only after using the route-distinguisher command to configure an RD for the address family;

• configure a VPN target for the IPv4 or IPv6 address family of the VPN instance using the VPN-target command. VPN targets control route learning between VPN instances;

• configure the ipv4-family on the BGP and bind the VPN-Instance;

• bind the VPN instance to a VPN-connected interface on the PE using the ip binding VPN-instance command.

For example, there is one VPN-Instance whose name is blue and we can configure it as per below.

Figure 1-2. Full-mesh VPN configuration example

This would be everything on the full mesh MPLS VPN deployment guide. Hope you enjoyed reading this post!