Hi, all. A few months ago, I got really good guidance here to pursue OAM instead of trying to use BFD in unnatural ways. I've been reaching out to my vendors and through various searches, since the OAM space is wholly foreign to me, and I'm currently on four different paths:
* IEEE 802.1ag<https://www.ieee802.org/1/pages/802.1ag.html> now part of IEEE 802.1Q-2022 CFM * IEEE 802.3ah<https://www.ieee802.org/21/doctree/2006_Meeting_Docs/2006-11_meeting_docs/802.3ah-2004.pdf> Ethernet OAM (aka Link OAM) * ITU-T Y.1731<https://www.itu.int/rec/T-REC-Y.1731> OAM functions and mechanisms for Ethernet based networks * MEF 17<https://www.mef.net/resources/mef-17-service-oam-framework-and-requirements/> Service OAM Framework and Requirements One of my vendors pointed out to me that recent search guidance is probably a bit hard to find because this is mostly service provider space (not the enterprise space I live in), and they generally have solved for this in the past and moved on. So I feel like these are four hills I'm simultaneously trying to climb instead of knowing one or two better ones and focusing on those. I'm curious for the folks here that have in fact solved for OAM on your networks — particularly in an MX480/MX304 Junos environment (I also have a bunch of Cat 8K/9K IOS-XE and some NCS5500 IOS-XR, but let's focus on Junos) — which standard you went with. If you can also speak to why you chose that path, that would help a lot. Extra bonus points if you have some configuration that you can share (privately if you wish) that helps my decision process for craft/complexity. -dp _______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/[email protected]/message/LNAGB42MNXWRFOMXFH4WNI3LK3FH7UI5/
