Hola a todos, mi caso es el siguiente poseo 2 router 7606-S, que forman el CORE WAN de una empresa, el tema es que se realizo una actualizacion de IOS para solventar un bug relacionado a unos túneles GRE, pero ahora se me esta presentando la situacion que el porcentaje de procesamiento se eleva hasta un 80%, con ayuda del output intepreter, este nuevo IOS me arrojo otro bug, que no me reporto la vez que investigué acerca de a cual IOS actualizar.
El tema es que necesito liberar ciertos procesos que estan "colgados" mientras me aprueban el control de cambio para hacer el nuevo upgrade.
El output del procesamiento del equipo:
sh processes cpu history
777777888885555544444444444444433333777774444444444333333333
511111000008888855555444442222200000000000000000000444448888
100
90
80 * *****
70 *********** *****
60 **************** *****
50 ********************* *****
40 ******************************* *************** **
30 **********************************************************
20 **********************************************************
10 **********************************************************
0....5....1....1....2....2....3....3....4....4....5....5....6
0 5 0 5 0 5 0 5 0 5 0
CPU% per second (last 60 seconds)
664688558795646785666987555945658575578555696765796676598757
499494987202693485438247767094918717089379603007611030244459
100
90 * * * * * * * * * * *
80 ** * * * *** * * ** * ** **
70 * ** *** * ** **** # * * * ** ** * *# * ***
60 ** **#****# * **#****#*****# * **** *# *********#**** *#*
50 ****##**#*#*#**##***####***#**#*#*#**##***##****#####**###
40 ##########################################################
30 ##########################################################
20 ##########################################################
10 ##########################################################
0....5....1....1....2....2....3....3....4....4....5....5....6
0 5 0 5 0 5 0 5 0 5 0
CPU% per minute (last 60 minutes)
* = maximum CPU% # = average CPU%
999998888988988898999999999998888888889999999999999889888898898988899999
449998453078067898009399499519853745579199999919194753523890495944619431
100 *** * * ** *** * ****** * * * * * *
90 ****** * *********************** * ******************** ** *** ****
80 **********************************************************************
70 **********************************************************************
60 **********************************************************************
50 ####******************************************************************
40 ####***************#########***************#########****************##
30 ######***#####################***##*#################****##****#######
20 ######################################################################
10 ######################################################################
0....5....1....1....2....2....3....3....4....4....5....5....6....6....7..
0 5 0 5 0 5 0 5 0 5 0 5 0
CPU% per hour (last 72 hours)
* = maximum CPU% # = average CPU%
El output interpreter de cisco dice:
------------------------
CPU UTILIZATION ANALYSIS
------------------------
INFO: Total CPU Utilization is comprised of process and interrupt percentages.
Total CPU Utilization: 86%
Process Utilization: 72%
Interrupt Utilization: 14%
These values are found on the first line of the output:
CPU utilization for five seconds: x%/y%; one minute: a%; five minutes: b%
Total CPU Utilization: x%
Process Utilization: (x - y)%
Interrupt Utilization: y%
Process Utilization is the difference between the Total and Interrupt; x minus
y. The one and five minute utilizations are exponentially decayed averages (rather
than an arithmetic average), therefore recent values have more influence on the
calculated average.
WARNING: Total CPU Utilization is 86% for the past 5 seconds, which is high
(>80%).
This can cause the following symptoms:
- Input queue drops
- Slow performance
- Slow response in Telnet or unable to Telnet to the router
- Slow response on the console
- Slow or no response to ping
- Router doesn't send routing updates
The following processes are causing excessive CPU usage:
PID CPU Time Process
232 18.79 Virtual Exec
578 17.91 SNMP ENGINE
INFO: The 'virtual EXEC process' handles virtual type terminal (vty) lines,
such as Telnet sessions on the router.
INFO: Issuing commands that generate long output, such as 'show tech-support',
can also increase the amount of CPU resources used by the virtual EXEC process.
MEMORY ANALYSIS
---------------
INFO: Processor memory utilization is 25.22434%.
INFO: Processor memory or main memory stores the running configuration and routing
tables. The Cisco IOS software executes from main memory.
INFO: The amount of processor memory required by the router is affected by the
Cisco IOS version used, the size of the network and by the access list configurations.
Ensure that an optimal IOS version has been chosen.
WARNING: The following processes are currently holding more than 1 MB of memory
with 'Freed' memory less that 'Holding' memory:
'Chunk Manager' (Holding 1093688 bytes)
'CWAN OIR Handler' (Holding 2194040 bytes)
'IP RIB Update' (Holding 2614996 bytes)
'Tbridge Monitor' (Holding 6324564 bytes)
This is considered to be high. High memory usage can be normal, or can indicate
a memory leak. To determine this, it is important to see if memory usage changes
over time.
INFO: A memory leak occurs when a process requests or allocates memory and then
forgets to free (de-allocate) the memory when it is finished with that task.
As a result, the memory block is reserved until the router is reloaded. Over
time, more and more memory blocks are allocated by that process until there is
no free memory available. At this point, the router will issue the 'SYS-2-MALLOCFAIL'
error message.
TRY THIS: Analyze the 'show process memory' output for this router over a period
of time (for example, every few hours or days depending on whether you have a
fast or slow leak).
Check to see if memory utilization for the affected process(es) continues to increase
and the amount of freed memory remains the same. The rate at which free memory
disappears depends on how often the event occurs that leads to the leak. A memory
leak is a complex condition sometimes requiring an IOS upgrade to correct. If
the above is in fact occurring, and you are uncertain about how to proceed, use
the Service Request Tool to contact the Cisco TAC for further assistance.
NOTE: It is normal for some processes, such as Border Gateway Protocol (BGP) or
Open Shortest Path First (OSPF), to use more than one megabyte of memory; this
does not mean they are leaking.
WARNING: The process '*Dead*' is holding more than 1 MB of memory.
This is considered to be high, and indicates a possible memory leak. The 'Dead'
process is not a real process. It only accounts for the memory allocated under
the context of another process which is terminated.
TRY THIS: If a memory leak is detected, and the 'Dead' process seems to be consuming
the memory, issue the "show memory dead" command from your device, and analyze
which process consumes more memory. To do so, look at the "What" section of
the output. This problem can also be caused due to a Cisco IOS Bug. Review the
Bug Tool Kit for potential bugs and upgrade the device with the latest version
of Cisco IOS software. If the problem persists, open a service request with Cisco
at Service Request Tool.
Gracias por la ayuda que me puedan brindar.
Salu2!
