Controllerless Networks

We have two IAP-134 access points. Both are wired and hence having a role of mesh portals.

How do I establish a wireless mesh link between them?

When I disconnect the wire from one of them, it becomes a mesh point and connects to the mesh portal through the air.

However, as soon as I put the Ethernet cable back, the AP becomes mesh portal again and breaks the wireless mesh link.

Thanks!

You need to provision one as a mesh Portal and one as a Mesh Point for this to work.

Thanks, that sounds logical. And that's what I'm trying to do, actually.

But there is no such configuration in GUI that will allow me to specify like OK, this baby is a mesh portal and this baby is a mesh point.

As I see now the mesh role is assigned automatically and depends on the Ethernet connectivity.

At the same time the CLI prompt gives me "Warning: configuration via CLI is not supported!" every time I try to configure the node.

So would you please give me a quick hint on how to "provision one as a mesh Portal and one as a Mesh Point".

The ArubaUS 6.1 User Guide here http://support.arubanetworks.com/DOCUMENTATION/tabid/77/DMXModule/512/Command/Core_Download/Default.aspx?EntryId=5926 in chapter 8 details how to create a mesh network.

There is a little configuration involved before you designate a device a mesh portal and mesh point and chapter 8 details this.

Thanks, reading the doc right now.

Last question, do I have to have a controller in addition to APs to deploy my described scenario?

Wait!  I made a mistake! You have IAPs.  You do NOT need a controller to do mesh.  Ignore that document.

Here is how you make the AP on the far end bridge that ethernet port:

Reboot that AP to make it work.

Sorry about that :(

No problem, my bad, I should have put better description :)

But now I don't have a "uplink" tab in my per-ap configuration menu.

I've looked everywhere, nothing related found.

Does it depend on firmware? Mine is:

ArubaOS (MODEL: 134), Version 6.1.3.1-3.0.0.1

Yes,

You need at least Version 6.1.3.1-3.1.x.x

Ahh, that's the root of a problem.

Thanks so much!

God give me patience as you have ;) 

Just a follow-up question.

I've made it run, the topology is as follows: two wired IAPs with a wireless link established between them. One IAP (remote) has bridging enabled.

However, when I try to send L2 traffic from an Ehternet segment attached to the first IAP to an Ethernet segment of a second IAP over the air, the traffic does not make it through. Though over-the-air ping from one IAP to another is OK.

Did I misconfigured something?

Would appreciate your help in solving this.

Eventually found a mistake.

So if you want to bridge wireless and wired interfaces on the remote AP make sure that you configure wired port as an access port. The default state is trunk (802.1q tagged).

To do so click the “Wired” tab, edit the “Wired networks” profile, and change the mode from trunk to access.

Here is the Knowledge Base article describing the steps.

https://kb.arubanetworks.com/app/answers/detail/a_id/1666

The link above appears to be broken - can you repost the correct one?

https://arubanetworkskb.secure.force.com/pkb/articles/HowTo/R-1666

I am setting up a simple test using two (2) IAPs.

1. I created a wlan (tested and working)

2. Added the second AP and waited for config/firmware sync

3. Set Eth0 to Bridge on the second AP and then rebooted.

4.  Move the AP 10 ft away and power up via POE injector

now the buck stops.  The AP is never seen by the master, the radio lights stay yellow and power light amber.

What am I missing?

Hi daddygrant

I´ve the same problem, I´ve set this up with an older firmware and it works, but now it doesn´t work with 6.4.0.

Habe anybody an idea what´s the problem?

Is this a bug?

Check under System -> Advanced Options to see if you have "Extended SSID" disabled.  This is required to enable Mesh.

Ok.  Mesh is up and running but I have one other question.  I only want to use the Meshed APs for wired access.  Is there a way to prevent wifi clients form connecting to them?

---

@Marcus wrote:

Check under System -> Advanced Options to see if you have "Extended SSID" disabled.  This is required to enable Mesh.

---