400-101: MPLS Concepts, Part II
MPLS L3VPNs
- MPLS L3VPNs allow ISPs to providate private Layer 3 services for their customers.
- MPLS L3VPNs are aware of the IP addressing at customer locations.
- At the same time, different customers can have overlapping IP address spaces.
- The concept of using multiple routing tables, called Virtual Routing and Forwarding (VRF) tables, separate customer routes, allowing duplicate address ranges.

- Routers have different roles in MPLS VPNs.
- Customer Edge (CE): A router that is not MPLS aware. Does not send any labeled packets, only peers with the PE router.
- Provider Edge (PE): An entry point into the MPLS network. Adds labels to packets received from the CE. Connects to multiple CEs and segregates their routes using VRFs.
- Provider (P): An LSR in the MPLS core. Fowards packets based on labels only. Does not know or care about customer VPN routes.
- CEs exchange routes with the PE using a routing protocol.
- The PE stores the routes in separate per-customer VRFs.
- The PE redistributes those routes into iBGP and exchanges those routes with other PEs.
- The routes are never advertised to P routers.
- The ingress PE pushes two labels on the packet:
- An outer MPLS header (S-bit = 0): a label to forward the packet towards the far-end PE.
- An inner MPLS header (S-bit = 1): a label to identify the VPN.
General MPLS VPN Traffic Flow
- CE1 forwards an unlabeled packet to PE1.
- PE1 receives the packet on an interface assigned to VRF-A and makes a routing decision based on VRF-A's forwarding tables. PE1 adds two labels and forwards the labeled packets.
- P1 processes the labeled packet and swaps the top label.
- P2 receives the labeled packet, pops the top label (penultimate hop pop) and sends the packet to PE2.
- Based on the VPN label, PE2 knows that the packet belongs to VRF-A. PE2 removes the label and forwards the packet unlabeled to CE2.
- Extranet (route leaking) means importing routes from one VRF into a different VRF that servies another VPN site.
MPLS VPLS
- Virtual Private LAN Service (VPLS) emulates a LAN segment across the MPLS backbone.
- When the customer with different Ethernet sites connects to an MPLS backbone where VPLS is deployed, it appears as if all the sites are interconnected through a virtual Ethernet switch.
- VPLS is the same as EoMPLS, as in it is a Layer 2 domain.
- However, EoMPLS is a service that is point-to-point in nature, whereas VPLS—emulating a LAN—is point-to-multipoint in nature.
Any Transport over MPLS (AToM)
- AToM provides a solution whereby the MPLS backbone also carries the Layer 2 traffic from the customers, thereby eliminating the need to run two separate networks side by side.
- The service provider can provide an existing service (ATM, Frame Relay, and so on) over the MPLS backbone.
- Customers might not want to migrate to MPLS VPNs for two reasons: 1) they want to retain complete control over their network and how it is built, and 2) they have legacy equipment running protocols that cannot be carried over IP.
- Whereas MPLS VPN provides a service of creating VPNs at Layer 3, AToM creates VPNs at Layer 2 and is sometimes referred to as L2VPN.
- AToM is a Layer 2 point-to-point service.
- Benefits of AToM:
- The customer does not need to change anything (no need for a routing protocol like with MPLS L3VPNs).
- The service provider does not have to change anything on the P routers in the MPLS core. The intelligence to support AToM sits entirely on the PE routers.
L2TPv3
- L2TPv3 is the Layer 2 transport service over an IP network.
- The Layer 2 frames are encapsulated with an L2TPv3 header and are transported across the IP network.
- Similar to AToM, L2TPv3 can carry ATM, Frame Relay, HDLC, PPP, Ethernet, and others.
- Both the AToM and L2TPv3 solutions use the same architecture, but the network that is carrying the service is different. AToM is carried over MPLS, L2TPv3 is carried over IP.
- The Layer 2 frames are either encapsulated into an IP packet (L2TPv3) or are labeled (AToM).
Overlay Transport Virtualization (OTV)
- OTV allows for live migration of virtual machines between sites, the process being completely transparent to the end users.
- A typical requirement for live migration is that the host machines are in the same IP subnet and the same VLAN. OTV extends the Layer 2 domain across data centers.
- In essence, OTV accomplishes the same goal as other L2 tunneling protocols such as L2TPv3, AToM, and VPLS. For OTV specifically, the goal is to take Ethernet frames from an end station, like a virtual machine, encapsulate them inside IPv4, transport them over the Data Center Interconnect (DCI) network, decapsulate them on the other side, and out pops the original Ethernet frame.
- OTV benefits over AToM and VPLS:
- Transport agnostic: As long as there is IPv4 connectivity between the data centers, OTV can be used. AToM and VPLS require MPLS.
- Simple provisioning: OTV is a CE side protocol. AToM and VPLS are PE side protocols.
- OTV is an encapsulation nightmare: ICMP over IP over Ethernet over MPLS over GRE over IP over Ethernet (IoIoEoMPLSoGREoIP for short).
- As a summary, OTV is a fancy GRE tunnel.
No comments:
Post a Comment