tenant.bgp_peer_prefix_policy¶
The peer prefix policy defines how many prefixes can be received from a neighbor and the action to take when the number of allowed prefixes is exceeded. This feature is commonly used for external BGP peers, but can also be applied to internal BGP peers.
ACI class |
|
RN |
|
Cursor |
|
Parent |
|
Atomic |
— |
Attributes¶
Accepted as keyword arguments of .bgp_peer_prefix_policy(name) and of .set(**attrs) on this cursor. Enum parameters also accept the plain string.
parameter |
wire |
type |
values |
default |
description |
|---|---|---|---|---|---|
|
|
|
— |
— |
The peer prefix policy name. This name can be up to 64 alphanumeric characters. |
|
|
|
|
Action to be performed when the maximum prefix limit is reached. |
|
|
|
|
— |
— |
Specifies a description of the policy definition. |
|
|
|
— |
|
Maximum number of prefixes allowed from the peer. |
|
|
|
— |
— |
The key for enabling clients to own their data for entity correlation. |
|
|
|
— |
— |
A tag for enabling clients to add their own data. For example, to indicate who created this object. |
|
|
|
— |
|
The period of time in minutes before restarting the peer when the prefix limit is reached. |
|
|
|
— |
|
The threshold percentage of the maximum number of prefixes before a warning is issued. For example, if the maximum number of prefixes is 10 and the threshold is 70%, a warning is issued when the number of prefixes exceeds 7 (70%). |