AP Invalid country code () when joining the controller

[luceroc]

I have some 1131 access points that refuse to join the controller and respond with errors pertaining to country code problems. The problem seems to be a hard one to nail down since I have installed about 75 of these all from the same shipment but only about 10 have failed. And it looks like some failed right away but others later on in the build out.

2- 4404 controllers ver-4.2.130.0

1131 LAps which appear to be "A" america coded.

** One thing that I found strange is that on one of the ones I have replaced, I was able to download the latest version of IOS upgrade code and it allowed it to join the first time and upgrade the code from the controller but after that got the same errors. I've seen the other posts about setting the time and checking for the country code on the controllers but that is not it.

Mon Jan 19 15:11:57 2009: 00:1f:9e:8f:e7:1e Successful transmission of LWAPP Join Reply to AP 00:1f:9e:8f:e7:1e

Mon Jan 19 15:11:57 2009: 00:1f:9e:8f:e7:1e spam_lrad.c:1766 - Operation State 0 ===> 4

Mon Jan 19 15:11:57 2009: 00:1f:9e:8f:e7:1e Register LWAPP event for AP 00:1f:9e:8f:e7:1e slot 0

Mon Jan 19 15:11:57 2009: 00:1f:9e:8f:e7:1e Register LWAPP event for AP 00:1f:9e:8f:e7:1e slot 1

Mon Jan 19 15:11:57 2009: spamVerifyRegDomainSlot: AP 00:13:c4:f3:a9:60(slot 1) unsupported radio type 0XFF.

Mon Jan 19 15:11:57 2009: spamVerifyRegDomainSlot: AP 00:1f:9e:8f:e7:1e(slot 0) unsupported radio type 0XFF.

Mon Jan 19 15:11:57 2009: spamVerifyRegDomainSlot: AP 00:1f:9e:8f:e7:1e(slot 1) unsupported radio type 0XFF.

Mon Jan 19 15:11:57 2009: spamVerifyRegDomainSlot: AP 00:13:c4:f3:a9:60(slot 1) unsupported radio type 0XFF.

Mon Jan 19 15:11:57 2009: spamVerifyRegDomainSlot: AP 00:1f:9e:8f:e7:1e(slot 0) unsupported radio type 0XFF.

Mon Jan 19 15:11:57 2009: spamVerifyRegDomainSlot: AP 00:1f:9e:8f:e7:1e(slot 1) unsupported radio type 0XFF.

Mon Jan 19 15:11:58 2009: 00:1f:9e:8f:e7:1e Received LWAPP CONFIGURE REQUEST from AP 00:1f:9e:8f:e7:1e to 00:1d:45:5e:89:8b

Mon Jan 19 15:11:58 2009: 00:1f:9e:8f:e7:1e AP 00:1f:9e:8f:e7:1e: Invalid country code ().

Mon Jan 19 15:11:58 2009: spamVerifyRegDomainSlot: AP 00:1f:9e:8f:e7:1e(slot 0) unsupported radio type 0XFF.

Mon Jan 19 15:11:58 2009: spamVerifyRegDomainSlot: AP 00:1f:9e:8f:e7:1e(slot 1) unsupported radio type 0XFF.

Mon Jan 19 15:11:58 2009: 00:1f:9e:8f:e7:1e AP 00:1f:9e:8f:e7:1e: Invalid country code ().

Mon Jan 19 15:11:58 2009: spamVerifyRegDomainSlot: AP 00:1f:9e:8f:e7:1e(slot 0) unsupported radio type 0XFF.

Mon Jan 19 15:11:58 2009: spamVerifyRegDomainSlot: AP 00:1f:9e:8f:e7:1e(slot 1) unsupported radio type 0XFF.

Mon Jan 19 15:11:58 2009: 00:1f:9e:8f:e7:1e Updating IP info for AP 00:1f:9e:8f:e7:1e -- static 0, 10.240.242.101/255.255.255.0, gtw 10.240.242.1

Mon Jan 19 15:11:58 2009: 00:1f:9e:8f:e7:1e Updating IP 10.240.242.101 ===> 10.240.242.101 for AP 00:1f:9e:8f:e7:1e

Mon Jan 19 15:11:58 2009: 00:1f:9e:8f:e7:1e AP 00:1f:9e:8f:e7:1e: Invalid country code ().

Mon Jan 19 15:11:58 2009: 00:1f:9e:8f:e7:1e AP 00:1f:9e:8f:e7:1e not allowed to join. Regulatory Domain check failed.

Allowed regulatory domain: 802.11bg:-AB 802.11a:-AB

Mon Jan 19 15:11:58 2009: 00:1f:9e:8f:e7:1e apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 00:1f:9e:8f:e7:1e slot 0

Mon Jan 19 15:11:58 2009: 00:1f:9e:8f:e7:1e apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 00:1f:9e:8f:e7:1e slot 1

[Leo Laohoo]

Can you console into the AP with the wrong country code and enter the command

clear lwapp private-config

Does this help?

[luceroc]

No this did not help. I was able to "downgrade" the unit to autonomous which showed the lack of functioning radios at the CLI. I have always had such great luck with Cisco access points that I hardly take hardware failure out of the box as an option but it might be just that. Thanks for the help!

[schmij01]

I am almost positive that is the error I have seen on 1131s where the AP has failed radio units. Boot one up with a console cable attached and watch the log messages. If the radios are bad, you'll see a log message like "No radio in slot 0".

I have been seeing a failure rate of 10% out of our most recent 1131 deployment with this problem.

[luceroc]

I think you're right. As per the last response- I tried to downgrade it to automonous and saw the lack of radios. At this time I'm contacting TAC to get replacements. I'm a little concerned about QC on the 1131 line since I have just installed over 100, I've got about 5 so far so hopefully I don;t creep closer to your experience of 10% failure rate. Thanks for the feedback,

Regards

[Stephen Rodriguez]

the AP should be fine. The error:

Allowed regulatory domain: 802.11bg:-AB 802.11a:-AB

Is indicating that the WLC is not configured with the country code "B". I don't remember off the top of my head what country that is, for some reason I'm thinking Mexico, but you can play with the country setting on the WLC to see what matches up.

So long as you are running 4.1 or beyond, you should be able to allow multiple country codes for AP's to join with, but be advised that the AP will join the first code it matches. For example, you have a -E AP. And you have Belgium and Germany allowed. The AP would join as Belgium, and then under the specific radio you can specify which regulatory domain you want it to use.

HTH,

Steve