Hey jgoff,
By SNMP indexes... normally a network device includes a table where you can cross reference the "human readable" form of the SNMP object to the "index number" that the device uses in it's SNMP database.
For example - if you query the OID for "if index" on a network switch, it will typically respond with something like (note .1.2.3.4.5.6 is totally a bogus OID - but it represents the "if index" for a particular device):
snmwalk -v2c -c public .1.2.3.4.5.6 10.1.1.1
.1.2.3.4.5.6.1 = "Gig1/0/1"
.1.2.3.4.5.6.2 = "Gig1/0/2"
.1.2.3.4.5.6.3 = "Gig1/0/3"
...
So, in this instance, you know that Gig1/0/1 has index 1, and Gig1/0/2 has index 2, and so on. You could then query the "tx packets" for a single interface using a different OID... let's say it's .7.8.9.10. By appending the interface index to the end of the "tx packets" OID, you can get the data for a specific interface, like so:
snmpget -v2c -c public .7.8.9.10.1 10.1.1.1
Now, in the Aruba WLC side of things, the OID I shared is indeed giving me the correct stats, but without the SSID to index mapping, the output is nearly meaningless. Here are the first 2 lines of output that I get when I query the following OID (.1.3.6.1.4.1.14823.2.2.1.5.3.3.1.1.8)
iso.3.6.1.4.1.14823.2.2.1.5.3.3.1.1.8.4.46.71.86.82 = Gauge32: 12585
iso.3.6.1.4.1.14823.2.2.1.5.3.3.1.1.8.5.68.111.98.108.101 = Gauge32: 0
So we know that iso.3.6.1.4.1.14823.2.2.1.5.3.3.1.1.8 is the Rx Rate for the WLAN, but we don't know what WLAN it is. I was assuming that each WLAN would have its own "index" like I shared in my hypothetical switch example, but I actually just figured that the rest of the OID is the SSID in decimal form... so I think I will be good now. If I convert .4.46.71.86.82 to ASCII it kind of gives me the SSID. There is a garbled character at the beginning of the string that I'll have to figure out how to deal with. If only there was a query that told me the ASCII string for the SSIDs in the SNMP database.
Thanks for your participation in my question jgoff - it's helped me brainstorm ideas and also work through the issue :)