Wireless Access

I am currently having issues getting a mesh network up using a Remote Mesh Portal and a Mesh Point running Arubaos 8.3

The 2 AP's are displayed as up in the gui but clients won't connect to the mesh point.

When i run "ap mesh neighbors" against the Remote Access Portal i get the following

Neighbor list
-------------
MAC                Portal             Channel  Age  Hops  Cost   Relation                 Flags  RSSI  Rate Tx/Rx  A-Req  A-Resp  A-Fail  HT-Details        Cluster ID
---                ------             -------  ---  ----  ----   -----------------        -----  ----  ----------  -----  ------  ------  ----------        ----------
xx:xx:xx:xx:3e:70  00:00:00:00:00:00  56E      0    1     65535  N 30s                    V      44    -           16     16      0       VHT-80MHzsgi-2ss  Mesh_Cluster
xx:xx:xx:xx:3e:71  00:00:00:00:00:00  64E      0    1     65535  N 21m:53s                Vu     45    -           0      0       0       VHT-80MHzsgi-2ss  Mesh_Cluster

Minutes later it goes to

Neighbor list
-------------
MAC                Portal             Channel  Age  Hops  Cost  Relation                 Flags  RSSI  Rate Tx/Rx  A-Req  A-Resp  A-Fail  HT-Details        Cluster ID
---                ------             -------  ---  ----  ----  -----------------        -----  ----  ----------  -----  ------  ------  ----------        ----------
xx:xx:xx:xx:3e:70  xx:xx:xx:xx:8c:91  64E      8    1     7.00  C 25s                    VZ     46    520/650     17     17      0       VHT-80MHzsgi-2ss  Mesh_Cluster
xx:xx:xx:xx:3e:71  xx:xx:xx:xx:8c:91  64E      0    1     7.00  N 22m:36s                VZ     41    -           0      0       0       VHT-80MHzsgi-2ss  Mesh_Cluster

Then goes to the below but still doesn't work

Neighbor list
-------------
MAC                Portal             Channel  Age  Hops  Cost  Relation                 Flags  RSSI  Rate Tx/Rx  A-Req  A-Resp  A-Fail  HT-Details        Cluster ID
---                ------             -------  ---  ----  ----  -----------------        -----  ----  ----------  -----  ------  ------  ----------        ----------
xx:xx:xx:xx:3e:70  xx:xx:xx:xx:8c:91  64E      10   1     7.00  C 16s                    VK     47    585/650     122    122     0       VHT-80MHzsgi-2ss  Mesh_Cluster
xx:xx:xx:xx:3e:71  xx:xx:xx:xx:8c:91  64E      0    1     7.00  N 2h:53m:44s             VK     43    -           0      0       0       VHT-80MHzsgi-2ss  Mesh_Cluster

A debug meshdlog against the Remote Mesh Portal shows

[1287]2018-10-26 11:29:44.618 meshd_update_neighbor: reachability changed to 1 for node xx:xx:xx:xx:3e:71.
[1287]2018-10-26 11:29:44.618 meshd_update_neighbor: nbr xx:xx:xx:xx:3e:70 new-mstate:0 should match 0
[1287]2018-10-26 11:29:48.626 meshd_update_neighbor: nbr xx:xx:xx:xx:3e:70 new-mstate:0 should match 0
[1287]2018-10-26 11:29:57.648 meshd_fill_neighbor_row: WARNING parent-bssid not found for child mac: xx:xx:xx:xx:3e:70, rssi unreliable.
[1287]2018-10-26 11:29:57.648 meshd_set_link_cost: Using forward RSSI for mac: xx:xx:xx:xx:3e:70, fwd-rssi: 44, rev-rssi: 0. (max_rssi: 38), link-cost(cH):0
[1287]2018-10-26 11:29:57.649 meshd_set_link_cost: Using forward RSSI for mac: xx:xx:xx:xx:3e:71, fwd-rssi: 40, rev-rssi: 0. (max_rssi: 38), link-cost(cH):0

[1287]2018-10-26 11:30:00.789 meshd_fill_neighbor_row: WARNING parent-bssid not found for child mac: xx:xx:xx:xx:3e:70, rssi unreliable.
[1287]2018-10-26 11:30:00.789 meshd_set_link_cost: Using forward RSSI for mac: xx:xx:xx:xx:3e:70, fwd-rssi: 44, rev-rssi: 0. (max_rssi: 38), link-cost(cH):0
[1287]2018-10-26 11:30:00.789 meshd_set_link_cost: Using forward RSSI for mac: xx:xx:xx:xx:3e:71, fwd-rssi: 42, rev-rssi: 0. (max_rssi: 38), link-cost(cH):0
[1287]2018-10-26 11:30:09.668 meshd_timer_handler: Aging out node xx:xx:xx:xx:3e:70
[1287]2018-10-26 11:30:09.668 meshd_clear_assoc_neighbor: mac: xx:xx:xx:xx:3e:70. called from meshd_timer_handler():925
[1287]2018-10-26 11:30:09.668 meshd_hostapd_send_event: DEL_STA xx:xx:xx:xx:3e:70 (len=25)
[1287]2018-10-26 11:30:09.669 meshd_hostapd_recv: recv-err:Success
[1287]2018-10-26 11:30:09.669 meshd_hostapd_send_event: reply=<OK
> expected 'OK'
[1287]2018-10-26 11:30:09.670 meshd_assoc_disconnect: xx:xx:xx:xx:8c:91 lost link to child xx:xx:xx:xx:3e:70
[1287]2018-10-26 11:30:09.670 meshd_clean_routing_tables: xx:xx:xx:xx:3e:70 to be removed
[1287]2018-10-26 11:30:09.670 meshd_clean_routing_tables: dev: aruba001. retval for ioctl is -1
[1287]2018-10-26 11:30:09.670 meshd_child_change: m->subtree_weight 1, subtree_delta -1

[1287]2018-10-26 11:30:09.670 meshd_adjust_subtree_weight: subtree_weight changed from 1 to 0
[1287]2018-10-26 11:30:09.671 meshd_lost_child: removed child xx:xx:xx:xx:3e:70, total: 0, branch-size: 0
[1287]2018-10-26 11:30:09.671 meshd_set_node_cost: set node-cost to 0, hop_count 0, child_wt: 0, algo: 0, portal_reachability 1
[1287]2018-10-26 11:30:09.672 meshd_binary_wif_sysctl: programmed /proc/sys/dev/wifi0/mesh_cmn_struct
[1287]2018-10-26 11:30:09.672 meshd_send_topology_update: chan:64, offs:4
[1287]2018-10-26 11:30:09.687 meshd_update_neighbor: reachability changed to 0 for node xx:xx:xx:xx:3e:71.

When i try run anything against the Mesh Point i get the error

Module MESH is busy. Please try later

The AP's are approximately 5 meters apart without any interfence

Hi

Did you find any solution?

My controllers are also at 8.3 and I have had a mesh link that has worked, but now it's down.

In gui, the Portal Access Point is listed under "mesh APs", but when I run "show ap mesh topology" no APs are listed.

When i run show ap mesh neighbors ap-name "ap-name"
I get this error message:
Module MESH is busy. Please try later

Regard

Hi,

No still haven't found a solution for this,

This sounds like the exact same issue i am facing,

Regards

Jason

What AP models and what specific build? I haven't done RMP in awhile but I can try it next week. For now, please open a TAC case as they can start looking at the debug logs to determine what might be going on.

Thank you Jerrod,

I am using AP205's for the mesh,

We are running version 8.3.0.3_66538

Regards

Jason

I will try to do a RMP next week and revert back, but for now you might open a TAC case to see if they have any history on this. I know of 1-2 RMP setups on AOS 8 (remote mesh portal is just not common), but they aren't having issues (I only know about them because I asked if they were still working heh). 

Hello,

Any news on this topic? I have similar case of losing mesh point (IAP 207) from time to time. Rarely recovers itself, but needs reboot of all APs.

Thanks

We also have a mesh point to point link that has been going up and down constantly since upgrading from 6.5 to 8.4. Strangely we have another mesh link which is pretty much identical that has survived the migration fine.

The only difference I can see (apart from having different mesh cluster profiles and a different uplink port config), is that the working mesh link has a WPA hexkey set and a WPA passphrase, whereas the non-working one just has a passphrase. This might be a complete red herring but it's all I can see that's different.

Ah - actually there is another difference - the inconsistent mesh is made up of 2 AP-277s, the working mesh is 2 AP-274s

AFAIK you should only set one or the other (HEX or PSK)

In the end we provisioned a new mesh point and replaced the existing one - it came straight up and has worked since. It would be interesting to know if (after blanking and reprovisioning) the old point would work again, I suspect it might and had just got itself in a funny state, but we won't be messing with the link now it is up and running again!