BGP Prefix-Limit: Session Teardown

The Prefix Limit features can be used to limit the number of prefixes that can be received on a BGP peer session. When that specified limit is exceeded, a system log message is sent. Optionally, you can also force persistent or temporal teardown of the BGP session, if the limit to the number of specified prefixes is exceeded. You can specify the received prefix limit as a value from 1 through 4,294,967,295. When session teardown is enabled, you can specify a threshold (percentage value from 1 through 100) to have a system log message sent when the number of received prefixes exceeds that percentage of the maximum limit. By default, a BGP session that is reset is reestablished within a short time. Alternatively, you can specify some idle timeout value to prevent the BGP session from being reestablished for a specified period of time, or specify the forever option to prevent the BGP session from being reestablished until the BGP session is manually cleared. This functionality is identical to the accepted prefix limit functionality except that it operates against received prefixes rather than accepted prefixes.