I think it can be set via the GUI as well - but as I don't remember exact menu....
Original Message:
Sent: Apr 07, 2022 08:47 AM
From: Unknown User
Subject: Wireless Mesh 387 Boot interrupt
Thanks all for your assistance. I have successfully set the environment and followed the instructions per https://community.arubanetworks.com/community-home/digestviewer/viewthread?MID=30405#bm7e46ff41-0a17-4de1-809b-f1b3f669b04f
and
https://aventistech.com/kb/setup-aruba-outdoor-point-to-point-network/
but I cannot make the Mesh point a mesh points. It is a mesh portal. So the two AP's dont' connect. They see each other but don't connect. I am missing this command "AP-SITE# enet0-bridging
HavBridgeMesh (config) # enet-bridging
^
% Parse error
What is the command to enable bridging on the Mesh Point?
ON THE MESH POINT
Mesh cluster :Enabled
Mesh cluster name :HavPointToPoint
Mesh role :Mesh Portal
Mesh Split5G Band Range :full
Mesh mobility :Disabled
ON THE MESH PORTAL
HavBridgePortal# sh ap mesh cluster status
Mesh cluster :Enabled
Mesh cluster name :HavPointToPoint
Mesh role :Mesh Portal
Mesh Split5G Band Range :full
Mesh mobility :Disabled
Original Message:
Sent: Mar 28, 2022 06:44 AM
From: Bruce Osborne
Subject: Wireless Mesh 387 Boot interrupt
Thank you.
I was not aware of ap-env via ssh. I have been using ArubaOS since 3.x, shortly after the 802.11n Ap-225 was released.
------------------------------
Bruce Osborne ACCP ACMP
Liberty University
The views expressed here are my personal views and not those of my employer
Original Message:
Sent: Mar 28, 2022 05:55 AM
From: Jochem Knoben
Subject: Wireless Mesh 387 Boot interrupt
Hi Bruce,
if do define the env-vars via console - this is true.
if you do this via ssh and "ap-env" command - that's not necessary (even not possible).
if you type "ap-env ?" in the ssh-session you will get the help-info displayed: <env_name> string
so it is written boot resistent - though such changes only get active after a restart
BTW: using "ap-env" you can also define the per-ap setting of antenna-gain for "external antenna AP's" via ssh, of course you need to ssh to the AP-mgmt-IP (and not to the VC-IP) when doing so
------------------------------
Jochem Knoben
Original Message:
Sent: Mar 28, 2022 05:40 AM
From: Bruce Osborne
Subject: Wireless Mesh 387 Boot interrupt
You forgot the nilan & most important command
saveenv
Otherwise, I believe the changes will be lost when rebooting.
------------------------------
Bruce Osborne ACCP ACMP
Liberty University
The views expressed here are my personal views and not those of my employer
Original Message:
Sent: Mar 25, 2022 03:19 AM
From: Jochem Knoben
Subject: Wireless Mesh 387 Boot interrupt
For just adding these settings to the AP an telnet/ssh session will be sufficient.
just execute the following commands when logged in:
show ap-env -> just to view the current settings
ap-env standalone_mode 1
ap-env uap_controller_less 1
show ap-env -> you should see those values now in the list with your new settings
Of course - those settings get only active after a reboot then
------------------------------
Jochem Knoben
Original Message:
Sent: Mar 23, 2022 03:37 PM
From: Unknown User
Subject: Wireless Mesh 387 Boot interrupt
Hi - New to the Aruba 387 Wireless Mesh scene. I am trying to configure a new AP 387 wireless mesh. It is already hung on a building and would like to configure it correctly. Which I thought I did but failed. Another posting specifically (Airheads Community)
mentions that you can interrupt the boot process in the UI. How do I do that?
Power up AP387 and interrupt it in the "apboot" prompt to set the following.
//This can be done in the GUI, but will require multiple reboots
setenv standalone_mode 1
setenv uap_controller_less 1