HPE FlexFabric 5950 Series Configuration Manual page 216

Step
8. Filter routes received from or
advertised to a peer or peer
group based on an AS_PATH
list.
9. Advertise a default VPN
route to a peer or peer group.
10. Apply an ACL to filter routes
received from or advertised
to a peer or peer group.
11. Save all route updates from a
peer or peer group.
12. Specify the device as the
next hop of routes sent to a
peer or peer group.
13. Configure BGP to not
change the next hop of
routes sent to a peer or peer
group.
14. Set a preferred value for
routes received from a peer
or peer group.
15. Apply a prefix list to filter
routes received from or
advertised to a peer or peer
group.
16. Configure BGP updates
advertised to an EBGP peer
or peer group to carry only
public AS numbers.
17. Configure the device as an
RR and specify a peer or
peer group as its client.
18. Set the maximum number of
routes BGP can receive from
a peer or peer group.
19. Apply a routing policy to a
peer or peer group.
20. Enable route target filtering
of received VPNv4 routes.
Command
peer { group-name | ipv4-address
[ mask-length ] } as-path-acl
as-path-acl-number { export |
import }
peer { group-name | ipv4-address
[ mask-length ] }
default-route-advertise
vpn-instance vpn-instance-name
peer { group-name | ipv4-address
[ mask-length ] } filter-policy
ipv4-acl-number { export |
import }
peer { group-name | ip-address
[ mask-length ] } keep-all-routes
peer { group-name | ipv4-address
[ mask-length ] } next-hop-local
peer { group-name | ipv4-address
[ mask-length ] }
next-hop-invariable
peer { group-name | ipv4-address
[ mask-length ] } preferred-value
value
peer { group-name | ipv4-address
[ mask-length ] } prefix-list
prefix-list-name { export |
import }
peer { group-name | ipv4-address
[ mask-length ] } public-as-only
peer { group-name | ipv4-address
[ mask-length ] } reflect-client
peer { group-name | ipv4-address
[ mask-length ] } route-limit
prefix-number [ { alert-only |
discard | reconnect
reconnect-time } |
percentage-value ] *
peer { group-name | ipv4-address
[ mask-length ] } route-policy
route-policy-name { export |
import }
policy vpn-target
208
Remarks
By default, no AS filtering list is
applied to a peer or peer group.
By default, no default VPN route is
advertised to a peer or peer
group.
By default, no ACL-based filtering
is configured.
By default, BGP does not save
route updates from any peer.
By default, the device sets itself
as the next hop for routes sent to
a peer or peer group.
By default, the device sets itself
as the next hop for routes sent to
a 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 BGP peers and
clients.
By default, the preferred value is
0.
By default, no prefix list based
filtering is configured.
By default, BGP route updates
advertised to an EBGP peer or
peer group can carry both public
and private AS numbers.
By default, no RR is configured.
By default, the number of routes
that BGP can receive from a peer
or peer group is not limited.
By default, no routing policy is
applied to a peer or peer group.
By default, route target filtering is
enabled for received VPNv4
routes. Only VPNv4 routes whose