01-26-2014 10:49 PM - edited 03-07-2019 05:48 PM
Dear All,
I have a cisco switch WS-C3750X-48T .During the operation of this switch i have the issue of high cpu utilization .
please suggest the major reason due to which the switch behave like this and what is the problem with switch.
please find the attached log ....
UG-GW-CORE#sh proc cpu | e 0.00
CPU utilization for five seconds: 34%/1%; one minute: 36%; five minutes: 36%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
10 833688 1686490 494 0.31% 0.71% 0.63% 0 ARP Input
69 144766 30391 4763 0.15% 0.13% 0.11% 0 Compute load avg
74 4470389 735065 6081 2.86% 2.75% 2.77% 0 RedEarth Tx Mana
80 1068811 60462 17677 0.79% 0.70% 0.65% 0 Adjust Regions
116 2567337 295705 8682 1.58% 1.55% 1.56% 0 hpm counter proc
156 24497604 2908539 8422 15.57% 14.80% 14.65% 0 Hulc LED Process
167 546741 30415 17976 0.31% 0.31% 0.31% 0 HQM Stack Proces
198 604538 1052522 574 0.31% 0.58% 0.55% 0 IP Input
217 8967911 1674951 5354 6.04% 5.16% 5.23% 0 Spanning Tree
Solved! Go to Solution.
01-28-2014 02:06 AM
Madhuraj,
Most of the IOS images on this platform have this bug, and even if you upgrade you might see the same issue again.
So as a workaround to reduce the CPU consumption of this process, go ahead and shut down all unused interfaces, and it might bring down the CPU consumed due to HULC LED little bit.
The High CPU consumption because of HULC LED process won't imact your network at all.
Thanks
Ankur
"Please rate the post if found useful"
01-27-2014 01:32 PM
Hi,
This issue can be due to Hulc LED Process:
Hulc LED Process - Is responsible for link status detection.
Symptom:
Hulc LED Process uses 15-30% CPU on Catalyst 3560X/3750X platforms.
Conditions:
The is seen in 12.2(53)SE releases or later.
Workaround:
This is an expected behavior and there is no workaround.
Further Problem Description:
The "Hulc LED" process does following tasks:
- Check Link status on every port
- If the switch supports POE, it checks to see if there is a Power Device (PD) detected
- Check the status of the transceiver
- Update Fan status
- Set Main LED and ports LEDs
- Update both Power Supplies and RPS
- Check on system temperature status
Bug details at :
Hence, this is expected behavior and you should not worry about it. As per what I can see your switch has a 34% of cpu usage which should not cause any issues, it is normal.
Hope this helps, and remember to rate any useful posts.
01-27-2014 10:52 PM
Hi Leo ,
Thanks for your answer ....
Current IOS version is 12.2.(55) SE
please suggest with good one ......
Message was edited by: Madhuraj singh kushwah
01-28-2014 02:06 AM
Madhuraj,
Most of the IOS images on this platform have this bug, and even if you upgrade you might see the same issue again.
So as a workaround to reduce the CPU consumption of this process, go ahead and shut down all unused interfaces, and it might bring down the CPU consumed due to HULC LED little bit.
The High CPU consumption because of HULC LED process won't imact your network at all.
Thanks
Ankur
"Please rate the post if found useful"
01-29-2014 08:04 AM
Thanks Ankur ,
Now the switch cpu utilization has reduced up to 15 %
now it is 25 % from 36%
Can I further reduced it .the cpu utilization is given below.
There is one more concern that i have configure the access list on switch in which i get logs for every packet.
if i disable the log on switch then can it will work so that cpu utilization reduce....
the logs is mention below-----
UG-GW-CORE#sh processes cpu | e 0.00
CPU utilization for five seconds: 27%/0%; one minute: 25%; five minutes: 25%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
10 2011986 3778260 532 0.63% 0.78% 0.76% 0 ARP Input
38 115380 336632 342 0.15% 0.10% 0.10% 0 Per-Second Jobs
39 178717 5727 31206 0.63% 0.07% 0.01% 0 Per-minute Jobs
73 761745 2470458 308 0.63% 0.51% 0.49% 0 RedEarth I2C dri
74 9815543 1633880 6007 2.55% 2.76% 2.72% 0 RedEarth Tx Mana
80 2406932 134778 17858 0.63% 0.65% 0.65% 0 Adjust Regions
83 217118 1048444 207 0.15% 0.07% 0.05% 0 hrpc <- response
96 282851 9460989 29 0.47% 0.28% 0.27% 0 HLFM address lea
116 5782765 658830 8777 1.59% 1.68% 1.65% 0 hpm counter proc
156 47830340 6784646 7049 4.63% 4.48% 4.58% 0 Hulc LED Process
157 137114 248278 552 0.15% 0.07% 0.05% 0 HL3U bkgrd proce
167 1220864 67698 18033 0.47% 0.40% 0.36% 0 HQM Stack Proces
168 432016 270478 1597 0.15% 0.15% 0.15% 0 HRPC qos request
186 922785 329956 2796 2.55% 0.37% 0.27% 0 CDP Protocol
198 1819965 2655418 685 0.95% 1.07% 1.00% 0 IP Input
204 311684 1261478 247 0.47% 0.23% 0.21% 0 ADJ resolve proc
217 14968786 5172271 2894 2.71% 2.70% 2.88% 0 Spanning Tree
253 128390 256773 500 0.15% 0.04% 0.03% 0 TCP Protocols
317 137640 523279 263 0.15% 0.13% 0.11% 0 CEF: IPv4 proces
343 249372 1969676 126 0.31% 0.17% 0.16% 0 EIGRP-IPv4 Hello
348 92 178 516 0.31% 0.12% 0.03% 2 Virtual Exec
UG-GW-CORE#sh loggin
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)
No Active Message Discriminator.
No Inactive Message Discriminator.
Console logging: level debugging, 795 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 6 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 795 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
File logging: disabled
Persistent logging: disabled
No active filter modules.
Trap logging: level informational, 808 message lines logged
Logging to 10.10.10.66 (udp port 514, audit disabled,
authentication disabled, encryption disabled, link up),
808 message lines logged,
0 message lines rate-limited,
0 message lines dropped-by-MD,
xml disabled, sequence number disabled
filtering disabled
Log Buffer (4096 bytes):
ted 10.11.35.103 302 packets
.Jan 27 10:26:32.934 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 10:31:33.559 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 10:36:34.561 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 300 packets
.Jan 27 10:41:35.084 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 10:46:35.700 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 300 packets
.Jan 27 10:51:36.358 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 10:56:36.974 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 11:01:37.783 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 300 packets
.Jan 27 11:06:38.365 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 11:11:39.006 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 300 packets
.Jan 27 11:16:39.647 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 11:21:40.574 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 11:26:41.072 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 300 packets
.Jan 27 11:31:41.705 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 300 packets
.Jan 27 11:36:42.363 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 300 packets
.Jan 27 11:41:43.247 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 11:43:30.958 IST: %SYS-5-CONFIG_I: Configured from console by ugamnet on vty1 (10.11.35.103)
.Jan 27 11:44:38.318 IST: %SYS-5-CONFIG_I: Configured from console by ugamnet on vty1 (10.11.35.103)
.Jan 27 11:46:43.888 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 11:51:44.504 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 300 packets
.Jan 27 11:56:45.145 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 12:01:45.770 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 300 packets
.Jan 27 12:06:46.377 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 12:11:46.976 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 12:16:47.567 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 300 packets
.Jan 27 12:21:48.393 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 12:24:21.796 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.10.8.65 1 packet
.Jan 27 12:26:48.841 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 12:29:49.189 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.10.8.65 1 packet
.Jan 27 12:31:49.440 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 300 packets
.Jan 27 12:34:49.754 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.10.8.65 2 packets
.Jan 27 12:36:49.989 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 12:41:50.865 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 300 packets
.Jan 27 12:46:51.355 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 12:51:51.963 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 12:56:52.570 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 300 packets
.Jan 27 13:01:53.161 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 13:06:53.777 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 13:11:54.359 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 300 packets
.Jan 27 13:16:55.227 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
.Jan 27 13:21:55.784 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 300 packets
.Jan 27 13:26:56.392 IST: %SEC-6-IPACCESSLOGS: list access-in permitted 10.11.35.103 298 packets
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide