R2511-HP MSR Router Series Layer 3 - IP Routing Configuration Guide(V5)

190
4. peer ip-prefix import
5. peer route-policy import
Only routes passing all the configured policies can be received.
To configure BGP route reception filtering policies:
Step Command Remarks
1. Enter system view.
system-view N/A
2. 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 method.
3. Configure BGP route
reception filtering policies.
• Filter incoming routes from all peers
with an ACL or IP prefix list:
filter-policy { acl-number | ip-prefix
ip-prefix-name } import
• Reference a routing policy to filter
routing information from a peer or
peer group:
peer { group-name | ip-address }
route-policy route-policy-name
import
• Reference an ACL to filter routing
information from a peer or peer
group:
peer { group-name | ip-address }
filter-policy acl-number import
• Reference an AS path ACL to filter
routing information from a peer or
peer group:
peer { group-name | ip-address }
as-path-acl as-path-acl-number
import
• Reference an IP prefix list to filter
routing information from a peer or
peer group:
peer { group-name | ip-address }
ip-prefix ip-prefix-name import
Use at least one method.
By default, no route reception
filtering is configured.
Enabling BGP and IGP route synchronization
Routing information synchronization between IBGP and IGP avoids giving wrong directions to routers
outside of the local AS.
By default, upon receiving an IBGP route, a BGP router checks the route's next hop. If the next hop is
reachable, the BGP router advertises the route to EBGP peers. If a non-BGP router works in an AS, it can