Code has to be written to support new mibs, it’s not sufficient for the mib to just exist.
For this particular thing though you should just be using syslog or some other logging mechanism to record the lease history. I’d not recommend using our syslog support to for long term storage, SQL isn’t suited to that sort of thing.
Our syslog is intended for viewing the last few days + generating notifications from syslog.
Adam.
Sent from my iPhone
On 4 Oct 2021, at 15:37, Nick Her via observium observium@observium.org wrote:
Hello,
I'm a system admin and I'm new to Observium. I've use other monitoring tools in the past, but deploying my own monitoring tool is all new to me. My plan is to test out the waters and possibly implement Observium to our corporate LAN/WAN consisting of approximately 250 devices. I've got 13 core devices responding and polling is working via SNMPv3. I'm getting a lot of useful data from my core switches.
One important data I need is DHCP server information (mac address binding/IP address leases) from our HP switches. These core switches have multiple functions and one of those function is DHCP server. I need to be able to pull this DHCP server data and retain it for a period of time. Maybe send it to a syslog server.
My problem is the MIB (HP-ICF-DHCPV4-SEVRER-MIB) is missing from my Observium install. I've been searching for a couple of hours and have not found a good starting point on how to add this MIB. I see that simply coping the MIB into the Observium install directory isn't the complete process. On your FAQ, the answer to "Vendor specific MIB" was very vague and was not very helpful. Can someone give me a brief run down of what I need to do to get this MIB working? What resources to read for more understanding of the MIB process.
I'm sure someone's asked this question before, sorry if I'm repeating the question.
Thank You, Nick _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium