Configuring Route Exchange Between a Hub-PE and a Spoke-PE

By importing extended community attributes to BGP, MP-IBGP can advertise VPNv6 routes between PEs.

Context

MP-IBGP peer relationships need be established between the Hub-PE and each Spoke-PE. Spoke-PEs need not exchange routes directly and therefore they do not need to establish MP-IBGP peer relationships.

Perform the following steps on the Hub-PE and all the Spoke-PEs:

Procedure

Run system-view
The system view is displayed.
Run bgp as-number
The BGP view is displayed.
Run peer peer-address as-number as-number
The remote PE is configured as a BGP peer.
Run peer peer-address connect-interface loopback interface-number
The interface used to establish a TCP connection is specified.

PEs must use the loopback interface addresses with 32-bit masks to establish an MP-IBGP peer relationship so that routes can recurse to the tunnel. The route to the loopback interface is advertised to the peer PE through IGP on the MPLS backbone network.
Run ipv6-family vpnv6 [unicast]
The BGP-VPN IPv6 address family view is displayed.
Run peer peer-address enable
The capability of exchanging BGP VPNv6 routing information with the peer is enabled.
Run commit
The configuration is committed.