[Missing SNMP Polling Profile] Synology DS414

[dbuttric]

Device Vendor: Synology

Device Model: DS414

System Object Identifier (SysOID): .1.3.6.1.4.1.8072.3.2.10

List of critical metrics that you expect in the profile (does not need to be all-inclusive, just a general idea of your expectations):

• Network traffic
• Storage by disk
• Storage by volume

Please provide a public gist with a sanitized (sensitive information removed) SNMP walk of the device. Providing MIB files is not a substitute for an SNMP walk and failure to provide one here will result in delays for closing this issue. The output of these commands shows the "true story" of what a device will respond to in SNMP and is used to ensure that our profiles are efficient and accurate for your devices.

Gist Link: https://gist.github.com/dbuttric/369cdca920d00a1a52f414a2fbdbbba5

Example SNMP walk commands:

# v2c example
snmpwalk -v 2c -t 10 -On -c $COMMUNITY_STRING $IP_ADDRESS . >> snmp_walk.out

# v3 example
snmpwalk -v3 -t 10 -l authPriv -u $USERNAME -a MD5|SHA -A $AUTH_PASS -x DES|AES -X $PRIV_PASS -ObentU -Cc $IP_ADDRESS . >> snmp_walk.out

[mcyork]

https://global.download.synology.com/download/Document/Software/DeveloperGuide/Firmware/DSM/All/enu/Synology_DiskStation_MIB_Guide.pdf

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[thezackm]

@dbuttric - looking at the results this device is already covered by the disk_station.yml profile. However, since the vendor is only providing the generic Linux sysoid from Net-SNMP, and there is nothing uniquely descriptive in the sysDescr field, there is no way to automatically match the profile to the device.

.1.3.6.1.2.1.1.1.0 = STRING: Linux storage 3.2.101 #42218 SMP Fri Sep 24 02:38:15 CST 2021 armv7l
.1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.8072.3.2.10

The work-around for this is the manually override the mib_profile and provider values in your snmp-base.yaml file to match them yourself.

example:

devices:
  nas123_192.168.0.1:
    device_name: nas123
    device_ip: 192.168.0.1
    ...
    mib_profile: "!disk_station.yml"
    provider: kentik-nas
    ...

This will ensure that both the correct profile is used for metric collection on the device and the correct provider value is sent to NR in order to synthesize a "NAS" entity in the UI for you.

You'll also want to ensure that the discovery.replace_devices key is set to false so you don't overwrite this change if you run a new discovery job later.