ZenPacks : fping : Comments

RE: fping

community@zenoss.org — Thu, 26 Nov 2009 18:05:46 GMT

Thanks it's work a great pack

RE: fping

community@zenoss.org — Tue, 23 Feb 2010 22:45:43 GMT

Has anyone else had an issue where if the destination device is down, no packet loss is graphed? What I am seeing is that if the device is down, fping does not provide the min avg max values. When the output is parsed, the xmt rcv loss values are placed in the min avg max values and the xmt rcv loss values are empty. Would appreciate any assistance with resolving this issue. See below:

/usr/sbin/fping -c 3 -sq 192.168.60.21 2>&1 | /bin/sed 's/$[0-9]*$\/$[0-9]*$\/$[0-9]$%/xmt=\1 rcv=\2 loss=\3/;s/$[0-9]*.[0-9]*$\/$[0-9].*$\/$[0-9].*$/min=\1 avg=\2 max=\3/' | /bin/sed -r '/targets/,/real time/d;s/[0-9]*.[0-9]*.[0-9]*.[0-9]* : xmt\/rcv\/%loss = /PING OK|/;s/, min\/avg\/max = / /'
against TS-1
PING OK|xmt=3 rcv=3 loss=0 min=28.7 avg=31.2 max=35.4
DONE in 2 seconds

/usr/sbin/fping -c 3 -sq 192.168.61.25 2>&1 | /bin/sed 's/$[0-9]*$\/$[0-9]*$\/$[0-9]$%/xmt=\1 rcv=\2 loss=\3/;s/$[0-9]*.[0-9]*$\/$[0-9].*$\/$[0-9].*$/min=\1 avg=\2 max=\3/' | /bin/sed -r '/targets/,/real time/d;s/[0-9]*.[0-9]*.[0-9]*.[0-9]* : xmt\/rcv\/%loss = /PING OK|/;s/, min\/avg\/max = / /'
against 192.168.61.25
192.168.61.25 : xmt/rcv/%loss =min= 3 avg=0 max=100%

Raw fping output (note thatsecond IP which is down does not have min avg max values)

/usr/sbin/fping -c 3 -sq 192.168.60.21
192.168.60.21 : xmt/rcv/%loss = 3/3/0%, min/avg/max = 27.8/28.0/28.3

       1 targets
       1 alive
       0 unreachable
       0 unknown addresses

       0 timeouts (waiting for response)
       3 ICMP Echos sent
       3 ICMP Echo Replies received
       0 other ICMP received

27.8 ms (min round trip time)
28.0 ms (avg round trip time)
28.3 ms (max round trip time)
2.521 sec (elapsed real time)

/usr/sbin/fping -c 3 -sq 192.168.61.25
192.168.61.25 : xmt/rcv/%loss = 3/0/100%

       1 targets
       0 alive
       1 unreachable
       0 unknown addresses

       0 timeouts (waiting for response)
       3 ICMP Echos sent
       0 ICMP Echo Replies received
       0 other ICMP received

0.00 ms (min round trip time)
0.00 ms (avg round trip time)
0.00 ms (max round trip time)
2.520 sec (elapsed real time)

RE: fping

community@zenoss.org — Sun, 14 Mar 2010 17:54:39 GMT

Yes, this pack breaks when the device is down, I think its because the data line changes when the device is down, the min/avg/max is not shown

RE: fping

community@zenoss.org — Fri, 23 Apr 2010 12:37:50 GMT

hi why in my zenoss core system, there is no fping_min graph.

The latecy and loss graph and the ping response spread graph alway display Missing RRD File: **** fping_min

other graph are displayed normaly.

any idea? thanks

RE: fping

community@zenoss.org — Fri, 30 Apr 2010 19:50:32 GMT

To divide the totals by 60 when graphing just add 60,/ to the RRD field for the graph point.

RE: fping

community@zenoss.org — Mon, 24 May 2010 15:58:49 GMT

This seems to work better for the fping data source:

/usr/sbin/fping -c 3 -sq ${dev/manageIp} 2>&1 | /bin/sed 's/$[0-9]*$\/$[0-9]*$\/$[0-9]$%/xmt=\1 rcv=\2 loss=\3/;s/ $[0-9]*.[0-9]*$\/$[0-9].*$\/$[0-9].*$/min=\1 avg=\2 max=\3/' | /bin/sed -r '/targets/,/real time/d;s/[0-9]*.[0-9]*.[0-9]*.[0-9]* : xmt\/rcv\/%loss = /PING OK|/;s/, min\/avg\/max =/ /'

Previous output looked like:

PING OK|xmt=3 rcv=3 loss=0, min/avg/max =min= 153 avg=153 max=154

New output looks like:

PING OK|xmt=3 rcv=3 loss=0 min=153 avg=153 max=154

My fping version is 2.4b2_to (current from Debian lenny). Hope this helps somebody.

RE: fping

community@zenoss.org — Fri, 18 Jun 2010 16:14:35 GMT

If you're running Ubuntu, "apt-get install fping" and you'll need to change the path in the template from "/usr/sbin/fping" to "/usr/bin/fping". Then you'll have a b_fping template you can bind to devices.

RE: fping

community@zenoss.org — Mon, 26 Jul 2010 02:59:04 GMT

Is there any way to get this installed under Zenoss 3? I sure miss the graphing.

Thanks

RE: fping

community@zenoss.org — Mon, 26 Jul 2010 14:47:58 GMT

I'm using it just fine with 3.0. Make sure you have the right path to the fping command and that you've bound the template. Of course, I realize I built it from source, so we'll need to package it up for Python 2.6 soon. It's in the queue to do, in the meantime try renaming the .egg from here to ZenPacks.BlakeDrager.fping-1.0.egg and it should work when you load it.

RE: fping

community@zenoss.org — Mon, 23 Aug 2010 20:47:24 GMT

This is an Excellent Pack.

I am curious why I am unable to graph devices in the /Devices/Ping container. I have hosts that I would like to ping and graph but do not support snmp.

Any thoughts?

Thanks,

RE: fping

community@zenoss.org — Mon, 23 Aug 2010 21:58:15 GMT

The Devices/Ping device class does not have any performance graphs, it is simply for availability. If you want ping-related performance graphs you can install and bind the template provided by this ZenPack.

RE: fping

community@zenoss.org — Mon, 23 Aug 2010 22:32:56 GMT

Matt,

Thanks for the response. I did as you suggested before writing the boards and tried simply adding a device to a class that seems to be graphing properly and am still unable to graph ping responses of a device that is not pollable via snmp. I see the graphs trying to build in the Perf Tab but there is no image.

I would have expected this template to work regardless of the device supporting snmp polling but from my tests it seems it does not.

Thoughts?

RE: fping

community@zenoss.org — Fri, 24 Sep 2010 20:46:39 GMT

Does anybody have any idea why the fping_min.rrd file isn't always created automatically? I've bound this template to 168 devices: fping_max.rrd has been created everywhere, but fping_min.rrd has only appeared on 21 of them.

~/zenoss/perf/Devices> find . -name fping_min.rrd | wc

21 21 518

~/zenoss/perf/Devices> find . -name fping_max.rrd | wc

168 168 4115

RE: fping

community@zenoss.org — Sat, 02 Oct 2010 00:46:11 GMT

Hello, it is a usefull ZenPack. I installed and runnig first graphs... I have a question, every how minutes run the tools ? Only appears send 3 pings in the last 10 minutes.

Thanks, Cristian.

RE: fping

community@zenoss.org — Mon, 04 Oct 2010 01:18:05 GMT

Go in to the performance template and check the cycle time that is set on the command datasource. They default to 5 minutes so that's probably what it's set at. If you increase it though, you're going to have to mess around with RRD graph settings.

RE: fping

community@zenoss.org — Thu, 14 Oct 2010 14:32:25 GMT

In 3.0.2 I encountered an issue with character handling for the command. Had to modify the template and change the command to:

/usr/sbin/fping -c 3 -sq ${dev/manageIp} 2>%261 | /bin/sed 's/$[0-9]*$\/$[0-9]*$\/$[0-9]$%/xmt=\1 rcv=\2 loss=\3/' | /bin/sed 's/ $[0-9]*.[0-9]*$\/$[0-9].*$\/$[0-9].*$/min=\1 avg=\2 max=\3/' | /bin/sed -r '/targets/,/real time/d' | /bin/sed -r 's/[0-9]*.[0-9]*.[0-9]*.[0-9]* : xmt\/rcv\/%loss = /PING OK|/' | /bin/sed -r 's/, min\/avg\/max =/ /'

RE: fping

community@zenoss.org — Fri, 05 Nov 2010 23:06:31 GMT

Today, I observed a 3.0.2 Zenoss generating fping processes (along with sed processes being forked by fping) that weren't properly terminating as they were waiting for standard input. This was due to a misconfiguration in Zenoss that had fping trying to ping a host that didn't have an IP address properly defined which lead to fping trying to ping nothing:

zenoss     500 /usr/sbin/fping -c 3 -sq
zenoss     501 /bin/sed s/$[0-9]*$\/$[0-9]*$\/$[0-9]$%/xmt=\1 rcv=\2 loss=\3/;s/$[0-9]*.[0-9]*$\/$[0-9].*$\/$[0-9].*$/min=\1 avg=\2 max=\3/
zenoss     502 /bin/sed -r /targets/,/real time/d;s/[0-9]*.[0-9]*.[0-9]*.[0-9]* : xmt\/rcv\/%loss = /PING OK|/;s/, min\/avg\/max = / /

Everytime fping attempted to run, similar processes would spawn and stay resident. This was fixed before anything significantly bad happened, but (unless this has been subsequently fixed) this is something to watch out for.

RE: fping

community@zenoss.org — Fri, 07 Jan 2011 02:41:09 GMT

I have 5 sites but only have Zenoss collectors in 1 of them (I am collecting over my WAN from remote devices). I'm intersted in measuring latency between 2 of the sites that have hosts, just no Zenoss collectors. Can anyone suggest a way for me to do this?

RE: fping

community@zenoss.org — Fri, 07 Jan 2011 16:46:01 GMT

The way I'd do it (if one of the remote sites has a linux host), is to write a bash script on that host that runs as a cron job every minute or so doing a ping and write the result to a file. Then I'd create an ssh command datasource that remotely executes a script on that server which reads from that file. You can then graph the values and threshold against them.

RE: fping

community@zenoss.org — Wed, 19 Jan 2011 15:20:31 GMT

Hello,

is there a way to decrease the interval of the command execution. I see that the cycle is 300 seconds. I can manipulate the interval and count of the packets, but this is not a solution I am looking for.

For example if I use interval of 10sec*count 30 packes = 300 packets*sec. But when I run this command to a host from the Zenoss web interface, it gives me timeout in 30sec. So also this interval is somehow limited to 30sec. Is there a way to manipulate with these intervals?

I want to achieve a constant ping to hosts on every 10 seconds.

I'm using Zenoss 3.0.3.

Thank you

RE: fping

community@zenoss.org — Wed, 19 Jan 2011 15:41:00 GMT

You are limited by how long the script takes to execute. If you set the cycle to 10 seconds on a template applied across all of your hosts, that doesn't just mean that 1 script needs to complete running every 10 seconds, it means that the script needs to finish running for every host within 10 seconds. The fact that you are getting timeouts shows that the fping script is taking a long time to finish with the settings that you specified. Zenoss is never going to be able to do a perfect continuous ping via an external script. You're not giving Zenoss enough time to actually finish the script execution for each host. Even if you only did 1 ping packet across 100 hosts, the scripts still most likely wouldn't finish within the 10 second window. Zenoss only runs a certain amount of scripts simultaneously (I believe it's 10 by default).

RE: fping

community@zenoss.org — Wed, 19 Jan 2011 16:51:52 GMT

Ryan thank you for the explanation.

What about limiting the cycle time? I see that in the monitoring templates for fping there is an option "cycle time". I limited this to 10sec.

In the command template I set the packet count to 3.

Does this mean that the hosts will be pinged every 10sec 3 times?

Thank you again!

RE: fping

community@zenoss.org — Wed, 19 Jan 2011 17:56:10 GMT

Yes, that is exactly what that means. The problem is, if it takes the fping script 3 seconds to ping a host 3 times, and you have 100 hosts, then you may run over the cycle time. It runs 10 scripts at once by default. Even if those 10 scripts finish running in 3 seconds, another 10 scripts kick off afterwards, and then another 10, and so on... you end up with 3 x (100 / 10) = 30 seconds, so you end up going over your set polling cycle and end up with gaps in graphs, or graphs not generating. The other thing is, if your RRD settings aren't configured to break the graph up in to enough parts, the data will be graphed in averaged 5 minute chunks, so you're not going to end up with a high resolution graph.

Under collector settings there are entries like:

RRA:AVERAGE:0.15:1:600
RRA:AVERAGE:0.15:6:600
RRA:AVERAGE:0.15:24:600
RRA:AVERAGE:0.15:288:600
RRA:MAX:0.15:6:600
RRA:MAX:0.15:24:600
RRA:MAX:0.15:288:600

I changed the first value to 0.15 to break the graph up in to 15 second slices. After adjusting those settings you need to delete the existing RRD files to allow them to regenerate with the new settings.

RE: fping

community@zenoss.org — Thu, 20 Jan 2011 09:07:18 GMT

Thanks for the reply.

I managed to increase the number of parallel jobs, adjusted the SNMP timers, ping and fping values and also regenerated the values for the graphs. I will see how it will work in a larger environment.

Thanks for your help!

RE: fping

community@zenoss.org — Thu, 20 Jan 2011 15:30:35 GMT

No problem.

RE: fping

community@zenoss.org — Tue, 01 Feb 2011 22:51:13 GMT

I have been working on getting the ping total count to display the correct number. Since its not a graph point I can't just do the RPN math in there, but it looks like I could modify the Custom Graph Definition to get the correct value displayed. I modified the Definiting to look like:

CDEF:pingloss=Pings_Sent-raw,Pings_Received-raw,-
LINE1:pingloss#ff000099:Pings Lost
GPRINT:pingloss:LAST:cur\: %2.2lf
GPRINT:pingloss:AVERAGE:avg\: %2.2lf
GPRINT:pingloss:MAX:max\: %2.2lf\j
VDEF:pingtotal=Pings_Sent-raw,TOTAL
GPRINT:pingtotal:Total Sent      \:%10.0lf%s\j
VDEF:rcvtotal=Pings_Received-raw,TOTAL
GPRINT:rcvtotal:Total Received \:%10.0lf%s
CDEF:realpingtotal=pingtotal,300,\/
GPRINT:realpingtotal:Total Sent      \:%10.0lf%s\j

I've tried this about a dozen other ways and reading into all the RRD info and RPN math it looks like I'm doing it correctly but anytime I change it my graph disapears with just the header of the graph. Still looking and reading and trying things but if anybody has any ideas I would apreciate it.

RE: fping

community@zenoss.org — Thu, 10 Feb 2011 17:43:28 GMT

Figured it out. When I was working with it however I removed the datapoints and made a complete custom definition though I don't think it was needed. Also my step was reduced in my template to 30 seconds so you need to change the 30 to whatever your step is set at.

The problem I was running into was explained in this thread:

http://rrd-mailinglists.937164.n2.nabble.com/Concatenated-VDEF-and-CDEF-commands-in-a-rrdtool-graph-cmd-td5727234.html

Here is the Custom Definition I ended up with:

-F
-E
--height=100
--width=500
--vertical-label=Pings
DEF:Pings_Sent-raw=${here/fullRRDPath}/fping_xmt.rrd:ds0:AVERAGE
DEF:Pings_Sent-raw-max=${here/fullRRDPath}/fping_xmt.rrd:ds0:MAX
CDEF:Pings_Sent=Pings_Sent-raw
LINE1:Pings_Sent-raw#00cc00ff:Pings Sent
GPRINT:Pings_Sent-raw:LAST:cur\:%5.2lf%s
GPRINT:Pings_Sent-raw:AVERAGE:avg\:%5.2lf%s
GPRINT:Pings_Sent-raw-max:MAX:max\:%5.2lf%s\j
DEF:Pings_Received-raw=${here/fullRRDPath}/fping_rcv.rrd:ds0:AVERAGE
DEF:Pings_Received-raw-max=${here/fullRRDPath}/fping_rcv.rrd:ds0:MAX
CDEF:Pings_Received=Pings_Received-raw
LINE1:Pings_Received-raw#0000ff99:Pings Received
GPRINT:Pings_Received-raw:LAST:cur\:%5.2lf%s
GPRINT:Pings_Received-raw:AVERAGE:avg\:%5.2lf%s
GPRINT:Pings_Received-raw-max:MAX:max\:%5.2lf%s\j
VDEF:pingtotal=Pings_Sent-raw,TOTAL
CDEF:realpingtotal=Pings_Sent-raw,POP,pingtotal,30,/
GPRINT:realpingtotal:MAX:Total Sent \:%10.0lf%s\j
VDEF:rcvtotal=Pings_Received-raw,TOTAL
CDEF:realrcvtotal=Pings_Received-raw,POP,rcvtotal,30,/
GPRINT:realrcvtotal:MAX:Total Received \:%10.0lf%s

I think if you wanted to quickly fix it you could just remove the last 4 lines of your custom definition and then paste in these lines:

VDEF:pingtotal=Pings_Sent-raw,TOTAL
CDEF:realpingtotal=Pings_Sent-raw,POP,pingtotal,30,/
GPRINT:realpingtotal:MAX:Total Sent \:%10.0lf%s\j
VDEF:rcvtotal=Pings_Received-raw,TOTAL
CDEF:realrcvtotal=Pings_Received-raw,POP,rcvtotal,30,/
GPRINT:realrcvtotal:MAX:Total Received \:%10.0lf%s

RE: fping

community@zenoss.org — Wed, 16 Mar 2011 11:54:42 GMT

Zenoss 3.1.0 and Ubuntu 10.04: Problem with run of this command

/usr/sbin/fping -c 3 -sq ${dev/manageIp} 2>&1 | /bin/sed 's/$[0-9]*$\/$[0-9]*$\/$[0-9]$%/xmt=\1 rcv=\2 loss=\3/;s/$[0-9]*.[0-9]*$\/$[0-9].*$\/$[0-9].*$/min=\1 avg=\2 max=\3/' | /bin/sed -r '/targets/,/real time/d;s/[0-9]*.[0-9]*.[0-9]*.[0-9]* : xmt\/rcv\/%loss = /PING OK|/;s/, min\/avg\/max = / /'

I created bash script $ZENHOME/libexec/fping-wrapper

#!/bin/bash

/usr/bin/fping -c 3 -sq $1 2>&1 | /bin/sed 's/$[0-9]*$\/$[0-9]*$\/$[0-9]$%/xmt=\1 rcv=\2 loss=\3/;s/ $[0-9]*.[0-9]*$\/$[0-9].*$\/$[0-9].*$/min=\1 avg=\2 max=\3/' | /bin/sed -r '/targets/,/real time/d;s/[0-9]*.[0-9]*.[0-9]*.[0-9]* : xmt\/rcv\/%loss = /PING OK|/;s/, min\/avg\/max =/ /'

chmod +x $ZENHOME/libexec/fping-wrapper

Command Template:

fping-wrapper ${dev/manageIp}

Enjoy it !

RE: fping

community@zenoss.org — Wed, 20 Jul 2011 16:50:11 GMT

I am having issue with this pack due to a known small amount of packetloss which causes the command syntax to give an errored response:

Normal, working device with no packetloss:

zenoss@Zenoss-Pinger:/etc/default# /usr/bin/fping -c 5 -sq 192.168.198.1 2>&1 | /bin/sed 's/$[0-9]*$\/$[0-9]*$\/$[0-9]$%/xmt=\1 rcv=\2 loss=\3/;s/$[0-9]*.[0-9]*$\/$[0-9].*$\/$[0-9].*$/min=\1 avg=\2 max=\3/' | /bin/sed -r '/targets/,/real time/d;s/[0-9]*.[0-9]*.[0-9]*.[0-9]* : xmt\/rcv\/%loss = /PING OK|/;s/, min\/avg\/max = / /'
PING OK|xmt=5 rcv=5 loss=0, min/avg/max =min= 335 avg=336 max=338

Normal, not working script due to the first packet being dropped every time:

zenoss @Zenoss-Pinger:/etc/default# /usr/bin/fping -c 5 -sq 10.61.6.135 2>&1 | /bin/sed 's/$[0-9]*$\/$[0-9]*$\/$[0-9]$%/xmt=\1 rcv=\2 loss=\3/;s/$[0-9]*.[0-9]*$\/$[0-9].*$\/$[0-9].*$/min=\1 avg=\2 max=\3/' | /bin/sed -r '/targets/,/real time/d;s/[0-9]*.[0-9]*.[0-9]*.[0-9]* : xmt\/rcv\/%loss = /PING OK|/;s/, min\/avg\/max = / /'
10.61.6.135 : xmt/rcv/%loss =min= 5 avg=4/20% 719/723 max=733

As you can see, the lack of PING OK in the line messes all other information to the point that the data is not graphed. How is this plugin meant to graph packetloss if it fails everytime when the first packet is dropped?

Any help would be greatly appreciated.

RE: fping

community@zenoss.org — Tue, 16 Aug 2011 18:53:43 GMT

I tried using this approach but with a slight modification and it worked great for me.

You see the problem that i found is that when some of the nodes were entered, some if not many of the IP address and host name was originally copied and pasted from an excel spreadsheet which meant there were hidden illegal characters that seemed to be screwing up fping.

As a result, when looking at the process list you can clearly see lots of fping commands being issued with NO IP address where the ${dev/manageIp} would be expected. (and of course these would stay open until they system ran out of open file handles)

Simple solution was to add some sanitization to strip out everything except 0-9 and . characters

Below are the modifications i made to the original fping-wrapper script provided by TopOSScz

#!/bin/bash

CLEAN=${1//[^0-9\.]/}

/usr/bin/fping -c 3 -sq $CLEAN 2>&1 | /bin/sed 's/$[0-9]*$\/$[0-9]*$\/$[0-9]$%/xmt=\1 rcv=\2 loss=\3/;s/ $[0-9]*.[0-9]*$\/$[0-9].*$\/$[0-9].*$/min=\1 avg=\2 max=\3/' | /bin/sed -r '/targets/,/real time/d;s/[0-9]*.[0-9]*.[0-9]*.[0-9]* : xmt\/rcv\/%loss = /PING OK|/;s/, min\/avg\/max =/ /'

And of course it should go without saying that from here you would use the same method of modifying the command template to call 'fping-wrapper ${dev/manageIp}' instead of the big long command string

(I found explicit paths to fping-wrapper worked best here)

this fixed my problems and was actually pretty easy to implement as a work around.

RE: fping

community@zenoss.org — Sat, 03 Sep 2011 19:40:36 GMT

fping stopped graphing after upgrade to Zenoss 3.2. When I test the template with a device, I first noticed that zenoss command shell didn't ouput the fping command properly just like if the sed's regex were not working anymore. So I wrapped the fping in the shell script and changed the template command accordingly. Now I see the command output correctly as PING OK|xmt=3 rcv=3 loss=0 min=19.1 avg=19.9 max=20.7 but still no graphing. Should I reset the whole graphs?

RE: fping

community@zenoss.org — Sun, 04 Sep 2011 18:58:50 GMT

I just found out on the forum that 3.2 is responsible of some graphing headaches...

This will certainly refrain me to upgrade to fast the next time.

RE: fping

community@zenoss.org — Mon, 19 Sep 2011 14:31:45 GMT

Hello,

I'm working with REDhat and I installed this zenpack on zenoss 3.2.

when I look through RRD file, only the fping_xmt.rrd is created.

any one has a solution??

thks

RE: fping

community@zenoss.org — Fri, 07 Oct 2011 16:09:28 GMT

Test work great..
Preparing Command...

Executing command /usr/sbin/fping -c 3 -sq 192.168.10.254 2>&1 | /bin/sed 's/$[0-9]*$\/$[0-9]*$\/$[0-9]$%/xmt=\1 rcv=\2 loss=\3/;s/$[0-9]*.[0-9]*$\/$[0-9].*$\/$[0-9].*$/min=\1 avg=\2 max=\3/' | /bin/sed -r '/targets/,/real time/d;s/[0-9]*.[0-9]*.[0-9]*.[0-9]* : xmt\/rcv\/%loss = /PING OK|/;s/, min\/avg\/max = / /' against 192.168.10.254

PING OK|xmt=3 rcv=3 loss=0 min=6.31 avg=6.80 max=7.42

DONE in 2 seconds

I add the template to /ping devices but the graphs are empty. Only ping count show me.
Any idea what is wrong ?

RE: fping

community@zenoss.org — Fri, 21 Oct 2011 08:10:10 GMT

Hello,

Zenpack doesn't work on my 3.2 installation.

Michael

RE: fping

community@zenoss.org — Fri, 02 Dec 2011 21:34:42 GMT

I think i've got a fix for this - i've been through the regular expressions on the sed commands and amended them to be a bit more robust. I'm currently testing with this as the fping command...

/usr/sbin/fping -c 3 -sq ${dev/manageIp} 2>&1 | /bin/sed 's/$[0-9]*$\/$[0-9]*$\/$[0-9]*\(\.[0-9]*$*\)%/xmt=\1 rcv=\2 loss=\3/;s/$[0-9]*\(\.[0-9]*$*\)\/$[0-9]*\(\.[0-9]*$*\)\/$[0-9]*\(\.[0-9]*$*\)/min=\1 avg=\3 max=\5/' | /bin/sed -r '/targets/,/real time/d;s/[0-9]*.[0-9]*.[0-9]*.[0-9]* : xmt\/rcv\/%loss = /PING OK|/;s/, min\/avg\/max = / /'

RE: fping

community@zenoss.org — Thu, 23 Feb 2012 08:48:12 GMT

How wil this zenpack cope with 6000 Devices ?

Regards,

Stefan

RE: fping

community@zenoss.org — Thu, 23 Feb 2012 15:03:01 GMT

You'll have 6000 scripts kicking off each cycle. Unless it's one hell of a server it probably wouldn't cope very well.

RE: fping

community@zenoss.org — Sat, 03 Mar 2012 16:57:27 GMT

Is there any pack for zenoss 3.2.* like this one?If doesn't, can someone help me to build one?I need some graphs for my /device/ping devices.

Thanks

RE: fping

community@zenoss.org — Sat, 03 Mar 2012 17:39:35 GMT

ZenPacks.BlakeDrager.fping-1.0-py2.6.egg.zip should be what your after. There generally isnt anything required for a pack that was tested on 3.0 vs 3.2.1. I'd download the 1.0-py2.6 egg and give it a shot. (Make sure you unzip it before installing)

RE: fping

community@zenoss.org — Sat, 05 May 2012 15:58:18 GMT

hi,

it works great when everything is up, nice graphs!!!

zenoss@server-ProLiant-DL160-G6:/home/server$ /usr/bin/fping -c 3 -sq "192.168.1.211" 2>&1 | /bin/sed 's/$[0-9]*$\/$[0-9]*$\/$[0-9]$%/xmt=\1 rcv=\2 loss=\3/;s/$[0-9]*.[0-9]*$\/$[0-9].*$\/$[0-9].*$/min=\1 avg=\2 max=\3/' | /bin/sed -r '/targets/,/real time/d;s/[0-9]*.[0-9]*.[0-9]*.[0-9]* : xmt\/rcv\/%loss = /PING OK|/;s/, min\/avg\/max = / /'

PING OK|xmt=3 rcv=3 loss=0 min=0.27 avg=0.44 max=0.68

But when the devices are down, the fping package doesnt provide anything...

192.168.1.211 : xmt/rcv/%loss =min= 3 avg=0 max=100%

how to fix this?

RE: fping

community@zenoss.org — Sat, 11 Aug 2012 18:58:48 GMT

Trying to install fping via web UI or commandline in the Zenoss 4.2 Demo VM fails with errör

AttributeError: 'NoneType' object has no attribute 'clone'

Any suggestions?

RE: fping

community@zenoss.org — Mon, 13 Aug 2012 15:38:45 GMT

First off you need to change the py2.6 to py2.7 in the filename to get it to install. Secondly, zenping provides similar stats in 4.2 and is less intensive. Check out the PING datasource. There are some details about it in the admin guide. I have a ZenPack planned that will provide a nice template for this.

RE: fping

community@zenoss.org — Tue, 18 Dec 2012 02:07:42 GMT

There is error in sed regexp. One * is missing.

Not working
/usr/sbin/fping -c 3 -sq ${dev/manageIp} 2>&1 | /bin/sed 's/$[0-9]*$\/$[0-9]*$\/$[0-9]$ ...

Working

/usr/sbin/fping -c 3 -sq ${dev/manageIp} 2>&1 | /bin/sed 's/$[0-9]*$\/$[0-9]*$\/$[0-9]*$ ...

joll200x suggest similar changes earlier.

RE: fping

community@zenoss.org — Fri, 31 May 2013 19:43:18 GMT

Same issue here.