Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-11726

icmp ping detects duplicate answer as ping loss

    Details

    • Type: Incident report
    • Status: Closed
    • Priority: Trivial
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Proxy (P), Server (S)
    • Labels:
    • Environment:
      Debian Wheezy
    • Team:
      Team A
    • Sprint:
      Sprint 1, Sprint 2
    • Story Points:
      4

      Description

      Destination host has loadbalancer in front of set of hosts. Pinging loadbalancer causes host to respond and thus multiple respond are received and duplicate answer is misinterpreted as packet loss even-though there's none.

      Global script ping is configured as: /bin/ping -c 3 {HOST.CONN} 2>&1

      Below is example response from live host(IP removed/masked):

      PING xxx.xx.xxx.xxx (xxx.xx.xxx.xxx) 56(84) bytes of data.
      64 bytes from xxx.xx.xxx.xxx: icmp_req=1 ttl=117 time=4.26 ms
      64 bytes from xxx.xx.xxx.xxx: icmp_req=1 ttl=117 time=4.28 ms (DUP!)
      64 bytes from xxx.xx.xxx.xxx: icmp_req=2 ttl=117 time=4.36 ms
      64 bytes from xxx.xx.xxx.xxx: icmp_req=2 ttl=117 time=4.38 ms (DUP!)
      64 bytes from xxx.xx.xxx.xxx: icmp_req=3 ttl=117 time=4.32 ms
      
      --- xxx.xx.xxx.xxx ping statistics ---
      3 packets transmitted, 3 received, +2 duplicates, 0% packet loss, time 2001ms
      rtt min/avg/max/mdev = 4.260/4.324/4.388/0.064 ms
      

      See comments below for correct source data.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              marko.sandholm Marko Sandholm
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: