Hi Rudi, Just to expand on Gert's answer. Your guess is correct - it has everything to do with the fact you have a DFC3B in a 3BXL system. The moment you installed this card and booted up the box it failed back to common denominator of the size of the TCAM - nonXL system. If you have a lot of prefixes -> you have full TCAMs -> rate limiter towards RP -> CPU switched traffic = low throughput. In order to fix this, probably the easiest way is to upgrade your DFC on the 10G modules with WS-F6700-DFC3BXL.
One thing that is weird is that you did not notice this is in the logs as usally when this happens the switch logs interesting messages about TCAM overflow over and over. There is a lot of info about the XL vs. non-XL in the C6500 architecture document over here: http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/prod_white_paper0900aecd80673385.html <http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/prod_white_paper0900aecd80673385.html> -pavel On Sun, Jun 27, 2010 at 7:52 PM, Gert Doering <g...@greenie.muc.de> wrote: > Hi, > > On Mon, Jun 28, 2010 at 12:41:46AM +0700, Rudy Setiawan wrote: > > Would the low TCAM of 239k (due to DFC3B daughter card) have something to > do > > with this weird traffic? > > If your router is carrying full Internet routing tables (>330k), most > definitely. > > gert > -- > USENET is *not* the non-clickable part of WWW! > // > www.muc.de/~gert/ > Gert Doering - Munich, Germany > g...@greenie.muc.de > fax: +49-89-35655025 > g...@net.informatik.tu-muenchen.de > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/