10-18-2022 01:59 AM
Since ExtremeNetworks forced us to use a remote Internet based cloudiq, often 10 or 15% of or AP show disconnected.
The internet cloudiq is only 7 ip hops away ( nl-gcp.extremecloudiq.com ), sub 10 milliseconds.
C:\WINDOWS>tracert -d nl-gcp.extremecloudiq.com
Tracing route to nl-gcp.extremecloudiq.com [34.91.82.64]
over a maximum of 30 hops:
1 <1 ms 3 ms 6 ms 10.12.255.253
2 3 ms 1 ms <1 ms 10.3.1.6
3 1 ms <1 ms <1 ms 172.31.44.3
4 2 ms 2 ms 1 ms 193.191.18.41
5 3 ms 13 ms 2 ms 10.28.35.54
6 24 ms 14 ms 6 ms 80.249.208.247
7 9 ms 9 ms 9 ms 34.91.82.64
Trace complete.
We can still get on the AP via SSH, and run commands like 'show capwap client'. Any hints welcome on how to trigger reconnect or test the connectivity from the AP command line.
10-18-2022 05:55 AM
Do you have more than one Internet connection which are balanced? If so, make sure the AP capwap connection goes out always using the same connection (meaning the same IP public address) otherwise the XIQ server might receive packets with different source addresses and think the AP is disconnected.
10-19-2022 07:20 AM
Double checked, one outside/public IP. Even if we would change that, the uniqe AP id should make it irrelevant, right?
10-21-2022 05:49 AM
Even the cloudiq on the internet is on different ip addresses ( in the same range )
I see 34.91.82.7, 72, 76 in the same second in a tcpdump capture.
10-24-2022 12:15 AM
Hi,
ssh to one AP and enter the command:
capwap client transport HTTP
save config
This will use TCP port 80 for capwap connection instead of UDP 12222.
Check if you still see session disconnects.