As Amit stated interface reset can be caused by link going up and down , that could be one possible reason for interface reset.
It can also happen if packets queued for transmission were not sent within several seconds' time.
On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it.
Interface resets can also occur when an interface is looped back or shut down.
So it is not necessary that you get it in logs cause not necessarily the physical interface might have flapped.
So you can check if there any output drops or you can als check the cabling or your modem also.
As seen there are many other errors on DS3 interface which can be sue to physical cabling issue so please check your cabling.
On E3 card there are no such errors other than many output drops which can be due to your QOS configuration and interface reset can occur if packets queued for transmission were not sent within several seconds' time. So check you QOS configuration also if you have any.
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 ...