308
527B
Configuring IBGP between a PE and a CE
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 Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP instance view.
bgp
as-number
[
instance
instance-name
]
[
multi-session-thread
]
N/A
3.
Enter BGP-VPN instance
view.
ip vpn-instance
vpn-instance-name
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.
4.
Configure the CE as the
VPN IBGP peer.
peer
{
group-name
|
ipv6-address
[
prefix-length
] }
as-number
as-number
By default, no BGP peers exist.
5.
Create the BGP-VPN IPv6
unicast family and enter its
view.
address-family ipv6
[
unicast
]
By default, the BGP-VPN IPv6
unicast family is not created.
6.
Enable IPv6 unicast route
exchange with the
specified peer.
peer
{
group-name
|
ipv6-address
[
prefix-length
] }
enable
By default, BGP does not
exchange IPv6 unicast routes
with any peer.
7.
Configure the CE as a
client of the RR.
peer
{
group-name
|
ipv6-address
[
prefix-length
] }
reflect-client
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.
8.
(Optional.) Enable route
reflection between clients.
reflect between-clients
By default, route reflection
between clients is enabled.
9.
(Optional.) Configure the
cluster ID for the RR.
reflector cluster-id
{
cluster-id
|
ip-address
}
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.
2.
Configure the CE: