Controllerless Networks

last person joined: 2 days ago 

Instant Mode - the controllerless Wi-Fi solution that's easy to set up, is loaded with security and smarts, and won't break your budget
Expand all | Collapse all

AP105 not able to join Aruba620 Controller

This thread has been viewed 1 times
  • 1.  AP105 not able to join Aruba620 Controller

    Posted Dec 06, 2018 02:13 PM

    We have Master-Local(version 6.4.2.5) setup, two 105 APs are not able to join the controller, we processed RMA, brand new APs are also having the same problem.

     

    logs as below.

    e 7172 error Unexpected result code CONFIG_ERR.
    Dec 6 14:08:12 :305004: <ERRS> |stm| AP ac:a3:1e:cf:cf:62: ap regulatory-domain-profile "default" is invalid.
    Dec 6 14:08:12 :305027: <ERRS> |stm| AP ac:a3:1e:cf:cf:62: No valid instances of required profile "ap regulatory-domain-profile"
    Dec 6 14:08:24 :399838: <WARN> |nanny| Resource 'Controlpath CPU' has exceeded 45% threshold (actual:61%).



  • 2.  RE: AP105 not able to join Aruba620 Controller

    EMPLOYEE
    Posted Dec 06, 2018 03:44 PM

    Hi,

     

    What is the exact type of the AP's? IAP-105-XX or AP-105?

     

     



  • 3.  RE: AP105 not able to join Aruba620 Controller

    Posted Dec 06, 2018 07:21 PM

    Hi,

     

    its AP-105 DBDC 2x2:2 802.11agn AP





  • 4.  RE: AP105 not able to join Aruba620 Controller

    EMPLOYEE
    Posted Dec 07, 2018 05:11 AM

    If you processed an RMA, you should also open a TAC case.  The message suggests a regulatory issue with your configuration, but I cannot be sure with a couple lines of logs.



  • 5.  RE: AP105 not able to join Aruba620 Controller

    Posted Dec 07, 2018 09:31 AM

    Yes, we have the TAC case, Initially, TAC suspects the AP fault after testing connecting not working AP to working AP port as we see the same issue.

    Now we received two new APs they are also behaving same as previous, I have added more logs from the controller.

     

    Dec 7 09:19:47 :305004: <ERRS> |stm| AP ac:a3:1e:cf:cf:67: ap regulatory-domain-profile "default" is invalid.
    Dec 7 09:19:47 :305027: <ERRS> |stm| AP ac:a3:1e:cf:cf:67: No valid instances of required profile "ap regulatory-domain-profile"
    Dec 7 09:20:31 :303022: <WARN> |AP ac:a3:1e:cf:cf:62@10.158.16.135 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:01:48 PST 1999: SAPD: Reboot after image upgrade
    Dec 7 09:20:43 :399838: <WARN> |nanny| Resource 'Controlpath CPU' has dropped below 45% threshold (actual:12%).
    Dec 7 09:20:50 :305004: <ERRS> |stm| AP ac:a3:1e:cf:cf:62: ap regulatory-domain-profile "default" is invalid.
    Dec 7 09:20:50 :305027: <ERRS> |stm| AP ac:a3:1e:cf:cf:62: No valid instances of required profile "ap regulatory-domain-profile"
    Dec 7 09:20:50 :311020: <ERRS> |AP ac:a3:1e:cf:cf:62@10.158.16.135 sapd| An internal system error has occurred at file sapd_msg.c function sapd_hello_cb line 7172 error Unexpected result code CONFIG_ERR.
    Dec 7 09:20:50 :305004: <ERRS> |stm| AP ac:a3:1e:cf:cf:62: ap regulatory-domain-profile "default" is invalid.
    Dec 7 09:20:50 :305027: <ERRS> |stm| AP ac:a3:1e:cf:cf:62: No valid instances of required profile "ap regulatory-domain-profile"
    Dec 7 09:22:35 :303022: <WARN> |AP ac:a3:1e:cf:cf:62@10.158.16.135 nanny| Reboot Reason: AP rebooted Fri Dec 31 16:01:25 PST 1999; SAPD: Reboot after image upgrade failed: 32512
    Dec 7 09:22:53 :305004: <ERRS> |stm| AP ac:a3:1e:cf:cf:67: ap regulatory-domain-profile "default" is invalid.
    Dec 7 09:22:53 :305027: <ERRS> |stm| AP ac:a3:1e:cf:cf:67: No valid instances of required profile "ap regulatory-domain-profile"
    Dec 7 09:22:54 :305004: <ERRS> |stm| AP ac:a3:1e:cf:cf:62: ap regulatory-domain-profile "default" is invalid.
    Dec 7 09:22:54 :305027: <ERRS> |stm| AP ac:a3:1e:cf:cf:62: No valid instances of required profile "ap regulatory-domain-profile"
    Dec 7 09:22:54 :311020: <ERRS> |AP ac:a3:1e:cf:cf:62@10.158.16.135 sapd| An internal system error has occurred at file sapd_msg.c function sapd_hello_cb line 7172 error Unexpected result code CONFIG_ERR.
    Dec 7 09:22:54 :305004: <ERRS> |stm| AP ac:a3:1e:cf:cf:62: ap regulatory-domain-profile "default" is invalid.
    Dec 7 09:22:54 :305027: <ERRS> |stm| AP ac:a3:1e:cf:cf:62: No valid instances of required profile "ap regulatory-domain-profile"



  • 6.  RE: AP105 not able to join Aruba620 Controller

    Posted Dec 07, 2018 10:08 AM

    Miss to add one more point, we tried rebooting the controller still no luck.

     



  • 7.  RE: AP105 not able to join Aruba620 Controller
    Best Answer

    MVP EXPERT
    Posted Dec 07, 2018 10:55 AM

    What is the regulatory domain of the controller and of the AP? Have you made any changes to the default profile of the regulatory domain?

     

    Dec 7 09:20:50 :305004: <ERRS> |stm| AP ac:a3:1e:cf:cf:62: ap regulatory-domain-profile "default" is invalid.
    Dec 7 09:20:50 :305027: <ERRS> |stm| AP ac:a3:1e:cf:cf:62: No valid instances of required profile "ap regulatory-domain-profile"


  • 8.  RE: AP105 not able to join Aruba620 Controller
    Best Answer

    Posted Dec 12, 2018 04:11 AM

    After changing the default AP group regulatory domain on Master controller issue got resolved.



  • 9.  RE: AP105 not able to join Aruba620 Controller

    EMPLOYEE
    Posted Dec 12, 2018 04:14 AM

    thanks for the update