bgp monitoring (check_bgp_neighbors) command syntax assistance

[Marc Powell]

On Oct 6, 2009, at 11:31 AM, Emily wrote:

> Hello, I am attempting to use this check_bgp_neighbors command which  
> was recommended however my manual execution gives this output:
>
> [root at dns libexec]# ./check_bgp_neighbors -H Core-RTR1-MiddleT -C  
> public -n 157.130.57.129 -n 65.205.26.197
> Error in packet
> Reason: (noSuchName) There is no such variable name in this MIB.
> Failed object: .1.3.6.1.4.1.9.9.187.1.2.4.1.1.157.130.57.129.1.1
> expr: syntax error
> Error in packet
> Reason: (noSuchName) There is no such variable name in this MIB.
> Failed object: .1.3.6.1.4.1.9.9.187.1.2.4.1.1.65.205.26.197.1.1
> expr: syntax error
> ./check_bgp_neighbors: line 107: [: -ge: unary operator expected
> Failed: status:12 prefixes: sent:1466115 received:1475079[root at dns  
> libexec]#
> [root at dns libexec]#
> perhaps my syntax is flawed as I don't know why I am getting this  
> "Failed object" error, the usage of the command is below, I would  
> really appreciate any help with my syntax for the above command:

I just played around with the script. Try running it again. I saw  
similar errors on the first run but subsequent runs were better (it  
creates a temp file to keep track of sends/receives). It also expects  
at least 2 minutes (and possibly 5 minutes) between runs in order to  
see sufficient messages sent/received.

--
Marc


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null