Limiting Prefixes Received From A Peer Or Peer Group - HP MSR Series Configuration Manual

discard a packet due to an unreachable destination. As shown in
of 8.0.0.0/8 from Router D through BGP. Router E then sends a packet to 8.0.0.0/8 through Router D,
which finds from its routing table that Router B is the next hop (configured using the peer next-hop-local
command). Because Router D has learned the route to Router B through IGP, Router D forwards the
packet to Router C through route recursion. Router C does not know the route 8.0.0.0/8, so it discards
the packet.
Figure 57 IBGP and IGP synchronization
For this example, if synchronization is enabled, and the route 8.0.0.0/24 received from Router B is
available in its IGP routing table, Router D advertises the IBGP route when the following conditions are
met:
The next hop of the route is reachable.
•
An active route with the same destination network segment is available in the IGP routing table (use
•
the display ip routing-table protocol command to check the IGP route state).
You can disable the synchronization feature in the following situations:
The local AS is not a transitive AS (AS 20 is a transitive AS in the above figure).
•
Routers in the local AS are IBGP fully meshed.
•
To enable BGP and IGP synchronization:
Step
1. Enter system view.
2. Enter BGP view.
3. Enable synchronization
between BGP and IGP.

Limiting prefixes received from a peer or peer group

This feature can prevent that send a large number of BGP routes to the router.
If the number of routes received from a peer or peer group exceeds the upper limit, the router takes one
of the following actions based on your configuration:
Tear down the BGP session to the peer or peer group.
•
Display an alarm message.
•
Tear down the BGP session to the peer or peer group and, after a specified period of time,
•
reestablishes a BGP session to the peer or peer group.
Command
system-view
bgp as-number
synchronization
191
Figure 57, Router E has learned a route
Remarks
N/A
N/A
Not enabled by default.