<p dir="ltr">There might be something that can be done with IEEE 802.1ag CFM, which you night be able to implement using a Ethernet demarcation device from someone like Adva, Metrodata etc.</p>
<p dir="ltr">I seem to remember one of our engineers talking about single member LAG for this.</p>
<p dir="ltr">Brocade MRP might also address this need.</p>
<p dir="ltr">Those are three ideas that could help.</p>
<div class="gmail_quote">On 21 Aug 2014 21:25, "Richard Laager" <<a href="mailto:rlaager@wiktel.com">rlaager@wiktel.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
A poster off-list suggested BFD.<br>
<br>
Can you clarify this a bit? I think you're looking at the problem<br>
backwards.<br>
<br>
+------+ /---------\ +-----+<br>
| MLXe | -- Network -- | CER |<br>
+------+ \---------/ +-----+<br>
| |<br>
+------+ +-----+<br>
| A | | B |<br>
+------+ +-----+<br>
<br>
When the "Network" fails, devices A & B (both of them) need to see their<br>
Ethernet links go down.<br>
<br>
If A & B supported BFD then I wouldn't need this link state propagation<br>
behavior at all. They're black boxes that, per the vendor, are meant to<br>
be directly connected.<br>
<br>
So what I need is for the MLXe and the CER to communicate in some way<br>
(MPLS / Ethernet OAM) and when that communication is interrupted, drop<br>
the Ethernet link on the ports facing the devices.<br>
<br>
My next best solution is that the vendor knows of some third-party<br>
devices that can do exactly this behavior. I'll go that route if I can't<br>
do it with the gear we already have.<br>
<br>
--<br>
Richard<br>
<br>_______________________________________________<br>
foundry-nsp mailing list<br>
<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br></blockquote></div>