223
To do…
Use the command…
Remarks
Configure BGP to filter received
routes
filter-policy
{
acl-number
|
ip-prefix
ip-prefix-name
}
import
Optional
By default, BGP does not filter
received routes.
NOTE:
•
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.
•
You can execute the
reflect between-clients
command and the
reflector cluster-id
command in multiple
views, such as BGP-VPN instance view and BGP-VPNv4 subaddress family view. The two commands
take effect for only the RR in the view where they are executed. For RRs in other views, they do not take
effect.
•
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 of the route.
2.
Configure the CE
To configure the CE:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Enter BGP view
bgp
as-number
—
Configure the PE as the iBGP peer
peer
{
group-name
|
ip-address
}
as-number
as-number
Required
Configure route redistribution
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 that the PE can
advertise them to the peer CE.
NOTE:
•
Exchange of BGP routes of 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 BGP peer group configuration, see
Layer 3—IP Routing
Configuration Guide. This chapter does not differentiate between peer and peer group.
Configuring routing between PEs
Perform the following configurations on PEs.
To configure routing between PEs:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Enter BGP view
bgp
as-number
Required
