×

Mensaje de advertencia

  • 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.

High CPU processes cisco 4507

Sin Contestar
Jun 23rd, 2014
User Badges:

 

someone can mention me which is the reason for the switch processing rises?

 

C4507_TB_P3#sh processes cpu sorted 
CPU utilization for five seconds: 61%/1%; one minute: 67%; five minutes: 65%
 PID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min TTY Process 
  58  2928937755 430991901       6795 39.51% 48.78% 46.60%   0 Cat4k Mgmt LoPri 
  57   823867809 879510700        936 12.87% 11.09% 11.50%   0 Cat4k Mgmt HiPri 
 121   169070264  39659911       4263  3.03%  2.55%  2.54%   0 Spanning Tree    
   7    14522793   1304746      11130  2.07%  0.29%  0.20%   0 Check heaps      
  39   104487574  12503627       8356  1.51%  1.52%  1.51%   0 IDB Work         
  96    10638538  70582649        150  0.31%  0.34%  0.32%   0 UDLD             
 186     4198472  79388221         52  0.15%  0.09%  0.08%   0 PM Callback      
 114     5913937  30525794        193  0.15%  0.06%  0.07%   0 IP Input         
 232     4204001  21998494        191  0.07%  0.04%  0.04%   0 IP SNMP          
  94      121988   7136807         17  0.07%  0.00%  0.00%   0 Ethernet Timer C 
 108     1838976   4431215        415  0.07%  0.04%  0.05%   0 OSPF-1 Hello     
 234    11209629   8491999       1320  0.07%  0.11%  0.13%   0 SNMP ENGINE      
  14     6009233  11386077        527  0.07%  0.05%  0.05%   0 ARP Input        
   3         307       234       1311  0.07%  0.02%  0.04%   1 SSH Process      

 

 

rface GigabitEthernet7/14, changed state to up
Jun 22 23:05:33: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet7/14, changed state to down
Jun 22 23:05:34: %LINK-3-UPDOWN: Interface GigabitEthernet7/14, changed state to down
Jun 22 23:05:36: %LINK-3-UPDOWN: Interface GigabitEthernet7/14, changed state to up
Jun 22 23:05:36: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi3/44 and vlan 25, the non-cumulative packet dropped count is 1.
Jun 22 23:05:37: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet7/14, changed state to up
Jun 22 23:05:48: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet7/14, changed state to down
Jun 22 23:05:49: %LINK-3-UPDOWN: Interface GigabitEthernet7/14, changed state to down
Jun 22 23:06:04: %LINK-3-UPDOWN: Interface GigabitEthernet7/14, changed state to up
Jun 22 23:06:07: %LINK-3-UPDOWN: Interface GigabitEthernet7/14, changed state to down
Jun 22 23:06:21: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi3/47 and vlan 25, the non-cumulative packet dropped count is 1.
Jun 22 23:07:06: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi3/47 and vlan 25, the non-cumulative packet dropped count is 1.
Jun 22 23:07:12: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/36, changed state to down
Jun 22 23:07:13: %LINK-3-UPDOWN: Interface GigabitEthernet4/36, changed state to down
Jun 22 23:07:17: %LINK-3-UPDOWN: Interface GigabitEthernet4/36, changed state to up
Jun 22 23:07:18: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/36, changed state to up
Jun 22 23:07:22: %LINK-3-UPDOWN: Interface GigabitEthernet7/14, changed state to up
Jun 22 23:07:23: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet7/14, changed state to up
Jun 22 23:07:24: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/36, changed state to down
Jun 22 23:07:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet7/14, changed state to down
Jun 22 23:07:25: %LINK-3-UPDOWN: Interface GigabitEthernet4/36, changed state to down
Jun 22 23:07:26: %LINK-3-UPDOWN: Interface GigabitEthernet7/14, changed state to down
Jun 22 23:07:29: %LINK-3-UPDOWN: Interface GigabitEthernet4/36, changed state to up
Jun 22 23:07:29: %LINK-3-UPDOWN: Interface GigabitEthernet7/14, changed state to up
Jun 22 23:07:30: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/36, changed state to up
Jun 22 23:07:30: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet7/14, changed state to up
Jun 22 23:07:34: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/36, changed state to down
Jun 22 23:07:35: %LINK-3-UPDOWN: Interface GigabitEthernet4/36, changed state to down
Jun 22 23:07:36: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi6/23 and vlan 25, the non-cumulative packet dropped count is 1.
Jun 22 23:07:39: %LINK-3-UPDOWN: Interface GigabitEthernet4/36, changed state to up
Jun 22 23:07:40: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet7/14, changed state to down
Jun 22 23:07:40: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/36, changed state to up
Jun 22 23:07:41: %LINK-3-UPDOWN: Interface GigabitEthernet7/14, changed state to down
Jun 22 23:08:21: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi3/44 and vlan 25, the non-cumulative packet dropped count is 1.
Jun 22 23:08:22: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet7/14, changed state to up
Jun 22 23:08:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet7/14, changed state to down
Jun 22 23:08:35: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet7/14, changed state to up
Jun 22 23:08:38: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet7/14, changed state to down
Jun 22 23:09:06: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi3/47 and vlan 25, the non-cumulative packet dropped count is 1.
Jun 22 23:09:28: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/36, changed state to down
Jun 22 23:09:29: %LINK-3-UPDOWN: Interface GigabitEthernet4/36, changed state to down
Jun 22 23:09:33: %LINK-3-UPDOWN: Interface GigabitEthernet4/36, changed state to up
Jun 22 23:09:34: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/36, changed state to up
Jun 22 23:09:40: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/36, changed state to down
Jun 22 23:09:41: %LINK-3-UPDOWN: Interface GigabitEthernet4/36, changed state to down
Jun 22 23:09:45: %LINK-3-UPDOWN: Interface GigabitEthernet4/36, changed state to up
Jun 22 23:09:46: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/36, changed state to up
Jun 22 23:09:50: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet7/14, changed state to up
Jun 22 23:09:50: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/36, changed state to down
Jun 22 23:09:51: %LINK-3-UPDOWN: Interface GigabitEthernet4/36, changed state to down
Jun 22 23:09:51: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi3/47 and vlan 25, the non-cumulative packet dropped count is 1.
Jun 22 23:09:53: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet7/14, changed state to down
Jun 22 23:09:55: %LINK-3-UPDOWN: Interface GigabitEthernet4/36, changed state to up
Jun 22 23:09:56: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/36, changed state to up
Jun 22 23:10:21: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi3/47 and vlan 25, the non-cumulative packet dropped count is 1.
Jun 22 23:11:06: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi3/44 and vlan 25, the non-cumulative packet dropped count is 1.
Jun 22 23:11:43: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/36, changed state to down
Jun 22 23:11:44: %LINK-3-UPDOWN: Interface GigabitEthernet4/36, changed state to down
Jun 22 23:11:48: %LINK-3-UPDOWN: Interface GigabitEthernet4/36, changed state to up
Jun 22 23:11:49: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/36, changed state to up
Jun 22 23:11:51: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi3/47 and vlan 25, the non-cumulative packet dropped count is 1.
Jun 22 23:11:55: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/36, changed state to down
Jun 22 23:11:56: %LINK-3-UPDOWN: Interface GigabitEthernet4/36, changed state to down
Jun 22 23:12:00: %LINK-3-UPDOWN: Interface GigabitEthernet4/36, changed state to up
Jun 22 23:12:01: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/36, changed state to up
Jun 22 23:12:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/36, changed state to down
Jun 22 23:12:06: %LINK-3-UPDOWN: Interface GigabitEthernet4/36, changed state to down
Jun 22 23:12:10: %LINK-3-UPDOWN: Interface GigabitEthernet4/36, changed state to up
Jun 22 23:12:11: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet4/36, changed state to up
Jun 22 23:12:16: %LINK-3-UPDOWN: Interface GigabitEthernet7/14, changed state to up
Jun 22 23:12:17: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet7/14, changed state to up
Jun 22 23:12:18: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet7/14, changed state to down
Jun 22 23:12:19: %LINK-3-UPDOWN: Interface GigabitEthernet7/14, changed state to down
Jun 22 23:12:21: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi3/47 and vlan 25, the non-cumulative packet dropped count is 1.
Jun 22 23:13:06: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi3/47 and vlan 25, the non-cumulative packet dropped count is 1.
Jun 22 23:13:23: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet7/14, changed state to up
Jun 22 23:13:26: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet7/14, changed state to down
Jun 22 23:13:36: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi3/47 and vlan 25, the non-cumulative packet dropped count is 1.
Jun 22 23:14:21: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi3/47 and vlan 25, the non-cumulative packet dropped count is 1.
Jun 22 23:15:06: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi3/47 and vlan 25, the non-cumulative packet dropped count is 1.
Jun 22 23:15:51: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi3/47 and vlan 25, the non-cumulative packet dropped count is 1.
Jun 22 23:16:21: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi3/47 and vlan 25, the non-cumulative packet dropped count is 1.
Jun 22 23:17:06: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi3/47 and vlan 25, the non-cumulative packet dropped count is 1.
Jun 22 23:17:36: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi3/44 and vlan 25, the non-cumulative packet dropped count is 1.
Jun 22 23:17:40: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet7/14, changed state to up
Jun 22 23:17:43: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet7/14, changed state to down
Jun 22 23:18:21: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi3/44 and vlan 25, the non-cumulative packet dropped count is 1.
Jun 22 23:18:51: %IP_SOURCE_GUARD-4-DENY_INVALID_PACKET: Detected and dropped illegal traffic on port Gi3/47 and vlan 25, the non-cumulative packet dropped count is 1.
C4507_TB_P3#          

 

 

 

Loading.
Ricardo Prado Rueda Mar, 06/24/2014 - 07:59
User Badges:
  • Cisco Employee,
  • Events Top Contributors,

    Cisco, 2014

El principal componente de la utilización de CPU son los procesos de baja prioridad del equipo (Cat4k Mgmt LoPri). Como su nombre lo indica son procesos que no interrumpirían la operación de forwarding de tráfico, ya que esta función es de alta prioridad. Para encontrar más información de qué procesos de baja prioridad están corriendo necesitas revisar la salida del comando "show platform health". Una explicación de esta actividad está en el siguiente link:

 

http://www.cisco.com/c/en/us/support/docs/switches/catalyst-4000-series-...

 

Ahora, dentro de los procesos de baja prioridad se encuentra el aprender direcciones MAC de tráfico que pasa a través del equipo. De acuerdo con tu log, tienes varias interfaces que están flapeando y algunos eventos de seguridad que pueden estar mandando interfaces a un estado de err-disable. Estas acciones hacen que el equipo tenga que volver aprender información MAC o de ARP en dichas interfaces y, por lo tanto, incrementar la utilización de CPU por procesos de baja prioridad. Yo revisaría ese tráfico que se está detectando y bloqueando así como las interfaces que están flapeando en el equipo ya sea por problemas de capa 1 ó capa 2. La utilización de CPU parece ser consecuencia y no causa de los logs presentes en tu equipo.

Caleb Quiros Lun, 07/07/2014 - 13:38
User Badges:
  • Cisco Employee,

Hi,

 

Could you please share the following outputs;

 

show module

show platform health

 

Regards,

 

Caleb Quiros

Acciones

Este Discusión