EMC Avamar Support

Feature Requests
,
1

Gents,

I need some advice onto how one should categorize Avamar. It’s software that run’s on either SuSe or RHEL but unlike other EMC products, it does not have a modified kernel.

Right now LibreNMS can recognize Avamar like a regular linux server. My question to the seniors here is if it’s better to try and add code to allow the discovery of Avamar as a new OS or just treat it as an application ?

Avamar does have it’s own snmp OIDs that we can get some information out of. Right now what I do is just use the nagios snmp poll to get information from those OIDs. Its not pretty, but it does do the job. However a baked in solution would be ideal

avamar-snmp
avamar-snmp731×321 2.44 KB

I’ll be more than happy to write some sort of code for it, just need the advice on which way this system should be categorized.

Thanks,

2

Is it an “appliance” or something you install on a server? Appliance => OS, Install => Application.

3

Got it. This was always a tricky one because EMC would let you install it yourself with strict requirements in the past but as of the last release, it appears it’s only going to be a virtual appliance only already prepped.

It’s probably best to treat it as an “Appliance” then. The hardware version hasn’t been announced yet but seems to be the smarter approach.

Thanks,

1 Like
4

In case anyone was waiting for this. Latest version 18.2 doesn’t seem to have the SNMP sub agent working anymore. I have a case with Dell/EMC but no official word if this is going to be removed in the future.