Rate and give feedback:
Feedback Received. Thank You!
accepted-prefix-limit
Syntax
accepted-prefix-limit {maximum number;teardown <percentage-threshold> idle-timeout (forever | minutes);}
Hierarchy Level
[edit logical-systems logical-system-name protocols bgp family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)],[edit logical-systems logical-system-name protocols bgp family route-target],[edit logical-systems logical-system-name protocols bgp group group-name family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)],[edit logical-systems logical-system-name protocols bgp group group-name family route-target],[edit logical-systems logical-system-name protocols bgp group group-name neighbor address family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)],[edit logical-systems logical-system-name protocols bgp group group-name neighbor address family route-target],[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)],[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp family route-target],[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)],[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name family route-target],[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)],[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp group group-name neighbor address family route-target],[edit protocols bgp family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)],[edit protocols bgp family route-target],[edit protocols bgp group group-name family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)],[edit protocols bgp group group-name family route-target],[edit protocols bgp group group-name neighbor address family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)],[edit protocols bgp group group-name neighbor address family route-target],[edit routing-instances routing-instance-name protocols bgp family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)],[edit routing-instances routing-instance-name protocols bgp family route-target],[edit routing-instances routing-instance-name protocols bgp group group-name family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)],[edit routing-instances routing-instance-name protocols bgp group group-name family route-target],[edit routing-instances routing-instance-name protocols bgp group group-name neighbor address family (inet | inet6) (any | flow | labeled-unicast | multicast | unicast)],[edit routing-instances routing-instance-name protocols bgp group group-name neighbor address family route-target]
Release Information
Statement introduced in Junos OS Release 9.2.
Statement introduced in Junos OS Release 9.2 for EX Series switches.
Description
Configure a limit to the number of prefixes that
can be accepted on a BGP peer session. When that limit is exceeded,
a system log message is sent. You can optionally specify to reset
the BGP session when the number of accepted prefixes exceeds the specified
limit.
This statement provides the ability to log a message, reset
the BGP session, or do both when the number of prefixes received from
the peer and accepted by policy exceeds a preset limit. This functionality
is identical to the prefix-limit functionality except that
it operates against accepted prefixes rather than received prefixes.
Options
maximum number—When you set the maximum number of prefixes, a message is
logged when that number is exceeded.
Range: 1 through 4,294,967,295 (232 – 1)
teardown <percentage>—(Optional)
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 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.
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.
Required Privilege Level
routing—To view this statement in the
configuration.
routing-control—To add this statement to the configuration.
Published: 2013-06-10
