Hi Ewan
What ArubaOS version are you testing on, .1.3.6.1.4.1.14823.2.2.1.5.2.1.1 (aka wlsxWlanTotalNumAccessPoints) seems to work correctly at least on 6.4.2.x
Master running 6.4.2.5 (has 6 locals with 3-10 APs each)
(master) #show ap active | include Num
Num APs:0
(master) #
(master) #show ap database status up | include Total
Total APs:36
(master) #
One of the locals connected to it
(local1) #show ap active | include Num
Num APs:11
(local1) #
another local connected to it
(local2) #show ap active | include Num
Num APs:6
(local2) #
snmpwalk
$ snmpwalk -v2c -c public -mALL -M. -O0X <master-ip> .1.3.6.1.4.1.14823.2.2.1.5.2.1.1
WLSX-WLAN-MIB::wlsxWlanTotalNumAccessPoints.0 = Gauge32: 0
$ snmpwalk -v2c -c public -mALL -M. -O0X <local1-ip> .1.3.6.1.4.1.14823.2.2.1.5.2.1.1
WLSX-WLAN-MIB::wlsxWlanTotalNumAccessPoints.0 = Gauge32: 11
$ snmpwalk -v2c -c public -mALL -M. -O0X <local2-ip> .1.3.6.1.4.1.14823.2.2.1.5.2.1.1
WLSX-WLAN-MIB::wlsxWlanTotalNumAccessPoints.0 = Gauge32: 6
the other OID you mentioned .1.3.6.1.4.1.14823.2.2.1.1.3.1 (aka wlsxSwitchTotalNumAccessPoints) gives the exact same data as above.
Is it possible you have something like HA standby configured ? that might cause it to report duplicate counts between a master an a local ?
I note that I was only able to test this on a master that had 0 APs up on it, perhaps there is a quirk there too. Let us know about whether you have HA configured.
regards
-jeff