Reset Search
 

 

Article

RFS7000 Not Adopting any APs

« Go Back

Information

 
TitleRFS7000 Not Adopting any APs
Symptoms
RFS7000 are not adopting any APs.
!###  show adoption status
not adopted to any wireless controller

Adopted Devices:
---------------------------------------------------------------------------------------------------------------
DEVICE-NAME       VERSION         CFG-STAT         MSGS ADOPTED-BY        LAST-ADOPTION                  UPTIME 
---------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------

 
Environment
  • Extreme Wireless
  • Extreme Wireless WiNG
  • WiNG version 5.X
  • RFS 7000
  • Cluster configured
Cause
  1. Cluster master priority is set incorrectly .
  2. APs adoption request send to cluster master which operational state in standby mode.
!###  show cluster members
----------------------------------------------------------------------------------------------------
         HOSTNAME           MEMBER-ID           MAC          MASTER OPERATIONAL-STATE   LAST-SEEN    
----------------------------------------------------------------------------------------------------
  rfs7000-D98D21-secondary  70.D9.8D.21   00-15-70-D9-8D-21   True    standby           00:00:51 ago  
  rfs7000-182DB5-primary    0B.18.2D.B5   5C-0E-8B-18-2D-B5   False   active            self          
----------------------------------------------------------------------------------------------------

!###  show adoption log adopter
2019-04-22 04:00:22:Redirected 5C-0E-8B-97-1D-28 (0B.97.1D.28) to the cluster master 70.D9.8D.21
2019-04-22 04:00:22:Redirected B4-C7-99-44-2E-A8 (19.44.2E.A8) to the cluster master 70.D9.8D.21
2019-04-22 04:00:22:Redirected FC-0A-81-DA-62-30 (1A.DA.62.30) to the cluster master 70.D9.8D.21
2019-04-22 04:00:22:Redirected 84-24-8D-59-8E-F8 (4D.59.8E.F8) to the cluster master 70.D9.8D.21
2019-04-22 04:00:22:Redirected 74-67-F7-E1-D5-72 (75.E1.D5.72) to the cluster master 70.D9.8D.21
2019-04-22 04:00:22:Redirected 84-24-8D-71-12-64 (4D.71.12.64) to the cluster master 70.D9.8D.21
2019-04-22 04:00:22:Redirected 84-24-8D-71-49-D8 (4D.71.49.D8) to the cluster master 70.D9.8D.21
2019-04-22 04:00:22:Redirected 84-24-8D-70-6E-1C (4D.70.6E.1C) to the cluster master 70.D9.8D.21
2019-04-22 04:00:22:Redirected 84-24-8D-71-49-28 (4D.71.49.28) to the cluster master 70.D9.8D.21
2019-04-22 04:00:22:Redirected 84-24-8D-70-79-BC (4D.70.79.BC) to the cluster master 70.D9.8D.21
2019-04-22 04:00:22:Redirected 5C-0E-8B-8A-70-2F (0B.8A.70.2F) to the cluster master 70.D9.8D.21



 
Resolution
Correct the master priority setting and force restore cluster to configured state.
At rfs7000-182DB5-primary,
>en
#self
#cluster master-priority 255
#commit write
#end
#service cluster force configured-state

 
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255