From fce4bc65e9c066cc5a103ce7b127a6fb5a35c412 Mon Sep 17 00:00:00 2001 From: thl-cmk <thl-cmk@outlook.com> Date: Wed, 29 Apr 2020 19:36:36 +0100 Subject: [PATCH] Update cisco_bgp_peer --- checkman/cisco_bgp_peer | 27 +++++++++++++++++++-------- 1 file changed, 19 insertions(+), 8 deletions(-) diff --git a/checkman/cisco_bgp_peer b/checkman/cisco_bgp_peer index 678dec2..b54de43 100644 --- a/checkman/cisco_bgp_peer +++ b/checkman/cisco_bgp_peer @@ -4,16 +4,27 @@ catalog: hw/network/cisco license: GPL distribution: https://thl-cmk.hopto.org description: - Monitors the status of BGP peers. It has support for IPv4/IPv6, more then one - address family per BGP peer. + Monitors the status of BGP peers. It supports IPv4/IPv6 peers and more then one + address family per BGP peer. + critical: + - if peer state is "idle" or adminstate is not "start" - warning: if peer state is not "established" or peer is not up long enough - Describe here: (1) what the check actually does, (2) under which - circumstances it goes warning/critical, (3) which devices are supported - by the check, (4) if the check requires a separated plugin or - tool or separate configuration on the target host. - + + - if accepted prefixes equal or above prefix admin limit + + warning: + + - if peer state is not "established" or peer is not up long enough + + - if accepted prefixes equal or above warn threshold + + This check is tested with a variaity of Cisco ASR and ISR routers. + + The "prefix admin limit" and "warn threshold" needs to be configured on the device. + For example: neighbor 172.17.10.10 maximum-prefix 10000 80. The threshold is in + percentage of the prefix limit . + item: Is build from the Address family and IP address of the BGP peer. For example "172.17.10.10 IPv4 Unicast" -- GitLab