Implementing Ipv6 Vpn Provider Edge Transport Over Mpls; Overview Of 6Pe/Vpe - Cisco NCS 540 Series Configuration Manual

L3vpn; for ios xr release 6.3.x

Hide thumbs Also See for NCS 540 Series:

Table of Contents

Implementing IPv6 VPN Provider Edge Transport

over MPLS

IPv6 Provider Edge or IPv6 VPN Provider Edge (6PE/VPE) uses the existing MPLS IPv4 core infrastructure

for IPv6 transport. 6PE/VPE enables IPv6 sites to communicate with each other over an MPLS IPv4 core

network using MPLS label switched paths (LSPs).

This feature relies heavily on multiprotocol Border Gateway Protocol (BGP) extensions in the IPv4 network

configuration on the provider edge (PE) router to exchange IPv6 reachability information (in addition to an

MPLS label) for each IPv6 address prefix. Edge routers are configured as dual-stack, running both IPv4 and

IPv6, and use the IPv4 mapped IPv6 address for IPv6 prefix reachability exchange.

Familiarity with MPLS and BGP4 configuration and troubleshooting is required for implementing 6PE/VPE.

•

Multiple techniques are available to integrate IPv6 services over service provider core backbones:

• Dedicated IPv6 network running over various data link layers

• Dual-stack IPv4-IPv6 backbone

• Existing MPLS backbone leverage

These solutions are deployed on service providers' backbones when the amount of IPv6 traffic and the revenue

generated are in line with the necessary investments and the agreed-upon risks. Conditions are favorable for

the introduction of native IPv6 services, from the edge, in a scalable way, without any IPv6 addressing

restrictions and without putting a well-controlled IPv4 backbone in jeopardy. Backbone stability is essential

for service providers that have recently stabilized their IPv4 infrastructure.

OSPFv3 6VPE, on page 57

L3VPN Configuration Guide for Cisco NCS 540 Series Routers, IOS XR Release 6.3.x

C H A P T E R

Table of Contents

Show Quick Links

Table of Contents