HPE SN2010M

[rhoover9192]

Device Vendor: HPE

Device Model: SN2010M HPE.SN2010M.SNMP-MIB.pdf hpe-switch.txt HPE SN2010M SNMP-MIB.pdf hpe-snmpwalk.txt hpe-switch.txt

System Object Identifier (SysOID):

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

If there is a New Relic technical support case related to this request, please provide the case number:

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:

---

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

[rhoover9192]

Any update on this issue?

[Mesverrum]

I apologize for the delayed response, there has been a change with the way SNMP profiles are handled. In the interest of not being a bottleneck, SNMP profiles are now to be handled as a self-service item for users of ktranslate. Your organization should fork this repo or copy the contents and make any desired changes directly there, you can see an example of how to pass a modified fork of the profile definitions in this documentation. You can find documentation of the syntax and capabilities of the profile definitions in this template. There will be no need for approvals or review except those you implement within your own fork for yourselves.