snmp, udp, 1.1beta2-1

[dp4]

hi there, newbie here.

how do i get zabbix to talk to the snmp daemon using udp? my daemon listens to udp:161 and tcp:199 (smux protocol). when setting the port to 161 in the "hosts" section, it tries to contact tcp port 161 and fails. when i set it to 199, it connects but does not appear to be sending any data back and forth...at least nothing that ethereal can decode.

or should i go try 1.0 instead?

thanks

[edit: found the 1.1 manual]

[dp4]

no one else using udp for their snmp traffic? does everyone else have a tcp capable snmp daemon?

thanks

[bbrendon]

I think your problem sounded so bizare and has a vague diescription that no one bothered to respond. Unless you tweeked your systems, everything should be udp. I have never messed with tcp snmp because nothing really supports it across the board.

That said, zabbix probably doesn't work with tcp snmp, though i could be wrong. I'm using the latest beta. It Just Works (tm) ....for me anyway.

[dp4]

hi infinity005, thanks for the reply. i'm just beginning to look at snmp again after 10 years and i was trying to double check my experience vs what was expected. (ie, was everyone using tcp:161 for snmp now?)

so in my case, i had downloaded the debian unstable package for zabbix which is the beta version. i installed it and then set it up to monitor a snmp host using the php frontend. when i noticed that the zabbix server was not getting any data, i broke out ethereal to troubleshoot any possible network problems. that's when i noticed that zabbix was using TCP to contact port 161.

so i deinstalled the beta and installed the 1.0 version in the debian stable distro. now, the 1.0 zabbix suckerd will contact the snmp host using udp port 161.

so since you are using the beta and are successfully retrieving snmp data over udp, then that must mean that i did something weird in my initial configuration. the only thing i can think of is that initially, i didn't change the port from the default 10050 (or was it 10000?) to 161. later, noticed that mistake and changed it to 161. since i see no field for setting which protocol to use, perhaps the interface is automagically determining the protocol at the time of creation and not adjusting afterwards? that would at least be consistent with my case where it continued to used tcp no matter what port i set it to.

thanks again

[bbrendon]

If it helps. I'm using the 1.1beta debian packages as well. SNMP works, though I hate using it inside zabbix because it is so tedious to configure. But it works.