There is something you could try. If the syslog dataspace has become overly fragmented, this could lead to a performance problem. TAC Can provide you with a DBSpaceReclaimer.class tool which will drop and recreate these dataspaces. All current syslogs will be lost (but you could save them out to a flat file first), but you'll have a clean slate for running reports moving forward.
Of course, if, during the following week, performance gradually gets worse, then the amount of syslogs is certainly causing the problem. In that case, your workarounds are:
* Get more CPU power (i.e. more CPUs, cores, etc.)
* Configure a shorter purge cycle
* Schedule the reports so you're not sitting on the computer waiting for them to complete.
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 ...