Trouble getting 3502I to register to a 4402

[Jeff Bull]

I have 2 3502I WAP's in my London office that i'm trying to register to our Amsterdam 4402 WLC. They were able to successfully pull DHCP from a local switch, including option 43, and did register with my controller yesterday. As per the normal process, the controller pushed an updated image to each, and the WAP's reboot. After the reboot, they are stuck in an endless loop of trying to call the ap-manager interface, not the Management interface, so are failing to register.

As of now, i'm at a loss as to how to correct this. Is there a compatibility issue with the image that was pushed? Is there a way to push a different image, with the correct IP?

Please see the attachment for the repeating logs on the CLI of one of the WAP's.

Any ideas/help would be greatly appreciated.

Jeff Bull

[Leo Laohoo]

Can you do a "sh inventory" on the WAP?

[Jeff Bull]

Sure thing...

NAME: "AP3500", DESCR: "Cisco Aironet 3500 Series (IEEE 802.11n) Access Point"

PID: AIR-CAP3502I-A-K9 , VID: V01,

[Leo Laohoo]

PID: AIR-CAP3502I-A-K9 , VID: V01,

Didn't you say your controller has European domain?

The "A" is AMERICAN domain.

That's easy enough fix!  You can enable the "A" domain in your controller.  I don't have a WLC at home so I couldn't sing out where to find it.

[Scott Fella]

That’s what I mentioned earlier, but don’t really know the country code there and if that can work.

[Jeff Bull]

Not sure how to tell...here's the inventory info from my controller

Model No.	AIR-WLC4402-12-K9
Burned-in MAC Address	00:27:0D:DF:18:00
Maximum number of APs supported	12
Gig Ethernet/Fiber Card	Absent
Crypto Accelerator 1	Absent
Crypto Accelerator 2	Absent
Power Supply 1	Present,Operational
Power Supply 2	Present,Operational
FIPS Prerequisite Mode	Disable
UDI :
Product Identifier Description	AIR-WLC4402-12-K9
Version Identifier Description	V04
Serial Number
Entity Name	Chassis
Entity Description	4400 Series WLAN Controller:12 APs

[Scott Fella]

You can run the cli command on the wlc.

show country

show country supported

[Leo Laohoo]

Using the GUI to Configure Country Codes

See if adding the "A" to your controller will fix it.

NOTE:  At least NOW we have a headway to the issue.

[Jeff Bull]

You were both correct. I just added the US country codes to the list, and both AP's immediately connected.

Thank you all for your patience and help with this. I sincerely appreciate it!

[Leo Laohoo]

Cool!  Glad to see it's finally working.

By the way, why do you have "A" domain WAP for your Amsterdam office?

If this is a mistake by the local distributor, return the WAP back to them.

[Scott Fella]

Just make sure you don’t’ get in trouble in case you’re not supposed to be using that US ap over there.

[Scott Fella]

Sometimes the ap still seems to keep the bad info:) One way to really make sure you clear the config is to console into the ap and issue:

debug capwap console cli

config t

erase /all nvram:

Then reboot

[Carl Harbeck]

Was this ever actually fixed? I am having the same issue and am thinking I need to RMA the device.

[Stephen Rodriguez]

Yes, the initial issue was resolved.  THe issue was a mismatch in regulatory domain between the AP and the WLC.

Can you open a new thread with your issue?

Steve

[Leo Laohoo]

Was this ever actually fixed? I am having the same issue and am thinking I need to RMA the device.

Yes it was, Carl.  The culprit was the regulatory domain of the WAP ("A" domain) and the controller (Amsterdam) didn't match.