Beginning with JUNOS Release 9.2, you can set a limit to the number of prefixes that can be accepted on a BGP peering session. When that specified limit is exceeded, a system log message is sent. You can also specify to reset the BGP session if the limit to the number of specified prefixes is exceeded.
To configure a limit to the number of prefixes that can be accepted on a BGP peering session, include the accepted-prefix-limit statement:
-
accepted-prefix-limit {
- maximum number;
- teardown <percentage> <idle-timeout
(forever | minutes)>;
- }
For a list of hierarchy levels at which you can include this statement, see the statement summary section for this statement.
For maximum number, specify a value in the range from 1 through 4,294,967,295.
Include the teardown statement to specify to the reset
the BGP peering session when the number of accepted prefixes exceeds
the configured limit. You can also include a percentage value from
1 through 100 to have a system log message sent when the number of
accepted prefixes exceeds that percentage of the maximum limit. By
default a BGP session that is reset is reestablished within a short
time. Include the idle-timeout statement to prevent the BGP
session from being reestablished for a specified period of time. You
can configure a timeout value from 1 through
2400 minutes.
Include the forever option to prevent the BGP session from
being reestablished until you issue the clear bgp neighbor command.
![]() |
Note: When nonstop routing is enabled and a switchover to a backup Routing Engine occurs, BGP peers that are down are automatically restarted. The peers are restarted even if the idle-timeout forever statement is configured. |
![]() |
Note: Alternatively, you can configure a limit to the number of prefixes that can be received on a BGP peering session. For more information, see Limiting the Number of Prefixes Received on a BGP Peering Session. |