222
NOTE:
•
Exchange of BGP routes for a VPN instance is the same as that of ordinary BGP routes.
•
The BGP configuration task in BGP-VPN instance view is the same as that in BGP view. For more
information, see
Layer 3—IP Routing Configuration Guide.
•
For information about BGP peer and peer group configuration, see
Layer 3—IP Routing Configuration
Guide. This chapter does not differentiate between peer and peer group.
Configuring iBGP between PE and CE
NOTE:
iBGP can be used between PE and CE devices in only common MPLS L3VPN networks. In networks such as
Extranet, inter-AS VPN, carrier’s carrier, nested VPN, and HoVPN, you cannot use iBGP between PE and
CE devices.
1.
Configure the PE
To configure iBGP between PE and CE:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Enter BGP view
bgp
as-number
—
Enter BGP VPN instance view
ipv4-family vpn-instance
vpn-instance-name
Required
Configure the CE as the VPN iBGP
peer
peer
{
group-name
|
ip-address
}
as-number
as-number
Required
Configure the system to be the RR
and specify the CE as the client of
the RR
peer
{
group-name
|
ip-address
}
reflect-client
Optional
By default, no RR or RR client is
configured.
Enable route reflection between
clients
reflect between-clients
Optional
Enabled by default.
If the clients are fully meshed, you
do not need to enable route
reflection.
Configure the cluster ID for the RR
reflector cluster-id
{
cluster-id
|
ip-address
}
Optional
By default, each RR in a cluster uses
its own router ID as the cluster ID.
If more than one RR exists in a
cluster, use this command to
configure the same cluster ID for all
RRs in the cluster to avoid routing
loops.
Configure BGP to filter routes to be
advertised
filter-policy
{
acl-number
|
ip-prefix
ip-prefix-name
}
export
[
direct
|
isis
process-id
|
ospf
process-id
|
rip
process-id
|
static
]
Optional
By default, BGP does not filter
routes to be advertised.
