OID for processor usage is .1.3.6.1.2.1.25.3.3.1.2.X where X is the id of the processor.
For whatever the reason (I don't know), this X is not fixed for my servers (I don't know if this happens to everyone). This number changes sometimes after a restart and the processor usage informatinon stops being monitored.
If I define the whole OID for the processor, i.e. .1.3.6.1.2.1.25.3.3.1.2.1 (note the last 1), it runs fine for some time, but after a restart of the server this 1 might have changed to another number, 5 for instance. When I note the graph is not showing correctly, I have to go and find the new value that should be used in the OID field of the datasource, and change it accordingly (to .1.3.6.1.2.1.25.3.3.1.2.5 in this case). This manual fix is not a nice/elegant solution to the problem.
I thought there would be a feature such as not defining this OID completely and leave it as .1.3.6.1.2.1.25.3.3.1.2.X so that cacti (or cactid) do a walk of that branch and retrieve the correct value (whatever X is). So I tried to define the OID of my datasource to .1.3.6.1.2.1.25.3.3.1.2.X and recieve the following error message in cacti.log:
Code: Select all
11/28/2005 11:20:29 AM - CACTID: Poller[0] Host[9] ERROR: Problems parsing Multi SNMP OID! (oid: .1.3.6.1.2.1.25.3.3.1.2.X)
Regards.