3Com 4007, Implementation Manual, Page: 100 / 684

100 C
HAPTER
4: C
ONFIGURING AND
U
SING
EME O
PTIONS
Configuring the
Event Log
The EME maintains a log of informational events, nonfatal errors, and
fatal errors that occur on all modules in the chassis. Event log entries are
stored in the chronological order in which they are received.
When two EMEs are installed in the chassis, only the Primary EME collects
information. Each EME only stores events that occur while that EME is the
Primary.
You can configure the following event log characteristics:
■
Amount of memory allocated to storing events
Event log memory is allocated in 64k blocks. The default allocation
(also the minimum setting) is eight 64k blocks (0.5 MB). The maximum
setting depends upon available memory.
■
Action for the EME to take when the event log buffer is full
You can set the system to stop logging events, or to begin overwriting
old events.
■
Mechanism that triggers the EME to copy the event log to a file server
The EME can upload the event log when the event log reaches a
certain percent usage (default is 80 percent), when a user-defined
time interval has passed, or when you initiate the event log upload.
Before the event log can be copied to a file server, you must create a
public-access file on the file server to which the event log is written.
Uploaded event logs are larger than the size that appears on the EME
because they are stored in a compressed format.
To display the status of the event log’s characteristics, use the
show
event_log status
command.
To display the contents of the Event Log, use the
show event_log unfiltered
command with the
nonverbose
,
verbose
,
or
<number>
options.
The event log full default is
WRAP
.