Redundancy Group License Aggregation Rules - Brocade Communications Systems RFS6000 System Reference Manual

Redundancy group license aggregation rules

The following are rules governing license usage amongst members of a redundancy group:
•
•
•
•
•
•
•
•
•
•
Managing clustering using the Web UI
Managing clustering in the Web UI is done through the Cluster GUI feature. The Cluster GUI feature
updates many key screens in the Web UI allowing you to see APs and Clients managed by all active
members of a cluster.
To enable the Cluster GUI feature:
1. Select Services > Redundancy from the main menu tree
Brocade Mobility RFS6000 and RFS7000 System Reference Guide
53-1001858-01
A redundancy group license is determined by adding individual controller licenses.
Do not allow different port speed/duplex settings on members. Each members should have
the settings.
In a redundancy group of three controllers (S1, S2 and S3), if S1 has X licenses, S2 has Y
licenses and S3 has Z licenses, the license count is X+Y+Z (the aggregation of each controller).
A cluster license is re-calculated whenever a new controller brings existing licenses to a group
or an existing controller's license value changes (increases or decreases).
A simple controller reboot will not initiate a new cluster license calculation, provided the
re-booted controller does not come up with different installed license.
A change to an installed license during runtime initiates a cluster license calculation.
If an existing redundancy group member goes down, it will not initiate a cluster license
calculation.
Whenever the cluster protocol is disabled, a member controller forgets the learned cluster
license as well as peer information needed to compute license totals.
If the controller start-up configuration is removed, a member controller forgets the learned
cluster license as well as peer information needed to compute license totals.
If adding a new controller (with zero or non-zero installed license) to a group with at least one
license contributing controller down, the new group member will receive a different cluster
license value.
For example, for a cluster of three controllers (S1 = 6, S2 = 6 and S3 = 6 licenses), the group
license count is 18. If S1 goes down, the license count is still 18, since the license calculation
is not initiated if a member controller goes down. If S4 (with zero licenses) is introduced, S4
becomes part of the group (can exchange updates and other packets), but has license count of
12 (NOT 18), even though S2 and S3 still show a license count of 18. This should be an
indicator a new member has been introduced during a period when the redundancy group is
not operating with all its license contributing members.
The Redundancy screen displays with the Configuration tab selected.
Configuring controller redundancy and clustering
5
305