Environment- 11ac Mesh troubleshooting in AOS 6.4.3
Answer- The logs in mesh ap debug provides information about the potential parent node. Sample output as below:
[904]1969-12-31 16:00:38.711 meshd_scan_complete: selected potential parent 6c:f3:7f:7c:6d:31 in profile 0 on ch 161(offs=0), hop_count 1
[904]1969-12-31 16:00:38.711 meshd_overlay_ht: ldpc:1, 20-sgi:1, 40-sgi:0, mcs:ffffff00, src-mcs:ffffff00
[904]1969-12-31 16:00:38.711 meshd_overlay_vht vht aft overlay: ldpc:1, 80-sgi:0, 160-sgi:0, 160 allow:0, 8080 allow:0, txbf 1, mcs_map 0xffea
[904]1969-12-31 16:00:38.712 meshd_set_mvap_ht_props: ht->supported_mcs_set.bits: ffffff00
[904]1969-12-31 16:00:38.714 meshd_set_mvap_ht_props: Set VAP commit on node: /proc/sys/net/aruba000/commit
[904]1969-12-31 16:00:38.714 meshd_scan_complete: Using Active profile Meshtest_CopperShieldCage
[904]1969-12-31 16:00:38.714 meshd_scan_complete: candidates:3, profiles:16, recovery:FALSE, num_scans 1, disconnected-time: 12(secs)
[904]1969-12-31 16:00:39.202 meshd_connection_check: authentication pending to 6c:f3:7f:7c:6d:31!
[904]1969-12-31 16:00:39.202 meshd_initiate_sae: SAE disabled, just try associating
[904]1969-12-31 16:00:40.205 meshd_binary_wif_sysctl: programmed /proc/sys/dev/wifi0/mesh_cmn_struct
[904]1969-12-31 16:00:40.234 meshd_dfs_channel: check DFS for channel 161 result 0