Brocade Mobility RFS Controller System Reference Guide (Supporting software release 5.5.0.0 and later) - Manual (Page 396)

384 Brocade Mobility RFS Controller System Reference Guide
53-1003099-01
8
5. Define the following Cluster Settings parameters to set this profile’s cluster mode and
deployment settings:
6. Within the Cluster Member field, select the Cluster VLAN checkbox to enable a spinner control
to designate the controller or service platform VLAN where cluster members are reachable.
Specify a VLAN in the range of 1 - 4094.
Specify the IP addresses of the VLAN’s cluster members using the table.
7. Select OK to save the changes made to the profile’s cluster configuration. Select Reset to
revert to the last saved configuration.
Cluster Profile Configuration and Deployment Considerations
Profile Cluster Configuration (Controllers and Service Platforms Only)
Before defining a profile cluster configuration, refer to the following deployment guidelines to
ensure the configuration is optimally effective:
Cluster Mode A member can be in either an Active or Standby mode. All active member can adopt Access Points.
Standby members only adopt Access Points when an active member has failed or sees an Access
Point not adopted by a controller or service platform. The default cluster mode is Active and enabled
for use with the profile.
Cluster Name Define a name for the cluster name unique to its configuration or profile support requirements. The
name cannot exceed 64 characters.
Master Priority Set a priority value from1 - 255, with the higher value given higher priority. This configuration is the
device’s priority to become the cluster master. In a cluster environment, one device from the cluster
is elected as the cluster master. The master priority setting is the device’s priority to become cluster
master. The active primary controller has the higher master priority. The default value is 128.
Handle STP Convergence Select the check box to enable Spanning Tree Protocol (STP) convergence for the controller or
service platform. In general, this protocol is enabled in layer 2 networks to prevent network looping.
Spanning Tree is a network layer protocol that ensures a loop-free topology in a mesh network of
inter-connected layer 2 controllers or service platforms. The spanning tree protocol disables
redundant connections and uses the least costly path to maintain a connection between any two
cluster members in the network. If enabled, the network forwards data only after STP convergence.
Enabling STP convergence delays the redundancy state machine execution until the STP
convergence is completed (the standard protocol value for STP convergence is 50 seconds).
Delaying the state machine is important to load balance APs at startup. The default setting is
disabled.
Force Configured State Select the check box to enable this controller or service platform to take over for an active controller
or service platform member if it were to fail. A standby node takes over APs adopted by the failed
controller or service platform. If the failed controller or service platform were to come available
again, the active controller or service platform starts a timer based on the Auto Revert Delay
interval. At the expiration of the Auto Revert Delay, the standby node releases all adopted APs and
goes back to a monitoring mode. The Auto Revert Delay timer is stopped and restarted if the active
controller or service platform goes down and comes up during the Auto Revert Delay interval. The
default value is disabled.
Force Configured State
Delay Specify a delay interval in either Seconds (1 - 1,800) or Minutes (1 - 30). This is the interval a
standby node waits before releasing adopted APs and goes back to a monitoring mode when a
controller or service platform becomes active again after a failure. The default interval is 5 seconds.