Thank you for sending that to me, and for letting me know, it was in my junk mail folder for some reason (also found your previous email that we had discussed, very sorry about that). I reviewed the tech data, thank you for enabling those debugs. I’m seeing a lot of echo time outs, which would explain why the AP is not connecting to your XIQ instance, even though the CLI says it has connected.
ExtremeCloud IQ (XIQ) and the APs have a call and response check-in system that allows them to confirm that each side of the connection is still responsive; these call and response packets are called echos. There is a specific time window within which an AP would need to respond to an echo to be considered still responsive. If the AP misses a certain number of echos back to back, it is considered disconnected until it responds again. If an AP is still connected to the internet and passing traffic while missing echos, it's likely due to latency on the network; the AP is unable to process the echo request quickly enough due to the amount of traffic it has to process before responding. You can see what I’m seeing if you search your tech data file for “echo” or “timed out”, look for these messages: ah_capwap_echo_timer timed out
Since the AP isn’t passing client traffic yet, the latency would likely be on your backend network between the AP and XIQ. I’d be interested to see a packet capture to take a look at the traffic the AP is seeing currently.
