RARE user and assistance email list

[Tim Chown <>]

Hi,

> On 7 Feb 2022, at 17:48, Frédéric LOUI <> wrote:
> 
> A pure IPv4 or IPv6 or dual stack profile ? :)

Dual-stack of course, as much as we’d like to drop legacy IPv4 :)

> IMHO, if IPv6 is not used the a pure IPv4 profile would be best. (Or vice 
> versa)
> No need of MPLS ? (SR etc.)

I really can’t see why any NREN would not deploy IPv6 for all its services.

> The objective is to max out the number entry for features that are  used.
> 
> But again, it is up to you to chose.

I’d hope we can keep the required features light.  Certainly no MPLS or SR.  
But we’d likely want stateless filtering for example.

Tim

> fl
> 
>> Le 7 févr. 2022 à 18:39, Tim Chown <> a écrit :
>> 
>> Hi,
>> 
>> Well, our use case is fairly simple.  The Wedge would act as a 100G 
>> gateway to host four 100G connected servers that we’d use to test 
>> perfSONAR and various data transfers tools on DTNs.  This would be a 
>> static setup, with maybe a single v4 and v6 subnet on the server side.   
>> So BGP seems overkill, but our engineers asked what RARE/FreeRtr supports.
>> 
>> What matters most is the performance, hence our interest in the tests by 
>> PSNC and on the Data Mover Challenge.  We’ve seen high rates from Joseph’s 
>> device at UvA, but inconclusive results from PSNC (they probably need to 
>> be more tightly defined).  We think in a scenario where there’s generally 
>> a limited number of concurrent flows, the small Wedge buffers (16 or 
>> 20MB?0 should be OK.   
>> 
>> There’s no initial need for multicast, PolKa or anything like that.
>> 
>> Raul and David are checking QSFPs and cables this week, so we’re getting 
>> closer to being ready to deploy.
>> 
>> Tim
>> 
>>> On 7 Feb 2022, at 15:23, mc36 <> wrote:
>>> 
>>> hi,
>>> exactly, it depends on the exact features you need...
>>> this is the ultimate source of thruth:
>>> https://bitbucket.software.geant.org/projects/RARE/repos/rare/browse/profiles
>>> the .tmpl files are the 'golas' that you have to set yourself...
>>> it's a two step optimization, first for the tcam, then for the sram...
>>> this is an ip-only profile with nothing else but the ipv4/ipv6 fib 
>>> enabled:
>>> https://bitbucket.software.geant.org/projects/RARE/repos/rare/browse/profiles/profile-rawip.tmpl
>>> https://bitbucket.software.geant.org/projects/RARE/repos/rare/browse/profiles/profile-rawip.p4
>>> and here is an other with mpls enabled:
>>> https://bitbucket.software.geant.org/projects/RARE/repos/rare/browse/profiles/profile-p.tmpl
>>> https://bitbucket.software.geant.org/projects/RARE/repos/rare/browse/profiles/profile-p.p4
>>> as flou said, you should set your own features and goals and then it'll 
>>> optimize for that specific profile...
>>> one thing to keep in mind that both sram and tcam table increase could 
>>> span to multiple code stages,
>>> resulting in lower tables so choose the primary goal according to your 
>>> needs and let the secondary
>>> goal span the remaining asic code space...
>>> regards,
>>> cs
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On 2/7/22 15:15, Fr  d  ric LOUI wrote:
>>>> Let me add Csaba as he is tweaking RARE profiles at teh moment.
>>>> The answer I presume will depends on your use case.
>>>>> Le 7 f  vr. 2022    14:51, Tim Chown <> a   crit :
>>>>> 
>>>>> Hi,
>>>>> 
>>>>> What size BGP table can the Wedge take running RARE?
>>>>> 
>>>>> i.e. should we suggest our engineers configure static routing?
>>>>> 
>>>>> Raul and David (our engineer) will be looking at the Wedge, servers and 
>>>>> cabling in their current location this week, as the plan to deploy 100G 
>>>>> in London gets nearer   
>>>>> Thanks,
>>>>> Tim
>> 
>