Ad Widget

Collapse

Zabbix queue fills with SNMPv1 items

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jasonsbailey
    Junior Member
    • Oct 2014
    • 6

    #1

    Zabbix queue fills with SNMPv1 items

    Hi all,

    I've just set up a new Zabbix server that will be replacing two different alarming servers, and it works well, except that my queue of items to be updated basically gets plugged up with SNMPv1 items, which is puzzling to me.

    This new server is querying servers (running the Zabbix agent), doing discovery on a dozen subnets or so and monitoring a host of virtual circuits, as well as some environmental monitoring equipment that reports status via SNMP. The servers never show up in the queue, but some of the SNMPv1 items end up waiting for 1-2 minutes.

    We are running Zabbix 2.4.0 on a CentOS 6.5 server (quad core Intel processor, 8 GB memory) using the PostgreSQL backend.

    Zabbix logs show lines like the following:

    SNMP agent item "sample.snmp.data.value" on host "Host Cabinet 1" failed: first network error, wait for 15 seconds
    temporarily disabling SNMP agent checks on host "Host Cabinet 1": host unavailable
    resuming SNMP agent checks on host "Host Cabinet 1": connection restored
    I can perform SNMP queries on these same hosts from the Zabbix tools using tools like snmpget and snmpwalk, and the values I get in return are extremely fast. There is plenty of network bandwidth between the Zabbix server and SNMP hosts (which number about 64). I have the server querying around 36 Linux and Unix servers.

    I have increased PostgreSQL shared_buffers to 512MB and checkpoint_segments to 32, which seems to make PostgreSQL more responsive. I have also set Zabbix StartPollers to 150, StartPollersUnreachable to 24, StartPingers to 200 and StartDiscoverers to 10 (we are doing discovery on about a dozen (/24) subnets). I also have CacheSize set to 128MB and StartDBSyncers to 10.

    Required server performance, new values per second currently reads at 61.83.

    Suggestions? Help is very appreciated!
  • ingus.vilnis
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Mar 2014
    • 908

    #2
    Hello and welcome to Zabbix forums!

    Some suggestions from my side:
    1) Please read this article and do some performance tuning according to your Zabbix server performance graphs: http://blog.zabbix.com/scalable-zabb...400-nvps/2615/

    2)
    I have increased PostgreSQL shared_buffers to 512MB and checkpoint_segments to 32, which seems to make PostgreSQL more responsive. I have also set Zabbix StartPollers to 150, StartPollersUnreachable to 24, StartPingers to 200 and StartDiscoverers to 10 (we are doing discovery on about a dozen (/24) subnets). I also have CacheSize set to 128MB and StartDBSyncers to 10.

    Required server performance, new values per second currently reads at 61.83.
    When editing all these parameters you have to be sure what you are doing. I am not a PostgreSQL expert so no comments on that part but some notes about Zabbix server conf:
    • the amount of pollers - tune them according to performance graphs. More is better will not suit this case. StartPollers to 150, StartPollersUnreachable to 24, StartPingers to 200 and StartDiscoverers to 10 may be far too much and waste the RAM on your server but let the graphs show it.
    • CacheSize set to 128MB - ok. Do the same for ValueCache
    • StartDBSyncers to 10 - I would leave the default 4 since each DBsyncer is capable of handling ~1000 new values per second but you have 61. You may leave it as is but that may cause some instability issues.
    • Timeout - now this is the most important part for SNMP checks. If on default 3 then maybe the server simply does not get the SNMP value thus ending in "host unavailable" errors in logs. Try somewhat longer period like 10 - max 30 seconds and see of that gets you the data.


    Hope this helps!

    Best Regards,
    Ingus

    Comment

    Working...