Lets Learn Network

Cluster gives you uninterrupted service during fail over. Cluster mainly design for Mission critical environment. To obtain this service you need Mobility Master base design

Cluster Provides you below Features

• Seamless Campus Roaming :- WLAN client remain anchored to single controller, where they roam on campus.
• Client stateful Fail-over :- Full Redundancy within redundancy  if Cluster member failed active and connected client will fail over to redundant controller
• Client Load balancing :- Clients are automatically load balance between the Cluster members to prevent high utilization
• AP Load Balancing :- AP create tunnel with primary controller and Secondary controller this is called Active ap anchor (A-AAC) and Create Standby AP anchor Controller (S-AAC)

When deploying cluster need to consider about below

• All Cluster members should have same OS
• Mix Hardware not Supported (HW and VM)
• Mix of 72XX and 70XX MC in same cluster not Recommended IF you using like this Cluster members should be 4
• If Cluster Terminating RAP only 4 members should be in cluster
• 70XX only 4 cluster members
• 72XX Max is 12 Members
• VMC only 4 Members

Cluster Leader election Process

• Configured Priority 128 Default
• Platform Value
• Controller MAC address

Cluster Leader Roles

• Becket map Computation :- Map Client to Dedicated MC in the Cluster
• Dynamically load-balance Client :- Leader make sure to each members in the cluster given service approximately same number of clients. Load balance automatically manage load increase or member joins or leave
• Identify standby MC :- Leader perform dynamic assignment of standby AP anchor controller S-AAC and standby user anchor controller S-UAC

Cluster Connection Types

L2 Connection	L3 Connection
Full Redundant	Not Full Redundant
Aps and Clients are fully Replicated	Only Aps are fully Replicated
Users Fully Sync between active and standby UAC nodes	Users are not fully sync between active and standby UAC nodes
High valued sessions are synced	High value sessions are not fully sync
Users are not de-authorized upon failover even Active to standby UAC	Users are de-authorized upon failover even from active to standby UAC Users must do a full dot1X Authentication

Define Mobility Cluster Roles

• Client Load balance Calculation :-
  • Active client load balance re balance threshold on any node should be 50%
  • Standby client re balance threshold 75% on any node
  • Unbalance threshold 5%
  • Load balance is trigger when active or standby re balance threshold is met and unbalance threshold is met
• AP and user mapping into a cluster
  • AP load Balancing
    • Lms-IP is ignore when AP LB enable
    • AP s are LB among cluster members based on 1% of each MC capacity
    • AP LB is disable by default
• During load balance a certain Oder is used 1st standby load is redistributed across cluster members and then active load is redistribute until total load is balance