adoption status comm error

  • 1
  • 2
  • Problem
  • Updated 12 months ago
  • Solved
when I do show adoption status on vx9000/wing586 I see "comm error" status for few access points. controller and ap's located in the different places. ap connected in trunk port and have native vlan 10 and trunk allowed 10-13 vlans. DHCP on vlan10 have "option 191 ip_controller;level=2". AP's wich located in the same place as controller doesn't have this trouble
show adoption config-error gives "no configuration error"
Photo of Alexander Rusov

Alexander Rusov

  • 92 Points 75 badge 2x thumb

Posted 1 year ago

  • 1
  • 2
Photo of Andy Holden

Andy Holden, Employee

  • 1,132 Points 1k badge 2x thumb

I have seen this error a few times, it is usually attributed to a slow network response from the AP to the controller IE the Controller may be busy handling the adoption of other APs in the network.


Try taking one of the APs and rebooting it and see if that clears the message

Photo of Andrew Webster

Andrew Webster

  • 1,756 Points 1k badge 2x thumb

Two issues you might want to check:

  1. Check that  no firewalls are blocking UDP port 24576,
  2. Make sure that the MTU between sites is 1500, if not you can lower the mint global MTU setting (mint-policy global-default mtu 900-1500), this affects all sites, to the lowest MTU among all the sites.


Photo of Alexander Rusov

Alexander Rusov

  • 92 Points 75 badge 2x thumb
Andrew, thanks for answer. I already found the problem. I changed default mint-mtu.