BillSchumacher
BillSchumacher
A possible fix would be to add a kernel option to specify interfaces that should be bonded. Which would allow for proper LACP negotiation on startup and avoid the LACP...
Some more details, I think that it thinks that the interface gained IPv6 connectivity when it did not. [ 2.373696] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready It's around this...
I suppose a custom oem would probably also solve this, should have scrolled to the bottom before spending hours troubleshooting this.
Custom OEM is the way to go if you're having this issue as well. This should probably still be addressed and/or the documentation should be updated.
It is timing out fetching the initial config.
90 seconds would be sufficient, 120 would definitely fix it. It takes 30 seconds for LACP to timeout, spanning tree hello and forwarding takes around 17 seconds without port fast...
I'll time the Intel pxe boot agent to see what it uses, they probably have it figured out pretty good.
They are using ~73 seconds, probably 75.
With port-fast it I get an IP at ~62 seconds and without ~72 seconds, the Intel agent always works though so maybe 75 is the magic number.
localhost didn't work for me, I use an https:// enabled domain.