APs unable to adopt to Controller RFS6K v5.8

  • 0
  • 1
  • Problem
  • Updated 2 months ago
  • Solved

Hi Champs!

Our client having issue where the APs at one of the sites are not joining the controller. Though the APs are up and running, serving the clients as well but we can’t see them online on controller.

We can ping the APs from the controller CLI and vice versa.

Another thing we noticed yesterday, when we logged into GUI of an AP, we could see rest of the APs there.

Any thoughts?


RFS6000 v5.8

AP Model: AP7131

Photo of dot1x

dot1x

  • 322 Points 250 badge 2x thumb

Posted 2 months ago

  • 0
  • 1
Photo of Madeline

Madeline, Employee

  • 272 Points 250 badge 2x thumb
Dear Moin, I would suggest you to take a look at this knowledge article:
What is recommended MINT MTU size?

Check to see if Ap is configured to be adopted to the controller or virtual controller ie AP
Do let us know the outcome~ 
Photo of dot1x

dot1x

  • 322 Points 250 badge 2x thumb
The APs have the correct config on them and they are serving the clients.
All the APs are configured to join the controller with following cli command:

controller host <ip address>
Photo of Wei Liang Loh

Wei Liang Loh, Employee

  • 198 Points 100 badge 2x thumb
Hi Moin,

Did you try to check on license count?
What is the message you get from show adoption history or show mint mlcp history?
Photo of Madeline

Madeline, Employee

  • 272 Points 250 badge 2x thumb
If that is the case this knowledge article should help~ 
What is recommended MINT MTU size?

By the way, for remote site AP, you should be using
controller host <ip_address> level 2 
For more information, please refer to the best practice guide pg 12
Photo of dot1x

dot1x

  • 322 Points 250 badge 2x thumb
it's configured as

controller host <ip address> pool 1 level 2
Photo of Robert Zarzycki

Robert Zarzycki, Employee

  • 4,218 Points 4k badge 2x thumb
In case any low bandwidth WAN links are present between the remote sites with high latency and packet loss, it is recommended to increase the default MiNT Hello Interval and Adjacency Hold Timer on both AP and Controller Profile. Usually hello interval value of 60 with adjacency hold-time of 180 should suffice on high latency links, but in some rare cases it may be extended to 120 hello interval and 360 adjacency hold-time. 
Photo of Robert Zarzycki

Robert Zarzycki, Employee

  • 4,218 Points 4k badge 2x thumb
Access Point Profile Example:

!
profile ap7532 default-ap7532
  autoinstall configuration
  autoinstall firmware
  interface radio1
  interface radio2
  interface ge1
  interface vlan1
    ip address dhcp
    ip address zeroconf secondary
    ip dhcp client request options all
  interface pppoe1
  use firewall-policy default
  use client-identity-group
  default controller
  hello-interval 60 adjacency-hold-time 180 service pm sys-restart
  router ospf
!