OPERATIONAL DEFECT DATABASE
...
...
vEdge1000 just upgraded to 20.6.5 is reporting high CPU utilization up to 100% every 30 minutes. Feb 9 16:04:07 vEdge SYSMGR[669]: %Viptela-USPIA-P-SDW002-SYSMGR-2-CRIT-200069: System cpu usage is above 90% (critically high) Feb 9 16:04:08 vEdge SYSMGR: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND Feb 9 16:04:08 vEdge SYSMGR: root 22045 30.0 0.1 8476 4168 ? Rs 16:04 0:00 [vconfd_netconf_] Feb 9 16:04:08vEdge SYSMGR: root 22049 29.0 0.1 8476 4092 ? Rs 16:04 0:00 [vconfd_netconf_] Feb 9 16:04:08 vEdge SYSMGR: root 21996 10.7 0.1 8476 4160 ? Ss 16:04 0:00 [vconfd_netconf_] Feb 9 16:04:08 vEdge SYSMGR: root 21997 10.7 0.1 8476 4300 ? Ss 16:04 0:00 [vconfd_netconf_] Feb 9 16:04:08 vEdge SYSMGR: root 21986 8.2 0.2 9692 7080 ? Ss 16:04 0:00 sshd: vmanage-admin [priv] Feb 9 16:04:08 vEdge SYSMGR: root 21987 8.2 0.2 9692 7084 ? Ss 16:04 0:00 sshd: vmanage-admin [priv] Feb 9 16:04:08 vEdge root 21951 4.7 0.2 9692 7116 ? Ss 16:04 0:00 sshd: vmanage-admin [priv] Feb 9 16:04:08 vEdge[669]: vconfd_send_snmp_v3_msg[215]: n_target_names(0) <= 0, nothing to send Feb 9 16:04:08 vEdge SYSMGR[669]: %Viptela-vEdge-sysmgrd-6-INFO-1400002: Notification: cpu-usage severity-level:critical host-name:"vEdge" system-ip:1.1.1.39 warning:"System cpu usage is above 90% (critically high)" cpu-user-percentage:"10.95" cpu-system-percentage:"88.56" cpu-idle-percentage:"0.50"
Router has DPI enabled, but so far, it hasn't been determined this a trigger condition. Due to the periodicity, it seems to be a pre schedule task coming from vManage since two mainly processes have been detected spiking the CPU: +sshd +vconfd In some occasions FTMd also have seen as spiker.
None at the moment.
/var/log/messages, /var/log/vsyslog and /var/log/vsyslog can provide more information on the list of processes requesting CPU cycles as well as the average CPU utilization in 1min,5min sampling.
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
