[ixpmanager] Adding a Reseller Port

[Barry O'Donovan]

On 23/06/2014 18:39, Paul Emmons wrote:
> I think what we are needing is the "ve" functionality.

Possibly. You originally said:

> We are connecting to them over a 10g MPLS where we will create a vpls
> for each member at that site.

But I think from the following examples:

> What I am needing to do is have some functionality where I can have
> multiple customers on a 802.1q trunks.
>
> Example Participant A	VLAN 101	AS 62	206.104.51.101 2001:504:11::101
> Participant B	VLAN 102	AS 62	206.104.51.102 2001:504:11::103
> Participant C	VLAN 103	AS 62	206.104.51.103 2001:504:11::103
> Participant C	PVVLAN 202

I think you mean: "where we will create a **VLAN** for each member at 
that site"?

If so, you don't need to put a switch in the other data centre, just 
host it yourselves and deaggregate the VLANs on it and connect a port 
per member to your peering switch.

If the numbers are small and you have ports to burn, while not pretty, 
you could even do it on your own switch by connecting it back to itself 
for each member!

It's for this scenario that ve functionality would be great where the ve 
port could translate the VLANs for us. We don't have switches capable of 
this ourselves right now but should in a few months. We wouldn't really 
be able to start developing this without the functionality.

That said, if you can make this work with ve ports, the SNMP poller 
might just find these new ports and add them to the system.

> At this point I am looking for a way to provision it in IXP for
> addresses and as#s.  I'm not worried about traffic graphs.

The problem is that a lot of the provisioning (as112, route collector 
config, route server configs, etc) rely on the existence of a physical 
interface (but a virtual interface should also work) so that it can 
ensure the port is in 'normal' state (i.e. not awaiting xconnect, 
quarantine, etc).

But once you have a physical interface, MRTG will start looking for it 
for stats.

It may be possible to add a flag to the physical interface such as 'do 
not poll' which would allow you to add a 'dummy' switch with 'dummy' 
ports to get you over a hump here. Obviously you wouldn't have traffic 
graphs.

> I will visit the idea about having he datacenter let us put a switch
> out at their site so we can have the functionality as it is written.

Or just terminate their 10Gb link locally on a switch and break out the 
VLANs there. In our own situation, we host and manage the fan out 
switches and terminate the reseller link in them.

  -  Barry


> I see this happening more and more for us though.
>
> Let me know what you think.
>
> Paul on the behalf of Phoenix-IX www.Phoenix-IX.net
>
>
> -----Original Message----- From: ixpmanager-bounces at inex.ie
> [mailto:ixpmanager-bounces at inex.ie] On Behalf Of Barry O'Donovan
> Sent: Monday, June 23, 2014 2:04 AM To: ixpmanager at inex.ie Subject:
> Re: [ixpmanager] Adding a Reseller Port
>
>
> Hi Paul,
>
> Firstly, we have some documentation here:
>
> https://github.com/inex/IXP-Manager/wiki/Reseller-Functionality
>
> The reseller system as it is implemented is based on LONAP's /
> INEX's requirements / situation where we have 'fan out' switches for
> resold members.
>
> The kit we designed this for did not support virtual ethernet
> interfaces so the use of a fan out switch was required. These
> switches essentially take a multiplex feed from a reseller where each
> member is individually .1q tagged. It then switches each resold
> member to a dedicated output port with a 1-1 connection (and stripped
> tag) with our peering switches.
>
> So, a resold member just sees their peering port as normal and is
> none the wiser. When adding ports, you do it as normal but
> additionally select a fanout port in addition to the peering port.
>
> Resellers see additional ports:
>
> - their large input port; - the fanout / output ports.
>
> Note that in our situation, we own and operate the fanout switches
> which are added to IXP Manager and are queried by SNMP / MRTG as
> usual.
>
> - Barry
>
>
> On 20/06/2014 20:42, Paul Emmons wrote:
>> Hi - We are extending our fabric to another datacenter.  We are
>> connecting to them over a 10g MPLS where we will create a vpls for
>> each member at that site.  This datacenter will be doing the layer2
>> switching function.
>>
>> I am a bit lost here with the ixp-manager configs. From a graphing
>> standpoint I am only concerned about the ram 10g port
>>
>> I have resellers turned on in the API.  I have created an account
>> for the datacenter as a reseller.  The datacenter's port show up as
>> a reseller port and on the Physical Connection I can setup 1 vlan
>> and set of ip addresses.
>>
>> How do I assign a second customer of the datacenter and add ip
>> addresses?
>>
>> I take it should do a fan out port and create a separate vlan for
>> each but that will get messy in the long run. (But I'm not worried
>> about traffic stats per customer there via MRTG)
>>
>> What is the best way to do this?
>>
>> Thanks- Paul
>>
>>
>>
>> _______________________________________________ INEX IXP Manager
>> mailing list ixpmanager at inex.ie
>> https://www.inex.ie/mailman/listinfo/ixpmanager
>>
>

-- 

Kind regards,
Barry O'Donovan
INEX Operations

Mob: +353 86 801 7669
Tel: +353  1 685 4220

+-------------------------------+-------------------------------------+
| Open Source Solutions Ltd.    | INEX Operations Team                |
| Lynx House Old Church Road,   | Internet Neutral Exchange           |
| Lower Kilmacud Road,          | Association, 4027 Kingswood Road,   |
| Stillorgan, Co Dublin.        | Citywest Business Campus, Dublin 24 |
| http://www.opensolutions.ie/  | http://www.inex.ie/                 |
+-------------------------------+-------------------------------------+