Carrier-Of-Carriers Using Bgp As The Label Distribution Protocol; Carrier-Of-Carriers Ipv6 Vpns; Figure 109: Carrier-Of-Carrier Ipv6 Vpns - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - BGP AND MPLS CONFIGURATION GUIDE 2010-10-12 Configuration Manual

Software for e series broadband services routers bgp and mpls configuration guide
Hide thumbs Also See for JUNOSE SOFTWARE FOR E SERIES 11.3.X - BGP AND MPLS CONFIGURATION GUIDE 2010-10-12:
Table of Contents

Advertisement

JunosE 11.3.x BGP and MPLS Configuration Guide

Carrier-of-Carriers Using BGP as the Label Distribution Protocol

Carrier-of-Carriers IPv6 VPNs

Figure 109: Carrier-of-Carrier IPv6 VPNs

478
You can run BGP instead of LDP as the label distribution protocol on the PE-CE link
between the Tier 1 and the Tier 2 carriers in a carrier-of-carriers topology. This capability
is available for carriers providing Internet access or VPN service to end users.
Figure 109 on page 478 illustrates a carrier-of-carrier scenario with IPv6 VPNs. MPLS labels
are exchanged on the PE–CE link for customer-internal routes, but customer-external
routes are not imported either into the VRFs on the PE router or into the core. VRFs
maintain a routing table only for the customer-internal routes. Forwarding is accomplished
primarily by label switching, without a routing table lookup.
Only customer-external routes (Tier 2 ISP routes as shown in Figure 109 on page 478) can
be native IPv6 addresses. Because LDP over TCP over IPv6 is not currently supported,
the customer-internal routes for which LDP can give out labels (Tier 1 ISP routes in Figure
109 on page 478) must be IPv4 addresses; they cannot be IPv6 addresses, whether native
or IPv4-mapped.
For more information about carrier-of-carriers VPNs, see "Carrier-of-Carriers IPv4 VPNs"
on page 472 .
Copyright © 2010, Juniper Networks, Inc.

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junose 11.3

Table of Contents