AP Provisioning |
15
The conductor AP will reject the association request of the member AP if its configuration is not supported
by the cluster. A member AP will be deemed incompatible by the cluster if there is a image class mismatch,
regulatory domain mismatch, or OEM mismatch between the member AP and the conductor AP.
Run the
show swarm state
command in the CLI of the member AP to view the swarm details. Check the
AP swarm state
to see if the member AP is allowed in the network. The AP swarm state will display
swarm_not_allowed
if the member AP is not supported in the cluster. Use the
show log system
command to get additional information about the cause for mismatch.
The sample below displays the swarm status of the member AP, generated by the
show swarm state
command:
(Member AP)# show swarm state
AP Swarm State
:swarm_not_allowed
mesh auto eth0 bridging
:no
Config in flash
:yes
factory SSID in flash :yes
extended-ssid configured :yes
extended-ssid active
:yes
advanced-zone configured :no
Factory default status
:no
Source of system time
:Image file
Config load cnt
:1
VC Channel index
:1
IDS Client Gateway Detect :yes
Config Init success cnt for heartbeat
:0
Config Init success cnt for register
:0
Config Init skipping cnt for heartbeat
:0
Config Init skipping cnt for register
:0
Config Init last success reason
:N/A
Config Init last success time
:N/A
The following are probable causes for member-cluster incompatibility:
Type of
Mismatch
Cause
Log Event
Image class
mismatch
Member AP and
the APs in the
cluster belong to
different image
classes
AP class not match, Conductor-X, member -Y
Regulatory
domain
Mismatch
Member AP and
the APs in the
cluster are of
different
regulatory
domains
AP regulatory domains don't match Conductor-X, member-Y
OEM Mismatch
Member AP and
the APs in the
cluster are of
different OEMs
AP regulatory domains don't match Conductor-X, member-Y
NOTE:
In the event of a image class mismatch, image download can be facilitated through Activate, or AirWave,
or Central platform. If either one of these management platforms are configured in the cluster, the member AP
will install the appropriate image file from the cloud platform, reboot, and join the cluster.