09-15-2018 03:58 PM - edited 07-05-2021 09:11 AM
Does anyone know if the 1815T Officeextend AP is compatible with vWlC 8.5.103.0? according to the documentation I have seen it should be but I am seeing the AP pull an IP address and partially join before continuously repeating the process over and over again.
From the debugs I have done i see this error message "Unsupported Platform, Config Request Rejected AP Name - Office"
According to Cisco this should be supported?
8.5.135.0 |
15.3(3)JF8 |
Lightweight APs: 1600, 1700, 1800i, 1810 OEAP, 1810W, 1815i, 1815m, 1815t, 1815w, 1830, 1850, 2600, 2700, 2800, 3500e, 3500i, 3500p, 3600e, 3600i, 3600p, 3702e, 3702i, 3702p, 3800, 700, 700W, AP802, AP803, Integrated Access Point on Cisco 1100 ISR, ASA5506W-AP702 Outdoor and Industrial APs: 1532E, 1532I, 1540, 1552E, 1552H, 1552I, 1552C, 1552EU, 1552CU, 1552S, 1560, 1570, and IW3700 Note The Cisco Aironet 1550 Series APs with 64-MB memory are not supported. Modules: AIR-RM3010L-x-K9 and AIR-RM3000M |
8.5.131.0 |
15.3(3)JF7 |
|
8.5.120.0 |
15.3(3)JF5 |
|
8.5.110.0 |
15.3(3)JF4 |
|
8.5.105.0 |
15.3(3)JF1 |
|
8.5.103.0 |
15.3(3)JF |
I have enabled the DTLS license as I thought this may be causing the problem but that loooks not to be the case.
(Cisco Controller) >show license sum
Feature name: ap_count
License type: Evaluation
License Eula: Accepted
Evaluation total period: 12 weeks 6 days
License state: Inactive, Not-In-Use
RTU License Count: 200
Feature name: ap_count (adder)
License type: Permanent
License state: Active, In-use
RTU License Count: 5
Feature name: data_encryption
License type: Permanent
License state: Active, In-use
License Count: Non-Counted
Any help would be much appreciated.
Thanks,
Shaun
Solved! Go to Solution.
10-04-2018 06:31 AM
Hi All,
Quick update. I raised a TAC who advised that the 1815T is not compatible with any virtual WLC
Thanks,
Shaun
09-15-2018 04:27 PM
I would suggest you to upgrade vWLC to 8.5.135.0 & test.
HTH
Rasika
09-15-2018 07:39 PM
@shaun barrs wrote:
Does anyone know if the 1815T Officeextend AP is compatible with vWlC 8.5.103.0?
Shaun,
It is compatible but one's gotta be brave to use this particular version. It's not stable.
Rasika's recommendation of using 8.5.135.0 is the best way forward.
09-16-2018 05:34 AM
Thanks both. I will upgrade to 8.5.135.0 and let you know how I get on.
Thanks,
Shaun
09-17-2018 01:57 PM
I have upgraded the vWLC to 8.5.135.0. The 1815T updated it's firmware ok but is still in the same state where it seems to register briefly and then drops off again with the same error message again "Unsupported Platform, Config Request Rejected AP Name - APBC26.C744.1F08"
Below is a debug from the controller showing the output of a debug capwap event, error and mac addr. Hope this helps to shed some light?
*spamApTask1: Sep 17 20:38:04.808: 00:ea:bd:57:52:c0 Discovery Request from 82.132.*.*:17609
*spamApTask1: Sep 17 20:38:04.808: 00:ea:bd:57:52:c0 ApModel: AIR-AP1815T-E-K9
*spamApTask1: Sep 17 20:38:04.808: 00:ea:bd:57:52:c0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 200, MaxLicense=200 joined Aps =0
*spamApTask1: Sep 17 20:38:04.808: 00:ea:bd:57:52:c0 apType = 65 apModel: AIR-AP1815T-E-K9
*spamApTask1: Sep 17 20:38:04.808: 00:ea:bd:57:52:c0 apType: Ox41 bundleApImageVer: 8.5.135.0
*spamApTask1: Sep 17 20:38:04.808: 00:ea:bd:57:52:c0 version:8 release:5 maint:135 build:0
*spamApTask1: Sep 17 20:38:04.808: 00:ea:bd:57:52:c0 Discovery Response sent to 82.132.*.* port 17609
*spamApTask1: Sep 17 20:38:04.808: 00:ea:bd:57:52:c0 Discovery Response sent to 82.132.*.*:17609
*spamApTask1: Sep 17 20:38:04.938: 00:ea:bd:57:52:c0 Discovery Request from 82.132.*.*:17609
*spamApTask1: Sep 17 20:38:04.938: 00:ea:bd:57:52:c0 ApModel: AIR-AP1815T-E-K9
*spamApTask1: Sep 17 20:38:04.938: 00:ea:bd:57:52:c0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 200, MaxLicense=200 joined Aps =0
*spamApTask1: Sep 17 20:38:04.938: 00:ea:bd:57:52:c0 apType = 65 apModel: AIR-AP1815T-E-K9
*spamApTask1: Sep 17 20:38:04.938: 00:ea:bd:57:52:c0 apType: Ox41 bundleApImageVer: 8.5.135.0
*spamApTask1: Sep 17 20:38:04.938: 00:ea:bd:57:52:c0 version:8 release:5 maint:135 build:0
*spamApTask1: Sep 17 20:38:04.938: 00:ea:bd:57:52:c0 Discovery Response sent to 82.132.*.* port 17609
(Cisco Controller) >*spamApTask1: Sep 17 20:38:04.938: 00:ea:bd:57:52:c0 Discovery Response sent to 82.132.*.*:17609
*spamApTask1: Sep 17 20:38:19.209: 00:ea:bd:57:52:c0 Join Request from 82.132.*.*:17609
*spamApTask1: Sep 17 20:38:19.209: 00:ea:bd:57:52:c0 Unable to get Ap mode in Join request
*spamApTask1: Sep 17 20:38:19.209: 00:ea:bd:57:52:c0 Allocate database entry for AP 82.132.*.*:17609, already allocated index 65535
*spamApTask1: Sep 17 20:38:19.209: 00:ea:bd:57:52:c0 AP Allocate request at index ffff
*spamApTask1: Sep 17 20:38:19.211: 00:ea:bd:57:52:c0 Join Version: = 134579968
*spamApTask1: Sep 17 20:38:19.211: 00:ea:bd:57:52:c0 apType = 65 apModel: AIR-AP1815T-E-K9
*spamApTask1: Sep 17 20:38:19.211: 00:ea:bd:57:52:c0 apType: Ox41 bundleApImageVer: 8.5.135.0
*spamApTask1: Sep 17 20:38:19.211: 00:ea:bd:57:52:c0 version:8 release:5 maint:135 build:0
*spamApTask1: Sep 17 20:38:19.211: 00:ea:bd:57:52:c0 Join resp: CAPWAP Maximum Msg element len = 82
*spamApTask1: Sep 17 20:38:19.211: 00:ea:bd:57:52:c0 Join Response sent to 82.132.*.*:17609
*spamApTask1: Sep 17 20:38:19.211: 00:ea:bd:57:52:c0 CAPWAP State: Join
*spamApTask1: Sep 17 20:38:19.211: 00:ea:bd:57:52:c0 capwap_ac_platform.c:2076 - Operation State 0 ===> 4
*spamApTask1: Sep 17 20:38:19.211: 00:ea:bd:57:52:c0 Capwap State Change Event (Reg) from capwap_ac_platform.c 2117
*apfReceiveTask: Sep 17 20:38:19.211: 00:ea:bd:57:52:c0 Register LWAPP event for AP 00:ea:bd:57:52:c0 slot 0
*spamApTask1: Sep 17 20:38:19.211: 00:ea:bd:57:52:c0 Capwap State Change Event (Reg) from capwap_ac_platform.c 2117
*spamApTask1: Sep 17 20:38:19.212: 00:ea:bd:57:52:c0 Capwap State Change Event (Reg) from capwap_ac_platform.c 2117
*apfReceiveTask: Sep 17 20:38:19.212: WARP IEs: (12)
*apfReceiveTask: Sep 17 20:38:19.212: [0000] dd 0a 00 c0 b9 01 00 00 00 08 01 01
*apfReceiveTask: Sep 17 20:38:19.212: 00:ea:bd:57:52:c0 Register LWAPP event for AP 00:ea:bd:57:52:c0 slot 1
*apfReceiveTask: Sep 17 20:38:19.212: WARP IEs: (12)
*apfReceiveTask: Sep 17 20:38:19.212: [0000] dd 0a 00 c0 b9 01 00 00 00 08 01 01
*apfReceiveTask: Sep 17 20:38:19.212: 00:ea:bd:57:52:c0 Register LWAPP event for AP 00:ea:bd:57:52:c0 slot 2
*spamApTask1: Sep 17 20:38:19.539: 00:ea:bd:57:52:c0 Configuration Status from 82.132.*.*:17609
*spamApTask1: Sep 17 20:38:19.539: 00:ea:bd:57:52:c0 CAPWAP State: Configure
*spamApTask1: Sep 17 20:38:19.539: 00:ea:bd:57:52:c0 Updating IP info for AP 00:ea:bd:57:52:c0 -- static 0, 192.168.137.46/255.255.255.0, gtw 192.168.137.1
*spamApTask1: Sep 17 20:38:19.539: 00:ea:bd:57:52:c0 Updating IP 82.132.231.101 ===> 82.132.*.* for AP 00:ea:bd:57:52:c0
*spamApTask1: Sep 17 20:38:19.539: 00:ea:bd:57:52:c0 Updated IP Domain info for AP 00:ea:bd:57:52:c0 -- set 0, Domain
*spamApTask1: Sep 17 20:38:19.539: 00:ea:bd:57:52:c0 Updating IP NamServer info for AP 00:ea:bd:57:52:c0 -- set 1, nameserver 8.8.8.8
*spamApTask1: Sep 17 20:38:19.539: 00:ea:bd:57:52:c0 00:ea:bd:57:52:c0 AP Country changed from:(UX) to (GB ).
*spamApTask1: Sep 17 20:38:19.539: 00:ea:bd:57:52:c0 00:ea:bd:57:52:c0 AP Country changed from:(UX) to (GB ).
*spamApTask1: Sep 17 20:38:19.540: 00:ea:bd:57:52:c0 Unsupported Platform, Config Request Rejected
AP Name - APBC26.C744.1F08
*spamApTask1: Sep 17 20:38:19.540: 00:ea:bd:57:52:c0 Failed post decode processing of config status from 82.132.*.*:17609
*spamApTask1: Sep 17 20:38:19.540: 00:ea:bd:57:52:c0 State machine handler: Failed to process msg type = 5 state = 5 from 82.132.*.*:17609
Thanks,
Shaun
09-17-2018 08:55 PM
10-04-2018 06:31 AM
Hi All,
Quick update. I raised a TAC who advised that the 1815T is not compatible with any virtual WLC
Thanks,
Shaun
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