User Manual

Chapter 4 - Operation and Administration Using the CLI Troubleshooting
4Motion 822 System Manual
4.11.1.1 Managing System-level Tracing
System-level tracing refers all the procedures to be executed for managing tracing
for the entire system. To manage system-level tracing:
 Enable/disable logging for the entire system and specify the destination (file or
console) where traces are to be maintained.
 Make periodic backups of trace files
You can, at any time, view the current destination to where traces are maintained.
After you have enabled/disabled system-level logging and specified the
destination for storing log messages, you can configure logging separately for each
module.
This section describes the commands to be used for:
 “Enabling System-level Tracing” on page 822
 “Disabling System-level Tracing” on page 823
 “Displaying the Current Status of Trace Destinations” on page 824
4.11.1.1.1 Enabling System-level Tracing
You can enable traces for all modules across the system and specify the
destination where traces should be written. The destination can be either a file
stored on the local system or console. To view whether tracing to file or console is
enabled or disabled, refer Section 4.11.1.1.3.
To enable system-level tracing, run the following command:
npu(config)# trace destination {file|console}
The system maintains a maximum of 1000 trace and log messages, after which
the oldest messages are overwritten.
NOTE
By default, system-level tracing to file is disabled. If you enable tracing to file, traces are written to
the same file that contains log messages. This file is not maintained after system reset. It is
recommended that you periodically make a backup of this file on the NPU flash. For details, refer to
Section 4.3.11.1.5.