Search found 9 matches
- Mon Mar 18, 2013 6:02 pm
- Forum: Nagios XI
- Topic: IPSLA -- To monitor more than one probes
- Replies: 16
- Views: 5963
Re: IPSLA -- To monitor more than one probes
[root@c1ecn-nagios1 libexec]# ./check_csco_ipsla.pl -H 1.1.1.1 -c XXXXXX -i ALL IP SLA status: OK | Total-Time=471 IP SLA 10 # HTTP ( http ) status: OK IP SLA 100 # ping ( echo ) status: OK IP SLA 15 # jitter ( udp-jitter ) status: OK | HTTP=410 ping=16 jitter=45 Please disregard the name of the plu...
- Mon Mar 18, 2013 12:59 am
- Forum: Nagios XI
- Topic: IPSLA -- To monitor more than one probes
- Replies: 16
- Views: 5963
Re: IPSLA -- To monitor more than one probes
Hi guys, Now I am using the pluggin which is in Nagios Exchange and i am still having some issues with it. When i run it as a service i can see all the statistics and also all the performance graphs but when i run it as host i can see all the statistics but in term of performance graph i can only se...
- Thu Mar 14, 2013 4:07 pm
- Forum: Nagios XI
- Topic: IPSLA -- To monitor more than one probes
- Replies: 16
- Views: 5963
Re: IPSLA -- To monitor more than one probes
yes i have used which scott mentioned earlier but it is not showing me the graph, using -ALL argument
- Thu Mar 14, 2013 2:22 pm
- Forum: Nagios XI
- Topic: IPSLA -- To monitor more than one probes
- Replies: 16
- Views: 5963
Re: IPSLA -- To monitor more than one probes
I have used the one which is Nagios exchange but again because it only support -ALL argument i was not able to see any diagram/chart. To run individual IPSLA i had to use this Pluggin https://www.monitoringexchange.org/inve ... monitoring
- Wed Mar 13, 2013 5:41 pm
- Forum: Nagios XI
- Topic: IPSLA -- To monitor more than one probes
- Replies: 16
- Views: 5963
Re: IPSLA -- To monitor more than one probes
its the same pluggin but renamed by me for some testing, any ways here you go : [root@c1ecn-nagios1 libexec]# ./check_cisco_ipsla.pl -H 1.1.1.1 -c XXXXXX -i ping IPSLA: This probe ( echo ) is not supported yet: UNKNOWN [root@c1ecn-nagios1 libexec]# ./check_cisco_ipsla.pl -H 1.1.1.1 -c XXXXXX -i jitt...
- Wed Mar 13, 2013 3:47 pm
- Forum: Nagios XI
- Topic: IPSLA -- To monitor more than one probes
- Replies: 16
- Views: 5963
Re: IPSLA -- To monitor more than one probes
thanks scottwilkerson. if i run -ALL command i am getting the following: [root@c1ecn-nagios1 libexec]# ./check_newipsla.pl -H 1.1.1.1 -c XXXXXX -i ALL Use of uninitialized value $fail in concatenation (.) or string at ./check_newipsla.pl line 42 0. IP SLA status ( 1 IP SLA probes have failed out of ...
- Wed Mar 13, 2013 3:39 pm
- Forum: Nagios XI
- Topic: IPSLA -- To monitor more than one probes
- Replies: 16
- Views: 5963
Re: IPSLA -- Performance data but no graph
Thanks scottwilkerson.
the strange thing is that when i use -ALL in my command, i can see one IPSLA graph (out of 20) and cant see anything when i run an individual IPSLA (TAG), infact the individual tagged ipsla command does not work for icmp-echo and jitter at all.
the strange thing is that when i use -ALL in my command, i can see one IPSLA graph (out of 20) and cant see anything when i run an individual IPSLA (TAG), infact the individual tagged ipsla command does not work for icmp-echo and jitter at all.
- Tue Mar 12, 2013 8:24 pm
- Forum: Nagios XI
- Topic: IPSLA -- To monitor more than one probes
- Replies: 16
- Views: 5963
IPSLA -- To monitor more than one probes
Hi guys, I just need to know the best way to monitor links via IPSLA, i am using this pluggin check_cisco1_ipsla.pl and my command is $USER1$/check_cisco_ipsla.pl -H $HOSTADDRESS$ -c XXXXX -i ALL it does work ok but if one link goes down you get an alerts for all of them that 1 out of 20 ip sla have...
- Tue Mar 12, 2013 8:16 pm
- Forum: Nagios XI
- Topic: IPSLA -- To monitor more than one probes
- Replies: 16
- Views: 5963
IPSLA -- Performance data but no graph
Hi guys, Needed a bit assistance with configuring IPSLA probes, i can see all the statistics but when it comes to the graph i don't see anything and i just a message "No performance graphs were found for this service." I am getting that when i configured that as a service. I have been some...