topic Can you do the following in Wireless

-B Regulatory Domain access point will not join WLC properly

rsherman — Mon, 05 Jul 2021 12:38:41 GMT

Does anyone know how to join -b regulatory domain access points to a controller properly? I have a 2504 running 8.2.121.0, a known firmware release that supports -b access points. I cannot get the AP's to download the firmware and register properly. They stay up for a few minutes and then reboot repeatedly. I do not currently have console access to them. Do these need primed like the universal AP's do?

Hello,

George Stefanick — Tue, 16 Aug 2016 13:12:30 GMT

Hello,

Yes they need to be primed in a special way so that the ap learns the country code.

http://www.cisco.com/c/en/us/td/docs/wireless/access_point/ux-ap/guide/uxap-mobapp-g.html

That said only B domain access points can share country codes with other B domain access points. Once you have one enabled keep it close to configure others.

******************************************************************************

HTH

Please rate helpful post!

www.my80211.com - Blog by a WiFi engineer for WiFi engineers

www.wifitraining.com/about-wifi/ - WiFi Training by hands on WiFi Engineers, Experts and Cisco Wireless VIPs

Thanks for the reply!

rsherman — Tue, 16 Aug 2016 14:08:45 GMT

Thanks for the reply!

So just to clarify, you prime a B domain access point, the same way you do a universal?

You know what I was

George Stefanick — Tue, 16 Aug 2016 14:14:37 GMT

You know what I was responding to two post and I mis typed here. My apologies. No if its a B domain you do not have to have it learn the country code.

What access point model is not joining ?

AIR-CAP2702e-B-K9

rsherman — Tue, 16 Aug 2016 14:26:07 GMT

AIR-CAP2702e-B-K9

Can you do the following

George Stefanick — Tue, 16 Aug 2016 14:41:09 GMT

Can you do the following debug ob the WLC while the AP joins and drops off ?

debug lwapp events enable

I have attached the debug. We

rsherman — Tue, 16 Aug 2016 14:57:08 GMT

I have attached the debug. We are specifically looking at the 2 access points that are 10.0.20.101 and 10.0.20.102. I have a primary and secondary controller, running the same config and code.

I dont see the attachment ..

George Stefanick — Tue, 16 Aug 2016 14:58:15 GMT

I dont see the attachment ..

Sorry about that, clicking

rsherman — Tue, 16 Aug 2016 15:09:59 GMT

Sorry about that, clicking the upload button would help....

You see this

George Stefanick — Tue, 16 Aug 2016 15:39:58 GMT

You see this

*spamApTask4: Aug 16 11:26:40.050: apType: Ox26 bundleApImageVer:

It should show an ap image but it doesn't. Im not sure why. But can you reboot the WLC and if that doesn't work any way you can update to the latest code.

I did, but honestly, I wasn't

rsherman — Tue, 16 Aug 2016 15:45:17 GMT

I did, but honestly, I wasn't sure what it meant.

It is currently running the latest code 8.2.121.0, and has been rebooted multiple times.

I have had it on the latest 8

rsherman — Tue, 16 Aug 2016 15:45:58 GMT

I have had it on the latest 8.0 code and now the latest 8.2 code, and have not had luck with either image.

Let me poke around.

George Stefanick — Tue, 16 Aug 2016 16:10:38 GMT

Let me poke around.

From the monitor screen take

George Stefanick — Tue, 16 Aug 2016 19:25:38 GMT

From the monitor screen take a screen shot of your version of code.

Here you go!

rsherman — Tue, 16 Aug 2016 20:55:22 GMT

Here you go!

Try to upgrade to v8.3. I

Scott Fella — Wed, 17 Aug 2016 03:29:43 GMT

Try to upgrade to v8.3. I have some -A with a -B running at home. I did have v8.2.100.0 when the 3802 -B joined my controller. Its hard to say what the issue is without console access. You have other AP's joined to the controller?

-Scott

Scott,

Fri, 09 Sep 2016 03:55:57 GMT

Scott,

I have the same issue. All -B AP's are able to join a WLAN controller is running 8.0.133 code. At second location, 3 -b AP's couldn't join a WLAN controller with same 8.0.133 code.

Eric,

Leo Laohoo — Fri, 09 Sep 2016 04:28:55 GMT

Eric,

Create a new thread for your issue.

Eric,

Scott Fella — Fri, 09 Sep 2016 04:31:27 GMT

Eric,

Try to point the discovery to a controller that -B have joined. It might be the version of AP in which you might need 8.0.135.0

-Scott

*** Please rate helpful posts ***

I was seeing this same issue

jjeffries — Fri, 09 Sep 2016 13:31:56 GMT

I was seeing this same issue with three 3702i-B APs trying to join a WiSM2 and a 5508 WLC. Two of them were RMA'd to Cisco to investigate a flash problem that was seen when I was able to obtain remote console to them. The third was snapped out of its boot loop when I had a local contact do a mode reset on the AP after I had upgraded the controller to 8.0.133. I didn't obtain console access to this one as I expected it to the same problem, so I can't say what the cause actually was. Both Controllers were running 8.0.120 and were upgraded to 8.0.133. I saw the same issue on both WLC versions with those APs.