Comment 6 for bug 1314760

Hmm,
this is unfortunate.
We really have everything together for a fix to be pushed, except valid steps to reproduce.
And I'm not snmp'ish enough to fix it up (in the constraint of my patience) it seems.

The initially reported command always gives me:
.1.3.6.1.2.1.25.6.3 = No more variables left in this MIB View (It is past the end of the MIB tree)

I tried to modify the command, installed extra MIB libraries, ...
Nothing worked so far :-/

I can get up to uptime .1.3.6.1.2.1.25.1.1.0
But nothing else in .1.3.6.1.2.1.25 seems populated.

# snmpwalk -v2c -c public localhost 1.3.6.1.2.1.25
iso.3.6.1.2.1.25.1.1.0 = Timeticks: (143971700) 16 days, 15:55:17.00
iso.3.6.1.2.1.25.1.2.0 = Hex-STRING: 07 E2 02 17 07 03 3B 00 2B 00 00
iso.3.6.1.2.1.25.1.3.0 = INTEGER: 393216
iso.3.6.1.2.1.25.1.4.0 = STRING: "BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic.efi.signed root=UUID=7da7e070-6e58-4b1b-ad8b-11ddb9c46992 ro quiet splash crashkernel"
iso.3.6.1.2.1.25.1.5.0 = Gauge32: 0
iso.3.6.1.2.1.25.1.6.0 = Gauge32: 75
iso.3.6.1.2.1.25.1.7.0 = INTEGER: 0
iso.3.6.1.2.1.25.1.7.0 = No more variables left in this MIB View (It is past the end of the MIB tree)

I think we should be able to test this before pushing I have to ask the reporter (or anyone else) if you'd know how to prepare that?

Not giving up yet ...