<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Dear IXP manager specialists,<div class=""><br class=""></div><div class="">As we mentioned here and there, LU-CIX is working on a migration project to take our in-house MemberDB to IXP Manager.</div><div class=""><br class=""></div><div class="">A first “issue” we have and where I’m asking for your guidance, is how to cover remote members. I assumed this would be something very common among IXPs, but thinking about it, maybe not. Let me explain.</div><div class=""><br class=""></div><div class="">Since many, many years LU-CIX operates remote connections to neighbouring IXPs. In the simplest form, this is just a very long L2 link taking our own peering VLAN to the remote IX’s infrastructure. Remote members get assigned our own peering VLAN on their port on the remote IX, and thus become “remote members” of our own IX. The same is done in the other direction for local members contracting the remote IX service.</div><div class=""><br class=""></div><div class="">On both exchanges, the remote connection takes the form of an L2 port, typically a LAG, behind which we find multiple members and thus multiple MACs.</div><div class=""><br class=""></div><div class="">In a more advanced setup, there would be one physical port (single or LAG), on which arrive n number of VLANs from the remote IX, one per local member that is connected to the remote IX. This VLAN then gets assigned to the member contracting the remote IX service. If we provide our own peering service to members on that remote IX, we need to connect a dedicated remote member VLAN arriving on the same physical port, into our peering VLAN.</div><div class=""><br class=""></div><div class="">In no case do we have dedicated physical switch ports for such remote members.</div><div class=""><br class=""></div><div class="">What’s the best approach to enter this setup in the IXP manager data model?</div><div class=""><br class=""></div><div class="">I have looked at reseller functionality, which might help, but I’m not quite sure it will cut it. Notably, we don’t have a fanout switch in our setup.</div><div class=""><br class=""></div><div class="">Ideas?</div><div class=""><br class=""></div><div class="">Thanks and enjoy the weekend</div><div class=""><br class=""></div><div class="">Michel<br class=""><div class="">
<br class="">
<span style="font-size: 10pt; font-family: 'tahoma' , 'new york' , 'times' , serif;" class="">
<div class=""><strong class="">Michel LANNERS</strong></div>
<div class="">CIO at LU-CIX Management G.I.E.</div>
<div class="">--</div>
</span>
<!-- banner -->
<div class=""><a href="https://my.weezevent.com/luxembourg-internet-days-2022" target="_blank" rel="noopener" class=""><img src="https://www.lu-cix.lu/LOGO/signature.png" width="408" height="90" class=""></a></div>
<!-- /banner -->
<span style="font-size: 9pt; font-family: 'tahoma' , 'new york' , 'times' , serif;" class="">
<div class="">Mail: <a href="mailto:michel.lanners@lu-cix.lu" rel="noopener nofollow noreferrer" target="_blank" class="">michel.lanners@lu-cix.lu</a></div>
<div class="">Phone: (+352) 28 99 29 92-81</div>
<div class="">LU-CIX Management G.I.E.</div>
<div class="">202, Z.A.E. Wolser F</div>
<div class="">L-3290 Bettembourg</div>
<div class=""><a href="https://www.lu-cix.lu" target="_blank" class="">lu-cix.lu</a></div>
<div class=""><a href="https://luxembourg-internet-days.com" target="_blank" class="">luxembourg-internet-days.com</a></div>
<div class=""><a href="https://www.lunog.lu" target="_blank" class="">lunog.lu</a></div>
</span>
</div>
<br class=""></div></body></html>