As I can see, the process is the loPri this process as well as the hiPri are normally related to traffic, if you do a "show platform health" you will see the specific proceds that is going over que target.
You can also do a debug to see the interface(s) that are flooding que CPU:
"debug platform cpu packet all count"
Wait over 10 seconds and do a:
"show platform cpu packet statistics"
And you will see the interfaces that are sending traffic to the CPU and if you shut the specific port, the Cpu will go down and you know what is causing the issue.
You can also enable:
"mac address-table notification mac-move"
It will reveal with a show log if there is MAC flapping which also causes high CPU on this platform.
You can also take an sniffer directly to the switch's CPU by connecting a laptop running wireshark and configuring the following at the switch:
"monitor session 1 source cpu"
"monitor session 1 destination interface g#/#"
This interface is where the PC will be connected. With this you will see the exact ip address that is hammering the CPU.
Note, some commands might not work depending on the IOS.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...