topic Re: Bridge two AP390's in Aerohive Migrated Content

Bridge two AP390's

rkowals — Sun, 16 Dec 2018 12:44:21 GMT

I'd like to know what is the best practice to bridge two AP390's for a bldg that isn't on any copper or fiber. Distance to each unit will be about 100 meters and will be connecting an outdoor wifi can on each end and connected to one of the 2.4 leads on each AP.

Re: Bridge two AP390's

samantha_lynn — Mon, 17 Dec 2018 22:38:34 GMT

Most importantly, we would need a clear line of site between the portal AP (the AP with a wired connection) and the remote AP (the AP without a wired connection).

It's best if we can get the APs on the same channel, same radio profiles, and same HiveOS version, or as close to the same as we can.

You would also want to eliminate as much competing traffic on the 2.4GHz band in the area as you can, as this band is more heavily used in general so it will experience more interference than 5GHz. We typically recommend using 5GHz when possible when meshing APs like this.

If you can let me know which HiveManager platform you are using, I can provide a guide for setting up a Mesh connection; HiveManager Classic (myhive.aerohive.com) or HiveManager (formerly NG, cloud.aerohive.com)?

Re: Bridge two AP390's

rkowals — Tue, 18 Dec 2018 03:16:19 GMT

HiveManager 2018-12-12, build 18.12.1.11

Re: Bridge two AP390's

samantha_lynn — Tue, 18 Dec 2018 03:35:25 GMT

Thank you for confirming that for me. This guide will walk you through how to set up Mesh in HiveManager- https://thehivecommunity.aerohive.com/s/article/Mesh-in-NG

Re: Bridge two AP390's

rkowals — Fri, 21 Dec 2018 05:44:12 GMT

Update: Since I just have the two AP390's, I used the default profile, I adjusted the configuration of the wireless interface for the following

wifi0 Radio off

wifi1 Radio On

5GHz

Channel 157

Transmission Power on

Client Transmission Power Auto

SSID set for a single policy profile

Radio set for Client Access and Backhaul Mesh

Both have same firmware

Still not connecting to each other, any idea?

Re: Bridge two AP390's

samantha_lynn — Fri, 21 Dec 2018 06:01:15 GMT

Could you SSH in to the Mesh APs and run "show hive"? This will show you your hive name (the one that isn't hive0), which we will need for the next command.

The second command is "show hive <hivename> neighbor". For example if the hive name was "Mesh_Test", the second command would be "show hive Mesh_Test neighbor".

Also I'd like to run "show amrp neighbor" to make sure we see a Two-way cost.

Re: Bridge two AP390's

rkowals — Fri, 21 Dec 2018 06:22:50 GMT

this is what I got from the online bridge:

HSW_Bridge01#show hive

Name N-vlan Frag RTS Mac filter

---- ------ ---- ---- ----------

hive0 1 2346 2346 None

VHM-WEQXZLME 1 2346 2346 VHM-WEQXZLME

HSW_Bridge01#show hive VHM-WEQXZLME neighbor

Chan=channel number; Pow=Power in dBm;

A-Mode=Authentication mode; Cipher=Encryption mode;

Conn-Time=Connected time; Hstate=Hive State;

Mac Addr Chan Tx Rate Rx Rate Pow(SNR) A-Mode Cipher Conn-Time Hstate Phymode Chan-width Hive

-------------- ---- ------- ------- -------- ---------- -------- --------- -------- ------- ---------- ----

Total neighbor count: 0

HSW_Bridge01#

Re: Bridge two AP390's

AnonymousM — Fri, 21 Dec 2018 23:27:53 GMT

Richard,

What is the far end AP390 plugged into? If it is a switch, the link will never come up as the AP is expecting to get DHCP over the link it senses on the ethernet port. You will need to pre-configure the eth0 port as a bridge-access or bridge-dot1q port first.

Likewise, if you have physical access to said switch (assuming it is a switch), you can also shut down that port (assuming it's a switch that will still deliver POE while shutdown). This will in turn move the "backhaul" over to RF. If you take this route, once the link comes up and you can fix the eth0 port via the GUI and an update, you can then re-enable said ethernet port.

A show acsp neighbor command might show you some information on far end device while the link is not up. Since the show hive <hivename> neighbor did not.

Re: Bridge two AP390's

rkowals — Sat, 22 Dec 2018 02:24:05 GMT

Both AP's are assigned a static IP, I had the remote AP plugged into a POE Unmanaged switch. I brought the AP back to the office, plugged the remote AP to an unmanaged switch with an POE Injector. I'm not seeing any reference to configure the Ethernet port as a bridge-access or bridge-dot1q port. It would be helpful if all this information was all in one KB instead of piecing it all together.

Should my remote AP be some distance from the Local Bridge, rather in the same room while I'm configuring the devices?

Re: Bridge two AP390's

samantha_lynn — Sat, 22 Dec 2018 03:36:49 GMT

The APs ports are in bridge-access when using the access port type. If you want the port to use bridge-dot1q, you would use the trunk ports settings in the device templates. If you are connecting to a switch, you would want to use a trunk or uplink port on the remote AP.

You should be able to test with the APs in the same room, and Mesh connections always need a clear line of site to each end of the connection. Are you seeing any neighbors when you run "show acsp neighbor"? If not, can you confirm all of the antennas are attached and assigned to the correct radio (2.4 or 5GHz)?

Re: Bridge two AP390's

rkowals — Thu, 17 Jan 2019 05:36:08 GMT

After replacing one of the AP390's, kept dropping profile, I was able to get the bridge connected within the office, now we will see if it work across campus. I'll keep you posted.

Re: Bridge two AP390's

rkowals — Mon, 18 Mar 2019 23:37:00 GMT

We have just started to roll out our new Aerohive switches, now I have some time to go back and start on the AP390 Bridge setup as well as getting a SR2208P connected to the remote AP, so other devices can attach to the Bridge.

AP390's are configured the same at this moment, Wifi0 Static IP, Cleient Access and Backhaul are enabled on channel 6. Eth0 and Eth1 are both set uplink, vlan1 , all vlans allowed.

SP2208P, ports 1-8 Access Ports, VLAN 2 voice, Vlan3 for Data. Ports 9,10 are Trunk native vlan 1 and vlan 2.3 allowed.

This is all still new to me, so talk to me like a 5th grader.

Re: Bridge two AP390's

samantha_lynn — Mon, 18 Mar 2019 23:57:33 GMT

I'm sorry, I'm not sure what your question is, could you clarify for me? And is the Mesh connection we worked on a couple months ago still working properly?

Re: Bridge two AP390's

rkowals — Tue, 19 Mar 2019 00:07:13 GMT

Same Mesh, it seemed to have been working, but once we rolled out the remote AP, it dropped. since then I have nit had the chance to see what changes have been made. everything else has been put on hold as we roll out the new aerohive switches that replace the old Cisco switches we have through the campuses. So, I'm back at square one.

Re: Bridge two AP390's

samantha_lynn — Tue, 19 Mar 2019 00:13:37 GMT

Thank you for letting me know. I think you would benefit most from opening a technical support case and setting up a call with one of our engineers. They can walk you through the entire set up process for Mesh, and answer any questions you have along the way. I'm happy to keep working with you over this thread if you'd like, but I don't think that would be the fastest path to a resolution for you and I can't be as hands on as an engineer could be with a case.