Problem with Regulatory Domain on pre-RD-change WLC and post-RD-change CAPWAP

[Dean Romanelli]

Hi All,

I have a problem.  Between the 1600/2600/3600 and 1700/2700/3700 generation of AP's, Cisco appears to have changed some of the regulatory domains-to-country-code mappings. My WLC is set to operate in -A and -N regulatory domains, and we have an existing 2602 CAPWAP also on -N domain.  This WLC and AP are both physically in India and have operated fine for years. However, we have just purchased a new 1702 CAPWAP from inside of India to add to this WLC, but the regulatory domain for India is now "-D," and as such, all of the 1700/2700/3700's for sale in India are -D's. As a result, my new capwap is not joining to the AP.  How do I fix this without needing to buy a new WLC or figure out how to get a "-N"capwap (now Mexico's code) into India?

[Flavio Miranda]

Hello,

 Did you try to and enable "Mexico" Regulatory domain?  I had WLC working with different Regularoty domains with no problems.

[Leo Laohoo]

The Regulatory Domain is mapped, via software, between the controller code and the Regulatory Domain of the AP.

So even if the AP is -N, as long as the country code is "India" it should work.

However, -A not the Regulatory Domain for India, regardless of model of AP.

If the AP is not joining the controller, console into the new AP and reboot. Post the entire boot up process of the AP. I would also like to see the complete output to the following commands:
1. WLC: sh sysinfo;
2. WLC: sh time;
3. AP: sh ip interface brief; and
4. AP: sh version

[Scott Fella]

I agree with what Leo mentioned here. You need to first make sure that the code supports the model access point you have and then you have to look for what code does that new regularly domain gets supported.  Yes you will need to add the country code to the list, but that's the easy piece. 

[Dean Romanelli · Accepted solution]

Hi All,

The problem was that the firmware on my WLC does not recognize the expansions made to the original 14 regulatory domains; -D being one of those expansions.  I upgraded the firmware on the WLC to the latest and now the new AP associates without an issue.

Thanks.