Wireless Access

last person joined: 20 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

AP105 mesh issue

This thread has been viewed 1 times

  • 1.  AP105 mesh issue

    Posted Apr 30, 2015 05:03 AM

    Hi all,

    we have an Aruba650 Controller (AOS 6.4.2.2) with 11 APs. Two of these APs, both AP105, is connected to each other in mesh. We have continuosly some problems with them: as you can see from the sreen below, the mesh-link is ok

     

    show ap mesh topology.PNG

     

    but periodically the mesh-link goes down and it doesn't come back active until we reboot the Portal AP.

    Can someone give me some explanation of why what happens and any suggestions on how to fix it?

     

    Here I attach the mesh configuration too. Are the parameters ok or do I have t change somethings?

    show ap mesh configuration.PNG

     

    Thanks,

    Massimo

     



  • 2.  RE: AP105 mesh issue

    EMPLOYEE
    Posted Apr 30, 2015 07:49 AM
    I would type "show log wireless 50" to see of there was a channel change related to DFS or Radar.


  • 3.  RE: AP105 mesh issue

    Posted Apr 30, 2015 08:11 AM

    Yes, this moorning for example we have this log messages for the Portal AP:

     

    Thu Apr 30 03:47:53 2015: <132>Apr 30 02:47:35 2015 192.168.150.9 sapd[722]: <404076> <WARN> |AP AP9@192.168.150.9 sapd| AM 24:de:c6:a4:76:68: Radar detected on interface wifi0, channel 136, typeid 34
    Thu Apr 30 03:47:53 2015: <132>Apr 30 02:47:36 2015 192.168.150.9 sapd[722]: <404064> <WARN> |AP AP9@192.168.150.9 sapd| AM 24:de:c6:a4:76:68: ARM Radar Detected Trigger Current Channel 136 new_rra 128/8
    Thu Apr 30 03:47:55 2015: <132>Apr 30 02:47:38 2015 192.168.150.9 sapd[722]: <404072> <WARN> |AP AP9@192.168.150.9 sapd| AM 24:de:c6:a4:76:68: ARM - too much power decreasing... cov-index 12/0 tx-power 12 new_rra 128/8

     

     

    but what I expect is that once changed the channel, after the right time, the mesh link becomes active again. Unluckily this doesn't happens until I reboot the Portal AP.

     

     



  • 4.  RE: AP105 mesh issue

    EMPLOYEE
    Posted Apr 30, 2015 08:15 AM
    The short answer would be to unchecked DFS channels from your regulatory domain profile so that you do not have those channel change issues. It might take some time for the mesh point to "find" the mesh portal after a forced radar channel change.


  • 5.  RE: AP105 mesh issue

    Posted Apr 30, 2015 09:26 AM

    Ok, thanks cjoseph.

    I see the only channels in Europe that are not affected by DFS  are 36,40,44,48, but these are indicated as "Indoor". My Mesh APs are set as "Outdoor" now. So if I want to enable only these 4 channels, will I have to set the APs as "Indoor"?

     

    P.S: I understand that It might take some time for the mesh point to "find" the mesh portal after a forced radar channel change, but it remains DOWN until I reboot the AP! I can wait also many hours!

     



  • 6.  RE: AP105 mesh issue

    EMPLOYEE
    Posted Apr 30, 2015 10:18 AM

    I am asking how DFS is handled with out mesh, but in general it's a very good idea to disable DFS channels for mesh anyway since it will be so disruptive. I also agree the AP should scan after X amount of time and that doesn't seem like it's happening. 

    Is your deployment for indoors or outdoors, and what antennas are used? When an AP is provisioned, if you leave it on 'auto', the controller sets the condition based on the AP-type (so a 105 would default to indoor). If you provision it to Outdoor, then they will exclusively use the outdoor channels. If you mesh is outdoor, it should certainly be re-provisioned to outdoor (re-provision the mesh point first!!!!). That will ensure they use the outdoor channels which are not bound under DFS and support higher EIRP (again depending on the antennas).