topic Re: Wrong registered APs number from snmp query in Wireless

Wrong registered APs number from snmp query

gdspa — Mon, 04 May 2026 08:07:51 GMT

In last 2 weeks number of registered APs to our WLC9800, 17.9.4a, is wrong.

Now we obtain 305, but on wlc dashboard we have 273.

I don't find any bug, have anyone ever had this issue?

Re: Wrong registered APs number from snmp query

Mark Elsen — Mon, 04 May 2026 08:12:39 GMT

- @gdspa I would suspect a bug ; note that 17.9.x is getting older and EOL ; consider using
a latest advisory release. You can also get a list of registered access points with :
WLC # show platform software dtls chassis active R0

Re: Wrong registered APs number from snmp query

Jonatan Jonasson — Mon, 04 May 2026 08:18:53 GMT

Is it possible that you're comparing the online/"operational" number from the WLC dashboard with the total number (online + offline + not-joined(disconnected)) from the SNMP query?

Re: Wrong registered APs number from snmp query

gdspa — Mon, 04 May 2026 08:50:50 GMT

I use oid 1.3.6.1.4.1.9.9.513.1.3.35.0

From wlc dashboard, joined APs are 273, not joined 79.

I know our version is old, we'll upgrade but we still have some 2700 APs, and I'd like to schedule upgrade after their renewal.

Re: Wrong registered APs number from snmp query

Mark Elsen — Mon, 04 May 2026 11:35:07 GMT

- @gdspa 17.12.6a will work for 2700 models.

Re: Wrong registered APs number from snmp query

gdspa — Mon, 04 May 2026 12:54:14 GMT

Here https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html it looks last version which supports 2700 is 17.12.3. Anyway, I was checking a version which fixes some bugs which cause random AP reboots.

Re: Wrong registered APs number from snmp query

Mark Elsen — Mon, 04 May 2026 12:57:47 GMT

- @gdspa Good remark ! And it is often made; 17.12.6a will work with the 2700 models. the compatibility
matrix was no longer updated after 17.12.3 because the later 17.12 versions where not
sufficiently back tested on the older models , but that has no impact.

Re: Wrong registered APs number from snmp query

gdspa — Mon, 04 May 2026 13:29:54 GMT

Ok, thanks. I'll try to force a failover to check if snmp wrong value will be fixed.

Re: Wrong registered APs number from snmp query

Mark Elsen — Mon, 04 May 2026 13:42:56 GMT

- @gdspa Ok, of course in HA SSO different versions cannot coexist. You can for instance download
and deploy the 9800 VM (CL) for free; with up to 50 access points without complaints about licensing.
That gives the opportunity to make a small lab for testing with future versions; but if done:
Do not deploy it on the same subnet as the main controllers, because access points will always
do a layer 2 capwap broadcast first; and you will loose control on which controller they will use for
joining

Re: Wrong registered APs number from snmp query

gdspa — Mon, 04 May 2026 14:20:19 GMT

I didn't share that snmp query wrong output started 1 day later after a reload of active wlc, this is why I'll try to change role, it should not change anything, but...

Re: Wrong registered APs number from snmp query

gdspa — Tue, 05 May 2026 16:40:43 GMT

After forcing a failover, and some minutes of disaster (web interface of active wlc was showing first install wizard and all ssids were down even if by ssh I could see all the config), and a phisical reload of both WLCs, now snmp value is correct again. Cisco bugs are always in ambush...

Re: Wrong registered APs number from snmp query

Mark Elsen — Tue, 05 May 2026 18:42:02 GMT

- @gdspa FYI : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwj73634
Another good reason to abandon the old 17.9.x and use one of the
Known Fixed Releases mentioned in the bug report.
In the meantime I would advise to copy the running configuration to
an external repository before doing an HA SSO failover (as an extra backup) ;
until you have upgraded