3com S7906E Verweisanleitung
1-4
Description
Use the display rmon eventlog command to display log information for the specified or all event
entries.
If entry-number is not specified, the log information for all event entries is displayed.
If you use the rmon event command to configure the system to log an event when the event is triggered,
the event is recorded into the RMON log. You can use this command to display the details of the log
table: event index, current event state, time the event was logged (the elapsed time in seconds since
system initialization/startup), and event description.
Examples
# Display the RMON log information for event entry 1.
<Sysname> display rmon eventlog 1
LogEntry 1 owned by null is VALID.
Generates eventLog 1.1 at 0day(s) 00h:00m:33s.
Description: The alarm formula defined in prialarmEntry 1,
uprise 80 with alarm value 85. Alarm sample type is absolute.
Generates eventLog 1.2 at 0day(s) 00h:42m:03s.
Description: The alarm formula defined in prialarmEntry 2,
less than(or =) 5 with alarm value 0. Alarm sample type is delta.
Table 1-3 display rmon eventlog command output description
Field
Description
LogEntry
Event log entry, corresponding to the MIB node logIndex.
owned by
Owner of the entry, corresponding to the MIB node
eventOwner.
eventOwner.
VALID
Status of the entry identified by the index (VALID means the
entry is valid, and UNDERCREATION means invalid. You
can use the display rmon command to view the invalid
entry; while with the display current-configuration and
display this commands you cannot view the corresponding
rmon commands.), corresponding to the MIB node
eventStatus.
entry is valid, and UNDERCREATION means invalid. You
can use the display rmon command to view the invalid
entry; while with the display current-configuration and
display this commands you cannot view the corresponding
rmon commands.), corresponding to the MIB node
eventStatus.
Generates eventLog at
Time when the log was created (Time passed since the
device was booted), corresponding to the MIB node logTime.
device was booted), corresponding to the MIB node logTime.
Description
Log description, corresponding to the MIB node
logDescription.
logDescription.
The above example shows that event 1 has generated two logs:
z
eventLog 1.1, generated by private alarm entry 1, which is triggered because the alarm value (85)
exceeds the rising threshold (80). The sampling type is absolute.
z
eventLog 1.2, generated by private alarm entry 2, which is triggered because the alarm value (0) is
lower than the falling threshold (5). The sampling type is delta.
display rmon history
Syntax
display rmon history [ interface-type interface-number ]