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


prefix-limit

Syntax

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

Hierarchy Level

[edit protocols bgp family inet (any | multicast | unicast)],
[edit protocols bgp group group-name family inet (any | multicast | unicast)],
[edit protocols bgp group group-name neighbor address
    family inet (any | multicast | unicast)],
[edit routing-instances
routing-instance-name protocols bgp family inet
    (any
 | multicast | unicast)],
[edit routing-instances routing-instance-name protocols bgp group group-name family inet
    (any | multicast | unicast)]
,
[edit routing-instances routing-instance-name protocols bgp group group-name
    
neighbor address  family inet (any | multicast | unicast)]

Description

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

Options

maximum number—When you set the maximum number of prefixes, a message is logged when that number is reached.
Range: 1 through 4,294,967,295

teardown <percentage>—If you include the teardown statement, the session is torn down when the maximum number of prefixes is reached. If you specify a percentage, messages are logged when the number of prefixes reaches that percentage. Once the session is torn down, it will reestablish 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: 0 through 100

idle-timeout (forever | timeout-in-minutes)—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 will be reestablished only after you intervene with a clear bgp neighbor command.
Range: 0 through 2400

Usage Guidelines

See Enable Multiprotocol BGP.

Required Privilege Level

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


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