I assume this is not an easy at least if you are not a real expert.
Background information: We have real high cpu now for about 3 weeks on our 3750X-Stack with 6 switches. The high CPU came from out of nowhere. It is about 70% most of the time and 25-30% are from the Hulc DAI process. However we do not have DAI activated. After a little deep diving I found a way to find the cause of it.
"show controllers cpu-interface" shows a strong growing routing-protocol Queue. That is strange as the stack isn't a router anymore for about one year now. Before it was routing between different VLANs but that role was migrated to a 4500X VSS.
"debug platform cpu-queues routing-protocol-q"brings really a lot of - if not a flood - of messages like these:
Now we see here the "RT-Q:DAI" which I assume is the root cause of the problem. The messages mention different VLANs and different uplinks while most of them show "Local Port Fwding", some of the "Remote Port Blocked".
I have no idea where the packets come from. I mean I followed one up to it's source port (according to the MAC address in the log message) but could not see why such a packet should be generated there.
I just came across with the same logs when I was trying to do the lab repro for one of my customer. These logs are seen for the DAI process (DAI would enable automatically in case you have 802.1x configured or you have IPDT enabled) which is receiving the ARP broadcast packets from Gig 2/0/37 and Ten 5/1/2. These packets would have been seen in the stack while the stack master would have been the switches other than switch 2 and switch 5. Packets received from the other stack member to the master would be using the routing protocol queue.
Game on! As a part of Cisco Live US auxiliary programs, we invite you to learn new technologies and obtain hands-on experience in a fun way by playing Capture the Flag (CTF).
Your mission: solve interesting challenges based on use-cases, technologies and ...
Hi,I'm trying to setup a cellular connection on my Cisco 1111 router.The interface is UP and it gets a private IPv4 and a public IPv6 address.If I try to send something on IPv4 through the cellular interface it works fine.But there seems to be an issue wi...
For an offline or printed copy of this document, simply choose ⋮ Options > Printer Friendly Page. You may then Print, Print to PDF or copy and paste to any other document format you like.
Is your WAN ready for a multicloud transformation?
Network Insider Live Webinar
Tuesday, July 21, 2020 10:00 am Pacific Time (San Francisco, GMT-08:00)
This webinar will show how convergence between SD-WAN and Security is emerging as important new SASE a...