This article outlines the procedure and troubleshooting steps for bringing up a mesh network in Aruba Instant 188.8.131.52-184.108.40.206 or above.
Feature Notes :
With Instant 220.127.116.11 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 18.104.22.168-22.214.171.124 where mesh has to be configured.
Network Topology :
Instant APs running 4.1 release
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.
"show aps" can be used to see the Mesh Role
On the point; "show uplink status" can be used to confirm the uplink in use is WiFi-Mesh.
"show log system" would show mesh uplink being used.
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
aruba000 is the interface used for mesh. We would see it in under show datapath bridge with M flag.
From Portal ::
From Point ::