[j-nsp] Can the QFX5100 log LACP state changes?

[Karl Gerhard]

Hello

I need to check interfaces for LACP flaps on a QFX5100.
On an EX4550 and EX4300 it is very easy to do that. Every LACP state change would get logged and the syslog messages would look like this:
Nov 16 14:44:15  ex4550-test /kernel: %KERN-5-KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd xe-0/0/16 - DETACHED state - will not carry traffic
Nov 16 14:44:24  ex4550-test /kernel: %KERN-5-KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd xe-0/0/16 - ATTACHED state - acting as standby link
Nov 16 14:44:24  ex4550-test /kernel: %KERN-5-KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd xe-0/0/16 - CD state - ready to carry traffic

However, with QFX5100 I don't see those syslog entries any more. Best thing I can find when I disable an interface is this:
Nov 19 11:55:48 qfx5100-test /kernel: %KERN-7: lag_set_dcd_link_state: ifd=ge-0/0/36, ifd flags=0xc002
Nov 19 11:55:48 qfx5100-test /kernel: %KERN-7: lag_set_dcd_link_state: DCD Down received for ifd=ge-0/0/36

Unfortunately "ifd" refers to the physical interface that is being shut down, therefore I think the message when LACP flaps without the physical interface going up/down (an example for this would be packet loss) will look different (or there is none at all).

Does anyone know whether the QFX5100 logs LACP state changes at all or whether it is possible to configure that?

Regards
Karl
_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https://puck.nether.net/mailman/l

[Karl Gerhard]

Hello

thanks for the replies.
I received confimation that the messages appear just fine with 14.1X53-D40.8, so this seems to be just another Junos bug.

At least the following Junos versions are affected:
17.3R2
17.3R3-S1

Yes, this is the officially recommended version that's broken and no, there seems to be no mention of this in the release notes.

Regards
Karl

Post by Karl Gerhard
Hello
I need to check interfaces for LACP flaps on a QFX5100.
Nov 16 14:44:15  ex4550-test /kernel: %KERN-5-KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd xe-0/0/16 - DETACHED state - will not carry traffic
Nov 16 14:44:24  ex4550-test /kernel: %KERN-5-KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd xe-0/0/16 - ATTACHED state - acting as standby link
Nov 16 14:44:24  ex4550-test /kernel: %KERN-5-KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd xe-0/0/16 - CD state - ready to carry traffic
Nov 19 11:55:48 qfx5100-test /kernel: %KERN-7: lag_set_dcd_link_state: ifd=ge-0/0/36, ifd flags=0xc002
Nov 19 11:55:48 qfx5100-test /kernel: %KERN-7: lag_set_dcd_link_state: DCD Down received for ifd=ge-0/0/36
Unfortunately "ifd" refers to the physical interface that is being shut down, therefore I think the message when LACP flaps without the physical interface going up/down (an example for this would be packet loss) will look different (or there is none at all).
Does anyone know whether the QFX5100 logs LACP state changes at all or whether it is possible to configure that?
Regards
Karl
_______________________________________________
https://puck.nether.net/mailman/listinfo/juniper-nsp

_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net