Our Linux team is afraid that the SCOM agent for Linux is not safe and uses root to much. So they wanted to see if SCOM can use SNMP to monitor our Linux systems.
I started to look at the MIB for Redhat and used the “Network Monitoring Management Pack Generator UI Tool” from Microsoft to create a MP. But I found to time consuming to add all the OID:s for each object and then set levels for them. And handling the number of disks on the server and diskusage was just a mess.
Is there anyone who has created a MP for monitoring Linux via SNMP? Most guides I found says: “dont use SNMP the Linux MP is much better”.
Anyone who has any input in the subject? Is the Linux agent safe?
Our *nix team were just as dubious. We’ve settled on a process where they install the agent, send me the certificate, I sign it and send it back and then discover only computers with the UNIX/Linux agent installed; this only uses the UNIX/Linux Action Account. We used the following to get this working:
We have some internal Linux appliances which are supported by a third party and they categorically refused to allow us to install the Unix-based SCOM Agent on those appliances.
What we’ve ended up doing is rolling our own solution. This uses an initial registry-based discovery to identify a ‘proxy’ which is then responsible for creating the required objects in the SCOM environment based on a configuration file. Once the objects are created the monitoring using SNMP is then performed by the same host using a custom PowerShell script and the Sharp SNMP Library.
If this sounds like something people are interested in then i’d be happy to post a bit more information. The script i’ve created uses an XML configuration document to map OID values back to named values. We then use some rules to log these into the databases and also with a custom unit monitor type to allow us to alert should specific values breach a threshold.
Please let me know if you’d like to see more information on this approach.