hi there, do you need to enable port 161 on firewall to? because im not receiving any respons from vyos true SNMP v2
@linuxtechschool4841 Жыл бұрын
Hi, yes, always keep in mind that you need to take care of the firewall. For SNMP protocol port 161and 162 should be allowed guarantee default and specific TRAP/INFORM communication. Regards, RSM.
@TiagoJoaoSilva2 жыл бұрын
kzbin.info/www/bejne/ZpDQZnyjn9GBgdU So *that's* how you convince Zabbix to accept SNMPv3 data from VyOS or other equipment that doesn't follow the RFC to the letter? What was the log message that convinced you that was the correct solution? If the warning is about authentication, it can also be because you're using the same EngineID in two different SNMP sources; also, dropping to DES instead of AES seems to also avoid the bug (haven't tested), but then the auth process isn't well protected...
@linuxtechschool48412 жыл бұрын
Hi Tiago, Well noted. I'll test it to confirm the engine ID issue. Thanks!
@TiagoJoaoSilva2 жыл бұрын
@@linuxtechschool4841 I'm basing myself on a thread in the Zabbix community, but can't post URLs here and I'm away from the computer right now... I'll try to post a google search to reach that thread. Edit: "zabbix snmpv3 issue pollers" should get you there (along with some bug report discussions on the same vein, ZBX-13413 for example). Now I'm feeling kind of dumb for not pursuing this issue a bit more, I ended up dropping to SNMPv2 to make it work. Now I know better!