04-15-2015 10:19 AM
I configure Wireless Mesh on the controller with basic settings
the mesh portal works well
the mesh point show the following error
asap_vap_gone:got vap gone notification on unknown VAP0:1
then it cannot be shown on the controller
04-15-2015 10:42 AM
Couple of things here,
1. Which AP model you are using for Portal and point ?
2. Do you have any other Mesh deployment nearby ?
Please clarify the above, we can fix the issue.
[Is my post helped you ? Give Kudos :) ]
04-15-2015 08:46 PM
I use AP-175 For both
There is no Mesh arround
i ask if the mesh point cannot find the portal
but it is direct connected to the controller
then it cannot see the controller or what is the right boot process
is there any debug commands to see why this Mesh cannot see the controller or cannot see the MESH Portal
10-13-2015 01:06 PM
I am having the same exact issue as the original message in this thread. I cannot get the mesh point to join the controller no matter what I do.
I am trying to setup a point to point configuration.
Please let me know if anyone has any sugestions. These are the error messages on the mesh point.
~ # [ 37.520896] wl0: set MESH_ID(Lamson Mesh, 11)
[ 37.952715] asap_vap_gone: Got vap gone notification on unknown vap:0:1
[ 39.105110] asap_vap_gone: Got vap gone notification on unknown vap:0:0
[ 39.196348] anul_get_max_amsdu_size(1631): WARN: AMSDU size is not explicitly configured
[ 40.174577] anul_get_max_amsdu_size(1631): WARN: AMSDU size is not explicitly configured
[ 40.271704] anul_get_max_amsdu_size(1631): WARN: AMSDU size is not explicitly configured
[ 40.371866] anul_get_max_amsdu_size(1631): WARN: AMSDU size is not explicitly configured
[ 40.468992] anul_get_max_amsdu_size(1631): WARN: AMSDU size is not explicitly configured
[ 364.601423] wl0: set MESH_ID(RecoveryH34dVd4AK+lLFSZW, 24)
[ 364.669977] anul_get_max_amsdu_size(1631): WARN: AMSDU size is not explicitly configured
[ 364.766895] anul_get_max_amsdu_size(1631): WARN: AMSDU size is not explicitly configured
10-13-2015 03:16 PM
Couple of questions:
* You are at at least AOS 6.4.3 or later?
* These were purged or new and when plugged in to the LAN, controller, came up and you provisioned them as mesh portal and point, and you provisioned these as 'outdoor' or 'auto'
* You haven't modified the AP groups allowed channels
You can ignore the AMSDU messages, until the mesh point is up
Sr. Techical Marketing Engineer
10-14-2015 07:52 AM
We are running 18.104.22.168
[ 97.857370] asap_vap_gone: Got vap gone notification on unknown vap:0:0
10-14-2015 08:32 AM
You might open a TAC case and they could help, the console logs can likely be ignored as they are common to see as a mesh point is coming up or down.
If you can, send me a show-tech at 'jhoward -at- arubanetworks -dot- com' and I can look at it. Common issues would be if the portal is on a channel the point can't run, but since they are both 277s, that seems unlikely.
Sr. Techical Marketing Engineer
10-14-2015 11:41 AM
Thank you Jerrod.
I got on the phone with TAC today and we were able to get the point connected to the portal AP. We had tried various things to try and bring the bridge connection up but there were 2 things that I made note of that seemed to make a diiference. Im not sure if these confiurations/steps should be nesccessary but at least the point seems to be working now.
In the Mesh Radio profile he changed the Reselction mode from startup-subthreshold to reselect-never. He mentioned that you would only do this in a point to point setup.
We had to reboot the AP using the command "apboot ap-name <ap-name>" from the contrller and the point AP would seem to start working after we would reboot this way. In the past I was rebooting the AP by basically removing the power/POE from the AP.
03-09-2016 12:23 AM
Sorry to step in your post, can I know did support told you the root cause of this?
I'm in the same situation with you as well now.