[c-nsp] 7604/sup32

[Brian Turnbow]

Hi, 

7600 is a hardware forwarding platform(basically a catalyst 6500), whereas the 7200 is processor based.
The 7600 can forward much much more traffic.
With full routes however the sup-32 isn't going to cut it you need the 720 with PFC3BXL.
The sup32 doesn't have enough tcam space for full routes anymore.
To confuse the matter cisco has divided the 6500/7600 into 2 groups and features will vary.
The 6500 will use  sup -xxx as the processor
The 7600 will use rsp -xxx as the processor 
There has been alot of talk about this on the list 

Regards
Brian


-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Mark Kent
Sent: martedì 8 gennaio 2008 16.45
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] 7604/sup32

So, I'm looking at the cisco web pages and I see the 7600 is
pushed big-time as a service provider edge device, and yet I see
that the sup32-3b has a 300Mhz processor, and so it is not
much faster than an NPE-300 (262Mhz).

I stopped taking full routes on NPE-300 equipment a couple of 
years ago, moving to an npe-g1.   So, what's the scoop with
the 7600/sup32-3b?    It seems like a step back to me, other than
the 8 built-in gigE ports.

I'm looking at an application where the box would push a total of
about 1Gbs over two gigE upstreams.  It would have two gigE internal
neighbors, each with full bgp routes... so four full tables.  I'm
concerned about the issue of traceroutes looking bad as they pass
through the box (which confuses EndUsers), due to the cpu load 
from the bgp scanner.

Thanks,
-mark
_______________________________________________
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/