Wireless Access

last person joined: 19 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

APs could not connect to the controller anymore

This thread has been viewed 3 times

  • 1.  APs could not connect to the controller anymore

    Posted May 17, 2020 08:26 AM

    We have a small site and local APs are connecting over an MPLS WAN line to the controllers in different location.

    Since the MPLS line was down on last friday, AP's could not connect anymore to the controller:

     

    May 15 08:41:42  sapd[1111]: <311020> <ERRS> |AP DELINEX05AP07@10.5.9.27 sapd|  An internal system error has occurred at file sapd_sysctl.c function sapd_sysctl_write_param line 167 error Error opening /proc/sys/net/aruba101/wmm_eap_ac : No such file or directory. 255.

    May 15 08:41:50  sapd[1111]: <311004> <WARN> |AP DELINEX05AP07@10.5.9.27 sapd|  Missed 8 heartbeats; rebootstrapping

    May 15 08:42:08  sapd[1111]: <311020> <ERRS> |AP DELINEX05AP07@10.5.9.27 sapd|  An internal system error has occurred at file sapd_sysctl.c function sapd_sysctl_write_param line 167 error Error opening /proc/sys/net/aruba100/wmm_eap_ac : No such file or directory. 255.

    May 15 08:42:08  sapd[1111]: <311020> <ERRS> |AP DELINEX05AP07@10.5.9.27 sapd|  An internal system error has occurred at file sapd_sysctl.c function sapd_sysctl_write_param line 167 error Error opening /proc/sys/net/aruba101/wmm_eap_ac : No such file or directory. 255.

    May 15 08:42:16  sapd[1111]: <311004> <WARN> |AP DELINEX05AP07@10.5.9.27 sapd|  Missed 8 heartbeats; rebootstrapping

     

    I was thinking maybe the iSP did some changes on their side but they didnt confirmed. Its weird that APs cannot build anymore tunnels with the controller.

    However, I can ping the APs from the controller.



  • 2.  RE: APs could not connect to the controller anymore

    MVP GURU
    Posted May 17, 2020 08:31 PM

    Have you looked into bug IDs AOS-186166 and AOS-199190. This was reported in 8.5.0.5 and fixed in 8.5.0.7 (for AP-105 and AP-135)

     

     



  • 3.  RE: APs could not connect to the controller anymore

    EMPLOYEE
    Posted May 18, 2020 10:06 AM

    Could it be that the path-MTU was reduced during the maintenance on your WAN? Campus APs expect a LAN like network with corresponding MTU. I've seen campus APs not coming up on lower MTU links, and I think there is a setting in the AP to reduce the mtu from the AP to overcome such issues.

     

    Please work with Aruba Support if you haven't involved them yet.