[c-nsp] Lot of input errors on a NPE-G1 interface

[Matlock, Kenneth L]

Ha! So that 1 port can do line rate to..... the CPU? :)
 
And I can see getting that linerate out of the box. It's things like QoS and Netflow that really have to involve the CPU much more than simple packet forwarding.
 
Once you get most of those services established (such as ISIS) there's really not much for the CPU to do to maintain the table. 
 
Ken

________________________________

From: Mark Tinka [mailto:mark.tinka at seacom.mu]
Sent: Thu 5/24/2012 6:30 AM
To: cisco-nsp at puck.nether.net
Cc: Matlock, Kenneth L; gal.9430 at googlemail.com
Subject: Re: [c-nsp] Lot of input errors on a NPE-G1 interface



On Thursday, May 24, 2012 02:19:39 PM Matlock, Kenneth L
wrote:

> I recently had a similar issue with a 7201 (which is
> effectively a NPE-G2). Keep in mind that a 7200 series
> platform is 100% software-based.

Except for the part where they said the 4th Gig-E port is a
PCI-X connection to the board and can run at line rate
independently.

Never did quite figure that one out :-).

> And NPE-G2 is rated for 1024Mb/sec. This is aggregate
> throughput, meaning you can do 1024mb/sec in one
> direction, or 512mb/sec each direction before
> overrunning the box. This is with no services running,
> static routes, etc. Talked to my SE and found out that
> performance with QoS drops to 512mb/sec aggregate, and
> with Netflow it dropped to 256mb/sec. (aggregate).

We used the NPE-G2 as a core router many, many years ago,
and extratced 950Mbps from it (aggregate) with 0% packet
loss at 91% CPU utilization. v6, v6, MPLS, IS-IS, LDP, RSVP.

Mark.


*** Exempla Confidentiality Notice *** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any other dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately by replying to the message and deleting it from your computer. Thank you. *** Exempla Confidentiality Notice ***