I did some more digging and I don't think it's this simple. First of all, the total number of neighbors that the IAP reports includes EVERY BSSID that it hears (its own network as well as interferers). This means I cannot divide the number and come up with real APs. And besides, if I have SSIDs that are single band only, then the divide by 2 logic doesn't work. The other thing I found is that the neighbor output contains BLANK ESS fields. An IAP can see a neighbor with a blank ESSID???
ARM Neighbors
-------------
bssid essid channel snr tx-power PL (dB) AP Flags Last Update (Total updates)
----- ----- ------- --- -------- ------- -------- ---------------------------
b4:5d:50:aa:2d:81 1 33 22 83 Passive
b4:5d:50:aa:2d:83 ACME-123 1 34 22 82 Passive
b4:5d:50:aa:b2:81 ACME-VoIP 1 39 22 77 Passive
b4:5d:50:aa:b2:83 ACME-123 1 40 22 77 Passive
b4:5d:50:aa:25:e1 ACME-VoIP 11 19 22 98 Passive
b4:5d:50:aa:25:e3 11 19 22 98 Passive
When I look up the "blank" ESSID in the bss-table output, I can find it there, with an ESS :-)
b4:5d:50:aa:2d:81 ACME-VoIP ?/? 172.20.7.120 g-HT ap 6/22.7/22.7 0 b4:5d:50:c2:a2:d8 0 6d:13h:34m:51s
I am still on a hunt for my Aruba IAP neighbour count and getting very confused. I am impressed at the low level nature of the CLI output (if I could make sense of it) but the GUI is supposed to make my life easier - and it's misleading. Because in my initial posting I showed a graphic that said "Neighboring APs" ... and if I were a normal user I'd read that literally. An AP is an AP, and not a BSSID.
Why would I care about the long list of BSSID's in a neighbor list? If an AP has 5 SSID's, then all of those SSIDs will be on the same band's channel. Hence, no need to list the BSSIDs. Just give me the AP neighbor and his 2.4 Channel, and his 5Ghz channel information.
I apologise if I mised something obvious but I am going in circles trying so answer a very basic thing.