Sets the cluster configuration
cluster [force-configured-state|force-configured-state-delay|handle-stp|master-priority|member|mode|name|radius-counter-db-sync-time]
cluster [force-configured-state|force-configured-state-delay <3-1800>|handle-stp| master-priority <1-255>]
cluster member [ip|vlan]
cluster member [ip <IP> {level [1|2]}|vlan <1-4094>]
cluster mode [active|standby]
cluster name <CLUSTER-NAME>
cluster radius-counter-db-sync-time <1-1440>
cluster [force-configured-state|force-configured-state-delay <3-1800>|handle-stp|master-priority <1-255>]
| force-configured-state | Forces adopted
APs to auto revert when a failed wireless controller or service platform (in
a cluster) restarts When an active controller (wireless controller, or service platform) fails, a standby controller in the cluster takes over APs adopted by the failed active controller. If the failed active controller were to restart, it starts a timer based on the ‘force-configured-state-delay‘ interval specified. At the expiration of this interval, the standby controller releases all adopted APs and goes back to a monitoring mode. If the active controller fails during this interval, the ‘force-configured-state-delay‘ timer is stopped. The timer restarts as soon as the active controller comes back up. This feature is disabled by default. |
| force-configured-state-delay <3-1800> | Forces cluster
transition to the configured state after a specified interval
This is the interval a standby controller waits before releasing adopted APs when a failed primary controller becomes active again. |
| handle-stp | Enables
Spanning Tree Protocol (STP) convergence handling. This
feature is disabled by default. In layer 2 networks, this protocol is enabled to prevent network looping. 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. |
| master-priority <1-255> | Configures
cluster master priority
In a cluster environment one device from the cluster is elected as the cluster master. A device‘s master priority value decides the device‘s priority to become cluster master. |
cluster member [ip <IP> {level [1|2]}|vlan <1-4094>]
| member | Adds a member to the cluster. It also configures the cluster VLAN where members can be reached. |
| ip <IP> level [1|2] | Adds IP address
of the new cluster member
|
| vlan <1-4094> | Configures the
cluster VLAN where members can be reached
|
cluster mode [active|standby]
| mode [active|standby] | Configures
cluster member‘s mode as active or standby
A member can be in either an Active or Standby mode. All active member controllers 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. |
cluster name <CLUSTER-NAME>
| name <CLUSTER-NAME> | Configures the
cluster name
|
cluster radius-counter-db-sync-time <1-1440>
| radius-counter-db-sync-time <1-1440> | Configures the interval, in minutes, at
which the RADIUS counter database is synchronized with
the dedicated NTP server resource.
Use the show > cluster > configuration command to view RADIUS counter DB sync time. |
nx9500-6C8809(config-profile-default-ap8533)#cluster name cluster1 nx9500-6C8809(config-profile-default-ap8533)#cluster member ip 172.16.10.3 nx9500-6C8809(config-profile-default-ap8533)#cluster mode active nx9500-6C8809(config-profile-default-ap8533)#show context profile ap8533 default-ap8533 bridge vlan 1 description Vlan1 ....................................................................... cluster name cluster1 cluster member ip 172.16.10.3 cluster member vlan 1 nx9500-6C8809(config-profile-default-ap8533)#
| no | Removes cluster member |