Subject: RARE user and assistance email list
List archive
- From: Tim Chown <>
- To: mc36 <>
- Cc: Frédéric LOUI <>, Xavier Jeannin <>, "" <>
- Subject: Re: [RARE-users] RARE/Wedge BGP table size?
- Date: Mon, 7 Feb 2022 17:39:05 +0000
- Accept-language: en-GB, en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=XK9nvFnOgVTMFu9TCg1v6NuEHXNXjSLIaV1mw10rxEc=; b=WIg6U6DRz3D0zufsHAMSh8QO5zwPPv0/Ff/y0mfHpLT7QqyG/nizep4JpKGXHOfkplxn2Z1SAQHiPJ93A/mYUqsvngAIEw6tpdQalh7z9WXpn4rpJxKxpxCqzXCO5UhrnT6CaLUZftfDfsxPb9yS68ob8EATy6ImlNxiDzCvO9FsgSl50/eDepw56n1cR5QHVCs3wIzqhKvKVS/Gx9NwS5MFFHqRNBPPOrZqJmX0uWI+0WEaKdVQesvGXM64DXPiZ0nU61zIMkOlGcPYE5g3Uno7IQ57FMzCp/1eXik29snNaEe10BOwcDJHcT7E3EhAoryKS0yWWYXl9layUYkFuw==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=YH9TeOpWZRIbo6D8lREfRy0UWhjfzUI2mLzsoW9p/0EZGL+QEONkd235PeHtrPPlN/8sWukudp7SAMJGZDP6GWBeqrkPt/zL2egmcve7KejwwyrrbPiSDEGgD1arBgncpLDfSRx6c+iIC1ActYcnRN6CaRQOh6pawdza6bDWceH9Oh7gR5bvhx1eT6Zt9R1lRM5egv0WaJsMPOlLcrD+SIxGrGskyXMuuWQC3zuAyReiFheXiIskiUT4FV9Px92avZEW6XvMcP96mqzag7BzLfcCn6B5UmI2YEmPOD8KtIgKaXsuHrb8LIgM0Jg1NEoUrQrNdJL9elrC6S5OMvztfw==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=jisc.ac.uk;
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
- Re: [RARE-users] RARE/Wedge BGP table size?, mc36, 02/07/2022
- Re: [RARE-users] RARE/Wedge BGP table size?, Tim Chown, 02/07/2022
- Re: [RARE-users] RARE/Wedge BGP table size?, Frédéric LOUI, 02/07/2022
- Re: [RARE-users] RARE/Wedge BGP table size?, Tim Chown, 02/10/2022
- Re: [RARE-users] RARE/Wedge BGP table size?, mc36, 02/10/2022
- Re: [RARE-users] RARE/Wedge BGP table size?, Tim Chown, 02/14/2022
- Re: [RARE-users] RARE/Wedge BGP table size?, mc36, 02/14/2022
- Re: [RARE-users] RARE/Wedge BGP table size?, Tim Chown, 02/14/2022
- Re: [RARE-users] RARE/Wedge BGP table size?, mc36, 02/14/2022
- Re: [RARE-users] RARE/Wedge BGP table size?, Tim Chown, 02/14/2022
- Re: [RARE-users] RARE/Wedge BGP table size?, mc36, 02/10/2022
- Re: [RARE-users] RARE/Wedge BGP table size?, Tim Chown, 02/10/2022
- Re: [RARE-users] RARE/Wedge BGP table size?, mc36, 02/07/2022
- Re: [RARE-users] RARE/Wedge BGP table size?, Tim Chown, 02/10/2022
- Message not available
- Re: [RARE-users] RARE/Wedge BGP table size?, Tim Chown, 02/10/2022
- Message not available
- Re: [RARE-users] RARE/Wedge BGP table size?, Tim Chown, 02/14/2022
- Message not available
- Re: [RARE-users] RARE/Wedge BGP table size?, Tim Chown, 02/10/2022
- Message not available
- Re: [RARE-users] RARE/Wedge BGP table size?, Tim Chown, 02/10/2022
- Re: [RARE-users] RARE/Wedge BGP table size?, Frédéric LOUI, 02/07/2022
- Re: [RARE-users] RARE/Wedge BGP table size?, Tim Chown, 02/07/2022
Archive powered by MHonArc 2.6.19.