The sysObjectId in versions 7.13 and earlier return the expected Mikrotik ID, but version 7.19.6 and 7.21.5 are returning 0.0 for that field. I've tried stopping and starting the snmp service, defaulting out the name/location/contact fields and restarting the service. Nothing works, except for reverting back to an earlier version of RouterOS. The specific model is a RB912UAG-5HPnD.
Is anyone else having this issue? And/or found a way to correct it?
On my Chateau i get follow
[patrik@archlinux mib]$ snmpwalk -c public -v2c 192.168.88.1
SNMPv2-MIB::sysDescr.0 = STRING: RouterOS S53UG+5HaxD2HaxD&RG650E-EU 7.23.3 (stable)
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.14988.1
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (64582800) 7 days, 11:23:48.00
SNMPv2-MIB::sysContact.0 = STRING:
SNMPv2-MIB::sysName.0 = STRING: Chateau
SNMPv2-MIB::sysLocation.0 = STRING:
SNMPv2-MIB::sysServices.0 = INTEGER: 78
I have just enabled snmp with no edit fields, like name/loc/contects.
So what do you expect that sysObjectID should return.
On my device i get following:
[patrik@archlinux mib]$ snmpwalk -c public -v2c 192.168.88.1 sysObjectID
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.14988.1
And how about you tried to get the enterprises values like this that your sysObjectID refers to:
[patrik@archlinux mib]$ snmpwalk -m ./mikrotik.mib -c public -v2c 192.168.88.1 SNMPv2-SMI::enterprises.14988.1
The output you have is what I see on version 7.13 and earlier. On the newer versions, and it isn't all of the RB912UAG boards that do it, some of them are working correctly after being updated. But some of them give the following:
snmpget -c:****** -v:2c -r:10.******* -o:.1.3.6.1.2.1.1.2.0
SnmpGet v1.01 - Copyright (C) 2009 SnmpSoft Company
[ More useful network tools on http://www.snmpsoft.com ]
OID=.1.3.6.1.2.1.1.2.0
Type=OID
Value=0.0
The 14988 oids are all still there too, but it messes with the LibreNMS categorizing the device and pulling all of the data that normally gets pulled for mikrotik devices. I have updated the SNMP location field on the effected devices and have a temporary work around for it. However, I cannot use that field to group them right now and would like to use it for that purpose.