3750 Switch Showing High CPU Utilization

Unanswered Question
Apr 20th, 2010
User Badges:

Hi all



We have around 40no.s 3750 switches.Almost all the switches is showing high cpu utilization


Any one faced the issue for 3750 switch facing high cpu utilization..


regards

-Danish

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
danishahammed015 Tue, 04/20/2010 - 05:50
User Badges:

Hi Fran


Thanks for your immediate reply


Pls find attached logs which is showing  cpu utilization.


Could you pls confirm it will show in the logs as well.


Thanks

-Danish

Attachment: 
francisco_1 Tue, 04/20/2010 - 05:58
User Badges:
  • Gold, 750 points or more

Please capture and upload


show stack 319

francisco_1 Tue, 04/20/2010 - 06:00
User Badges:
  • Gold, 750 points or more

sorry the command is "show stacks 319"

francisco_1 Tue, 04/20/2010 - 06:09
User Badges:
  • Gold, 750 points or more

are your 3750 switches stacked?

francisco_1 Tue, 04/20/2010 - 06:14
User Badges:
  • Gold, 750 points or more

Danish,


It is not a bug or to do with your configuation. It is common to see the hulc proccess using high CPU  If Catalyst 3750 Switches are connected in a stack. How it works is if there are any configuration changes made to a switch, the hulc running config process wakes up and generates a new copy of the running configuration. Then, it sends to all the switches in the stack. The new running configuration is CPU-intensive. Therefore, the CPU usage is high when building a new running configuration process and when forwarding the new configurations to other switches. However, this high CPU usage should exist only for the same amount of time it takes to perform the building configuration step of the show running-configuration command.


There is no need of a workaround for this problem. The CPU usage is normally high in these situations.


This is a sample output of the show processes cpu command when the CPU utilization is high due to the hulc running process:

switch#show processes cpu 

CPU utilization for five seconds: 63%/0%; one minute: 27%; five minutes: 23%      

 PID  Runtime(ms)     Invoked   uSecs          5Sec   1Min   5Min    TTY    Process
   1      384            32789      11             0.00%  0.00%   0.00%   0    Load Meter 
   2     2752            1179    2334          0.73%  1.06%   0.29%   0    Exec 
   3   318592             5273   60419           0.00%  0.15%   0.17%   0    Check heaps 
   4        4               1    4000             0.00%  0.00%   0.00%   0    Pool Manager 
   5     6472           6568     985          0.00%  0.00%   0.00%   0    ARP Input 
   6    10892            9461    1151          0.00%  0.00%   0.00%   0    IGMPSN
   7    67388           53244    1265          0.16%  0.04%   0.02%   0    CDP Protocol 
   8   145520             166455     874            0.40%  0.29%   0.29%   0    IP Background 
   9     3356             1568    2140           0.08%  0.00%   0.00%   0    BOOTP Server 
  10       32             5469       5           0.00%  0.00%   0.00%   0    Net Background 
  11    42256             163623     258            0.16%  0.02%   0.00%   0    Per-Second Jobs 
  12   189936             163623    1160            0.00%  0.04%   0.05%   0    Net Periodic 
  13     3248             6351     511           0.00%  0.00%   0.00%   0    Net Input 
  14      168              32790       5           0.00%  0.00%   0.00%   0    Compute load avgs 
  15   152408             2731   55806           0.98%  0.12%   0.07%   0    Per-minute Jobs 
  16         0                 1         0           0.00%  0.00%   0.00%   0    HRPC h12mm reque
  17    85964            426    201793          55.72% 12.05%  5.36%   0    hulc running

Actions

This Discussion