12-22-2012 08:28 PM - edited 07-03-2021 11:16 PM
Hi all,
Need suggestions and guidance.
I want to install new APs with Australian standards as per model number:
AIR-LAP1142N-N-K9
We are using below process to register any new IP, but this time it does not allow and its not visible in WLC WLANs tab.
1. We go to gui WLC and open security --> AP policies, and add a new MAC address.
2. In the switch the APs are already visible in cdp neighbor and getting the IP addresses from DHCP scope.
3. We go to WLANs tab and add the APs in to the required group. But this time the APs are not visible.
4. Out of 15 Aps of same model, 2 are registered properly.
Pl. guide what could be the reason for this.
We have 100APs license and in Security policies we have added more than 100 mac. Is this the reason which cause the problem to register any new APs.
pl. find logs below:
A. From Switch CDP neighbor details:
--------------------------------------------------------
Device ID: APe02f.6d5b.e2f3
Entry address(es):
IP address: 10.3.173.163
Platform: cisco AIR-LAP1142N-N-K9 , Capabilities: Router Trans-Bridge
Interface: GigabitEthernet3/6, Port ID (outgoing port): GigabitEthernet0.1
Holdtime : 131 sec
Version :
Cisco IOS Software, C1140 Software (C1140-RCVK9W8-M), Version 15.2(2)JA, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Thu 23-Aug-12 04:49 by prod_rel_team
advertisement version: 2
Duplex: full
Power drawn: 14.500 Watts
Power request id: 9551, Power management id: 3
Power request levels are:14500 0 0 0 0
Management address(es):
B. Wireless Controller details as below:
==============================
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 6.0.196.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS
System Name...................................... (Hidden for reason)
System Location.................................. TS AU Primary Data Centre
System Contact................................... Sam Tse
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
IP Address....................................... (Hidden for reason)
Last Reset....................................... Software reset
System Up Time................................... 593 days 16 hrs 35 mins 38 secs
System Timezone Location......................... (GMT+10:00) Sydney, Melbourne, Canberra
Current Boot License Level....................... base
Current Boot License Type........................ Permanent
Next Boot License Level.......................... base
Next Boot License Type........................... Permanent
--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............................. +37 C
External Temperature............................. +18 C
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 2
3rd Party Access Point Support................... Disabled
Number of Active Clients......................... 34
Burned-in MAC Address............................ 88:43:E1:63:57:C0
Power Supply 1................................... Present, OK
Power Supply 2................................... Present, OK
Maximum number of APs supported.................. 100
Pl. suggest for solution and troubleshooting steps. We want to resolve it as soon as possible as its new project and is critical.
Kalpesh Modi
Solved! Go to Solution.
12-23-2012 08:13 AM
Here is my 2 cents... Adding the MAC address for each ap is crazy. It's only really required for mesh. If you don't have authorize ap from Mac filter or auth list (something like that) adding the MAC address is useless.
Here is a link to how you get an ap to join a WLC. I usually prime/stage the AP's on the same subnet as the WLC. Once the ap joins, I canoe the ap to any subnet.
https://supportforums.cisco.com/docs/DOC-5711
Sent from Cisco Technical Support iPhone App
12-22-2012 08:36 PM
Hi Kalpes,
Verify if you are able to ping the AP from its gateway.
If so console to the AP and issue below command on command prompt.
capwap ap controller ip address
where IP-address is the managment ip address on the WLC. This command let your wireless AP know which ip address the controller is availble for it to register.
Also verify the configuration
show capwap ip config
Regards
Najaf
12-22-2012 08:50 PM
Console into the WAP and reboot.
Post the entire bootup process.
12-22-2012 10:34 PM
We are getting the ping response for the AP from Switch and also from the desktop in the network.
But not able to get its entry in the WLC after we had already added in to Security - AP policies.
Not able to connect the console to the AP right now, as working remotely. Tomorrow it can be possible.
But let us know if any command we can give on WLC to check further today.
Regards,
Kalpesh
12-22-2012 11:33 PM
Hi Kalpesh,
You could try below command to see if the AP is actually trying to regsiter with the WLC.
debug mac addr(in xx:xx:xx:xx:xx format) debug client
&
debug lwapp event
This command provides information on the LWAPP events and errors that occur during the LWAPP discovery and join process.
Hope that helps.
Regards
Najaf
12-23-2012 01:41 AM
Hi Najaf,
No output is comming after we gave the above two commands.
We are now stuck with this problem. Pl. help us out. Most probably tomorrow we may be in a position to provide you all the logs. Please let me know for the troubleshooting steps, which we can take from our side.
Regards,
Kalpesh
12-23-2012 02:09 AM
We go to gui WLC and open security --> AP policies, and add a new MAC address.
This is the first time I've ever heard somebody using this. Are you sure you entered the correct MAC address?
12-23-2012 02:32 AM
Hi,
Since the ap has ip address, are you able to telnet or ssh into it?
You could try power cycle (if you are using Poe switch please shut and no shut the switch port to power cycle device) while issuing those two comments on the controller.
More likely your ap does not know the WLC ip address and hence you are not able see any ap registration logs on controller. I would recommend try consoling to ap and issuing capwap ap controller ip address tomorrow when u have physical access to the device.
Sent from Cisco Technical Support iPhone App
12-23-2012 07:59 AM
Hi
, what is the correct or common procedure to add a fresh new AP and get it registered with WLC. Should we do it via commmand line or via GUI. Which is most commonly used.
Pl. let us know the correct procedure, if we are doing any mistake.
Thanks and regards,
Kalpesh
12-23-2012 12:37 PM
Hi Kalpesh,
I agree with Scott's post when he stated this (below):
Adding the MAC address for each ap is crazy.
Turn that feature off and add the WAP.
Let me know what you get from the outputs I've requested.
12-24-2012 10:10 PM
Thanks to all of you for the support provided.
The investigation and resolution was as below for this case.
1. Logged in to the controller with ssh
tried giving below commands
debug mac addr
debug capwap events enable
debug event errors enable
show debug
there was no log igenerated to the the WLC.
Suspected AP was not able to find the WLC.
studied the document and understood the process, it was happening because AP did not have the knowledge of WLC IP address to which it is must to contact.
There are two ways to do this.
1. We can add WLC IP to the AP by cli command logging in to AP by console - not feasible in our case as due to christmas less staff available and dependency on remote hands and feet.
2. Can enable DHCP option 43 and provide WLC IP in the configuration of scope itself.
We have enabled DHCP option 43 in the Wireless management Scope with Single wlc IP in Hexadecimal. Process is as below to enable DHCP option 43
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00808714fe.shtml
for a Single WLC IP to be entered below is the entry code we have done in DHCP scope:
0000 F1 04 xx xx xx xx
(Line number - type F1 - 04 because of single WLC, if two WLC need to enter, we can user 2*4 =8, will result in F1 08)
(Last four xx xx xx xx is the actual IP address of the WLC converted to HexaDecimal Value)
All the APs were visible in WLC and registered and configured.
This was the first time I have registered in Support forum cisco and got extreme support. you guys are Awesome.
Regards,
Kalpesh Modi
12-24-2012 10:17 PM
Mark Scott's post as "Answered" for the benefit of others who have the same issue as you.
12-23-2012 08:13 AM
Here is my 2 cents... Adding the MAC address for each ap is crazy. It's only really required for mesh. If you don't have authorize ap from Mac filter or auth list (something like that) adding the MAC address is useless.
Here is a link to how you get an ap to join a WLC. I usually prime/stage the AP's on the same subnet as the WLC. Once the ap joins, I canoe the ap to any subnet.
https://supportforums.cisco.com/docs/DOC-5711
Sent from Cisco Technical Support iPhone App
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide