Syntax
display rmon alarm [ entry-number ]
View
Any view
Parameter
entry-number:
Alarm entry index, in the range of 1 to 65535. If you do not specify this
argument, the configuration of all alarm entries is displayed.
Description
Use the display rmon alarm
command to display the configuration of a specified alarm entry or all the
alarm entries.
Related command: rmon alarm.
Example
# Display the configuration of all the
alarm entries.
<H3C> display rmon alarm
Alarm table 1 owned by user1 is Valid.
Samples type : absolute
Variable formula :
1.3.6.1.2.1.2.2.1.10.4227626<ifInOctets.4227626>
Sampling interval : 6(sec)
Rising threshold :
10000(linked with event 1)
Falling threshold : 2000(linked
with event 1)
When startup enables :
risingOrFallingAlarm
Latest value : 0
Table 1-1 Description on the fields of the display rmon alarm command
|
Field
|
Description
|
|
Alarm table
|
Alarm
entry
|
|
user1
|
Creator
|
|
Valid
|
Valid for alarm entries corresponding to
the index
|
|
Samples type
|
Sample type:
delta (indicates the sample is an increment)
absolute (indicates the sample is an
absolute value)
|
|
Variable formula
|
Variable formula of the sampled node
|
|
Sampling interval
|
Sampling interval
|
|
Rising threshold
|
Rising threshold
|
|
Falling threshold
|
Falling threshold
|
|
When startup enables
|
Alarm startup type:
risingOrFallingAlarm (an alarm is
triggered when the rising or falling threshold is reached)
risingAlarm (an alarm is triggered when
the rising threshold is reached)
FallingAlarm (an alarm is triggered when
the falling threshold is reached)
|
|
Latest value
|
Latest sampled value
|
Syntax
display rmon event [ event-entry ]
View
Any view
Parameter
event-entry:
Event entry index, in the range of 1 to 65535. If you do not specify this
argument, the configuration of all the event entries is displayed.
Description
Use the display rmon event command
to display the configuration of a specified event entry or all the event
entries.
The displayed information includes: event
entry index, event entry owner, event description, the action triggered by the
event (log or alarm messages), and the time (in seconds) when the latest event
is triggered (in terms of the time elapsed since the system is started/initialized).
Related command: rmon event.
Example
# Display the configuration of all the
event entries.
<H3C> display rmon event
Event table 1 owned by user1 is
VALID.
Description: null.
Will cause log-trap when triggered,
last triggered at 0days 00h:02m:27s.
Table 1-2 Description on the fields of
the display rmon event command
|
Field
|
Description
|
|
Event table
|
Event entries
|
|
VALID
|
The status of the line corresponding to
the index is valid
|
|
Description
|
Event description
|
|
Will cause log-trap when triggered
|
The event triggers logs and an trap alarm
|
|
last triggered at
|
Time the latest event is triggered
|
Syntax
display rmon eventlog [ event-entry ]
View
Any view
Parameter
event-entry:
Event entry index, in the range of 1 to 65535. If you do not specify this
argument, the log of all the event entries is displayed.
Description
Use the display rmon eventlog
command to display the log of a specified event entry or all the event entries.
The displayed information includes: the
indexes and status of the event entries in the event table, the time (in
seconds) when an event log is generated (in terms of the time elapsed since the
system is started or initialized), and the event description.
Example
# Display the log generated by the event
entry numbered 1.
<H3C> display rmon eventlog 1
Event table 1 owned by user1 is
VALID.
Generates eventLog 1.1 at 0days
00h:01m:39s.
Description: The
1.3.6.1.2.1.16.1.1.1.4.1 defined in alarm table 1,
less than(or =) 100 with alarm value
0. Alarm sample type is absolute.
Generates eventLog 1.2 at 0days
00h:02m:27s.
Description: The alarm formula
defined in private alarm table 1,
less than(or =) 100 with alarm value
0. Alarm sample type is absolute.
Table 1-3 Description on the fields of
the display rmon eventlog command
|
Field
|
Description
|
|
Event table
|
Event entries
|
|
VALID
|
The status of the line corresponding to
the line is valid
|
|
Generates eventLog 1.1 at 0days
00h:02m:27s
|
Time when the event is triggered. The
event may be triggered several times. 1.1 indicates the time event 1 is first
triggered
|
|
Description
|
Description of an event log
|
Syntax
display rmon history [ interface-type interface-number | unit unit-number
]
View
Any view
Parameter
interface-type: Interface type.
interface-number: Interface number.
unit unit-number: Specifies a unit number.
Description
Use the display rmon history command
to display the RMON history information about a specified port. The information
about the latest sample, including utilization, the number of errors, the total
number of packets and so on, is also displayed.
Related command: rmon history.
Example
# Display the RMON history information
about Ethernet1/0/1.
<H3C> display rmon history Ethernet
1/0/1
History control entry 1 owned by
user1 is VALID
Samples interface : Ethernet1/0/1<ifIndex.4227626>
Sampling interval : 5(sec) with
10 buckets max
Latest sampled values :
dropevents : 0 ,
octets : 0
packets : 0 ,
broadcast packets : 0
multicast packets : 0 , CRC
alignment errors : 0
undersize packets : 0 ,
oversize packets : 0
fragments : 0 ,
jabbers : 0
collisions : 0 ,
utilization : 0
Table 1-4 Description on the fields of the display rmon eventlog command
|
Field
|
Description
|
|
History control entry
|
Index number in the history control table
|
|
VALID
|
The status of the line corresponding to
the index is valid
|
|
Samples interface
|
Sampled interface
|
|
Sampling interval
|
Sampling interval
|
|
buckets
|
Number of records in the history control
table
|
|
Latest sampled values
|
Latest sampled information
|
|
dropevents
|
Event about dropping packets
|
|
octets
|
Number of received or transmitted bytes
during sampling duration
|
|
packets
|
Number of received or transmitted packets
during sampling duration
|
|
broadcastpackets
|
Number of broadcast packets
|
|
multicastpackets
|
Number of multicast packets
|
|
CRC alignment errors
|
Number of checkerror packets
|
|
undersize packets
|
Number of undersize packets
|
|
oversize packets
|
Number of oversize packets
|
|
fragments
|
Number of undersize and checkerror
packets
|
|
jabbers
|
Number of oversize and checkerror packets
|
|
collisions
|
Number of collision packets
|
|
utilization
|
Bandwidth utilization
|
Syntax
display rmon prialarm [ prialarm-entry-number ]
View
Any view
Parameter
prialarm-entry-number:
Extended alarm entry Index, in the range of 1 to 65535. If you do not specify
this argument, the configuration of all the extended alarm entries is
displayed.
Description
Use the display rmon prialarm command
to display the configuration of a specified RMON extended alarm entry or all
the RMON extended alarm entries.
Related command: rmon prialarm.
Example
# Display the configuration of all the
extended RMON alarm entries.
<H3C>
display rmon prialarm
Prialarm table 1 owned by user1 is
VALID.
Samples type : absolute
Variable formula :
.1.3.6.1.2.1.16.1.1.1.4.1
Description :
Sampling interval : 10(sec)
Rising threshold :
10000(linked with event 1)
Falling threshold : 2000(linked
with event 1)
When startup enables : risingOrFallingAlarm
This entry will exist : forever.
Latest value : 0
Table 1-5 Description on the fields of the display rmon prialarm
command
|
Field
|
Description
|
|
Prialarm table
|
Index number of a line of the extended
alarm table
|
|
owned by user1
|
Creator user 1
|
|
VALID
|
Valid
|
|
Samples type
|
Sample type: change value or absolute
value
|
|
Variable formula
|
Variable formula of the sampled node
|
|
Description
|
Description
|
|
Sampling interval
|
Sampling interval
|
|
Rising threshold
|
Rising threshold. An alarm is triggered
when the rising threshold is reached
|
|
Falling threshold
|
Falling threshold. An alarm is triggered
when the falling threshold is reached
|
|
linked with event
|
Event index corresponding to an alarm
|
|
When startup enables: risingOrFallingAlarm
|
Alarm startup type:
risingOrFallingAlarm (an alarm is
triggered when the rising or falling threshold is reached)
risingAlarm (an alarm is triggered when
the rising threshold is reached)
FallingAlarm (an alarm is triggered when
the falling threshold is reached)
|
|
This entry will exist: forever
|
Existing period. This entry can exist
forever or exist in the specified cycle
|
|
Latest value
|
Latest sampled value
|
Syntax
display rmon statistics [ interface-type interface-number | unit unit-number
]
View
Any view
Parameter
interface-type: Interface type.
interface-number: Interface number.
unit unit-number: Specifies a unit number.
Description
Use the display rmon statistics
command to display the RMON statistics of a specified port.
The displayed information include the
number of the following items: collisions, packets with CRC errors, undersize
or oversize packets, broadcast packets, multicast packets, received bytes, and
received packets.
Related command: rmon statistics.
Example
# Display the RMON statistics information
about Ethernet1/0/1 port.
<H3C> display rmon statistics
Ethernet 1/0/1
Statistics entry 1 owned by
user1-rmon is VALID.
Interface : Ethernet1/0/1<ifIndex.4227626>
etherStatsOctets :
0 , etherStatsPkts : 0
etherStatsBroadcastPkts :
0 , etherStatsMulticastPkts : 0
etherStatsUndersizePkts :
0 , etherStatsOversizePkts : 0
etherStatsFragments :
0 , etherStatsJabbers : 0
etherStatsCRCAlignErrors :
0 , etherStatsCollisions : 0
etherStatsDropEvents (insufficient
resources): 0
Packets received according to
length:
64 : 0 , 65-127 :
0 , 128-255 : 0
256-511: 0 , 512-1023:
0 , 1024-1518: 0
Table 1-6 Description
on the fields of the display rmon statistics command
|
Field
|
Description
|
|
Statistics entry
|
Index number of the statistics
information table
|
|
VALID
|
Valid
|
|
Interface
|
Interface for which information
statistics is to be made
|
|
etherStatsOctets
|
Number of bytes
|
|
etherStatsPkts
|
Number of packets
|
|
etherStatsBroadcastPkts
|
Number of broadcast packets
|
|
etherStatsMulticastPkts
|
Number of multicast packets
|
|
etherStatsUndersizePkts
|
Number of undersize packets
|
|
etherStatsOversizePkts
|
Number of oversize packets
|
|
etherStatsFragments
|
Number of undersize and checkerror
packets
|
|
etherStatsJabbers
|
Number of oversize and checkerror packets
|
|
etherStatsCRCAlignErrors
|
Number of checkerror packets
|
|
etherStatsCollisions
|
Number of collision packets
|
|
etherStatsDropEvents
|
Event about dropping packets
|
|
Packets received according to length
|
Number of received packets of different
lengths
|
Syntax
rmon alarm entry-number
alarm-variable sampling-time { delta | absolute }
rising-threshold threshold-value1 event-entry1
falling-threshold threshold-value2 event-entry2
[ owner text ]
undo rmon alarm entry-number
View
System view
Parameter
entry-number:
Alarm entry index, in the range of 1 to 65535.
alarm-variable:
Alarm variable, a string comprising 1 to 256 characters in dotted node OID
format (such as 1.3.6.1.2.1.2.1.10.1). Only the variables that can be resolved
to ASN.1 INTEGER data type (that is, INTEGER, Counter, Gauge, or TimeTicks) can
be used as alarm variables.
sampling-time:
Sampling interval (in seconds), in the range of 5 to 65,535.
delta:
Specifies to sample increments (that is, the current increment with regard to
the latest sample)
absolute:
Specifies to sample absolute values.
rising-threshold
threshold-value1: Specifies the upper threshold. The threshold-value1
argument ranges from 0 to 2,147,483,647.
event-entry1:
Index of the event entry corresponding to the upper threshold, in the range of
0 to 65535.
falling-threshold
threshold-value2: Specifies the lower threshold. The threshold-value2
argument ranges from 0 to 2,147,483,647.
event-entry2:
Index of the event entry corresponding to the lower threshold, in the range of
0 to 65535.
owner
text: Specifies the owner of the entry. The text
argument is a string comprising 1 to 127 characters.
Description
Use the rmon alarm command to add an
alarm entry to the alarm table.
Use the undo rmon alarm command to
remove an alarm entry from the alarm table.
You can use the rmon alarm command
to define an alarm entry so that a specific alarm event can be triggered under
specific circumstances. The act (such as logging and sending trap messages to
NMS) taken after an alarm event occurs is determined by the corresponding alarm
entry.
With an alarm entry defined in an alarm
group, a network device performs the following operations accordingly:
l
Sample the defined alarm variables
(alarm-variable) once in each specified period, which is specified by the sampling-time
argument.
l
Comparing the sampled value with the set
threshold and performing the corresponding operations, as described in Table 1-7.
Table 1-7 Sample value and the
corresponding operation
|
Comparison
|
Operation
|
|
The sample value is larger than or equal
to the set upper threshold (threshold-value1)
|
Triggering the event identified by the event-entry1
argument
|
|
The sample value is smaller than the set
lower threshold (threshold-value2)
|
Triggering the event identified by the event-entry2
argument
|
l
Before adding an alarm entry, you need to use
the rmon event command to define the events to be referenced by the
alarm entry.
l
Make sure the node to be monitored exists before
executing the rmon alarm command.
Example
# Add the alarm entry numbered 1 as
follows:
l
The node to be monitored: 1.3.6.1.2.1.16.1.1.1.4.1
l
Sampling interval: 10 seconds
l
Upper threshold: 50
l
The event-entry1 argument identifies
event 1.
l
Lower threshold: 5
l
The event-entry2 argument identifies
event 2
l
Owner: user1.
<H3C> system-view
System View: return to User View with
Ctrl+Z.
[H3C] rmon event 1 log
[H3C] rmon event 2 none
[H3C]rmon alarm 1
1.3.6.1.2.1.16.1.1.1.4.1 10 absolute rising_threshold 50 1 falling_threshold 5 2
owner user1
# Delete the alarm entry numbered 15 from
the alarm table.
[H3C] undo rmon alarm 15
Syntax
rmon event
event-entry [ description string ] { log | trap
trap-community | log-trap log-trapcommunity
| none } [ owner text ]
undo rmon event event-entry
View
System view
Parameter
event-entry:
Event entry index, in the range of 1 to 65535.
description string:
Specifies the event description, a string comprising 1 to 127 characters.
log: Logs
events.
trap: Sends
trap message to the NMS.
trap-community:
Community name of the NMS that receives the trap messages, a string comprising
1 to 127 characters.
log-trap:
Logs the event and sends trap messages to NMS.
log-trapcommunity:
Community name of the NMS that receives the log messages, a character string of
1 to 127 characters.
none:
Specifies that the event triggers no action.
owner text: Specifies the owner of the event entry. The text argument
is a string comprising 1 to 127 characters.
Description
Use the rmon event command to add an
entry to the event table.
Use the undo rmon event command to
delete an entry from the event table.
When adding an event entry to an event
table, you need to specify the event index. You need also to specify the
corresponding actions, including logging the event, sending trap messages to
the NMS, and the both, for the network device to perform corresponding
operation when an alarm referencing the event is triggered.
Example
# Add the event entry numbered 10 to the
event table and configure it to be a log event.
<H3C> system-view
System View: return to User View with
Ctrl+Z.
[H3C] rmon event 10 log
Syntax
rmon history
entry-number buckets number interval sampling-interval
[ owner text ]
undo rmon history entry-number
View
Ethernet port view
Parameter
entry-number:
History entry index, in the range of 1 to 65535.
buckets number:
Specifies the size of the history table that corresponds to the entry, in the
range of 1 to 65535.
interval sampling-interval:
Specifies the sampling interval (in seconds). The sampling-interval
argument ranges from 5 to 3,600.
owner text:
Specifies the owner of the entry, a string comprising 1 to 127 characters.
Description
Use the rmon history command to add
an entry to a history control table.
Use the undo rmon history command to
delete an entry from a history control table.
You can use the rmon history command
to sample a specific port. You can also set the sampling interval and the
number of the samples that can be saved. After you execute this command, the
RMON system samples the port periodically and stores the samples for later
retrieval. The sampled information includes utilization, the number of errors,
and total number of packets.
You can use the display rmon history
command to display the statistics of the history control table.
Example
# Create the history entry numbered 1 for
Ethernet1/0/1 port, with the table size being 10, the sampling interval being 5
seconds, and the owner being user1.
<H3C> system-view
System View: return to User View with
Ctrl+Z.
[H3C]interface Ethernet 1/0/1
[H3C-Ethernet1/0/1]rmon history 1
buckets 10 interval 5 owner user1
# Remove the history entry numbered 15.
[H3C-Ethernet1/0/1] undo rmon history
15
Syntax
rmon prialarm entry-number prialarm-formula prialarm-des sampling-timer { delta | absolute | changeratio } rising-threshold
threshold-value1 event-entry1 falling-threshold threshold-value2
event-entry2 entrytype { forever | cycle
cycle-period } [ owner text ]
undo rmon prialarm entry-number
View
System view
Parameter
entry-number:
Extended alarm entry index, in the range of 1 to 65535.
prialarm-formula: Expression used to perform operations on the alarm variables, a
string comprising 1 to 256 characters. The alarm variables in the expression
must be represented by OIDs, for example, (.1.3.6.1.2.1.2.1.10.1)*8. The
operations available are addition, subtraction, multiplication and division
operations. The operation results are rounded to values that are of long
integer type. To prevent invalid operation results, make sure the operation
results of each step are valid long integers.
prialarm-des:
Alarm description, a string comprising 1 to 128 characters.
sampling-timer:
Sampling interval (in seconds), in the range of 10 to 65,535.
delta |
absolute | changeratio: Specifies sample type, which can be deltas,
absolute values or change ratios.
threshold-value1:
Upper threshold, in the range of 0 to 2,147,483,647.
event-entry1:
Index of the event entry that corresponds to the upper threshold, in the range
of 0 to 65535.
threshold-value2:
Lower threshold, in the range of 0 to 2,147,483,647.
event-entry2:
Index of the event entry that corresponds to the lower threshold, in the range
of 0 to 65535.
forever:
Specifies the alarm entry is valid indefinitely.
cycle:
Specifies the alarm entry is valid periodically.
cycle-period:
Cycle period, in seconds, ranging from 0 to 2,147,483,647.
owner
text: Specifies the owner of the alarm entry, a
string comprising 1 to 127 characters.
Description
Use the rmon prialarm command to
create an extended entry in an extended RMON alarm table.
Use the undo rmon prialarm command
to remove a specified extended alarm entry.
l
Before adding an extended alarm entry, you need
to use the rmon event command to define the events to be referenced by
the entry.
l
Make sure the node to be monitored exists before
executing the rmon event command.
l
You can define up to 50 extended alarm entries.
With an extended alarm entry defined in an
extended alarm group, the network devices perform the following operations
accordingly:
l
Sampling the alarm variables referenced in the
defined extended alarm expressions (prialarm-formula) once in each
period specified by the sampling-timer argument.
l
Performing operations on sampled values
according to the defined extended alarm expressions (prialarm-formula)
l
Comparing the operation result with the set
thresholds and perform corresponding operations, as described in Table 1-8.
Table 1-8 Operation result and corresponding
operation
|
Comparison
|
Operation
|
|
The operation result is larger than or
equal to the set upper threshold (threshold-value1)
|
Triggering the event identified by the event-entry1
argument
|
|
The operation result is smaller than or
equal to the set lower threshold (threshold-value2)
|
Triggering the event identified by the event-entry2
argument
|
Example
# Add the extended alarm entry numbered 2
as follows:
l
Perform operations on the corresponding alarm
variables using the expression ((1.3.6.1.2.1.16.1.1.1.4.1)*100).
l
Sampling interval: 10 seconds
l
Upper threshold: 50
l
Lower threshold: 5
l
Event 1 is triggered when the change ratio is
larger than the upper threshold.
l
Event 2 is triggered when the change ratio is
less than the lower threshold.
l
The alarm entry is valid forever.
l
Entry owner: user1
<H3C> system-view
System View: return to User View with
Ctrl+Z.
[H3C]interface Ethernet 1/0/1
[H3C-Ethernet1/0/1] rmon statistics 1
[H3C-Ethernet1/0/1] quit
[H3C] rmon prialarm 2
((.1.3.6.1.2.1.16.1.1.1.4.1)*100) test 10 changeratio rising-threshold 50 1
falling-threshold 5 2 entrytype forever owner user1
# Remove the extended alarm entry numbered
2 from the extended alarm table.
[H3C] undo rmon prialarm 2
Syntax
rmon statistics entry-number [ owner text ]
undo rmon statistics entry-number
View
Ethernet port view
Parameter
entry-number:
Statistics entry Index, in the range of 1 to 65535.
owner
text: Specifies the owner of the entry, a string comprising
1 to 127 characters.
Description
Use the rmon statistics command to
add an entry to the statistics table.
Use the undo rmon statistics command
to remove an entry from the statistics table.
The RMON statistics management function is
used to take statistics of the usage of the monitored ports and errors occurred
to them. The statistics includes the number of the following items: collisions,
packet with CRC errors, undersize (or oversize) packets, broadcast and
multicast packets, received packets and bytes and so on.
For each port, only
one RMON alarm table entry can be created, that is to say, if one RMON alarm
table entry was already created for a given port, creation of another entry
with a different index number for the same port will not succeed.
You can use the display rmon statistics
command to display the statistics entries.
Example
# Add the statistics entry numbered 20 to
take statistics of Ethernet1/0/1 port.
<H3C> system-view
System View: return to User View with
Ctrl+Z.
[H3C]interface Ethernet 1/0/1
[H3C-Ethernet1/0/1] rmon statistics
20
