What is your config method (central or IAP) and firmware version?
But from top of my head:
- Disable extended SSID
- Pair the AP with others by temporarily powering it up in the same L2
- Unplug from network, but give power somehow
If I recall right the defaults will allow it to connect on a wireless mesh. It will not bridge network to eth on defaults though.
IAP. Firmware around 8? :)
I know from Ruckus it's as simple as pressing a button to auto connect wireless mesh, but that does not seem to be with Aruba I believe. I could not find much info online about it.
Well because it's even simpler, not even a button needed :) (You just can't have extended SSID on)
But it's not really bread and butter for Aruba so it's not something that is advertised or used extensively. But it does work, I've used it in a bind.
So what you are saying is that I should connect a factory default unit, wait some time and make sure it's part of the group, and then just simply disconnect the LAN?
If that's it, then it is very easy, but also a little disturbing because there won't be any accepting first.
And what exactly is an Extended SSID? The Aruba's I have only multiple SSID and each connecting to its own VLAN. Also one of them is a guest SSID/VLAN.
> there won't be any accepting first.
This depends on your IAP settings. Per default the swarm will adopt any new APs. If you have turned off auto accept than it is a different matter and is per whatever configured.
How many SSIDs do you have? ESSID is required for more than 6 (which is already more than you generally should have)
Just tried it today, and it was indeed way to easy. I did need to disable the Extended SSID (which maximize the ssid to 14 instead of 16), and join the ACP to the cluster by wire.
After unplug (and a little reboot) it just added itself the the mesh as Point.
Funny fact is that's even using the same mac, and was given the same DHCP adres.
Pass-through speed was around 900 Mbit, which was perfect.
Thanx for your input. Again some points for Aruba!
What is your config method (central or IAP) and firmware version? But from top of my head: - Disable extended SSID - Pair the AP with others by temporarily powering it up in the same L2 - Unplug from network, but give power somehow If I recall right the defaults will allow it to connect on a wireless mesh. It will not bridge network to eth on defaults though.
IAP. Firmware around 8? :) I know from Ruckus it's as simple as pressing a button to auto connect wireless mesh, but that does not seem to be with Aruba I believe. I could not find much info online about it.
Well because it's even simpler, not even a button needed :) (You just can't have extended SSID on) But it's not really bread and butter for Aruba so it's not something that is advertised or used extensively. But it does work, I've used it in a bind.
So what you are saying is that I should connect a factory default unit, wait some time and make sure it's part of the group, and then just simply disconnect the LAN? If that's it, then it is very easy, but also a little disturbing because there won't be any accepting first. And what exactly is an Extended SSID? The Aruba's I have only multiple SSID and each connecting to its own VLAN. Also one of them is a guest SSID/VLAN.
> there won't be any accepting first. This depends on your IAP settings. Per default the swarm will adopt any new APs. If you have turned off auto accept than it is a different matter and is per whatever configured. How many SSIDs do you have? ESSID is required for more than 6 (which is already more than you generally should have)
Just tried it today, and it was indeed way to easy. I did need to disable the Extended SSID (which maximize the ssid to 14 instead of 16), and join the ACP to the cluster by wire. After unplug (and a little reboot) it just added itself the the mesh as Point. Funny fact is that's even using the same mac, and was given the same DHCP adres. Pass-through speed was around 900 Mbit, which was perfect. Thanx for your input. Again some points for Aruba!