This article outlines the procedure and troubleshooting steps for bringing up a mesh network in Aruba Instant 22.214.171.124-126.96.36.199 or above.
Feature Notes :
With Instant 188.8.131.52 release ::
extended-ssid is enabled by default hence mesh feature is disabled
If a customer has mesh feature working already and upgrades to this release; it wouldn't be affected.
Any factory-default Instant deployment running 184.108.40.206-220.127.116.11 where mesh has to be configured.
Network Topology :
Steps to configure Mesh in 4.1 release:
•Put all IAPs in a wired switch, make sure basic information has been synchronized.
•Configure a new SSID and delete factory default SSID
•Turn off ‘extended-ssid’ and reboot the IAP cluster;
• Move one of the IAP to the remote site, without wired uplink it will become mesh point.
If an AP model doesn't support mesh; then "mesh role" would be set to N/A in "show aps". Such APs shouldn't be used for Mesh deployment.
"show swarm state" can be used to confirm if factory-default ssid / extended-ssid config have been removed.
# show swarm state
AP Swarm State :swarm_config_sync_complete
mesh ldart State :suspending
Config in flash :yes
factory SSID in flash :no
extended-ssid configured :no
extended-ssid active :no
I got through all of the above (With the help of TAC) including IAP frimware upgrades to include the 215, 275, 315, 325 all to work together and support Mesh. I have an IAP/VC group managed with Airwave I would like to set the Mesh Point IAP to backhaul on 5.8 and allow/prefer client access on 2.4. How do I do this within Airwave? Can anyone point me in the right direction.
In our setup, we use the mesh technology to bridge the wired network to another building. This is working fine so far.
However, we face timeouts for the devices behind the Mesh point. One switch (directly connected to Mesh point) loses connection after some time and is not reachable until ARP is flashed or the switch is sending a Multicast package. (Ping to the switch, 45% of packets are lost). Port is configured to be trusted so I can assume that we dont have any issued with authentication to an access role profile.
A computer or notebook, which is communication all the time, does not show this behavior. It has connection all the time. Phones are loosing the connection as well.
Any ideas what is missing?
Enet 0 bridging should be enabled in-order to use AP wired port to extend wired network.
Please refer below article.
how can i used the wired link form the mesh point to extend the wired network.
I have the same issue with an IAP-325 on the latest firmware 18.104.22.168-4.3.0. Extended SSID is disabled by configuration but the IAP-325 still says "extended-ssid active:yes". Two other IAP-275 are fine (active: no"
So the IAP-325 also says "Mesh: N/A" in the VC while the IAPs-275 say both "Portal".
Any ideas? I understand the 325 should be working just fine with mesh as well?!
This was solved with an early access firmware (22.214.171.124-126.96.36.199). 188.8.131.52-4.1 (IAP-205) didn't support Meshing with 802.11ac.
I did it according this recommendation (incl. reboot) but "show swarm state" still shows "extended-ssid active:yes" and Mesh not working. Reboot didn't help.
Do I need to delete all existing SSIDs? Or is there another way?
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.