Wireless Access

Hi, 

I have a small lab setup with a virtual Conductor and Virtual Controller running version 8.10.0.9 with a single AP 215 registered to it. 

I haven't sorted a license for it yet, and it is a used AP so support is probably not an option. 

Reading the release notes the AP is supported in the code, I can't see any relevant open known issues etc. 

The console of the AP and the logs on the controller show that the controller is requesting the reboot. It isn't a process on the AP falling over. 

A while after that the AP does also show a message of the tunnel to the controller MTU changing from 1500 to 1578, but not sure that is relevant. 

AP rebooted Tue Dec  5 15:48:25 GMT 2023; SAPD: Reboot requested by controller
shutting down watchdog process (nanny will restart it)...
 
        <<<<<       Welcome to the Access Point     >>>>>
 
~ # [   61.803507] uol_add_tun_l3:252 tun add l3(10.10.51.10->10.10.50.120): mtu=1500, l2hlen=14, ifnum=0 odev=br0
[   62.117051] uol_add_tun_l2:290 tun add l2(10.10.51.10->10.10.50.120): smac=40:e3:d6:c2:d0:32 dmac=00:27:90:db:7a:c5
[   71.492807] uol_del_tun:308 tun del (10.10.51.10->10.10.50.120)
[   71.580799] uol_add_tun_l3:252 tun add l3(10.10.51.10->10.10.50.120): mtu=1500, l2hlen=14, ifnum=0 odev=br0
[   72.261047] uol_add_tun_l2:290 tun add l2(10.10.51.10->10.10.50.120): smac=40:e3:d6:c2:d0:32 dmac=00:27:90:db:7a:c5
[   94.551032] aruba_usb_power_control:1318 en:0 status:0
[  132.505883] uol_update_mtu:427 tun update (10.10.51.10->10.10.50.120): mtu updated to 1578

Is there anything anyone can suggest? Could it be the lack of license? Is there a recommended code to downgrade to seeing as I am running the latest and greatest code (I am aware the 215 will not be supported in 8.11). 

Not sure if relevant but the AP used to be used in IAP mode running version 6 software before I upgraded it to a CAP. 

The MTU messages look innocent to me.

The Reboot reason indicates that the controller requested a reboot, so I would have a look at the controller logs. Those should also indicate if there were licensing or other issues.

------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------

Do you have any Flags on the show ap Database?

what is the Max MTU to the AP? did you try setting it under the ap-profile?

Are you using CPSEC?

show log all | i APname or mac?

If you have no licensing in place for the Mobility Conductor or the VMC then the AP is not going to be successful in communicating with the VMC and will result in the AP rebooting on a normal cycle.

------------------------------
Carson Hulcher, ACEX#110
------------------------------

Hi hawley_craig,

controller logs would be indeed interesting to see. You can input:

show log all | include "Ap-Name"

I'd look for heartbeat timeouts for example. We once had an issue affecting an entire plant, where APs were rebooting all 10-15min or so. Logs showed massive heartbeat tieouts. We fixed this configuring storm-control on the switchports correctly. The fetaure was missconfigured and the values were too strict.

Hope this helps.

Greetings