256
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view.
bgp
as-number
N/A
3.
Configure the PE as the EBGP
peer.
peer
{
group-name
|
ip-address
}
as-number
as-number
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.
4.
Configure the route
redistribution and
advertisement behavior.
import-route
protocol
[
process-id
]
[
med
med-value
|
route-policy
route-policy-name
] *
Optional.
A CE must advertise its routes to the
connected PE so the PE can
advertise them to the peer CE.
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.
Configuring IBGP between PE and CE
Use IBGP between PE and CE devices in only common MPLS L3VPN network. 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:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view.
bgp
as-number
N/A
3.
Enter BGP VPN instance view.
ipv4-family vpn-instance
vpn-instance-name
N/A
4.
Configure the CE as the VPN
IBGP peer.
peer
{
group-name
|
ip-address
}
as-number
as-number
N/A
5.
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.
By default, a PE does not advertise
routes learned from IBGP peer CEs
to IBGP peers, including VPNv4
IBGP peers. Only when you
configure an IBGP peer CE as a
client of the RR, does the PE
advertise routes learned from it to
other IBGP peers.
