User Manual

Chapter 3 - Operation and Administration of the Macro BTS NPU Configuration
4Motion 387 System Manual
You can, at any time, view the current log destination or delete log files from the
NPU flash. After you have enabled/disabled system-level logging and specified the
destination for storing log messages, you can configure logging separately for each
module. You can also transfer log files from the NPU file system to an external
TFTP server. To support debugging, you can create a “collect logs” file that
contains the also all status and configuration files. This section describes the
commands to be used for:
 “Enabling System-level Logging” on page 387
 “Disabling Logging to File or Server” on page 389
 “Displaying System-level Logs” on page 391
 “Displaying the Current Log Destination” on page 392
 “Making a Backup of Log Files on the NPU Flash” on page 393
 “Deleting Backup Log Files from the NPU Flash” on page 395
 “Creating a Collected System Logs File” on page 396
 “Transferring Files from the NPU Flash to a TFTP Server” on page 396
 “Displaying Log Files Residing on the NPU Flash” on page 397
3.4.13.1.1 Enabling System-level Logging
You can enable logging for the entire system and specify the destination where
logs should be written. The destination can be either written to:
 File
 External server (Log files are sent to the external server in the Syslog log
format. The Syslog daemon on the external server can save these log messages
in the appropriate format depending upon the server configuration.)
By default, system-level logging is enabled. To view whether the system-level
logging is enabled/disabled for logging to file or server. For details, refer
Section 3.4.13.1.4.
The system maintains a maximum of 1000 log and trace messages. The system
stores log and trace messages using the cyclic buffer method. That is, when there