F3726, F3211, F3174, R5135, R3816-HP Firewalls and UTM Devices Network Management Configuration Guide-6PW100

480
{ peer ip-prefix export
{ peer route-policy export
Only routes passing the first policy can go to the next, and only routes passing all the configured
policies can be advertised.
To configure BGP route distribution filtering policies:
Ste
p
Command Remarks
512. Enter system view. system-view N/A
513. Enter BGP view or
BGP-VPN instance
view.
• Enter BGP view:
bgp as-number
• Enter BGP-VPN instance view:
a. bgp as-number
b. ipv4-family vpn-instance
vpn-instance-name
Use either approach.
514. Configure BGP route
distribution filtering
policies.
• Configure the filtering of redistributed routes
advertised to all peers:
filter-policy { acl-number | ip-prefix
ip-prefix-name } export [ direct | isis
process-id | ospf process-id | rip process-id |
| static ]
• Reference a routing policy to filter
advertisements to a peer or peer group:
peer { group-name | ip-address } route-policy
route-policy-name export
• Reference an ACL to filter advertisements to a
peer or peer group:
peer { group-name | ip-address } filter-policy
acl-number export
• Reference an AS path list to filter routing
information sent to a peer or peer group:
peer { group-name | ip-address } as-path-acl
as-path-acl-number export
• Reference an IP prefix list to filter routing
information sent to a peer or peer group:
peer { group-name | ip-address } ip-prefix
ip-prefix-name export
Use at least one approach.
Not configured by default.
Support for the isis process-id
option depends on the device
model. For more information,
see Network Management
Command Reference.
3. Configuring BGP route reception filtering policies
You can use the following methods to configure BGP route reception filtering policies:
{ Use ACL or IP prefix list to filter routing information received by all peers.
{ Use routing policy, ACL, AS path list, or IP prefix list to filter routing information received by the
specified peer or peer group.
If several filtering policies are configured, they are applied in the following sequence:
a. filter-policy import
b. peer filter-policy import
c. peer as-path-acl import
d. peer ip-prefix import
e. peer route-policy import