×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Swith/Router Memory and CPU

Answered Question
Sep 10th, 2009
User Badges:

Hi all,


What is the acceptable percentage level of CPU and Memory for a Cisco router or switch? what kind of actions can be taken when the CPU utilization is high or Memory low?


Thanks,

Correct Answer by bill.efthimiou about 7 years 11 months ago

Quite a difficult series of questions to answer as there are many many dependencies. My response to your router CPU question would be, if the router is performance is acceptable then whatever the level of CPU is acceptable. However, you probably want to take into account, capacity planning to ensure the router will cope with futre demands.


CPU on a switch is a little different. Generally speaking, traffic traversing a switch "should" not touch CPU, although there are exceptions. You would need to consider things such as control plain protocols such Spanning tree, routing protocols, SNMP, etc, etc and the load these are placing on your switch.


Memory again will depend on the functional requirements of the router. What routing protocol(s) are required and how large is the routing table? Other features on the router also affect memory utilization not to mention CPU.


Nevertheless, the above views are quite generalised. Cisco has written many good documents that help explain and troubleshoot CPU and memory related issues on routers and switches. i have listed some these below. I hope you find some answers here:


Troubleshooting memory problems:

http://www.cisco.com/en/US/products/sw/iosswrel/ps1831/products_tech_note09186a00800a6f3a.shtml


Troubleshooting High CPU utilization on routers:

http://www.cisco.com/en/US/products/hw/routers/ps133/products_tech_note09186a00800a70f2.shtml


Catalyst 3750 Series Switches High CPU Utilization Troubleshooting:

http://www.cisco.com/en/US/products/hw/switches/ps5023/products_tech_note09186a00807213f5.shtml


Troubleshooting High CPU Utilization:

http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/troubleshooting/cpu_util.html


Regards,

Bill.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
bill.efthimiou Thu, 09/10/2009 - 05:42
User Badges:

Quite a difficult series of questions to answer as there are many many dependencies. My response to your router CPU question would be, if the router is performance is acceptable then whatever the level of CPU is acceptable. However, you probably want to take into account, capacity planning to ensure the router will cope with futre demands.


CPU on a switch is a little different. Generally speaking, traffic traversing a switch "should" not touch CPU, although there are exceptions. You would need to consider things such as control plain protocols such Spanning tree, routing protocols, SNMP, etc, etc and the load these are placing on your switch.


Memory again will depend on the functional requirements of the router. What routing protocol(s) are required and how large is the routing table? Other features on the router also affect memory utilization not to mention CPU.


Nevertheless, the above views are quite generalised. Cisco has written many good documents that help explain and troubleshoot CPU and memory related issues on routers and switches. i have listed some these below. I hope you find some answers here:


Troubleshooting memory problems:

http://www.cisco.com/en/US/products/sw/iosswrel/ps1831/products_tech_note09186a00800a6f3a.shtml


Troubleshooting High CPU utilization on routers:

http://www.cisco.com/en/US/products/hw/routers/ps133/products_tech_note09186a00800a70f2.shtml


Catalyst 3750 Series Switches High CPU Utilization Troubleshooting:

http://www.cisco.com/en/US/products/hw/switches/ps5023/products_tech_note09186a00807213f5.shtml


Troubleshooting High CPU Utilization:

http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/troubleshooting/cpu_util.html


Regards,

Bill.

Actions

This Discussion