Lap 1142N not joining WLC2106
Hi,
I have a 1142N which does not join the WLC when connected via a 2960 switch. When I connect a different lap 1142N to the same port on the same switch using the same cables, it does join the lap to the WLC. And when I connect the first lap directly to the WLC it also works fine.
Resetting the failing lap does not fix the problem. All software levels on the lap are the same.
Anyone an idea what could be wrong?
Thanks in advance.
Regards
Jeroen
thnx for your support so far.
All the AP's are the same, AIR-LAP1142N-E-K9 v05. I have two AP's which work fine when connected via the 2960 therefore I assume that the switch, wlc, vlan and dhcp configuration is fine.The thirth one is giving me some challenges ;-)
Note: the non working AP is only not working when connected via de 2960, it is working fine when directly connected to the WLC2106.
@David, where can i find the regulatory domain setting?
working AP
NAME: "AP1140", DESCR: "Cisco Aironet 1140 Series (IEEE 802.11n) Access Point"
PID: AIR-LAP1142N-E-K9
failing AP
NAME: "AP1140", DESCR: "Cisco Aironet 1140 Series (IEEE 802.11n) Access Point"
PID: AIR-LAP1142N-E-K9
AP manager subnet
192.168.1.0/24
Management subnet
192.168.2.0/24
WLC2106 sysinfo
==================================================================================
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.0.220.0
RTOS Version..................................... 7.0.220.0
Bootloader Version............................... 4.0.191.0
Emergency Image Version.......................... 6.0.199.4
Build Type....................................... DATA + WPS
System Name...................................... CiscoWLC1
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.828
IP Address....................................... 192.168.2.2
System Up Time................................... 10 days 0 hrs 31 mins 36 secs
System Timezone Location.........................
Configured Country............................... NL - Netherlands
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +48 C
--More-- or (q)uit
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 2
Number of Active Clients......................... 0
Burned-in MAC Address............................ 70:81:05:AE:F9:C0
Maximum number of APs supported.................. 6
DHCP pool configured on core switch
==================================================================================
ip dhcp pool AP-Pool
network 192.168.1.0 255.255.255.0
default-router 192.168.1.254
dns-server 192.168.1.1
Boot info failing WAP
==================================================================================
using eeprom values
WRDTR,CLKTR: 0x85000800 0x40000000
RQDC ,RFDC : 0x80000037 0x0000020f
using ÿÿÿÿ ddr static values from serial eeprom
ddr init done
Running Normal Memtest...
Passed.
IOS Bootloader - Starting system.
FLASH CHIP: Numonyx P33
Checking for Over Erased blocks
Xmodem file system is available.
DDR values used from system serial eeprom.
WRDTR,CLKTR: 0x85000800, 0x40000000
RQDC, RFDC : 0x80000037, 0x0000020f
PCIE0: link is up.
PCIE0: VC0 is active
PCIE1: link is up.
PCIE1: VC0 is active
PCIEx: initialization done
flashfs[0]: 28 files, 8 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
% Please define a domain-name first.
Press RETURN to get started!
*Mar 1 00:00:08.197: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed
*Mar 1 00:00:08.208: *** CRASH_LOG = YES
Security Core found.
Base Ethernet MAC address: 64:9E:F3:B3:5F:88
*Mar 1 00:00:09.787: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0
*Mar 1 00:00:10.359: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1
*Mar 1 00:00:10.393: %LWAPP-3-CLIENTEVENTLOG: Read and initialized AP event log (contains, 215 messages)
*Mar 1 00:00:10.416: status of voice_diag_test from WLC is false
*Mar 1 00:00:11.459: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:12.536: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:12.573: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1140 Software (C1140-K9W8-M), Version 12.4(23c)JA3, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Tue 18-Oct-11 14:52 by prod_rel_team
*Mar 1 00:00:12.573: %SNMP-5-COLDSTART: SNMP agent on host AP649e.f3b3.5f88 is undergoing a cold start
*Mar 1 00:11:43.044: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Mar 1 00:11:43.105: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar 1 00:11:43.105: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 1 00:11:44.106: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Mar 1 00:11:44.106: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:11:44.297: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Mar 1 00:11:52.102: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 192.168.1.44, mask 255.255.255.0, hostname AP649e.f3b3.5f88
*Mar 1 00:12:01.917: status of voice_diag_test from WLC is false
*Mar 1 00:12:01.972: Logging LWAPP message to 255.255.255.255.
*Mar 1 00:12:04.769: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
*Mar 1 00:12:04.792: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:12:04.816: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:12:05.776: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Mar 1 00:12:05.776: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.255 started - CLI initiated
*Mar 1 00:12:05.802: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (192.168.1.1)
*Mar 1 00:13:13.006: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
Not in Bound state.
*Mar 1 00:13:23.524: %CAPWAP-3-ERRORLOG: Invalid event 38 & state 2 combination.
*Mar 1 00:13:23.637: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 192.168.1.45, mask 255.255.255.0, hostname AP649e.f3b3.5f88
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (192.168.1.1)
*Mar 1 00:14:19.511: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
Not in Bound state.
*Mar 1 00:14:30.030: %CAPWAP-3-ERRORLOG: Invalid event 38 & state 2 combination.
*Mar 1 00:14:30.139: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 192.168.1.46, mask 255.255.255.0, hostname AP649e.f3b3.5f88
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (192.168.1.1)
*Mar 1 00:15:26.013: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
Not in Bound state.
*Mar 1 00:15:36.532: %CAPWAP-3-ERRORLOG: Invalid event 38 & state 2 combination.
*Mar 1 00:15:36.640: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 192.168.1.47, mask 255.255.255.0, hostname AP649e.f3b3.5f88
Show version failing wap
==================================================================================
Cisco IOS Software, C1140 Software (C1140-K9W8-M), Version 12.4(23c)JA3, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Tue 18-Oct-11 14:52 by prod_rel_team
ROM: Bootstrap program is C1140 boot loader
BOOTLDR: C1140 Boot Loader (C1140-BOOT-M) Version 12.4(23c)JA3, RELEASE SOFTWARE (fc1)
uptime is 6 minutes
System returned to ROM by power-on
System image file is "flash:/c1140-k9w8-mx.124-23c.JA3/c1140-k9w8-mx.124-23c.JA3"
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
cisco AIR-LAP1142N-E-K9 (PowerPC405ex) processor (revision A0) with 98294K/32768K bytes of memory.
Processor board ID FCZ1548W0GJ
PowerPC405ex CPU at 586Mhz, revision number 0x147E
Last reset from power-on
LWAPP image version 7.0.220.0
1 Gigabit Ethernet interface
2 802.11 Radio(s)
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 64:9E:F3:B3:5F:88
Part Number : 73-12836-03
PCA Assembly Number : 800-33767-03
PCA Revision Number : A0
PCB Serial Number : FOC15443W5A
Top Assembly Part Number : 800-33775-02
Top Assembly Serial Number : FCZ1548W0GJ
Top Revision Number : A0
Product/Model Number : AIR-LAP1142N-E-K9
Configuration register is 0xF
show inventory failing wap
==================================================================================
NAME: "AP1140", DESCR: "Cisco Aironet 1140 Series (IEEE 802.11n) Access Point"
PID: AIR-LAP1142N-E-K9
Message was edited by: Jeroen
Similar Messages
-
AIR-LAP Does not Join With WLC2100
Dear All,
Our offcie use WLC2100 Series controller with AIR-LAP1031 and successfully join and running. Now i am trying to replace one ap with AIR-LAP1041N and join with WLC, but i can't and below the error message generate:
*Mar 25 02:37:28.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.9 peer_port: 5246
*Mar 25 02:37:28.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Mar 25 02:37:29.397: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.9 peer_port: 5246
*Mar 25 02:37:29.398: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.9
*Mar 25 02:37:29.399: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Mar 25 02:37:29.410: %CAPWAP-3-ERRORLOG: This AP is not supported in controller version 6.0.199.4
*Mar 25 02:37:29.493: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Mar 25 02:37:29.493: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.1.9:5246
*Mar 25 02:37:29.495: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Mar 25 02:37:29.495: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Mar 25 02:37:29.549: %CAPWAP-3-ERRORLOG: Dropping dtls packet since session is not established.
*Mar 25 02:37:39.548: %CAPWAP-3-ERRORLOG: Go join a capwap controller
Can you please help me how can i solve the problem ?
Please see the attached.
Reagrds and waiting for your reply?
Palash.This AP is not supported in controller version 6.0.199.4
Upgrade the WLC 2106 firmware to 7.0.240.0. This firmware will support the newer 1040, however, this version will NOT be able to support the older 1030.
You either replace your very old 1030 or run the 1040 on autonomous IOS. -
Cisco LAP 2602 can not join Virtual WLC
dear all,
i just install Virtual WLC and i remove WLC 2504 , i install & configured it , but LAP can not join. it was work fine with WLC 2504.
i used the same network topology with the old WLC.
i receive this error logs.
*spamApTask4: Feb 04 06:01:30.082: <<<< Start of CAPWAP Packet >>>>
*spamApTask4: Feb 04 06:01:30.082: CAPWAP Control mesg Recd from 10.192.200.93, Port 26711
*spamApTask4: Feb 04 06:01:30.082: HLEN 4, Radio ID 0, WBID 1
*spamApTask4: Feb 04 06:01:30.082: Msg Type : CAPWAP_DISCOVERY_REQUEST
*spamApTask4: Feb 04 06:01:30.082: Msg Length : 155
*spamApTask4: Feb 04 06:01:30.082: Msg SeqNum : 0
*spamApTask4: Feb 04 06:01:30.082:
*spamApTask4: Feb 04 06:01:30.082: Type : CAPWAP_MSGELE_DISCOVERY_TYPE, Length 1
*spamApTask4: Feb 04 06:01:30.082: Discovery Type : CAPWAP_DISCOVERY_TYPE_UNKNOWN
*spamApTask4: Feb 04 06:01:30.082:
*spamApTask4: Feb 04 06:01:30.082: Type : CAPWAP_MSGELE_WTP_BOARD_DATA, Length 62
*spamApTask4: Feb 04 06:01:30.083: Vendor Identifier : 0x00409600
*spamApTask4: Feb 04 06:01:30.083: WTP_SERIAL_NUMBER : AIR-CAP2602E-I-K9
*spamApTask4: Feb 04 06:01:30.083:
*spamApTask4: Feb 04 06:01:30.083: Type : CAPWAP_MSGELE_WTP_DESCRIPTOR, Length 40
*spamApTask4: Feb 04 06:01:30.083: Maximum Radios Supported : 2
*spamApTask4: Feb 04 06:01:30.083: Radios in Use : 2
*spamApTask4: Feb 04 06:01:30.083: Encryption Capabilities : 0x00 0x01
*spamApTask4: Feb 04 06:01:30.083:
*spamApTask4: Feb 04 06:01:30.083: Type : CAPWAP_MSGELE_WTP_FRAME_TUNNEL, Length 1
*spamApTask4: Feb 04 06:01:30.083: WTP Frame Tunnel Mode : NATIVE_FRAME_TUNNEL_MODE
*spamApTask4: Feb 04 06:01:30.083:
*spamApTask4: Feb 04 06:01:30.083: Type : CAPWAP_MSGELE_WTP_MAC_TYPE, Length 1
*spamApTask4: Feb 04 06:01:30.083: WTP Mac Type : SPLIT_MAC
*spamApTask4: Feb 04 06:01:30.083:
*spamApTask4: Feb 04 06:01:30.083: Type : CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, Length 10
*spamApTask4: Feb 04 06:01:30.083: Vendor Identifier : 0x00409600
*spamApTask4: Feb 04 06:01:30.083:
IE : UNKNOWN IE 207
*spamApTask4: Feb 04 06:01:30.083: IE Length : 4
*spamApTask4: Feb 04 06:01:30.083: Decode routine not available, Printing Hex Dump
*spamApTask4: Feb 04 06:01:30.083: 00000000: 03 00 00 01 ....
*spamApTask4: Feb 04 06:01:30.083:
*spamApTask4: Feb 04 06:01:30.083: Type : CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, Length 12
*spamApTask4: Feb 04 06:01:30.083: Vendor Identifier : 0x00409600
*spamApTask4: Feb 04 06:01:30.083:
IE : RAD_NAME_PAYLOAD
*spamApTask4: Feb 04 06:01:30.083: IE Length : 6
*spamApTask4: Feb 04 06:01:30.083: Rad Name :
*spamApTask4: Feb 04 06:01:30.083: CEO_AP
*spamApTask4: Feb 04 06:01:30.083: <<<< End of CAPWAP Packet >>>>
*spamApTask4: Feb 04 06:01:30.083: dc:a5:f4:8c:ff:30 Discovery Request from 10.192.200.93:26711
*spamApTask4: Feb 04 06:01:30.083: dc:a5:f4:8c:ff:30 ApModel: AIR-CAP2602E-I-K9
*spamApTask4: Feb 04 06:01:30.083: dc:a5:f4:8c:ff:30 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 200, joined Aps =0
*spamApTask4: Feb 04 06:01:30.083: apModel: AIR-CAP2602E-I-K9
*spamApTask4: Feb 04 06:01:30.083: apType = 26 apModel: AIR-CAP2602E-I-K9
*spamApTask4: Feb 04 06:01:30.083: apType: Ox1a bundleApImageVer: 8.0.110.0
*spamApTask4: Feb 04 06:01:30.083: version:8 release:0 maint:110 build:0
*spamApTask4: Feb 04 06:01:30.083: dc:a5:f4:8c:ff:30 Discovery Response sent to 10.192.200.93 port 26711
*spamApTask4: Feb 04 06:01:30.083: dc:a5:f4:8c:ff:30 Discovery Response sent to 10.192.200.93:26711
Please any help.dear
yes the wlc 2504 is 8.0.110 but because its damaged i replaced it with new vWLC v 8.0.110.
also i can not put the LAP in flexconnect until its joint. -
Lap not joining over a wan link
hi
i have 2 wism running on 6509 chassis and i have access points in remote branches. the lap is not joining the wism. here is the situation:
lap can ping the controllers
lap is getting ip address
option 43 is there on the vlan
dns entry for the wlc is there.
however, when i checked the lap boot: it s getting an ip address and gives the command prompt.
the below debugging on the wlc gives nothing:
debug capwap events
debug capwap errors
debug mac addr <mac addr>
the wan link is private wan running ospf on both routers from each end.
I see no point why this lap is not joining
any idea?Hi,
According to your description, I understand that all attachments in Outlook are opened slowly since updating Outlook 2003 to 2013. Please confirm whether all users encounter this issue. Also check whether the issue continues in cached mode and in OWA.
Based on your post, I suggest we can try to disable the following add-ins to check whether the issue persists:
Acrobat PDFMaker office com addin
symantec endpoint protection outlook addin
If there is any updates, please feel free to let us know.
Thanks,
Winnie Liang
TechNet Community Support -
LAP not joining the controller
Gents
I have 1 AP out of ten not joining the controller. I connected the access point to the network and I checked its boot. the access point reaches LWAPP Discovery" and then give me console input. I hard reset the access point and I hard coded an IP address for the AP the AP joins the controller, but when I reset it to assign it to another controller it did not join again.
why the discovery process is not showing the DHCP option 43 configured and DNS for CISCO-LWAPP-CONTROLLER configured on the DNS. All the access point is operating normally except this one. it has many certificate inside, why a hard reset did not work to solve the problem?
Please advise
Thanks,Does the LAP have a valid IP address?
Can the LAP ping the WLC managment IP address?
Console into the LAP and in enable mode, type the command "lwapp ap controller ". -
LAP: 1242AG version 12.3(7)JX3
WLC: CTVM version 7.6.100.0
LAP IP: 192.168.3.11
WLC IP: 192.168.2.22
Followed directions on
http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/99948-lap-notjoin-wlc-tshoot.html
1) Verified LAP and WLC can ping each other.
2) Verified that time on WLC is correct:
(Cisco Controller) >show time
Time............................................. Mon Mar 3 22:46:40 2014
3) Verified MIC on LAP is NOT expired:
Certificate
Status: Available
Certificate Serial Number: 4CD884DD0000000B2182
Certificate Usage: General Purpose
Issuer:
cn=Cisco Manufacturing CA
o=Cisco Systems
Subject:
Name: C1240-00175a9b08a4
[email protected]
cn=C1240-00175a9b08a4
o=Cisco Systems
l=San Jose
st=California
c=US
CRL Distribution Point:
http://www.cisco.com/security/pki/crl/cmca.crl
Validity Date:
start date: 05:02:38 UTC Apr 4 2006
end date: 05:12:38 UTC Apr 4 2016
renew date: 00:00:00 UTC Jan 1 1970
Associated Trustpoints: Cisco_IOS_MIC_cert
4) Getting the following messages on WLC. (00:17:0f:20:c4:30 is the LAP)
*spamApTask0: Mar 03 22:45:39.885: 00:17:0f:20:c4:30 Received LWAPP DISCOVERY REQUEST to 00:0c:29:9e:17:d7 on port '1'
*spamApTask0: Mar 03 22:45:39.885: 00:17:0f:20:c4:30 LWAPP Discovery Request AP Software Version: 0x3027415
*spamApTask0: Mar 03 22:45:39.885: 00:17:0f:20:c4:30 Join Priority Processing status = 0, Incoming Ap's Priority 0, MaxLrads = 200,joined Aps =0
*spamApTask0: Mar 03 22:45:39.885: 00:17:0f:20:c4:30 Received a Discovery Request from 00:17:0F:20:C4:30 destined for a different controller (0.0.0.0)!. Dropping the packet
5) Getting the following messages on LAP:
*Mar 1 00:15:50.797: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway found
*Mar 1 00:16:00.805: %DOT11-6-FREQ_USED: Interface Dot11Radio0, frequency 2437 selected
*Mar 1 00:16:00.812: %DOT11-6-FREQ_USED: Interface Dot11Radio1, frequency 5765 selected
*Mar 1 00:16:00.812: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
"show run-config" from vWLC attached. How shall I troubleshoot?
Thank you!AP0017.5a9b.08a4#capwap ap controller ip address 192.168.2.22
^
% Invalid input detected at '^' marker.
AP0017.5a9b.08a4#
Exec commands:
cd Change current directory
clear Reset functions
clock Manage the system clock
crypto Encryption related commands.
debug Debugging functions (see also 'undebug')
delete Delete a file
dir List files on a filesystem
disable Turn off privileged commands
dot11 IEEE 802.11 commands
enable Turn on privileged commands
exit Exit from the EXEC
fsck Fsck a filesystem
help Description of the interactive help system
led LED functions
lock Lock the terminal
login Log in as a particular user
logout Exit from the EXEC
mkdir Create new directory
monitor Monitoring different system events
more Display the contents of a file
name-connection Name an existing network connection
no Disable debugging functions
ping Send echo messages
pwd Display current working directory
release Release a resource
reload Halt and perform a cold restart
rename Rename a file
renew Renew a resource
rmdir Remove existing directory
save Start to save raise_interrupt_level stack
send Send a message to other tty lines
set Set system parameter (not config)
show Show running system information
systat Display information about terminal lines
terminal Set terminal line parameters
test Test subsystems, memory, and interfaces
traceroute Trace route to destination
undebug Disable debugging functions (see also 'debug')
upgrade Upgrade software
verify Verify a file
where List active connections
AP0017.5a9b.08a4#
From LAP:
AP0017.5a9b.08a4#ping 192.168.2.22
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.2.22, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
AP0017.5a9b.08a4#
From vWLC:
(Cisco Controller) >ping 192.168.3.11
Send count=3, Receive count=6 from 192.168.3.11
(Cisco Controller) > -
WLC 5508 with LAP-1142n - Several Errors
Hello all,
I had installed a WLC 5508 with 7 LAP 1142n and 2 converted AP 1131abg.
I am seeing some errors relating 2 issues.
1st- One particular AP 1142 is disassociating and reseting the radios.
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table 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:10.0pt;
font-family:"Times New Roman","serif";}
Thu Oct 28 11:50:49 2010
AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:e8:04:62:23:ac:e0 Cause=Radio interface reset. Status:NA
Thu Oct 28 11:50:49 2010
AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:e8:04:62:23:ac:e0 Cause=Radio interface reset. Status:NA
Thu Oct 28 11:50:49 2010
AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:e8:04:62:23:ac:e0 Cause=Radio interface reset. Status:NA
Thu Oct 28 11:50:49 2010
AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:e8:04:62:23:ac:e0 Cause=Radio interface reset. Status:NA
Thu Oct 28 11:50:46 2010
AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:e8:04:62:23:ac:e0 Cause=Radio reset due to Init. Status:NA
Thu Oct 28 11:50:46 2010
AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:e8:04:62:23:ac:e0 Cause=Radio reset due to Init. Status:NA
Thu Oct 28 11:50:46 2010
AP 'AP3', MAC: e8:04:62:23:ac:e0 disassociated previously due to AP Reset. Uptime: 1 days, 10 h 24 m 23 s . Last reset reason: operator changed 11g mode.
Thu Oct 28 11:50:35 2010
AP Disassociated. Base Radio MAC:e8:04:62:23:ac:e0
Thu Oct 28 11:50:35 2010
AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:e8:04:62:23:ac:e0 Cause=New Discovery Status:NA
Thu Oct 28 11:50:35 2010
AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:e8:04:62:23:ac:e0 Cause=New Discovery Status:NA
I had some search, and the new discovery cause, might be that the AP didnt know what WLC do associate, in a multi-controller environment. This is not the case. I only have one WLC in the same management vlan.
2st-The Radius server is beeing related in the logs as been deactivated. I raise the server time-out on Radius configuration option, but it still continues to do it.
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table 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:10.0pt;
font-family:"Times New Roman","serif";}
Thu Oct 28 10:24:41 2010
RADIUS server 10.67.128.36:1812 deactivated in global list
Thu Oct 28 10:24:41 2010
RADIUS server 10.67.128.36:1812 failed to respond to request (ID 172) for client e8:06:88:51:c0:2b / user 'unknown'
Is this meaning the WLC stop sending request to the Radius Server ? We dont have BackUp Radius.
As far as i know, its always the same mac-address client that is associated to that error, maybe a iphone.
I had so many clients in that SSID and they are all working good.
The Radius server is a NPS from windows Server 2008
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table 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:10.0pt;
font-family:"Times New Roman","serif";}
, and the client says that the medium response time is 0,02 sec, so im wondering why the controller is not getting response from Radius for a particular client?! My client also says, that didnt found any log related to that mac-address client ... what is weird...
WLC with last software available 7.0.164
Hope some one help me here.
Best Regards,
Bruno PetrónioThanks Scott,
I understand what you are mentioning, and i really didnt do it yet.
I realize that the primary controller was not configured on the
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table 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:10.0pt;
font-family:"Times New Roman","serif";}
Wireless –> All APs –> High Availability tab, and did it only to the AP that is taking this beahviour.
Is this mandatory for a 1 controller only ?
No mather what the manual say, after that the AP is rebooting 2 mins in 2 mins... with the same kind of messages.
The interface on the switch is getting a few input errors and the same numbers of crc... but are so few...
Next step ... i will change it to another one's place/pathing cable.
Regarding the Radius messages... any ideas ?
I'm already on 30 sec's of server timeout.
Best Regards,
Bruno Petrónio -
Cisco 7925 not joining WLAN Network
hi
I have one 7925G-E phone, 1142-E LAP & WLC 5508 & CME 71. in a 3900 router. I am trying to join the phone with CME but the
phone is not joining the WLAN network.
showing error msg connection failed, i have tried with WEP, Open, Open+WEP option on the phone and WLC but still facing problem,.
Thanks
Saurav
I have tried with WPA-PSK and tried the notebook to join it is joining but the Phone is not joiining getting the same error.
connection failed.
*May 02 15:37:52.629: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:37:52.629: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:37:52.628: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:37:52.628: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:37:52.628: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:37:52.628: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:37:52.626: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:37:52.626: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:37:52.625: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:37:52.625: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:37:52.623: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:37:52.623: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:27:36.864: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:27:36.864: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:27:36.863: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:27:36.863: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:27:36.861: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:27:36.861: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:27:36.859: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:27:36.859: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:27:36.857: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:27:36.857: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:27:36.856: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:27:36.855: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:22:35.811: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:22:35.811: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:22:35.809: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:22:35.809: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:22:35.808: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:22:35.808: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:22:35.806: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:22:35.806: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:22:35.804: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:22:35.804: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:22:35.802: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:22:35.802: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:18:32.227: %APF-1-PROC_RSN_WARP_IE_FAILED: apf_80211.c:2235 Could not process the RSN and WARP IEs. station not using WPA or WPA2 on WLAN requiring WPA and/or WPA2.MobileStation: 00:21:6b:39:a1:ac, SSID:voip,AP: c4:7d:4f:4b:a4:40.
*May 02 15:18:32.082: %APF-1-PROC_RSN_WARP_IE_FAILED: apf_80211.c:2235 Could not process the RSN and WARP IEs. station not using WPA or WPA2 on WLAN requiring WPA and/or WPA2.MobileStation: 00:21:6b:39:a1:ac, SSID:voip,AP: c4:7d:4f:4b:a4:40.
*May 02 15:18:31.995: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:18:31.995: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:18:31.993: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:18:31.993: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:18:31.992: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:18:31.992: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:18:31.989: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:18:31.989: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:18:31.984: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:18:31.984: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:18:31.979: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:18:31.979: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:17:49.474: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a6:d0
*May 02 15:17:49.474: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a6:d0
*May 02 15:17:49.472: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a4:40
*May 02 15:17:49.472: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a4:40
*May 02 15:17:49.470: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:98:40
*May 02 15:17:49.470: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:98:40
*May 02 15:17:49.468: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f1:b0
*May 02 15:17:49.468: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f1:b0
*May 02 15:17:49.465: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f0:d0
*May 02 15:17:49.465: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f0:d0
*May 02 15:17:49.460: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:e3:80
*May 02 15:17:49.460: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:e3:80
*May 02 15:17:49.457: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:17:49.457: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:17:49.456: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:17:49.456: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:17:49.452: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:17:49.452: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:17:49.447: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:17:49.447: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:17:49.443: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:17:49.443: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:17:49.440: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:17:49.440: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:16:24.677: %APF-1-DISCONECT_MOBILE_DUE_TO_WLAN_SW: apf_policy.c:541 Disconnecting mobile 00:21:6b:39:a1:ac due to switch of WLANs from 6(cisco_test) to 7(voip)
*May 02 15:14:20.572: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a6:d0
*May 02 15:14:20.572: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a6:d0
*May 02 15:14:20.571: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a4:40
*May 02 15:14:20.571: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a4:40
*May 02 15:14:20.571: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:98:40
*May 02 15:14:20.571: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:98:40
*May 02 15:14:20.569: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f1:b0
*May 02 15:14:20.569: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f1:b0
*May 02 15:14:20.569: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f0:d0
*May 02 15:14:20.569: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f0:d0
*May 02 15:14:20.568: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:e3:80
*May 02 15:14:20.568: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:e3:80
*May 02 15:14:20.568: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:14:20.568: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:14:20.568: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:14:20.568: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:14:20.567: %APF-3-SET_VAP_STATUS_FAILED: apf_api.c:15464 Could not Set the Status of Virtual Access point Entry.Encryption mode for static WEP does not match encryption mode for dynamic WEP on WLAN.Static WEP:1.Dynamic WEP:2. WLAN:'voip'
*May 02 15:14:20.566: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:14:20.566: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:14:20.564: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:14:20.564: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:14:20.562: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:14:20.562: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:14:20.560: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:14:20.560: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:08:45.139: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a6:d0
*May 02 15:08:45.139: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a6:d0
*May 02 15:08:45.137: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a4:40
*May 02 15:08:45.137: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a4:40
*May 02 15:08:45.135: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:98:40
*May 02 15:08:45.135: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:98:40
*May 02 15:08:45.134: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f1:b0
*May 02 15:08:45.133: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f1:b0
*May 02 15:08:45.132: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f0:d0
*May 02 15:08:45.132: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f0:d0
*May 02 15:08:45.131: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:e3:80
*May 02 15:08:45.130: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:e3:80
*May 02 15:08:45.129: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:08:45.129: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:08:45.128: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:08:45.128: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:08:45.126: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:08:45.126: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:08:45.124: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:08:45.124: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:08:45.122: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:08:45.122: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:08:45.120: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:08:45.120: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:08:43.623: %APF-1-DISCONECT_MOBILE_DUE_TO_WLAN_SW: apf_policy.c:541 Disconnecting mobile 00:21:6b:39:a1:ac due to switch of WLANs from 4(CGC-7FL-WLAN) to 6(cisco_test)
*May 02 15:07:35.339: %APF-1-DISCONECT_MOBILE_DUE_TO_WLAN_SW: apf_policy.c:541 Disconnecting mobile 00:21:6b:39:a1:ac due to switch of WLANs from 7(voip) to 4(CGC-7FL-WLAN)
*May 02 15:06:55.072: %AAA-3-EAPMETHOD_ADD_FAILED: localeap_db.c:2716 Unable to add method 'peap' to EAP profile for user 'test'. method already exist.
*May 02 15:06:55.072: %AAA-3-EAPMETHOD_ADD_FAILED: localeap_db.c:2716 Unable to add method 'tls' to EAP profile for user 'test'. method already exist.
*May 02 15:06:55.072: %AAA-3-EAPMETHOD_ADD_FAILED: localeap_db.c:2716 Unable to add method 'fast' to EAP profile for user 'test'. method already exist.
*May 02 15:06:55.072: %AAA-3-EAPMETHOD_ADD_FAILED: localeap_db.c:2716 Unable to add method 'leap' to EAP profile for user 'test'. method already exist.
*May 02 15:06:27.672: %DOT1X-3-MAX_EAP_RETRIES: 1x_auth_pae.c:2872 Max EAP identity request retries (3) exceeded for client 00:21:6b:39:a1:ac
*May 02 15:05:27.648: %DOT1X-3-MAX_EAP_RETRIES: 1x_auth_pae.c:2872I have tried with WPA-PSK and tried the notebook to join it is joining but the Phone is not joiining getting the same error.
connection failed.
*May 02 15:37:52.629: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:37:52.629: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:37:52.628: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:37:52.628: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:37:52.628: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:37:52.628: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:37:52.626: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:37:52.626: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:37:52.625: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:37:52.625: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:37:52.623: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:37:52.623: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:27:36.864: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:27:36.864: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:27:36.863: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:27:36.863: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:27:36.861: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:27:36.861: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:27:36.859: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:27:36.859: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:27:36.857: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:27:36.857: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:27:36.856: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:27:36.855: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:22:35.811: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:22:35.811: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:22:35.809: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:22:35.809: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:22:35.808: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:22:35.808: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:22:35.806: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:22:35.806: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:22:35.804: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:22:35.804: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:22:35.802: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:22:35.802: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:18:32.227: %APF-1-PROC_RSN_WARP_IE_FAILED: apf_80211.c:2235 Could not process the RSN and WARP IEs. station not using WPA or WPA2 on WLAN requiring WPA and/or WPA2.MobileStation: 00:21:6b:39:a1:ac, SSID:voip,AP: c4:7d:4f:4b:a4:40.
*May 02 15:18:32.082: %APF-1-PROC_RSN_WARP_IE_FAILED: apf_80211.c:2235 Could not process the RSN and WARP IEs. station not using WPA or WPA2 on WLAN requiring WPA and/or WPA2.MobileStation: 00:21:6b:39:a1:ac, SSID:voip,AP: c4:7d:4f:4b:a4:40.
*May 02 15:18:31.995: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:18:31.995: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:18:31.993: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:18:31.993: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:18:31.992: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:18:31.992: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:18:31.989: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:18:31.989: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:18:31.984: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:18:31.984: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:18:31.979: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:18:31.979: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:17:49.474: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a6:d0
*May 02 15:17:49.474: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a6:d0
*May 02 15:17:49.472: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a4:40
*May 02 15:17:49.472: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a4:40
*May 02 15:17:49.470: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:98:40
*May 02 15:17:49.470: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:98:40
*May 02 15:17:49.468: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f1:b0
*May 02 15:17:49.468: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f1:b0
*May 02 15:17:49.465: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f0:d0
*May 02 15:17:49.465: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f0:d0
*May 02 15:17:49.460: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:e3:80
*May 02 15:17:49.460: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:e3:80
*May 02 15:17:49.457: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:17:49.457: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:17:49.456: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:17:49.456: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:17:49.452: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:17:49.452: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:17:49.447: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:17:49.447: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:17:49.443: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:17:49.443: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:17:49.440: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:17:49.440: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:16:24.677: %APF-1-DISCONECT_MOBILE_DUE_TO_WLAN_SW: apf_policy.c:541 Disconnecting mobile 00:21:6b:39:a1:ac due to switch of WLANs from 6(cisco_test) to 7(voip)
*May 02 15:14:20.572: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a6:d0
*May 02 15:14:20.572: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a6:d0
*May 02 15:14:20.571: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a4:40
*May 02 15:14:20.571: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a4:40
*May 02 15:14:20.571: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:98:40
*May 02 15:14:20.571: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:98:40
*May 02 15:14:20.569: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f1:b0
*May 02 15:14:20.569: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f1:b0
*May 02 15:14:20.569: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f0:d0
*May 02 15:14:20.569: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f0:d0
*May 02 15:14:20.568: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:e3:80
*May 02 15:14:20.568: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:e3:80
*May 02 15:14:20.568: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:14:20.568: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:14:20.568: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:14:20.568: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:14:20.567: %APF-3-SET_VAP_STATUS_FAILED: apf_api.c:15464 Could not Set the Status of Virtual Access point Entry.Encryption mode for static WEP does not match encryption mode for dynamic WEP on WLAN.Static WEP:1.Dynamic WEP:2. WLAN:'voip'
*May 02 15:14:20.566: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:14:20.566: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:14:20.564: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:14:20.564: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:14:20.562: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:14:20.562: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:14:20.560: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:14:20.560: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:08:45.139: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a6:d0
*May 02 15:08:45.139: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a6:d0
*May 02 15:08:45.137: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a4:40
*May 02 15:08:45.137: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:a4:40
*May 02 15:08:45.135: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:98:40
*May 02 15:08:45.135: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:4b:98:40
*May 02 15:08:45.134: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f1:b0
*May 02 15:08:45.133: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f1:b0
*May 02 15:08:45.132: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f0:d0
*May 02 15:08:45.132: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:f0:d0
*May 02 15:08:45.131: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:e3:80
*May 02 15:08:45.130: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP c4:7d:4f:46:e3:80
*May 02 15:08:45.129: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:08:45.129: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e9:90
*May 02 15:08:45.128: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:08:45.128: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e8:b0
*May 02 15:08:45.126: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:08:45.126: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e5:c0
*May 02 15:08:45.124: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:08:45.124: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:0d:e2:50
*May 02 15:08:45.122: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:08:45.122: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:70
*May 02 15:08:45.120: %LWAPP-3-WLAN_ERR2: spam_lrad.c:20904 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:08:45.120: %LWAPP-3-WLAN_ERR2: spam_lrad.c:21261 Unable to find WLAN 7 to be deleted; AP 00:3a:98:08:2f:60
*May 02 15:08:43.623: %APF-1-DISCONECT_MOBILE_DUE_TO_WLAN_SW: apf_policy.c:541 Disconnecting mobile 00:21:6b:39:a1:ac due to switch of WLANs from 4(CGC-7FL-WLAN) to 6(cisco_test)
*May 02 15:07:35.339: %APF-1-DISCONECT_MOBILE_DUE_TO_WLAN_SW: apf_policy.c:541 Disconnecting mobile 00:21:6b:39:a1:ac due to switch of WLANs from 7(voip) to 4(CGC-7FL-WLAN)
*May 02 15:06:55.072: %AAA-3-EAPMETHOD_ADD_FAILED: localeap_db.c:2716 Unable to add method 'peap' to EAP profile for user 'test'. method already exist.
*May 02 15:06:55.072: %AAA-3-EAPMETHOD_ADD_FAILED: localeap_db.c:2716 Unable to add method 'tls' to EAP profile for user 'test'. method already exist.
*May 02 15:06:55.072: %AAA-3-EAPMETHOD_ADD_FAILED: localeap_db.c:2716 Unable to add method 'fast' to EAP profile for user 'test'. method already exist.
*May 02 15:06:55.072: %AAA-3-EAPMETHOD_ADD_FAILED: localeap_db.c:2716 Unable to add method 'leap' to EAP profile for user 'test'. method already exist.
*May 02 15:06:27.672: %DOT1X-3-MAX_EAP_RETRIES: 1x_auth_pae.c:2872 Max EAP identity request retries (3) exceeded for client 00:21:6b:39:a1:ac
*May 02 15:05:27.648: %DOT1X-3-MAX_EAP_RETRIES: 1x_auth_pae.c:2872 -
AIR-CAP3501I access point not joining the Cisco 2100 Wireless Lan controller.
Hello All,
I am installing a new LAP (AIR-CAP3501I ) through the wireless lan controller (AIR-WLC2112-K9) with software version 7.0. I have an external ADSL modem which will act as the DHCP server for the wireless clients and the LAP.
Please find my network setup as below:
The ISP ADSL modem , WLC and LAP are connected to a unmanaged POE switch. The LAP gets its power through the POE switch. When i connect the LAP and the WLC to the switch along with the ADSL modem, the LAPs are getting the ip address from the ADSL modem, however they are not joining the WLC for further process.
ADSL Modem ip address: 192.168.1.254
Management ip address on the LAP: 192.168.1.1 ( Assigned to port 1, untagged Vlan).
Ap Manager ip address: 192.168.1.1 ( Assigned to the same port i.e port1, Untagged Vlan).
The LAP is getting an IP address from the ADSL modem in the range of the DHCP scope.
I will paste the logs very soon.
Please let me know if i am doing anything wrong oe what will be the issue.
Thanks in advance,
Mohammed AmeenHello All,
Please find the logs for "debug capwap event" from the WLC below:
*spamReceiveTask: Sep 26 19:44:59.196: e8:04:62:0a:3f:10 Join Version: = 117465600
*spamReceiveTask: Sep 26 19:44:59.197: e8:04:62:0a:3f:10 Join resp: CAPWAP Maximum Msg element len = 92
*spamReceiveTask: Sep 26 19:44:59.197: e8:04:62:0a:3f:10 Join Response sent to 192.168.1.156:45510
*spamReceiveTask: Sep 26 19:44:59.197: e8:04:62:0a:3f:10 CAPWAP State: Join
*spamReceiveTask: Sep 26 19:44:59.197: e8:04:62:0a:3f:10 capwap_ac_platform.c:1216 - Operation State 0 ===> 4
*apfReceiveTask: Sep 26 19:44:59.198: e8:04:62:0a:3f:10 Register LWAPP event for AP e8:04:62:0a:3f:10 slot 0
*spamReceiveTask: Sep 26 19:44:59.341: e8:04:62:0a:d1:20 DTLS connection not found, creating new connection for 192:168:1:158 (45644) 192:168:1:2 (5246)
*spamReceiveTask: Sep 26 19:45:00.119: e8:04:62:0a:d1:20 DTLS Session established server (192.168.1.2:5246), client (192.168.1.158:45644)
*spamReceiveTask: Sep 26 19:45:00.119: e8:04:62:0a:d1:20 Starting wait join timer for AP: 192.168.1.158:45644
*spamReceiveTask: Sep 26 19:45:00.121: e8:04:62:0a:d1:20 Join Request from 192.168.1.158:45644
*spamReceiveTask: Sep 26 19:45:00.123: e8:04:62:0a:d1:20 Join Version: = 117465600
*spamReceiveTask: Sep 26 19:45:00.123: e8:04:62:0a:d1:20 Join resp: CAPWAP Maximum Msg element len = 92
*spamReceiveTask: Sep 26 19:45:00.124: e8:04:62:0a:d1:20 Join Response sent to 192.168.1.158:45644
*spamReceiveTask: Sep 26 19:45:00.124: e8:04:62:0a:d1:20 CAPWAP State: Join
*spamReceiveTask: Sep 26 19:45:00.124: e8:04:62:0a:d1:20 capwap_ac_platform.c:1216 - Operation State 0 ===> 4
*apfReceiveTask: Sep 26 19:45:00.125: e8:04:62:0a:d1:20 Register LWAPP event for AP e8:04:62:0a:d1:20 slot 0
*spamReceiveTask: Sep 26 19:45:00.273: e8:04:62:0a:d1:20 Configuration Status from 192.168.1.158:45644
*spamReceiveTask: Sep 26 19:45:00.273: e8:04:62:0a:d1:20 CAPWAP State: Configure
*spamReceiveTask: Sep 26 19:45:00.273: Invalid channel 1 spacified for the AP APf866.f2ab.24b6, slotId = 0
*spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 Updating IP info for AP e8:04:62:0a:d1:20 -- static 0, 192.168.1.158/255.255.255.0, gtw 192.168.1.254
*spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 Updating IP 192.168.1.158 ===> 192.168.1.158 for AP e8:04:62:0a:d1:20
*spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 Setting MTU to 1485
*spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 Finding DTLS connection to delete for AP (192:168:1:158/45644)
*spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 Disconnecting DTLS Capwap-Ctrl session 0xa06d6a4 for AP (192:168:1:158/45644)
*spamReceiveTask: Sep 26 19:45:00.274: e8:04:62:0a:d1:20 CAPWAP State: Dtls tear down
*spamReceiveTask: Sep 26 19:45:00.277: spamProcessGlobalPathMtuUpdate: Changing Global LRAD MTU to 576
*spamReceiveTask: Sep 26 19:45:00.277: e8:04:62:0a:d1:20 DTLS connection closed event receivedserver (192:168:1:2/5246) client 192:168:1:158/45644).
The Acess point joins the Controller for 2-3 seconds and then unjoins again. I am not sure what i am doing wrong here. The access points are getting the IPs from the ADSL modem through the switch, then it talks to the WLC, however it does not join the controller for further process.
Note:
The Managemnet interface and the AP manager interface are assigned to the same port 1 with unassigned Vlan as mention above. -
3502i APs not joining controller
So basically my infrastructure consists of four 4402 WLCs running on 7.0.235.3. I'm trying to get new access points to join to the environment, but I am having difficulty doing so. All currently joined APs work fine and are operating well. I'm getting a red, green, off blink code which means it's trying to join, but never does. The other one I get a constantly blinking green but it never joins either. I've setup option 43 in DHCP, added cisco-capwap-controller entries in DNS thinking it was because those are missing, and still cannot get these two access points to join. Can anyone think why it would not be joining?
The access points and WLC are all on the Same VLAN by the way.Hello,
In a Cisco Unified Wireless network, the LAPs must first discover and join a WLC before they can service wireless clients.
Originally, the controllers only operated in Layer 2 mode. In Layer 2 mode, the LAPs are required to be on the same subnet as the management interface and the Layer 3 mode AP-manager interface is not present on the controller. The LAPs communicate with the controller using Layer 2 encapsulation only (ethernet encapsulation) and do not Dynamic Host Configuration Protocol (DHCP) an IP address.
When Layer 3 mode on the controller was developed, a new Layer 3 interface called AP-manager was introduced. In Layer 3 mode, the LAPs would DHCP an IP address first and then send their discovery request to the management interface using IP addresses (Layer 3). This allowed the LAPs to be on a different subnet than the management interface of the controller. Layer 3 mode is the dominate mode today. Some controllers and LAPs can only perform Layer 3 mode.
However, this presented a new problem: how did the LAPs find the management IP address of the controller when it was on a different subnet?
In Layer 2 mode, they were required to be on the same subnet. In Layer 3 mode, the controller and LAP are essentially playing hide and seek in the network. If you do not tell the LAP where the controller is via DHCP option 43, DNS resolution of "Cisco-lwapp-controller@local_domain", or statically configure it, the LAP does not know where in the network to find the management interface of the controller.
In addition to these methods, the LAP does automatically look on the local subnet for controllers with a 255.255.255.255 local broadcast. Also, the LAP remembers the management IP address of any controller it joins across reboots. Therefore, if you put the LAP first on the local subnet of the management interface, it will find the controller's management interface and remember the address. This is called priming. This does not help find the controller if you replace a LAP later on. Therefore, Cisco recommends using the DHCP option 43 or DNS methods.
When the LAPs discover the controller, they do not know if the controller is in Layer 2 mode or Layer 3 mode. Therefore, the LAPs always connect to the management interface address of the controller first with a discovery request. The controller then tells the LAP which mode it is in the discovery reply. If the controller is in Layer 3 mode, the discovery reply contains the Layer 3 AP-manager IP address so the LAP can send a join request to the AP-manager interface next.
Note: By default both management and AP-manager interfaces are left untagged on their VLAN during configuration. In case these are tagged, make sure they are tagged to the same VLAN in order to properly receive discovery and join response from the WLC.
The LWAPP AP goes through this process on startup for Layer 3 mode:
The LAP boots and DHCPs an IP address if it was not previously assigned a static IP address.
The LAP sends discovery requests to controllers through the various discovery algorithms and builds a controller list. Essentially, the LAP learns as many management interface addresses for the controller list as possible via:
DHCP option 43 (good for global companies where offices and controllers are on different continents)
DNS entry for cisco-capwap-controller (good for local businesses - can also be used to find where brand new APs join)
Note: If you use CAPWAP, make sure that there is a DNS entry for cisco-capwap-controller.
Management IP addresses of controllers the LAP remembers previously
A Layer 3 broadcast on the subnet
Over the air provisioning
Statically configured information
From this list, the easiest method to use for deployment is to have the LAPs on the same subnet as the management interface of the controller and allow the LAP’s Layer 3 broadcast to find the controller. This method should be used for companies that have a small network and do not own a local DNS server.
The next easiest method of deployment is to use a DNS entry with DHCP. You can have multiple entries of the same DNS name. This allows the LAP to discover multiple controllers. This method should be used by companies that have all of their controllers in a single location and own a local DNS server. Or, if the company has multiple DNS suffixes and the controllers are segregated by suffix.
DHCP option 43 is used by large companies to localize the information via the DHCP. This method is used by large enterprises that have a single DNS suffix. For example, Cisco owns buildings in Europe, Australia, and the United States. In order to ensure that the LAPs only join controllers locally, Cisco cannot use a DNS entry and must use DHCP option 43 information to tell the LAPs what the management IP address of their local controller is.
Finally, static configuration is used for a network that does not have a DHCP server.You can statically configure the information necessary to join a controller via the console port and the AP’s CLI. For information on how to statically configure controller information using the AP CLI, refer to Manually Configuring Controller Information Using the Access Point CLI.
For a detailed explanation on the different discovery algorithms that LAPs use to find controllers, refer to LAP Registration with WLC.
For information on configuring DHCP option 43 on a DHCP server, refer to DHCP OPTION 43 for Lightweight Cisco Aironet Access Points Configuration Example.
Send a discovery request to every controller on the list and wait for the controller's discovery reply which contains the system name, AP-manager IP addresses, the number of APs already attached to each AP-manager interface, and overall excess capacity for the controller.
Look at the controller list and send a join request to a controller in this order (only if the AP received a discovery reply from it):
Primary Controller system name (previously configured on LAP)
Secondary Controller system name (previously configured on LAP)
Tertiary Controller system name (previously configured on LAP)
Master controller (if the LAP has not been previously configured with any Primary, Secondary, or Tertiary controller names. Used to always know which controller brand new LAPs join)
If none of the above are seen, load balance across controllers using the excess capacity value in the discovery response.
If two controllers have the same excess capacity, then send the join request to the first controller that responded to the discovery request with a discovery response. If a single controller has multiple AP-managers on multiple interfaces, choose the AP-manager interface with the least number of APs.
The controller will respond to all discovery requests without checking certificates or AP credentials. However, join requests must have a valid certificate in order to get a join response from the controller. If the LAP does not receive a join response from its choice, the LAP will try the next controller in the list unless the controller is a configured controller (Primary/Secondary/Tertiary).
When it receives the join reply, the AP checks to make sure it has the same image as that of the controller. If not, the AP downloads the image from the controller and reboots to load the new image and starts the process all over again from step 1.
If it has the same software image, it asks for the configuration from the controller and moves into the registered state on the controller.
After you download the configuration, the AP might reload again to apply the new configuration. Therefore, an extra reload can occur and is a normal behavior. -
Hi all
I'm having an issue with a 1252 LAP that is connected to the WLC over a WAN link.
Basically, it won't associate. The following is taken from a console into the LAP:
*Mar 1 00:00:07.799: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:08.799: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:26.851: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
*Mar 1 00:00:27.003: Logging LWAPP message to 255.255.255.255.
%CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
%CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
%DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 10.148.x.x, mask 255.255.255.0, hostname AP002
2.90a3.533a
Translating "CISCO-LWAPP-CONTROLLER.nation.radix"...domain server (10.x.x.x)
%LWAPP-3-CLIENTEVENTLOG: Controller address 10.x.x.x obtained through DHCP
%LWAPP-3-CLIENTEVENTLOG: Did not get log server settings from DHCP.
%SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.255 started - CLI initiated
%LWAPP-3-CLIENTEVENTLOG: Performing DNS resolution for CISCO-LWAPP-CONTROLLER.nation.radix
%LWAPP-3-CLIENTERRORLOG: DNS Name Lookup: could not resolve CISCO-LWAPP-CONTROLLER.nation.radix
%LWAPP-5-CHANGED: LWAPP changed state to JOIN
%LWAPP-3-CLIENTERRORLOG: Join Timer: did not recieve join response (controller - Fxxxxxxx)
%LWAPP-3-CLIENTERRORLOG: Set Transport Address: no more AP manager IP addresses remain
%SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Reason: DID NOT GET JOIN RESPONSE.
%LWAPP-5-CHANGED: LWAPP changed state to DOWN
IOS Bootloader - Starting system.
Xmodem file system is available.
The ap-manager interface is configured correctly and there isn't a duplicate IP address.
The LAP was initially stand alone and was converted to LWAPP.
The MTU over the WAN link is 1500 bytes.
All I'm getting from the WLC debugs is:
Mon Jul 20 11:42:59 2009: 00:22:xx:xx:xx:xx Received LWAPP DISCOVERY REQUEST from AP 00:22:xx:xx:xx:xx to 00:19:xx:xx:xx:xx on port '29'
Mon Jul 20 11:42:59 2009: 00:22:xx:xx:xx:xx LWAPP Discovery Request AP Software Version: 0x3003300
Mon Jul 20 11:42:59 2009: 00:22:xx:xx:xx:xx Successful transmission of LWAPP Discovery Response to AP 00:22:xx:xx:xx:xx on port 29
So basically the join messages don't seem to reach the WLC. In fact they don't even seem to reach the local router on the remote subnet. The discovery packets are seen on the local router but the joins don't seem to appear at all.
I'm not sure if it's a latency issue. Average latency over the WAN link is under 70ms.
I'm assuming the certificate on the WAP is MIC and the MAC details have been entered into the WLC AP Security policies for authentication. I'm not seeing any debugging messages relating to bad authentication at all.
I can't debug from the LAP as it's LWAPP, obviously.
I've been through many Cisco documents trying to troubleshoot the problem, including this http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00808f8599.shtml, but can't find a solution.
We're running WLC version 4.2.130.0.
Can anyone help?
Thanks
BrodieI assume you have connected to router's AUX and doing reverse telnet. You should be getting Password: prompt on your LAP's console. Password and Enable are both Cisco. Below is console output from my lab's 1250 LAP after erasing configuration (which can only be initiated from controller). In my case, the vlan is not configured with Option 43 and no proper DNS, so LAP doesn't join the controller.
By the way, your best bet might be to convert this LAP back to IOS and then back to LAP again. Use this method:
http://www.cisco.com/en/US/docs/wireless/access_point/conversion/lwapp/upgrade/guide/lwapnote.html#wp160918
Do you have "Authorize APs against AAA" checked under Security > AP Policies in any of your WLCs ?
Press RETURN to get started!
*Mar 1 00:00:07.099: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0
*Mar 1 00:00:07.619: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1
*Mar 1 00:00:08.595: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to up
*May 10 23:17:25.199: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
*May 10 23:17:26.155: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1250 Software (C1250-K9W8-M), Version 12.4(10b)JDC, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Fri 01-May-09 10:49 by prod_rel_team
*May 10 23:17:26.155: %SNMP-5-COLDSTART: SNMP agent on host ap is undergoing a cold start
*May 10 23:17:27.183: %SSH-5-ENABLED: SSH 2.0 has been enabled
*May 10 23:17:27.387: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*May 10 23:17:27.387: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*May 10 23:17:28.439: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*May 10 23:17:28.439: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*May 10 23:17:30.783: %LWAPP-3-CLIENTERRORLOG: ../lwapp/lwapp_l2.c:152 - discarding msg type 12 in state 0
*May 10 23:17:30.783: %CDP_PD-4-POWER_OK: Full power - AC_ADAPTOR inline power source
*May 10 23:17:30.795: %DOT11-6-FREQ_SCAN: Interface Dot11Radio0, Scanning frequencies for 16 seconds
*May 10 23:17:44.571: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
*May 10 23:17:44.731: Logging LWAPP message to 255.255.255.255.
%LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
%LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
%LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
%SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.255 started - CLI initiated
%LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
%LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
%LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
%LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
%LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
%DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 172.16.8.3, mask 255.255.255.0, hostname AP0022.558e.24bc
User Access Verification
Password:
AP0022.558e.24bc>en
Password:
AP0022.558e.24bc#show lwapp ?
client LWAPP Client Information
ids LWAPP IDS Information
ip LWAPP IP configuration
mcast LWAPP Mcast Information
reap LWAPP REAP Information
rm LWAPP RM Information
AP0022.558e.24bc#show lwapp client config
AP0022.558e.24bc#
AP0022.558e.24bc#ping 3.45.47.143
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 3.45.47.143, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
AP0022.558e.24bc# -
Problems with LAP-1142n booting
Hi,
I recently installed about 40 LAP-1142n access points fresh out of the box in a new elementary school. All but 5 of the AP's were able to join the controller and were set to function in H-Reap mode. The AP's that didn't join seem to be stuck in the boot process and the LED is coontinuously blinking green. I can leave them in that state all night and the next day it's still blinking green. Powering it down and bringing it back up has no effect.
All AP's are connected to C3750X POE switches and the switchports are all trunked and have the native vlan set, so all 40 have identical settings. Is it possible that I have 5 that are bad out of the box or is there something that I can do to fix this problem? Has anyone seen this before?
Thanks for any help you may be able to give me.Have the cable vendor check wiring scheme and repunch down the cables at each end.
No need. The APs are connected to 3750X. To verify if you have a potential cable defect one has to run the 3750X's built-in TDR test. Works like a charm (much to the annoyance of the cable people!). -
TS1398 will not join with router
just got ipad out of box. tried connecting to my router but would not join only says, dismiss. standing next to router so no probs with signal strength. lap top and notepad connect wirelessly okay and i have checked security code stamped on the router. any thoughts for a complete novice?
Can see network?
Settings>WiFi>Choose a network -
Does not join to any fact source issue in 10g
HI,
I am getting below issue while compiling rpd.
Logical Dimension Table Dim-XX has a source xx_aa that does not join to any fact source.
Let me describe situation here.
In physical layer , i have one xx_v table . there is no join condition physical layer. But in BMM layer we have created two logical tables for single xx_v table and providing join in bmm layer. When am compiling it i'm getting an error.
The one which i have using current rpd, same rpd in production with out any warnings(Logical Dimension Table Dim-XX has a source xx_aa that does not join to any fact source) and they don't have any logical level mapping in content tab. But i am using same rpd in dev instance getting warnings.
Thanks,
Mal
Edited by: user10675696 on Feb 11, 2013 3:08 AMHi Srini,
Please find the below warning here and we don't have an hierarchy for MTL_SYSTE_ITEMS_B
[39008] Logical dimension table Mtl System Items B has a source MTL_SYSTEM_ITEMS_B that does not join to any fact source.
I am getting this in Dev instance only but not in Production. But one rpd can be used in dev and production instances.
Thanks,
Mall -
I can not join my Apple extreme with the Apple express. I shows a conflict in the network! I've tried everything. How can they join on the same network?
It says that my DHCP has to be changed! How? to what?
It is 802.11g.express. but is set to default by the computer (Macbook Air).
The other is 802.11n. (express)
Extreme is 802.11.g. Is the Main Airport.
It is on ethernet & wep 128 security.
Maybe you are looking for
-
MBP does not detect external monitor on DVI connection...
(2007) MBP C2D 2.33 15", OSX LION 3gb. Worked fine till about 3 days ago (right after installing the last round of updates). My external monitor now fails to connect on DVI cable. Since it also has VGA, I was able to test this way with a DVI to VGA
-
OWA Excel Survey Missing on some Site Collections?
Weird issue with Office Web Apps & the Excel Survey function: I know that OWA isn't configured this way, but it seems that for many site collections the "Survey" button on the ribbon is missing. Since the configuration for OWA & SharePoint is pretty
-
Why is my mac book blank and not loading when I turn it on?
Why is my mac a blank screen when I turn it on and not loading?
-
Camera RAW for Photoshop version 8.0 CS Middle Eastern Edition
Hi, I am using Photoshop version 8.0 CS Middle Eastern Edition. I am using Nikon D60. I would be greateful if you let me know what Camera RAW version to be used for that and from where to get it. Thanking you in anticipation. Regards, Riz Abbasi
-
How do I create a link from my site to my facebook page?
How do I creat a link on my site to go to my facebook page?