270
Step Command
Remarks
8.
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.
9.
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.
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 only on 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:
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
IBGP peer.
peer
{
group-name
|
ip-address
}
as-number
as-number
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.
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 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
.
Configuring routing between PEs
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view.
bgp
as-number
N/A
3.
Configure the remote PE as
the peer.
peer
{
group-name
|
ip-address
}
as-number
as-number
N/A
4.
Specify the source interface
for route updates.
peer
{
group-name
|
ip-address
}
connect-interface
interface-type
interface-number
By default, BGP uses the source
interface of the optimal route
update packet.