1242AG LAP not joining vWLC
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) >
Similar Messages
-
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 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 -
Hi,
I have a hard time geting a AP to connect to a vWLC. I get certificate error on the AP, he dose'nt trust the vWLC's selfsigned certificate.
I know about the requirement for the AP, to have 7.3 code on before connecting to a vWLC. This AP were connected to another demo-license vWLC before, 4 months ago. But now, when I did a reinstall of vWLC, my AP dose'nt connect.
I have done recovery on the AP with all 15.2.2 images for the AP (3502I)
ap3g1-rcvk9w8-tar.152-2.JA.tar
ap3g1-rcvk9w8-tar.152-2.JA1.tar
ap3g1-rcvk9w8-tar.152-2.JB.tar
I have tried to reinstall and change version of the vWLC. (and tried the diffrent images)
AIR-CTVM-7-3-112-0.ova
AIR-CTVM-7-3-101-0.ova
I do see that the right code is on the AP for example:
cisco AIR-CAP3502I-E-K9 (PowerPC460exr) processor (revision A0) with 81910K/49152K bytes of memory.
Processor board ID FCZ1544W0N1
PowerPC460exr CPU at 666Mhz, revision number 0x18A8
Last reset from power-on
LWAPP image version 7.3.1.73
1 Gigabit Ethernet interface
I have checked the time on the vWLC vs AP for missmatch but they are spot on.
Still only get this on the AP:
*Jun 5 23:43:09.012: %CAPWAP-3-ERRORLOG: Certificate verification failed!
*Jun 5 23:43:09.012: DTLS_CLIENT_ERROR: ../capwap/base_capwap/capwap/base_capwap_wtp_dtls.c:447 Certificate verified failed!
*Jun 5 23:43:09.012: %DTLS-5-SEND_ALERT: Send FATAL : Bad certificate Alert to 192.168.50.227:5246
*Jun 5 23:43:09.012: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.50.227:5246
*Jun 5 23:43:09.012: %CAPWAP-3-ERRORLOG: Invalid event 38 & state 3 combination.
*Jun 5 23:44:14.003: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jun 5 23:43:09.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.50.227 peer_port: 5246
*Jun 5 23:43:09.009: %CAPWAP-3-ERRORLOG: Failed to authorize controller using trust config.
*Jun 5 23:43:09.009: %CAPWAP-1-SSC_CERT_AUTH_FAILED: Failed to authorize controller, SSC certificate validation failed.Peer certificate verification failed FFFFFFFF
A good tip on how to get this working would be nice. :-)
Can I clear the AP from rommon in some way?
CheerDisable hash validation on the wlc but it did not work.
And I tried, from rommon, the 'sscoff' but coulde'nt see any results. Do you now what that command does?
In the link you sent there was commands to clear the capwap settings on the AP
'test capwap erase'
'test capwap restart'
After these commands I got another error in tha AP log:
PKI-3-CERTIFICATE_INVALID_NOT_YET_VALID
When I look at the WLC I see that the self signed certificate is valid from to day, 6/6?
I configured the NTP server during setup yesterday so I dont understand how date could be a problem/be wrong on the ssc? I checked time and date an both AP abd vWLC but I did'nt check start date on the certificate...
The AP is on UTC and the WLC on GMT+1 so I'll have to wait 2 hours to see if that was the problem :-)
(tried to set the clock on the AP but It keeps changing back?)
(Cisco Controller) >show certificate ssc
SSC Hash validation.............................. Disabled.
SSC Device Certificate details:
Subject Name :
C=US, ST=California, L=San Jose, O=Cisco Virtual Wireless LAN Controller,
CN=DEVICE-vWLC-AIR-CTVM-K9-000C29E255EE, MAILTO=[email protected]
Validity :
Start : 2013 Jun 6th, 22:49:27 GMT
End : 2023 Apr 15th, 22:49:27 GMT
Hash key : 2d56a1c88e549e8ce66b67770aff8539c4f85cd2
(Cisco Controller) >show time
Time............................................. Thu Jun 6 22:22:41 2013
Timezone delta................................... 0:0
Timezone location................................ (GMT +1:00) Amsterdam, Berlin, Rome, Vienna
NTP Servers
NTP Polling Interval......................... 84000
Index NTP Key Index NTP Server NTP Msg Auth Status
1 0 193.11.166.36 AUTH DISABLED
Cheers -
Cisco 3602e CAPWAP will not join vWLC
I am having a rather troubling issue. I had an access point that was connected to my virtual wireless lan controller. It worked fine in the testing environment, but then I tried to roll the environment over to production. This meant connecting the AP to the primary Wireless Lan Controller. The original lan controller would have become the primary but I could not get the management interface moved over to the VLAN I wanted it on.
(Not sure why that did not work, but regardless I had to reinstall the controller and enter 3 as the VLAN during the initial config to get it to take.)
So now I am trying to connect the AP to a new controller and the old controller is gone. No matter what I try it will not connect. My controller says that there is not an entry in the database. The times on the 2 devices do not match up, and the certificate fails during the initialization process. I cannot set the time on the AP because I cannot connect to it. So I just set the wrong time on my controller so they would match, but no luck there either. I cannot connect via the console port on any speed or setting for flow control. I cannot telnet or SSH. I can access the web interface but I have no options to change anything. I am told that running a write erase command on the AP will reset it so I can connect it to the new controller, but I cannot access this device to run that command. Is there a fault in the console port on this device? Is there any other way to force this device to join the new controller? I already tried setting it as the master controller and removing the arp cache. No idea how to remove the MAC cache. I get the error that the AP is not found in the temporary database. Is there any way I can add it manually? It fails on the certificate, can I disable the use of certificates/authentication of any kind at least until I can wipe this AP?Just wanted to note that I was able to gain access to my AP finally. The console cable I was using was bad. Now I have a different issue. Apparently the IOS is corrupt and wont boot. I tried changing the os to a different version within the flash folder, which got the device to boot, but then it rebooted right back into the other IOS and failed when I restarted the AP. I entered the set boot command with the image name of the working IOS but that did not seem to do anything. I then deleted the faulty IOS and now the boot process just cycles even when manually tell it to boot from the one that worked. Is there a location on the device that keeps an archive of the IOS? I would like to just erase my flash folder and start over with a new IOS.
If no archive then is there a location where I can download the IOS for this? I want to try to avoid Cisco smartnet... I feel troubled paying thousands for something that I already own. -
LAP not joining WiSM in Virtualization mode
hi
I have 2 WiSM running in virtualization mode, the AP are not able join, knowing that i am running DHCP locally on the core switch and there is no DNS server, when I checked the boot of the access point it is saying it is unable to receive vci code and unable to resolve CISCO-LWAPP-CONTROLLER. the access point is 1252. I tried the configuration of option 43 on the core when the dhcp is located but it is not working do u have any running configuration for this?
Thanks,
ElieThe access point can discover controllers through your domain name server (DNS). For the access point to do so, you must configure your DNS to return controller IP addresses in response to CISCO-LWAPP-CONTROLLER.localdomain, where localdomain is the access point domain name. When an access point receives an IP address and DNS information from a DHCP server, it contacts the DNS to resolve CISCO-LWAPP-CONTROLLER@localdomain. When the DNS sends a list of controller IP addresses, the access point sends discovery requests to the controllers.
-
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. -
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
Jeroenthnx 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 -
I am working with a vWLC on 7.4 code with a 3500i AP on 12.4(23c)JA code. The AP is not joining the controller automatically here is the output from the AP during a join failure,
*Jul 15 09:57:58.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.2.98.225 peer_port: 5246
*Jul 15 09:57:59.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Jul 15 09:57:59.016: %LWAPP-3-CLIENTERRORLOG: Peer certificate verification failed
*Jul 15 09:57:59.016: %CAPWAP-3-ERRORLOG: Certificate verification failed!
*Jul 15 09:57:59.016: DTLS_CLIENT_ERROR: ../capwap/capwap_wtp_dtls.c:333 Certificate verified failed!
*Jul 15 09:57:59.016: %DTLS-4-BAD_CERT: Certificate verification failed. Peer IP: 10.2.98.225
*Jul 15 09:57:59.016: %DTLS-5-SEND_ALERT: Send FATAL : Bad certificate Alert to 10.2.98.225:5246
*Jul 15 09:57:59.016: %DTLS-3-BAD_RECORD: Erroneous record received from 10.2.98.225: Malformed Certificate
*Jul 15 09:57:59.016: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.2.98.225:5246
*Jul 15 09:57:59.016: %CAPWAP-3-ERRORLOG: Invalid event 38 & state 3 combination.
*Jul 15 09:58:18.881: %CDP_PD-2-POWER_LOW: All radios disabled - NON_CISCO-NO_CDP_RECEIVED (0000.0000.0000)
From my research about this issue I should be able to do debug pm pki enable and get the SSC key hash and join the AP manually to the controller. When I do the debug I do not see the SSC key hash, I only see,
(Cisco Controller) >*sshpmLscTask: Jul 15 09:46:08.268: sshpmLscTask: LSC Task received a message 4
*spamApTask1: Jul 15 09:57:58.190: 50:3d:e5:f0:dc:f1 Discovery Request from 10.2.98.3:3536
*spamApTask1: Jul 15 09:57:58.190: 50:3d:e5:f0:dc:f1 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 200, joined Aps =0
*spamApTask1: Jul 15 09:57:58.190: 50:3d:e5:f0:dc:f1 Discovery Response sent to 10.2.98.3:3536
*spamApTask1: Jul 15 09:57:58.190: 50:3d:e5:f0:dc:f1 Discovery Response sent to 10.2.98.3:3536
*spamApTask1: Jul 15 09:58:09.121: 50:3d:e5:f0:dc:f1 DTLS connection not found, creating new connection for 10:2:98:3 (3536) 10:2:98:225 (5246)
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCID: called to evaluate <cscoDefaultIdCert>
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCID: comparing to row 0, CA cert >bsnOldDefaultCaCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCID: comparing to row 1, CA cert >bsnDefaultRootCaCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCID: comparing to row 2, CA cert >bsnDefaultCaCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCID: comparing to row 3, CA cert >bsnDefaultBuildCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCID: comparing to row 4, CA cert >cscoDefaultNewRootCaCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCID: comparing to row 5, CA cert >cscoDefaultMfgCaCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCID: comparing to row 0, ID cert >bsnOldDefaultIdCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCID: comparing to row 1, ID cert >bsnDefaultIdCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCID: comparing to row 2, ID cert >cscoDefaultIdCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCertFromCID: called to get cert for CID 1234873a
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCertFromCID: comparing to row 0, certname >bsnOldDefaultCaCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCertFromCID: comparing to row 1, certname >bsnDefaultRootCaCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCertFromCID: comparing to row 2, certname >bsnDefaultCaCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCertFromCID: comparing to row 3, certname >bsnDefaultBuildCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCertFromCID: comparing to row 4, certname >cscoDefaultNewRootCaCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCertFromCID: comparing to row 5, certname >cscoDefaultMfgCaCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCertFromCID: comparing to row 0, certname >bsnOldDefaultIdCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCertFromCID: comparing to row 1, certname >bsnDefaultIdCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCertFromCID: comparing to row 2, certname >cscoDefaultIdCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCID: called to evaluate <cscoDefaultIdCert>
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCID: comparing to row 0, CA cert >bsnOldDefaultCaCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCID: comparing to row 1, CA cert >bsnDefaultRootCaCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCID: comparing to row 2, CA cert >bsnDefaultCaCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCID: comparing to row 3, CA cert >bsnDefaultBuildCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCID: comparing to row 4, CA cert >cscoDefaultNewRootCaCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCID: comparing to row 5, CA cert >cscoDefaultMfgCaCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCID: comparing to row 0, ID cert >bsnOldDefaultIdCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCID: comparing to row 1, ID cert >bsnDefaultIdCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetCID: comparing to row 2, ID cert >cscoDefaultIdCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetSshPrivateKeyFromCID: called to get key for CID 1234873a
*spamApTask1: Jul 15 09:58:09.121: sshpmGetSshPrivateKeyFromCID: comparing to row 0, certname >bsnOldDefaultIdCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetSshPrivateKeyFromCID: comparing to row 1, certname >bsnDefaultIdCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetSshPrivateKeyFromCID: comparing to row 2, certname >cscoDefaultIdCert<
*spamApTask1: Jul 15 09:58:09.121: sshpmGetSshPrivateKeyFromCID: match in row 2
*spamApTask3: Jul 15 09:58:09.139: 50:3d:e5:f0:dc:f1 DTLS connection closed event receivedserver (10:2:98:225/5246) client (10:2:98:3/3536)
*spamApTask3: Jul 15 09:58:09.139: 50:3d:e5:f0:dc:f1 No entry exists for AP (10:2:98:3/3536)
*spamApTask3: Jul 15 09:58:09.139: 50:3d:e5:f0:dc:f1 No AP entry exist in temporary database for 10.2.98.3:3536
What else can I try to get this AP to join the controller??
Thank you."configure certificate ssc hash validation disable" didn't help, same problems
I tried to add the AP by its MAC and MIC to the authorized APs list but it just tells me "
50:3d:e5:f0:dc:f1 No AP entry exist in temporary database for 10.2.98.3:3536"
The SSC key Hash still doesn't show in the debug output. What else can I try? -
Hello community,
I hope you can help me with my problem.
I have a vWLC Firmware version: 7.4.121.0, I have also Aironet 1700Aps
I have successfully configured wlc with service and management interface. In the management network I can ping the vWLC managenemt interface as well the APs in this network. The firewall is also the DHCP Server for the management network. (It is working because APs get an IP address) The problem is the APs are not joining the vWLC. This is my first time I use WLC and APs. So they are completely new and not used before.
Here is the debug output of vWLC:
ApTask4: Feb 11 16:31:07.997: 84:80:2d:bd:fa:10 Finding DTLS connection to delete for AP (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:07.997: 84:80:2d:bd:fa:10 Disconnecting DTLS Capwap-Ctrl session 0x8faa580 for AP (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:07.997: 84:80:2d:bd:fa:10 CAPWAP State: Dtls tear down
*spamApTask4: Feb 11 16:31:07.998: 84:80:2d:bd:fa:10 DTLS connection closed event receivedserver (192:168:200:3/5246) client (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:07.998: 84:80:2d:bd:fa:10 Entry exists for AP (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:07.998: 84:80:2d:bd:fa:10 No AP entry exist in temporary database for 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.004: 84:80:2d:bd:fa:1e DTLS connection not found, creating new connection for 192:168:200:10 (57250) 192:168:200:3 (5246)
*spamApTask4: Feb 11 16:31:08.472: 84:80:2d:bd:fa:1e DTLS Session established server (192.168.200.3:5246), client (192.168.200.10:57250)
*spamApTask4: Feb 11 16:31:08.472: 84:80:2d:bd:fa:1e Starting wait join timer for AP: 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.477: 84:80:2d:bd:fa:10 Join Request from 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.477: 84:80:2d:bd:fa:1e Deleting AP entry 192.168.200.10:57250 from temporary database.
*spamApTask4: Feb 11 16:31:08.477: 84:80:2d:bd:fa:10 Finding DTLS connection to delete for AP (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:08.477: 84:80:2d:bd:fa:10 Disconnecting DTLS Capwap-Ctrl session 0x8faa720 for AP (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:08.477: 84:80:2d:bd:fa:10 CAPWAP State: Dtls tear down
*spamApTask4: Feb 11 16:31:08.479: 84:80:2d:bd:fa:10 DTLS connection closed event receivedserver (192:168:200:3/5246) client (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:08.479: 84:80:2d:bd:fa:10 Entry exists for AP (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:08.479: 84:80:2d:bd:fa:10 No AP entry exist in temporary database for 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.515: 84:80:2d:bd:fa:10 Discovery Request from 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.515: 84:80:2d:bd:fa:10 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 200, joined Aps =0
*spamApTask4: Feb 11 16:31:08.515: 84:80:2d:bd:fa:10 Discovery Response sent to 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.515: 84:80:2d:bd:fa:10 Discovery Response sent to 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.516: 84:80:2d:bd:fa:10 Discovery Request from 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.516: 84:80:2d:bd:fa:10 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 200, joined Aps =0
*spamApTask4: Feb 11 16:31:08.516: 84:80:2d:bd:fa:10 Discovery Response sent to 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.516: 84:80:2d:bd:fa:10 Discovery Response sent to 192.168.200.10:57250
*spamApTask0: Feb 11 16:31:08.516: 84:80:2d:bd:fa:1e Received LWAPP DISCOVERY REQUEST to 40:4a:03:79:d7:20 on port '1'
*spamApTask0: Feb 11 16:31:08.516: 84:80:2d:bd:fa:1e Discarding discovery request in LWAPP from AP supporting CAPWAP
Sadly I don`t have a debuging cable for the APs. Therefore I have no debuging output of the APs. (It is ordered ;-) )
But I hope the output of the APs is right now not important to solve this problem.
Thank you
//EDIT
On the firewall are no ports blockedOkay I upgraded the vWLC to 8.0.110.0.
I looked in the event log of the vWLC. It was successfully discovered and also the new image version was send to the AP.
Sadly the Ap does not join to the vWLC.
*apfReceiveTask: Feb 12 09:53:35.640: WARP IEs: (12)
*apfReceiveTask: Feb 12 09:53:35.640: [0000] dd 0a 00 c0 b9 01 00 00 00 08 01 01
*apfReceiveTask: Feb 12 09:53:35.640: Wlan Feature status 0 for AP:84:80:2d:45:75:e0 (slotID 1)
*apfReceiveTask: Feb 12 09:53:35.640: Split tunnel status (Disabled) encoded in the vap payload for WLAN(1), AP:84:80:2d:45:75:e0 (slotID 1)
*spamApTask5: Feb 12 09:53:35.789: 84:80:2d:45:75:e0 Configuration Status from 192.168.200.10:57251
*spamApTask5: Feb 12 09:53:35.789: 84:80:2d:45:75:e0 CAPWAP State: Configure
*spamApTask5: Feb 12 09:53:35.789: 84:80:2d:45:75:e0 Updating IP info for AP 84:80:2d:45:75:e0 -- static 0, 192.168.200.10/255.255.255.0, gtw 192.168.200.3
*spamApTask5: Feb 12 09:53:35.789: 84:80:2d:45:75:e0 Updating IP 192.168.200.10 ===> 192.168.200.10 for AP 84:80:2d:45:75:e0
*spamApTask5: Feb 12 09:53:35.789: 84:80:2d:45:75:e0 Invalid length (9) countedlen 6 sizeUserPayload 277 for vendor-specific element 0x00409600-unknown (185) from AP 84:80:2D:45:75:E0
*spamApTask5: Feb 12 09:53:35.790: 84:80:2d:45:75:e0 Setting MTU to 1485
*spamApTask5: Feb 12 09:53:35.790: 84:80:2d:45:75:e0 Finding DTLS connection to delete for AP (192:168:200:10/57251)
*spamApTask5: Feb 12 09:53:35.790: 84:80:2d:45:75:e0 Disconnecting DTLS Capwap-Ctrl session 0xb947000 for AP (192:168:200:10/57251)
*spamApTask5: Feb 12 09:53:35.790: 84:80:2d:45:75:e0 CAPWAP State: Dtls tear down
*spamApTask5: Feb 12 09:53:35.791: 84:80:2d:45:75:e0 DTLS connection closed event receivedserver (192.168.200.3/5246) client (192.168.200.10/57251)
*spamApTask5: Feb 12 09:53:35.791: 84:80:2d:45:75:e0 Entry exists for AP (192.168.200.10/57251)
*spamApTask5: Feb 12 09:53:35.791: 84:80:2d:45:75:e0 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 84:80:2d:45:75:e0 slot 0
*spamApTask5: Feb 12 09:53:35.791: 84:80:2d:45:75:e0 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 84:80:2d:45:75:e0 slot 1
*spamApTask5: Feb 12 09:53:35.791: update ap status:84:80:2d:45:75:e0 ,index:60
*spamApTask5: Feb 12 09:53:35.791: 84:80:2d:45:75:e0 No AP entry exist in temporary database for 192.168.200.10:57251
*apfReceiveTask: Feb 12 09:53:35.792: 84:80:2d:45:75:e0 Deregister LWAPP event for AP 84:80:2d:45:75:e0 slot 0
*apfReceiveTask: Feb 12 09:53:35.792: 84:80:2d:45:75:e0 Deregister LWAPP event for AP 84:80:2d:45:75:e0 slot 1
*spamApTask4: Feb 12 09:53:35.918: 84:80:2d:45:75:e0 Discovery Request from 192.168.200.10:57250
*spamApTask4: Feb 12 09:53:35.918: 84:80:2d:45:75:e0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 200, joined Aps =0
*spamApTask4: Feb 12 09:53:35.918: apModel: AIR-CAP702I-C-K9
*spamApTask4: Feb 12 09:53:35.918: apType = 45 apModel: AIR-CAP702I-C-K9
*spamApTask4: Feb 12 09:53:35.918: 84:80:2d:45:75:e0 Discovery Response sent to 192.168.200.10 port 57250
*spamApTask4: Feb 12 09:53:35.918: 84:80:2d:45:75:e0 Discovery Response sent to 192.168.200.10:57250
*spamApTask4: Feb 12 09:53:35.919: 84:80:2d:45:75:e0 Discovery Request from 192.168.200.10:57250
*spamApTask4: Feb 12 09:53:35.919: 84:80:2d:45:75:e0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 200, joined Aps =0
*spamApTask4: Feb 12 09:53:35.919: apModel: AIR-CAP702I-C-K9
*spamApTask4: Feb 12 09:53:35.919: apType = 45 apModel: AIR-CAP702I-C-K9
*spamApTask4: Feb 12 09:53:35.919: 84:80:2d:45:75:e0 Discovery Response sent to 192.168.200.10 port 57250
*spamApTask4: Feb 12 09:53:35.919: 84:80:2d:45:75:e0 Discovery Response sent to 192.168.200.10:57250
Sadly I don`t understand what this debugging log says :-(
Maybe you can help me again
Thank you
//SOLUTION -----------------------------------------------------------------------------------------------------------------------------------------------------------
I found something on the internet, but for all people having also this problem here is the solution:
Change the country of your vWLC. Right now I am in China, so I changed it and then it was working flawlessly :-)
Step 1
Disable the 802.11 networks as follows:
Choose Wireless > 802.11a/n > Network.
Unselect the 802.11a Network Status check box.
Click Apply.
Choose Wireless > 802.11a/n > Network.
Unselect the 802.11b/g Network Status check box.
Click Apply.
Step 2
Choose Wireless > Country to open the Country page.
Thank you all for your help :-)
Paul -
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. -
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 -
1242AG Lap wont come up :error power low
hi
i have a cisco 1242AG lap that uses PoE and connects to a C2950-24 switch.When connected to the switch via a power injector or directly to the swicth with TP cable the access point does powerup but after that the reports that the power is too low.
when i feed the lap with power without using PoE the it comes up though
i suspect that this might have something to do with inline power in the swicth...please assist.The Cisco AP1242 requires a power source that can do IEEE 802.3af. Check the power capability of your particular switch, it needs to be able to supply 15 Watts. Many earlier powered switches can supply power but at a lesser wattage (say 6-8 Watts).
The AP can learn from Cisco CDP what the capability of the switch is and if it can not provide enough power the AP will attempt to come up without radios active or warn that the power is too low.
Again, the powered switch does NEED to be able to support IEEE 802.3af PoE and needs to be able to supply up to 15 Watts of power.
Maybe you are looking for
-
How to link a radio button selection to a submit destination ?
Hi, I am working on a JSP page. Depending on the check from a radio button on a form, the form will be submitted to a different destination. Does anyone know how to do that? Any code samples? Thanks! wyp
-
How do you get OS X Lion to authenticate against LDAP?
Need help getting OpenLDAP to authenticate against LDAP on Linux server....please help!
-
Hi, I want to use XSLT in my abap program : CALL TRANSFORMATION 'name of the XSLT program'. where should i code the XSLT ? i'm using sap 4.6c. Thanks Ihsen
-
Wildcards in type declarations or only methods?
Can you declare wildcards in type declarations such as: public class ListManager<List<?>> { }When I try this, I get the following compiler errror: C:\dev\hcj\tiger\src>c:\j2sdk1.5.0\bin\javac -source 1.5 oreilly/hcj/tiger/*.java oreilly/hcj/tiger/Lis
-
Using the cloud in a unsupported country
I want to use the programs in the creative cloud. I can get a membership while in my home county of Canada, but will I still be able to do the monthly internet validation/updates while in central/south america which is not on the list where this prod