The message "Dup Packet Fail for Sw Port" is seen when certain multicast
packets are software bridged and software has run out of buffers while
replicating the packets in software.
In typical deployments, one should NOT have a lot of multicast packets to CPU. Could you check what is
causing multicast packets to CPU periodically? Can you get the output of
"show platform cpu packet driver" ? This could provide a hint as to packets drops due to high incoming rate to CPU.
It can be normal situation as some multicast should come to CPU to build all records, so depending on the mcast groups number sometimes buffers can be filled. So you can Change the logging level to '5' not to see that message.
Other possibility is that you get Multicast packets with TTL expired (TTL=1) thus those punted to CPU and dropped there. For this sniffer should be done on mcast ports to check mcast packets.
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 ...