11-04-2015 05:09 AM - edited 07-05-2021 04:10 AM
Hi Guys,
i am having issues with registering the AP 1602 controller based to the catalyst 3850 controller , below errro is what i am seeing in the consol
aedub1-sw-core-1(config-if-range)#
*Nov 4 11:56:13.323: %ILPOWER-7-DETECT: Interface Gi1/0/37: Power Device detected: IEEE PD
*Nov 4 11:56:13.326: %ILPOWER-7-DETECT: Interface Gi1/0/38: Power Device detected: IEEE PD
*Nov 4 11:56:13.327: %ILPOWER-7-DETECT: Interface Gi1/0/39: Power Device detected: IEEE PD
*Nov 4 11:56:13.727: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/38: Power granted
*Nov 4 11:56:13.727: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/39: Power granted
*Nov 4 11:56:14.612: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/37, changed state to down
*Nov 4 11:56:14.626: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/38, changed state to down
*Nov 4 11:56:14.637: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/39, changed state to down
*Nov 4 11:56:14.738: %ILPOWER-5-POWER_GRANTED: Interface Gi1/0/37: Power granted
*Nov 4 11:56:18.367: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/38, changed state to up
*Nov 4 11:56:18.518: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/39, changed state to up
*Nov 4 11:56:18.526: %LINK-3-UPDOWN: Interface Vlan20, changed state to up
*Nov 4 11:56:18.667: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/37, changed state to up
*Nov 4 11:56:19.368: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/38, changed state to up
*Nov 4 11:56:19.522: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/39, changed state to up
*Nov 4 11:56:19.527: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan20, changed state to up
*Nov 4 11:56:19.666: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/37, changed state to up
*Nov 4 11:57:50.446: *spamApTask0: 1 wcm: %DTLS-3-PKI_ERROR: PKI initialization error : Certificate initialization failed
*Nov 4 11:57:52.445: *spamApTask0: 1 wcm: %DTLS-3-PKI_ERROR: PKI initialization error : Certificate initialization failed
*Nov 4 11:57:53.622: *spamApTask1: 1 wcm: %DTLS-3-PKI_ERROR: PKI initialization error : Certificate initialization failed
*Nov 4 11:57:55.622: *spamApTask1: 1 wcm: %DTLS-3-PKI_ERROR: PKI initialization error : Certificate initialization failed
*Nov 4 11:57:56.807: *spamApTask0: 1 wcm: %DTLS-3-PKI_ERROR: PKI initialization error : Certificate initialization failed [...It occurred 2 times/sec!.]
*Nov 4 11:57:58.807: *spamApTask0: 1 wcm: %DTLS-3-PKI_ERROR: PKI initialization error : Certificate initialization failed
*Nov 4 11:58:02.807: *spamApTask0: 1 wcm: %DTLS-3-PKI_ERROR: PKI initialization error : Certificate initialization failed [...It occurred 2 times/sec!.]
*Nov 4 11:58:04.446: *spamApTask0: 1 wcm: %DTLS-3-PKI_ERROR: PKI initialization error : Certificate initialization failed
*Nov 4 11:58:07.622: *spamApTask1: 1 wcm: %DTLS-3-PKI_ERROR: PKI initialization error : Certificate initialization failed
*Nov 4 11:58:10.807: *spamApTask0: 1 wcm: %DTLS-3-PKI_ERROR: PKI initialization error : Certificate initialization failed
Below is how the config is on the switch
aedub1-sw-core-1#sh license right-to-use
*Nov 4 12:05:14.537: *spamApTask1: 1 wcm: %DTLS-3-PKI_ERROR: PKI initialization error : Certificate initialization failed
Slot# License name Type Count Period left
----------------------------------------------------------
1 ipbase permanent N/A Lifetime
1 apcount evaluation 50 69
1 apcount adder 39 Lifetime
License Level on Reboot: ipbase
Slot# License name Type Count Period left
----------------------------------------------------------
2 ipbase permanent N/A Lifetime
License Level on Reboot: ipbase
aedub1-sw-core-1#sh ap auth-list
Authorize MIC APs against AAA : Enabled
Authorize LSC APs against Auth-List : Enabled
APs Allowed to Join:
AP with Manufacturing Installed Certificate : Enabled
AP with Self-Signed Certificate : Enabled
AP with Locally Significant Certificate : Disabled
aedub1-sw-core-1#sh ap join stats summary
Number of APs : 3
Base MAC Ethernet MAC AP Name IP Address Status
---------------------------------------------------------------------------------
b0aa.77fa.7120 0000.0000.0000 APb0aa.77fa.7120 10.28.6.206 Not Joined
b0aa.77fa.7186 0000.0000.0000 APb0aa.77fa.7186 10.28.6.205 Not Joined
b0aa.77fa.71ba 0000.0000.0000 APb0aa.77fa.71ba 10.28.6.202 Not Joined
Switch Config
interface GigabitEthernet1/0/36
switchport access vlan 10
switchport mode access
switchport voice vlan 15
spanning-tree portfast
!
interface GigabitEthernet1/0/37
switchport access vlan 20
switchport mode access
spanning-tree portfast
!
interface GigabitEthernet1/0/38
switchport access vlan 20
switchport mode access
spanning-tree portfast
!
interface GigabitEthernet1/0/39
switchport access vlan 20
switchport mode access
spanning-tree portfast
interface Vlan20
description WiFi Mgmt Vlan
ip address 10.28.6.201 255.255.255.248
ip helper-address 10.28.6.201
wsma agent exec
profile httplistener
profile httpslistener
wsma agent config
profile httplistener
profile httpslistener
wsma agent filesys
profile httplistener
profile httpslistener
wsma agent notify
profile httplistener
profile httpslistener
!
wsma profile listener httplistener
transport http
!
wsma profile listener httpslistener
transport https
wireless mobility controller
wireless management interface Vlan20
wireless mgmt-via-wireless
wlan aedub1-wifi 1 WLAN
client vlan 10
no security wpa akm dot1x
security wpa akm psk set-key ascii 0 pa55w0rd
no shutdown
ap auth-list ap-policy authorize-ap
ap auth-list ap-policy authorize-lsc-ap
ap auth-list ap-policy ssc
ap dot11 24ghz rrm channel dca 1
ap dot11 24ghz rrm channel dca 6
ap dot11 24ghz rrm channel dca 11
ap dot11 5ghz rrm channel dca 36
ap dot11 5ghz rrm channel dca 40
ap dot11 5ghz rrm channel dca 44
ap dot11 5ghz rrm channel dca 48
ap dot11 5ghz rrm channel dca 52
ap dot11 5ghz rrm channel dca 56
ap dot11 5ghz rrm channel dca 60
ap dot11 5ghz rrm channel dca 64
ap dot11 5ghz rrm channel dca 149
ap dot11 5ghz rrm channel dca 153
ap dot11 5ghz rrm channel dca 157
ap dot11 5ghz rrm channel dca 161
ap group default-group
end
Please advise a solution to fix the issue
Many Thanks
Adarsh
11-05-2015 09:27 AM
Looking at the Cisco Error meessage decoder, that could be realted to the LSC authorization you have enabled.
I would disable LSC:
no ap auth-list ap-policy authorize-lsc-ap
reboot and see if the AP joins.
HTH,
Steve
11-07-2015 05:08 AM
Hi Stephen,
tried that but still no joy ... actually the initiall config were without that and i added thinking it might help , now its local cert auth is been taken out ... any other thoughts why the AP's not joining ... below is whats been showing on AP's ...
*Nov 7 12:50:54.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.28.6.201 peer_port: 5246
*Nov 7 12:51:23.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0x3EA52C8!
*Nov 7 12:51:53.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.28.6.201:5246
Not in Bound state.
*Nov 7 12:51:59.499: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*Nov 7 12:52:04.619: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.28.6.206, mask 255.255.255.248, hostname APb0aa.77fa.70e2
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (10.28.6.201)
*Nov 7 12:52:20.567: AP has SHA2 MIC certificate - Using SHA1 MIC certificate for DTLS.
*Nov 7 12:52:21.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.28.6.201 peer_port: 5246
*Nov 7 12:52:50.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0x3EA52C8!
*Nov 7 12:53:20.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.28.6.201:5246
*Nov 7 12:53:21.067: AP has SHA2 MIC certificate - Using SHA1 MIC certificate for DTLS.
*Nov 7 12:53:21.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.28.6.201 peer_port: 5246
*Nov 7 12:53:50.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0x3EA52C8!
*Nov 7 12:54:20.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.28.6.201:5246
*Nov 7 12:54:41.067: AP has SHA2 MIC certificate - Using SHA1 MIC certificate for DTLS.
*Nov 7 12:54:41.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.28.6.201 peer_port: 5246
*Nov 7 12:55:10.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0x3EA52C8!
*Nov 7 12:55:40.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.28.6.201:5246
*Nov 7 12:55:41.067: AP has SHA2 MIC certificate - Using SHA1 MIC certificate for DTLS.
*Nov 7 12:55:41.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.28.6.201 peer_port: 5246
*Nov 7 12:56:10.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0x3EA52C8!
*Nov 7 12:56:40.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.28.6.201:5246
Not in Bound state.
*Nov 7 12:56:56.499: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*Nov 7 12:57:01.619: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.28.6.205, mask 255.255.255.248, hostname APb0aa.77fa.70e2
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (10.28.6.201)
*Nov 7 12:57:27.566: AP has SHA2 MIC certificate - Using SHA1 MIC certificate for DTLS.
*Nov 7 12:57:28.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.28.6.201 peer_port: 5246
*Nov 7 12:57:57.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0x3EA52C8!
*Nov 7 12:58:27.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.28.6.201:5246
*Nov 7 12:58:28.067: AP has SHA2 MIC certificate - Using SHA1 MIC certificate for DTLS.
*Nov 7 12:58:28.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.28.6.201 peer_port: 5246
*Nov 7 12:58:57.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0x3EA52C8!
*Nov 7 12:59:27.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.28.6.201:5246
*Nov 7 12:59:48.067: AP has SHA2 MIC certificate - Using SHA1 MIC certificate for DTLS.
*Nov 7 12:59:48.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.28.6.201 peer_port: 5246
*Nov 7 13:00:17.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0x3EA52C8!
*Nov 7 13:00:47.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.28.6.201:5246
*Nov 7 13:00:48.067: AP has SHA2 MIC certificate - Using SHA1 MIC certificate for DTLS.
*Nov 7 13:00:48.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.28.6.201 peer_port: 5246
*Nov 7 13:01:17.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0x3EA52C8!
*Nov 7 13:01:47.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.28.6.201:5246
Not in Bound state.
*Nov 7 13:01:53.499: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*Nov 7 13:01:58.619: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.28.6.204, mask 255.255.255.248, hostname APb0aa.77fa.70e2
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (10.28.6.201)
*Nov 7 13:02:14.567: AP has SHA2 MIC certificate - Using SHA1 MIC certificate for DTLS.
*Nov 7 13:02:15.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.28.6.201 peer_port: 5246
*Nov 7 13:02:44.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0x3EA52C8!
*Nov 7 13:03:14.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.28.6.201:5246
*Nov 7 13:03:15.067: AP has SHA2 MIC certificate - Using SHA1 MIC certificate for DTLS.
*Nov 7 13:03:15.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.28.6.201 peer_port: 5246
*Nov 7 13:03:44.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0x3EA52C8!
*Nov 7 13:04:14.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.28.6.201:5246
*Nov 7 13:04:35.067: AP has SHA2 MIC certificate - Using SHA1 MIC certificate for DTLS.
*Nov 7 13:04:35.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.28.6.201 peer_port: 5246
*Nov 7 13:05:04.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0x3EA52C8!
*Nov 7 13:05:34.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.28.6.201:5246
*Nov 7 13:05:35.067: AP has SHA2 MIC certificate - Using SHA1 MIC certificate for DTLS.
*Nov 7 13:05:35.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.28.6.201 peer_port: 5246
*Nov 7 13:06:04.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0x3EA52C8!
*Nov 7 13:06:34.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.28.6.201:5246
Not in Bound state.
*Nov 7 13:06:50.499: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*Nov 7 13:06:55.619: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.28.6.203, mask 255.255.255.248, hostname APb0aa.77fa.70e2
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (10.28.6.201)
*Nov 7 13:07:21.566: AP has SHA2 MIC certificate - Using SHA1 MIC certificate for DTLS.
*Nov 7 13:07:21.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.28.6.201 peer_port: 5246
*Nov 7 13:07:50.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0x3EA52C8!
*Nov 7 13:08:20.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.28.6.201:5246
*Nov 7 13:08:21.067: AP has SHA2 MIC certificate - Using SHA1 MIC certificate for DTLS.
*Nov 7 13:08:21.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.28.6.201 peer_port: 5246
*Nov 7 13:08:50.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0x3EA52C8!
11-08-2015 01:14 AM
Pls post "show version" output from both AP & 3850
Rasika
11-08-2015 02:21 AM
Hi, please see below
3850
aedub1-sw-core-1#sh ver
Cisco IOS Software, IOS-XE Software, Catalyst L3 Switch Software (CAT3K_CAA-UNIVERSALK9-M), Version 03.02.03.SE RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Mon 23-Sep-13 18:24 by prod_rel_team
Cisco IOS-XE software, Copyright (c) 2005-2013 by cisco Systems, Inc.
All rights reserved. Certain components of Cisco IOS-XE software are
licensed under the GNU General Public License ("GPL") Version 2.0. The
software code licensed under GPL Version 2.0 is free software that comes
with ABSOLUTELY NO WARRANTY. You can redistribute and/or modify such
GPL code under the terms of GPL Version 2.0.
(http://www.gnu.org/licenses/gpl-2.0.html) For more details, see the
documentation or "License Notice" file accompanying the IOS-XE software,
or the applicable URL provided on the flyer accompanying the IOS-XE
software.
ROM: IOS-XE ROMMON
BOOTLDR: MD0002R01.0112182013
aedub1-sw-core-1 uptime is 1 day, 21 hours, 56 minutes
Uptime for this control processor is 1 day, 22 hours, 0 minutes
System returned to ROM by reload
System image file is "flash:packages.conf"
Last reload reason: Reload command
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
export@cisco.com.
License Level: Ipbase
License Type: Permanent
Next reload license Level: Ipbase
cisco WS-C3850-48F (MIPS) processor with 4194304K bytes of physical memory.
6 Virtual Ethernet interfaces
104 Gigabit Ethernet interfaces
8 Ten Gigabit Ethernet interfaces
2048K bytes of non-volatile configuration memory.
4194304K bytes of physical memory.
257008K bytes of Crash Files at crashinfo:.
257008K bytes of Crash Files at crashinfo-2:.
1550272K bytes of Flash at flash:.
1550272K bytes of Flash at flash-2:.
0K bytes of Dummy USB Flash at usbflash0:.
0K bytes of Dummy USB Flash at usbflash0-2:.
0K bytes of at webui:.
Base Ethernet MAC Address : dc:eb:94:2e:b8:00
Motherboard Assembly Number : 73-15800-07
Model Revision Number : T0
Motherboard Revision Number : A0
Model Number : WS-C3850-48F
Switch Ports Model SW Version SW Image Mode
------ ----- ----- ---------- ---------- ----
1 56 WS-C3850-48F 03.02.03.SE cat3k_caa-universalk9 INSTALL
2 56 WS-C3850-48F 03.02.03.SE cat3k_caa-universalk9 INSTALL
Switch 02
---------
Switch uptime : 1 day, 22 hours, 0 minutes
Base Ethernet MAC Address : f0:b2:e5:ac:12:80
Motherboard Assembly Number : 73-15800
Model Revision Number : T0
Motherboard Revision Number : A0
Model Number : WS-C3850-48F
Configuration register is 0x102
AP 1602
Cisco IOS Software, C1600 Software (AP1G2-RCVK9W8-M), Version 15.3(3)JA3, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Thu 19-Feb-15 09:33 by prod_rel_team
Initializing flashfs...
FLASH CHIP: Micronix MX25L256_35F
flashfs[2]: 11 files, 2 directories
flashfs[2]: 0 orphaned files, 0 orphaned directories
flashfs[2]: Total bytes: 31808000
flashfs[2]: Bytes used: 5918208
flashfs[2]: Bytes available: 25889792
flashfs[2]: flashfs fsck took 10 seconds.
flashfs[2]: Initialization complete.
flashfs[3]: 0 files, 1 directories
flashfs[3]: 0 orphaned files, 0 orphaned directories
flashfs[3]: Total bytes: 11999232
flashfs[3]: Bytes used: 1024
flashfs[3]: Bytes available: 11998208
flashfs[3]: flashfs fsck took 0 seconds.
flashfs[3]: Initialization complete....done Initializing flashfs.
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
export@cisco.com.
cisco AIR-CAP1602E-E-K9 (PowerPC) processor (revision B0) with 187382K/74672K bytes of memory.
PowerPC CPU at 533Mhz, revision number 0x2151
Last reset from power-on
LWAPP image version 8.0.115.0
1 Gigabit Ethernet interface
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: B0:AA:77:FA:70:E2
Part Number : 73-14508-04
PCA Assembly Number : 000-00000-00
PCA Revision Number :
Top Assembly Part Number : 800-38553-03
Top Revision Number : A0
Product/Model Number : AIR-CAP1602E-E-K9
11-08-2015 11:26 AM
I would do the following
1. Upgrade 3850 IOS-XE 3.6.3E code (though current software version supports 1600 series, code is too old and my have some defects)
2. Check your 3850 configured for correct country code for wireless and Time is sync properly. See below post
http://mrncciew.com/2013/09/29/getting-started-with-3850/
3850-1(config)#ap country X
3850-1#show wireless country configured
HTH
Rasika
*** Pls rate all useful responses ***
11-09-2015 08:07 PM
Hi Manannalage,
i had chnaged the country from US to AE now , and is showing as chnaged in the config , but still have the same error .. as you said to upgrade the IOS-XE too which i havent done yet , but do that really help , cuz for changing i need to have rfc approved so just trying to see if without changing the IOS-XE will the issue be fixed !
Many Thanks
Adarsh
11-09-2015 08:22 PM
Yes, I would suggest you to upgrade your switch image. I am running 3.6.3E in my production and I can recommend that from stablity point of view.
HTH
Rasika
11-09-2015 08:26 PM
ok , sure will do the upgrade , just asking cuz of curiosity ... is that a reason for the AP's not registering to the 3850
11-09-2015 08:40 PM
I am not sure at this stage, but first get this done, so we know there is no suspcet on 3850 image.
HTH
Rasika
11-11-2015 08:44 AM
HI Manannalage,
i upgraded the IOS on the switch successfully and all working well , but the AP's still have joined the controller and i am getting the same error as before ... any other solution you could think of ...
05-18-2016 08:52 PM
Hello aadhu1, could you solve this error ?
02-19-2017 12:09 PM
Hi!
Somebody resolve this? I Have the same issue, please help. Need solution.
02-19-2017 05:36 PM
Hi Maxim,
It is better if you could open a new thread for your issue. Attach the following output onto that thread.
From your 3850
1. show version
2. show wireless country configured
3. show clock
From your AP
1. show version
2. complet onsole log while AP trying to register to WLC
HTH
Rasika
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