- Community Home
- >
- Networking
- >
- IMC
- >
- iMC 7.3 causes high cpu utilization on HP 10508V a...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2018 03:25 AM
05-11-2018 03:25 AM
I recognized that HP iMC 7.3 (E0506P09) consumes high CPU usage when it runs snmp agent on HP 10508V and 5400 series (5406zl and 5412zl) switches in the network.
Is there any solution to fix this issue?
Here is the tech log of 10508V:
[10508V]display diagnostic-information Save or display diagnostic information (Y=save, N=display)? [Y/N]:n ================================================================= ===============running CPU usage information=============== ================================================================= ===== Current CPU usage info ===== CPU Usage Stat. Cycle: 50 (Second) CPU Usage : 98% CPU Usage Stat. Time : 2018-05-08 10:38:24 CPU Usage Stat. Tick : 0x153cd7(CPU Tick High) 0x2b0e2188(CPU Tick Low) Actual Stat. Cycle : 0x0(CPU Tick High) 0xc7bc2ecf(CPU Tick Low) TaskName CPU Runtime(CPU Tick High/CPU Tick Low) VIDL 2% 0/ 5ec6672 TICK 0% 0/ 1562a29 STMR 0% 0/ 38f173 RECV 1% 0/ 2e12836 DSTK 0% 0/ a68d3 DDEV 0% 0/ 29babf bDPC 0% 0/ 14510 L2X0 1% 0/ 3585dc0 bC.0 1% 0/ 2a36d3d bLK0 0% 0/ 1b16612 DQFD 0% 0/ 102e6e DQIT 1% 0/ 21e31cd LPDT 0% 0/ bbd STAT 0% 0/ 8ce95 FMCK 0% 0/ 63d3f T_DM 0% 0/ 89f07 mIPC 0% 0/ 78539 T_VA 0% 0/ 11e72 DARP 0% 0/ 8e331 TPBR 0% 0/ 1247ee BGRT 0% 0/ 1a5500 MARP 0% 0/ 832c9 VMAC 0% 0/ 1284a SCAR 0% 0/ 301d9 RTMC 0% 0/ 41f570 bRX1 6% 0/ c5f9f29 bRX2 0% 0/ 80ff7c STKT 0% 0/ d75bee IUCT 0% 0/ 15700d5 SYRP 0% 0/ cb66a TSHL 0% 0/ 2a88f FANT 0% 0/ 14da3 TEMP 0% 0/ 16345c CHEK 0% 0/ 75f0 bIP0 0% 0/ 2b9c1 NSET 0% 0/ 4ed143 NSTM 0% 0/ 1db02 VP 0% 0/ 87c IPCB 2% 0/ 557fe15 IPCD 0% 0/ 1136e6 RPCQ 0% 0/ 12f8010 RPCD 0% 0/ 25bdb3 STM 0% 0/ 988fd1 STMH 0% 0/ 2a4833 IPCM 0% 0/ 1f0b2 INFO 0% 0/ 1568d HAMT 0% 0/ 84c HACT 0% 0/ aa0cb DEV 0% 0/ 7ef159 EXCP 0% 0/ 44d46 ADJ4 0% 0/ ac249 SFLW 0% 0/ 3742c ACL 0% 0/ 4804e mac 0% 0/ 19ff5 LAGG 0% 0/ 238f2 MSTP 0% 0/ 165f4e9 GARP 0% 0/ 118caa CLST 0% 0/ 6fce2 NDP 0% 0/ bac6e NTDP 0% 0/ 1f6ec HABP 0% 0/ 19102 CFD 0% 0/ 1a8798 EAIS 0% 0/ 1560d RRPP 0% 0/ 6a1e3 LLDP 0% 0/ 1e464d DLDP 0% 0/ 48ae8 SMLK 0% 0/ 21b3c ARP 7% 0/ fc0eeff IP 0% 0/ 83e61a FSLH 0% 0/ 1db03 FSLR 0% 0/ f7cfd NTPT 0% 0/ 4e754 VTYD 0% 0/ 214e87 DHCP 0% 0/ 2b7ffa ND 0% 0/ 2203fc AGNT 62% 0/7cc1d4e1 CWMP 0% 0/ 3f756 ACM 0% 0/ 23128f LS 0% 0/ e482e RDS 0% 0/ adc3e SC 0% 0/ 35228 NAT 0% 0/ 12ed9 BFD 0% 0/ 58dc20 MFIB 0% 0/ 310657 IGSP 3% 0/ 76263cb STND 0% 0/ 6e002 ROUT 0% 0/ a7d0b0 TNLM 0% 0/ 1c73b IFNT 0% 0/ 1dfda NETM 0% 0/ a0f74 vt0 1% 0/ 2a95c4a ================================================= ===============display clock=============== ================================================= 10:38:25 UTC Tue 05/08/2018 =================================================== ===============display version=============== =================================================== HP Comware Platform Software Comware Software, Version 5.20.105, Release 1208 Copyright (c) 2010-2013 Hewlett-Packard Development Company, L.P. HP 10508-V uptime is 148 weeks, 1 day, 19 hours, 47 minutes LPU Chassis 1 Slot 0: Uptime is 148 weeks,1 days,19 hours,38 minutes HP 10508-V LPU with 1 XLS408 Processor BOARD TYPE: LSU1GP24TSE0 DRAM: 1024M bytes FLASH: 0M bytes NVRAM: 0K bytes PCB 1 Version: VER.B Bootware Version: 511 CPLD 1 Version: 001 CPLD 2 Version: 002 Release Version: HP 10508-V-1208 Patch Version : None Chassis 1 Slot 1 Without Board LPU Chassis 1 Slot 2: Uptime is 148 weeks,1 days,19 hours,31 minutes HP 10508-V LPU with 1 XLS408 Processor BOARD TYPE: LSU1TGS16SC0 DRAM: 1024M bytes FLASH: 0M bytes NVRAM: 0K bytes PCB 1 Version: VER.B Bootware Version: 511 CPLD 1 Version: 003 CPLD 2 Version: 003 Release Version: HP 10508-V-1208 Patch Version : None LPU Chassis 1 Slot 3: Uptime is 148 weeks,1 days,19 hours,37 minutes HP 10508-V LPU with 1 XLS408 Processor BOARD TYPE: LSU1TGS16SC0 DRAM: 1024M bytes FLASH: 0M bytes NVRAM: 0K bytes PCB 1 Version: VER.B Bootware Version: 511 CPLD 1 Version: 003 CPLD 2 Version: 003 Release Version: HP 10508-V-1208 Patch Version : None MPU(M) Chassis 1 Slot 4: Uptime is 148 weeks,1 days,19 hours,47 minutes HP 10508-V MPU(M) with 1 XLS408 Processor BOARD TYPE: LSU1SUPA0 DRAM: 1024M bytes FLASH: 128M bytes NVRAM: 512K bytes PCB 1 Version: VER.A Bootware Version: 101 CPLD 1 Version: 003 CPLD 2 Version: 003 CPLD 3 Version: 003 Release Version: HP 10508-V-1208 Patch Version : None MPU(S) Chassis 1 Slot 5: Uptime is 148 weeks,1 days,19 hours,48 minutes HP 10508-V LPU with 1 XLS408 Processor BOARD TYPE: LSU1SUPA0 DRAM: 1024M bytes FLASH: 128M bytes NVRAM: 512K bytes PCB 1 Version: VER.A Bootware Version: 101 CPLD 1 Version: 003 CPLD 2 Version: 003 CPLD 3 Version: 003 Release Version: HP 10508-V-1208 Patch Version : None LPU Chassis 1 Slot 6: Uptime is 148 weeks,1 days,19 hours,50 minutes HP 10508-V LPU with 1 XLS408 Processor BOARD TYPE: LSU1TGS16SC0 DRAM: 1024M bytes FLASH: 0M bytes NVRAM: 0K bytes PCB 1 Version: VER.B Bootware Version: 511 CPLD 1 Version: 003 CPLD 2 Version: 003 Release Version: HP 10508-V-1208 Patch Version : None LPU Chassis 1 Slot 7: Uptime is 148 weeks,1 days,19 hours,46 minutes HP 10508-V LPU with 1 XLS408 Processor BOARD TYPE: LSU1TGS16SC0 DRAM: 1024M bytes FLASH: 0M bytes NVRAM: 0K bytes PCB 1 Version: VER.B Bootware Version: 511 CPLD 1 Version: 003 CPLD 2 Version: 003 Release Version: HP 10508-V-1208 Patch Version : None Chassis 1 Slot 8 Without Board LPU Chassis 1 Slot 9: Uptime is 148 weeks,1 days,19 hours,41 minutes HP 10508-V LPU with 1 XLS408 Processor BOARD TYPE: LSU1GT48SE0 DRAM: 1024M bytes FLASH: 0M bytes NVRAM: 0K bytes PCB 1 Version: VER.B Bootware Version: 202 CPLD 1 Version: 003 Release Version: HP 10508-V-1208 Patch Version : None LPU Chassis 1 Slot 10: Uptime is 148 weeks,1 days,19 hours,39 minutes HP 10508-V LPU with 1 XLS404 Processor BOARD TYPE: LSU1FAB08A0 DRAM: 1024M bytes FLASH: 0M bytes NVRAM: 0K bytes PCB 1 Version: VER.B Bootware Version: 511 CPLD 1 Version: 003 Release Version: HP 10508-V-1208 Patch Version : None LPU Chassis 1 Slot 11: Uptime is 148 weeks,1 days,19 hours,44 minutes HP 10508-V LPU with 1 XLS404 Processor BOARD TYPE: LSU1FAB08A0 DRAM: 1024M bytes FLASH: 0M bytes NVRAM: 0K bytes PCB 1 Version: VER.B Bootware Version: 511 CPLD 1 Version: 003 Release Version: HP 10508-V-1208 Patch Version : None LPU Chassis 1 Slot 12: Uptime is 148 weeks,1 days,19 hours,40 minutes HP 10508-V LPU with 1 XLS404 Processor BOARD TYPE: LSU1FAB08A0 DRAM: 1024M bytes FLASH: 0M bytes NVRAM: 0K bytes PCB 1 Version: VER.B Bootware Version: 511 CPLD 1 Version: 003 Release Version: HP 10508-V-1208
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2018 08:35 AM
05-11-2018 08:35 AM
SolutionSounds more like a problem with the switch rather than IMC. Check the versions & release notes for the switch software to see if there's anything there about fixed SNMP agent issues.