Closed naveen-karedi closed 1 year ago
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.
Device Vendor: Cisco
Device Model: C9800, AIR-CT5508, AIR-CT5520, AIR-CT3504
System Object Identifier (SysOID): IR-CT3504 ------> SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.1.2427 C9800 (2 models) C9800LF -----> SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.1.2861
C980040------> SNMPv2-SMI::enterprises.9.1.2530 AIR-CT5508 -------> SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.1.1069 AIR-CT5520 ------> SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.1.2170
List of critical metrics that you expect in the profile (does not need to be all-inclusive, just a general idea of your expectations):
MIB: https://www.circitor.fr/Mibs/Mib/C/CISCO-LWAPP-DOT11-CLIENT-MIB.mib
If there is a New Relic technical support case related to this request, please provide the case number: Case #00120495
Gist Link: https://gist.github.com/naveen-karedi/dc8eca686253abe5284ca08c29ac0140