Ad Widget

Collapse

Lost data on dell servers monitor

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • walter
    Junior Member
    • Sep 2017
    • 16

    #1

    Lost data on dell servers monitor

    Hi,

    I tried to monitor Dell PowerEdge R920 through SNMP on my test environment. I found the graphs is not continues. But my network device monitor looks great on graphs. So I use tcpdump to find connections of udp port 161 from the Dell sever, things like where the blank area on graphs that the Zabbix server didn't send requests.
    In my another Zabbix environment, everything looks well, both of the environment use the same SNMP template.

    losing data environment:
    zabbix version: 3.4.10
    2 server: master/slave
    2 db: Ver 15.1 Distrib 10.1.34-MariaDB master/slave + elasticsearch

    health environment:
    zabbix version: 3.4.4
    1 server
    2 db: Ver 15.1 Distrib 10.1.34-MariaDB master/slave

    Click image for larger version  Name:	zbx_graph.png Views:	2 Size:	68.2 KB ID:	362295
    Click image for larger version  Name:	tcpdump.png Views:	2 Size:	310.7 KB ID:	362296
    Click image for larger version  Name:	zabbix.png Views:	2 Size:	139.8 KB ID:	362297


    Thanks
    Last edited by walter; 12-07-2018, 11:58.
  • walter
    Junior Member
    • Sep 2017
    • 16

    #2
    After I installed a proxy to monitor the dell server and change the timeout to 15s, the problem solved. So the reason is timeout, I don't know why everything works well on my prod environment, which timeout is 5s the same as the test environment before.

    Comment

    • ingus.vilnis
      Senior Member
      Zabbix Certified Trainer
      Zabbix Certified SpecialistZabbix Certified Professional
      • Mar 2014
      • 908

      #3
      Check zabbix_server.log and grep for the exact host name which is failing. Some more clues could be seen that way.

      Compare those two instances. Do you have "Bulk requests" configured identically for the SNMP interface on both Zabbixes?

      Since you have one server on the healthy environment but a two node cluster in the faulty then maybe it has something to do with the network and addressing configuration?

      Comment

      Working...