[ixpmanager] Remote members

[André Grüneberg]

Dear Michel, et.al.,

We are faced with a similar issue. We only support the second model -- we
never(!) extend our peering LAN to some L2 infrastructure to connect
multiple peers via one VLAN.

Originally we used to have so called reseller switches (i.e. physical
switches that fan out the different VLANs to different physical ports), but
this obviously has a lot of operational challenges ("resold" peers
effectively being more expensive).
Since we migrated to Arista 7280R series switches, we are using L2
subinterfaces. By doing so, each remote peer (=VLAN) receives a virtual
interface that appears in the list of interfaces within IXP manager.
IXP manager can be bent to work with this kind of setup, but it's not ideal
yet -- we do experience some operational challenges:

   - sFlow data contains the original VLAN ID and we thus need to tweak it
   - The data model of having multiple VLANs on a port is disrupted
   - It's a challenge to correctly configure the reseller port within IXP
   manager

We are thinking about making all interfaces L2 subinterfaces, but we have
not yet identified all drawbacks. So we are a bit reluctant to carry on. :)
We are considering sponsoring some IXP manager development to improve the
situation -- but we have not yet contacted Barry about it. *wink*

I hope this helps a bit.

BR,
André


On Fri, 26 Aug 2022 at 19:43, Michel Lanners via ixpmanager <
ixpmanager at inex.ie> wrote:

> Dear IXP manager specialists,
>
> As we mentioned here and there, LU-CIX is working on a migration project
> to take our in-house MemberDB to IXP Manager.
>
> 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.
>
> 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.
>
> 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.
>
> 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.
>
> In no case do we have dedicated physical switch ports for such remote
> members.
>
> What’s the best approach to enter this setup in the IXP manager data model?
>
> 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.
>
> Ideas?
>
> Thanks and enjoy the weekend
>
> Michel
>
> *Michel LANNERS*
> CIO at LU-CIX Management G.I.E.
> --
> <https://my.weezevent.com/luxembourg-internet-days-2022>
> Mail: michel.lanners at lu-cix.lu
> Phone: (+352) 28 99 29 92-81
>
> LU-CIX Management G.I.E.
> 202, Z.A.E. Wolser F
> L-3290 Bettembourg
> lu-cix.lu <https://www.lu-cix.lu>
> luxembourg-internet-days.com
> lunog.lu <https://www.lunog.lu>
>
> _______________________________________________
> INEX IXP Manager mailing list
> ixpmanager at inex.ie
> Unsubscribe or change options here:
> https://www.inex.ie/mailman/listinfo/ixpmanager
>


-- 
André Grüneberg, Managing Director
andre.grueneberg at bcix.de
+49 30 2332195 42

BCIX Management GmbH
Albrechtstr. 110
12103 Berlin
Germany

Geschäftsführer/Managing Directors: Jens Lietzmann, André Grüneberg
Handelsregister: Amtsgericht Charlottenburg, HRB 143581 B
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20220831/12907a1a/attachment.htm>