Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

Determining the Mesh points that drops from Mesh parents due to weak mesh links

This thread has been viewed 2 times
  • 1.  Determining the Mesh points that drops from Mesh parents due to weak mesh links

    Posted Apr 13, 2017 04:57 AM

    Hi Experts,

     

    In my outdoor mesh network, there are few Mesh points that go to either unprovisioned list or gets dropped off : probably due to weak mesh link signal strength.

     

    Is there any means to know about the mesh point APs that are down through controller: in neighbor list .....?

     

     



  • 2.  RE: Determining the Mesh points that drops from Mesh parents due to weak mesh links

    Posted Apr 13, 2017 05:07 AM

    The method I generally follow is issuing "show ap arm neighbors <ap-names of APs which are nearby to the AP which is down> | include <mac address of the down AP>"
    Not sure if there other appropriate ways as well.

     



  • 3.  RE: Determining the Mesh points that drops from Mesh parents due to weak mesh links

    Posted Apr 13, 2017 05:13 AM
    Every mesh AP will still get an IP address. You can ping the IP address of each AP in the mesh to observe some latency. You can establish throughput by connecting to the mesh AP as a client and running a throughput test. You can see signal strength by doing a "show ap mesh topology" command and seeing the RSSI column:

    (ArubaM3) #show ap mesh topology

    Mesh Cluster Name: aruba-mesh
    -----------------------------
    Name Mesh Role Parent Path Cost Node Cost Link Cost Hop Count RSSI Rate Tx/Rx Last Update Uplink Age #Children
    ---- --------- ------ --------- --------- --------- --------- ---- ---------- ----------- ---------- ---------
    Bridge-CAP Portal (N) - 3 1 0 0 0 - 5m:54s 1d:3h:39m:10s 1
    MeshPoint Point Bridge-CAP 4 0 0 1 24 36/54 7m:5s 1d:3h:20m:17s 0

    Total APs :2
    (R): Recovery AP. (N): 11N Enabled. For Portals 'Uplink Age' equals uptime.


  • 4.  RE: Determining the Mesh points that drops from Mesh parents due to weak mesh links

    Posted Apr 16, 2017 02:42 AM

    Thank You.

    From the explaination appears that even if a Mesh point is dropped from a parent, it may still have an IP address.

    What is the threshold at which the Mesh point is caused to drop from a mesh link?

     

    The mesh topology in my network has too many APs with Tx/Rx not matching and the uplink age too appearing a cause of worry. Please comment.

     

    Mesh Cluster Name: mesh-clst-1
    -----------------------------------
    Name            Mesh Role   Parent             Path Cost  Node Cost  Link Cost  Hop Count  RSSI  Rate Tx/Rx  Last Update  Uplink Age       # Children
    ----            ---------   ------             ---------  ---------  ---------  ---------  ----  ----------  -----------  ----------       - --------
    B05-K7PO-T-AP2  Point (AC)  B-D9OB-T-AP1          1          2          0          1          29    12/86       2m:54s       3h:23m:55s       0
    B05-K7PO-T-AP3  Point (AC)  B-L60B-T-AP3          1          2          0          1          22    43/28       1m:11s       9h:42m:40s       0
    B05-K7PO-T-AP4  Point (AC)  B-L60B-T-AP2          1          2          0          1          33    173/173     1m:36s       6d:7h:19m:52s    0
    B05-K7PO-T-AP5  Point (AC)  B-D9OB-T-AP1          1          2          0          1          30    130/72      1m:9s        51m:57s          0
    B06-K8PO-T-AP1  Point (AC)  B-K9OB-T-AP1-UPDATED  1          2          0          1          22    43/65       8m:3s        2h:38m:34s       0
    B06-K8PO-T-AP2  Point (AC)  B-B6OB-T-AP1          1          2          0          1          32    12/12       3m:55s       23h:44m:2s       0
    B06-K8PO-T-AP4  Point (AC)  B-L60B-T-AP3          1          2          0          1          27    43/43       2m:23s       2d:23h:45m:19s   0
    B06-K8PO-T-AP5  Point (AC)  B-D9OB-T-AP1          1          2          0          1          28    57/86       7m:36s       48m:10s          0
    B07-K8PO-T-AP1  Point (AC)  B-K9OB-T-AP3-UPDATED  1          2          0          1          34    12/12       7m:28s       1h:58m:4s        0
    B07-K8PO-T-AP2  Point (AC)  B-B6OB-T-AP1          1          2          0          1          25    12/12       9m:10s       19m:38s          0
    B07-K8PO-T-AP3  Point (AC)  B-B6OB-T-AP1          1          2          0          1          22    43/43       4m:38s       20h:2m:56s       0
    B07-K8PO-T-AP4  Point (AC)  B-K9OB-T-AP3-UPDATED  1          2          0          1          30    86/57       4m:57s       6d:7h:20m:38s    0
    B07-K8PO-T-AP5  Point (AC)  B-K9OB-T-AP1-UPDATED  1          2          0          1          34    43/86       9m:24s       22h:31m:53s      0
    B08-K9PO-T-AP1  Point (AC)  B-K9OB-T-AP6-NEW      1          2          0          1          36    130/144     3m:56s       44m:21s          0
    B08-K9PO-T-AP2  Point (AC)  B-K9OB-T-AP6-NEW      1          2          0          1          27    65/12       3m:17s       53m:43s          0
    B08-K9PO-T-AP3  Point (AC)  B-K9OB-T-AP1-UPDATED  1          2          0          1          36    86/57       2m:13s       3d:23h:32m:9s    0