H3C Technologies H3C SR8800 - Manual (Page 232)

216
Step Command Remarks
3. Configure BGP route
reception filtering policies.
• Filter incoming routes with an
ACL or IP prefix list:
filter-policy { acl-number |
ip-prefix ip-prefix-name }
import
• Reference a routing policy to
filter routes from a peer/peer
group:
peer { group-name |
ip-address } route-policy
route-policy-name import
• Reference an ACL to filter
routing information from a
peer/peer group:
peer { group-name |
ip-address } filter-policy
acl-number import
• Reference an AS path ACL to
filter routing information from
a peer/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/peer group:
peer { group-name |
ip-address } ip-prefix
ip-prefix-name import
Configure at least one command.
By default, no route reception
filtering is configured.
If several filtering policies are
configured, they are applied in the
following sequence:
4. filter-policy import
5. peer filter-policy import
6. peer as-path-acl import
7. peer ip-prefix import
8. peer route-policy import
Only routes passing all the
configured policies can be received.
Enabling BGP and IGP route synchronization
By default, when a BGP router receives an IBGP route, it only checks the reachability of the route’s next
hop before advertisement. With BGP and IGP synchronization enabled, the BGP router cannot advertise
the IBGP route to EBGP peers unless the route is also available in the IGP routing table.
To enable BGP and IGP synchronization:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter BGP view. bgp as-number N/A
3. Enable synchronization
between BGP and IGP.
synchronization Not enabled by default
Limiting prefixes received from a peer/peer group
To configure the maximum number of prefixes allowed to be received from a peer/peer group: