Environment- 11ac mesh troubleshooting in 6.4.3
Answer- Post Scanning, identifying Portals, Calculating the potential parent, Point goes ahead and connects to the mesh portal.
Below is the mesh debug log which provides information about how the connecting stage goes through:
[904]1969-12-31 16:00:40.234 meshd_send_assoc_request: Sent assoc req to 6c:f3:7f:7c:6d:31. HT=1
[904]1969-12-31 16:00:40.266 Received assoc response from 6c:f3:7f:7c:6d:31
[904]1969-12-31 16:00:40.266 meshd_handle_assoc_resp: received assoc_resp from 6c:f3:7f:7c:6d:31 with status SUCCESS
[904]1969-12-31 16:00:40.266 meshd_write_lms_ip: MP set LMS to that of parent: 10.65.13.136
[904]1969-12-31 16:00:40.267 meshd_write_lms_ip: MP set master to LMS of parent: 10.65.13.136
[904]1969-12-31 16:00:40.267 meshd_set_rmp_mpv_to_asap: programmed mpv 0
[904]1969-12-31 16:00:40.267 meshd_handle_assoc_resp: success, turning off assoc_flag, lms 10.65.13.136
[904]1969-12-31 16:00:40.267 meshd_overlay_ht: ldpc:1, 20-sgi:1, 40-sgi:1, mcs:ffff0000, src-mcs:ffff0000
[904]1969-12-31 16:00:40.267 meshd_overlay_vht vht aft overlay: ldpc:1, 80-sgi:1, 160-sgi:0, 160 allow:0, 8080 allow:0, txbf 1, mcs_map 0xffea
[904]1969-12-31 16:00:40.267 meshd_set_mvap_ht_props: ht->supported_mcs_set.bits: ffff0000
[904]1969-12-31 16:00:40.270 meshd_set_mvap_ht_props: Set VAP commit on node: /proc/sys/net/aruba000/commit
[904]1969-12-31 16:00:40.270 meshd_handle_assoc_resp:969 set channel, chan: 161, offs: 0.
[904]1969-12-31 16:00:40.270 meshd_set_channel:189 change channel to 161/0
[904]1969-12-31 16:00:40.271 meshd_dfs_channel: check DFS for channel 161 result 0