WLC 802.11a/n Radio Regulatory Domain Issue
Dear All
We are facing an issue with a customer where a Cisco 4400 Series controller is blocking the 802.11a/n Radio Interface of a 1250 AP. The radio shows as down on the controller GUI. The error message on the GUI is that the 'Regulatory Domain' is not supported. This can be seen from the attached screenshot. Also relevant parts of the WLC configs are attached.
WLC: Cisco 4402 Wireless
WLC Country: SA
Device: Cisco Lightweight Access Point 1250 (LAP) is controlled through the 4402 Cisco Wireless LAN Controller (WLC)
The operating system version of the LAP: c1250-k9w8-mx.124-18a.JA version of the WLC: Software Version 5.2.178.0
The problem is that the controller shows that the 802.11a/n Radio Interface in Radio Slot # 1 is always down , the customer tried to manually 'no shut' the AP interface from the console and it worked , but obviously this solution would not work as the configuration cannot be saved (LW AP).
Any help or pointers would be greatly appreciated.
Regards
Farrukh
Hello
This is sort of like a testbed setup, so can you tell me which country/reg domain I can set on my controller in order to make our access point work. There is only one AP connected to this controller.
LAP: AIR-AP1252AG-N-K9
Also as per the guide, we can configure the country on a per-AP basis, would this be a viable option?
http://www.cisco.com/en/US/docs/wireless/controller/5.2/configuration/guide/c52lwap.html#wp1147805
Regards
Farrukh
P.S I think South Africa is ZA
Similar Messages
-
RRM misconfiguration on 802.11a/n radio
I am working on tunneling a wireless network with the following components:
wlan-controller-14-4 impa-wireless4 --> AIR-WLC2106-K9
wlan-controller-14-2 impa-wireless2 --> AIR-WLC2106-K
11 AIR-LAP1131AG-A-K9
10 AIR-LAP1252AG-T-K9
They are geographically distributed on four floors in the same building.
Controllers and APs have the same sw version respectively.
I have configured RRM feature on both 802.11 a/n and 802.11 b/g/n
RRM feature on 802.11 b/g/n is working fine.
RRM feature on 802.11 a/n is unable to set different values for power conveniently.
All 1252 APs have been set to power equal 1.
Six Aps have been set to channel 149 even if they are neighbors (same floor or on correspondent position on other floors)
debugging client mac 50:cc:f8:86:80:7e I have gotten:
debug mac addr 50:cc:f8:86:80:7e *dot11a: Apr 07 16:39:36.537: Airewave Director: Processing Interference data on 802.11a AP 58:8D:09:1E:33:B0(1)
*dot11a: Apr 07 16:39:36.538: Airewave Director: Processing noise data on 802.11a AP 58:8D:09:1E:33:B0(1)
debug mac 50:cc:f8:86:80:7e*dot11a: Apr 07 16:39:36.540: Airewave Director: Processing Interference data on 802.11a AP 58:8D:09:1E:33:B0(1)
Any idea?
Tks RosaHello
This is sort of like a testbed setup, so can you tell me which country/reg domain I can set on my controller in order to make our access point work. There is only one AP connected to this controller.
LAP: AIR-AP1252AG-N-K9
Also as per the guide, we can configure the country on a per-AP basis, would this be a viable option?
http://www.cisco.com/en/US/docs/wireless/controller/5.2/configuration/guide/c52lwap.html#wp1147805
Regards
Farrukh
P.S I think South Africa is ZA -
WLC 4404 - Not able to see the 802.11a/n AP summary details
Hi Friends,
I have a query related to wireless. I have multiple WLCs in my network. Recently I observed that in one WLC, in monitoring page while we checking the access point summary information, I can see in 802.11a/n Radios, 8 APs are down. And I tried to see those details by clicking the ‘detail’ option over there, but no result was displaying. Same I have checked in ‘Wireless’ tab as well but the result was same. We have total 69 APs associated with this WLC. AP Models which are associated with this WLC are AIR-LAP1231G-A-K9 & AIR-LAP1242AG-A-K9. Firmware version running in the WLC is 7.0.235.3 which is recently upgraded.
Then I logged into multiple WLCs for checking the same. All these WLC are running with 7.0.116.0 code. In some APs I am able to see some AP information which is down for 802.11a/n Radios, for eg: if I have 18 APs down in a/n radio I can see 7 AP’s details. But can’t able to see all the AP information. For 802.11b/g/n Radios it is perfectly fine. And in these WLCs we have AIR-LAP1262N-N-K9 model also associated.
And one thing I noticed here is the number of APs that I can see the details is exactly same as the number of AIR-LAP1262N-N-K9 model APs associated with that WLC.
So can anyone confirm that the other 2 models won’t support a/n radios (hardware limitation) or is it any kind of bug in the firmware.
My WLC models are AIR-WLC4404-100-K9 & WS-SVC-WISM-1-K9
Thanks in advance for your time and response
Regards,
AnandHi Leo,
I am not able to identify the AP which are down for 802.11a/n radio :( (we are not using a/n radio in this location, that is why 8 out of 8 are showing down). -
Hi,
There are three different types of APs associated with controller and working fine.
1. AIR-LAP1252AG-E-K9
2. AIR-LAP1522AG-E-K9
3. AIR-CAP1552E-C-K9
WLC is AIR-CT5508-K9. Software version is 7.4.100.0. Field Recovery Image is 7.0.112.21. Firmware version is FPGA 1.7, Env 1.8, USB console 2.2. WCS is 7.0.240.0 for Windows.
WCS is sending alarms for AIR-LAP1522AG-E-K9:
Message: AP is unable to associate. The Regulatory Domain '-E' configured on interface '802.11a' does not match the Controller Regulatory Domain '-C'.
Before Controller was 7.2.4 (not sure).
Country configured on WLC is AE and shows -CE regulatory domain. Mesh APs are also associated.
I believe this Critical alarm should not come.
how much is this alarm important? What should be done to resolve this?Typically you still need to make sure that the country codes are indeed configured on the WLC. Thing can change when you upgrade code as standards might of changed and regulations also. If your AP's are functional, then you should be okay and I wouldn't worry too much about it, but if after the upgrade, the WLC complains about country code stuff, then you just need to verify that the AP's country code is defined on the WLC. May times the AP will not join and if it does join, the radios might be disabled or in a down status.
Sent from Cisco Technical Support iPad App -
AP1042 802.11a/n/ac Radios down in the controller
802.11b/g/n Radios is up but 8021.11a/n/ac radio is down. 802.11a netowrk status is already enabled. Not too sure what may most likely be causing it to down?
Below is the output of "show sysinfo" from the controller and "show version" from the AP
Any input is appreciated.
Thanks Cathy
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 8.0.100.0
RTOS Version..................................... 8.0.100.0
Bootloader Version............................... 8.0.100.0
Emergency Image Version.......................... 8.0.100.0
Build Type....................................... DATA + WPS
System Name...................................... wlc01
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1631
IP Address....................................... 172.20.0.102
IPv6 Address..................................... ::
System Up Time................................... 3 days 1 hrs 57 mins 9 secs
System Timezone Location......................... (GMT+10:00) Sydney, Melbourne, Canberra
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... AU - Australia
--More-- or (q)uit
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 2
Number of Active Clients......................... 1
Burned-in MAC Address............................ 00:0C:29:ED:49:8A
Maximum number of APs supported.................. 200
System Nas-Id.................................... Cisco_ed:49:8a
TestAP#show ver
Cisco IOS Software, C1040 Software (C1140-K9W8-M), Version 15.3(3)JA, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Fri 15-Aug-14 13:14 by prod_rel_team
ROM: Bootstrap program is C1040 boot loader
BOOTLDR: C1040 Boot Loader (C1140-BOOT-M) Version 12.4(23c)JA6, RELEASE SOFTWARE (fc1)
TestAP uptime is 40 minutes
System returned to ROM by power-on
System image file is "flash:/c1140-k9w8-mx.153-3.JA/c1140-k9w8-xx.153-3.JA"
Last reload reason:
cisco AIR-LAP1042N-A-K9 (PowerPC405ex) processor (revision A0) with 98294K/32768K bytes of memory.
Processor board ID FGL1707S3P4
PowerPC405ex CPU at 333Mhz, revision number 0x147E
Last reset from power-on
LWAPP image version 8.0.100.0
1 Gigabit Ethernet interface
2 802.11 Radios
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 00:06:F6:3B:A9:F7
Part Number : 73-14034-06
PCA Assembly Number : 800-34273-07
PCA Revision Number : A0
PCB Serial Number : FOC17015X6X
Top Assembly Part Number : 800-34285-05
Top Assembly Serial Number : FGL1707S3P4
Top Revision Number : A0
Product/Model Number : AIR-AP1042N-A-K9Configured Country............................... AU - Australia
WLC is configured for Australia (-N for AP1042).
Product/Model Number : AIR-AP1042N-A-K9
AP Regulatory Domain is for USA (-A).
This is the reason why your AP's 802.11a radio is permanently disabled. Unfortunately, the Wireless LAN Compliance Status (06 October 2014) doesn't list old-model APs. And this doesn't help anyone.
You may need to contact your vendor and ask them politely if it's possible for you to replace your AP with the ones with the correct Regulatory Domain. -
WLC 4402 & AP 3502i Regulatory Domain Mismatch
BACKGROUND: Access Point AP3502i successfully joins the WLC4402 (v 7.0.235.3) controller.
PROBLEM: AP3502i after boot and joining the WLC, shuts down both the Radios due to "Regulartory Domain MISMATCH"
ERROR:
AP on the 802.11a radio with Base Radio MAC xx:xx:xx:xx:xx:xx (AP1xxx.xxxx.xxxx) is unable to associate. The regulatory domain configured on it '-N' does not match the controller's regulatory domain: -A
AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:08:17:35:31:a9:d0 Cause=Radio reset due to Init. Status:NA
AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:08:17:35:31:a9:d0 Cause=Radio reset due to Init. Status:NA
To verify the Country & Regulatory Domains configured on WLC & AP, I check:
Under: Wireless->All APs->Details for APxxxx.xxxx.xxxx->Advanced Tab: Regulatory Domains: 802.11bg:-A 802.11a:-N
Under Wireless->Country---> ONLY US is CHECKED
It is clear that the WLC is setup for US Country; however, the AP is setup for US ONLY for 802.11bg AND MEXICO FOR 802.11a
WLC & AP are both located in US. Therefore, I need to update the AP Regulatory domain for US (-A) instead of Mexico (-N)
Question is, how do I update AP for US Regulatory Domain?
Any information would be greatly appreciated.Even adding country code to WLC (i.e: WLC Country Code is set/checked to US & Mexico (-A and -N), even then I get the same error and the result is that the radio is powered off on access points.
To re-sum the current status:
WLC Configured Country Codes: MX, US
WLC Regulatory Domain: 802.11a: -AN
802.11bg: -A
3502i Access Points Country Code: US
3502i Regulatory Domain: 802.11a:-N <<<-- This is the access point config that is causing the mismatch eventhough
802.11bg:-A WLC Regulatory domain show both US & Mex (-AN).
There's got to be way to change AP's Regulatory Domain. -
Need to admin disable 802.11a radio from a few light weight access points
Hi team,
I need help to admin disable the 802.11a radio interface from a few lightweight APs. The operational status of these radio interfaces is down, so I am getting the following error when I try to disable them from the wireless LAN controller.
(Cisco Controller) config>802.11a disable wds2.hyd.shaw.net
This slot is not operational because Regulatory Domain Check has failed! Unable to disable the Cisco AP.
Could you please let me know how I can administratively disable the 802.11a radios on these APs? Please let me know if you need more details here.
Regards,
SwatiThe two previous posts are correct: the regulatory domain is probably not allowing radio a to be enabled.
To be sure about this you can go to GUI of the wireless LAN controller > Wireless > Country. Here your country (or region) should be selected. Then depending on the access points that you have they may or may not join or turn on the radio. Per example if you have an access point from Europe (like AIR-AP1131AG-E-K9) then you will have a conflict if only the “America” regulatory domain (-A) is selected.
Here is a link with a list of products and their regulatory domain that might help:
http://tools.cisco.com/squish/648C8
What you can do here is to simply allow the regulatory domain that the access point needs and you should not have any problems.
IMPORTANT NOTE: If you change the regulatory domain and use an access point that transmit at certain channels and frequencies that are not allowed (illegal) in your country (region) you may have legal implications.
I hope this information helps you with your concern. -
Version 6.0.182 Australia Regulatory Domain 5 Gig radios OFF
Version 5 software all works OK
Upgrade to 6.0.128
5Gig radios all disabled with error
AP on the 802.11a radio with Base Radio MAC xx:xx:xx:xx:xx:xx (APxxx.xxxx.xxxx) is unable to associate. The regulatory domain configured on it '-A' does not match the controller's regulatory domain: -N
The controller is set to Australia
Configured Country Code(s) AU
Regulatory Domain
802.11a: -N
802.11bg: -A
The access point is a AIR-LAP1131AG-A-K9 (the one for Australia)
http://www.cisco.com/en/US/prod/collateral/wireless/ps5679/ps5861/product_data_sheet0900aecd80537b6a.html#wp9004368
all looks OK.
What has broken since version 5.0 I could and the country US to the county list and get around but I should not have to do this/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Tabla normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
Hi Charles,
I am also Cisco Network Engineer and found you on Cisco Support Community forum. I would like to ask you something in regards to one of your topics if you don’t mind. You mentioned that you would be doing the following “I would also be changing the polarization of the antenna to be 90 degrees off the existing one. IE rotate the antenna by 90 degrees“, have you done it already? What was the result of this and why would you do that? You see I have also a client with 2 Yagis pointing at each other with a distance around 2.5km and AIR-BR1310 bridges. What I am looking for it to get the signal strength better because it seems like now and then the non-root bridge disassociate itself from the root bridge due to weak signal. I heard that by turning both antennas by 90 degrees (changing polarization) clockwise or anticlockwise you can actually improve the signal strength, is that correct? How do you actually do that, by turning the tube in relation to the horizontal axis?
I would greatly appreciate you experience on that and ony other tips you would like to share with me.
Best regards,
Remi -
WiSM2 WLC 7.2 Maximum Allowed Clients under Global Parameters 802.11a/n b/g/n
Hello everyone,
Just loaded the 7.2.103.0 software onto the brand new WiSM2. Going throught the options and have found that under the global parameters for 802.11a/n, 802.11b/g/n radios is now the "Maximum Allowed Clients" option. The allowed setting is from 1 - 200 clients.
Does that mean only 200 clients will be allowed to associate to the WLC on that radio at a maximum?
Doesn't seems to make sense... I have the 500 AP license on this WiSM2... I know this option used to be an optional setting under a WLAN in previous releases.
Any ideas?
Regards,
Sasha.Does that mean only 200 clients will be allowed to associate to the WLC on that radio at a maximum?
As what Scott has responded, this means 200 clients per WAP.
If you do exceed 200 clients per WAP (or whatever value you put in there) the clients will just get a nag and the system will let you in eventually. -
Aironet 1400 bridge Radio 802.11a disable
I have some problem with 802.11A radio is enabled but the detaild status is still display software status is disabled and hardware status is down. I checked the settings on Enable Radio is checked on enable. I can't get any radio accross. Any ideas whereelse I can check to get this working?
speed basic-6.0 basic-9.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0
power local 18 <<<<<<<<<<< I can't input this line from the command line. I assume that the bridge is taking the MAX setting. Please helps.
power client 18
packet retries 128
station-role non-root
rts threshold 4000
rts retries 128
concatenation
beacon period 20
infrastructure-client
I am really appreciated that everyone can give me some helps.
Thanks
CDHi Jeff
I copy the configuration of the bridge. This is a new bridge that I setup as a role non-root bridge. with the new default configuration, as soon as I changed the role to non-root bridge, the 802.11A interface is down and disabled. Is it normal operation and how do I enable it back? any helps I am really appreciated that
Thanks
version 12.4
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
hostname NonRootBridge1
no logging console
aaa new-model
aaa group server radius rad_eap
aaa group server radius rad_mac
aaa group server radius rad_acct
aaa group server radius rad_admin
aaa group server tacacs+ tac_admin
aaa group server radius rad_pmip
aaa group server radius dummy
aaa authentication login default local
aaa authentication login eap_methods group rad_eap
aaa authentication login mac_methods local
aaa authorization exec default local
aaa accounting network acct_methods start-stop group rad_acct
aaa session-id common
resource policy
clock timezone MST -7
clock save interval 24
ip subnet-zero
ip domain name NonRootBridge1
dot11 activity-timeout bridge default 10000
dot11 ssid LabTest
vlan 51
authentication open
infrastructure-ssid
dot11 network-map
bridge irb
interface Dot11Radio0
no ip address
no ip route-cache
ssid LabTest
speed basic-6.0 basic-9.0 basic-12.0 basic-18.0 basic-24.0 basic-36.0 basic-48.0 basic-54.0
packet retries 128
station-role non-root bridge
rts threshold 4000
rts retries 128
cca 90
concatenation
beacon period 20
infrastructure-client
interface Dot11Radio0.51
encapsulation dot1Q 51 native
no ip route-cache
no snmp trap link-status
bridge-group 1
interface FastEthernet0
no ip address
no ip route-cache
interface FastEthernet0.51
encapsulation dot1Q 51 native
no ip route-cache
no snmp trap link-status
bridge-group 1
interface BVI1
ip address 192.168.0.10 255.255.255.0
no ip route-cache
ip http server
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
ip radius source-interface BVI1
radius-server attribute 32 include-in-access-req format %h
radius-server vsa send accounting
bridge 1 protocol ieee
bridge 1 route ip
line con 0
line vty 0 4
sntp server 192.168.0.50
sntp broadcast client
end -
Unstable Wireless Bridge Connection via 802.11a(Radio 1) of Aironet 1242
Hi,
I'm going to setup up an AP 1242 in a remote area to support b/g client via a 802.11a bridge link (all using AP 1242).
Before the deployment, I tested the configuration in a lab environment. However, I found the bridge link will come up a while and suddenly gone. Resetting the root AP or the non-root AP cannot bring the connection up again. Sometimes, when I shutdown the b/g radio (radio 0) of the remote AP, the bridge link will be established again. Following is the log from the root AP.
Thanks!
*Apr 4 12:24:05.013: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to r
eset
*Apr 4 12:24:05.054: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Apr 4 12:24:05.665: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0, changed state to down
*Apr 4 12:24:06.009: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio
1, changed state to up
*Apr 4 12:24:06.013: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio
0, changed state to down
*Apr 4 12:24:07.054: %LINK-3-UPDOWN: Interface BVI1, changed state to down
*Apr 4 12:24:16.091: %DOT11-4-CANT_ASSOC: Interface Dot11Radio0, cannot associa
te: No Response
*Apr 4 12:24:16.811: %LINK-3-UPDOWN: Interface BVI1, changed state to up
*Apr 4 12:24:17.811: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, chan
ged state to upInternal error: command failed <<<< Internal error: command failed ??????
<<<<don't know the meaning of this message
*Apr 4 12:27:22.206: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to r
eset
*Apr 4 12:27:22.233: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Apr 4 12:27:22.233: dot11_mgmt: bad cookie returned from driver for mac 003a.9 <<<<<003a.928.dad0 is radio 1 / non root bridge of remote AP
928.dad0(expected 0x00000000, got 0x010ADAB0) - force driver to delete client <<<<<don't know the meaning of this message
*Apr 4 12:27:22.235: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to r
eset
*Apr 4 12:27:22.262: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Apr 4 12:27:23.513: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0, changed state to up
*Apr 4 12:27:26.993: %DOT11-6-ASSOC: Interface Dot11Radio1, Station T9_QC168_Ca
ntil 003a.9928.dad0 Reassociated KEY_MGMT[NONE]
*Apr 4 12:27:28.465: %DOT11-4-MAXRETRIES: Packet to client 003a.9928.dad0 reach
ed max retries, removing the client
*Apr 4 12:27:28.465: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating
Station 003a.9928.dad0 Reason: Previous authentication no longer valid
*Apr 4 12:27:28.467: %DOT11-4-MAXRETRIES: Packet to client 003a.9928.dad0 reach
ed max retries, removing the client
*Apr 4 12:27:31.673: %DOT11-6-ASSOC: Interface Dot11Radio1, Station T9_QC168_Ca
ntil 003a.9928.dad0 Reassociated KEY_MGMT[NONE]
*Apr 4 12:27:32.687: %DOT11-6-ADD: Interface Dot11Radio1, Station 003a.9926.e76
0 Associated to Parent 003a.9928.dad0
*Apr 4 12:28:46.178: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating
Station 003a.9928.dad0 Reason: Sending station has left the BSS
*Apr 4 12:28:46.179: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating
Station 003a.9926.e760
*Apr 4 12:28:46.181: %DOT11-6-ASSOC: Interface Dot11Radio1, Station T9_QC168_Ca
ntil 003a.9928.dad0 Reassociated KEY_MGMT[NONE]
*Apr 4 12:28:47.196: %DOT11-6-ADD: Interface Dot11Radio1, Station 003a.9926.e76
0 Associated to Parent 003a.9928.dad0
*Apr 4 12:29:15.132: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthern
et0, changed state to down
*Apr 4 12:29:32.442: %DOT11-4-MAXRETRIES: Packet to client 003a.9928.dad0 reach
ed max retries, removing the client
*Apr 4 12:29:32.442: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating
Station 003a.9928.dad0 Reason: Previous authentication no longer valid
*Apr 4 12:29:32.443: %DOT11-6-DISASSOC: Interface Dot11Radio1, Deauthenticating
Station 003a.9926.e760
*Apr 4 12:29:32.444: %DOT11-4-MAXRETRIES: Packet to client 003a.9928.dad0 reach
ed max retries, removing the client
*Apr 4 12:31:10.285: %DOT11-4-CANT_ASSOC: Interface Dot11Radio0, cannot associa
te: Rcvd response from 003a.9928.2660 channel 6 2560
*Apr 4 12:31:18.286: %DOT11-4-CANT_ASSOC: Interface Dot11Radio0, cannot associa
te: AssociatingInternal error: command failed
*Apr 4 12:31:27.021: dot11_mgmt: bad cookie returned from driver for mac 003a.9
928.2660(expected 0x00000000, got 0x010ADAB0) - force driver to delete client
*Apr 4 12:31:29.107: %DOT11-4-UPLINK_ESTABLISHED: Interface Dot11Radio0, Associ
ated To AP T9_SML_LT2_AP2 003a.9928.2660 [None]
*Apr 4 12:31:29.108: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Apr 4 12:31:30.108: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio
0, changed state to upThanks dmantill for reminding me to revisit the antenna and related stuff.
As the setup is in a lab environment, the APs are put on a work bench next to each other, therefore, the radio output power was lowered.
After adjusting the output powers, it works as expected.
Thanks Surendra and dmantill. -
Issue connecting 1131AG - Regulatory domain check has failed for the AP
I have 2 1131AG LWAPP AP's purchased in the UK connecting to a WLC 5508 in the US that is setup only for Country US. I am getting the above error when trying to add Country GB United Kingdon I get an error that 802.11b and 802.11a are enabled and must be disabled to use this country code. I am not sure if there is a workaround for this because I do not want to disable these networks.
Here is the method to change country code:
GUI:
Step 1 Follow these steps to disable the 802.11a and 802.11b/g networks as follows:
a. Choose Wireless> 802.11a/n > Network.
b. Unselect the 802.11a Network Status check box.
c. Click Apply to commit your changes.
d. Choose Wireless > 802.11b/g/n > Network.
e. Unselect the 802.11b/g Network Status check box.
f. Click Apply to commit your changes.
Step 2 Choose Wireless > Country to open the Country page
Step 3 Select the check box for each country where your access points are installed. If you selected more than one check box, a message appears indicating that RRM channels and power levels are limited to common channels and power levels.
Step 4 Click OK to continue or Cancel to cancel the operation.
Step 5 Click Apply to commit your changes.
Step 6 Reenable the 802.11a and 802.11b/g networks
By CLI:
Before you can change the country code of a WLC, you must disable the 802.11a and 802.11b network :
>config 802.11a disable network
>config 802.11b disable network
Now you can change the country code of the controller. For example, we change it from US to IN (INDIA)
>config country GB
After changing the country,enable the 802.11 interfaces.
>config 802.11a enable network
>config 802.11b enable network
Regards
Dont forget to rate helpful posts. -
LAP1142 with different regulatory domains on each wireless
Hi, I wonder if anyone has come across this before:
We've seen an AIR-LAP1142-E-K9 wireless access point - one of a batch on the pre-used market although I understand that they have been simply removed from the original user - where the regulatory domain on each of the radios is different.
The 2.4GHz radio is 802.11bg:-E and the 5GHz radio is 802.11a:-A (as reported by the controller).
This is really strange as the AP shows itself to be the Product/Model Number : AIR-LAP1142N-E-K9
And the radio circuit board contains the circuitry for both radios so it's not that the wrong board has been installed for the A radio.
I don't know the software version that is running on the controller - and I've tried a bug search but that hasn't turned up anything useful (yet).
Has anyone here seen anything like this or offer any explanation?
Thanks in advance
RobinThat's what I thought, Scott, but I've had one of these to pieces and both radios are driven from the one circuit board...
I did wonder if there was a bug in the firmware level on the WLC but I don't have access to it to check. Especially since others from the same batch are reported to have worked without problems - we ourselves have had some - and they are reported to have worked fine in their original installation (these are pre-owned units).
Oh well, I guess this will remain a mystery. Thanks to everyone who replied.
Robin -
Is an AP got problem with multiple regulatory domain?
Hello,
Our customer in China reported that they got poor 2.4GHz wireless quality(i.e.slow response, slow data transfer). But these not happened on 5GHz band. The main WLC installed in Bangkok, Thailand. This controller take controll all their APs over the country and oversea branchs. We checked into the AP configurations and saw this..
Regulatory Domains: 802.11bg:-E 802.11a:-C
Country Code: CN (China)
AP Part: AIR-CAP2602I-C-K9
After we checked these tables
(http://www.cisco.com/en/US/prod/collateral/wireless/ps5679/ps5861/product_data_sheet0900aecd80537b6a.html#wp9005671)
All regulatory domains for this AP should be -C right?
We followed this page for configuring China country code.
(http://www.cisco.com/en/US/docs/wireless/controller/7.4/configuration/guides/lwap/config_lwap_chapter_010000.html)
I got noticed in guidelines and limitations
Although the controller supports different access points in different regulatory domains (countries), it requires all radios in a single access point to be configured for the same regulatory domain. For example, you should not configure a Cisco 1231 access point’s 802.11b/g radio for the US (-A) regulatory domain and its 802.11a radio for the Great Britain (-E) regulatory domain. Otherwise, the controller allows only one of the access point’s radios to turn on, depending on which regulatory domain you selected for the access point on the controller.
So, this should be a problem? or I hit a bug?
WLC information:
Part: AIR-CT5508-K9
Version: 7.3.112
Configured Country Code(s): TH,US,CN
Regulatory Domain: 802.11a: -ACE, 802.11bg: -ACE
Thank you.This is not a bug. Refer to Cisco TAC response.
Its not a bug, from the WLC you can run the command:
Show country supported tx-power
(WLC-5508-RAC1) >show country supported tx-power KEY: ## = Tx Power in dBm.
##*= Channel supports radar detection.
. = Channel is not legal in this country.
= Regulatory Domains allowed by this country.
(-,-) = (indoor, outdoor) regulatory Domains allowed by this country.
-----------------:+--+--+--+--+--+--+--+--+--+--+--+--+--+--
802.11BG :
Channels : 1 1 1 1 1
: 1 2 3 4 5 6 7 8 9 0 1 2 3 4
-----------------:+--+--+--+--+--+--+--+--+--+--+--+--+--+--
(-CE ,-CE ) AE : 20 20 20 20 20 20 20 20 20 20 20 20 20 .
(-A ,-AR ) AR : 27 27 27 27 27 27 27 27 27 27 27 . . .
(-E ,-E ) AT : 20 20 20 20 20 20 20 20 20 20 20 20 20 .
(-A ,-NA ) AU : 27 27 27 27 27 27 27 27 27 27 27 . . .
(-E ,- ) BA : 20 20 20 20 20 20 20 20 20 20 20 20 20 .
(-A ,- ) BB : 27 27 27 27 27 27 27 27 27 27 27 . . .
(-E ,-E ) BE : 20 20 20 20 20 20 20 20 20 20 20 20 20 .
(-E ,-E ) BG : 20 20 20 20 20 20 20 20 20 20 20 20 20 .
(-E ,- ) BH : 20 20 20 20 20 20 20 20 20 20 20 20 20 .
(-E ,- ) BN : 20 20 20 20 20 20 20 20 20 20 20 20 20 20
(-A ,-A ) BO : 27 27 27 27 27 27 27 27 27 27 27 . . .
--More-- or (q)uit
(-A ,-AR ) BR : 27 27 27 27 27 27 27 27 27 27 27 . . .
(-E ,- ) BY : 20 20 20 20 20 20 20 20 20 20 20 20 20 .
(-A ,-ABN ) CA : 27 27 27 27 27 27 27 27 27 27 27 . . .
(-A ,-ABN ) CA2: 27 27 27 27 27 27 27 27 27 27 27 . . .
(-E ,-E ) CH : 20 20 20 20 20 20 20 20 20 20 20 20 20 .
(-AER ,-AR ) CL : 20 20 20 20 20 20 20 20 20 20 20 20 20 .
(-E ,-E ) CM : 20 20 20 20 20 20 20 20 20 20 20 20 20 .
(-CE ,-CE ) CN : 20 20 20 20 20 20 20 20 20 20 20 20 20 .
And for 802.11a:
-----------------:+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--
802.11A : 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Channels : 3 3 3 4 4 4 4 4 5 5 6 6 0 0 0 1 1 2 2 2 3 3 4 4 5 5 6 6 6 7
: 4 6 8 0 2 4 6 8 2 6 0 4 0 4 8 2 6 0 4 8 2 6 0 9 3 7 1 5 9 3
-----------------:+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--
(-CE ,-C ) AE : . 23 . 23 . 23 . 23 23*23*23*23*30*30*30*30*30*30*30*30*30*30*30*23 23 23 23 23 . .
(-A ,-A ) AR : . 23 . 23 . 23 . 23 23*23*23*23*23*23*23*23*23* . . . 23*23*23*30 30 30 30 30 . .
(-E ,-E ) AT : . 20 . 20 . 20 . 20 20*20*20*20*27*27*27*27*27*27*27*27*27*27*27* . . . . . . .
(-NZ ,-NZ ) AU : . 23 . 23 . 23 . 23 23*23*23*23*30*30*30*30*30*30*30*30*30*30*30*30 30 30 30 30 . .
(-E ,- ) BA : . 20 . 20 . 20 . 20 20*20*20*20*27*27*27*27*27*27*27*27*27*27*27* . . . . . . .
(-N ,- ) BB : . 23 . 23 . 23 . 23 23*23*23*23* . . . . . . . . . . . 30 30 30 30 30 . .
(-E ,-E ) BE : . 20 . 20 . 20 . 20 20*20*20*20*27*27*27*27*27*27*27*27*27*27*27* . . . . . . .
(-E ,-E ) BG : . 20 . 20 . 20 . 20 20*20*20*20*27*27*27*27*27*27*27*27*27*27*27* . . . . . . .
(-E ,- ) BH : . 20 . 20 . 20 . 20 20*20*20*20*27*27*27*27*27*27*27*27*27*27*27* . . . . . . .
(-S ,- ) BN : . 20 . 20 . 20 . 20 20*20*20*20* . . . . . . . . . . . 30 30 30 30 30 . .
--More-- or (q)uit
(-A ,-A ) BO : . 23 . 23 . 23 . 23 23*23*23*23*23*23*23*23*23* . . . 23*23*23*30 30 30 30 30 . .
(-T ,-AN ) BR : . . . . . . . . . 17*17*17*27*27*27*27*27*27*27*27*27*27*27*30 30 30 30 30 . .
(-I ,- ) BY : . 20 . 20 . 20 . 20 20*20*20*20* . . . . . . . . . . . . . . . . . .
(-A ,-ABN ) CA : . 23 . 23 . 23 . 23 23*23*23*23*23*23*23*23*23* . . . 23*23*23*30 30 30 30 30 . .
(-A ,-ABN ) CA2: . 23 . 23 . 23 . 23 23*23*23*23*23*23*23*23*23* . . . 23*23*23*30 30 30 30 30 . .
(-E ,-E ) CH : . 20 . 20 . 20 . 20 20*20*20*20*27*27*27*27*27*27*27*27*27*27*27* . . . . . . .
(-SA ,-A ) CL : . 20 . 20 . 20 . 20 20*20*20*20*27*27*27*27*27*27*27*27*27*27*27*30 30 30 30 30 . .
(- ,- ) CM : . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(-C ,-C ) CN : . . . . . . . . . . . . . . . . . . . . . . . 23 23 23 23 23 . .
So from that you can confirm that for 802.11bg you can use E and C regulatory domains. -
802.11a/g/n optimizing for compatibility
How to ensure maximum client compatibility and stability in 802.11a/b/g/n networks?
I am running a Wireless network based on the WLC 5508 6 SW version, (with WCS mgmt) and 1142 APs. I would like a broad variety of clients, old G clients and new N clients to experience a stable connection to the network. I see Apple Macbooks, Lenovo-, Dell- and HP laptops in addition to HTC smartphones and iPhones on this network.
I am having issues with some types of clients experiencing "unstable" connections. They are able to get a link for a variable ammount of time, then suddenly loose connection for a short period of time before reconnecting. These clients mostly use a third party SSL-VPN link over my wireless, therefore the loss of connection can be quite annoying. From time to time some of these clients seem to be flapping between access points but not seamless like roaming should be, rather with a short stop in connectivity before reconnecting.
Previously we had a 802.11g Aruba wireless network in the same location. It had no such difficulties. This points me toward the config parametres in the controller.
Which 802.11 b/g/n and WLAN parameters can affect this? I am looking for a document describing a best practice for setting up these parameters, or if someone here has input to a successful stable setup as the configuration guide only says e.g. "Enable if you want Aironet Information Elements" does not help in deciding if I want this
My WLAN is set up with WPA2/AES PSK
and a guest network with web auth
Examples of parameters:
which Radio policy (bgn or gn)
Aironet IE?
MFP (disabled or enabled)
QoS profile?
can CCX location measurement affect performance?
Which Data rates should be set mandatory/enabled/disabled?
MCS (data rate) settings for 802.11n
anything I have forgotten?
The goal is:
A simple, no hassle network providing maximum compatibility with different clients with a plus of 802.11n speeds for compatible clients
wbr
-LAHey! I implemented your suggested improvements and the first impression is good!
on 802.11a and b/g I disabled lower datarates, set 12Mbps to mandatory and the higher ones to supported. The instant improvement was the RTT measurements I made (previously they averaged at about 13ms (to an internet site) after the change they dropped to about 3-4 ms on average! I would say this is a very significant improvement!
I have not been able to get any feedback from the user community yet :), but it sounds promising...
I am still looking for some more insight into these issues, so if someone still has some ideas, please let us know!
-LA
Maybe you are looking for
-
Need advice on multiple imac repairs
hi all i bought my imac a few years ago its a white intel 17 inch imac i have been having alot of problems with it for the past 8 months its had 3 logic boards replaced in last 7 months the most recent being 2 weeks ago and now i am getting same prob
-
Firefox should display .swf and .flv files without Adobe. You can do it can't you?
If the program, 'Media Player Classic' can play .swf and .flv files, the surely Firefox programmers can do for those what was done for .pdf files. PLEASE!
-
Cannot unzip .zip even with Archive Utility
Hi, I have problem unzipping a .zip file. When I use the Archive Utility to unzip it, it yields a file with the same name with .zip.cpgz on its end. When I subsequently make another trial - to unzip this new file, it yields the very same file only wi
-
Data Structure of ReFS file system
Hi All Is there anyone who can explain Data Structure of ReFS file system Regards
-
I am unable to export from cs6 bridge to facebook.
Error message "An error occurred while request facebook connection. "