Wireless Access

See link below and see if you missed anything setting up the mesh. When set up the APs will be portals if they have a wired connection back to the network, or a point if it has to use the wireless for backhaul.

https://www.flomain.de/2018/08/aruba-instantap-mesh-iap-mesh/

I am not using IAPs, i'm on a Controller managed by a Conductor, so i do not know how applicable these settings are as i have no experience with IAPs.

Your link confirms the behavior i'm seeing for Instant APs, but all documentation i find for controller based APs just say to provision your APs as mesh point.

And my assumption would be that an AP that has explicitly been configured as a mesh point should come up faster than an AP set to mesh auto.

See link below and see if you missed anything setting up the mesh. When set up the APs will be portals if they have a wired connection back to the network, or a point if it has to use the wireless for backhaul.

https://www.flomain.de/2018/08/aruba-instantap-mesh-iap-mesh/

When you provision the AP as a mesh point you must remove any existing link to the network or the AP will not operate as a mesh point.

Provision, AP reboots, unplug AP.  Supply power to the AP without providing an Ethernet link (PoE injector without uplink or AC power) and the AP should come up as a point and mesh with one of the available portals.

I am not using IAPs, i'm on a Controller managed by a Conductor, so i do not know how applicable these settings are as i have no experience with IAPs.

Your link confirms the behavior i'm seeing for Instant APs, but all documentation i find for controller based APs just say to provision your APs as mesh point.

And my assumption would be that an AP that has explicitly been configured as a mesh point should come up faster than an AP set to mesh auto.

See link below and see if you missed anything setting up the mesh. When set up the APs will be portals if they have a wired connection back to the network, or a point if it has to use the wireless for backhaul.

https://www.flomain.de/2018/08/aruba-instantap-mesh-iap-mesh/

Yes, that works, when i provision the AP as "mesh auto".

If the AP has ethernet connectivity, it comes up as mesh portal, if it does not, it comes up as mesh point.

But coming up as mesh point takes a long time, at least 10 minutes, and looking at the LEDs, the AP seems to restart once.

My hope and expectation was to be able to configure an AP as a only a mesh point, resulting in a faster connection time.

The location where the point will be deployed is not powered all the time. Waiting 10 or more minutes for network connectivity every time will be difficult to sell to my users...

When you provision the AP as a mesh point you must remove any existing link to the network or the AP will not operate as a mesh point.

Provision, AP reboots, unplug AP.  Supply power to the AP without providing an Ethernet link (PoE injector without uplink or AC power) and the AP should come up as a point and mesh with one of the available portals.

I am not using IAPs, i'm on a Controller managed by a Conductor, so i do not know how applicable these settings are as i have no experience with IAPs.

Your link confirms the behavior i'm seeing for Instant APs, but all documentation i find for controller based APs just say to provision your APs as mesh point.

And my assumption would be that an AP that has explicitly been configured as a mesh point should come up faster than an AP set to mesh auto.

See link below and see if you missed anything setting up the mesh. When set up the APs will be portals if they have a wired connection back to the network, or a point if it has to use the wireless for backhaul.

https://www.flomain.de/2018/08/aruba-instantap-mesh-iap-mesh/

Dedicated mesh mode is always faster.

Auto process to determine point operation:

•  AP boots
• Detects an Ethernet connection and attempts DHCP
• Upon DHCP failure, mark as mesh point operation, AP reboot
• AP boots as mesh point
• AP searches for mesh portal

Configured as mesh point:

• AP boots as mesh point
• AP searches for mesh portal

Yes, that works, when i provision the AP as "mesh auto".

If the AP has ethernet connectivity, it comes up as mesh portal, if it does not, it comes up as mesh point.

But coming up as mesh point takes a long time, at least 10 minutes, and looking at the LEDs, the AP seems to restart once.

My hope and expectation was to be able to configure an AP as a only a mesh point, resulting in a faster connection time.

The location where the point will be deployed is not powered all the time. Waiting 10 or more minutes for network connectivity every time will be difficult to sell to my users...

When you provision the AP as a mesh point you must remove any existing link to the network or the AP will not operate as a mesh point.

Provision, AP reboots, unplug AP.  Supply power to the AP without providing an Ethernet link (PoE injector without uplink or AC power) and the AP should come up as a point and mesh with one of the available portals.

I am not using IAPs, i'm on a Controller managed by a Conductor, so i do not know how applicable these settings are as i have no experience with IAPs.

Your link confirms the behavior i'm seeing for Instant APs, but all documentation i find for controller based APs just say to provision your APs as mesh point.

And my assumption would be that an AP that has explicitly been configured as a mesh point should come up faster than an AP set to mesh auto.

See link below and see if you missed anything setting up the mesh. When set up the APs will be portals if they have a wired connection back to the network, or a point if it has to use the wireless for backhaul.

https://www.flomain.de/2018/08/aruba-instantap-mesh-iap-mesh/

Thanks for the confirmation, this is exactly what i expected.

Which brings me back to my original Issue: I cannot provision an AP as Mesh Point.

When i try, nothing happens. Even when i try to change another parameter of the AP, like the AP group, as long as i select mesh point, none of the changes are saved.

Seems like a case for TAC?

Dedicated mesh mode is always faster.

Auto process to determine point operation:

•  AP boots
• Detects an Ethernet connection and attempts DHCP
• Upon DHCP failure, mark as mesh point operation, AP reboot
• AP boots as mesh point
• AP searches for mesh portal

Configured as mesh point:

• AP boots as mesh point
• AP searches for mesh portal

Yes, that works, when i provision the AP as "mesh auto".

If the AP has ethernet connectivity, it comes up as mesh portal, if it does not, it comes up as mesh point.

But coming up as mesh point takes a long time, at least 10 minutes, and looking at the LEDs, the AP seems to restart once.

My hope and expectation was to be able to configure an AP as a only a mesh point, resulting in a faster connection time.

The location where the point will be deployed is not powered all the time. Waiting 10 or more minutes for network connectivity every time will be difficult to sell to my users...

When you provision the AP as a mesh point you must remove any existing link to the network or the AP will not operate as a mesh point.

Provision, AP reboots, unplug AP.  Supply power to the AP without providing an Ethernet link (PoE injector without uplink or AC power) and the AP should come up as a point and mesh with one of the available portals.

I am not using IAPs, i'm on a Controller managed by a Conductor, so i do not know how applicable these settings are as i have no experience with IAPs.

Your link confirms the behavior i'm seeing for Instant APs, but all documentation i find for controller based APs just say to provision your APs as mesh point.

And my assumption would be that an AP that has explicitly been configured as a mesh point should come up faster than an AP set to mesh auto.

See link below and see if you missed anything setting up the mesh. When set up the APs will be portals if they have a wired connection back to the network, or a point if it has to use the wireless for backhaul.

https://www.flomain.de/2018/08/aruba-instantap-mesh-iap-mesh/

Is the AP accepted by the controller (allowlisted) and licensed? Does it show up? Can you move it to the relevant AP group?

Thanks for the confirmation, this is exactly what i expected.

Which brings me back to my original Issue: I cannot provision an AP as Mesh Point.

When i try, nothing happens. Even when i try to change another parameter of the AP, like the AP group, as long as i select mesh point, none of the changes are saved.

Seems like a case for TAC?

Dedicated mesh mode is always faster.

Auto process to determine point operation:

•  AP boots
• Detects an Ethernet connection and attempts DHCP
• Upon DHCP failure, mark as mesh point operation, AP reboot
• AP boots as mesh point
• AP searches for mesh portal

Configured as mesh point:

• AP boots as mesh point
• AP searches for mesh portal

Yes, that works, when i provision the AP as "mesh auto".

If the AP has ethernet connectivity, it comes up as mesh portal, if it does not, it comes up as mesh point.

But coming up as mesh point takes a long time, at least 10 minutes, and looking at the LEDs, the AP seems to restart once.

My hope and expectation was to be able to configure an AP as a only a mesh point, resulting in a faster connection time.

The location where the point will be deployed is not powered all the time. Waiting 10 or more minutes for network connectivity every time will be difficult to sell to my users...

When you provision the AP as a mesh point you must remove any existing link to the network or the AP will not operate as a mesh point.

Provision, AP reboots, unplug AP.  Supply power to the AP without providing an Ethernet link (PoE injector without uplink or AC power) and the AP should come up as a point and mesh with one of the available portals.

I am not using IAPs, i'm on a Controller managed by a Conductor, so i do not know how applicable these settings are as i have no experience with IAPs.

Your link confirms the behavior i'm seeing for Instant APs, but all documentation i find for controller based APs just say to provision your APs as mesh point.

And my assumption would be that an AP that has explicitly been configured as a mesh point should come up faster than an AP set to mesh auto.

See link below and see if you missed anything setting up the mesh. When set up the APs will be portals if they have a wired connection back to the network, or a point if it has to use the wireless for backhaul.

https://www.flomain.de/2018/08/aruba-instantap-mesh-iap-mesh/

Yes, the AP is in the allowlist, is licensed and shows up fine and works once it is up.

I also can move it freely between AP groups, but only when i select "mesh auto". It comes up as mesh point and works when i set mesh auto, but it takes quite a while to do so.

Funny enough the GUI shows the AP with the radio button on "Mesh point". If i try to change the AP group then, it does not work: The change is not saved in the GUI and the AP also does not reboot. Once i set the selection to "Mesh auto" it works, just as with the initial configuration.

Is the AP accepted by the controller (allowlisted) and licensed? Does it show up? Can you move it to the relevant AP group?

Thanks for the confirmation, this is exactly what i expected.

Which brings me back to my original Issue: I cannot provision an AP as Mesh Point.

When i try, nothing happens. Even when i try to change another parameter of the AP, like the AP group, as long as i select mesh point, none of the changes are saved.

Seems like a case for TAC?

Dedicated mesh mode is always faster.

Auto process to determine point operation:

•  AP boots
• Detects an Ethernet connection and attempts DHCP
• Upon DHCP failure, mark as mesh point operation, AP reboot
• AP boots as mesh point
• AP searches for mesh portal

Configured as mesh point:

• AP boots as mesh point
• AP searches for mesh portal

Yes, that works, when i provision the AP as "mesh auto".

If the AP has ethernet connectivity, it comes up as mesh portal, if it does not, it comes up as mesh point.

But coming up as mesh point takes a long time, at least 10 minutes, and looking at the LEDs, the AP seems to restart once.

My hope and expectation was to be able to configure an AP as a only a mesh point, resulting in a faster connection time.

The location where the point will be deployed is not powered all the time. Waiting 10 or more minutes for network connectivity every time will be difficult to sell to my users...

When you provision the AP as a mesh point you must remove any existing link to the network or the AP will not operate as a mesh point.

Provision, AP reboots, unplug AP.  Supply power to the AP without providing an Ethernet link (PoE injector without uplink or AC power) and the AP should come up as a point and mesh with one of the available portals.

I am not using IAPs, i'm on a Controller managed by a Conductor, so i do not know how applicable these settings are as i have no experience with IAPs.

Your link confirms the behavior i'm seeing for Instant APs, but all documentation i find for controller based APs just say to provision your APs as mesh point.

And my assumption would be that an AP that has explicitly been configured as a mesh point should come up faster than an AP set to mesh auto.

See link below and see if you missed anything setting up the mesh. When set up the APs will be portals if they have a wired connection back to the network, or a point if it has to use the wireless for backhaul.

https://www.flomain.de/2018/08/aruba-instantap-mesh-iap-mesh/

We have seen another report of someone having this issue while running 8.10.0.9.  I tested the process on 8.10.0.9 and 8.11.2.1, starting from factory default APs I was able to successfully associate, provision, and connect an AP as a mesh portal and as a mesh point.

Yes, the AP is in the allowlist, is licensed and shows up fine and works once it is up.

I also can move it freely between AP groups, but only when i select "mesh auto". It comes up as mesh point and works when i set mesh auto, but it takes quite a while to do so.

Funny enough the GUI shows the AP with the radio button on "Mesh point". If i try to change the AP group then, it does not work: The change is not saved in the GUI and the AP also does not reboot. Once i set the selection to "Mesh auto" it works, just as with the initial configuration.

Is the AP accepted by the controller (allowlisted) and licensed? Does it show up? Can you move it to the relevant AP group?

Thanks for the confirmation, this is exactly what i expected.

Which brings me back to my original Issue: I cannot provision an AP as Mesh Point.

When i try, nothing happens. Even when i try to change another parameter of the AP, like the AP group, as long as i select mesh point, none of the changes are saved.

Seems like a case for TAC?

Dedicated mesh mode is always faster.

Auto process to determine point operation:

•  AP boots
• Detects an Ethernet connection and attempts DHCP
• Upon DHCP failure, mark as mesh point operation, AP reboot
• AP boots as mesh point
• AP searches for mesh portal

Configured as mesh point:

• AP boots as mesh point
• AP searches for mesh portal

Yes, that works, when i provision the AP as "mesh auto".

If the AP has ethernet connectivity, it comes up as mesh portal, if it does not, it comes up as mesh point.

But coming up as mesh point takes a long time, at least 10 minutes, and looking at the LEDs, the AP seems to restart once.

My hope and expectation was to be able to configure an AP as a only a mesh point, resulting in a faster connection time.

The location where the point will be deployed is not powered all the time. Waiting 10 or more minutes for network connectivity every time will be difficult to sell to my users...

When you provision the AP as a mesh point you must remove any existing link to the network or the AP will not operate as a mesh point.

Provision, AP reboots, unplug AP.  Supply power to the AP without providing an Ethernet link (PoE injector without uplink or AC power) and the AP should come up as a point and mesh with one of the available portals.

I am not using IAPs, i'm on a Controller managed by a Conductor, so i do not know how applicable these settings are as i have no experience with IAPs.

Your link confirms the behavior i'm seeing for Instant APs, but all documentation i find for controller based APs just say to provision your APs as mesh point.

And my assumption would be that an AP that has explicitly been configured as a mesh point should come up faster than an AP set to mesh auto.

See link below and see if you missed anything setting up the mesh. When set up the APs will be portals if they have a wired connection back to the network, or a point if it has to use the wireless for backhaul.

https://www.flomain.de/2018/08/aruba-instantap-mesh-iap-mesh/

Could this be related to the AP model? All my tests were done with an AP-515 (RW), and i don't think that acting as a mesh point is a common workload for these APs.

At the moment i do not have any other APs and i am waiting for the internal go ahead to order something with external antennas.

We have seen another report of someone having this issue while running 8.10.0.9.  I tested the process on 8.10.0.9 and 8.11.2.1, starting from factory default APs I was able to successfully associate, provision, and connect an AP as a mesh portal and as a mesh point.

Yes, the AP is in the allowlist, is licensed and shows up fine and works once it is up.

I also can move it freely between AP groups, but only when i select "mesh auto". It comes up as mesh point and works when i set mesh auto, but it takes quite a while to do so.

Funny enough the GUI shows the AP with the radio button on "Mesh point". If i try to change the AP group then, it does not work: The change is not saved in the GUI and the AP also does not reboot. Once i set the selection to "Mesh auto" it works, just as with the initial configuration.

Is the AP accepted by the controller (allowlisted) and licensed? Does it show up? Can you move it to the relevant AP group?

Thanks for the confirmation, this is exactly what i expected.

Which brings me back to my original Issue: I cannot provision an AP as Mesh Point.

When i try, nothing happens. Even when i try to change another parameter of the AP, like the AP group, as long as i select mesh point, none of the changes are saved.

Seems like a case for TAC?

Dedicated mesh mode is always faster.

Auto process to determine point operation:

•  AP boots
• Detects an Ethernet connection and attempts DHCP
• Upon DHCP failure, mark as mesh point operation, AP reboot
• AP boots as mesh point
• AP searches for mesh portal

Configured as mesh point:

• AP boots as mesh point
• AP searches for mesh portal

Yes, that works, when i provision the AP as "mesh auto".

If the AP has ethernet connectivity, it comes up as mesh portal, if it does not, it comes up as mesh point.

But coming up as mesh point takes a long time, at least 10 minutes, and looking at the LEDs, the AP seems to restart once.

My hope and expectation was to be able to configure an AP as a only a mesh point, resulting in a faster connection time.

The location where the point will be deployed is not powered all the time. Waiting 10 or more minutes for network connectivity every time will be difficult to sell to my users...

When you provision the AP as a mesh point you must remove any existing link to the network or the AP will not operate as a mesh point.

Provision, AP reboots, unplug AP.  Supply power to the AP without providing an Ethernet link (PoE injector without uplink or AC power) and the AP should come up as a point and mesh with one of the available portals.

I am not using IAPs, i'm on a Controller managed by a Conductor, so i do not know how applicable these settings are as i have no experience with IAPs.

Your link confirms the behavior i'm seeing for Instant APs, but all documentation i find for controller based APs just say to provision your APs as mesh point.

And my assumption would be that an AP that has explicitly been configured as a mesh point should come up faster than an AP set to mesh auto.

See link below and see if you missed anything setting up the mesh. When set up the APs will be portals if they have a wired connection back to the network, or a point if it has to use the wireless for backhaul.

https://www.flomain.de/2018/08/aruba-instantap-mesh-iap-mesh/