01-08-2014 07:20 AM - edited 07-04-2021 11:55 PM
Hi all,
I just purchase 3 AIR-CAP1552E-x-K9 for outdoor wifi purpuse i want to add them in wirless controller, i dont want to use them as mesh AP. I just want to configure them so that client can get wifi access and these all APs manage by Wireless Controller 2504.
Solved! Go to Solution.
01-09-2014 04:25 AM
HI Zohaib,
Add the MAC address of the MAP to the MAC filter table. In order to do this, choose security > AAA > Mac Filtering > Mac Address
Here is the full CLI command syntax:
(WLC) >config macfilter add
Once you do this your AP should register to WLC in mesh mode. Then you can convert it to local mode via WLC GUI or CLI.
Here is the CLI way of doing it
(WLC) >config ap mode local submode none
Reagrds.
01-09-2014 04:53 AM
GUI Way:
Wireless> All APs click on specific AP then gerneral tab you will see the AP mode, there you can change to local.
Here is the CLI way of doing it
(WLC) >config ap mode local submode none
Regards
01-08-2014 11:50 AM
HI Zohaib,
First paste the output of the command
from WLC: sh sysinfo
from AP: sh inventory
Regards
01-09-2014 04:03 AM
Sorry for late reply i just reached in my office
AP189c.5d8e.2a60>sh inventory
NAME: "AP1550", DESCR: "Cisco Aironet 1550 Series (IEEE 802.11n) Access Point"
PID: AIR-CAP1552E-N-K9 , VID: V04, SN: FTX1751P0FK
>sh sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.5.102.0
Bootloader Version............................... 1.0.18
Field Recovery Image Version..................... 1.0.0
Firmware Version................................. PIC 16.0
Build Type....................................... DATA + WPS
System Name...................................... WLC
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1279
IP Address....................................... 192.168.30.4
Last Reset....................................... Power on reset
System Up Time................................... 22 days 21 hrs 12 mins 53 secs
System Timezone Location.........................
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
--More-- or (q)uit
Configured Country............................... AU - Australia
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +24 C
External Temperature............................. +30 C
Fan Status....................................... 3800 rpm
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 2
Number of Active Clients......................... 24
Burned-in MAC Address............................ 50:17:FF:27:23:20
Maximum number of APs supported.................. 50
01-09-2014 04:14 AM
HI Zohaib,
Did you connected these APs to edge or core swicth or somewhere in your network??
A lightweight AP joins a controller via DHCP, DNS or broadcast. You don't add them or anything on the controller, you setup your systems to provide the IP address of the controllers and then the AP joins it. Best and easiest way is to use DHCP.
Check your DHCP scopes to see if there's a option 42 with the controller address.
How to add Lightweight Access point to Wireless LAN Controller
https://supportforums.cisco.com/docs/DOC-5711
Regards
01-09-2014 04:22 AM
Thanks for your reply but i can see on log AP is getting IP from DHCP and Ip or controller but not adding what configuration i have to do at my controller to joins these new Mesh APs
Both Controller and APs are on LAN switch
01-09-2014 04:31 AM
Logs at AP:
*Jan 9 16:11:28.535: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.30.4
% CDP is not supported on this interface, or for this encapsulation
*Jan 9 16:12:22.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.30.4:5246
*Jan 9 16:12:23.039: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Jan 9 16:12:33.095: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jan 9 16:12:33.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.30.4 peer_port: 5246
*Jan 9 16:12:33.535: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.30.4 peer_port: 5246
*Jan 9 16:12:33.535: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.30.4
*Jan 9 16:12:33.539: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Jan 9 16:12:33.539: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Jan 9 16:12:33.539: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Jan 9 16:12:33.539: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 192.168.30.4
*Jan 9 16:12:38.535: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.30.4
01-09-2014 04:19 AM
Logs at AP:
*Jan 9 16:11:28.535: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.30.4
% CDP is not supported on this interface, or for this encapsulation
*Jan 9 16:12:22.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.30.4:5246
*Jan 9 16:12:23.039: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Jan 9 16:12:33.095: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jan 9 16:12:33.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.30.4 peer_port: 5246
*Jan 9 16:12:33.535: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.30.4 peer_port: 5246
*Jan 9 16:12:33.535: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.30.4
*Jan 9 16:12:33.539: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Jan 9 16:12:33.539: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Jan 9 16:12:33.539: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Jan 9 16:12:33.539: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 192.168.30.4
*Jan 9 16:12:38.535: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.30.4
01-09-2014 04:25 AM
HI Zohaib,
Add the MAC address of the MAP to the MAC filter table. In order to do this, choose security > AAA > Mac Filtering > Mac Address
Here is the full CLI command syntax:
(WLC) >config macfilter add
Once you do this your AP should register to WLC in mesh mode. Then you can convert it to local mode via WLC GUI or CLI.
Here is the CLI way of doing it
(WLC) >config ap mode local submode none
Reagrds.
01-09-2014 04:48 AM
Thank you so much sandeep but can u explain how i can convert it to local mode via GUI
01-09-2014 04:53 AM
GUI Way:
Wireless> All APs click on specific AP then gerneral tab you will see the AP mode, there you can change to local.
Here is the CLI way of doing it
(WLC) >config ap mode local submode none
Regards
01-09-2014 04:36 AM
Did you tried to add MAC address of mesh AP to controller ??
Please add the MAC address and let me know.
If still you have the problems then boot the AP and put the entire bootprocess here.
Regards
Dont forget to rate helpful posts.
01-09-2014 05:58 AM
Thanks its works
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: