Dear Everyone ,
We are having issue to join the cisco 2702i AP to our new 9800 WLC . After collecting the debug IP and debug mac address from the 9800 , we found out the 9800 was the one drop the dtls connection with below reason :
2024/06/24 12:38:28.941891425 {wncmgrd_R0-0}{1}: [capwapac-srvr] [19272]: (info): Dropping DTLS pkt, not a client-hello message
2024/06/24 12:38:28.941895695 {wncmgrd_R0-0}{1}: [ewlc-capwapmsg-sess] [19272]: (ERR): Source IP:10.255.94.48[16975], DTLS message process failed. length:19
2024/06/24 12:38:28.941904003 {wncmgrd_R0-0}{1}: [capwapac-srvr] [19272]: (ERR): Message dispatching failed. Source IP: 10.255.94.48[16975]
2024/06/24 12:38:28.941918988 {wncmgrd_R0-0}{1}: [tdl_plat_main] [19272]: (debug): PLAT: containment enabled: 0, leak tracking: 0, not checking leaks
2024/06/24 12:38:28.941986264 {wncmgrd_R0-0}{1}: [tdl_plat_main] [19272]: (debug): PLAT: containment enabled: 0, leak tracking: 0, not checking leaks
2024/06/24 12:38:37.966531239 {wncmgrd_R0-0}{1}: [ewlc-infra-capwap-dgram] [19272]: (debug): dgram handle, index is 0, udplite 0
2024/06/24 12:38:37.966544401 {wncmgrd_R0-0}{1}: [capwapac-srvr] [19272]: (debug): IP:10.255.94.48[16975], Now processing Capwap UDP message, length:182
2024/06/24 12:38:37.966552323 {wncmgrd_R0-0}{1}: [capwapac-srvr] [19272]: (debug): Cluster: process_cleartxt_msg called
2024/06/24 12:38:37.966610266 {wncmgrd_R0-0}{1}: [ewlc-capwapmsg-parse] [19272]: (debug): Message type:discovery_request, message length:158 bytes:(1264)
2024/06/24 12:38:37.966617832 {wncmgrd_R0-0}{1}: [ewlc-capwapmsg-parse] [19272]: (debug): Parse discovery_type message element, length:1
2024/06/24 12:38:37.966621306 {wncmgrd_R0-0}{1}: [ewlc-capwapmsg-parse] [19272]: (debug): Parse wtp_board_data message element, length:62
2024/06/24 12:38:37.966631271 {wncmgrd_R0-0}{1}: [ewlc-capwapmsg-parse] [19272]: (debug): Parse wtp_descriptor message element, length:40
2024/06/24 12:38:37.966639286 {wncmgrd_R0-0}{1}: [ewlc-capwapmsg-parse] [19272]: (debug): Parse wtp_frame_tunnel_mode message element, length:1
2024/06/24 12:38:37.966642313 {wncmgrd_R0-0}{1}: [ewlc-capwapmsg-parse] [19272]: (debug): Parse wtp_mac_type message element, length:1
2024/06/24 12:38:37.966760149 {wncmgrd_R0-0}{1}: [ewlc-capwapmsg-parse] [19272]: (debug): Parse board_data_opt vendor payload data length 32
2024/06/24 12:38:37.966764472 {wncmgrd_R0-0}{1}: [ewlc-capwapmsg-parse] [19272]: (debug): Parse rad_name vendor payload data length 72
2024/06/24 12:38:37.966772015 {wncmgrd_R0-0}{1}: [capwapac-discovery] [19272]: (note): MAC: fc5b.39d4.24e0 IP:10.255.94.48[16975], Discovery Request received
2024/06/24 12:38:37.966810938 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): Add Cursor: table tbl_ap_discovery_info/b1c61bbdc1be1ad6d0b9571ed0396b85 not in the list /tmp/rp/tdldb/0/WNCMGRD_DB
2024/06/24 12:38:37.966832370 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): ReplDB explicit record enq: Successfully enqueued record update for table with identifier: table tbl_ap_discovery_info/b1c61bbdc1be1ad6d0b9571ed0396b85/0and luid: b1c61bbdc1be1ad6d0b9571ed0396b85
2024/06/24 12:38:37.966837773 {wncmgrd_R0-0}{1}: [capwapac-discovery] [19272]: (debug): Mac: fc5b.39d4.24e0 DISCOVERY: antena type: 1 remote type: 0 wtp_type: 0 incoming join priority: 1
2024/06/24 12:38:37.966840998 {wncmgrd_R0-0}{1}: [capwapac-discovery] [19272]: (note): MAC: fc5b.39d4.24e0 EWLC TAGS payload is not present in discovery request
2024/06/24 12:38:37.966841177 {wncmgrd_R0-0}{1}: [capwapac-discovery] [19272]: (debug): Board data option VPld is not present in discovery request
2024/06/24 12:38:37.966844044 {wncmgrd_R0-0}{1}: [capwapac-discovery] [19272]: (debug): Mac: fc5b.39d4.24e0 DISCOVERY: version 0
2024/06/24 12:38:37.966844218 {wncmgrd_R0-0}{1}: [capwapac-discovery] [19272]: (ERR): MAC: fc5b.39d4.24e0 Radio Information is not present
2024/06/24 12:38:37.967144733 {wncmgrd_R0-0}{1}: [capwapac-srvr] [19272]: (debug): AP image version: 17.9.4.27
2024/06/24 12:38:37.967156196 {wncmgrd_R0-0}{1}: [capwapac-discovery] [19272]: (debug): Reading from discovery req Version:7 Release:6 Maint:100 Build:0 and overall version=117859328
2024/06/24 12:38:37.967156366 {wncmgrd_R0-0}{1}: [capwapac-discovery] [19272]: (debug): Reading from file Version:17 Release:9 Maint:4 Build:27 and overall version=285803547
2024/06/24 12:38:37.967167578 {wncmgrd_R0-0}{1}: [capwapac-discovery] [19272]: (debug): IP:10.255.94.48[16975], Succesfully processing discovery request : & Max concurrent download limit is ok.Downloads in progress=1 &Maximum concurrent downloads=150
2024/06/24 12:38:37.967171169 {wncmgrd_R0-0}{1}: [capwapac-discovery] [19272]: (debug): Mac: fc5b.39d4.24e0 IP:10.255.94.48[16975], Join priority processing status:1, Priority:1, Max Lrads:6000, joined APs:126 , AP_JOIN_PRIORITY_DEFAULT : 1
2024/06/24 12:38:37.967171728 {wncmgrd_R0-0}{1}: [capwapac-discovery] [19272]: (debug): Mac: fc5b.39d4.24e0 In AP disc processing, ap throttle: 0 joined APs: 126
2024/06/24 12:38:37.967179981 {wncmgrd_R0-0}{1}: [capwapac-discovery] [19272]: (debug): Mac: fc5b.39d4.24e0 Successfully got ethernet mac, ethernet mac: MAC: fc5b.39d4.24e0
2024/06/24 12:38:37.967188912 {wncmgrd_R0-0}{1}: [ewlc-infra-evq] [19272]: (debug): instance :0 port:11589MAC: 4b39.0001.000b
2024/06/24 12:38:37.967191360 {wncmgrd_R0-0}{1}: [loadbalance-notify] [19272]: (debug): IPv4: 10.255.94.48 AP message (Discovery) received in loadbalancer-server mode
2024/06/24 12:38:37.967260330 {wncmgrd_R0-0}{1}: [loadbalance-notify] [19272]: (debug): MAC: fc5b.39d4.24e0 ,Couldn't find AP entry in MAC table
2024/06/24 12:38:37.967264085 {wncmgrd_R0-0}{1}: [loadbalance-notify] [19272]: (note): Key IPv4 address: 10.255.94.48 :16975, Coundn't find AP entry in IP:port address table,
2024/06/24 12:38:37.967265498 {wncmgrd_R0-0}{1}: [loadbalance-notify] [19272]: (debug): IPv4: 10.255.94.48 Handle remote entity, AP not found in database
2024/06/24 12:38:37.967267555 {wncmgrd_R0-0}{1}: [loadbalance-algo] [19272]: (debug): Site based Loadbalance algorithm called
2024/06/24 12:38:37.967273266 {wncmgrd_R0-0}{1}: [loadbalance-algo] [19272]: (debug): Incoming TAG details before passing to resolver. Site tag :, RF tag : , Policy tag : .
2024/06/24 12:38:37.967302374 {wncmgrd_R0-0}{1}: [ewlc-resolver] [19272]: (debug): No static tag map entry found for ap:chrhew032
2024/06/24 12:38:37.967314207 {wncmgrd_R0-0}{1}: [ewlc-resolver] [19272]: (debug): resolver got site tag:, policy tag: rf tag: for AP:chrhew032
2024/06/24 12:38:37.967320213 {wncmgrd_R0-0}{1}: [ewlc-filter] [19272]: (debug): failed to resolve filter from ap_info,no matching filter for ap:chrhew032
2024/06/24 12:38:37.967320833 {wncmgrd_R0-0}{1}: [ewlc-resolver] [19272]: (debug): resolver got site tag:, policy tag: rf tag: for AP:chrhew032
2024/06/24 12:38:37.967340530 {wncmgrd_R0-0}{1}: [ewlc-resolver] [19272]: (debug): AP: chrhew032 resolved tags default-policy-tag default-site-tag default-rf-tag, tag source:default
2024/06/24 12:38:37.967341083 {wncmgrd_R0-0}{1}: [ewlc-resolver] [19272]: (debug): resolver got site tag:default-site-tag, policy tag:default-policy-tag rf tag:default-rf-tag for AP:chrhew032
2024/06/24 12:38:37.967467006 {wncmgrd_R0-0}{1}: [loadbalance-algo] [19272]: (ERR): ap spec config record not found
2024/06/24 12:38:37.967471941 {wncmgrd_R0-0}{1}: [loadbalance-notify] [19272]: (note): IPv4:10.255.94.48 Found AP tag default-site-tag, AP tag mapped to instance: = 3
2024/06/24 12:38:37.967472836 {wncmgrd_R0-0}{1}: [loadbalance-algo] [19272]: (note): Algo counter incremented, inst:3(joined rb:1, joined site:24), max site ap: 0
2024/06/24 12:38:37.967479762 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): Add Cursor: table ewlc_loadbalancer_algo_stats_tbl/34c5e7e40422fa82304e9ef42bf61447 not in the list /tmp/rp/tdldb/0/WNCMGRD_DB
2024/06/24 12:38:37.967488036 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): ReplDB explicit record enq: Successfully enqueued record update for table with identifier: table ewlc_loadbalancer_algo_stats_tbl/34c5e7e40422fa82304e9ef42bf61447/0and luid: 34c5e7e40422fa82304e9ef42bf61447
2024/06/24 12:38:37.967490461 {wncmgrd_R0-0}{1}: [loadbalance-notify] [19272]: (note): IPv4:10.255.94.48 WNCD instance:3, selected by loadbalance algo
2024/06/24 12:38:37.967520503 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl handle to oid: Calling tdl oid mapping create. Pointer is 0x8c80498830 OID attribute passed in is 1
2024/06/24 12:38:37.967534489 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl oid mapping create: Inserted mapping into ptr->id mapping table for OID with ptr: 4000000000498830, and attribute 1
2024/06/24 12:38:37.967544418 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl oid mapping create: Generated a new OID with: id 0000000000000000000000000000704d and source: d6af62cebb9211eeb91e0050568fe071 for the object at 0x4000008c80498830
2024/06/24 12:38:37.967560193 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl oid mapping create: Inserted mapping into id->ptr mapping table for OID with ptr: 4000000000498830, id: 0000000000000000000000000000704d and source: d6af62cebb9211eeb91e0050568fe071 and attribute 1
2024/06/24 12:38:37.967568625 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl handle to oid: Obtained omap entry with OID ptr: 4000000000498830 ID: 0000000000000000000000000000704d attribute 1 in ref:0 and SRC: d6af62cebb9211eeb91e0050568fe071. Handle passed in was at: 0x8c80498830
2024/06/24 12:38:37.967568877 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl handle to oid: Incrementing ref count of omap entry at 0x8c80498980
2024/06/24 12:38:37.967569624 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl update oid ref count: Existing oid in ref count is 0
2024/06/24 12:38:37.967570191 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl update oid ref count: Incremented oid ref count.New ref count is: 1
2024/06/24 12:38:37.967573329 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl handle to oid: Calling tdl oid mapping create. Pointer is 0x8c80498750 OID attribute passed in is 1
2024/06/24 12:38:37.967576993 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl oid mapping create: Inserted mapping into ptr->id mapping table for OID with ptr: 4000000000498750, and attribute 1
2024/06/24 12:38:37.967583717 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl oid mapping create: Generated a new OID with: id 0000000000000000000000000000704e and source: d6af62cebb9211eeb91e0050568fe071 for the object at 0x4000008c80498750
2024/06/24 12:38:37.967591728 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl oid mapping create: Inserted mapping into id->ptr mapping table for OID with ptr: 4000000000498750, id: 0000000000000000000000000000704e and source: d6af62cebb9211eeb91e0050568fe071 and attribute 1
2024/06/24 12:38:37.967598352 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl handle to oid: Obtained omap entry with OID ptr: 4000000000498750 ID: 0000000000000000000000000000704e attribute 1 in ref:0 and SRC: d6af62cebb9211eeb91e0050568fe071. Handle passed in was at: 0x8c80498750
2024/06/24 12:38:37.967598561 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl handle to oid: Incrementing ref count of omap entry at 0x8c80498a00
2024/06/24 12:38:37.967598752 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl update oid ref count: Existing oid in ref count is 0
2024/06/24 12:38:37.967599249 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl update oid ref count: Incremented oid ref count.New ref count is: 1
2024/06/24 12:38:37.967606344 {wncmgrd_R0-0}{1}: [loadbalance-notify] [19272]: (debug): MAC: fc5b.39d4.24e0 Pending timer started
2024/06/24 12:38:37.967617614 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): Add Cursor: table ewlc_loadbalancer_mac_tbl/f957690ce6243b33def87bf4c596d5c7 not in the list /tmp/rp/tdldb/0/WNCMGRD_DB
2024/06/24 12:38:37.967631471 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): ReplDB explicit record enq: Successfully enqueued record update for table with identifier: table ewlc_loadbalancer_mac_tbl/f957690ce6243b33def87bf4c596d5c7/0and luid: f957690ce6243b33def87bf4c596d5c7
2024/06/24 12:38:37.967631791 {wncmgrd_R0-0}{1}: [loadbalance-notify] [19272]: (note): MAC: fc5b.39d4.24e0 Inserted macdb successfully
2024/06/24 12:38:37.967633901 {wncmgrd_R0-0}{1}: [loadbalance-algo] [19272]: (debug): MAC: fc5b.39d4.24e0 update discv time sec= 1719225517, msec= 967632
2024/06/24 12:38:37.967636485 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): ReplDB internal write cursor move: Record is present and already at the tail of temporal list for tablewith identifier: table ewlc_loadbalancer_mac_tbl/f957690ce6243b33def87bf4c596d5c7/0 and luid: f957690ce6243b33def87bf4c596d5c7
2024/06/24 12:38:37.967637447 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): ReplDB explicit record enq: Successfully enqueued record update for table with identifier: table ewlc_loadbalancer_mac_tbl/f957690ce6243b33def87bf4c596d5c7/0and luid: f957690ce6243b33def87bf4c596d5c7
2024/06/24 12:38:37.967637674 {wncmgrd_R0-0}{1}: [loadbalance-algo] [19272]: (debug): Loadbalancer algo context updated successfully
2024/06/24 12:38:37.967642942 {wncmgrd_R0-0}{1}: [loadbalance-notify] [19272]: (note): Address Key IPv4 address: 10.255.94.48 :16975 entry not present hence adding
2024/06/24 12:38:37.967660952 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl handle to oid: Calling tdl oid mapping create. Pointer is 0x8c80498830 OID attribute passed in is 1
2024/06/24 12:38:37.967663669 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl oid mapping create: ptr id entry already exists for OID with ptr: 4000000000498830, and attribute 1
2024/06/24 12:38:37.967670693 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl handle to oid: Obtained omap entry with OID ptr: 4000000000498830 ID: 0000000000000000000000000000704d attribute 1 in ref:1 and SRC: d6af62cebb9211eeb91e0050568fe071. Handle passed in was at: 0x8c80498830
2024/06/24 12:38:37.967670893 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl handle to oid: Incrementing ref count of omap entry at 0x8c80498980
2024/06/24 12:38:37.967671440 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl update oid ref count: Incremented oid ref count.New ref count is: 2
2024/06/24 12:38:37.967680060 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl handle to oid: Calling tdl oid mapping create. Pointer is 0x8c80498b00 OID attribute passed in is 1
2024/06/24 12:38:37.967681626 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl oid mapping create: Inserted mapping into ptr->id mapping table for OID with ptr: 4000000000498b00, and attribute 1
2024/06/24 12:38:37.967689565 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl oid mapping create: Generated a new OID with: id 0000000000000000000000000000704f and source: d6af62cebb9211eeb91e0050568fe071 for the object at 0x4000008c80498b00
2024/06/24 12:38:37.967698358 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl oid mapping create: Inserted mapping into id->ptr mapping table for OID with ptr: 4000000000498b00, id: 0000000000000000000000000000704f and source: d6af62cebb9211eeb91e0050568fe071 and attribute 1
2024/06/24 12:38:37.967704986 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl handle to oid: Obtained omap entry with OID ptr: 4000000000498b00 ID: 0000000000000000000000000000704f attribute 1 in ref:0 and SRC: d6af62cebb9211eeb91e0050568fe071. Handle passed in was at: 0x8c80498b00
2024/06/24 12:38:37.967705291 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl handle to oid: Incrementing ref count of omap entry at 0x8c80498c38
2024/06/24 12:38:37.967705533 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl update oid ref count: Existing oid in ref count is 0
2024/06/24 12:38:37.967706032 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): tdl update oid ref count: Incremented oid ref count.New ref count is: 1
2024/06/24 12:38:37.967712843 {wncmgrd_R0-0}{1}: [loadbalance-notify] [19272]: (note): Key IPv4 address: 10.255.94.48 :16975 Inserted to addr 1 successfully
2024/06/24 12:38:37.967719294 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): Add Cursor: table ewlc_loadbalancer_stats_tbl/39a4b25f477511813e309de297c04ebc not in the list /tmp/rp/tdldb/0/WNCMGRD_DB
2024/06/24 12:38:37.967724942 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): ReplDB explicit record enq: Successfully enqueued record update for table with identifier: table ewlc_loadbalancer_stats_tbl/39a4b25f477511813e309de297c04ebc/0and luid: 39a4b25f477511813e309de297c04ebc
2024/06/24 12:38:37.967726517 {wncmgrd_R0-0}{1}: [loadbalance-notify] [19272]: (debug): Inst id: 3, Discovery counter Incremented, discv count: 25, join count: 24
2024/06/24 12:38:37.967728439 {wncmgrd_R0-0}{1}: [loadbalance-notify] [19272]: (debug): MAC: fc5b.39d4.24e0 update tag default-site-tag of len = 16
2024/06/24 12:38:37.967737234 {wncmgrd_R0-0}{1}: [loadbalance-algo] [19272]: (debug): Loadbalancer MACDB searching record while updating algo ctx
2024/06/24 12:38:37.967739817 {wncmgrd_R0-0}{1}: [loadbalance-algo] [19272]: (debug): MAC: fc5b.39d4.24e0 update discv time sec= 1719225517, msec= 967738
2024/06/24 12:38:37.967741496 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): ReplDB internal write cursor move: Record is present and already at the tail of temporal list for tablewith identifier: table ewlc_loadbalancer_mac_tbl/f957690ce6243b33def87bf4c596d5c7/0 and luid: f957690ce6243b33def87bf4c596d5c7
2024/06/24 12:38:37.967742084 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): ReplDB explicit record enq: Successfully enqueued record update for table with identifier: table ewlc_loadbalancer_mac_tbl/f957690ce6243b33def87bf4c596d5c7/0and luid: f957690ce6243b33def87bf4c596d5c7
2024/06/24 12:38:37.967742267 {wncmgrd_R0-0}{1}: [loadbalance-algo] [19272]: (debug): Loadbalancer algo context updated successfully
2024/06/24 12:38:37.967764387 {wncmgrd_R0-0}{1}: [capwapac-discovery] [19272]: (note): MAC: fc5b.39d4.24e0 Public IP learnt is TRUE, public IP discovery is TRUE, private IP discovery is TRUE.
2024/06/24 12:38:37.967786704 {wncmgrd_R0-0}{1}: [ewlc-infra-capwap-dgram] [19272]: (debug): dgram handle, index is 0, udplite 0
2024/06/24 12:38:37.967838485 {wncmgrd_R0-0}{1}: [capwapac-srvr] [19272]: (debug): AP image version: 17.9.4.27
2024/06/24 12:38:37.967890773 {wncmgrd_R0-0}{1}: [ewlc-capwapmsg-gen] [19272]: (debug): generate mwar_type vendor_payload
2024/06/24 12:38:37.967893215 {wncmgrd_R0-0}{1}: [ewlc-capwapmsg-gen] [19272]: (debug): generate ap_timesync vendor_payload
2024/06/24 12:38:37.967895107 {wncmgrd_R0-0}{1}: [capwapac-discovery] [19272]: (debug): Mac: fc5b.39d4.24e0 Message type: discovery response, Payload length: 1292 Data Length:0
2024/06/24 12:38:37.967900144 {wncmgrd_R0-0}{1}: [ewlc-infra-capwap-dgram] [19272]: (debug): dgram handle, index is 0, udplite 0
2024/06/24 12:38:37.967979782 {wncmgrd_R0-0}{1}: [capwapac-discovery] [19272]: (note): MAC: fc5b.39d4.24e0 IP:10.255.94.48[16975], Discovery Response sent
2024/06/24 12:38:37.967983271 {wncmgrd_R0-0}{1}: [ap-join-info-db] [19272]: (debug): MAC: fc5b.39d4.24e0 Updated Discovery resp sent to 1114
2024/06/24 12:38:37.967992174 {wncmgrd_R0-0}{1}: [ewlc-infra-capwap-dgram] [19272]: (debug): dgram handle, index is 0, udplite 0
2024/06/24 12:38:37.968011025 {wncmgrd_R0-0}{1}: [capwapac-srvr] [19272]: (debug): AP image version: 17.9.4.27
2024/06/24 12:38:37.968029863 {wncmgrd_R0-0}{1}: [ewlc-capwapmsg-gen] [19272]: (debug): generate mwar_type vendor_payload
2024/06/24 12:38:37.968030363 {wncmgrd_R0-0}{1}: [ewlc-capwapmsg-gen] [19272]: (debug): generate ap_timesync vendor_payload
2024/06/24 12:38:37.968031095 {wncmgrd_R0-0}{1}: [capwapac-discovery] [19272]: (debug): Mac: fc5b.39d4.24e0 Message type: discovery response, Payload length: 1292 Data Length:0
2024/06/24 12:38:37.968034467 {wncmgrd_R0-0}{1}: [ewlc-infra-capwap-dgram] [19272]: (debug): dgram handle, index is 0, udplite 0
2024/06/24 12:38:37.968070839 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): Add Cursor: table tbl_capwap_discovery_pkt_info/3ea5fb80351a5f95537d36c355e029d3 not in the list /tmp/rp/tdldb/0/WNCMGRD_DB
2024/06/24 12:38:37.968077581 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): ReplDB explicit record enq: Successfully enqueued record update for table with identifier: table tbl_capwap_discovery_pkt_info/3ea5fb80351a5f95537d36c355e029d3/0and luid: 3ea5fb80351a5f95537d36c355e029d3
2024/06/24 12:38:37.968085329 {wncmgrd_R0-0}{1}: [ewlc-capwapmsg-sess] [19272]: (debug): Source IP:10.255.94.48[16975], clear text message processed. length:182
2024/06/24 12:38:37.968098171 {wncmgrd_R0-0}{1}: [tdl_plat_main] [19272]: (debug): PLAT: containment enabled: 0, leak tracking: 0, not checking leaks
2024/06/24 12:38:37.968143513 {wncmgrd_R0-0}{1}: [tdl_plat_main] [19272]: (debug): PLAT: containment enabled: 0, leak tracking: 0, not checking leaks
2024/06/24 12:40:57.965418602 {wncmgrd_R0-0}{1}: [ewlc-infra-capwap-dgram] [19272]: (debug): dgram handle, index is 0, udplite 0
2024/06/24 12:40:57.965430334 {wncmgrd_R0-0}{1}: [ewlc-utility] [19272]: (debug): DTLS packet parse, size: 69
2024/06/24 12:40:57.965432401 {wncmgrd_R0-0}{1}: [ewlc-utility] [19272]: (debug): No extensions present in DTLS Client-Hello
2024/06/24 12:40:57.965445381 {wncmgrd_R0-0}{1}: [loadbalance-notify] [19272]: (debug): IPv4: 10.255.94.48 AP message (DTLS Hello) received in loadbalancer-server mode
2024/06/24 12:40:57.965489616 {wncmgrd_R0-0}{1}: [loadbalance-notify] [19272]: (note): Key IPv4 address: 10.255.94.48 :16975, Coundn't find AP entry in IP:port address table,
2024/06/24 12:40:57.965491297 {wncmgrd_R0-0}{1}: [loadbalance-notify] [19272]: (debug): IPv4: 10.255.94.48 Handle remote entity, AP not found in database
2024/06/24 12:40:57.965495599 {wncmgrd_R0-0}{1}: [loadbalance-notify] [19272]: (note): IPv4:10.255.94.48 Handle remote entity, dropped DTLS message, since no entry in loadblancer DB for the AP
2024/06/24 12:40:57.965522558 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): Add Cursor: table ewlc_loadbalancer_stats_tbl/39a4b25f477511813e309de297c04ebc not in the list /tmp/rp/tdldb/0/WNCMGRD_DB
2024/06/24 12:40:57.965543748 {wncmgrd_R0-0}{1}: [tdllib] [19272]: (debug): ReplDB explicit record enq: Successfully enqueued record update for table with identifier: table ewlc_loadbalancer_stats_tbl/39a4b25f477511813e309de297c04ebc/0and luid: 39a4b25f477511813e309de297c04ebc
2024/06/24 12:40:57.965545693 {wncmgrd_R0-0}{1}: [loadbalance-notify] [19272]: (debug): DTLS drop counter Incremented, dtls drop cnt: 29002
I am suspecting it is due to software bug , but just that i couldnt find a 100% matched BUG ID . Appreciate if you could share us the finding why the AP is not able to register with 9800.
WLC model : C9800-CL-K9
Running firmware on WLC : 17.09.04a
