Controllerless Networks

Reply
Highlighted

AP105 not able to join Aruba620 Controller

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%).

Super Contributor I

Re: AP105 not able to join Aruba620 Controller

Hi,

 

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

 

 

Cheers, Frank
Aruba Partner Ambassador| AMFX#22| ACCX#613| ACMX#733| ACDX#744

If you like my posts, kudo's are welcome. If it solves your problem, please click 'Accept as Solution'

Re: AP105 not able to join Aruba620 Controller

Hi,

 

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



Guru Elite

Re: AP105 not able to join Aruba620 Controller

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.


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.3 User Guide
InstantOS 8.3 User Guide
Airheads Knowledgebase
Airheads Learning Videos

Re: AP105 not able to join Aruba620 Controller

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"

Re: AP105 not able to join Aruba620 Controller

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

 

Re: AP105 not able to join Aruba620 Controller

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"

ACMP, ACSA, ACDX #985
If my post addresses your query, give kudos:)

Re: AP105 not able to join Aruba620 Controller

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

Super Contributor I

Re: AP105 not able to join Aruba620 Controller

thanks for the update

Cheers, Frank
Aruba Partner Ambassador| AMFX#22| ACCX#613| ACMX#733| ACDX#744

If you like my posts, kudo's are welcome. If it solves your problem, please click 'Accept as Solution'
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: