Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

prefix-limit

Syntax

Hierarchy Level

Description

Limit the number of prefixes received on a BGP peer session and a rate-limit logging when injected prefixes exceed a set limit.

This functionality is identical to the accepted-prefix-limit functionality except that it operates against received prefixes rather than accepted prefixes.

Options

maximum number—When you set the maximum number of prefixes, a message with peer address, address family and instance name is logged when that number is exceeded.

  • Range: 1 through 4,294,967,295 (232 – 1)

teardown <percentage>—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. 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 you issue a clear bgp neighbor command.

  • Range: 1 through 100

idle-timeout (forever | timeout-in-minutes)—(Optional) If you include the idle-timeout statement, the session is torn down for a specified amount of time, or forever. If you specify a period of time, the session is allowed to reestablish after this timeout period. If you specify forever, the session is reestablished only after you intervene with a clear bgp neighbor command.

  • Range: 1 through 2400

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

Release Information

Statement introduced before Junos OS Release 7.4.