Lightweight APs used with WLC

After reading the Cisco documentation, it seems that the Lightweight AP's are reduced to ceiling/wall decorations when the WLC is off the network or otherwise unreachable. Is this true? Do they provide for no client connectivity whatsoever if the WLC fails? Does all client traffic pass from a LAP to the WLC before being sent to it's destination? In particular this is in regards to 1142n APs and an 5508 WLC.
Thanks!

it seems that the Lightweight AP's are reduced to ceiling/wall decorations when the WLC is off the network or otherwise unreachable.
Not entirely true. Depending on your design, you can configure H-REAP.
H-Reap Design and Deployment Guide
http://www.cisco.com/en/US/customer/products/ps6087/products_tech_note09186a0080736123.shtml
H-REAP Modes of Operation Configuration Example
http://www.cisco.com/en/US/customer/tech/tk722/tk809/technologies_configuration_example09186a00807cc3b8.shtml
Hybrid Remote Edge Access Point (H-REAP) Basic Troubleshooting
http://www.cisco.com/en/US/customer/tech/tk722/tk809/technologies_tech_note09186a008081103d.shtml
Hope this helps. Please don't forget to rate useful posts. Thanks.

Similar Messages

Cannot use IP-phone-7921 with EAP-Fast using internal WLC Radius

Hello,
I Cannot authenticate IP-phone when I use internal WLC-radius with a profile "eap-fast"
The eror message I recieved on a debug is:
*Mar 09 03:15:09.765: Unable to find requested user entry for anonymous
But of course there is a user configured on my ipphone !
Note1 : I use a WLC with version : AIR-4400-K9-5-1-163-0 (AES)
Note2: When I use LEAP it is OK
Note3: When I try with my PC to autenticate in eap-fast with internal WLC radius, it is OK.
See attacehement for more detail.
Many thanks in advance.
Michel Misonne
*Mar 09 03:15:09.765: Unable to find requested user entry for anonymous

ABSOLUTLEY DO NOT DO THIS!
config advanced eap identity-request-timeout 120
config advanced eap identity-request-retries 20
config advanced eap request-timeout 120
config advanced eap request-retries 20
This can cause you issues for up to 40 minutes. 20 attempts * 2 minutes apart
Please take a look at
https://supportforums.cisco.com/docs/DOC-12110
config advanced eap identity-request-timeout 5
config advanced eap identity-request-retries 12
config advanced eap request-timeout 5
config advanced eap request-retries 12
would be much better, as it is only 60 seconds. No device should take longer than 5 seconds to respond, but sometimes the phones need more than the 1 second default.
HTH,
Steve

Trouble using Oracle with WLCS

Hi,
I am trying to use Oracle 8.1.7 with WLCS 3.5 on Linux.
I am getting the error:
java.sql.SQLException: System.loadLibrary threw java.lang.UnsatisfiedLinkError
with the message 'no weblogicoci37 in java.library.path'.
Any help?
Thanks,
- Sougata

if you still want to use the OCI driver, make sure the library in your error
message is in the LD_LIBRARY_PATH,
otherwise, switch to the thin driver from Oracle and it will work without
any libraries
Filip
~
Namaste - I bow to the divine in you
~
Filip Hanik
Software Architect
[email protected]
www.filip.net
"Sougata Mukherjea" <[email protected]> wrote in message
news:3baa34b8$[email protected]..
>
Hi,
I am trying to use Oracle 8.1.7 with WLCS 3.5 on Linux.
I am getting the error:
java.sql.SQLException: System.loadLibrary threwjava.lang.UnsatisfiedLinkError
with the message 'no weblogicoci37 in java.library.path'.
Any help?
Thanks,
- Sougata

Register APs at remote site with WLCs at the core via Metro E.

All,
I have problem with register APs at the remote site with WLCs at the core.
All of my WLCs are on main site; and the majority of APs are on same subnet and same site with the WLCs. This works just fine.
However I have a remote site with connected to the core via metro E. And I am unable to make the APs at this site register to the controllers at the core.
On remote site APs and PCs are on subnet. And PCs are work just fine. I have the DHCP scope options 43 set for the ip address of the WLCs.
Metro E interfaces are on 192.168.0.0 /24.
Clients (PCs and APs) at remote are on 192.168.56.0 /24
I have the configuration on the Metro E and and remote site on the attachment.
Thank in advantage.

To get APs registered, make sure AP is getting an ip address and can ping WLC
Once this is verified, run the following debugs on WLC CLI and attach it to the thread:
- debug mac addr
- debug capwap OR lwapp events enable
- debug capwap OR lwapp errors enable
- debug pm pki enable
To stop debug
- debug disable-all
In case you have 'console' access to remote site AP, capture AP boot up and then run "debug ip udp" on AP CLI
To stop this debug
AP# undebug all

Client get connected occationally with WLC 5508

Hi ,
I have one strange problem on wireless connection.
I just upgraded several 1131 APs to LAP with 2 new Cisco 5508 controller deployed, and we found the clients sometime can get conneted to the 1131 AP, and connection well, sometimes cannot. during our test, one conecion is ok, next one cannot, the third one seems ok again and again.
And we also have 2 new 1140 APs, seems no such problem,
The version for controller is 6.0.196.0, and Client is Lenevo PC with XP.
Any suggestion? or some troubleshooting procedure I can follow?
Thanks!
Roy

Thanks!
Seems some problem with open authentication.
On the Client, it reported cannot get associated.
on the WLC, while I am debug client it reports:
*Jul 14 10:18:51.844: 00:1f:3c:c2:e9:71 Sending Assoc Response to station on BSSID c4:7d:4f:47:a5:c0 (status 12)
*Jul 14 10:18:51.889: 00:1f:3c:c2:e9:71 Ignoring 802.11 assoc request from mobile pending deletion
*Jul 14 10:18:51.889: 00:1f:3c:c2:e9:71 Sending Assoc Response to station on BSSID c4:7d:4f:47:a5:c0 (status 12)
*Jul 14 10:18:51.928: 00:1f:3c:c2:e9:71 Ignoring 802.11 assoc request from mobile pending deletion
*Jul 14 10:18:51.928: 00:1f:3c:c2:e9:71 Sending Assoc Response to station on BSSID c4:7d:4f:47:ae:b0 (status 12)
*Jul 14 10:18:52.446: 00:1f:3c:c2:e9:71 apfMsExpireCallback (apf_ms.c:418) Expiring Mobile!
*Jul 14 10:18:52.446: 00:1f:3c:c2:e9:71 apfMsExpireMobileStation (apf_ms.c:4427) Changing state for mobile 00:1f:3c:c2:e9:71 on AP c4:7d:4f:47:ae:b0 from Associated to Disassociated
I am using remote radius with WLC only.
The strange thing is, when get connected, it looks fine, but I tried disconnect manually, then connect again, it reported cannot get associated, then I try again, it can get connect again,....

An issue with WLC 5508 and 7921 phone

Hello all!
I have a system with WLC 5508 and some 1242 APs. And I use a lot of 7921 phones.
One of 7921 phones was in trouble. It loses registration, disconnect conversations...
I installed the trial WLC and run voice diagnostics.
I saw some of "Potentially degraded QoS in downlink direction because of incorrect packet classification" messages and one "Fair upstream packet loss ratio: 1,2%, which is less than threshold 2.5%"
As I understand all of 7921 phones in these area are affected.
what does it mean? I set up Platinum QoS for voice WLAN. I don't have any qos configuration string for AP and WLC ports on switches...
any ideas?
thanx in advance

Sergey:
There is one application called "WLC Config analyzer". You save your "show run-config" from your WLC in a text file and import it by this application. it will analyze the file for you and tell you what recommendations for voice are missing so you improve them.
When importing a config file you choose what voice clinets you are using, so you need to choose cisco 7921 to it tells you what config improvemetns is needed based on 7921 needs.
Here is the link to download the application:
https://supportforums.cisco.com/docs/DOC-1373
download the latest versoin.
BTW, how many voice/data clients are connected to one AP in that area? if I remember correctly if you are utilizing voice then the max number of clients connected to one AP should not exceed 17. If you have more than this number per AP try to minimize the number of users concurrently connected to the AP then try again.
Hope you'll find the config analyzer useful.
If useful please don't forget to rate.
Amjad

Mesh & Remote AP with WLC

Dears
I have 4 WLCs,3 are active and one is backup Controller with AIR-LAP1522HZ-E-K9
So mesh technology i need i-e- One Rap will be connected through ethernet and 5 MAPs will be through wireless with 100 meter radius and start topology.RAP will be in the middle and MAPs arround the RAP as per my understanding.
I saw a documentaion in which we have to use the mac filter option.But at the same time RAP will be act as MAP.What are the options like for RAP we will say you are RAP and MAP and for MAP we will just instruct that you are MAP only and have to communicate with RAP.
Is there any step by step documentation or any suggestion from forum?
Can any one suggest for Option43 and Option 60? and what if we define DHCP on WLC we need options or not ?
For Remote Failiver which parameters we have to consider
Second i have to use Air Magnet.can some one suggest from forum?
Advance Thanks to All

Hi there!
The first thing you need to do is put mac addresses of all the APs (RAP and MAPS) in the MAC filtering list of WLC (Using GUI is easier for this). Now you have to get ur APs registered to WLC first before you can declare them RAP or MAP (Default setting is MAP so u need to declare only RAP). There are many ways to get APs registered to the controller, I would share the following two:
1. Priming the APs:
connect ur primary controller to a switch and connect all the APs (RAPs and MAPs) to the same subnet (preferably the same switch). Once you have put all the MACs in WLC, the APs will join controller in few minutes. When an AP joins the controller, access it using the gui of the controller and put necessary information like controller IPs and gateway (if u intend to put ur RAP in a different subnet than WLC). Save the configuration and reboot the APs. repeat the procedure for all APs. now the APs are ready to be placed in the network.
2. Using DHCP option 43 and 60:
This procedure is an alternate to priming. Here u prepare ur DHCP server before you connect ur APs in the network. You have to define a few strings and go through some steps. (cisco website has a very good documents available for the details)
Answering ur question you cannot define these DHCP options on WLC. Reason is when the APs boots for the first time, it needs to find the controller and by default, it generates request to the DHCP server on the network (See AP booting sequence for details). When we configure DHCP option 43 and 60, we actually place the controller IP address in the DHCP messages for the APs to find WLC. so configuring DHCP 43 on WLC is just like calling someone on phone to get one's phone number (in short, it wont work)

Extend the same WLAN using more WLCs

I have a bit of a question,
We already have one 50 AP WLC 4402 in our organization, and currently we have ran out of the 50 AP license. Issue is we want to extend the WLAN to another area but because of the 50 AP max on our WLC we are faced with getting another 50 AP WLC.
My question is can we extend the SAME WLANs using another WLC. I know it will work for the WLC fail-over but not sure if using another WLC will give us the mobility/roaming feature throughout the organization we want. Do we needto go for WCS as well in this situation to deploy organization wide roaming?. Basically is there a way to make existing WLC and new one act like the same WLAN with roaming throughout or will using two WLCs be separate roaming domains.
Please advice. Thanks.
Cheers
Lal Antony
www.lalantony.com

Hi Lal,
Yes it is possible and works awesome!! here is the mobility link which gives you more info as well.. but in short for your question that you have.. We can extend the WLAN and there is no problen at all..
http://www.cisco.com/en/US/docs/wireless/controller/7.0/configuration/guide/c70mobil.html
My other suggestion will be to go for a WLC which supports more APs.. so that in future if we wanna extend the network, then there wont be any issues..
lemme know if this answered your question..
Regards
Surendra
====
Please dont forget to rate the posts which answered your question and mark it as answered or was helpfull

Help me : Problem with WLC and AP

Hi,
We have a few AP on our network which work fine.
But, those which are behind our fw don't work.
LAN WI-FI with WLC <>--------Lan Routed---with Ap (Ok) ------------------
<> -------FW <> Vlan behind Fw and APs not work fine.
WLC = Software Version 7.0.220.0
Logs on WLC :
spamApTask2: Jun 04 11:49:59.494: %DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:631 Failed to complete DTLS handshake with peer 172.37.251.71
*spamApTask1: Jun 04 11:48:49.323: %DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:631 Failed to complete DTLS handshake with peer 172.37.251.71
*spamApTask2: Jun 04 11:47:39.149: %DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:631 Failed to complete DTLS handshake with peer 172.37.251.71
*spamApTask1: Jun 04 11:46:28.978: %DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:631 Failed to complete DTLS handshake with peer 172.37.251.71
*spamApTask2: Jun 04 11:45:18.806: %DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:631 Failed to complete DTLS handshake with peer 172.37.251.71
*spamApTask1: Jun 04 11:44:08.632: %DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:631 Failed to complete DTLS handshake with peer 172.37.251.71
*osapiBsnTimer: Jun 04 11:43:51.235: %DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:2202 Failed to complete DTLS handshake with peer 172.37.251.71
debud dtls :
*spamApTask1: Jun 04 11:22:42.434: 64:a0:e7:5f:e5:70 record=Alert epoch=0 seq=2
*spamApTask1: Jun 04 11:22:42.435: 64:a0:e7:5f:e5:70 SSL_do_handshake: SSL_ERROR_SSL while communicating with 172.37.251.71 : (null)
*spamApTask1: Jun 04 11:22:42.435: 64:a0:e7:5f:e5:70 Requested by openssl_dtls_process_packet
*spamApTask1: Jun 04 11:22:42.435: dtls_conn_hash_delete: Deleting hash for Local 172.18.3.2:5246 Peer 172.37.251.71:52258
*spamApTask1: Jun 04 11:22:42.435: 64:a0:e7:5f:e5:70 DTLS Connection 0x145520d0 closed by controller
*spamApTask1: Jun 04 11:22:42.436: dtls_conn_hash_search: Searching hash for Local 172.18.3.2:5247 Peer 172.37.251.71:52258
Cordially,

HI,
- On the fw-
a. Make sure the FW is open for udp 5246 and 5247 ports required for the capwap process.
If this is a cisco ASA, you can set up ingress and egress packet captures to see what packets enter and leave the FW for this AP-
cap capin interface match udp any
cap capout interface match udp any
**match captures bidirectional flow for the interesting traffic.
b. Check the logs on the firewall for any drops.
c. cap capdrop type asp-drop all
This will tell you if the pkt was dropped and the reason for the drop
d. You can run the packet-tracer command on the firewall tracking this udp flow-
e.g. packet-tracer input inside udp 3.3.3.3 1212 2.2.2.3 5246 detailed
- What AP model is this? Is it the same AP that connects to the controller if there is no fw in the path?
- Does it use MIC or SSC cert? If SSC, make sure you have SSC checked and you will need to manually enter the hash for the AP on the controller under AP Authorization List -
Security> AP Policies
You can get the hash of the AP (f you dont have it) by enabling the following debug on the controller
debug pm pki enable
Other controller debugs for the AP-
debug mac address
debug capwap error enable
debug capwap events enable
- What about AP console log? Do you have access to that?

Help required with WLC software upgrade

I have a customer with WLC 4402 in use, running software version 7.0.98.0, and supporting 11 APs at present. The customer wants to enlarge the WLAN, which involves increasing the number of APs. I have purchased a new WLC5508, and have installed it onto the network alongside the 4402. the 5508 is running software version 7.0.116.0. Because the wireless network is critical to the user, we want to move the APs over to the new controller while the network is up and running, then remove the 4402.
However, when we set the 5508 as the master controller, or tell one of the APs to use the 5508 as its primary controller, the AP connects to the new controller, downloads the new software version, attempts to load it but reports an error with the unzipped file size of the software and fails to boot. formatting the flash on the AP, then disconnecting the 5508 from the network and rebooting the AP allows it to connect to the 4402, it downloads the older software and boots as normal. A new AP, if connected to the 5508 in a test scenario (ie no 4402) connects, downloads and boots perfectly.
I have the upgrade software to allow the 4402 to be upgraded to 7.0.116.0, but I am concerned that, if this is installed, the existing APs will then fail to boot from the 4402 or the 5508.
all APs are 3502s, running IOS version 12.04(23c)JA when connected to the 4402 and 12.04(23c)JA2 on the 5508.
Any suggestions would be gratefully received
Thanks

Hi Pat,
thanks for the reply. I am off site until the morning, but will attach the colsole output tomorrow.
Your mentioning a corrupt image makes me wonder - we had a lot of trouble setting up the initial config on the new WLC, getting a lot of launch failures. Eventually things seemed to settle down (it certainly booted successfully first time this morning) and getting an AP to connect without a problem made me hope it was just a quirk of the configuration wizard, but I think I will try a reboot of the WLC before I do anything else, just to check it is stable.
If it is a corrupt image it may take a little while to sort, as we have not as yet got a support contract on the 5508 - the plan was to upgrade the existing contract on the 4402 once they were swapped out, but I'll let you know whats going on
Rob

LWAPP assocoation with WLC

hi,
m lwapp cisco 1242ag is not getting associted with wlc.
it is giving following logs in console of AP -
%LWAPP-3-CLIENTEVENTLOG: Performing DNS resolution for CISCO-LWAPP-CONTROLLER
%LWAPP-3-CLIENTERRORLOG: DNS Name Lookup: could not resolve CISCO-LWAPP-CONTROLL
ER
pls help on this.

http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00808f8599.shtml
Check that link
What you should try
clear lwapp or capwap private config
clear nvram
If still no go,
MAke sure that DHCP is proving domain name and DNS ip address
If it still does not join, convert it to aIOS and then clear nvram and then convert back again to lightweight using the latest RCVK image or lightweight ios and see if it works
if not try this:
debug lwapp console cli
debug capwap console cli
AP(config)# ip domain name company.com
AP(config)# ip name-server
Let us know how did you go

VLAN concept with WLC

Hi guys,
This is my VLAN background:
VLANs are used to segment the network and break up the broadcast domains in order to reduce congestion and isolate network problems as well as providing scalability, performance improvement, security and making network additions, moves, and changes easier and more manageable.
And this is my wireless VLAN background with the controllers:
Host A is a wireless LAN client communicating with the wired device, Host B. At the access point, the access point adds an LWAPP Header to the frame and send it to the controller. After processing the 802.11 MAC Header by WLC, it extracts the payload (the IP packet), encapsulates it into an Ethernet frame, and then forwards the frame onto the appropriate wired network, typically adding an 802.1Q VLAN tag.
According to Cisco's "Fundamentals of Wireless Controllers" video (starting at 2:53), the 5508 controller allows you to use much larger subnets and less wireless VLANs. So with a 5508 controller in a completely wireless infrastructure (no wired hosts),
1. I don't need to break up broadcast domains and have multiple subnets and I'm free to use a giant flat network?
2. If I'm allowed to use large subnets, as far as the broadcast traffics (other than ARP and DHCP which are specially handled by WLC) are concerned, how does the controller handle that? I think I still will need multiple VLANs to control them according to my following WLC broadcast handeling background:
"All traffic including broadcast sent to any destination by wireless client get forwarded to WLC from its connected AP. WLC places the broadcast message on to that VLAN, both wired and wireless clients that are part of that vlan interface will get this broadcast message. Now, the receiving wireless clients on that vlan can be associateded on to any/different APs, APs mapped to different AP groups, even APs using different L3 addresses from one or multiple WLCs, WLC inteligently identifies the mapped VLAN interfaces and its respective APs through AP group and forwards the broadcast(encapsulates) as Multicast packet to those specific AP groups. Once APs receives the Multicast(broadcast), it places it on the respective Radio's BSSID(where WLAN/ssid mapped) of AP to reach the right wireless client. AP Radio's BSSID to SSID/WLAN to interface mapping is pushed to AP by WLC at AP join. Also, Wired PCs will receive the broadcast on its vlan as tagged(if tagged, otherwise untagged) from WLC's interface, so does the other WLCs that spans this vlan interface."
Regards,
Saman

You should still follow your best practice for your subnet size. Remember that wireless is half duplex and only one device can talk at a given time. Also... The AP can be in a different vlan, ap group, etc, but the clients are still on the same vlan. So it means that the clients need to be on the same vlan, but the AP's can be on a different subnet since this doesn't matter.
Sent from Cisco Technical Support iPhone App

How-do-i-configure-guest-wifi-access-using-2504-wlc-fortigate-utm-l3-device

Dear All
I have a 2504 Wireless Controller with multiple radios attached. I currently have a "private" WLAN configured (taking ip from windows server based DHCP of Range 192.1681.0/24 ) and working, but I need to add a Guest/Public WLAN which should take the IP from Other DHCP Configured on Fortigate UTM of range 172.16.0.0/24.
We have one SG300 switch in the office and the rest are basic switches.
Our firewall/router is a Fortigate UTM 240D
Find the attached network diagram for the issue.
Is there a SIMPLE way to enabling guest access that doesn't require VLANS (or are VLANS easier than I'm making them)?
Thanks.
- See more at: https://supportforums.cisco.com/discussion/12473186/how-do-i-configure-guest-wifi-access-using-2504-wlc-fortigate-utm-l3-device#sthash.aj1XcWI0.dpuf

Complete these steps in order to configure the devices for this network setup:
http://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-vlan/70937-guest-internal-wlan.html
Configure Dynamic Interfaces on the WLC for the Guest and Internal Users
Create WLANs for the Guest and Internal Users
Configure the Layer 2 Switch Port that Connects to the WLC as Trunk Port

ISE device registration webauth with wlc 7.0 lwa

Is it possible to use the DRW feature with WLCs running 7.0 code? All configuration examples refer to 7.2 code. Its only for guest user device registration. No profiling / provisioning.
Compatibility matrix says that "Wireless Controllers support MAC filtering with RADIUS lookup. For WLCs that support version 7.2.103.0, there is support for session ID and COA with MAC filtering so it is more MAB-like."
Thanks.

Hi,
The reason you need to run the upgraded code is that the radius NAC feature coupled with a mac-filtering enabled SSID will work together. On the release prior you were unable to get both features to work with one another.
For your reference here is the item in the New Features section of the 7.2 WLC release notes:
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn7_2.html#wp855314
thanks,
Tarik Admani
*Please rate helpful posts*

Troubleshoot Cisco Airlap 1242 with WLC 4400 Series LWAPP_CLIENT_ERROR_DEBUG: spamHandleCfgReqTimer: Did not recieve the Config response

I have a Problem with my new AIRLAP 1242 to connect with WLC 4400
after debug in my airlap it shows :
Reset done!
ethernet link up, 100 mbps, full-duplex
Ethernet port 0 initialized: link is up
Loading "flash:/c1240-k9w8-mx.123-7.JX8/c1240-k9w8-mx.123-7.JX8"...######################################################################################################################################################################################################################################
File "flash:/c1240-k9w8-mx.123-7.JX8/c1240-k9w8-mx.123-7.JX8" uncompressed and installed, entry point: 0x3000
executing...
              Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
           cisco Systems, Inc.
           170 West Tasman Drive
           San Jose, California 95134-1706
Cisco IOS Software, C1240 Software (C1240-K9W8-M), Version 12.3(7)JX8, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2007 by Cisco Systems, Inc.
Compiled Mon 19-Mar-07 01:42 by hqluong
Image text-base: 0x00003000, data-base: 0x004051E0
Initializing flashfs...
flashfs[1]: 9 files, 3 directories
flashfs[1]: 0 orphaned files, 0 orphaned directories
flashfs[1]: Total bytes: 15998976
flashfs[1]: Bytes used: 5062144
flashfs[1]: Bytes available: 10936832
flashfs[1]: flashfs fsck took 4 seconds.
flashfs[1]: Initialization complete....done Initializing flashfs.
cisco AIR-LAP1242AG-E-K9   (PowerPCElvis) processor (revision A0) with 24566K/8192K bytes of memory.
Processor board ID FCW1411U0FZ
PowerPCElvis CPU at 266Mhz, revision number 0x0950
Last reset from power-on
1 FastEthernet interface
2 802.11 Radio(s)
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 68:EF:BD:5F:9A:18
Part Number                          : 73-10256-07
PCA Assembly Number                  : 800-26918-06
PCA Revision Number                  : A0
PCB Serial Number                    : FOC14093XU3
Top Assembly Part Number             : 800-29152-03
Top Assembly Serial Number           : FCW1411U0FZ
Top Revision Number                  : A0
Product/Model Number                 : AIR-LAP1242AG-E-K9
Press RETURN to get started!
*Mar 1 00:00:05.608: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed
*Mar 1 00:00:06.858: %DOT11-2-VERSION_INVALID: Interface Dot11Radio0, unable to find required radio version 581.18
*Mar 1 00:00:06.858: Interface Dot11Radio0, Accepting as a test version of radio firmware
*Mar 1 00:00:06.878: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0
*Mar 1 00:00:07.234: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar 1 00:00:08.212: %DOT11-2-VERSION_INVALID: Interface Dot11Radio1, unable to find required radio version 581.18
*Mar 1 00:00:08.212: Interface Dot11Radio1, Accepting as a test version of radio firmware
*Mar 1 00:00:08.232: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1
*Mar 1 00:00:09.278: %SYS-6-LOGGERSTART: Logger process started
*Mar 1 00:00:09.326: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1240 Software (C1240-K9W8-M), Version 12.3(7)JX8, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2007 by Cisco Systems, Inc.
Compiled Mon 19-Mar-07 01:42 by hqluong
*Mar 1 00:00:09.332: %CDP_PD-4-POWER_OK: Full power - AC_ADAPTOR inline power source
*Mar 1 00:00:09.388: %DOT11-6-FREQ_SCAN: Interface Dot11Radio0, Scanning frequencies for 32 seconds
*Mar 1 00:00:10.271: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up
*Mar 1 00:00:10.332: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Mar 1 00:00:10.332: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:00:11.271: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to up
*Mar 1 00:00:28.331: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
*Mar 1 00:00:28.361: %DOT11-6-FREQ_USED: Interface Dot11Radio0, frequency 2462 selected
*Mar 1 00:00:28.362: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 1 00:00:28.363: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 1 00:00:28.369: %DOT11-6-FREQ_USED: Interface Dot11Radio1, frequency 5260 selected
*Mar 1 00:00:28.372: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:00:28.398: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:00:28.399: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar 1 00:00:28.465: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:00:29.398: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 1 00:00:29.465: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
Translating "CISCO-LWAPP-CONTROLLER.ekahospital.com"...domain server (202.134.0.155)
*Mar 1 00:00:38.351: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned DHCP address 172.31.xxx.xxx, mask 255.255.255.0, hostname AP68ef.bd5f.9a18
*Mar 1 00:00:38.820: %DOT11-6-FREQ_USED: Interface Dot11Radio0, frequency 2417 selected
*Mar 1 00:00:38.827: %DOT11-6-FREQ_USED: Interface Dot11Radio1, frequency 5200 selected (203.130.196.5)
*Mar 1 00:00:49.835: %DOT11-6-FREQ_USED: Interface Dot11Radio0, frequency 2422 selected
*Mar 1 00:00:49.842: %DOT11-6-FREQ_USED: Interface Dot11Radio1, frequency 5220 selected
*Mar 1 00:00:49.851: %LWAPP-5-CHANGED: LWAPP changed state to JOIN
*Mar 1 00:00:49.852: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Mar 1 00:00:49.852: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Mar 1 00:00:50.852: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:00:50.852: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Sep 18 07:02:25.504: %LWAPP-5-CHANGED: LWAPP changed state to CFG
*Sep 18 07:02:29.288: LWAPP_CLIENT_ERROR: lwapp_name_lookup - Could Not resolve CISCO-LWAPP-CONTROLLER.MYDOMAIN.com
*Sep 18 07:02:30.504: LWAPP_CLIENT_ERROR_DEBUG: spamHandleCfgReqTimer: Did not recieve the Config response
*Sep 18 07:02:30.551: %SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Reason: DID NOT GET CONFIG RESPONSE.
*Sep 18 07:02:30.551: %LWAPP-5-CHANGED: LWAPP changed state to DOWNXmodem file system is available.
flashfs[0]: 9 files, 3 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 15998976
flashfs[0]: Bytes used: 5062144
flashfs[0]: Bytes available: 10936832
flashfs[0]: flashfs fsck took 26 seconds.
Base ethernet MAC Address: 68:ef:bd:5f:9a:18
Initializing ethernet port 0...
Reset ethernet port 0...
Reset done!
and after that i check in my WLC that shows
AP with Base Radio MAC xx:xx:xx:xx:xx:xx (APxxxx.xxxx.xxxx) is unable to associate.
The reulatory domain configured on it '-e' does not match the controller's country
code: USA
i found that the problem about the region.
question :
1. is it possible to change the region in AIRLAP 1242 or in WLC?
2. if possible how to change it?
INFO :
my first AIRLAP Product/Model Number : AIR-LAP1242AG-A-K9 and my new AIRLAP Product/Model Number : AIR-LAP1242AG-E-K9

WLC GUI >> Wireless >> Country >> Select the country.
Regards
Surendra

Lightweight APs used with WLC

Similar Messages

Maybe you are looking for