Observed spikes can be displayed by two signs on sh proc cpu history": asterisk "*" of number sign (#)
Asterisk peaks means peak load which can last evel less than a second - but if it happens it will be shown int 60 sec diagram, and other diagrams, such peaks hard to troubleshoot as they're very short and even EEM not always can catch them. Also most of such spikes are caused by nx-os components running on the box: snmp, tacacs etc are snmp intensive processes and can cause such spikes.
Spikes displayed with number sign (#) reflect average load - and are more relevant to load on the box, they can be captured by EEM.
As Kruh said EEM is most convenient way to capture such spikes, but please remember that only n7k platform support EEM at the moment.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...