Display Rmon History - H3C SR6600 Command Reference Manual

Table 31 Command output
Field
LogEntry
owned by
VALID
Generates eventLog at
Description
This example shows that event 1 generated two logs.

display rmon history

Use display rmon history to display RMON history control entry and history sampling information.
Syntax
display rmon history [ interface-type interface-number ] [ | { begin | exclude | include }
regular-expression ]
Views
Any view
Default command level
1: Monitor level
Parameters
interface-type interface-number: Specifies an interface by its type and number.
|: Filters command output by specifying a regular expression. For more information about regular
expressions, see Fundamentals Configuration Guide.
begin: Displays the first line that matches the specified regular expression and all lines that follow.
exclude: Displays all lines that do not match the specified regular expression.
include: Displays all lines that match the specified regular expression.
regular-expression: Specifies a regular expression, a case-sensitive string of 1 to 256 characters.
Usage guidelines
After you have created history control entry on an interface, the system calculates the information for the
interface periodically and saves the information to the etherHistoryEntry table. You can use this
command to display the entries in this table.
To configure the number of history sampling records that can be displayed and the history sampling
interval, use the rmon history command.
Description
Event entry, corresponding to the MIB node logIndex.
Event entry owner, corresponding to the MIB node eventOwner.
Entry status:
•
VALID—The entry is valid.
•
UNDERCREATION—The entry is invalid.
The display rmon command can display invalid entries, but the display
current-configuration and display this commands do not display their
settings.
Status value is stored in the MIB node eventStatus.
Time when the log was created (time passed since the device was
booted), corresponding to the MIB node logTime.
Log description, corresponding to the MIB node logDescription.
136