What does Actor Churn State and Partner Churn State means about an slave interface in /proc/net/bonding/bond0 and what are the possible values for it and what do they mean?
What does Actor Churn State and Partner Churn State means about an slave interface in /proc/net/bonding/bond0 and what are the possible values for it and what do they mean?
In order to setup Link Aggregation (LAG) each Ethernet link exchanges LACPDUs (Link Aggregation Control Protocol Data Units) with directly connected device that also implement LACP. [Summary] [Details]
The system is collecting information from the received PDUs on each participating link to find possible aggregations. If a received PDU changes the knowledge (LACP state information) about any of the links, this link will inform its peer about the changed state information. This goes on until there is a consensus about the role of each link in the aggregation. [LACP state information] [More details]
Churn in this context means the failure of a link to reach a consensus with its peer in a reasonable time.
Churn State shows if the Link is either waiting (monitoring) for additional PDUs to reach consensus, the result was a churn (churned) or the link is in sync (none).
Different Churn Count for Actor and Partner indicate that one end of the link was able to reach synchronous state and the other end did not.
However, the current IEEE 802.1AX-2014 standard which superseded 802.1ad removed the Churn machines from the protocol.
The Churn machines have been removed. They were a nice idea but don’t do much or work as originally intended. [details]