Environment : Aruba Instant deployment with multiple authentication servers used with server load balancing enabled.
Aruba Instant allows configuring upto 2 authentication servers for client authentication and load balance between them.
GUI Config ::
CLI Config ::
However; it maybe noticed that authentication traffic isn't equally distributed with more / all requests being sent to primary server.
This is expected behavior by design. Aruba Instant's authentication mechanism isn't round-robin based. Load balancing happens based on outstanding authentication sessions. If there are no outstanding sessions, i.e. if rate of auth is low, only primary will be used. secondary will be used only if there are outstanding auth sessions to primary. This approach would allow load balance across asymmetric capacity radius server without getting any input about server capabilities from administrator.