Here's the whole thing
#####
AP-387 in InstantOS in Standalone Mesh Mode
In most all cases, the pair of AP-387s should be deployed in Standalone mode with mesh (new in 8.4). There are a number of reasons, but the main reason is this allows the APs to run independent of what rides across the links. Unlike a pair of APs running mesh with Instant in a VC where they must be L2 separated from other Instant APs, two AP-387s in Standalone Mesh mode will ignore L2 VC advertisements and run independently, allowing you to bridge an IAP VC over an AP-387 PtP.
Currently Standalone Mesh mode is mostly configured via the CLI only (there are currently no Standalone Mesh GUI elements in 8.4). The minimum commands to put the AP-387 in Standalone Mesh mode are as follows:
1. Interrupt AP boot and enter the following (note this can be done in the GUI but will require multiple reboots). This will allow the AP-387 to run in standalone mode and not look for a controller for firmware (basically forcing Standalone mode)
setenv standalone_mode 1
setenv uap_controller_less 1
2. Once the AP boots up, the following are entered in to the configuration of the AP-387
Set country and disable extended SSID
conf t
virtual-controller-country US
name <AP-Name>
no extended-ssid
exit
commit apply
Configure the clusterless mesh settings (these are written to AP ENV, not in 'config' mode)
no mesh-disable
mesh-cluster-name <cluster name, unique per PtP>
mesh-cluster-key <cluster-key>
commit apply
On the Mesh Point only:
wired-port-profile default_wired_port_profile
trusted
no shutdown
type employee
exit
enet0-bridging <== Note this is written into AP ENV with "enet0_bridging=1"
commit apply
NOTE: Once you apply 'enet0-bridging' on the mesh point, it will no longer come up on the wire. Additionally, if the point and portal are wired to the same VLAN/switch while the mesh is established and the mesh link is up with bridging on the mesh point, it will loop the network. So ensure after the point reboots, that it is removed from the same VLAN that the portal is connected to.
When this is completed, everything will need to be rebooted. Once done, the following commands will verify the standalone mesh role, and if the link is up
show ap mesh cluster status
show ap mesh link
show ap mesh neighbour
Please use the 'Aruba Instant 8.4.0.0 CLI Guide' for more details. The rest of the ethernet config for bridging follows the same rules/commands as the other Instant mesh bridging commands (access, trunk, etc).