AP-387 is for 802.11ad 60Ghz Point to Point Solution.The AP-387's 5Ghz radio will not serve clients, it will only operate in Point to Point mesh mode.If you are doing controllerless networks, The pair of AP-387s should be deployed in Standalone mode with mesh.Two AP-387s in Standalone mode will ignore L2 VC advertisements and run independently, allowing you to bridge an IAP VC over an AP-387 Point to Point link.
How to configure AP-387 for Point to Point link:
Version Used: ArubaInstant_Hercules_220.127.116.11_71711
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 rebootssetenv standalone_mode 1setenv uap_controller_less 1
We are making the AP387 in standalone mode and telling it not to look for controller.
Set country code and disable extended SSIDvirtual-controller-country AUname <AP-Name>no extended-ssid
Configure the clusterless mesh settings. You don't need to goto "configure terminal" for this.no mesh-disablemesh-cluster-name <cluster-name>mesh-cluster-key <cluster-key>
The cluster name is unique per Point to Point link.
In the Mesh Point, make the ethernet port trusted and enable ethernet briding.
Enabling Ethernet Briding on Mesh Point.
AP Environment Variable and Values.
Mesh Portal AP-Env:
Mesh Point AP-Env:
show ap mesh link
show ap mesh neighbour
The 60Ghz radio has only three channels (1-3). Channel 2 will offer the highest performance for longer links.
Nice post. Only think I would add is that any current and future AP-387 PtP links should be upgraded to IAP 18.104.22.168 or later. there was a change to the radio balancing algorithm to prefer the 60Ghz link more heavily so that in the presence of high 5Ghz interference, the link performance is not as impacted due to 5Ghz interference.
Does anyone know if I can upgrade the 387's while they are in mesh portal/point roles, or do I have to go and pull down the mesh point and bring it back to the office, plug it into the network to upgrade it? In my two installations the mesh points are not easily accessable to bring down.
You should be able to do that while it is connected. If this is an Instant-based 387, the standard method of upgrading applies for an Instant cluster
Yes, it is instant based. Everytime I go into the cluster and do an upgrade it seems like only the mesh portal upgrades and the point doesn't. Does anyone know if there is an upgrade guide for instant point to point AP's?
What models are the rest of the APs? The AP-387 is Hercules class, so if your other APs are Hercules Class, it should upgrade with those, as well. If not, a multi-class cluster upgrade requires a external HTTP, ftp or tftp server to upgrade all pieces...
EDIT: What is your configuration?
version 22.214.171.124-8.4.0virtual-controller-country USvirtual-controller-keyname Robo-BN-Meshterminal-accessclock timezone none 00 00rf-band all
allow-new-apsallowed-ap 90:4c:81:c0:27:feallowed-ap 90:4c:81:c0:28:4c
armwide-bands 5ghz80mhz-supporta-channels 116Emin-tx-power 9max-tx-power 127band-steering-mode prefer-5ghzair-time-fairness-mode default-accesschannel-quality-aware-arm-disableclient-awarescanning
rf dot11g-radio-profilemax-distance 0max-tx-power 9min-tx-power 6disable-arm-wids-functions offfree-channel-index 40
rf dot11a-radio-profilemax-distance 0max-tx-power 18min-tx-power 12disable-arm-wids-functions off
syslog-level warn ap-debugsyslog-level warn networksyslog-level warn securitysyslog-level warn systemsyslog-level warn usersyslog-level warn user-debugsyslog-level warn wireless
wlan access-rule BRindex 0rule any any match any any any permit
wlan access-rule default_wired_port_profileindex 1rule any any match any any any permit
wlan access-rule wired-SetMeUpindex 2rule masterip 0.0.0.0 match tcp 80 80 permitrule masterip 0.0.0.0 match tcp 4343 4343 permitrule any any match udp 67 68 permitrule any any match udp 53 53 permit
wlan access-rule Wired-Trunk-Portindex 3rule any any match any any any permit
wlan ssid-profile BRenableindex 0type employeeessid BNRwpa-passphraseopmode wpa2-psk-aesmax-authentication-failures 0rf-band allcaptive-portal disabledtim-period 1broadcast-filter arpdmo-channel-utilization-threshold 90local-probe-req-thresh 0max-clients-threshold 64
enet-vlan 400auth-survivability cache-time-out 24
wlan external-captive-portalserver localhostport 80url "/"auth-text "Authenticated"auto-whitelist-disablehttps
blacklist-time 3600auth-failure-blacklist-time 3600
wired-port-profile wired-SetMeUpswitchport-mode accessallowed-vlan allnative-vlan guestno shutdownaccess-rule-name wired-SetMeUpspeed autoduplex autono poetype guestcaptive-portal disableno dot1x
wired-port-profile default_wired_port_profileswitchport-mode trunkallowed-vlan allnative-vlan 1shutdownaccess-rule-name default_wired_port_profilespeed autoduplex fullno poetype employeecaptive-portal disableno dot1x
wired-port-profile Wired-Trunk-Portswitchport-mode trunkallowed-vlan allnative-vlan 400no shutdownaccess-rule-name Wired-Trunk-Portspeed autoduplex autono poetype employeeauth-server InternalServercaptive-portal disableno dot1x
enet0-port-profile Wired-Trunk-Portenet1-port-profile Wired-Trunk-Port
uplinkpreemptionenforce nonefailover-internet-pkt-lost-cnt 10failover-internet-pkt-send-freq 30failover-vpn-timeout 180
airgroupservice airplaydisabledescription AirPlay
airgroupservice airprintdisabledescription AirPrint
"In the Mesh Point, make the ethernet port trusted and enable ethernet briding."
These settings only apply for the Mesh Point? Not for the Mesh Portal? Any additional configuration for the Mesh Portal?
FYI: I have the point-to-point link up and running
No additional config for Mesh Portal. Just ensure that the ap environment variables of Mesh Point and Mesh Portal matches the screenshot in the post.
Thx for your reply. I got it up and running smoothly. *thumbs_up*
Q: What will trigger the AP to move from Mesh Portal to Mesh Point except a manual reboot when in Standalone mode?
I'm trying to use this a backup link for a single fiber between two buildings.
During normal scenario the AP designated as Mesh Point will have Eth0 connectivity to it's gateway. During error situation (if fiber is disconnected) it will loose this connectivity, but switch link will be up. I think tho that it will only revert to Mesh Point if the physical switch-port goes down.
I have tried to simulate this by doing an interface disable (so that POE is still up), but in standalone mode the "Mesh Point" AP doesn't reboot and change to Mesh Point unless I manually do a "no power-over-ethernet". In cluster mode it will reboot after a few seconds and come up in Mesh Point mode.
It looks to me like I have to have manually disconnect/reconnect the "Mesh Point" to get the Mesh link up in case of fiber-disconnect..
Any tips for how to achieve what I want here without having to do this manual reconnect?
I think it's a matter of Spanning-Tree to get working properly.
the MeshPoint-AP must have the "ethernet-bridging" set - so it stays to be a meshpoint if the uplink is up.
Did you get it working as intended ?
I guess - it would be similar if you do have two P2P-links (one as a backup) and want to make use of shared L2 between the locations and not do any ECMP via the two P2P-links.
Did you try if STP is working via the P2P-link when using tagged management-vlan and untagged VLAN-1 on the mesh-ap-uplinks ?
Of course the stp-cost should be much higher compared to the fiber-link stp-costs, so the meshpoint-AP uplink is in stp-blocking during normal operation.
When I activate "Enabling Ethernet Brinding" on mesh point.
I lose the connection with the mesh point. I can't ping anymore the IP adress of the mesh point and I can't access on webadmin.
Can you help me for this problem ?
Thank you for your help,
I've had a few Mesh Points take up to 15 minutes to check in with the Mesh Portal. Just keep the Point aimed at the portal and powered up. It will probably reboot a few times until it finally checks in.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.