SNMP v1 with rust plugin

Question

The new RUST plugins (will) supports SNMPv1?

I’m testing on a device that allow only v1 and it seems no.

snmpwalk

snmpwalk -v1 -c **** 10.*.*.* .1.3.6.1.2.1.1.1
SNMPv2-MIB::sysDescr.0 = STRING: ****

with rs plugin

/usr/lib/centreon/plugins/centreon-plugin-rust-snmp -H 10.*.*.* -v 1 -c **** --json /usr/lib/centreon/plugins/rs-collections/applications-protocol-snmp/sysdesc.json --check-response
UNKNOWN: Could not connect to 10.*.*.*:161 is the hostname and the snmp community correct ? Resource temporarily unavailable (os error 11)

With TCPdump I see that it force SNMPv2c GetBulk, a function not present on SNMPv1

11:41:08.191089 IP (tos 0x0, ttl 64, id 14733, offset 0, flags [DF], proto UDP (17), length 68)
    10.*.*.*.59760 > 10.*.*.*.161: [bad udp cksum 0x3caa -> 0x6f89!]  { SNMPv2c C="*" { GetBulk(24) R=1  N=1 M=1 .1.3.6.1.2.1.1.1 } }

ltirand · Answer

Hello ​@DalfoThanks for testing the Rust plugin and for the detailed report, it’sis very helpful.Your analysis is correct: the plugin sends a GetBulk request, which is an SNMPv2c operation that doesn’t exist in SNMPv1, so a v1-only device can’t answer it. As things stand, the Rust SNMP plugin doesn’t work with SNMPv1 devices, even when -v 1 is passed.We do plan to support SNMPv1. One of our goals with the Rust collection is to be able to replace the existing Perl SNMP plugins without breaking anything, and SNMPv1 is supported on the Perl side, so it needs to be covered too. We know some older equipment will only ever speak v1.I can’t give you a date yet, but we’re tracking it.Thanks again for the feedback, this is exactly the kind of case we need to hear about during this phase.Best regards.

Sign up

Login to the community