NPM reporting the wrong SSID in the Wireless Summary View

Can you please open a support case so this can be looked into further.

Case opened #101693

I have a packet capture from the access point to the server, and would like to make sure that the correct SNMP information is sent to the server.  I am looking for the correct MIB value that ORION uses to search for the SSID and associate it with a client MAC or IP address.

I've seen the same issue on my 1200's though not the 1100's.

Is it against a controller or thick ap?  If thick AP try doing an SNMP Walk with the 802dot11 MIB as that is what we use and see what is reported back.  Odd that it works for some and not for others

These are 1242's and I tried this OID (the standard 802):

1.2.840.10036 (no SSID values returned in the branches)

Then I tried the Cisco one, and this table returns the SSID's in alpha order:

1.3.6.1.4.1.9.9.272.1.1.1.6

Is it possible it's using this OID and just reporting them in alpha order, regardless if the client is on another one?

The access points are thick client (IOS based), no controller is used.

From the development team, I learned they are polling the following OIDs:

OID 1.3.6.1.4.1.11.2.14.11.6.4.1.1.9.2.1.2
OID 1.3.6.1.4.1.9.9.272.1.1.1.6.1.2

The second one is valid for my access points. Both a MIB walk and a packet capture (access point to the ORION server) show the following:

1.3.6.1.4.1.9.9.272.1.1.1.6.1.2.1.1 = Client
1.3.6.1.4.1.9.9.272.1.1.1.6.1.2.1.2 = Reserved
1.3.6.1.4.1.9.9.272.1.1.1.6.1.2.2.1 = Reserved
1.3.6.1.4.1.9.9.272.1.1.1.6.1.2.2.2 = Client

It looks as though ORION is only storing the first value from the array.

Forgot to mention that I have applied SP2 to Orion; now I am running NPM 9.5 SP2
This was in the hopes to resolve "unintended" wireless features.
Unfortunately, this did not resolve the issue.

We are researching and looking into this issue

I have the same problem with all of our 1130 and 1231 APs.  They have three SSIDs each, and all clients will report on only one of the three (the single SSID could be any of the three on the AP) regardless to what SSID they are actually connected to.

I had this problem in 9.5 and just upgraded to SP2 in hopes this problem was resolved, but no dice.