User Manual

Chapter 4 - Operation and Administration Using the CLI Troubleshooting
4Motion 821 System Manual
4.11 Troubleshooting
4.11.1 Configuring Tracing
The system can generate traces to be used for tracing the execution sequence of a
module and determining the actual cause of an erroneous condition. Traces are
recorded for events that occur with respect to the following system modules:
 System startup procedures: Refers to all procedures/events that occur during
system startup.
 NPU/AU upgrade procedures: Refers to all the procedures executed while
upgrading the NPU/AU.
 Fault management procedures: Refers to internal processes that are executed
for monitoring erroneous conditions or fault conditions.
 System performance procedures: Refers to internal processes that are
executed for monitoring system performance.
 Shelf management procedures: Refers to internal processes that are executed
for monitoring the health and temperature of all hardware components (other
than the NPU) such as the AU, PIU and PSU.
 WiMAX signaling protocols: Refers to all the protocols that implement the
ASN-GW functionality.
 User interface: Refers to the command line or remote management interface
used for executing all user-initiated events such as system shut down or reset.
 AU Manager: Refers to all internal processes used for fault, configuration, and
performance management for AU.
The system stores a maximum of 1000 trace and log messages, after which the
oldest messages are overwritten. First configure system-level tracing, and then
configure tracing separately for each module. This section describes the
commands to be used for:
 “Managing System-level Tracing” on page 822
 “Configuring Module-level Tracing” on page 825