|
Cluster Mode
|
A member can be in either an Active or Standby mode. All
active member controllers or service platforms can adopt
access points. Standby members only adopt access points
when an active member has failed or sees an access point
that‘s not yet adopted. 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 from 1 and 255 with the higher value
being given higher priority. This configuration is the
device‘s priority to become cluster master. In cluster
environment one device from cluster members is elected
as cluster master. This configuration is the device‘s
priority to become cluster master. The default is
128.
|
|
Handle STP Convergence
|
Select the radio button 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
controller or service platform. The spanning tree
protocol disables redundant connections and uses the
least costly path to maintain a connection between any
two controllers or service platforms 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 radio button to allow this controller or
service platform to take over for an active member if it
were to fail. A standby controller or service platform
in the cluster takes over APs adopted by the failed
active member. If the failed active member were to come
back up, the active member starts a timer based on the
Auto Revert Delay interval. At the expiration of the
Auto Revert Delay, the standby member releases all
adopted APs and goes back to a monitoring mode. The Auto
Revert Delay timer is stopped and restarted if the
active member 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 minutes (3 - 1,800). This is
the interval a standby member waits before releasing
adopted APs and goes back to a monitoring mode when an
active cluster member becomes active again after a
failure. The default interval is 5 minutes.
|
|
Radius Counter DB Sync Time
|
Specify a sync time (from 1 - 1,440 minutes) a RADIUS
counter database uses as its synchronization interval
with the dedicated NTP server resource. The default
interval is 5 minutes.
|
