Wireless Access

Upcoming community maintenance Oct. 27th through Oct. 29th
For more info click here
Reply
Highlighted
New Contributor

AP 387 Bridge setup

Hello, 

 

I'm having a lot of trouble setting up a bridge mesh network. This is my first time configuring this kind of setup 

Short explanation: I'm trying to make a wireless bridge between two buildings across roads with two AP387 without a controller.

First thing I did was update the firmware to version 8.6.0.2, so far so good.

What I've noticed is that neither of both send out the default ssid.

 

I then connected the first AP to my Poe switch and it received an DHCP address correctly. 

I assigned a static IP to the device, deleted the existing ssid and created a new one as described in tutorials I found on this site.

I also modified the exesting default ethernet as described (trusted, all vlans)

When connecting my second AP to the same Switch it also received a Ip which I also made static.

I set the first AP as preferred master and after a while I can see both AP's showing up in the web gui.

When I look at the mesh tab I can see both and they are both Indicated as 'portal'.

 

The problem starts when I disconnect the second Ap, it just disappears from the web gui and it stays that way.

With or without eth bridge enabled. 

 

I also tried to follow the standalone manual but it is the same result.

Could someone please explain too me what I'm doing wrong. I supposed if I can see them both in the web gui in the mesh section that the second one would connect as mesh point. 

 

FYI: I don't have a console cable. 

Please help!

 

Highlighted
Frequent Contributor II

Re: AP 387 Bridge setup

Did you follow this guide? I recently did the same with some 377s, which should be the same config. Now I’m curious, I will try to pull my 387s out tomorrow and setup the same configuration. 

 

https://community.arubanetworks.com/t5/Controllerless-Networks/Configuring-AP-387-for-Point-to-Point-link/m-p/554115

 

 

Highlighted
Frequent Contributor II

Re: AP 387 Bridge setup

Here's a basic standalone bridge config with two 387s. I just pulled out most the default config. 

 

ALSO: Note that the default command "extended-ssid" is NOT in the configs. Disable extended-ssid for Mesh. 

 

 

mesh-portal# show ap mesh link

Neighbor list
-------------
MAC                Portal             Channel  Age  Hops  Cost  Relation                 Flags  RSSI  Rate Tx/Rx  A-Req  A-Resp  A-Fail  HT-Details        Cluster ID
---                ------             -------  ---  ----  ----  -----------------        -----  ----  ----------  -----  ------  ------  ----------        ----------
90:4c:81:82:3e:b1  90:4c:81:82:43:70  100      0    1     4.00  C 23m:18s                VLK    82    866/175     1      1       0       VHT-20MHzsgi-2ss  effdab42d7c3                    77d0c5a601d081938b3
90:4c:81:82:3e:01  -                  2        -    -     -     C                        AD     34    2310/2310   -      -       -       -                 effdab42d7c3                    77d0c5a601d081938b3

Total count: 2, Children: 1
Relation: P = Parent; C = Child; N = Neighbor; B = Blacklisted-neighbor
Flags: R = Recovery-mode; S = Sub-threshold link; D = Reselection backoff; F = Auth-failure; H = High Throughput; V = Very High Throughput, E= High efficient, L = Lega                    cy allowed
        K = Connected; U = Upgrading; G = Descendant-upgrading; Z = Config pending; Y = Assoc-resp/Auth pending
        a = SAE Accepted; b = SAE Blacklisted-neighbour; e = SAE Enabled; u = portal-unreachable; o = opensystem
        AD = 60g neighbor
mesh-portal# show ap-env

Antenna Type:Internal
Need USB field:No
name:mesh-portal
standalone_mode:1
uap_controller_less:1
mesh-cluster-name:P2PBRIDGE
mesh-cluster-key:f7ff47564c6dfcc7e0e9e2eb9f11af659c0ffd5da183ca66
mesh-point# show ap-env

Antenna Type:Internal
Need USB field:No
name:mesh-point
standalone_mode:1
enet0_bridging:1
uap_controller_less:1
mesh-cluster-name:P2PBRIDGE
mesh-cluster-key:2979ee4486ce229062dbd4ce47e25de3547315bf54e41d7f
mesh-portal# show running-config
version 8.6.0.0-8.6.0
virtual-controller-country US
virtual-controller-key 733e753001261d1cf1215941bf9a86eae372ecc7c64d6c29a4
name SetMeUp-C0:24:36
terminal-access
loginsession timeout 30
clock timezone none 00 00
rf-band all



wlan access-rule ethernet-trunk
 index 0
 rule any any match any any any permit


wlan access-rule UNUSED
 index 3
 rule any any match any any any deny

wlan ssid-profile UNUSED
 enable
 index 0
 type employee
 essid UNUSED
 wpa-passphrase e74e39df9331591f926ac50313d5429b1ba4b6988dd920659ed9b5d011fddb6d
 opmode wpa2-psk-aes
 max-authentication-failures 0
 vlan 999
 rf-band 2.4
 captive-portal disable
 hide-ssid
 dtim-period 1
 broadcast-filter arp
 dmo-channel-utilization-threshold 90
 local-probe-req-thresh 0
 max-clients-threshold 64



wired-port-profile ethernet-trunk
 switchport-mode trunk
 allowed-vlan all
 native-vlan 1
 trusted
 no shutdown
 access-rule-name ethernet-trunk
 speed auto
 duplex auto
 poe
 type employee
 auth-server InternalServer
 captive-portal disable
 no dot1x


enet0-port-profile ethernet-trunk
mesh-point# show running-config
version 8.6.0.0-8.6.0
virtual-controller-country US
virtual-controller-key 2deae28801431c9735ea55d2afc9a339ed34fb3a4beac9ed27
name SetMeUp-C0:23:EA
terminal-access
loginsession timeout 30
clock timezone none 00 00
rf-band all


wlan access-rule ethernet-trunk
 index 0
 rule any any match any any any permit

wlan access-rule UNUSED
 index 3
 rule any any match any any any deny

wlan ssid-profile UNUSED
 enable
 index 1
 type employee
 essid UNUSED
 wpa-passphrase 41330c3f6ca26ed869cacf7b8a5d0641efdf2fc71575412b51326f1011fee335
 opmode wpa2-psk-aes
 max-authentication-failures 0
 vlan 999
 rf-band 2.4
 captive-portal disable
 hide-ssid
 dtim-period 1
 broadcast-filter arp
 dmo-channel-utilization-threshold 90
 local-probe-req-thresh 0
 max-clients-threshold 64


wired-port-profile ethernet-trunk
 switchport-mode trunk
 allowed-vlan all
 native-vlan 1
 trusted
 no shutdown
 access-rule-name ethernet-trunk
 speed auto
 duplex auto
 poe
 type employee
 auth-server InternalServer
 captive-portal disable
 no dot1x


enet0-port-profile ethernet-trunk

 

 

Highlighted
New Contributor

Re: AP 387 Bridge setup

Hello ~ I have the Bridge Setup in Mesh Mode.  I have the Point unit plug into a switch and its not passing DHCP request to the Main unit... I am missing something?

 

Thanks

Bob

 

 

Highlighted
MVP Expert

Re: AP 387 Bridge setup

May help to start a new thread, and I'm not clear on the question. But if this doesn't coverit, start a new thread and I will try to keep an eye out. 

 

If you mean the mesh point is not getting an IP from the DHCP on the wired interface on the switch it's connected to, that is by design. A mesh point will derive it's AP from the defined uplink which in a mesh point's case would be the mesh uplink to the portal (otherwise if the point's IP via wired DHCP was different L2, the mesh link wouldn't work). 


Jerrod Howard
Distinguished Technologist, TME
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: