Re: delay the start of a service until LACP negotiation is complete
<quote who="Sven Hartge">
> John Ratliff <jratliff@bluemarble.net> wrote:
>
>> I have a 4 port LAGG (LACP / bond-mode 4) interface named bond0. It
>> seems
>> to take about 45 seconds after the links come up to negotiate with the
>> switch.
>
> This long delay is not normal. For me LACP-based bonds never take longer
> than 1 or at most 2 seconds to be operational.
>
> This smells of STP. Disable STP on the switch for that port or change to
> rSTP.
>
> Grü�e,
> Sven.
>
> --
> Sigmentation fault. Core dumped.
>
>
The ports are trunk ports carrying multiple vlans. I have enabled
spanning-tree portfast trunk on the port channel. It still takes around 5
seconds, but that's significantly faster. However, I have another slight
issue. When conntrackd is started on boot, it gives me some errors:
Aug 11 09:35:30 bltn-firewall-02 conntrackd[1157]: [Fri Aug 11 09:35:30
2017] (pid=1157) [notice] using user-space event filtering
Aug 11 09:35:30 bltn-firewall-02 conntrackd[1157]: [Fri Aug 11 09:35:30
2017] (pid=1157) [notice] netlink event socket buffer size has been set to
262142 bytes
Aug 11 09:35:30 bltn-firewall-02 conntrackd[1157]: [Fri Aug 11 09:35:30
2017] (pid=1157) [notice] initialization completed
Aug 11 09:35:30 bltn-firewall-02 conntrackd[1157]: [Fri Aug 11 09:35:30
2017] (pid=1157) [notice] -- starting in console mode --
Aug 11 09:35:30 bltn-firewall-02 conntrackd[1157]: [Fri Aug 11 09:35:30
2017] (pid=1157) [ERROR] no dedicated links available!
I don't get these errors if I run my delay script. I wonder if this is a
problem.
Thanks.
--John
Reply to: