R21xx-HP FlexFabric 11900 MPLS Configuration Guide

214
# Start BGP on PE 2.
[PE2] bgp 600
# Configure the capability to advertise labeled routes to IBGP peer 4.4.4.9 and to receive labeled
routes from the peer.
[PE2-bgp] peer 4.4.4.9 as-number 600
[PE2-bgp] peer 4.4.4.9 connect-interface loopback 0
[PE2-bgp] ipv6-family unicast
[PE2-bgp-ipv4] peer 4.4.4.9 enable
[PE2-bgp-ipv4] peer 4.4.4.9 label-route-capability
[PE2-bgp-ipv4] quit
# Configure the maximum hop count from PE 2 to EBGP peer 2.2.2.9 as 10.
[PE2-bgp] peer 2.2.2.9 as-number 100
[PE2-bgp] peer 2.2.2.9 connect-interface loopback 0
[PE2-bgp] peer 2.2.2.9 ebgp-max-hop 10
# Configure peer 2.2.2.9 as a VPNv6 peer.
[PE2-bgp] ipv6-family vpnv6
[PE2-bgp-vpnv6] peer 2.2.2.9 enable
[PE2-bgp-vpnv6] quit
# Redistribute direct routes to the routing table of vpn1.
[PE2-bgp] ip vpn-instance vpn1
[PE2-bgp-vpn1] ipv6-family unicast
[PE2-bgp-ipv6-vpn1] import-route direct
[PE2-bgp-ipv6-vpn1] quit
[PE2-bgp-vpn1] quit
[PE2-bgp] quit
5. Verify the configuration:
# PE 1 and PE 2 can ping each other. Take PE 1 as an example:
[PE1] ping ipv6 -a 2001:1::1 -vpn-instance vpn1 2001:1::2
PING6(104=40+8+56 bytes) 2001:1::1 --> 2001:1::2
56 bytes from 2001:1::2, icmp_seq=0 hlim=64 time=1.000 ms
56 bytes from 2001:1::2, icmp_seq=1 hlim=64 time=0.000 ms
56 bytes from 2001:1::2, icmp_seq=2 hlim=64 time=0.000 ms
56 bytes from 2001:1::2, icmp_seq=3 hlim=64 time=0.000 ms
56 bytes from 2001:1::2, icmp_seq=4 hlim=64 time=0.000 ms
--- 2001:1::2 ping6 statistics ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.000/0.200/1.000/0.400 ms
Configuring IPv6 MPLS L3VPN carrier's carrier
Network requirements
Configure carrier's carrier for the scenario shown in Figure 58. In this scenario:
• PE 1 and PE 2 are the provider carrier's PE switches. They provide VPN services for the customer
carrier.