<html><head></head><body>I concur:<br>
<br>
The people you want to have this conversation with are over on NANOG.<br><br><div class="gmail_quote">On November 21, 2017 11:51:44 AM EST, James Cornman <james@atlanticmetro.net> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr"><div>Thanks for moving. I was unaware of this list.<br /><br />In my opinion, this requirement is a bit extraneous, however the
downstream customer with this mandate is pretty passionate about this
configuration. That being said, the benefit is that if any peer has a preference for either one of our next hops (we cant control their route selection to ensure they do ECMP), we still get the upside of the extra capacity, as well as port level redundancy. I can't imagine having 1 more mac address in the exchange point's port-security criteria is overly complicated. That apparently is the biggest point of contention with Equinix thus far, since its "non standard". To note, we're not even requiring different chassis on the exchange point side; just want to take advantage of the MC LAG on our side so from the Equinix side, its pretty simple to make us go away :) <br /></div><div><br /></div><div>-James<br /></div><div><br /><br /></div></div><div class="gmail_extra"><br /><div class="gmail_quote">On Tue, Nov 21, 2017 at 11:38 AM, Hugo Slabbert <span dir="ltr"><<a href="mailto:hslabbert@demonware.net" target="_blank">hslabbert@demonware.net</a>></span> wrote:<br /><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Moved to outages-discussion.<br />
<br />
This seems like <a href="mailto:outages-discussion@outages.org" target="_blank">outages-discussion@outages.org</a> at best and likely more suited to nanog. I don't see anything related to an outage on this.<br />
<br />
On the surface, why not do discrete L3 links and equal-cost across the members rather than shoving L2 redundancy and complexity (MC-LAG) in the middle only to stuff L3 redundancy back over top of it (multiple IPs & discrete routing protocol sessions)?<br />
<br />
-- <br />
Hugo<br />
<br />
On Tue 2017-Nov-21 11:14:51 -0500, Chad Austin via Outages <<a href="mailto:outages@outages.org" target="_blank">outages@outages.org</a>> wrote:<br />
<br />
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Can you describe what the end result would look like?<br />
<br />
-Chad<br />
<br />
<br />
On 11/21/2017 11:11 AM, James Cornman via Outages wrote:<br />
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Anyone present with some contacts / influence with Equinix regarding their Exchange product?<br />
<br />
We're working to establish what they consider a unique situation thats not supported, and we're mostly getting told NO from the Equinix NOC w/o any escalation, and I'm looking to get someone with more technical expertise to talk to.<br />
<br />
We're looking to establish 2x10Gbps connections in an LACP LAG, with 2 IP addresses; 1 per MC LAG member, so we get the benefit of redundancy and capacity. Apparently the 2 IP address thing is the current show stopper. I haven't received any meaningful feedback as to whether this is a political problem or a technical one.<br />
<br />
FWIW, Other exchange points support this such as Any2 and NYIIX, etc.<br />
<br />
-James<br />
<br />
-- <br />
<br />
*James Cornman*<br />
<br />
/Chief Technology Officer<br />
/<a href="mailto:jcornman@atlanticmetro.net" target="_blank">jcornman@atlanticmetro.net</a> <mailto:<a href="mailto:jcornman@atlanticmetro.net" target="_blank">jcornman@atlanticmetro<wbr />.net</a>><br />
<a href="tel:212.792.9950" value="+12127929950" target="_blank">212.792.9950</a> - ext 101<br />
*<br />
Atlantic Metro Communications*<br />
<br />
/4 Century Drive, Parsippany NJ 07054/<br />
<br />
/<br />
//Cloud Hosting //• //Colocation • Network Connectivity • Managed Services/<br />
<br />
Follow us on Twitter: @atlanticmetro <<a href="https://twitter.com/atlanticmetro" rel="noreferrer" target="_blank">https://twitter.com/atlanticm<wbr />etro</a>> /• Like us on Facebook <<a href="https://www.facebook.com/atlanticmetro" rel="noreferrer" target="_blank">https://www.facebook.com/atla<wbr />nticmetro</a>>/<br />
<a href="http://www.atlanticmetro.net" rel="noreferrer" target="_blank">www.atlanticmetro.net</a> <<a href="https://www.atlanticmetro.net/" rel="noreferrer" target="_blank">https://www.atlanticmetro.net<wbr />/</a>><br />
<br />
<br />
<br />
______________________________<wbr />_________________<br />
Outages mailing list<br />
<a href="mailto:Outages@outages.org" target="_blank">Outages@outages.org</a><br />
<a href="https://puck.nether.net/mailman/listinfo/outages" rel="noreferrer" target="_blank">https://puck.nether.net/mailma<wbr />n/listinfo/outages</a><br />
</blockquote>
<br />
</blockquote>
<br />
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
______________________________<wbr />_________________<br />
Outages mailing list<br />
<a href="mailto:Outages@outages.org" target="_blank">Outages@outages.org</a><br />
<a href="https://puck.nether.net/mailman/listinfo/outages" rel="noreferrer" target="_blank">https://puck.nether.net/mailma<wbr />n/listinfo/outages</a><br />
</blockquote>
<br />
</blockquote></div><br /><br clear="all" /></div></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>