[rbak-nsp] SE800 QoS architecture (David Freedman)

[Ian Calderbank]

> Date: Fri, 11 Sep 2009 10:58:39 +0100
> From: "David Freedman" <david.freedman at uk.clara.net>
> To: "Jim Tyrrell" <jim at scusting.com>, <redback-nsp at puck.nether.net>
> Subject: Re: [rbak-nsp] SE800 QoS architecture
> Message-ID:
> <7B8B0D6F623C3A40A0D0A80A66756E2B0D7F88 at EXVS01.claranet.local>
> Content-Type: text/plain; charset="iso-8859-1"

> The circuit is managed by the card who has the best route to the l2tp peer 
> at the time, this is the "owner" card,
> for instance, the GE-3 cards can terminate 16K of these (it is possibly 
> now 32K, not heard if this limit has been increased or not), due to RAM 
> constraints.

24k with Qos in SEOS 6

> It used to be the case (not sure about now) that you could create a 
> "group" of cards to share the sub load,
> as you know, in order to avoid the 16K limit, the problem with this was 
> that, if your sub is "owned" by card 1 but the route to the peer (where 
> the EPPA is sending L2TP to >the peer) is on card 2, then QoS is not 
> possible because a virtual circuit had to exist between the PPA on card 1 
> and EPPA on card 2 which could not have prioritisation or >congestion 
> management applied to it (again, somebody correct me if this is now 
> possible, this information could be out of date), so you had to ensure 
> that subs stayed glued >to
>the card where the active L2TP peer route was present if you wanted any QoS 
>(which is why I suppose now the card-groups are no longer the default and 
>peer route is)


correct. you have to make them stay nailed to the card for l2tp Qos to work.

Ian