353
{
Configure BGP as the PE-CE routing protocol, and redistribute routes of the CEs into the
PEs.
For more information about basic IPv6 MPLS L3VPN configurations, see "
851H
Configuring IPv6
MPLS L3VPNs
."
# Execute the
display ipv6 routing-table
command on CE 2 to verify that CE 2 has not learned
the route to the VPN (100::/96) behind CE 1.
<CE2> display ipv6 routing-table
Destinations : 6 Routes : 6
Destination: ::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 10:2::/96 Protocol : Direct
NextHop : :: Preference: 0
Interface : Vlan-int12 Cost : 0
Destination: 10:2::2/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 200::/96 Protocol : Static
NextHop : :: Preference: 60
Interface : NULL0 Cost : 0
Destination: FE80::/10 Protocol : Direct
NextHop : :: Preference: 0
Interface : NULL0 Cost : 0
Destination: FF00::/8 Protocol : Direct
NextHop : :: Preference: 0
Interface : NULL0 Cost : 0
# Execute the
display ipv6 routing-table
command on CE 1 to verify that CE 1 has not learned
the route to the VPN behind CE 2. (Details not shown.)
# Execute the
display ipv6 routing-table vpn-instance
command on the PEs. The output
shows the route to the VPN behind the peer CE. This example uses PE 2.
<PE2> display ipv6 routing-table vpn-instance vpn1
Destinations : 7 Routes : 7
Destination: ::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 10:2::/96 Protocol : Direct
NextHop : :: Preference: 0
Interface : Vlan-int12 Cost : 0