11-26-2014 08:16 AM - edited 07-05-2021 02:01 AM
I am trying to get setup with my WLC 5508 and I have run into the next set of challenge...
Software version : 7.6.130.0
FRI: 7.6.101.1
My first AP out of the box started up and received an ip add and was listed under Wireless > ALL APS status "Downloading"
It received some IOS updates rebooted and now it never registers under the area above....
At first I thought it was option 43 in DHCP but than how did it work the first time...
Anyways to eliminate DHCP I assigned static ip add and static controller address as well
capwap ap controller ip address 10.31.99.21
capwap ap ip address 10.31.99.149 255.255.255.0
Still no joy !
Do I need to configure the controller with some settings before the AP can successfully register and start broadcasting my test SSID ?
I have posted below the error log the DHCP ip log and than the STATIC ip log...
Any help will be much appreciated.
cheers
===============================================================
%CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Nov 26 14:53:29.675: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Nov 26 14:53:30.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.31.99.21 peer_port: 5246
*Nov 26 14:53:30.467: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.31.99.21 peer_port: 5246
*Nov 26 14:53:30.467: %CAPWAP-5-SENDJOIN: sending Join Request to 10.31.99.21
*Nov 26 14:53:30.467: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Nov 26 14:53:30.467: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Nov 26 14:53:30.467: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Nov 26 14:53:30.467: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.31.99.21
., 1)26 14:53:48.579: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max (UNKNOWN_MESSAGE_TYPE (5)
*Nov 26 14:53:48.579: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE
*Nov 26 14:53:48.579: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.31.99.21:5246
*Nov 26 14:53:48.623: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Nov 26 14:53:48.643: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Nov 26 14:53:48.643: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Nov 26 14:53:48.647: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Nov 26 14:53:48.671: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Nov 26 14:53:49.647: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Nov 26 14:53:49.675: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Nov 26 14:53:49.683: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Nov 26 14:53:50.667: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Nov 26 14:53:50.675: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Nov 26 14:53:50.703: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Nov 26 14:53:50.711: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Nov 26 14:53:50.719: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Nov 26 14:53:51.703: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Nov 26 14:53:51.711: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Nov 26 14:53:51.747: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Nov 26 14:53:52.747: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Nov 26 14:53:58.667: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Nov 26 14:53:58.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.31.99.21 peer_port: 5246
*Nov 26 14:53:58.463: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.31.99.21 peer_port: 5246
*Nov 26 14:53:58.463: %CAPWAP-5-SENDJOIN: sending Join Request to 10.31.99.21
*Nov 26 14:53:58.467: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Nov 26 14:53:58.467: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Nov 26 14:53:58.467: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Nov 26 14:53:58.467: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.31.99.21
======================================================================================
*Nov 26 16:04:46.751: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Nov 26 16:04:52.675: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Nov 26 16:04:53.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.31.99.21 peer_port: 5246
*Nov 26 16:04:53.463: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.31.99.21 peer_port: 5246
*Nov 26 16:04:53.463: %CAPWAP-5-SENDJOIN: sending Join Request to 10.31.99.21
*Nov 26 16:04:53.467: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Nov 26 16:04:53.467: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Nov 26 16:04:53.467: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Nov 26 16:04:53.467: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.31.99.21
======================================================================================
Solved! Go to Solution.
11-26-2014 11:25 AM
Yes, that Option 43 hex value is correct.
Regarding switchport type, it has to be ACCESS mode.
I do not think that is the issue here, as AP send join request to that WLC & still fails. May be regulatory domain issue or time.
Pls provide these info
WLC : show sysinfo & show time output
AP : show version output
HTH
Rasika
11-27-2014 11:47 AM
Hi
Good to see you figured this issue quickly.
Regarding the other queries you have here is my feedback
2. So I have three different models of AP so will that setting not cause problems in DHCP?
Yes, DHCP option 43 does not cause any issues with different AP model. I believe you use a single DHCP pool for all different AP models without using any DHCP vendor class option (60). In that way every AP get the WLC information via DHCP & even AP in different L3 network, it will be able to find your WLC & register. DHCP Option 43 & DNS method are two most commonly configured option for WLC discovery.
3. Is there a generic option 43 setting ? As the initial digit points to the type of AP model correct
Yes, typically option 43 you can configure without option 60-vendor class identifier. See this video you will find out (was in the link you already found)
https://supportforums.cisco.com/video/11927936/dhcp-option-43-cisco-ios-dhcp-server
HTH
Rasika
**** Pls rate all useful responses ****
11-26-2014 09:11 AM
I read some text on-line which was conflicting but I tried it any ways and no joy.
Tried the AP switch port as Trunk - No joy ( it would not even get an ip add from DHCP )
Tried the AP switch port as Trunk + native vlan set to AP - No joy ( it would not even get an ip add from DHCP )
Set the port back to Access now it does get an ip address..
What should my hex settings be for this specific AP model I am a little confused reading this article :(
http://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/97066-dhcp-option-43-00.html
cheers
11-26-2014 09:42 AM
Would this be the correct value for WLC within DHCP for the above mentioned AP?
I need to deploy 1552i + 3602E in this project...
0xf1040A1F6315 ( with no "spaces" inserted into the ASCI section of Windows DHCP option 43)
10.31.99.21
The AP keeps flashing RED and green
cheers
11-26-2014 11:25 AM
Yes, that Option 43 hex value is correct.
Regarding switchport type, it has to be ACCESS mode.
I do not think that is the issue here, as AP send join request to that WLC & still fails. May be regulatory domain issue or time.
Pls provide these info
WLC : show sysinfo & show time output
AP : show version output
HTH
Rasika
11-27-2014 02:31 AM
Thank you for your response I had already left for the day hence the delayed response.
Here are my findings.
1. You are correct the country was not set correctly and I kept ignoring the irritating message box but it was advising me to disable the radios and I thought it had changed clearly not.
So I disabled the and re-enabled and now it is set to GB correctly
=====================================================================================================
(Cisco Controller) >show country co
Configured Country............................. US - United States
Configured Country Codes
US - United States............................. 802.11a Indoor,Outdoor / 802.11b / 802.11g
=====================================================================================================
(Cisco Controller) >config 802.11a disable network
Disabling the 802.11a network may strand mesh APs. Are you sure you want to continue? (y/n)y
(Cisco Controller) >config 802.11b disable network
=====================================================================================================
(Cisco Controller) >show country co
Configured Country............................. US - United States
Configured Country Codes
US - United States............................. 802.11a Indoor,Outdoor / 802.11b / 802.11g
(Cisco Controller) >config country GB
Changing country code could reset channel & RRM grouping configuration.
If running in RRM One-Time mode, reassign channels after this command.
Check customized APs for valid channel values after this command.
Are you sure you want to continue? (y/n) y
Configured Country............................. GB - United Kingdom
=====================================================================================================
(Cisco Controller) >config 802.11b enable network
(Cisco Controller) >config 802.11a enable network
========================================
(Cisco Controller) >show country code
Configured Country............................. GB - United Kingdom
Configured Country Codes
GB - United Kingdom............................ 802.11a Indoor,Outdoor / 802.11b / 802.11g
========================================
Now it the sysinfo is showing the correct configuration...
I than opened a new 3602E-E-K9 and started the process from scratch and it upgraded the IOS and rebooted and now it registers with the WLC correctly.
I also assigned a static ip address + renamed the host name to reflect the naming standard and it worked like a treat !!!
No more reboots...
2. So I have three different models of AP so will that setting not cause problems in DHCP?
3. Is there a generic option 43 setting ? As the initial digit points to the type of AP model correct ?
4. Timezone was all set correctly. Eventually it will point to a NTP server early next week.
Thank you for pushing me in the right direction.
cheers
11-27-2014 11:47 AM
Hi
Good to see you figured this issue quickly.
Regarding the other queries you have here is my feedback
2. So I have three different models of AP so will that setting not cause problems in DHCP?
Yes, DHCP option 43 does not cause any issues with different AP model. I believe you use a single DHCP pool for all different AP models without using any DHCP vendor class option (60). In that way every AP get the WLC information via DHCP & even AP in different L3 network, it will be able to find your WLC & register. DHCP Option 43 & DNS method are two most commonly configured option for WLC discovery.
3. Is there a generic option 43 setting ? As the initial digit points to the type of AP model correct
Yes, typically option 43 you can configure without option 60-vendor class identifier. See this video you will find out (was in the link you already found)
https://supportforums.cisco.com/video/11927936/dhcp-option-43-cisco-ios-dhcp-server
HTH
Rasika
**** Pls rate all useful responses ****
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide