Wireless Access

last person joined: 2 hours ago 

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

Mesh Point Troubleshooting

  • 1.  Mesh Point Troubleshooting

    Posted Dec 03, 2020 11:13 AM
    Hello,

    Super simple setup here, but I'm stuck.

    Overall setup: 6 7240xm controllers, clustered.

    Two 515 CAPs, one portal and one point. Using default mesh cluster. Using one SSID, assigned to their own AP Group.

    I can get the portal up no problem, broadcasts the open SSID, I can connect to that fine. But when I bring the point up, it won't broadcast the SSID, and I cannot see it in the CLI under mesh topology. In the GUI it shows up, but oddly doesn't have a standby controller.

    I am able to get the point up both connected to ethernet and just a power brick, but eventually it falls off the network, like it can't talk to the portal. I've copied some of the console log of the point, and was curious if anyone can explain the last messages "Got MTU config but no tunnel to AAC yet". Maybe this is the issue?

    <<<<< Welcome to the Access Point >>>>>



    password: [ 36.576955] wl0: set MESH_ID(aruba-mesh, 10)

    [ 38.726984] Got MTU config but no tunnel to AAC yet

    [ 38.778350] asap_vap_gone: Got vap gone notification on unknown vap:0:1

    [ 39.868003] asap_vap_gone: Got vap gone notification on unknown vap:0:0

    [ 40.951300] Got MTU config but no tunnel to AAC yet

    [ 47.945924] random: nonblocking pool is initialized

    [ 74.008868] asap_firewall_forward: br0, insufficient headroom, require 84, but has 16, skb data length 60. mac header: dst mac FF:FF:FF:FF:FF:FF, src mac D0:D3:E0:C6:5C:C6, etype 2054

    [ 75.914850] asap_firewall_forward: br0, insufficient headroom, require 84, but has 16, skb data length 60. mac header: dst mac FF:FF:FF:FF:FF:FF, src mac D0:D3:E0:C6:5C:C6, etype 2054

    [ 78.126847] asap_firewall_forward: br0, insufficient headroom, require 84, but has 16, skb data length 60. mac header: dst mac FF:FF:FF:FF:FF:FF, src mac D0:D3:E0:C6:5C:C6, etype 2054

    [ 102.095050] Got MTU config but no tunnel to AAC yet



    Thanks for any help!

    ------------------------------
    Brian
    ------------------------------


  • 2.  RE: Mesh Point Troubleshooting

    Posted Dec 09, 2020 11:24 PM
    some thoughts...
    • See if the mesh point is getting an IP address from DHCP
    • Can you check if the point is coming in on a recovery profile ?
    • Please provide the full console log of the point from bootup time.



  • 3.  RE: Mesh Point Troubleshooting

    Posted Dec 10, 2020 12:35 PM
    An update. I had the point plugged into a switch when I abandoned it for the weekend. Monday I bounced the port just to verify it would at least come back up for a few minutes, and lo and behold it connects to the portal, and I have no explanation why.

    Now I can see it in "show ap database long", and can also connect a client to the point SSID. Bizarre.

    So, I can say I got it working, but unfortunately I cannot say why I got it working. Does the point need to be rebooted X amount of times before it establishes its link to the portal? I don't get it.

    ------------------------------
    Brian Simpson
    ------------------------------



  • 4.  RE: Mesh Point Troubleshooting

    Posted Dec 11, 2020 01:01 AM
    "Does the point need to be rebooted X amount of times before it establishes its link to the portal"
    no, that shouldn't be the case, only the reboot when you provision it to become a mesh point.


  • 5.  RE: Mesh Point Troubleshooting

    Posted Dec 23, 2020 10:14 PM

    One thing that often bites us is, when the point comes up, the wired mac of the point shows up on the uplink port the portal is plugged in to. If port security is enabled on the portal's switch port, that can prevent the point from communicating to the controller, even though the mesh link is 'up'. Not sure if that is what happened here, but it's a common issue that we see when new mesh links are brought up.



    ------------------------------
    Jerrod Howard
    ------------------------------