Prefix Withdrawal
This alarm detects when a peer withdraws a prefix.
The withdrawal of a prefix from a few BGP peers does not necessarily mean that the prefix is unreachable since there are multiple paths to reach a prefix. However, if a large enough number of peers withdraw off the prefix in a geographical area, the reachability of the prefix can be degraded. It is recommended that thresholds for this alarm are set higher than other alarms to suppress noise caused by router flap.
 Note |
It is useful to know which of your peers may be doing something wrong (leaking route information or having some type of misconfiguration) so that you can address the problem right away. A My Peers rule is available for this alarm with certain Crosswork Cloud subscriptions. The My Peers option follows BGP updates only from your peers, whereas All Peers follow BGP updates from your peers and global peers. To configure this option, see Add Crosswork Cloud Network Insights Policies. |
Possible Problem Detected
This alarm can help identify a misconfiguration resulting in prefix withdrawal.
Relevant Alarm Rule Configurations
The following options must be configured when adding this alarm rule to a Prefix policy configuration (External Routing Analysis > Configure > Policies > Add Policy > Prefix Policy > Add Rule > Prefix Withdrawal):
Feedback