HPE FlexFabric 5950 Series Configuration Manual page 316

C onfiguring IBGP between a PE and a CE
5 2 7 B
Use IBGP between PE and CE only in a basic IPv6 MPLS L3VPN network. In networks such as
inter-AS VPN and carrier's carrier, you cannot configure IBGP between PE and CE.
1. Configure the PE:
Step
1. Enter system view.
2. Enter BGP instance view.
3. Enter BGP-VPN instance
view.
4. Configure the CE as the
VPN IBGP peer.
5. Create the BGP-VPN IPv6
unicast family and enter its
view.
6. Enable IPv6 unicast route
exchange with the
specified peer.
7. Configure the CE as a
client of the RR.
8. (Optional.) Enable route
reflection between clients.
9. (Optional.) Configure the
cluster ID for the RR.
2. Configure the CE:
Command
system-view
bgp as-number [ instance
instance-name ]
[ multi-session-thread ]
ip vpn-instance
vpn-instance-name
peer { group-name |
ipv6-address [ prefix-length ] }
as-number as-number
address-family ipv6 [ unicast ]
peer { group-name |
ipv6-address [ prefix-length ] }
enable
peer { group-name |
ipv6-address [ prefix-length ] }
reflect-client
reflect between-clients
reflector cluster-id { cluster-id |
ip-address }
308
Remarks
N/A
N/A
Configuration commands in
BGP-VPN instance view are the
same as those in BGP instance
view. For more information, see
Layer 3—IP Routing
Configuration Guide.
By default, no BGP peers exist.
By default, the BGP-VPN IPv6
unicast family is not created.
By default, BGP does not
exchange IPv6 unicast routes
with any peer.
By default, no RR or RR client is
configured, and the PE does not
advertise routes learned from
the IBGP peer CE to other IBGP
peers, including VPNv6 IBGP
peers. The PE advertises routes
learned from the CE to other
IBGP peers only when you
configure the IBGP peer CE as
a client of the RR.
Configuring an RR does not
change the next hop of a route.
To change the next hop of a
route, configure an inbound
policy on the receiving side.
By default, route reflection
between clients is enabled.
By default, the RR uses its own
router ID as the cluster ID.
If multiple RRs exist in a cluster,
use this command to configure
the same cluster ID for all RRs
in the cluster to avoid routing
loops.