Android not able to pull IPv6 address from AP

[billydailey]

I have a pretty complex IPV6 network setup with the 9800 and using 9136 APs.  All seems to be working well except for android phones.  They authenticate but are unable to pull an IPV6 address.  This happens for Pixel phones, Galazy phones, basically android devices.  Iphones and laptops work fine.  Im attaching the Radioactive trace for this device.  The device seems to stay in the iplearn state then is removed. 

Also, i am thinking about a secondary controller.  If the primary fails, is data and management of the APs lost including client connectivity? or just AP management?

Is their any place to reference for secondary topology possibilities as well as proper configuration for both devices?

@marce1000 

[marce1000]

  - Below you will find the output of the debug Trace when analyzed with https://cway.cisco.com/wireless-debug-analyzer/ , also have a checkup of the controller configuration with the CLI command show tech wireless ; feed the output into https://cway.cisco.com/wireless-config-analyzer/ , (referring to : 'as well as checking checking proper  configuration for 9800 devices and or controllers')

                                            Use these tools for analyzing problems related to client connectivity :
                                          https://logadvisor.cisco.com/logadvisor/wireless/9800/9800ClientConnectivity

                                           Output from debugTrace  obtained from wireless debug analyzer

Connection attempt #1
Connection attempt #2
2023/06/14 14:57:14.008	client-orch-sm	Client made a new Association to an AP/BSSID: BSSID 687d.b45f.686f, WLAN MCS-Site-1, Slot 1 AP 687d.b45f.6860, 9136I-B
2023/06/14 14:57:14.009	dot11	Association success for client, assigned AID is: 1. Client performed fast roam.
2023/06/14 14:57:14.009	client-orch-sm	Client started layer 2 authentication (either dot1X or PSK)
2023/06/14 14:57:14.014	client-keymgmt	Sent M1 for EAPOL 4-Way Handshake
2023/06/14 14:57:14.074	client-keymgmt	Received and validated M2 for EAPOL 4-Way Handshake
2023/06/14 14:57:14.074	client-keymgmt	Sent M3 for EAPOL 4-Way Handshake
2023/06/14 14:57:14.085	client-keymgmt	Received and validated M4 for EAPOL 4-Way Handshake
2023/06/14 14:57:14.085	client-keymgmt	Negotiated the following encryption mechanism: AKM:FT-PSK Cipher:CCMP WPA Version: WPA2
2023/06/14 14:57:14.085	client-auth	Client successfully completed Pre-shared Key authentication. Assigned VLAN: 301
2023/06/14 14:57:14.085	client-orch-sm	Client passed layer 2 authentication
2023/06/14 14:57:14.086	client-orch-state	Starting Mobility Anchor discovery for client
2023/06/14 14:57:14.087	avc-afc	AVC is enabled for the client session
2023/06/14 14:57:14.087	client-orch-state	Entering IP learn state
2023/06/14 14:57:15.060	client-iplearn
2023/06/14 14:59:14.088	client-orch-sm	Controller initiated client deletion with code: CO_CLIENT_DELETE_REASON_IPLEARN_CONNECT_TIMEOUT. Explanation: Controller did not learn client IP address in the allowed time. Actions: Check DHCP server and client IP configuration. Validate if DHCP required is set and client is performing DHCP negotiation. If all is correct, collect RA traces and EPC
2023/06/14 14:59:14.089	dot11	Disassociation packet sent with code status: 108

[billydailey]

Yes sir, i ran it through the tool, and i noticed the highlighted area, what is a possible solution for that?

[marce1000]

 - Have a checkup of the controller configuration with the CLI command show tech wireless ; feed the output into https://cway.cisco.com/wireless-config-analyzer/ , (referring to : 'as well as checking checking proper  configuration for 9800 devices and or controllers')

                                            Use these tools for analyzing problems related to client connectivity :
                                          https://logadvisor.cisco.com/logadvisor/wireless/9800/9800ClientConnectivity

  Also what software version are you using ?

 M.

[billydailey]

Hi there, i attached show tech wireless and ran it, but i dont see anything that would correlate to androids not being able to connect to the active WLAN.  

I am using 17.9.3  

[marce1000]

              >...i attached show tech wireless 
               - I don't see the attachment , 

 M.

[billydailey]

Sorry, i realized it didnt have an extension when i tried to attach.  here it is:

btw back to the debug trace, what is the solution for "Controller did not learn client IP address in the allowed time.?

[marce1000]

                      >... i realized it didnt have an extension when i tried to attach.  here it is:
  - You posted the input for WirelessAnalyzer not the result , I will attach it here : correct the errors reported in the tab wlc1-Check-Results (to start with) , then check if the problem persists , 

 M.

[billydailey]

17.9.3