high cpu utilisation HPE5800 - high VIDL, bRX1

[Eby]

I'm facing high cpu usage on HPE5800 48Port, during the day it is above 95% and comes down to somewhat 70% during night. This wasn't the case till a month ago, the average used to be less than 20% and no changes to the network been made and no loops.

[CORESW_IDC_1-hidecmd]disp cpu-usage task slot 1 cpu 0
===== Current CPU usage info =====
CPU Usage Stat. Cycle: 6 (Second)
CPU Usage            : 100%
CPU Usage Stat. Time : 2019-01-03  16:50:41
CPU Usage Stat. Tick : 0xc4358(CPU Tick High) 0x6234bdb5(CPU Tick Low)
Actual Stat. Cycle   : 0x0(CPU Tick High) 0x18e4788e(CPU Tick Low)

TaskName        CPU        Runtime(CPU Tick High/CPU Tick Low)
bRX1            60%               0/ f00366f
SOCK            24%               0/ 6006ff8

 Rest of the tasks consuming 0 or less than 3% of the cpu.

[CORESW_IDC_1-hidecmd]disp cpu-usage task slot 1 cpu 1
===== Current CPU usage info =====
CPU Usage Stat. Cycle: 57 (Second)
CPU Usage            : 1%
CPU Usage Stat. Time : 2019-01-03  16:54:54
CPU Usage Stat. Tick : 0xc435c(CPU Tick High) 0x4fc6323f(CPU Tick Low)
Actual Stat. Cycle   : 0x0(CPU Tick High) 0xe2b73f44(CPU Tick Low)

TaskName        CPU        Runtime(CPU Tick High/CPU Tick Low)
VIDL            99%               0/e1064b0e

Any idea what might be the cause ?. And what are the functions of VIDL and SOCK?.

[akg7]

Hi,

Could you plwase share the output of below:

display version

display logbuffer reverse

Thanks!

[Northwoods]

VIDL = the higher this is, the more idle the device is...higher is better

bRX1 - broadcast receiving high.....possible loop or other traffic causing large amounts of broadcast traffic.

[Eby]

I have disabled info-center, sflow and snmp, assuming these can cause high cpu utilisation. But it is not.

<CORESW_IDC_1>disp version
HP Comware Platform Software
Comware Software, Version 5.20, Release 1211P09
Copyright (c) 2010-2012 Hewlett-Packard Development Company, L.P.
HP A5800-48G-PoE+ Switch with 2 Interface Slots uptime is 86 weeks, 4 days, 2 hs

HP A5800-48G-PoE+ Switch with 2 Interface Slots with 2 Processors
1024M   bytes SDRAM
4M      bytes Nor Flash Memory
512M    bytes Nand Flash Memory
Config Register points to Nand Flash

Hardware Version is Ver.C
CPLDA Version is 003, CPLDB Version is 003
BootRom Version is 215
[SubSlot 0] 48GE+4SFP Hardware Version is Ver.C
[SubSlot 1] No Module
[SubSlot 2] No Module
[SubSlot 3] No Module
[SubSlot 4] No Module

<CORESW_IDC_1>

[Eby]

<CORESW_IDC_1>disp logbuffer reverse
Logging buffer configuration and contents:enabled
Allowed max buffer size : 1024
Actual buffer size : 1024
Channel number : 4 , Channel name : logbuffer
Dropped messages : 0
Overwritten messages : 20119620
Current messages : 1024

%Jan  3 15:26:56:774 2019 CORESW_IDC_1 SC/6/SC_AAA_SUCCESS: -AAAType=ACCOUNT-AA.
%Jan  3 15:26:56:501 2019 CORESW_IDC_1 SC/6/SC_AAA_LAUNCH: -AAAType=ACCOUNT-AAA.
%Jan  3 15:26:56:478 2019 CORESW_IDC_1 SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=172.e
%Jan  3 15:26:56:454 2019 CORESW_IDC_1 SC/6/SC_AAA_SUCCESS: -AAAType=AUTHOR-AAA.
%Jan  3 15:26:56:151 2019 CORESW_IDC_1 SC/6/SC_AAA_LAUNCH: -AAAType=AUTHOR-AAAS.
%Jan  3 15:25:31:816 2019 CORESW_IDC_1 SNMP/6/SNMP_GET: -seqNO=<19651988>-srcIP;

%Jan  3 15:25:02:957 2019 CORESW_IDC_1 SNMP/6/SNMP_GET: -seqNO=<19651915>-srcIP;
%Jan  3 15:24:26:704 2019 CORESW_IDC_1 SC/6/SC_AAA_SUCCESS: -AAAType=ACCOUNT-AA.
%Jan  3 15:24:26:419 2019 CORESW_IDC_1 SC/6/SC_AAA_LAUNCH: -AAAType=ACCOUNT-AAA.
%Jan  3 15:24:26:402 2019 CORESW_IDC_1 SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=172.r
%Jan  3 15:24:26:346 2019 CORESW_IDC_1 SC/6/SC_AAA_SUCCESS: -AAAType=AUTHOR-AAA.
%Jan  3 15:24:26:053 2019 CORESW_IDC_1 SC/6/SC_AAA_LAUNCH: -AAAType=AUTHOR-AAAS.
%Jan  3 15:24:13:649 2019 CORESW_IDC_1 SC/6/SC_AAA_SUCCESS: -AAAType=ACCOUNT-AA.
%Jan  3 15:24:13:396 2019 CORESW_IDC_1 SC/6/SC_AAA_LAUNCH: -AAAType=ACCOUNT-AAA.
%Jan  3 15:24:13:374 2019 CORESW_IDC_1 SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=172.s
%Jan  3 15:24:13:328 2019 CORESW_IDC_1 SC/6/SC_AAA_SUCCESS: -AAAType=AUTHOR-AAA.
%Jan  3 15:24:13:046 2019 CORESW_IDC_1 SC/6/SC_AAA_LAUNCH: -AAAType=AUTHOR-AAAS.
%Jan  3 15:24:07:998 2019 CORESW_IDC_1 SHELL/5/SHELL_LOGIN: eby.mani logged in .
%Jan  3 15:24:07:976 2019 CORESW_IDC_1 SC/6/SC_AAA_SUCCESS: -AAAType=ACCOUNT-AA.
%Jan  3 15:24:07:682 2019 CORESW_IDC_1 SC/6/SC_AAA_LAUNCH: -AAAType=ACCOUNT-AAA.
%Jan  3 15:24:07:644 2019 CORESW_IDC_1 SC/6/SC_AAA_SUCCESS: -AAAType=AUTHOR-AAA.
%Jan  3 15:24:07:308 2019 CORESW_IDC_1 SC/6/SC_AAA_LAUNCH: -AAAType=AUTHOR-AAAS.
%Jan  3 15:24:07:308 2019 CORESW_IDC_1 SC/6/SC_AAA_SUCCESS: -AAAType=AUTHEN-AAA.
%Jan  3 15:24:06:956 2019 CORESW_IDC_1 SC/6/SC_AAA_LAUNCH: -AAAType=AUTHEN-AAAS.
%Jan  3 15:22:29:309 2019 CORESW_IDC_1 SNMP/6/SNMP_GET: -seqNO=<19651914>-srcIP;

%Jan  3 15:20:02:864 2019 CORESW_IDC_1 SNMP/6/SNMP_GET: -seqNO=<19651839>-srcIP;
%Jan  3 15:18:07:725 2019 CORESW_IDC_1 IC/5/IC_SECLOG_USAGEHIGH: The usage of s.
%Jan  3 15:17:29:338 2019 CORESW_IDC_1 SNMP/6/SNMP_GET: -seqNO=<19651838>-srcIP;

%Jan  3 15:10:02:500 2019 CORESW_IDC_1 SNMP/6/SNMP_GET: -seqNO=<19651687>-srcIP;
%Jan  3 15:08:07:707 2019 CORESW_IDC_1 IC/5/IC_SECLOG_USAGEHIGH: The usage of s.


%Jan  3 15:00:02:583 2019 CORESW_IDC_1 SNMP/6/SNMP_GET: -seqNO=<19651535>-srcIP;
%Jan  3 14:58:07:745 2019 CORESW_IDC_1 IC/5/IC_SECLOG_USAGEHIGH: The usage of s.
%Jan  3 14:57:29:077 2019 CORESW_IDC_1 SNMP/6/SNMP_GET: -seqNO=<19651534>-srcIP;

%Jan  3 14:50:02:491 2019 CORESW_IDC_1 SNMP/6/SNMP_GET: -seqNO=<19651383>-srcIP;
%Jan  3 14:48:07:703 2019 CORESW_IDC_1 IC/5/IC_SECLOG_USAGEHIGH: The usage of s.
%Jan  3 14:47:30:010 2019 CORESW_IDC_1 SNMP/6/SNMP_GET: -seqNO=<19651382>-srcIP;

%Jan  3 14:40:03:209 2019 CORESW_IDC_1 SNMP/6/SNMP_GET: -seqNO=<19651230>-srcIP;
%Jan  3 14:38:07:744 2019 CORESW_IDC_1 IC/5/IC_SECLOG_USAGEHIGH: The usage of s.

<CORESW_IDC_1> 

Deleted some lines to fix "Message cannot exceed 25,000 characters." issue here.

[akg7]

Hi,

Thank You for providing the informtion !

As I have seen, the device is running on very old firmware (2012) and it is always advisable to upgrade it to latest version because some issues related to High CPU is covered in latest version.

If problem remains after the upgrade then kindly log a case with support.

Thanks!