182
Configuring BGP VPNv4 route control
BGP VPNv4 route control is configured similarly with BGP route control, except that it is configured in
BGP VPNv4 address family view. For detailed information about BGP route control, see
Layer 3—IP
Routing Configuration Guide.
To configure BGP VPNv4 route control:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view.
bgp as-number
N/A
3.
Enter BGP VPNv4 address
family view.
address-family vpnv4
N/A
4.
Configure filtering of
advertised routes.
filter-policy
{
acl-number
|
prefix-list
prefix-list-name
}
export
[
protocol process-id
]
By default, BGP does not filter
advertised routes.
5.
Configure filtering of
received routes.
filter-policy
{
acl-number
|
prefix-list
prefix-list-name
}
import
By default, BGP does not filter
received routes.
6.
Advertise community
attributes to a peer or peer
group.
peer
{
group-name
|
ip-address
[
mask-length
]
}
advertise-community
By default, no community
attributes are advertised to any
peer or peer group.
7.
Allow the local AS number to
appear in the AS_PATH
attribute of routes received
from the peer, and set the
maximum number of
repetitions.
peer
{
group-name
|
ip-address
[
mask-length
] }
allow-as-loop
[
number
]
By default, BGP discards route
updates that contain the local AS
number.
8.
Filter routes received from or
advertised to a peer or peer
group based on an AS_PATH
list.
peer
{
group-name
|
ip-address
[
mask-length
] }
as-path-acl
as-path-acl-number
{
export
|
import
}
By default, no AS filtering list is
applied to a peer or peer group.
9.
Advertise a default VPN
route to a peer or peer group.
peer
{
group-name
|
ip-address
[
mask-length
]
}
default-route-advertise
vpn-instance
vpn-instance-name
By default, no default VPN route is
advertised to a peer or peer
group.
10.
Apply an ACL to filter routes
received from or advertised
to a peer or peer group.
peer
{
group-name
|
ip-address
[
mask-length
] }
filter-policy
acl-number
{
export
|
import
}
By default, no ACL-based filtering
is configured.
11.
Save all route updates from a
peer or peer group.
peer
{
group-name
|
ip-address
[
mask-length
] }
keep-all-routes
By default, BGP does not save
route updates from any peer.
12.
Specify the router as the next
hop of routes sent to a peer
or peer group.
peer
{
group-name
|
ip-address
[
mask-length
] }
next-hop-local
By default, the router sets itself as
the next hop for routes sent to a
peer or peer group.
13.
Configure BGP
to not
change the next hop of
routes sent to an EBGP peer
or peer group.
peer
{
group-name
|
ip-address
[
mask-length
]
}
next-hop-invariable
By default, the router sets itself as
the next hop for routes sent to an
EBGP peer or peer group.
In an inter-AS option C network
where an RR is used to advertise
VPNv4 routes, configure this
command on the RR so the RR
does not change the next hop of
routes sent to EBGP peers and
clients.
Содержание FlexNetwork 5510 HI Series
Страница 9: ...vii Remote support 460 Documentation feedback 460 Index 462 ...
Страница 318: ...309 Request list 0 Retransmit list 0 ...
Страница 363: ...354 Verify that CE 1 and CE 2 can ping each other Details not shown ...
Страница 446: ...437 The MCE has redistributed the OSPF routes of the two VPN instances into the EBGP routing tables of PE 1 ...