[c-nsp] OC3 Throughput

Clayton Zekelman clayton at mnsi.net
Mon Nov 26 08:07:09 EST 2007



An NPE-G1 easily handles 2 full ATM-OC3's worth of L2TP tunnels.

We have several of these in production, and typically hit around 60% CPU utilization.

----- Original Message ---------------

Subject: Re: [c-nsp] OC3 Throughput
   From: "Robert E. Seastrom" <rs at seastrom.com>
   Date: Mon, 26 Nov 2007 07:48:40 -0500
     To: Aaron <dudepron at gmail.com>
     Cc: cisco-nsp at puck.nether.net

>
>Of course, the *real* answer which everyone seems to be overlooking is
>that you're terminating PPPoE-over-L2TP per Paul's original mail.  The
>encap/deencap is the limiting factor, and you're gonna pummel any
>known NPE up to and including the NPE-G1 before you hit the link speed
>limit with ATM or POS (you're running an ISP; you *will* have traffic
>going both ways, and substantial upstream in todays p2p world).
>
>What processor do you have in there?
>
>                                        ---Rob
>
>Aaron <dudepron at gmail.com> writes:
>
>> Of course you didn't specify ATM originally either. POS would probably
>> give you a few more since you don't have the ATM overhead.
>>
>> On Nov 17, 2007 3:09 PM, Garry <gkg at gmx.de> wrote:
>>> Paul Stewart wrote:
>>> > A few people hit me offline stating that it's not nice to hold back the
>>> > answers and that they were curious... right you are - sorry about that...;)
>>> >
>>> > The general answer has been 110-120Mb/s considering ATM overheads etc. on a
>>> > 5 minute graph average - beyond that you are really pushing your luck.  We
>>> > have one such circuit today that is hitting 110 regularily and sometimes
>>> > hits 120 for short peaks - my concerns are now staring at me on a graph....
>>>
>>> In general (at least speaking from an ISP's point of view) when
>>> utilizing a link beyond 90% peak or beyond 75% average, it's time to
>>> upgrade ... otherwise it's just a question of time when the link
>>> capacity is causing quality degradation for the users ... (unless the
>>> peaks are caused by batch-only traffic).
>>>
>>> Take the usage graph to your boss and tell him you need another link or
>>> an OC12 upgrade ;)
>>>
>>> -garry
>>>
>>> _______________________________________________
>>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>>
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>_______________________________________________
>cisco-nsp mailing list  cisco-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-nsp
>archive at http://puck.nether.net/pipermail/cisco-nsp/



More information about the cisco-nsp mailing list