Hello, I am trying to establish a Mesh with the IAP-205-RWs. I have disabled the extended ssid and rebooted the Cluster which has 1 SSID so far. Unfortunately, the Mesh Role status is N/A and when I type "show ap mesh link" I receive this message "No mesh supported in current mode". Is Mesh supported on the IAP-205-RW ? Firmware: 18.104.22.168-22.214.171.124_54915
Could you please help me with this ?
You have the two IAPs. They were both brought up on the wired network to establish the cluster, and you saw both APs up in the GUI before configuring the mesh? One is on the network, where is the other one and how/what is it connected to?
Thanks for your reply. Yes I have wired the 2 IAPs to the network, saw them in the GUI as part of the cluster. The VC was properly set up and one SSID was configured. Then, disabled the extended ssid on the GUI and rebooted the IAPs. Removed the network connection from one of them, rebooted it and wait for the Mesh to establish, but it never came up. I noted that although Extended SSID is disabled, when you click on the Access Point the Mesh Role is N/A. I tried in the CLI typing no extended ssid and commit apply, but same result.I will reset both IAPs to factory default and start from scratch again. I let you know the result.Thanks again and have a great day.Best regards,
Please upgrade to Aruba Instant 4.2 or up to enable mesh on the 11ac access-points. From the Release Notes:
Starting with Instant 126.96.36.199-188.8.131.52 release, the 802.11ac IAPs, including IAP-22x, IAP-27x, IAP-21x, and IAP-20x support Mesh configuration.
I will upgrade the firmware as you say. Thanks a lot !!
I had problems getting a mesh working with IAP's and couldn't get it to work well until I used this AOS version.
FYI, if you intend using captive portal, This AOS version and those prior to this one use the revoke default certificate.
Thanks a lot for the information KrisS !!!
I will let you know when I upgrade the firmware.
@adebasa Were you successful in getting the mesh link established after starting over with your config?
Yes Jamie !!! The Mesh is working properly now. I just upgraded the firmware and bang, bang !! Solved.
Thank you and the others for being a great help !!
As you are probably aware, Initially both AP’s to be used in mesh link have to be wired and in the same subnet. Ensure the basic configuration has been synchronised.
From experience, In some versions of AOS the GUI displays extended SSID as disabled but it isn’t. If extended SSID is enabled then the mesh link will fail.
Check from the cli
Show swarm state
and if extended-ssid is shown as enabled use the cli command
When the config is sychronised remove the ethernet cable from the IAP being used for the far end (point) and reboot.
All IAP's should be running same code version
Thanks a lot for your reply. Well, I have done everything like that. I am planning to start from scratch and upgrading the firmware.
I will let you know about the result.
Thanks again and have a great day.
Just to thank you all for being so helpful. The problem solved once I upgraded the firmware to 184.108.40.206-220.127.116.11_57496
Thanks again and God bless !!!
PERFECT!!!! Glad to hear your good to go.
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 2020 Hewlett Packard Enterprise Development LPAll Rights Reserved.