Dealing with swarm mode problems
Found on The Aruba Blog
*Written By arunkumar1 *posted Jun 26, 2014 12:09 PM
How to troubleshoot Aruba AP connectivity.
First:
Pound is a proxy server that intercepts all swarm communication and hands it off to our SwarmHandler
(all non-swarm traffic goes to apache).
This would be a good command:
grep swarm /var/log/pound
A lack of data here would indicate that no requests are arriving from the Instant APs. So, going from there:
qlog enable swarm_debug
This should create a swarm_debug
log in ``/var/log/amp_diag` that’s base64-encoded.
You could use this command after enabling the logging to see detailed headers that actually arrive at the AMP:
qlog_decoder --topics <topic> --notail --nofollow /var/log/amp_diag/swarm_debug
- cmd_queue
- Records all commands sent to SwarmHandler
- headers
- HTTPS headers received from a swarm
- commands
- when a command is being put into HTTPS response
- config
- the running-config sent from a swarm
- delta-config
- the delta-config being sent to SwarmHandler
- state
- decoded state payload data
- stat
- decoded stat payload data
This command is useful for putting human-readable versions of each topic into /tmp/swarm
:
On the IAP, from the support link, you can check the device’s Datapath Session Table for connections to AMP by the virtual controller.