Ad Widget

Collapse

Fping output interpretation from 2.0.9=>2.4.3

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Pedro.Almeida
    Junior Member
    • Sep 2014
    • 22

    #1

    Fping output interpretation from 2.0.9=>2.4.3

    Hi there,

    We've upgraded to 2.4.3 and three (and only those 3 out of 2K+ hosts) are giving out as unavailable via icmp.

    fPinging from the console works.

    But, in all cases, we are pinging the IP address an internal interface of a router which responds (if that interface) with source on it's external IP.

    Example:

    [root /usr/sbin]# /usr/sbin/realfping -C3 80.XXX.XX.0
    80.XXX.XX.0 : [0], 96 bytes, 0.41 ms (0.41 avg, 0% loss) [<- 195.XX.X.XX]
    80.XXX.XX.0 : [1], 96 bytes, 0.39 ms (0.40 avg, 0% loss) [<- 195.XX.X.XX]
    80.XXX.XX.0 : [2], 96 bytes, 0.38 ms (0.39 avg, 0% loss) [<- 195.XX.X.XX]

    80.XXX.XX.0 : 0.41 0.39 0.38

    I guess the "extra part" (in bold) is confusing the zabbix_pinger

    I wrote a "wrapper" that call's the realfping and trims out that "extra" (if available):
    (Notice I kept the original filename in order not to change the zabbix-server configuration)

    [root /usr/sbin]# /usr/sbin/fping -C3 80.XXX.XX.0
    80.XXX.XX.0 : [0], 96 bytes, 0.38 ms (0.38 avg, 0% loss)
    80.XXX.XX.0 : [1], 96 bytes, 0.39 ms (0.40 avg, 0% loss)
    80.XXX.XX.0 : [2], 96 bytes, 0.41 ms (0.41 avg, 0% loss)

    80.XXX.XX.0 : 0.41 0.39 0.38

    When this was set in place the problem disappeared.

    Were any changes made so that this "extra data" now causes the result not to match?
Working...