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
------------------------------