3502 AP not join 5500 series WLC
I have 5508 wireless lan controller and 3502 AP. I did all configuration on WLC using the configuration guide. But AP don't join the WLC. AP can assign an IP address and i can ping this IP from WLC. When i connect the AP from console i see the logs below;
*Mar 1 15:36:57.128: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLL ER
Not in Bound state.
*Mar 1 15:37:42.637: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
*Mar 1 15:37:46.730: %CAPWAP-3-ERRORLOG: Invalid event 38 & state 2 combination.
*Mar 1 15:37:46.793: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP addres s 10.17.25.13, mask 255.255.255.0, hostname AP4c00.82e9.a218
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 1 15:37:53.638: %CAPWAP-3-ERRORLOG: Did not get log server settings from DH CP.
I research similar problems in forums and i implement all they said but i can't solve the problem. there are also DHCP options below;
ddns-update-style interim;
allow bootp;
option space Cisco_LWAPP_AP;
option Cisco_LWAPP_AP.server-address code 43 = string;
subnet 10.17.25.0 netmask 255.255.255.0 {
authoritative;
option routers 10.17.25.1;
option subnet-mask 255.255.255.0;
range dynamic-bootp 10.17.25.10 10.17.25.20;
default-lease-time 300;
class "Cisco-AP-c3500" {
match if option vendor-class-identifier = "Cisco AP c3500";
option vendor-class-identifier "Cisco AP c3500";
vendor-option-space Cisco_LWAPP_AP;
option Cisco_LWAPP_AP.server-address f1:04:0a:11:07:0a; (Management IP : 10.17.7.10 )
What could be the cause of problem ??
Try changing your option 43 address to look like this:
f104.0a11.070a
Steve
Sent from Cisco Technical Support iPhone App
Similar Messages
-
5500 Series WLC internal DHCP Server - Exclusion?
Hi there,
We're using the internal DHCP server on our 5500 Series WLC which works fine.
However on one WLAN we ran out of addresses so changed the subnet from a /25 to a /24.
The problem is that the router/gateway is still in the middle (124/125/126) and not easily changed.
I've moved the WLC interface to the top of the subnet (251) but the router is more difficult as its externally managed/controlled.
So is there a way we can create a DHCP pool of .1 through 250 on a /24 mask but exclude 124/125/126?
Thanks
Mike
PS - Router subnet masks were changed so can see whole subnet.Mike,
The WLC isn't a fully functional DHCP server, it only allows you to define what is in scope, not what is out of scope. Now if you have a cisco router/switch, you could use that for the DHCP server and specifically exclude the necessary addresses.
HTH,
Steve -
Cisco 5500 Series WLC Field Recovery Compatibility
Is Software Version 7.2.111.3 compatible with Field Recovery Image Version 7.6.95.16.
Duplicate posts.
Go here: http://supportforums.cisco.com/discussion/12154556/cisco-5500-series-wlc-field-recovery-compatibility -
Guest wireless setup not working on 5500 series WLC
I have a 5508 core WLC with a 3850 as the local controller for an AP3G2-K9W8-M Access Point. The 3850 and the core WLC both have the wireless guest WLAN configured. My client can see the wireless LAN. When it tries to connect, it fails.
Can you give me debug commands that I can run on the AP, 3850, and/or WLC to try to determine why it won't connect?Thanks! I ran the debug - but I haven't found anything in it yet to help. Hopefully I have overlooked something that will help.
I created a test wlan with no security and it is not connecting either. Any additional thoughts would be greatly appreciated.
(Cisco Controller) >debug client 48-F8-B3-AE-EC-CF
(Cisco Controller) >*mmMaListen: Dec 26 19:31:19.493: 48:f8:b3:ae:ec:cf Adding mob
ile on Remote AP 00:00:00:00:00:00(0)
*mmMaListen: Dec 26 19:31:19.493: 48:f8:b3:ae:ec:cf Scheduling deletion of Mobile
Station: (callerId: 69) in 1 seconds
*osapiBsnTimer: Dec 26 19:31:20.461: 48:f8:b3:ae:ec:cf apfMsExpireCallback (apf_ms
.c:626) Expiring Mobile!
*apfReceiveTask: Dec 26 19:31:20.462: 48:f8:b3:ae:ec:cf pemApfDeleteMobileStation2
: APF_MS_PEM_WAIT_L2_AUTH_COMPLETE = 0.
*apfReceiveTask: Dec 26 19:31:20.462: 48:f8:b3:ae:ec:cf 0.0.0.0 START (0) Deleted
mobile LWAPP rule on AP [00:00:00:00:00:00]
*apfReceiveTask: Dec 26 19:31:20.462: 48:f8:b3:ae:ec:cf Deleting mobile on AP 00:0
0:00:00:00:00(0)
*mmMaListen: Dec 26 19:31:20.485: 48:f8:b3:ae:ec:cf Adding mobile on Remote AP 00:
00:00:00:00:00(0)
*mmMaListen: Dec 26 19:31:20.485: 48:f8:b3:ae:ec:cf Scheduling deletion of Mobile
Station: (callerId: 69) in 1 seconds
*osapiBsnTimer: Dec 26 19:31:21.461: 48:f8:b3:ae:ec:cf apfMsExpireCallback (apf_ms
.c:626) Expiring Mobile!
*apfReceiveTask: Dec 26 19:31:21.462: 48:f8:b3:ae:ec:cf pemApfDeleteMobileStation2
: APF_MS_PEM_WAIT_L2_AUTH_COMPLETE = 0.
*apfReceiveTask: Dec 26 19:31:21.462: 48:f8:b3:ae:ec:cf 0.0.0.0 START (0) Deleted
mobile LWAPP rule on AP [00:00:00:00:00:00]
*apfReceiveTask: Dec 26 19:31:21.462: 48:f8:b3:ae:ec:cf Deleting mobile on AP 00:0
0:00:00:00:00(0)
*mmMaListen: Dec 26 19:31:21.476: 48:f8:b3:ae:ec:cf Adding mobile on Remote AP 00:
00:00:00:00:00(0)
*mmMaListen: Dec 26 19:31:21.476: 48:f8:b3:ae:ec:cf Scheduling deletion of Mobile
Station: (callerId: 69) in 1 seconds
*osapiBsnTimer: Dec 26 19:31:22.461: 48:f8:b3:ae:ec:cf apfMsExpireCallback (apf_ms
.c:626) Expiring Mobile!
*apfReceiveTask: Dec 26 19:31:22.462: 48:f8:b3:ae:ec:cf pemApfDeleteMobileStation2
: APF_MS_PEM_WAIT_L2_AUTH_COMPLETE = 0.
*apfReceiveTask: Dec 26 19:31:22.462: 48:f8:b3:ae:ec:cf 0.0.0.0 START (0) Deleted
mobile LWAPP rule on AP [00:00:00:00:00:00]
*apfReceiveTask: Dec 26 19:31:22.462: 48:f8:b3:ae:ec:cf Deleting mobile on AP 00:0
0:00:00:00:00(0) -
Hi,
I have an existing setup where in i have a 4400 WLC and AP 1242 registered to it.
I had to replace the WLC with a new 5500 WLC. I tried registering the the 1242 AP with this new controller but i'm getting the following error message:
AP0026.0b4d.093a#
*Apr 25 07:51:59.216: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.7.51.11:5246
Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Apr 25 07:52:13.735: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER
AP0026.0b4d.093a#
Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)
*Apr 25 07:52:22.736: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Apr 25 07:52:22.736: %CAPWAP-3-ERRORLOG: Dropping dtls packet since session is not established.
*Apr 25 07:52:22.794: %WIDS-6-DISABLED: IDS Signature is removed and disabled.
*Apr 25 07:52:22.795: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Apr 25 07:52:22.796: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Apr 25 07:52:22.863: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Apr 25 07:52:22.863: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Apr 25 07:52:22.885: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Apr 25 07:52:22.885: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Apr 25 07:52:22.886: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Apr 25 07:52:22.918: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Apr 25 07:52:22.918: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Apr 25 07:52:22.946: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Apr 25 07:52:22.947: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Apr 25 07:52:31.885: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER
*Apr 25 07:52:40.886: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Apr 25 07:52:40.888: status of voice_diag_test from WLC is false
*Apr 25 07:52:40.889: %CAPWAP-3-ERRORLOG: Could not send primary discoveryrequest. The CAPWAP state has not moved to RUN yet
*Apr 25 07:52:40.890: %CAPWAP-3-ERRORLOG: Could not send primary discoveryrequest. The CAPWAP state has not moved to RUN yet
*Apr 25 07:52:40.900: %LWAPP-3-CLIENTERRORLOG: Primary Discovery Reply: received primary discovery reply when connected to a Primary/Secondary/Tertiary controller
*Apr 25 07:52:50.887: %CAPWAP-3-ERRORLOG: Selected MWAR 'L&T-WLC-Powai'(index 0).
*Apr 25 07:52:50.887: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Apr 25 13:23:03.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.5.3 peer_port: 5246
*Apr 25 13:23:03.001: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Apr 25 13:23:04.717: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.5.3 peer_port: 5246
*Apr 25 13:23:04.718: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.5.3
*Apr 25 13:23:04.718: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Apr 25 13:23:04.719: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.5.3
*Apr 25 13:23:04.719: %DTLS-5-PEER_DISCONNECT: Peer 172.16.5.3 has closed connection.
*Apr 25 13:23:04.720: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.16.5.3:5246
*Apr 25 13:23:04.721: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Apr 25 07:52:41.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.7.51.11 peer_port: 5246
*Apr 25 07:52:41.001: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Apr 25 07:52:42.449: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.7.51.11 peer_port: 5246
*Apr 25 07:52:42.450: %CAPWAP-5-SENDJOIN: sending Join Request to 10.7.51.11
*Apr 25 07:52:42.450: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Apr 25 07:52:42.647: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Apr 25 07:52:42.794: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Apr 25 07:52:42.807: %CAPWAP-5-CHANGED: CAPWAP changed state to UP
*Apr 25 07:52:42.808: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Apr 25 07:52:42.879: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller WLC1-T
*Apr 25 07:52:42.940: %LWAPP-3-CLIENTEVENTLOG: SSID LTHE-Mobile added to the slot[0]
Writing out the event log to nvram...
The AP is getting a close message from the new controller. What could the issue be?After the AP gets a close message from the new WLC, it gets re associated to the old WLC.
-
Hi,
I setup a mini wireless LAN network lab with a not for resale 2106 wireless lan controller and a sales air-lap1242ag access point. I do not have a DHCP and DNS in my lab environment. I have configured the WLC with the basic configuration using the CLI wizard, i also configured the WLC as a DHCP server for clients that will be connecting to the APs associated to the controller.
I powered up the AP and connect the ethernet port directly to the controller, the controller issued an IP address to the AP, the AP downloaded a new operating system from the controller but failed to join the controller.
I check both debug message on the controller console and the trap messages on the controller's GUI and it say the AP could not download a configuration from the controller and it is beacuse of invalid license. Below is the trap message:
Configuration Phase Statistics
Requests Received
Responses Sent
Unsuccessful Request Processed
Reason For Last Unsuccessful Attempt
Last Successful Attempt Time
Last Unsuccessful Attempt Time
Last Error Summary
Last AP Message Decryption Failure
Last AP Connection Failure
Last Error Occurred
Last Error Occurred Reason
Last Join Error Timestamp
Also, I tried to log into the GUI of the AP using the both the username and password ''Cisco'' but I cannot get into the device. I can only get in through the CLI. In the CLI, almost all the commands I enter gives an error the it is disabled. I don't know what to do any more, I want to know if the access point is faulty or i am not doing the right thing.
PLEASE HELP!!!!!!!!!!!!!!!!!!!Thank you for the quick response.
The controller is running firmware version:
Software Version 6.0.199.4
Emergency Image Version 6.0.199.4
The AP can ping the Management IP address of the controller successfully via console. I have also entered in the AP the WLC's Management IP address information and it is still the same. Below is the message I'm getting on the console of the AP it self:
*Jul 9 13:06:09.803: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jul 9 13:06:10.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip:
192.168.50.246 peer_port: 5246
*Jul 9 13:06:10.001: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Jul 9 13:06:11.636: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully
peer_ip: 192.168.50.246 peer_port: 5246
*Jul 9 13:06:11.638: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.50.246
*Jul 9 13:06:11.638: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Jul 9 13:06:11.724: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Jul 9 13:06:11.726: %DTLS-5-ALERT: Received WARNING : Close notify alert from
192.168.50.246
*Jul 9 13:06:11.727: %DTLS-5-PEER_DISCONNECT: Peer 192.168.50.246 has closed conne
ction.
*Jul 9 13:06:11.727: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 1
92.168.50.246:5246
*Jul 9 13:06:11.772: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Jul 9 13:06:11.772: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
I will also like to know if AIR-LAP1242AG is compatible with WLC 2106 controller.
Any help will be greatly appreciated, i really need to resolve this issue in my LAB now so that I don't go to my customer site to fumble.
thanks in advance. -
AIR-CAP3702I booting up in mesh mode and not joining our 5508 WLC
I have a batch of 30+ AIR-CAP3702I-A-K9 APs that I need to setup but none of them are joining to the 5508 WLC and when I connect a console cable and view the output from the AP it shows that it is trying to initiate in mesh mode. I have read other forums that are showing that I need to put in the APs MAC address to a filter list on the WLC for it to show up and then I will be able to change it from mesh mode to local mode. The only issue I'm having with that solution is not knowing how it will affect my current production environment off of that 5508 WLC. I have 69 active production APs with clients working off them and there are no MAC filters currently in place on the WLC. By adding a MAC filter entry for the new APs would the WLC create an implicit deny for all other clients that don't have their MAC addresses entered?? If so is there another work around? Can the mode be changed via the CLI on the AP itself to make it local instead of mesh?
sh capwap client rcb
AdminState : ADMIN_ENABLED
SwVer : 7.6.1.118
NumFilledSlots : 2
Name : AP88f0.4290.7184
Location : default location
MwarName : xxxxx
MwarApMgrIp : x.x.x.x !<it has the correct name and IP of the WLC>
MwarHwVer : 0.0.0.0
ApMode : Bridge
ApSubMode : Not Configured
OperationState : JOIN
CAPWAP Path MTU : 576
LinkAuditing : disabled
ApRole : MeshAP
ApBackhaul : 802.11a
ApBackhaulChannel : 0
ApBackhaulSlot : 2
ApBackhaul11gEnabled : 0
ApBackhaulTxRate : 24000
Ethernet Bridging State : 0
Public Safety State : disabled
AP Rogue Detection Mode : Enabled
AP Tcp Mss Adjust : Disabled
AP IPv6 TCP MSS Adjust : Disabled
Predownload Status : None
Auto Immune Status : Disabled
RA Guard Status : Disabled
Efficient Upgrade State : Disabled
Efficient Upgrade Role : None
TFTP Server : Disabled
Antenna Band Mode : Unknown
802.11bg(0) Radio
ADMIN State = ENABLE [1]
OPER State = DOWN [1]
CONFIG State = UP [2]
HW State = UP [4]
Radio Mode : Bridge
GPR Period : 0
Beacon Period : 0
DTIM Period : 0
World Mode : 1
VoceraFix : 0
Dfs peakdetect : 1
Fragmentation Threshold : 2346
Current Tx Power Level : 0
Current Channel : 11
Current Bandwidth : 20
802.11a(1) Radio
ADMIN State = ENABLE [1]
OPER State = DOWN [1]
CONFIG State = UP [2]
HW State = UP [4]
Radio Mode : Bridge
GPR Period : 0
Beacon Period : 0
DTIM Period : 0
World Mode : 1
VoceraFix : 0
Dfs peakdetect : 1
Fragmentation Threshold : 2346
Current Tx Power Level : 1
Current Channel : 165
Current Bandwidth : 20
It is showing the following error on our WLC in the log file:
Tue Jul 15 14:01:26 2014
AAA Authentication Failure for UserName:88f042907184 User Type: WLAN USER
And here are some of the errors it's showing on the AP after bootup:
*Jul 15 17:47:30.471: %CAPWAP-5-SENDJOIN: sending Join Request to x.x.x.x
*Jul 15 17:47:31.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jul 15 17:47:31.031: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jul 15 17:47:31.039: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jul 15 17:47:31.047: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jul 15 17:47:32.067: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jul 15 17:47:33.067: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jul 15 17:47:35.471: %CAPWAP-5-SENDJOIN: sending Join Request to x.x.x.x
*Jul 15 17:47:35.471: %DTLS-5-ALERT: Received WARNING : Close notify alert from x.x.x.x
*Jul 15 17:47:35.475: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jul 15 17:47:35.483: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jul 15 17:47:36.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jul 15 17:47:36.503: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jul 15 17:47:37.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jul 15 17:48:15.007: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
*Jul 15 17:48:15.007: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
*Jul 15 17:48:15.007: %MESH-6-LINK_UPDOWN: Mesh station 88f0.4290.7184 link Down
*Jul 15 17:48:17.007: %LINK-6-UPDOWN: Interface BVI1, changed state to down
*Jul 15 17:48:22.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to down
*Jul 15 17:59:10.099: %CAPWAP-3-ERRORLOG: Invalid event 31 & state 4 combination
*Jul 15 17:59:10.099: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 31, state 4 -
2602i does not Join to 3850 WLC
Trying to join 2602i to 3850 wlc but after join to WLC, the access point keeps rebooting
AP Console log:
APc067.afa7.1ee4#
*Nov 29 23:32:55.027: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Nov 29 23:32:55.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.129.0.254 peer_port: 5246
*Nov 29 23:32:55.223: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.129.0.254 peer_port: 5246
*Nov 29 23:32:55.223: %CAPWAP-5-SENDJOIN: sending Join Request to 10.129.0.254
., 1)29 23:33:13.415: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(UNKNOWN_MESSAGE_TYPE (5)
*Nov 29 23:33:13.415: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE
*Nov 29 23:33:19.299: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Nov 29 23:33:19.319: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Nov 29 23:33:19.323: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Nov 29 23:33:19.327: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Nov 29 23:33:19.347: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Nov 29 23:33:20.323: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Nov 29 23:33:20.351: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Nov 29 23:33:20.359: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Nov 29 23:33:21.343: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Nov 29 23:33:21.351: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Nov 29 23:33:21.379: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Nov 29 23:33:21.387: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Nov 29 23:33:21.395: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Nov 29 23:33:22.379: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Nov 29 23:33:22.387: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Nov 29 23:33:22.415: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Nov 29 23:33:23.415: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
Not in Bound state.
*Nov 29 23:34:14.847: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
*Nov 29 23:34:19.847: %CAPWAP-3-ERRORLOG: Invalid event 40 & state 2 combination.
*Nov 29 23:34:19.967: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.129.0.212, mask 255.255.255.128, hostname APc067.afa7.1ee4
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Nov 29 23:34:25.847: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Nov 29 23:34:34.847: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Nov 29 23:35:04.847: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Nov 29 23:35:04.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.129.0.254 peer_port: 5246
*Nov 29 23:35:04.223: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.129.0.254 peer_port: 5246
*Nov 29 23:35:04.223: %CAPWAP-5-SENDJOIN: sending Join Request to 10.129.0.254
., 1)29 23:35:22.411: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(UNKNOWN_MESSAGE_TYPE (5)
*Nov 29 23:35:22.411: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE
*Nov 29 23:35:27.479: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Nov 29 23:35:27.499: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Nov 29 23:35:27.499: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Nov 29 23:35:27.503: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Nov 29 23:35:27.527: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Nov 29 23:35:28.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Nov 29 23:35:28.531: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Nov 29 23:35:28.539: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Nov 29 23:35:29.523: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Nov 29 23:35:29.531: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Nov 29 23:35:29.559: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Nov 29 23:35:29.567: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Nov 29 23:35:29.575: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Nov 29 23:35:30.559: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Nov 29 23:35:30.567: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Nov 29 23:35:30.595: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Nov 29 23:35:31.595: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
WLC Log:
Nov 29 23:40:46.469: *%LWAPP-3-RD_ERR7: 1 wcm: Invalid country code () for AP c0:25:5c:68:7f:10
Nov 29 23:40:46.469: *%LWAPP-3-RD_ERR9: 1 wcm: APs c0:25:5c:68:7f:10 country code changed from () to (GB )
Nov 29 23:40:46.470: %CAPWAP-3-AP_PORT_CFG: AP connected port Gi1/0/24 is not an access port.
Nov 29 23:40:46.471: *%LWAPP-3-RD_ERR7: 1 wcm: Invalid country code () for AP c0:25:5c:68:7f:10
Nov 29 23:40:46.471: *%LWAPP-3-RD_ERR9: 1 wcm: APs c0:25:5c:68:7f:10 country code changed from () to (GB )
Nov 29 23:40:46.471: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP c0:25:5c:68:7f:10
54C1BR01A01254#
Nov 29 23:40:46.474: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP c0:25:5c:68:7f:10
Nov 29 23:40:46.474: *%CAPWAP-3-DATA_TUNNEL_CREATE_ERR2: 1 wcm: Failed to create CAPWAP data tunnel with interface id: 0xd670c00000002a for AP: c025.5c68.7f10 Error Reason: Capwap Data Tunnel create retry exceeded max retry count.
Nov 29 23:41:09.584: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination
Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination
Nov 29 23:42:55.496: *%LWAPP-3-RD_ERR7: 1 wcm: Invalid country code () for AP c0:25:5c:68:7f:10
Nov 29 23:42:55.496: *%LWAPP-3-RD_ERR9: 1 wcm: APs c0:25:5c:68:7f:10 country code changed from () to (GB )
Nov 29 23:42:55.496: *%LWAPP-3-RD_ERR7: 1 wcm: Invalid country code () for AP c0:25:5c:68:7f:10
Nov 29 23:42:55.496: *%LWAPP-3-RD_ERR9: 1 wcm: APs c0:25:5c:68:7f:10 country code changed from () to (GB )
Nov 29 23:42:55.496: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP c0:25:5c:68:7f:10
54C1BR01A01254(config)#
Nov 29 23:42:55.499: %CAPWAP-3-AP_PORT_CFG: AP connected port Gi1/0/24 is not an access port.
Nov 29 23:42:55.499: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP c0:25:5c:68:7f:10
Nov 29 23:42:55.500: *%CAPWAP-3-DATA_TUNNEL_CREATE_ERR2: 1 wcm: Failed to create CAPWAP data tunnel with interface id: 0xcb73c00000002b for AP: c025.5c68.7f10 Error Reason: Capwap Data Tunnel create retry exceeded max retry count.
GB - United Kingdom : 802.11a Indoor,Outdoor/ 802.11b / 802.11g
Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination
Nov 29 23:42:55.496: *%LWAPP-3-RD_ERR7: 1 wcm: Invalid country code () for AP c0:25:5c:68:7f:10
Nov 29 23:42:55.496: *%LWAPP-3-RD_ERR9: 1 wcm: APs c0:25:5c:68:7f:10 country code changed from () to (GB )
Nov 29 23:42:55.496: *%LWAPP-3-RD_ERR7: 1 wcm: Invalid country code () for AP c0:25:5c:68:7f:10
Nov 29 23:42:55.496: *%LWAPP-3-RD_ERR9: 1 wcm: APs c0:25:5c:68:7f:10 country code changed from () to (GB )
Nov 29 23:42:55.496: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP c0:25:5c:68:7f:10
Nov 29 23:42:55.499: %CAPWAP-3-AP_PORT_CFG: AP connected port Gi1/0/24 is not an access port.
Nov 29 23:42:55.499: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP c0:25:5c:68:7f:10
Nov 29 23:42:55.500: *%CAPWAP-3-DATA_TUNNEL_CREATE_ERR2: 1 wcm: Failed to create CAPWAP data tunnel with interface id: 0xcb73c00000002b for AP: c025.5c68.7f10 Error Reason: Capwap Data Tunnel create retry exceeded max retry count.
and sometimes:
Nov 30 21:16:56.781: *%CAPWAP-3-ALREADY_IN_JOIN: 1 wcm: Dropping join request from AP c025.5c68.7f10 - AP is already in joined state
Nov 30 21:16:56.785: *%CAPWAP-3-DATA_TUNNEL_DELETE_ERR2: 1 wcm: Failed to delete CAPWAP data tunnel with interface id: 0x0 from internal database. Reason: AVL database entry not found
Sh Wirless Country Configured:
GB - United Kingdom : 802.11a Indoor,Outdoor/ 802.11b / 802.11g
Sh version (AP):
LWAPP image version 10.1.100.0
1 Gigabit Ethernet interface
2 802.11 Radios
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: C0:67:AF:A7:1E:E4
Part Number : 73-14588-02
PCA Assembly Number : 800-37899-01
PCA Revision Number : A0
PCB Serial Number : FOC17353HXS
Top Assembly Part Number : 800-38356-01
Top Assembly Serial Number : FCZ1743P1VC
Top Revision Number : A0
Product/Model Number : AIR-SAP2602I-E-K9
Configuration register is 0xF
APc067.afa7.1ee4#
APc067.afa7.1ee4#^C
Not in Bound state.
*Nov 30 20:04:56.019: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
*Nov 30 20:05:01.019: %CAPWAP-3-ERRORLOG: Invalid event 40 & state 2 combination.c
*Nov 30 20:05:01.139: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.129.0.211, mask 255.255.255.128, hostname APc067.afa7.1ee4
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Nov 30 20:05:07.019: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
Sh ver (Switch):
Base Ethernet MAC Address : d0:c7:89:75:c3:00
Motherboard Assembly Number : 73-12238-06
Motherboard Serial Number : FOC172896LQ
Model Revision Number : B0
Motherboard Revision Number : D0
Model Number : WS-C3850-24T
System Serial Number : FOC1729V133
Switch Ports Model SW Version SW Image Mode
* 1 32 WS-C3850-24T 03.03.00SE cat3k_caa-universalk9 INSTALL
2 32 WS-C3850-24T 03.03.00SE cat3k_caa-universalk9 INSTALL
Switch 02
Switch uptime : 5 days, 23 hours, 2 minutes
Base Ethernet MAC Address : ec:e1:a9:df:93:80
Motherboard Assembly Number : 73-12238-06
Motherboard Serial Number : FOC17236GD1
Model Revision Number : B0
Motherboard Revision Number : D0
Model Number : WS-C3850-24T
System Serial Number : FOC1725V0FT
Configuration register is 0x102Hi,
3850 is in MC mode.
The AP is connected to an access switch which is connected via trunk port to 3850. the access port is in a same vlan as wireless management VLAN.AP is not connected directly to 3850 as this switch is not poe capable.
Country code is set to GB as th AP is ion Europe domain.
NTP has been configured
1- show license right-to-use summary :
ipservices permanent N/A Lifetime
apcount base 0 Lifetime
apcount adder 4 Lifetime
License Level In Use: ipservices
License Level on Reboot: ipservices
Evaluation AP-Count: Disabled
Total AP Count Licenses: 4
AP Count Licenses In-use: 1
AP Count Licenses Remaining: 3
the one which is in use is my AP which has issue. keeps rebooting:
2. show wireless mobility summary
Mobility Controller Summary:
Mobility Role : Mobility Controller
Mobility Protocol Port : 16666
Mobility Group Name : BSTAR
Mobility Oracle IP Address : 0.0.0.0
DTLS Mode : Enabled
Mobility Domain ID for 802.11r : 0x276d
Mobility Keepalive Interval : 10
Mobility Keepalive Count : 3
Mobility Control Message DSCP Value : 48
Mobility Domain Member Count : 1
Link Status is Control Link Status : Data Link Status
Controllers configured in the Mobility Domain:
IP Public IP Group Name Multicast IP Link Status
10.129.0.254 - BSTAR 0.0.0.0 UP : UP
3- Show run | in Wireless
qos wireless-default-untrust
wireless mobility controller
wireless mobility group name BSTAR
wireless management interface Vlan10
wireless wps ap-authentication -
New LWAPP 1702i not joining new CT2504 WLC
Have three new products on Test Bench:
CT2504 WLC w/ver 8.0.100.0
1702i LWAPP w/ver 15.3(3) JA
SG300-28MP Switch w/ver 1.3.7.18 (DHCP configured on switch with Option 43.)
(no DNS server available)
All three devices can ping each other but thats as far as it gets. The AP continuously loops w/DTLS error. I can issue CAPWAP
commands from the CLI telling AP IP of WLC and assigning the AP it's own IP but AP just continually loops without joining.
Console output of AP boot sequence attached.Thanks Rasiki, I opened a case today. Going over the compatibility documents I also noticed that the 1702i LWAPP software I am running, 15.3(3)JA, may need to be upgraded to the current 15.3(3)JAB.
All the configuration / reference material for the 1702i on the Cisco Support Site is in reference to "Autonomous" mode. I cannot find any written information for "Lightweight" mode. Is the procedure for upgrading the firmware on the LWAPP the same, i.e. TFTP, TAR files, etc.??? How does the AP know I want to upgrade in lightweight mode? -
I search how can i work two Controller on redundancy, i find high_availability article on site but this article says you should upgrade software at least 7.3 (my controller is 7.2). The thing that i wonder is can not we use redundancy feature on release before 7.3 ? if it was, which feature can i use for redundacy structure ?
And also i want to know; when i read high_availability article i saw one controller is being back-up controller and holding on standby. i understand that this controller not work unless active controller is crash. in other words the controllers do not load balancing. i maybe wrong about this so i'm so glad if you lighting me. Thanks already for all replies...Hi Olgu,
If you want make redudncy with 7.2 then follow this procedure:
Configure primary and second controller on each access points.
Below lists the Access Point join order:
* The AP will associate first with its primary controller, assuming it has been primed.
* Upon failing with the primary, it will try to register with its secondary and then its tertiary.
* If there is no controller information primed in the AP, the AP will then look for a master controller.
* Finally, if there is no primed controller and no master controller, the AP will select the least loaded from all controllers that have responded to the discovery.
http://www.cisco.com/en/US/docs/wireless/controller/7.2/configuration/guide/cg_lwap.html#wpmkr1426782
Hope it helps.
Reagrds
Please rate helpful posts. -
AIR-LAP521G-E-K9 is not joining WLC4402-12
Hi,
Please I need some help with any guide or info regarding my LAP521 access points that are refusing to join the WLC4402-12.
This is my first lightweight access point implementation and I have 3 LAP521's and 1 AIR-CAP3502I-E-K9 access points on my network.
They are meant to pick up ip address from external dhcp server and then join the WLC but only the 3502i joins successfuly while the 521's get dhcp address but do not join the WLC. From the logs, I can see that the WLC is discovered by the 521's and even get a response message from the controller but they are still unable to join as shown in the screenshot below.
My WLC is running software version 7.0.230.0 and the 521's are running an lwapp image version 4.2.61.8.
Base Radio MAC
AP Name
Status
Ethernet MAC
IP Address
Last Join Time
00:23:04:cc:56:d0
NA
Not Joined
00:00:00:00:00:00
172.31.5.115
00:23:04:f2:8d:10
NA
Not Joined
00:00:00:00:00:00
172.31.5.113
00:23:33:22:3d:b0
NA
Not Joined
00:00:00:00:00:00
172.31.5.110
3c:ce:73:94:b4:d0
AP001
Joined
44:2b:03:6d:5d:50
172.31.5.120
Oct 01 18:01:17.713
Please any suggestions or help with resolving this issue will be appreciated.
ThanksThe reason the 521 will not join, is because they require the Cisco Express WLC. They will not join the 4400 WLC. Take a look at this matrix with the code you are running and the AP's that are supported.
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html#wp81600
Sent from Cisco Technical Support iPhone App -
AP(2720e) not joining a WLC (2504)
I recently purchased two 2702e AP's to expand the wireless coverage of our network but when I plug them in, they will not join the AP for some reason.
This is what I am getting on the controller;
(Cisco Controller) >show ap join stats detailed f44e0544e944
Discovery phase statistics
- Discovery requests received.............................. 51
- Successful discovery responses sent...................... 26
- Unsuccessful discovery request processing................ 0
- Reason for last unsuccessful discovery attempt........... Not applicable
- Time at last successful discovery attempt................ Dec 08 10:24:37.695
- Time at last unsuccessful discovery attempt.............. Not applicable
Join phase statistics
- Join requests received................................... 0
- Successful join responses sent........................... 0
- Unsuccessful join request processing..................... 0
- Reason for last unsuccessful join attempt................ Not applicable
- Time at last successful join attempt..................... Not applicable
- Time at last unsuccessful join attempt................... Not applicable
Configuration phase statistics
- Configuration requests received.......................... 0
- Successful configuration responses sent.................. 0
- Unsuccessful configuration request processing............ 0
- Reason for last unsuccessful configuration attempt....... Not applicable
--More-- or (q)uit
- Time at last successful configuration attempt............ Not applicable
- Time at last unsuccessful configuration attempt.......... Not applicable
Last AP message decryption failure details
- Reason for last message decryption failure............... Not applicable
Last AP disconnect details
- Reason for last AP connection failure.................... Not applicable
- Last AP disconnect reason................................ Not applicable
Last join error summary
- Type of error that occurred last......................... None
- Reason for error that occurred last...................... Not applicable
- Time at which the last join error occurred............... Not applicable
AP disconnect details
- Reason for last AP connection failure.................... Not applicable
I have tried it with just the default settings and by setting the IP on the AP to no avail.
Any suggestion would be much appreciated.
EricHi Eric,
What software code is running on your 2504 ? I hope it is 7.6.130.0
If it is 8.0.100.0, then there was a crtical bug given below, you need to check whether you hitting this
https://tools.cisco.com/bugsearch/bug/CSCur43050
Conditions:
Seen only with APs that were manufactured in August, September or October, 2014 - all Aironet APs were affected EXCEPT the 700 series. Seen with WLCs running 8.0.100.0 or an 8.0.100.x special.
If the WLC was manufactured in September 2014, or later (i.e. has a SHA2 MIC), then the first symptom is seen, i.e. the AP joins the 8.0.100 WLC, downloads the image, but then fails to rejoin.
If the WLC was manufactured before September 2014 (i.e. does not have a SHA2 MIC), then the second symptom is seen, i.e. the AP can join the 8.0.100 WLC OK, but then will fail download during a subsequent upgrade.
Also seen with new APs trying to join a controller running IOS-XE 3.6.0 (15.3(3)JN k9w8 image.) (Track CSCur50946 for the IOS-XE fix)
Workaround:
Downgrade to AireOS 7.6.130.0, or to IOS-XE 3.3, if the APs are supported in the earlier code
Pls attach AP console output while trying to boot & register to see the exact reason for failure.
HTH
Rasika
**** Pls rate all useful responses **** -
Cisco 3502 AP will not join 4402
Have 5 WLC 4402's in my network. I upgraded one of them to 7.0.98.0 to test the new 3502 APs. When I go to join the new 3502 it will not join to the upgraded WLC. Keep in mind all WLC's are in the same mobility group. Does it matter that the rest of the controllers are not on 7.0 code?
thanks
izzyAP3500 requires a minimum of 7.0.98.0. So my question is: When you console into the AP and reboot the AP (all in that order), can you please post everything?
-
LAP1142 can not join wlc 2100 !
I'd WLC 2100 series and 9 access point LAP1142N .
8 LAP1142N can work fine and join a capwap controller is ok but only one LAP1142 is can not .
Could you help me to solve it ? Part of LAP is AIR-LAP1142N-A-K9
Apr 2 10:52:42.284: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway found
*Apr 2 10:52:42.284: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway found
*Apr 2 10:52:42.284: LWAPP_CLIENT_EVENT: Dropping discovery in LWAPP. This AP model is not supported by LWAPP WLC.
*Apr 2 10:52:42.284: status of voice_diag_test from WLC is false
*Apr 2 10:52:52.284: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Apr 2 10:52:52.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.28.21 peer_port: 5246
*Apr 2 10:52:52.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Apr 2 10:52:52.667: LWAPP_CLIENT_EVENT: lwapp_check_image_good: image is good now
*Apr 2 10:52:53.107: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.28.21 peer_port: 5246
*Apr 2 10:52:53.108: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.28.21
*Apr 2 10:52:53.108: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Apr 2 10:52:53.198: LWAPP_CLIENT_EVENT: ap model AIR-LAP1142N-A-K9
*Apr 2 10:52:53.198: LWAPP_CLIENT_EVENT: ap sw version 12.4(23c)JA
*Apr 2 10:52:53.198: LWAPP_CLIENT_EVENT: lwapp_encode_ap_reset_button_payload: reset button state on
*Apr 2 10:52:53.237: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Apr 2 10:52:53.240: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.28.21
*Apr 2 10:52:53.240: %DTLS-5-PEER_DISCONNECT: Peer 172.16.28.21 has closed connection.
*Apr 2 10:52:53.241: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.16.28.21:5246
*Apr 2 10:52:53.279: LWAPP_CLIENT_EVENT: bsnDeleteAllMobiles radio 0
*Apr 2 10:52:53.279: LWAPP_CLIENT_EVENT: bsnLockDevice radio 0
*Apr 2 10:52:53.279: LWAPP_CLIENT_EVENT: bsnDeleteAllMobiles radio 1
*Apr 2 10:52:53.279: LWAPP_CLIENT_EVENT: bsnLockDevice radio 1
*Apr 2 10:52:53.280: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Apr 2 10:52:53.280: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Apr 2 10:52:53.286: LWAPP_CLIENT_EVENT: spamInitCfgData: Loaded configuration into v2 struct (version 7.0.98.0)Actually, 5.2 or later is needed.
5.0 and 5.1 do not even support 1140 Access point.
Rating useful replies is more useful than saying "Thank you" -
Does the WLC 5500 Series support LLDP?
We have 2 WLC 5508s running v7.0.98.0 and 70+ 1230, 1240, & 1250 series LWAPs. We are currently enabling LLDP because we will be installing some non-Cisco switches in the near future. Does the WLC5508 and the access points it controlls support LLDP?
Hi David:
The Data Sheet for the 5500 series wireless LAN controllers is at
http://tools.cisco.com/squish/b7D77
That data sheet does not currently list LLDP (as LLDP) or IEEE 802.11AB as supported protocols in the product as it sits today.
I would encourage you to contact your Cisco SE, Cisco account team or Cisco authorized wireless reseller, and let them know you think that this support would be valuable to the wireless LAN controllers. The "sales side of the house" has procedures in place to gather and accumulate input from the customers they serve, and forward it to the respective business units within Cisco for possible inclusion in future releases of Cisco's products.
Sincerely,
Rollin Kibbe
Network Management Systems Team
Maybe you are looking for
-
How do I back up and restore my ipod touch if when i connect it to itunes It does not appear in the devices column? I have a white screen and have tried holding down the wake/sleep and home buttons and that is not working. Please help
-
How to stop the prodution order creating when the product is not valued?
Hi guyes: How to stop the prodution order creating when the product is not valued using CO01? I hope that when i create the production order,the system will check the product is valued or not,if not the system will show an error or warning message! H
-
Truncate table loses privs on table...
Oracle11g/RHEL5 Hi, We have a table that is inserted into a then deleted every so often. The current method that was being used to remove the rows was the TRUNCATE TABLE ption. However, we found out that when that statement is issued, that any user t
-
TS3992 i cannot have a backup on itunes. it says cannot backup due to an error occured
When i connect my iphone to itunes, it says cannot backup due to an error occured.. This started happening all of a sudden.. Please find me a solution for this.. I really need a backup of the phone in my laptop. Thanks
-
Why does the BlackBoard HTML editor freeze and crash Firefox 3.6?
Black Board uses a HTML editor that seems to be based on JAVA. I teach by added posts to threads and can use the editor or disable the editor in either case after adding some text the window freezes and I cannot add text or delete text. If I enable t