Что нагружает процессор в роутере

Процессор является одним из ключевых компонентов современного компьютера или роутера Keenetic, отвечающим за выполнение всех вычислений и обработку данных. Однако, в зависимости от нагрузки на устройство, процессор может значительно затормозить и ухудшить общую производительность системы.

Основные причины, грузящие процессор Keenetic, могут включать в себя выполнение сложных вычислений, обработку большого объема данных, подключение и управление большим количеством устройств, а также работу с тяжелыми приложениями и программами. Кроме того, некорректная настройка или загрузка ненужных процессов также может привести к перегрузке процессора.

Оптимизация процессора Keenetic позволяет снизить его нагрузку и улучшить производительность устройства в целом. Некоторые способы оптимизации могут включать в себя ограничение фоновых процессов и служб, удаление ненужных программ и файлов, установку антивирусного программного обеспечения, а также улучшение вентиляции и охлаждения системы.

Что нагружает процессор Keenetic: основные причины и способы оптимизации

Одной из основных причин, нагружающих процессор Keenetic, является неправильная настройка или использование маршрутизатора. Например, использование VPN-соединений с высокой нагрузкой, работа с большим количеством компьютеров и устройств, или установка приложений, потребляющих большое количество ресурсов. Все эти факторы могут привести к повышенной нагрузке на процессор и снижению производительности устройства.

Другой причиной, нагружающей процессор, может быть работа сети и передача данных. Если сеть настроена неправильно или существуют проблемы с ее стабильностью, процессор может испытывать дополнительную нагрузку при обработке и передаче данных. Проверьте уровень сигнала Wi-Fi, убедитесь, что все устройства подключены к высокоскоростной сети, и выполните проверку настройки маршрутизатора.

Оптимизация процессора Keenetic может быть достигнута путем применения следующих методов:

• Настройка VPN-соединений и использование только необходимых и проверенных приложений.
• Оптимизация сети и установка правильных настроек для Wi-Fi.
• Обновление прошивки Keenetic и настройка параметров работы маршрутизатора.
• Установка дополнительных модулей и приложений для оптимизации работы.

В целом, чтобы избежать повышенной нагрузки на процессор Keenetic и обеспечить его оптимальную работу, следует правильно настроить и использовать маршрутизатор, установить обновления ПО, проверить сеть на наличие сбоев и настроить необходимые компоненты для работы.

Множество активных подключений в сети

Оптимизация процесса обработки подключений может помочь снизить нагрузку на процессор и повысить производительность сети. Вот несколько способов оптимизации:

Оптимизация активных подключений в сети может существенно снизить нагрузку на процессор Keenetic и повысить производительность сети в целом. Это особенно важно в случае использования большого количества устройств или при работе с высокой нагрузкой на сеть.

Загрузка тяжелых приложений и сайтов

При запуске тяжелых приложений и сайтов процессору требуется больше времени и ресурсов для выполнения задач. Такие приложения обычно используют много различных скриптов, анимаций, изображений и других элементов, что требует дополнительных вычислительных мощностей.

Сайты могут быть загружены тяжелыми и большими файлами, такими как изображения высокого разрешения или видео. Также некоторые веб-страницы могут быть наполнены большим количеством скриптов и стилей, что приводит к дополнительной нагрузке на процессор.

В результате загрузки тяжелых приложений и сайтов процессор может испытывать проблемы с обработкой задач, что приводит к замедлению работы устройства и повышению нагрузки на процессор.

Для оптимизации процессора и снижения его загрузки при работе с тяжелыми приложениями и сайтами рекомендуется:

• Оптимизировать приложения и сайты, удалять ненужные расширения, плагины и скрипты;
• Очищать систему от временных файлов и мусора;
• Установить браузер с меньшим потреблением ресурсов или использовать расширения для блокировки рекламы и ненужной анимации;
• Обновлять программное обеспечение и драйвера для повышения производительности;
• Выполнять регулярную проверку системы на наличие вирусов и вредоносного ПО;
• Оптимизировать настройки системы и изменять приоритеты процессов в диспетчере задач;
• При необходимости увеличить объем оперативной памяти;

Соблюдение этих рекомендаций поможет снизить нагрузку на процессор Keenetic и повысить общую производительность устройства при работе с тяжелыми приложениями и сайтами.

Использование устаревших версий программного обеспечения

Один из основных факторов, загружающих процессор Keenetic, может быть связан с использованием устаревших версий программного обеспечения.

Устаревшие версии программ могут быть менее оптимизированными и содержать ошибки и уязвимости, которые не только замедляют работу системы, но и могут привести к непредвиденным сбоям и проблемам.

Если ваш Keenetic использует устаревшие версии программного обеспечения, это может отрицательно сказаться на его производительности и нагрузить процессор.

Чтобы оптимизировать работу процессора Keenetic, важно регулярно обновлять установленное программное обеспечение. Производитель регулярно выпускает обновления, которые включают исправления ошибок и уязвимостей, а также улучшают общую производительность системы.

Для обновления программного обеспечения Keenetic вы можете воспользоваться встроенной функцией автоматического обновления, которая позволяет своевременно получать и устанавливать последние версии программ.

Помимо обновления операционной системы, также важно следить за обновлениями различных установленных приложений и драйверов Keenetic. Устаревшие версии дополнительного программного обеспечения могут также негативно сказываться на производительности процессора и загружать систему.

Использование последних версий программного обеспечения поможет оптимизировать работу процессора Keenetic, улучшить производительность системы и предотвратить возможные проблемы и сбои.

On 1/30/2020 at 7:33 PM, Mikesk said:

Судя по ответу саппорта вот ваше исправление: 

• Web: ускорена работа при обращении к списку хостов (сообщил @biospb)

Скорее всего это другое исправление и оно связано с долгой загрузкой страницы списка хостов, а у нас была проблема опрос хостов встроенным коммутатором и это проявляясь другой проблемой.

On 2/4/2020 at 8:34 AM, Nick007 said:

Поддерживаю, 3.3.7 работает стабильно, ЦП не грузится больше ~50% 

Вышла версия 3.3.8 предварительная! Discovery: исправлен опрос хостов по ARP. Мне кажется вот это как раз наше исправление, с этой версии точно проблема должна быть устранена.

Исправления:

• Исправлено поведение светодиода «Интернет»
• TSMB: исправлено переименование файлов для файловых систем, нечувствительных к регистру
• Discovery: исправлен опрос хостов по ARP

Edited February 5, 2020 by steken

Introduction

This document describes common symptoms and causes of high CPU utilization on Cisco routers and provides guidelines and solutions for common issues. 

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

• Cisco routers 
• Cisco IOS^® software switching paths

For information on Cisco IOS software switching paths, see Performance Tuning Basics.

Components Used

This document is not restricted to specific software and hardware versions.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.

Symptoms of High CPU Utilization

This list describes common symptoms of high CPU utilization. If you notice any of these symptoms, troubleshoot the problem with steps provided in this document.

• High percentages in the show processes cpu command output.

  If you have the output of a show processes cpu command from your Cisco device, you can use Cisco CLI Analyzer  to display potential issues and fixes.

  Note: To use Cisco CLI Analyzer, you must be a registered Cisco user, be logged in, and have JavaScript enabled.

• Slow performance

• Services on the router fail to respond, for instance:

  • Slow response in Telnet or unable to Telnet to the router

  • Slow response on the console

  • Slow or no response to ping

  • Router does not send routing updates to other routers

• High buffer failures

Troubleshoot High CPU Utilization

Once you notice any of the symptoms from the Symptoms of High CPU Utilization:

• Check for a possible security issue. Commonly, high CPU utilization is caused by a security issue, such as a worm or virus operating in your network. This is especially likely to be the cause if there have not been recent changes to the network. Usually, a configuration change, when you add additional lines to your access lists can mitigate the effects of this problem. Cisco Product Security Advisories and Notices contains information on detection of the most likely causes and specific workarounds.

  For additional information, refer to:

  • 100 Questions and Answers about Internet Threats

  • Cisco Product Security Advisories and Notices

  • Cisco Threat Control

• Make sure all debug commands in your router are turned off with the undebug all or no debug all commands.

• Are you able to issue show commands on the router? If yes, start to collect more information immediately, with these show commands.

• Is the router inaccessible? Can you reproduce this problem? If yes, power-cycle the router and, before you reproduce the problem, configure the scheduler interval 500 command. This schedules low priority processes to run every 500 milliseconds, which provides time for you to run some commands, even if CPU usage is at 100 percent. On Cisco 7200 and Cisco 7500 Series Routers, use the scheduler allocate 3000 1000 command.

• Does the router show symptoms of high CPU utilization at brief and unpredictable intervals? If yes, periodically collect the output of the show processes cpu command, which shows if the high CPU utilization is caused by interrupts or by a certain process. Use this UNIX script and, based on what you find first, modify the script to collect data needed for further investigation of the issue.

Determine Causes and Solve the Problem

Use the show processes cpu command to check if CPU utilization is high due to interrupts or processes.

High CPU Utilization due to Interrupts

For more information, refer to Troubleshooting High CPU Utilization Caused by Interrupts. If the level of the CPU rises due to interrupts that are likely due to CEF switching packets, the level of CPU does not affect the router performance.

High CPU when Enabling NetFlow NDE on Cisco 7600 Series Router

If NetFlow is configured for version 7, the flow is performed by the Routing Processor, which can cause high CPU utilization.

To troubleshoot the high CPU utilization due to NetFlow version 7, configure mls nde sender version 5, as the NetFlow export is performed by the SP, which is the default for version 5 or version 9.

High CPU Utilization due to Processes

Check which process loads the CPU. Unusual activity related to a process results in an error message in the log. Therefore, the output of the show logging exec command must be checked first for any errors related to the process which consumes lots of CPU cycles.

You can use debug commands to troubleshoot high CPU utilization in these processes. Debug commands must be carried out with extreme caution because it can raise the CPU utilization even more. These prerequisites must be met in order to use debug commands safely:

• All logging destinations except buffer logging must be either disabled or their logging severity level must be lowered from 7 (debugging) to 6 (informational) or less, with use of the appropriate logging destination [ severity-level ]  configuration  command. To see which logging destinations and corresponding levels are enabled, read the header lines of the show logging exec command.

• Logging buffer size must be increased in order to capture sufficient information. For more details, refer to the description of the logging buffer global configuration command.

• In order to be able to better read and understand debugs, the datetime and millisecond timestamps must be enabled. For more details, refer to the description of the service timestamps global configuration command.

A sample debugging session of IP packets is provided in Troubleshooting High CPU Utilization in the IP Input Process.

To troubleshoot high CPU utilization in specific processes, refer to:

• ARP Input—ARP Input section of the document Troubleshooting High CPU Utilization due to Processes.

• BGP Router—High CPU due to BGP Router Process section of the document Troubleshooting High CPU caused by the BGP Scanner or BGP Router Process.

• BGP Scanner—High CPU due to BGP Scanner section of the document Troubleshooting High CPU caused by the BGP Scanner or BGP Router Process.

• EXEC—High CPU Utilization in the EXEC and Virtual EXEC Processes.

• HyBridge Input—Troubleshoot High CPU Utilization caused by the HyBridge Input Process on Routers With ATM Interfaces.

• IP Input—Troubleshooting High CPU Utilization due to the IP Input Process.

• IP Simple Network Management Protocol (SNMP)—IP Simple Network Management Protocol (SNMP) Causes High CPU Utilization.

• LC ADJ Updater—What Causes High CPU Utilization in the LC Adjacency Updater Process on a Cisco 12000 Series Internet Router?

• TCP Timer—TCP Timer section of the document Troubleshooting High CPU Utilization due to Processes.

• TTY Background—TTY Background section of the document Troubleshooting High CPU Utilization due to Processes.

• Virtual EXEC —See the link for EXEC. High CPU Utilization in Exec and Virtual Exec Processes.

• Vtemplate Backgr—Virtual Template Background section of the document Troubleshooting High CPU Utilization due to the Processes.

• SSH Process—Can go high if it captures a show tech or a debug is enabled.

• Other processes—Other Processes section of the document, Troubleshooting High CPU Utilization due to the Processes.

PCI and FAST Memory Pools Show Very High Utilization

It is normal to see low free memory with PCI and Fast memory pools. The PCI memory is used for memory access to the GT64260 controller on the PRP mainboard for the PCI buses connected to it. This memory is used for internal communication between the system controller and other parts, so it appears to be high all the time.

If more memory is needed, it falls back to processor pool memory. The Fast memory is a small amount of memory that has been set aside for use by the hardware Interface Descriptor Block (IDB) data structures. This memory is also completely reserved throughout bootup, so it is always shows as high since the memory is completely used. Because of this, it is normal to see low free memory with the Fast memory pool.

%SNMP-4-HIGHCPU: Process exceeds [dec]ms threshold ([dec]ms IOS quantum) for [chars] of [chars]—result [chars]

The CPU hog message looks like this:

SNMP-4-HIGHCPU: Process exceeds 200ms threshold (200ms Cisco IOS quantum)
for GET of rmon.19.16.0--result rmon.19.16.0

A new syslog message (HIGHCPU) was added to Cisco IOS in 12.4(13). If a process holds on to the CPU for more than 200 ms, it reports a HIGHCPU message. The HIGHCPU message has no impact on the router. It just lets you know what process has caused the high CPU. The HIGHCPU message is similar to the CPUHOG message, but the HIGHCPU message has a much lower tolerance threshold, at 1/10 the amount of time compared to a CPUHOG message, that is, measured in milliseconds). In versions prior to 12.4(13) on the 2600, the processes ran for longer times but did not generate messages because the Cisco IOS versions did not have this enhancement.

SNMP PDU processing (MIB object queries) are supposed to be performed in a single CPU time quantum to ensure that each object in the PDU is retrieved as if simultaneously. This is a requirement imposed by the SNMP protocol standard. Some objects are aggregates of a lot of data in the system, so, even though they are single objects, there is a lot of processing involved due to the way they are instrumented. If they do not relinquish the CPU, as required by MIB instrumentation rules, there is a possibility of this error message. Additionally, if you poll several different objects in the same object group/table and get the error message, is not unusual because of this same reason.

This message is used to identify objects that use more CPU time than expected (but still not CPUHOG). Some NMS/instrumentation tools do not behave well when polling. This issue is documented in Cisco bug ID CSCsl18139.

Note: Only registered Cisco users have access to internal tools and bug information.

High CPU due to Software Encryption

When there is no hardware encryption module installed in the device, then all encrypted traffic comes through the device has to be encrypted by the software. This is very CPU intensive. It is not recommended to use software encryption for any encryption deployment with a reasonable throughput requirement. One option to resolve this issue is to reduce the volume of encrypted traffic (re-route traffic or limit the flows that are encrypted). However, the best way to address this issue is to get a Hardware Encryption module installed for this device which eliminates the need for encryption to take place through the software.

Note: If you enable crypto maps on Tunnel/Physical interfaces it causes the memory consumption process and can cause an increase in CPU.

High CPU Utilization due to Fragmentation

Reassemblies can drive up the CPU very high if the CPU has to reassemble a large number of packets.

To troubleshoot the high CPU utilization due to fragmentation, issue the  tcp mss-adjust 1400 command on the interface which sets the maximum segment size (MSS) value of TCP synchronize/start (SYN) packets that go through a router.

Commands to Obtain More Information

These commands provide more information about the problem:

• show processes cpu

• show interfaces   

• show interfaces switching   

• show interfaces stat

• show ip nat translations

• show align   

• show version   

• show log   

For more details on show commands, see the Cisco IOS Configuration Fundamentals Command Reference.

If the router is completely inaccessible, first power-cycle it. Then, periodically collect the output of the commands in this section, except for the show log command, whose messages must be logged on a syslog server. The interval to collect the output must be five minutes. You can collect the data manually or automatically, with this UNIX shell script . You can also collect data with HTTP or SNMP.

The show processes cpu Command

This is an example of the header of the show processes cpu command.

 CPU utilization for five seconds: X%/Y%; one minute: Z%; five minutes: W% 
  PID  Runtime(ms)  Invoked  uSecs    5Sec   1Min   5Min TTY Process 

This table describes the fields in the header:

¹CPU utilization on process level = X — Y

²Values do not represent an arithmetical average, but an exponentially decayed average. Thus, more recent values have more influence on the calculated average.

For details, refer to the show commands reference guide.

Note: Total CPU utilization must not be used as a measure of the ability of the router to switch more packets. On Cisco 7500 routers, Versatile Interface Processors (VIPs) and Route/Switch Processors (RSPs) do not report linear CPU utilization. Close to half of the switching packet-per-second power comes after 90 to 95 percent CPU utilization.

The show interfaces Command

This command is used to determine active interfaces.

The show interfaces switching  Command

This command is used to determine active switching paths on interfaces.

This is a sample output of the  show interfaces switching command for one interface:

RouterA#show interfaces switching
 Ethernet0 
           Throttle count          0 
         Drops         RP          0         SP          0 
   SPD Flushes       Fast          0        SSE          0 
   SPD Aggress       Fast          0 
  SPD Priority     Inputs          0      Drops          0 

      Protocol       Path    Pkts In   Chars In   Pkts Out  Chars Out 
         Other    Process          0          0        595      35700 
             Cache misses          0 
                     Fast          0          0          0          0 
                Auton/SSE          0          0          0          0 
            IP    Process          4        456          4        456 
             Cache misses          0 
                     Fast          0          0          0          0 
                Auton/SSE          0          0          0          0 
           IPX    Process          0          0          2        120 
             Cache misses          0 
                     Fast          0          0          0          0 
                Auton/SSE          0          0          0          0 
 Trans. Bridge    Process          0          0          0          0 
             Cache misses          0 
                     Fast         11        660          0          0 
                Auton/SSE          0          0          0          0 
       DEC MOP    Process          0          0         10        770 
             Cache misses          0 
                     Fast          0          0          0          0 
                Auton/SSE          0          0          0          0 
           ARP    Process          1         60          2        120 
             Cache misses          0 
                     Fast          0          0          0          0 
                Auton/SSE          0          0          0          0 
           CDP    Process        200      63700        100      31183 
             Cache misses          0 
                     Fast          0          0          0         0 
                Auton/SSE          0          0          0          0 

The output lists the switching paths for all protocols configured on the interface, so you can easily see what kind and the amount of traffic that goes through the router. This table explains the output fields.

The show interfaces stat Command

This command is a summarized version of the show interfaces switching command. This is a sample output for one interface:

 RouterA#show interfaces stat
 Ethernet0 
           Switching path    Pkts In   Chars In   Pkts Out  Chars Out 
                Processor      52077   12245489      24646    3170041 
              Route cache          0          0          0          0 
        Distributed cache          0          0          0          0 
                    Total      52077   12245489      24646    3170041 

The output of the show interfaces stat command is different for different platforms, and depends on available and configured switching paths.

The show ip nat translations Command

The show ip nat translations command displays the Network Address Translation (NAT) translations active on the router. Each active translation generates CPU interrupts and has an impact on the total CPU utilization of the router. A very large number of translations can have a performance impact on the router.

This is a sample output from the show ip nat translations command:

     router#show ip nat translations
     Pro Inside global    Inside local    Outside local    Outside global
     --- 172.16.131.1     10.10.10.1      ---              ---

The show align Command

This command is available only on reduced instruction set computing (RISC) processor-based platforms. On these platforms, the CPU can correct for memory reads or writes that do not align. This is sample output:

 Alignment data for: 
 4500 Software (C4500-DS40-M), Version mis-aligned RELEASE SOFTWARE (fc1) 
 Compiled Tue 31-Mar-98 15:05 by jdoe

 Total Corrections 33911, Recorded 2, Reads 33911, Writes 0 

 Initial Initial 
 Address Count Access Type Traceback 
 40025F4D 15561 16bit read 0x606F4A7C 0x601C78F8 0x6012FE94 0x600102C0 
 40025F72 18350 32bit read 0x606FB260 0x6013113C 0x600102C0 0x60010988 

The show version Command

To track high CPU utilization problems, the important information to take from the command output is the Cisco IOS Software version, platform, CPU type, and the uptime of the router. The command reference gives a detailed explanation of this command.

The show log Command

This command shows the contents of buffered log messages.

EEM Scripts for Automatic Data Collection in High CPU Conditions

Embedded Event Manager can be used to automatically collect data when a high CPU condition occurs.  EEM is triggered by monitoring either the SNMP OID for the process utilization or by monitoring the syslog messages for the output from the CPU threshold command. Various show commands can be executed through the EEM script, and the output can be saved to the file system.

Example EEM Script with the SNMP OID

This script is executed when the process utilization increases about 85%. 

For more information, see How to Collect CPU Utilization on Cisco IOS Devices Using SNMP.

event manager applet high-cpu
!
event snmp oid 1.3.6.1.4.1.9.9.109.1.1.1.1.3 get-type next entry-op gt entry-val 85 poll-interval 5 exit-time 500 maxrun 600
!
 action 0.1 cli command "enable"
 action 0.2 syslog msg "TAC - Capturing high cpu information to flash:"
 action 0.3 cli command "term length 0"
 action 1.1 cli command "show process cpu sorted | redirect flash:eem-cpu1.txt"
 action 1.2 cli command "show interface | redirect flash:eem-interface1.txt"
 action 1.3 cli command "show interface stats | redirect flash:eem-stat1.txt"
 action 1.4 cli command "show ip traffic | redirect flash:eem-traffic1.txt"
 action 4.1 syslog msg "TAC - Finished logging information to separate eem files in flash"
 action 9.4 cli command "end"
 action 9.5 cli command "term default length"
!
!
end

Example EEM Script with the CPU Threshold Notifications Messages

A combination of EEM and the CPU threshold notifications command can trigger the EEM script. In this example, a CPURISHINGTHRESHOLD syslog message is generated when the utilization rises over 85% for a 5 second interval.  The EEM script can trigger off the syslog message and execute a list of commands that are saved to a file on the file system.

process cpu threshold type total rising 85 interval 5
!
event manager applet high-cpu
event syslog pattern "CPURISINGTHRESHOLD"
  action 0.1 syslog msg "EEM: HIGH CPU detected. Writing info to flash:eem-log.txt"
  action 0.2 cli command "enable"
  action 0.3 cli command "term exec prompt timestamp"
  action 0.4 cli command "term len 0"
  action 1.1 cli command "show process cpu sorted | append flash:eem-log.txt"
  action 1.2 cli command "show proc mem sorted | append flash:eem-log.txt"
  action 1.3 cli command "show mem alloc total | append flash:eem-log.txt"
  action 2.2 syslog msg "EEM: Self-removing applet from configuration..."
  action 2.5 cli command "end"
!
end

Example EEM Script to Start/Stop CPU Profile

EEM is used to start/stop CPU profiling as well as log data from various show commands. See Troubleshooting High CPU Utilization Due to Interrupts for more information.

event manager applet High_CPU
event snmp oid 1.3.6.1.4.1.9.9.109.1.1.1.1.4.1 get-type exact entry-op ge entry-val "75" exit-time 10 poll-interval 5
action 0.1 syslog msg "CPU Utilization is high"
action 0.2 cli command "enable"
action 0.4 cli command "show version | append flash:CPU_Profile.txt"
action 0.4 cli command "show log | append flash:CPU_Profile.txt"
action 0.5 cli command "show process cpu sorted | append flash:CPU_Profile.txt"
action 0.6 cli command "show interfaces | append flash:CPU_Profile.txt"
action 0.7 cli command "show region | append flash:CPU_Profile.txt"
action 1.2 cli command "profile 4000F000 42C9FFFF 4"
action 1.3 cli command "profile start"
action 2.3 syslog msg "Entering TCLSH"
action 2.4 cli command "tclsh"
action 2.5 cli command "after 240000"
action 2.6 cli command "exit"
action 2.9 syslog msg "Exiting TCLSH"
action 3.0 cli command "profile stop"
action 3.1 cli command "show profile terse | append flash:CPU_Profile.txt"
action 3.2 cli command "clear profile"
action 3.3 cli command "unprofile all"
action 4.1 syslog msg "Finished logging information to flash:CPU_Profile.txt..."
action 4.2 cli command "end"

UNIX Shell Script for Periodic Data Collection

This appendix describes a simple script that periodically captures data from the router. The core of the script is this line:

  (echo "show version") | telnet 192.168.1.1

The command in parentheses is executed in sub-shell and the output is sent to a Telnet session. This is a sample script to capture the output from the show version and show processes cpu commands:

     #!/opt/local/bin/bash

     ########################################### 
     # Router's IP address 
     # 
     IP_ADDRESS='10.200.40.53' 
       

     # Directory where the log files can be stored 
     # 
     DIR=/var/log/router 

     ######################################## 

     if [ ! -e $DIR ] 
     then 
       mkdir $DIR 
     fi 

     # Tag specification: mmddhhmm 
     DATE=`date +'%m%d'` 
     TIME=`date +'%H%M'` 
     TAG=$DATE$TIME 

     # Collect data from the router 
     (echo "foo";\ 
     echo "bar";\ 
     echo "term len 0";\ 
     echo "show version";\ 
     echo "show processes cpu";\ 
     echo "term len 15";\ 
     echo "show memory summary";\ 
     echo "q";\ 
     sleep 30)|telnet $IP_ADDRESS > $DIR/info.$TAG 2>$DIR/info.$TAG.msg 

Note: In this script all data, this includes the password, are sent in a clear text format.

In the first section, you need to specify the IP address and the destination directory for log files. The second section contains the actual commands that are sent to the router. The first is the username, then the password, and so on. to capture only the first lines of output of certain commands is included. Terminal length is set to something short (15 in this case), and the «q» character is sent only by prompt.

If data is collected periodically, the output of show version shows if the problem has a periodic nature, for example, if it appears always at a certain time of day or on a particular day of the week. If you need to collect the output of more commands, they can be added to the script in the same manner as those shown in the example. If you need to truncate the output sent to the file, first increase the sleep period (the sleep command in parenthesis).

Run this script every five minutes if the high CPU utilization problem appears often and does not last long. Otherwise, you can run it every 15 or 30 minutes. For ease of use, save the script in a file such as /usr/bin/router-script . Then, to run it every five minutes, add the next line to the /etc/crontab file:

     */5       *       *       *       *       /usr/bin/router-script

Restart the cron server. If you do not have the authority to change the /etc/crontab file, run the script in a separate process, like this:

     while [ 1 ]; do ./router-script ; sleep 300; done &

Related Information

• High CPU Utilization on Catalyst 2900XL/3500XL Switches
• Performance Tuning Basics
• Cisco Technical Support & Downloads