diff --git a/checkman/cisco_bgp_peer b/checkman/cisco_bgp_peer
index 678dec24e7e3ea6439aacc92018debc8a6ced32f..b54de4350e34801e61bb60921cb406c18601bb17 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"