@DanielEbling wrote:
Hey,
i just want to give you a feedback: I have them up and running. We have found a document, where the controller based configuration is described and working. Steps i have taken:
- New AP Mesh group
- New Mesh cluster profile with wpa2-psk
- Under Configuration -> System -> Profiles -> RF Management -> 60GHz set to channel 2 (available 0 to 3). This is not under the AP Group profile but under the general System Profile. That was on of my errors, when i searched for the 60GHz settings.
- Configuration -> System -> Profiles -> AP -> AP System new wired AP Profile
- Configuration -> System -> Profiles -> AP -> AP wired port new wired port profile
- Configuration -> AP Groups -> Mesh add existing Cluster
- Configuration -> AP Groups -> Mesh -> Profiles assing created wired AP Profile to ETH0
- Then provisioned the APs into the AP group as mesh portal and point
The main problem was the 60GHz setting under Configuration -> System -> Profiles -> RF Management -> 60GHz, because this is empty per default.
Neighbor list
-------------
MAC Portal Channel Age Hops Cost Relation Flags RSSI Rate Tx/Rx A-Req A-Resp A-Fail HT-Details Cluster ID
--- ------ ------- --- ---- ---- ----------------- ----- ---- ---------- ----- ------ ------ ---------- ----------
90:4c:81:82:68:b0 Yes 132+ 0 0 8.00 P 7h:39m:25s VLK 26 360/243 1 1 0 VHT-40MHzsgi-2ss 387Mesh
90:4c:81:82:68:00 Yes 2 - - - P AD 34 3080/3080 - - - - 387Mesh
Looks like you are getting similar to me, i've set mine up in the sane way. Be warned, I read any changes to the mesh profile you will need to reload the controller
Looks like your 387 link is only using a 40Mhz proifile on 5Ghz.
My link establishes ok, however it seems to use 5Ghz (proven with spectum anayliser during iperf test). From my output the 60Ghz profile is never assigned so how can it ever use it?
TAC are still working on my case and its been escliated several times.
Will update with any info.
(aruba-mc-dev) #show ap mesh neighbors ap-name "ap-xxx387point-a01"
Neighbor list
-------------
MAC Portal Channel Age Hops Cost Relation Flags RSSI Rate Tx/Rx A-Req A-Resp A-Fail HT-Details Cluster ID
--- ------ ------- --- ---- ---- ----------------- ----- ---- ---------- ----- ------ ------ ---------- ----------
xx Yes 112E 0 0 3.00 P 36m:49s VLK 39 468/866 1 1 0 VHT-80MHzsgi-2ss aruba-mesh-test
xx Yes 2 - - - P AD 5 1540/1155 - - - - aruba-mesh-test
Total count: 2, Children: 0
Relation: P = Parent; C = Child; N = Neighbor; B = Blacklisted-neighbor
Flags: R = Recovery-mode; S = Sub-threshold link; D = Reselection backoff; F = Auth-failure; H = High Throughput; V = Very High Throughput, L = Legacy allowed
K = Connected; U = Upgrading; G = Descendant-upgrading; Z = Config pending; Y = Assoc-resp/Auth pending
a = SAE Accepted; b = SAE Blacklisted-neighbour; e = SAE Enabled; u = portal-unreachable; o = opensystem
(aruba-mc-dev) #
(aruba-mc-dev) #show ap mesh topology
Mesh Cluster Name: aruba-mesh-test
----------------------------------
Name Mesh Role Parent Path Cost Node Cost Link Cost Hop Count RSSI Rate Tx/Rx Last Update Uplink Age #Children
---- --------- ------ --------- --------- --------- --------- ---- ---------- ----------- ---------- ---------
ap-xxx387point-a01 Point (AC+AD) ap-xxx387portal-a01 3 0 2 1 62 866/866 8s 19s 0
ap-xxx387portal-a01 Portal (AC+AD) - 0 1 0 0 0 - 15s 2h:46m:22s 1
Total APs :2
(R): Recovery AP. (N): 11N Enabled. (AC): 11AC Enabled. For Portals 'Uplink Age' equals uptime.
(aruba-mc-dev)