Does anyone else see a large number of MIBs that cause errors when attempting to do snmp walks/gets? When I had the free version of Observium, I simply removed the offending MIBs from /opt/observium/mibs but since I have moved to the SVN version, this may become more of an annoyance since I will be updating frequently, and may actually need the MIBs as I find other uses for Observium.
I'm getting many errors similar to this:
Cannot find module (ZYXEL-MIB): At line 10 in /opt/observium/mibs/220AQV1C0-private
However, in this case (and probably many others) ZYXEL-MIB exists just fine in /opt/observium/mibs/zyxel/ZYXEL-MIB.
My snmp.conf is as follows:
/opt/observium/mibs# cat /etc/snmp/snmp.conf
#
# As the snmp packages come without MIB files due to license reasons, loading
# of MIBs is disabled by default. If you added the MIBs you can reenable
# loaging them by commenting out the following line.
#mibDirs +/sw/share/snmp/mibs:/usr/share/mibs/netsnmp:/opt/observium/mibs
mibDirs +/opt/observium/mibs
mibs all
showMibErrors no
I am sure I'm just missing something simple but it's escaping me at the moment.
Thanks,
Ricardo Meleschi
I know not many shops use OS X servers any more, but we do – so here’s a how to on getting Observium to draw pretty, pretty graphs of your Apple boxes. This guide applies to both the Community and Professional editions.
- Observium has a very powerful way of using entity types & check conditions to do alerting. But you do need to know how this is implemented. There is some documentation on the Observium site itself, which is useful to read.
- Adding support for new MIBs can be quite involved. We have documentation for adding detection for new OSes at but not yet any documentation for adding support for new MIBs. Some things are as simple as writing a few arrays to describe where the data is, some things can take 100s of lines of code.
Observium / mibs / aos / MPLS-LDP-MIB.mib. Find file Copy path Fetching contributors Cannot retrieve contributors at this time. I'm looking at a project to move nodes out of Solarwinds NPM and Observium. Seems there are a lot of custom mibs they use in both and they have created some nice tables to show this info in Solarwinds. Can LibreNMS do similar, I see in Oberservium there is an easy button to just add mibs, but can't see this in LibreNMS and ideas? Observium is an auto-discovering network monitoring platform supporting a wide range of hardware platforms and operating systems including Cisco, Windows, Linux, HP, Juniper, Dell, FreeBSD, F5, Brocade, Citrix Netscaler, NetApp and many more.
Note: I’m going to do this walk through assuming you are running OS X 10.10 “Yosemite.” 10.11 has a feature called System Integrity Protection – tl;dr it means we can’t write to /usr/bin/ or /usr/lib. The instructions below will work just fine for any version of OS X before 10.11, there are just a few steps that are slightly extraneous. If you need to configure SNMP on 10.11, the only change is that snmpconf will walk you through the instructions differently – see an updated post with more information here if you get stuck.
In this post I will detail how to set up the SNMP daemon so Observium can poll information about the server.
Open up a terminal window (Applications -> Utilities -> Terminal). We’ll create a basic SNMP configuration using the snmpconf tool – it is interactive and will prompt you for the various options.
sudo snmpconf -i -g basic_setup
When prompted which files to read in, “all” is a sensible default. I definitely recommend configuring the system MIB group – the location field should be the physical address of where the server is located. This will let Observium plot it on a map. Contact information can be a common alerting email inbox / list or your own, depending on your setup.
I recommend you skip configuring the sysServices.0 OID unless you really know what you’re doing.
Access control is our next thing – we want to ensure that we protect the information that SNMP will expose. We’ll use SNMPv2 because it is the simplest (if you need encryption between your servers and the Observium host, use SNMPv3). Say “no” to both SNMPv3 access options, “no” to SNMPv2 read-write, and “yes” to SNMPv2 read-only. Generate a random string for the community name:
openssl rand -base64 16
Observium Install Mibs
Make sure you note the string for later, you’ll need it to add the device to Observium. The configuration tool will then ask what network resources should be able to access the SNMP daemon with this community. Input either the IP of your Observium server, or a range if you are using multiple SNMP pollers on different IPs. I don’t recommend leaving it open to your whole network, especially if the server is on the public internet. Press return to give no restrictions on OID access. After you’ve configured that read only community, say no to creating more. You can say no to configuring trap setup as well as no to the option asking if you want to configure the agent’s ability to monitor “other aspects of your system” – for a basic setup, this isn’t needed.
There’s now a shiny new snmpd.conf file sitting in the current directory! On versions of OS X before 10.11, the configuration tool will automatically move the file to /usr/share/snmp/snmpd.conf. On 10.11, you will need to manually copy the file –
Observium Update Mibs
sudo mv /etc/snmp/snmpd.conf /etc/snmp/snmpd.conf.bak
sudo cp snmpd.conf /etc/snmp/
Finally, we’ll restart the SNMP daemon by unloading and re-loading the launchd job:
sudo launchctl unload /System/Library/LaunchDaemons/org.net-snmp.snmpd.plist
sudo launchctl load /System/Library/LaunchDaemons/org.net-snmp.snmpd.plist
Observium Adding Mibs
You’re now ready to add the device to Observium in the usual way – select SNMP v2c and input the string as the community name, input the hostname, and that’s it! The next time your discovery and poller runs, you’ll have gorgeous looking graphs started.
Observium Custom Mibs
To learn how to configure the Observium Agent, read on to Part 2!