This will occur when Config Archive runs if your selected protocol order under RME > Admin > Config Mgmt > Transport Settings is not as correct as it can be. In any event, you can manage the size of daemons.log using the NMSROOT/bin/logrot.pl tool. First, run NMSROOT/bin/logrot.pl -c to configure log rotation. Specify the path to daemons.log, how large you want the file to be able to grow, and how many archives to keep (if any). then add a cron entry to run logrot.pl as often as you need (e.g. once per day).
More on logrot can be found in the Common Services online help.
thanks, I've indeed changed the order of the transport protocol i.e. removed telnet from the list because the customer's network does use SSH. So It shouldn't report a connection refused. Is there a way to find out what devices in the DCR are causing this?
In the mean time I will setup a cronjob with logrot.
There is no way to disable this logging. However, I have developed a patch for bug CSCso57052 which will help reduce the amount of these connection refused exceptions. The patch doesn't actually address the logging issue, but it greatly cuts down on the number of connections attempted, and thus will reduce the logging.
For example, before the patch, you could get, say, 100 connections per device. After the patch there will never be more than three.
You can contact the TAC, and reference the above bug to get the patch.
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 ...