[Contents] [Prev] [Next] [Index] [Report an Error]

Limiting the Number of Prefixes Received on a BGP Peering Session

You can limit the number of prefixes received on a BGP peering session, and log rate-limited messages when the number of injected prefixes exceeds a set limit. You can also tear down the peering when the number of prefixes exceeds the limit.

To configure a limit to the number of prefixes that can received on a BGP session, include the prefix-limit statement:




prefix-limit {
maximum number;
teardown <percentage> <idle-timeout
(forever | minutes)>;
}

For a list of hierarchy levels at which you can configure 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. When the specified maximum number of prefixes is exceeded, a system log message is sent.

If you include the teardown statement, the session is torn down when the maximum number of prefixes is exceeded. If you specify a percentage, messages are logged when the number of prefixes exceeds that percentage of the specified maximum limit. After the session is torn down, it is reestablished in a short time (unless you include the idle-timeout statement). Then the session can be kept down for a specified amount of time, or forever. If you specify forever, the session is reestablished only after the you issue a clear bgp neighbor command.

Note: Beginning with JUNOS Release 9.2, you can alternatively configure a limit to the number of prefixes that can accepted on a BGP peering session. For more information, see Limiting the Number of Prefixes Accepted on a BGP Peering Session.

[Contents] [Prev] [Next] [Index] [Report an Error]