Advice with new OS/discovery for Dell ME4084

Currently working with a librenms test server to add a Dell ME4084 array.

I’ve some Dell ME4084 arrays, sat behind proxied SNMPD.conf on fileservers.

The proxy is working. Proxy is used because fileserver connects directly to the array’s two controllers (A,B) using ethernet cables. Back-to-back interfaces.

snmpwalk | head of an ME4084…

.1.3.6.1.2.1.1.1.0 = STRING: DELL EMC ME4084
.1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.674
.1.3.6.1.2.1.1.3.0 = Timeticks: (295337865) 34 days, 4:22:58.65
.1.3.6.1.2.1.1.4.0 = STRING: our_org
.1.3.6.1.2.1.1.5.0 = STRING: our_name_for_array
.1.3.6.1.2.1.1.6.0 = STRING: location
.1.3.6.1.2.1.1.7.0 = INTEGER: 64
.1.3.6.1.2.1.1.8.0 = Timeticks: (295337865) 34 days, 4:22:58.65
.1.3.6.1.2.1.1.9.1.2.1 = OID: .1.3.6.1.6.3.11.2.3.1.1
.1.3.6.1.2.1.1.9.1.2.2 = OID: .1.3.6.1.6.3.15.2.1.1

This is how I’ve started out.

contents of new file includes/definitions/dell-me-array.yaml

os: dell-me4084
text: ‘Dell ME4084’
type: storage
icon: dell
group: dell
discovery:
- sysObjectID:
- .1.3.6.1.2.1.1.1.0
- sysDescr_regex:
- ‘/^DELL(\s)+EMC(\s)+ME4084/’

Now it is getting discovered which is good…

So now I think I need a file in includes/definitions/discovery/<os>.yaml

Which points to MIB at top in first line. Then definitions.

MIB is abit curious…named “FCMGMT-MIB.mib”

https://www.dell.com/support/home/en-uk/drivers/driversdetails?driverid=j2p9c

Noticed above request for the me4012.

We just need to make sense of this MIB. A03 I think is latest version/zip