The number of trace messages stored in memory for each instance of a trace is configurable up to 65536 entries. Event tracing also applies a timestamp to each trace message, which aids in identifying the message sequence. This way, all messages associated with a single instance of a trace get the same ID number.

To do this, the feature assigns a unique ID number to each instance of a trace. The Event Tracer feature can support multiple traces simultaneously. Optionally, event trace messages can be saved in ASCII format for additional file processing. Saving messages in binary format allows event tracing to collect informational messages faster and for a longer time prior to a system malfunction or processor switchover. Trace messages stored in memory can be displayed on the screen or saved to a file for later analysis.īy default, trace messages saved to a file are saved in binary format without applying additional processing or formatting. This feature is intended for use as a software diagnostic tool and should be configured only under the direction of a Cisco Technical Assistance Center (TAC) representative.Įvent tracing works by reading informational messages from specific Cisco IOS software subsystem components that have been preprogrammed to work with event tracing, and by logging messages from those components into system memory.

This feature gives Cisco service representatives additional insight into the operation of the Cisco IOS software and can be useful in helping to diagnose problems in the unlikely event of an operating system malfunction or, in the case of redundant systems, route processor switchover. The Event Tracer feature provides a binary trace facility for troubleshooting Cisco IOS software.

Cm list packet tracer