Clustering MAG devices are supported on the LAN; but rarely on the WAN. The reason for this is that WAN connections are often the source of sporadic latency and reduced bandwidth that will almost certainly interfere with cluster communication; regardless of whether it is for MAG PCS devices or the previous generation PCS devices.
In a well connected environment, in which latency remains low and available bandwidth remains high, the ability for each device to fully communicate without pause is preserved and clustered systems should not get confused over which system should own potentially tens of thousands of live user sessions. The nodes regularly communicate session, configuration, and timestamp information and any interruptions and loss of communications will impact cluster nodes, when attempting to recover.
It is this LAN or campus network class of service that must be displayed in both the design and delivery, if maximum uptime is indeed the goal, as WAN circuits tend to become congested, when remote access is required.
For high latency connections between cluster nodes, to maintain configurations between multiple systems across the WAN, the Push Config
feature is the recommended approach.
The best network for Active-Active cluster connectivity of nodes is a LAN-Type or campus network with extremely low latency and high bandwidth.
Other good practices for an Active-Active cluster, when latency is high are as follows:Note: Disabling session and last access sync will cause users to re-authenticate, when connecting to other nodes of the same cluster.