Hi Sasha, thank you for sharing your concern. It is a very interesting scenario. I think that the root of it is how CE views its connections to PEs. Taking a different PoV, if it was not CCM but BFD, I'd not expect RFC 7130 uBFD <https://datatracker.ietf.org/doc/html/rfc7130> perform better. I think that CE should treat its connections to PEs as MC-LAG, not a single LAG. For CFM that means that CE should run CCM to each PE. As for BFD, we had a proposal for MC-LAG scenario <https://www.ietf.org/archive/id/draft-mtm-rtgwg-bfd-mc-lag-05.txt>, but it expired. If you find that idea interesting, I'd be glad to discuss it with you.
Regards, Greg On Tue, Dec 23, 2025 at 12:31 AM Alexander Vainshtein <Alexander.Vainshtein= [email protected]> wrote: > Hi all, > > I have serious concerns about applicability of Ethernet CFM mechanisms > defined in IEEE 802.1ag and ITU-T Y.1731 to EVPN services that include > attachment circuits on multi-homed Ethernet Segments, especially if these > Ethernet Segments operate in All-Active redundancy mode. > > > > E.g., suppose that a given customer site is connected to multiple EVPN PEs > via a MH ES operating in All-Active redundancy mode. > > Suppose further that a DOWN MEPs at the service level are configured on > the CE and all these PEs. > > > > Since the CE treats the group of links connecting it to all the EVPN PEs > as a single LAG, it will send all its CCM messages via just one of the > links connecting it to the EVPN PEs, so hat the rest of the PEs will report > lost of connectivity with the CE. Is this the expected behavior? > > > > Your timely feedback would be highly appreciated. > > > > Regards, > > Sasha > > > > > *Disclaimer* > > This e-mail together with any attachments may contain information of > Ribbon Communications Inc. and its Affiliates that is confidential and/or > proprietary for the sole use of the intended recipient. Any review, > disclosure, reliance or distribution by others or forwarding without > express permission is strictly prohibited. If you are not the intended > recipient, please notify the sender immediately and then delete all copies, > including any attachments. > _______________________________________________ > BESS mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
