Ixia EE11ABG ユーザーズマニュアル
EmulationEngine 11a/b/g User's Guide
Rev #/Date: 2.0.0 Beta/07.17.03
7-1
CHAPTER 7: Event Logging
Overview
Overview
During normal operation, the EmulationEngine processes and can
log various types of events. When an event is logged, a record of
the event is stored for future analysis. The event record includes a
timestamp, an indicator of the type of event that occurred, and a
limited amount of data to describe the event.
Event logging is controlled on three levels:
1) master enable (controlled by set evlog enable/disable)
2) verbosity level (controlled by set evlog level <level>)
3) module enable (controlled by set evlog module <module name>
enable/disable)
1) The master enable controls whether event logging occurs at all.
The master control is independent of other filters. If "set evlog
disable" is used, enabling event logging for a particular module
has no effect.
2) The verbosity level sets an “importance” threshold for events: at
lower verbosity, only more “important” events are logged; at higher
verbosity, less important events may also be logged.
3) Each event is processed by a given module or process within
the EmulationEngine. The various processes of the system can be
individually enabled for event logging.
The event logging function stores event records into a buffer area
in memory. The log buffer is a circular buffer that can hold 512
event records. The "get evlog buffer" command can be used to
display the contents of the buffer at any time.
Event data can also be written to a log file in Flash. When writing
to a file is enabled by the "set evlog file enable" command, the log
buffer is flushed to a file every 30 seconds or every time it wraps
at the 512-record limit (which ever comes first). There are two log
files, A and B. The EmulationEngine will alternate between the two
files so that at least one full file is available at any given time.
Each log file can store up to 4,000 event records. You can display
the records stored in either file using the "get evlog file A" and "get
evlog file B" CLI commands.
log various types of events. When an event is logged, a record of
the event is stored for future analysis. The event record includes a
timestamp, an indicator of the type of event that occurred, and a
limited amount of data to describe the event.
Event logging is controlled on three levels:
1) master enable (controlled by set evlog enable/disable)
2) verbosity level (controlled by set evlog level <level>)
3) module enable (controlled by set evlog module <module name>
enable/disable)
1) The master enable controls whether event logging occurs at all.
The master control is independent of other filters. If "set evlog
disable" is used, enabling event logging for a particular module
has no effect.
2) The verbosity level sets an “importance” threshold for events: at
lower verbosity, only more “important” events are logged; at higher
verbosity, less important events may also be logged.
3) Each event is processed by a given module or process within
the EmulationEngine. The various processes of the system can be
individually enabled for event logging.
The event logging function stores event records into a buffer area
in memory. The log buffer is a circular buffer that can hold 512
event records. The "get evlog buffer" command can be used to
display the contents of the buffer at any time.
Event data can also be written to a log file in Flash. When writing
to a file is enabled by the "set evlog file enable" command, the log
buffer is flushed to a file every 30 seconds or every time it wraps
at the 512-record limit (which ever comes first). There are two log
files, A and B. The EmulationEngine will alternate between the two
files so that at least one full file is available at any given time.
Each log file can store up to 4,000 event records. You can display
the records stored in either file using the "get evlog file A" and "get
evlog file B" CLI commands.
Event Record Format
Event records are printed in the following format:
[header]: [message] [optional parameters]
Example:
12/27/2002,9:59:57,2296.320226,11396: RX: ok pDesc 0x9326c0
hwStatus 01cd803c:0be20203 numRxDesc 9643712