[c-nsp] Getting ready to pull the trigger: RSP720/SUP720
Rick Ernst
rick at woofpaws.com
Mon Apr 6 10:51:40 EDT 2009
The stars are starting to come into alignment and I'm about ready to
order equipment for a network refresh.
I currently have a edge/core/aggregation model with 7206VXR/NPE-G1 at the
edge, 7500/RSP16/GEIP+ in the core, and various aggregation devices from
5500/RSM to 7500/RSP8 and dialup, DSL, etc. We are migrating from OC-3 to
GigE at our edge.
We currently push about 300mbs in each direction and that is expected to
grow by at least 100mbs this year. The rate of growth has increased
dramatically.
I'm planning on collapsing the border/core into a pair of
7600/Sup720-3BXLs, and it looks like they will be almost idle with this
amount of load.
The problem I am running into is spec'ing the aggregation layer. Almost
all of our traffic is ethernet now, and all the interfaces need
bi-drectional rate-limiting/traffic-shaping/policing. We have a variable
bandwidth model and need to cap traffic at 1Mbs granularity. 1,5, and
10Mbs connections are common, and 20,50,100Mbs connections exist with a
200Mbs pipe in process.
The only traffic management I have used in the past is Cisco's rate-limit,
and it is very CPU intensive. I'm trying to find out if a Sup720/RSP720
can handle hundreds of interfaces, each being rate-limited in some manner.
The Cisco data sheet is vague about "some features" and "QoS" in
hardware, but isn't specific about what features are in hardware.
Is the Sup720 (RSP720 a better answer?) sufficient? Is traffic-management
in hardware, and should I be looking at rate-limit or some different
mechanism?
The network itself is otherwise pretty low-touch. My intent is to "just
move the bits", but I also use uRPF with a BGP blackhole system for IDS.
Note: I'd like to keep as much of the equipment the same to simplify
sparing, configuration, etc.
Thanks!
More information about the cisco-nsp
mailing list