Wireless Access

After configuring a few dozen AP335 as remote APs I've now had 3 times that a RAP would no longer boot from its ENET0.

Powercycling a RAP (physically unplugging the cable) that is stuck like that does not help resolve the issue.

Interrupting the APboot and triggering DHCP several times does not work (or help) either.

apboot> dhcp
eth0: No link.
eth1 Waiting for PHY auto negotiation to complete......... TIMEOUT !
eth1: No link.
apboot> dhcp
eth0: No link.
eth1 Waiting for PHY auto negotiation to complete......... TIMEOUT !
eth1: No link.
apboot> dhcp
eth0: No link.
eth1 Waiting for PHY auto negotiation to complete......... TIMEOUT !
eth1: No link.

Also letting the entire boot run its course does not help.

Aruba watchdog daemon started [1 thread(s)]
LLDP not sent yet, DHCP is waiting
net.ipv4.conf.all.arp_notify = 1
Getting an IP address...
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!
Not LACP mode, adding 30 seconds updelay!

The fix for now has always been to boot once from ENET1, this has always resolved the issue.

Aruba watchdog daemon started [1 thread(s)]
Starting DHCP
net.ipv4.conf.all.arp_notify = 1
Getting an IP address...
Not LACP mode, adding 30 seconds updelay!
[   39.122527] asap_firewall_forward: br0, insufficient headroom, require 68, but has 16, skb data length 60. mac header: dst mac FF:FF:FF:FF:FF:FF, src mac 20:A6:CD:CF:50:A4, etype 2054
Not LACP mode, adding 30 seconds updelay!
[   41.325524] asap_firewall_forward: br0, insufficient headroom, require 68, but has 16, skb data length 60. mac header: dst mac FF:FF:FF:FF:FF:FF, src mac 20:A6:CD:CF:50:A4, etype 2054
Not LACP mode, adding 30 seconds updelay!
[   43.332519] asap_firewall_forward: br0, insufficient headroom, require 68, but has 16, skb data length 60. mac header: dst mac FF:FF:FF:FF:FF:FF, src mac 20:A6:CD:CF:50:A4, etype 2054
Not LACP mode, adding 30 seconds updelay!
net.ipv4.conf.all.arp_notify = 0
net.ipv4.conf.br0.arp_notify = 1
192.168.50.12 255.255.255.0 192.168.50.1
Running ADP...Done. Master is <our master>

After having booted from ENET1, now also ENET0 works again.

Aruba watchdog daemon started [1 thread(s)]
Starting DHCP
net.ipv4.conf.all.arp_notify = 1
Getting an IP address...
Not LACP mode, adding 30 seconds updelay!
[   39.122527] asap_firewall_forward: br0, insufficient headroom, require 68, but has 16, skb data length 60. mac header: dst mac FF:FF:FF:FF:FF:FF, src mac 20:A6:CD:CF:50:A4, etype 2054
Not LACP mode, adding 30 seconds updelay!
[   41.325524] asap_firewall_forward: br0, insufficient headroom, require 68, but has 16, skb data length 60. mac header: dst mac FF:FF:FF:FF:FF:FF, src mac 20:A6:CD:CF:50:A4, etype 2054
Not LACP mode, adding 30 seconds updelay!
[   43.332519] asap_firewall_forward: br0, insufficient headroom, require 68, but has 16, skb data length 60. mac header: dst mac FF:FF:FF:FF:FF:FF, src mac 20:A6:CD:CF:50:A4, etype 2054
Not LACP mode, adding 30 seconds updelay!
net.ipv4.conf.all.arp_notify = 0
net.ipv4.conf.br0.arp_notify = 1
192.168.50.12 255.255.255.0 192.168.50.1
Running ADP...Done. Master is ...

Problem is, these APs are to be installed where we can not easily unplug/replug those APs. I'd also rather not simply use ENET1 as in future models/deployement ENET1 might not be usuable to draw POE power from. Ans besides from that, I a not confident this issue is limited to ENET0 only.

Anybody got an idea what is going wrong here?  What could trigger an AP to pull down an interface across powercycles?

hi Koen

these messages

[   39.122527] asap_firewall_forward: br0, insufficient headroom, require 68, but has 16, skb data length 60. mac header: dst mac FF:FF:FF:FF:FF:FF, src mac 20:A6:CD:CF:50:A4, etype 2054

are always bad (and are a bug) - what s/w version are you on and whats the rap topology (split tun, bridge etc.)

8.4.0.0 with all tunneled, although I doubt that matters much since my issue is even getting the AP up at all.

Any info on what headroom warning is actually about?

@koen wrote:

8.4.0.0 with all tunneled, although I doubt that matters much since my issue is even getting the AP up at all.

Any info on what headroom warning is actually about?

---

the headroom message is a low level bug in packet assembly, it should not be happening - please raise a ticket on it. 

I installed 8.4.0.0 and have this message too on a IAP-305 converted into RAP (right after conversion).

But don't know if it implies issue for the AP as I'm troubleshooting something else.

Did anoyone find a solution to this? I too am reciving these error messages right after converting an AP to a Remote. 

Running 8.4.0.1

Thanks.