본문 바로가기

Ryu's Tech

시스코 장비의 process 중 Hulc Led Process 가 높은 비중을 차지할 때

이 내용은 2012년에 작성했던 내용이네요.

특정 장비의 CPU가 높게 나와 확인 해보니 Hulc LED Process 가 높게 나왔었는데요

지금은 조금 내려간 값이고 당시에는 거의 50% 정도 CPU가 차던 기억이 나는데… 확실하게 기억이 안나네요

   

   

Switch#show process cpu sorted

CPU utilization for five seconds: 22%/0%; one minute: 21%; five minutes: 21%

PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process

139 71726174 11800374 6078 13.29% 13.24% 13.30% 0 Hulc LED Process

4 4508098 253413 17789 1.09% 1.02% 0.79% 0 Check heaps

108 4007592 562832 7120 0.59% 0.70% 0.69% 0 hpm counter proc

306 120 131 916 0.59% 0.13% 0.03% 3 Virtual Exec

69 1135016 5278798 215 0.49% 0.15% 0.11% 0 RedEarth Tx Mana

37 475752 562980 845 0.39% 0.13% 0.10% 0 Per-Second Jobs

178 121802 657399 185 0.29% 0.12% 0.10% 0 IP Input

193 602539 1121594 537 0.29% 0.23% 0.20% 0 Spanning Tree

304 2190 775 2825 0.29% 0.02% 0.00% 1 Virtual Exec

148 1193191 113441 10518 0.19% 0.19% 0.19% 0 HQM Stack Proces

250 980611 1514797 647 0.09% 0.07% 0.09% 0 Inline Power

90 87534 15886981 5 0.09% 0.00% 0.00% 0 HLFM address ret

   

아무튼 위와 같은 경우가 발생하면 아래 표에서 보시는 것처럼

물리 링크가 Flapping (죽었다가 살았다가 반복) 되는 경우가 대부분이고 로그나 물리적인 인터페이스를 살펴 보는 것으로 해결하시면 됩니다.

   

Process Name

Percentage of Active Resources

  

Possible Root Cause

Suggested Action

  

Normal

Considered High

  

  

Hulc LED Process

0 to 2 %

24 ports or less:

More than 5 %

48 ports: More than 8 %

Physical link flapping.

Review the syslog for a physical link losing and gaining connectivity.

Inline Power Twt

0

More than 5 %

Bad power supply.

Review the syslog for reports of a failed power controller.

HACL

0

More than 50 %

Too many ACLs configured on the switch in a short time period. This can occur when the ACLs are being applied in an automated fashion (from a script).

Consider changing the SDM template.

SNMP Engine

0

More than 40%

See the "SNMP Engine Process" section.

  

Table 3 System Processes that Consume CPU Resources

   

출처: <http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/troubleshooting/cpu_util.html>