In the absence of any other errors output discards are indicative of transient oversubscription. Whether it's an actual problem or not depends on how sensitive the applications on the port are to packet loss.
The number by itself is meaningless - you need to divide it by the total packets output to get a percentage packet loss. If it's a very small number (e.g. <0.001%) then it's unlikely to be an issue, but as the % increases so does the risk that it might be service affecting.
There's no absolute answer to how much packet loss is acceptable - a callmanager server will be critically affected by a very small amount of packet loss but an ftp server can handle a much larger amount.
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 ...