snmp indexing

I just had yet another client ask if we could monitor switching TCNs and I had to explain we can't because SNMP community/context indexing is not supported in this product.  I will see if I can work around this with an external script, but seems a shame.

Mark

@mnagel Can you explain the issue a bit more? maybe give some specific OID's as an example. Ive done a lot of custom groovy (snmp) based scripts that reference across multiple mibs and oid's without issue across both v2c and v3 snmp

This is a special case for some MIBs that predated the existence of VLANs, like the BRIDGE-MIB (see: https://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/40367-camsnmp40367.html).  It is not an OID subtree, they are parallel versions of the same OID subtree selected based on the SNMPv1/2c community index or SNMPv3 context.  Without support for this, it is not possible to check for per-VLAN TCN issues, among other critical items to monitor in a switched environment.

Regards,
Mark

@mnagel I havnt tried it but LM documented their SNMP library a bit more. this example shows how you can break down the command which should allow you to override and use the index feature

https://github.com/logicmonitor/monitoring-recipes/blob/master/Groovy/SNMP/Groovy_SNMP.groovy

https://github.com/logicmonitor/monitoring-recipes/blob/master/Groovy/SNMP/Groovy_SNMP_V3.groovy

@jamiemurphyit Ah! Thanks for the pointer -- I guess I didn't realize there was other documentation beyond what was in the... documentation :).  This looks like it would do the trick for SNMPv2 since that just requires the community@vlan format.  For SNMPv3, you need to use a context.  It may be possible, but the sample shows nothing like that in the parameter map.

Regards,
Mark