Various Linux distros - SNMP disk OID change
Hi LM Community
I'm having a issue that I've searched these forums and the web, but unable to find anyone who have a solution on this matter.
We are monitoring Linux server with SNMP, t...
Forum Discussion
11 hours ago, Michael Rodrigues said:SNMP index OID shuffling is common, and it's why LM uses the WILDALIAS/Instance Name as the unique identifier for an instance, while the WILDVALUE/Instance Value is the index OID. The wildvalue can change without losing an instance and its history. AD needs to run after re-shuffling to make data reporting work correctly, as the wildvalue is used to match up reported data to the instance.
Generally, this shouldn't happen often enough for it to throw off more than a poll here and there.
How often are you restarting SNMPd?
Making AD run more often is one way to mitigate.
Not often to be honest, we mostly see it on reboots in relation to patching.
Just last night we updated our SNMPD config (We use Puppet) to include the extended disk information, then we rebooted the SNMPD service. This caused a lot of alarms again across multiple servers.
