At 7:37 PM -0400 4/26/02, Lupi, Guy wrote:
>I was wondering if there was ever any kind of study done by Cisco to
>determine the acceptable average level of processor utilization on their
>equipment.  How much is too much on, let's say, a 3524 switch, or a 7513
>router?  I am sure it varies, but is there a list of some sort that states
>that at a particular average usage you should think about upgrading, or
>removing some of the load on a particular piece of gear?  Just curious.

I'd have to dig out some old notes, but there was an informal 
discussion on some ISP mailing lists.  With the RISC processors, 70% 
is about the highest 5-minute utilization you should see in routine 
use. Non-RISC processors are more like 50%.  YMMV if you are doing 
especially processor-intensive things, especially if they are bursty 
in nature.

This is generally pure IP, as you'd expect with ISPs. In the older 
days, I did some strange and wonderful things when the 7000 had great 
transfer rates but an underpowered CPU.  One approach would be to get 
a 3-slot 7010 and put a CIP, an FDDI (then the only available 100 
Mbps), and maybe a maintenance Ethernet into it.  I'd use the FDDI to 
connect to 4500/4700 processors that did all the heavy-duty RSRB and 
the like, and bridge to the CIP chassis.

At the edge of the network, four 2500s had more CPU power than a single 7000.
-- 
"What Problem are you trying to solve?"
***send Cisco questions to the list, so all can benefit -- not 
directly to me***
********************************************************************************
Howard C. Berkowitz      [EMAIL PROTECTED]
Chief Technology Officer, GettLab/Gett Communications http://www.gettlabs.com
Technical Director, CertificationZone.com http://www.certificationzone.com
"retired" Certified Cisco Systems Instructor (CID) #93005




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=42721&t=42712
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to