logging level critical to avoid ISDN calls being logged
We have IOS routers (12.1(16) that make and receive hundreds of ISDN calls per day. The routers also have a number of serial interfaces. These routers are logging events to a syslog server.
We do not want to fill our syslog server with logs associated with ISDN calls (Dialer interface changed to up, etc.).
However, to stop Dialer interface state changes from being logged, we need to set the logging trap level to critical. By doing this, we miss being notified of significant events such as config changes or other interface state changes.
Is there a way we can configure the router to demote the severity level of Dialer interface state changes so we can set the logging trap level to warnings or notifications and not be bombarded with Dialer interface state changes?
Re: logging level critical to avoid ISDN calls being logged
I don't know of a way to reset the severity, but if you consider Dialer interface state changes to be totally uninteresting, you may set "no logging event link-status" on the Dialer interface to prevent it from being logged at all. You continue to get any AAA accounting data you may be recording, and debugs still work.
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 ...