First of all, let me introduce myself since I'm new with cisco community. I'm syafiq currently working as an network administrator in Malaysia.
I need guidance on cisco LMS as I'm really new with the LMS systems. Currently I'm having issue with LMS where the log files are exceeding the size limit set by pervious administrator. Can anyone help me on how to backup/ remove the logs file and set it to a new locations i.e. new drive ?
Ciscoworks has many features and all of those features has dedicated processes. All those processes and many ciscoworks agnets write their output (logggin) to the *.log files. Most of them are under NMSROOT/logs.
These files are usually not important enough (except syslog.log mostly) unless there is any issue with any of the LMS function and it needs to be t/shooted.
But these logs files should not be deleted, nor there data needs to be preserved for long, unless your organisation policy says so.
Because processes keeps on writing constantly to these log files, these log files can grow and can continue to grow to become extravagantly huge sometimes, hence need to be controlled, which is why the 'Logrot' feature was inlcuded.
Logrot is a log rotation program that enables you to control the log files size growth. It helps you to:
•Rotate log files while CiscoWorks is running.
•Optionally archive and compress rotated logs.
•Rotate log files only when they have reached a particular size.
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 ...