LACP Partner/Actor churn
Posted: Wed May 26, 2021 10:03 am
Hello,
We have a WS-26-400-AC set with two ports as part of an LACP link. Traffic stopped flowing over the link and I found this in the peer's(Arista) logs.
I rebooted the WS-26-400-AC in order to get things back up and running before I looked at it's logs I don't have them to post here.
Thanks,
Richard
We have a WS-26-400-AC set with two ports as part of an LACP link. Traffic stopped flowing over the link and I found this in the peer's(Arista) logs.
- Code: Select all
May 23 12:33:23 localhost Lldp: %LLDP-5-NEIGHBOR_TIMEOUT: LLDP neighbor with chassisId 5064.d12a.d074 and portId "Port 25" timed out on interface Ethernet49
May 23 12:33:23 localhost Lldp: %LLDP-5-NEIGHBOR_TIMEOUT: LLDP neighbor with chassisId 5064.d12a.d074 and portId "Port 26" timed out on interface Ethernet51
May 23 12:42:00 localhost Lldp: %LLDP-5-NEIGHBOR_NEW: LLDP neighbor with chassisId 5064.d12a.d074 and portId "Port 25" added on interface Ethernet49
May 23 12:42:00 localhost Lldp: %LLDP-5-NEIGHBOR_NEW: LLDP neighbor with chassisId 5064.d12a.d074 and portId "Port 26" added on interface Ethernet51
May 23 12:44:00 localhost Lldp: %LLDP-5-NEIGHBOR_TIMEOUT: LLDP neighbor with chassisId 5064.d12a.d074 and portId "Port 25" timed out on interface Ethernet49
May 23 12:44:00 localhost Lldp: %LLDP-5-NEIGHBOR_TIMEOUT: LLDP neighbor with chassisId 5064.d12a.d074 and portId "Port 26" timed out on interface Ethernet51
May 23 12:45:02 localhost CROND[31510]: (root) CMD (/etc/cron.hourly/logrotate)
May 23 12:46:49 localhost Lldp: %LLDP-5-NEIGHBOR_NEW: LLDP neighbor with chassisId 5064.d12a.d074 and portId "Port 25" added on interface Ethernet49
May 23 12:46:49 localhost Lldp: %LLDP-5-NEIGHBOR_NEW: LLDP neighbor with chassisId 5064.d12a.d074 and portId "Port 26" added on interface Ethernet51
May 23 12:48:32 localhost Ebra: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet49, changed state to down
May 23 12:48:33 localhost Ebra: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet51, changed state to down
May 23 12:48:33 localhost Ebra: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-Channel1 (Link to PoE distribution switch), changed state to down
May 23 12:48:33 localhost Stp: %SPANTREE-6-INTERFACE_DEL: Interface Port-Channel1 has been removed from instance MST0
May 23 12:48:34 localhost Ebra: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet51, changed state to up
May 23 12:48:34 localhost Ebra: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet49, changed state to up
May 23 12:48:41 localhost Lldp: %LLDP-5-NEIGHBOR_NEW: LLDP neighbor with chassisId ec13.b202.5762 and portId "Port 25" added on interface Ethernet49
May 23 12:48:41 localhost Lldp: %LLDP-5-NEIGHBOR_NEW: LLDP neighbor with chassisId ec13.b202.5762 and portId "Port 26" added on interface Ethernet51
May 23 12:48:42 localhost Ebra: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-Channel1 (Link to PoE distribution switch), changed state to up
May 23 12:48:42 localhost Stp: %SPANTREE-6-LOOPGUARD_CONFIG_CHANGE: Loop guard enabled on port Port-Channel1.
May 23 12:48:42 localhost Stp: %SPANTREE-6-INTERFACE_ADD: Interface Port-Channel1 has been added to instance MST0
May 23 12:48:43 localhost Stp: %SPANTREE-6-MSTP_REGION_BORDER_CLEARED: MSTP region border cleared on Port-Channel1
May 23 12:48:43 localhost Stp: %SPANTREE-6-INTERFACE_STATE: Interface Port-Channel1 instance MST0 moving from discarding to learning
May 23 12:48:43 localhost Stp: %SPANTREE-6-INTERFACE_STATE: Interface Port-Channel1 instance MST0 moving from learning to forwarding
May 23 12:48:54 localhost Ebra: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet49, changed state to down
May 23 12:48:54 localhost Ebra: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet51, changed state to down
May 23 12:48:54 localhost Ebra: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-Channel1 (Link to PoE distribution switch), changed state to down
May 23 12:48:54 localhost Stp: %SPANTREE-6-INTERFACE_DEL: Interface Port-Channel1 has been removed from instance MST0
May 23 12:49:08 localhost Ebra: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet51, changed state to up
May 23 12:49:09 localhost Ebra: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet49, changed state to up
May 23 12:49:22 localhost Ebra: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet49, changed state to down
May 23 12:49:23 localhost Ebra: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet51, changed state to down
May 23 12:49:23 localhost Ebra: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet49, changed state to up
May 23 12:49:25 localhost Ebra: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet51, changed state to up
May 23 12:49:38 localhost Lldp: %LLDP-5-NEIGHBOR_NEW: LLDP neighbor with chassisId ec13.b202.5762 and portId "Port 25" added on interface Ethernet49
May 23 12:49:38 localhost Lldp: %LLDP-5-NEIGHBOR_NEW: LLDP neighbor with chassisId ec13.b202.5762 and portId "Port 26" added on interface Ethernet51
May 23 12:49:39 localhost Ebra: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-Channel1 (Link to PoE distribution switch), changed state to up
May 23 12:49:39 localhost Stp: %SPANTREE-6-LOOPGUARD_CONFIG_CHANGE: Loop guard enabled on port Port-Channel1.
May 23 12:49:39 localhost Stp: %SPANTREE-6-INTERFACE_ADD: Interface Port-Channel1 has been added to instance MST0
May 23 12:49:39 localhost Stp: %SPANTREE-6-MSTP_REGION_BORDER_CLEARED: MSTP region border cleared on Port-Channel1
May 23 12:49:39 localhost Stp: %SPANTREE-6-INTERFACE_STATE: Interface Port-Channel1 instance MST0 moving from discarding to learning
May 23 12:49:39 localhost Stp: %SPANTREE-6-INTERFACE_STATE: Interface Port-Channel1 instance MST0 moving from learning to forwarding
May 23 12:50:08 localhost Lldp: %LLDP-5-NEIGHBOR_NEW: LLDP neighbor with chassisId 0000.0000.d074 and portId "Port 25" added on interface Ethernet49
May 23 12:50:08 localhost Lldp: %LLDP-5-NEIGHBOR_NEW: LLDP neighbor with chassisId 0000.0000.d074 and portId "Port 26" added on interface Ethernet51
May 23 12:51:09 localhost Lldp: %LLDP-5-NEIGHBOR_NEW: LLDP neighbor with chassisId 0000.0000.0000 and portId "Port 25" added on interface Ethernet49
May 23 12:51:09 localhost Lldp: %LLDP-5-NEIGHBOR_NEW: LLDP neighbor with chassisId 0000.0000.0000 and portId "Port 26" added on interface Ethernet51
May 23 12:51:38 localhost Lldp: %LLDP-5-NEIGHBOR_TIMEOUT: LLDP neighbor with chassisId ec13.b202.5762 and portId "Port 25" timed out on interface Ethernet49
May 23 12:51:38 localhost Lldp: %LLDP-5-NEIGHBOR_TIMEOUT: LLDP neighbor with chassisId ec13.b202.5762 and portId "Port 26" timed out on interface Ethernet51
May 23 12:52:47 localhost Lag+LacpAgent: %LACP-4-PARTNER_CHURN: LACP Partner Churn Detected on Ethernet49
May 23 12:52:47 localhost Lag+LacpAgent: %LACP-4-PARTNER_CHURN: LACP Partner Churn Detected on Ethernet51
May 23 12:52:50 localhost Lag+LacpAgent: %LACP-4-ACTOR_CHURN: LACP Actor Churn Detected on Ethernet49
May 23 12:52:50 localhost Lag+LacpAgent: %LACP-4-ACTOR_CHURN: LACP Actor Churn Detected on Ethernet51
I rebooted the WS-26-400-AC in order to get things back up and running before I looked at it's logs I don't have them to post here.
Thanks,
Richard