07-RMON Commands
Chapters Download (93.79 KB)
Syntax
display rmon alarm [ entry-number ]
View
Any view
Default Level
1: Monitor level
Parameters
entry-number: Index of an RMON alarm entry, in the range 1 to 65535. If no entry is specified, the configuration of all alarm entries is displayed.
Description
Use the display rmon alarm command to display the configuration of the specified or all RMON alarm entries.
Related commands: rmon alarm.
Examples
# Display the configuration of all RMON alarm table entries.
AlarmEntry 1 owned by user1 is VALID.
Samples type : absolute
Variable formula : 1.3.6.1.2.1.16.1.1.1.4.1<etherStatsOctets.1>
Sampling interval : 10(sec)
Rising threshold : 50(linked with event 1)
Falling threshold : 5(linked with event 2)
When startup enables : risingOrFallingAlarm
Latest value : 0
Table 1-1 display rmon alarm command output description
|
Field |
Description |
|
AlarmEntry |
Alarm entry, corresponding to the management information base (MIB) node alarmIndex. |
|
owned by |
Owner of the entry, user1 in this example, corresponding to the MIB node alarmOwner. |
|
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 alarmStatus. |
|
Samples type |
The sampling type (the value can be absolute or delta), corresponding to the MIB node alarmSampleType. |
|
Variable formula |
Alarm variable, namely, the monitored MIB node, corresponding to the MIB node alarmVariable. |
|
Sampling interval |
Sampling interval, in seconds, corresponding to the MIB node alarmInterval. |
|
Rising threshold |
Alarm rising threshold (When the sampling value is bigger than or equal to this threshold, a rising alarm is triggered.), corresponding to the MIB node alarmRisingThreshold. |
|
Falling threshold |
Alarm falling threshold (When the sampling value is smaller than or equal to this threshold, a falling alarm is triggered.), corresponding to the MIB node alarmFallingThreshold. |
|
When startup enables |
How an alarm can be triggered, corresponding to the MIB node alarmStartupAlarm. |
|
Latest value |
The last sampled value, corresponding to the MIB node alarmValue. |
Syntax
display rmon event [ entry-number ]
View
Any view
Default Level
1: Monitor level
Parameters
entry-number: Index of an RMON event entry, in the range 1 to 65535. If no entry is specified, the configuration of all event entries is displayed.
Description
Use the display rmon event command to display the configuration of the specified or all RMON event entries.
Displayed information includes event index, event owner, event description, action triggered by the event (such as sending log or trap messages), and last time the event occurred (the elapsed time since system initialization/startup) in seconds.
Related commands: rmon event.
Examples
# Display the configuration of RMON event table.
<Sysname> display rmon event
EventEntry 1 owned by user1 is VALID.
Description: null.
Will cause log-trap when triggered, last triggered at 0days 00h:02m:27s.
Table 1-2 display rmon event command output description
|
Field |
Description |
|
EventEntry |
Event entry, corresponding to the MIB node eventIndex. |
|
owned by |
Owner of the entry, corresponding to the MIB node 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. |
|
Description |
Description for the event, corresponding to the MIB node eventDescription. |
|
cause log-trap when triggered |
The actions that the system will take when the event is triggered: l none: The system will take no action l log: The system will log the event l snmp-trap: The system will send a trap to the NMS l log-and-trap: The system will log the event and send a trap to the NMS This field corresponds to the MIB node eventType. |
|
last triggered at |
Time when the last event was triggered, corresponding to the MIB node eventLastTimeSent. |
Syntax
display rmon eventlog [ entry-number ]
View
Any view
Default Level
1: Monitor level
Parameters
entry-number: Index of an event entry, in the range 1 to 65535.
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. |
|
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. |
|
Generates eventLog at |
Time when the log was created (Time passed since the device was booted), corresponding to the MIB node logTime. |
|
Description |
Log description, corresponding to the MIB node logDescription. |
The above example shows that event 1 has generated two logs:
l 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.
l 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.
Syntax
display rmon history [ interface-type interface-number ]
View
Any view
Default Level
1: Monitor level
Parameters
interface-type interface-number: Specifies an interface by its type and number.
Description
Use the display rmon history command to display RMON history control entry and history sampling information.
After you have created history control entry on an interface, the system calculates the information of the interface periodically and saves this information to the etherHistoryEntry table. You can use this command to display the entries in this table.
You can configure the number of history sampling records that can be displayed and the history sampling interval through the rmon history command.
Related commands: rmon history.
Examples
# Display RMON history control entry and history sampling information for interface GigabitEthernet1/0/1.
<Sysname> display rmon history gigabitethernet 1/0/1
HistoryControlEntry 1 owned by null is VALID
Samples interface : GigabitEthernet1/0/1<ifIndex.1>
Sampling interval : 10(sec) with 5 buckets max
Sampled values of record 1 :
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
Sampled values of record 2 :
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
Sampled values of record 3 :
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
Sampled values of record 4 :
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
Sampled values of record 5 :
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 display rmon history command output description
|
Field |
Description |
|
HistoryControlEntry |
History control entry, corresponding to the MIB node etherHistoryIndex. |
|
owned by |
Owner of the entry, corresponding to the MIB node historyControlOwner. |
|
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 historyControlStatus. |
|
Samples Interface |
The sampled interface |
|
Sampling interval |
Sampling period, in seconds, corresponding to the MIB node historyControlInterval. The system samples the information of an interface periodically. |
|
buckets max |
The maximum number of history table entries that can be saved, corresponding to the MIB node historyControlBucketsGranted. If the specified value of the buckets argument exceeds the history table size supported by the device, the supported history table size is displayed. If the current number of the entries in the table has reached the maximum number, the system will delete the earliest entry to save the latest one. |
|
Sampled values of record number |
The (number)th statistics recorded in the system cache. Statistics records are numbered according to the order of time they are saved into the cache. |
|
dropevents |
Dropped packets during the sampling period, corresponding to the MIB node etherHistoryDropEvents. |
|
octets |
Number of octets received during the sampling period, corresponding to the MIB node etherHistoryOctets. |
|
packets |
Number of packets received during the sampling period, corresponding to the MIB node etherHistoryPkts. |
|
broadcastpackets |
Number of broadcasts received during the sampling period, corresponding to the MIB node etherHistoryBroadcastPkts. |
|
multicastpackets |
Number of multicasts received during the sampling period, corresponding to the MIB node etherHistoryMulticastPkts. |
|
CRC alignment errors |
Number of packets received with CRC alignment errors during the sampling period, corresponding to the MIB node etherHistoryCRCAlignErrors. |
|
undersize packets |
Number of undersize packets received during the sampling period, corresponding to the MIB node etherHistoryUndersizePkts. |
|
oversize packets |
Number of oversize packets received during the sampling period, corresponding to the MIB node etherHistoryOversizePkts. |
|
fragments |
Number of fragments received during the sampling period, corresponding to the MIB node etherHistoryFragments. |
|
jabbers |
Number of jabbers received during the sampling period, corresponding to the MIB node etherHistoryJabbers. |
|
collisions |
Number of colliding packets received during the sampling period, corresponding to the MIB node etherHistoryCollisions. |
|
utilization |
Bandwidth utilization during the sampling period, corresponding to the MIB node etherHistoryUtilization. |
Syntax
display rmon prialarm [ entry-number ]
View
Any view
Default Level
1: Monitor level
Parameters
entry-number: Private alarm entry index, in the range 1 to 65535. If no entry is specified, the configuration of all private alarm entries is displayed.
Description
Use the display rmon prialarm command to display the configuration of the specified or all private alarm entries.
Related commands: rmon prialarm.
Examples
# Display the configuration of all private alarm entries.
<Sysname> display rmon prialarm
PrialarmEntry 1 owned by user1 is VALID.
Samples type : absolute
Variable formula : (.1.3.6.1.2.1.16.1.1.1.6.1*100/.1.3.6.1.2.1.16.1.1.1.5.1)
Description : ifUtilization. GigabitEthernet1/0/1
Sampling interval : 10(sec)
Rising threshold : 80(linked with event 1)
Falling threshold : 5(linked with event 2)
When startup enables : risingOrFallingAlarm
This entry will exist : forever
Latest value : 85
Table 1-5 display rmon prialarm command output description
|
Field |
Description |
|
PrialarmEntry |
The entry of the private alarm table |
|
owned by |
Owner of the entry, user1 in this example |
|
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.) |
|
Samples type |
Sampling type, whose value can be absolute or delta. |
|
Sampling interval |
Sampling interval, in seconds. The system performs absolute sample or delta sample to sampling variables according to the sampling interval. |
|
Rising threshold |
Alarm rising threshold. An event is triggered when the sampled value is greater than or equal to this threshold. |
|
Falling threshold |
Alarm falling threshold. An event is triggered when the sampled value is less than or equal to this threshold. |
|
linked with event |
Event index associated with the prialarm |
|
When startup enables |
How can an alarm be triggered |
|
This entry will exist |
The lifetime of the entry, which can be forever or span the specified period |
|
Latest value |
The count result of the last sample |
Syntax
display rmon statistics [ interface-type interface-number ]
View
Any view
Default Level
1: Monitor level
Parameters
interface-type interface-number: Specifies an interface by its type and number.
Description
Use the display rmon statistics command to display RMON statistics.
This command displays the interface statistics during the period from the time the statistics entry is created to the time the command is executed. The statistics are cleared after the device reboots.
Related commands: rmon statistics.
Examples
# Display RMON statistics for interface GigabitEthernet1/0/1.
<Sysname> display rmon statistics gigabitethernet1/0/1
EtherStatsEntry 1 owned by null is VALID.
Interface : GigabitEthernet1/0/1<ifIndex.3>
etherStatsOctets : 43393306 , etherStatsPkts : 619825
etherStatsBroadcastPkts : 503581 , etherStatsMulticastPkts : 44013
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 display rmon statistics command output description
|
Field |
Description |
|
EtherStatsEntry |
The entry of the statistics table, corresponding to the MIB node etherStatsIndex. |
|
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 etherStatsStatus. |
|
Interface |
Interface on which statistics are gathered, corresponding to the MIB node etherStatsDataSource. |
|
etherStatsOctets |
Number of octets received and transmitted by the interface during the statistical period, corresponding to the MIB node etherStatsOctets. |
|
etherStatsPkts |
Number of packets received and transmitted by the interface during the statistical period, corresponding to the MIB node etherStatsPkts. |
|
etherStatsBroadcastPkts |
Number of broadcast packets received and transmitted by the interface during the statistical period, corresponding to the MIB node etherStatsBroadcastPkts. |
|
etherStatsMulticastPkts |
Number of multicast packets received and transmitted by the interface during the statistical period, corresponding to the MIB node etherStatsMulticastPkts. |
|
etherStatsUndersizePkts |
Number of undersize packets received and transmitted by the interface during the statistical period, corresponding to the MIB node etherStatsUndersizePkts. |
|
etherStatsOversizePkts |
Number of oversize packets received and transmitted by the interface during the statistical period, corresponding to the MIB node etherStatsOversizePkts. |
|
etherStatsFragments |
Number of undersize packets with CRC errors received and transmitted by the interface during the statistical period, corresponding to the MIB node etherStatsFragments. |
|
etherStatsJabbers |
Number of oversize packets with CRC errors received and transmitted by the interface during the statistical period, corresponding to the MIB node etherStatsJabbers. |
|
etherStatsCRCAlignErrors |
Number of packets with CRC errors received and transmitted on the interface during the statistical period, corresponding to the MIB node etherStatsCRCAlignErrors. |
|
etherStatsCollisions |
Number of collisions received and transmitted on the interface during the statistical period, corresponding to the MIB node etherStatsCollisions. |
|
etherStatsDropEvents |
Total number of drop events received and transmitted on the interface during the statistical period, corresponding to the MIB node etherStatsDropEvents. |
|
Packets received according to length: 64 : 0 , 65-127 : 0 , 128-255 : 0 256-511: 0 , 512-1023: 0 , 1024-1518: 0 |
Statistics of packets received and transmitted according to length during the statistical period (Hardware support is needed for the statistics. If the hardware does not support the function, all statistics are displayed as 0.), in which: l Information of the field 64 corresponds to the MIB node etherStatsPkts64Octets l Information of the field 65-127 corresponds to the MIB node etherStatsPkts65to127Octets l Information of the field 128-255 corresponds to the MIB node etherStatsPkts128to255Octets l Information of the field 256-511 corresponds to the MIB node etherStatsPkts256to511Octets l Information of the field 512-1023 corresponds to the MIB node etherStatsPkts512to1023Octets l Information of the field 1024-1518 corresponds to the MIB node etherStatsPkts1024to1518Octets |
Syntax
rmon alarm entry-number alarm-variable sampling-interval { absolute | delta } rising-threshold threshold-value1 event-entry1 falling-threshold threshold-value2 event-entry2 [ owner text ]
undo rmon alarm entry-number
View
System view
Default Level
2: System level
Parameters
entry-number: Alarm entry index, in the range 1 to 65535.
alarm-variable: Alarm variable, a string of 1 to 256 characters. It can be in dotted object identifier (OID) format (in the format of entry.integer.instance or leaf node name.instance, for example, 1.3.6.1.2.1.2.1.10.1), or a node name like ifInOctets.1. Only variables that can be parsed into INTEGER (INTEGER, Counter, Gauge, or Time Ticks) in the ASN.1 can be used for the alarm-variable argument, such as the instance of the leaf node (like etherStatsOctets, etherStatsPkts, etherStatsBroadcastPkts, and so on) of the etherStatsEntry entry, the instance of the leaf node (like ifInOctets, ifInUcastPkts, ifInNUcastPkts, and so on) of the ifEntry entry.
sampling-interval: Sampling interval, in the range 5 to 65,535 seconds.
absolute: Sets the sampling type to absolute, namely, the system obtains the value of the variable when the sampling time is reached.
delta: Sets the sampling type to delta, namely, the system obtains the variation value of the variable during the sampling interval when the sampling time is reached.
rising-threshold threshold-value1 event-entry1: Sets the rising threshold, where threshold-value1 represents the rising threshold, in the range –2,147,483,648 to +2,147,483,647, and event-entry1 represents the index of the event triggered when the rising threshold is reached. event-entry1 ranges from 0 to 65,535, with 0 meaning no corresponding event is triggered and no event action is taken when an alarm is triggered.
falling-threshold threshold-value2 event-entry2: Sets the falling threshold, where threshold-value2 represents the falling threshold, in the range –2,147,483,648 to +2,147,483,647 and event-entry2 represents the index of the event triggered when the falling threshold is reached. event-entry2 ranges from 1 to 65,535.
owner text: Owner of the entry, a string of 1 to 127 characters. It is case sensitive and space is supported.
Description
Use the rmon alarm command to create an entry in the RMON alarm table.
Use the undo rmon alarm command to remove a specified entry from the RMON alarm table.
This command defines an alarm entry, so as to trigger the specified event when abnormity occurs. The event defines how to deal with the abnormity.
The following is how the system handles alarm entries:
1) Samples the alarm variables at the specified interval.
2) Compares the sampled values with the predefined threshold and does the following:
l If the rising threshold is reached, triggers the event specified by the event-entry1 argument.
l If the falling threshold is reached, triggers the event specified by the event-entry2 argument.
l Before creating an alarm entry, define the events to be referenced in the event table with the rmon event command.
l When you create an entry, if the values of the specified alarm variable (alarm-variable), sampling interval (sampling-interval), sampling type (absolute or delta), rising threshold (threshold-value1) and falling threshold (threshold-value2) are identical to those of the existing alarm entry, the system considers their configurations are the same and the creation fails.
l You can create up to 60 alarm entries.
Related commands: display rmon alarm, rmon event, rmon history, rmon statistics.
Examples
# Add entry 1 in the alarm table and sample the node 1.3.6.1.2.1.16.1.1.1.4.1 at a sampling interval of 10 seconds in absolute sampling type. Trigger event 1 when the sampled value is greater than or equal to the rising threshold of 5000, and event 2 when the sampled value is less than or equal to the falling threshold of 5. Set the owner of the entry to be user1.
<Sysname> system-view
[Sysname] rmon event 1 log
[Sysname] rmon event 2 none
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rmon statistics 1
[Sysname-GigabitEthernet1/0/1] quit
[Sysname] rmon alarm 1 1.3.6.1.2.1.16.1.1.1.4.1 10 absolute rising-threshold 5000 1 falling-threshold 5 2 owner user1
1.3.6.1.2.1.16.1.1.1.4 is the OID of the leaf node etherStatsOctets. It represents the statistics of the received packets on the interface, in bytes. In the above example, you can use etherStatsOctets.1 to replace the parameter 1.3.6.1.2.1.16.1.1.1.4.1, where 1 indicates the serial number of the interface statistics entry. Therefore, if you execute the rmon statistics 5 command, you can use etherStatsOctets.5 to replace the parameter.
The above configuration implements the following:
l Sampling and monitoring interface GigabitEthernet1/0/1
l Obtaining the absolute value of the number of received packets. If the total bytes of the received packets reach 5,000, the system will log the event; if the total bytes of the received packets are no more than 5, the system will take no action.
Syntax
rmon event entry-number [ description string ] { log | log-trap log-trapcommunity | none | trap trap-community } [ owner text ]
undo rmon event entry-number
View
System view
Default Level
2: System level
Parameters
entry-number: Event entry index, in the range 1 to 65,535.
description string: Event description, a string of 1 to 127 characters.
log: Logs the event when it occurs.
log-trap log-trapcommunity: Log and trap events. The system performs both logging and trap sending when the event occurs. log-trapcommunity indicates the community name of the network management station that receives trap messages, a string of 1 to 127 characters.
none: Performs no action when the event occurs.
trap trap-community: Trap event. The system sends a trap with a community name when the event occurs. trap-community specifies the community name of the network management station that receives trap messages, a string of 1 to 127 characters.
owner text: Owner of the entry, a string of 1 to 127 characters. It is case sensitive and space is supported.
Description
Use the rmon event command to create an entry in the RMON event table.
Use the undo rmon event command to remove a specified entry from the RMON event table.
When create an event entry, you can define the actions that the system will take when the event is triggered by its associated alarm in the alarm table. According to your configuration, the system can log the event, send a trap, do both, or do neither at all.
Related commands: display rmon event, rmon alarm, rmon prialarm.
l When you create an entry, if the values of the specified event description (description string), event type (log, trap, logtrap or none), and community name (trap-community or log-trapcommunity) are identical to those of the existing event entry, the system considers their configurations are the same and the creation fails.
l You can create up to 60 alarm entries.
Examples
# Create event 10 in the RMON event table.
<Sysname> system-view
[Sysname] rmon event 10 log owner user1
Syntax
rmon history entry-number buckets number interval sampling-interval [ owner text ]
undo rmon history entry-number
View
Ethernet interface view
Default Level
2: System level
Parameters
entry-number: History control entry index, in the range 1 to 65535.
buckets number: History table size for the entry, in the range 1 to 65,535.
interval sampling-interval: Sampling period, in the range 5 to 3600 seconds.
owner text: Owner of the entry, a string of 1 to 127 characters. It is case sensitive and space is supported.
Description
Use the rmon history command to create an entry in the RMON history control table.
Use the undo rmon history command to remove a specified entry from the RMON history control table.
After an entry is created, the system periodically samples the number of packets received/sent on the current interface, and saves the statistics as an instance under the leaf node of the etherHistoryEntry table. The maximum number of history entries can be saved in the table is specified by buckets number. If the number of the entries in the table has reached the maximum number, the system will delete the earliest entry to save the latest one. The statistics include total number of received packets on the current interface, total number of broadcast packets, and total number of multicast packets in a sampling period,
When you create an entry in the history table, if the specified history table size exceeds that supported by the device, the entry will be created. However, the validated value of the history table size corresponding to the entry is that supported by the device. You can use the display rmon history command to view the configuration result.
l When you create an entry, if the value of the specified sampling interval (interval sampling-interval) is identical to that of the existing history entry, the system considers their configurations are the same and the creation fails.
l You can create up to 100 alarm entries.
Related commands: display rmon history.
Examples
# Create RMON history control entry 1 for interface GigabitEthernet1/0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rmon history 1 buckets 10 interval 5 owner user1
Syntax
rmon prialarm entry-number prialarm-formula prialarm-des sampling-interval { absolute | changeratio | delta } 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
Default Level
2: System level
Parameters
entry-number: Index of a private alarm entry, in the range 1 to 65535.
prialarm-formula: Private alarm variable formula, a string of 1 to 256 characters. The variables in the formula must be represented in OID format that starts with a point “.”, the formula (.1.3.6.1.2.1.2.1.10.1)*8 for example. You may perform the basic operations of addition, subtraction, multiplication, and division on these variables. The operations should yield a long integer. To prevent errors, make sure that the result of each calculating step falls into the value range for long integers.
prialarm-des: Private alarm entry description, a string of 1 to 127 characters.
sampling-interval: Sampling interval, in the range 10 to 65,535 seconds.
absolute | changeratio | delta: Sets the sampling type to absolute, delta, or change ratio. Absolute sampling is to obtain the value of the variable when the sampling time is reached; delta sampling is to obtain the variation value of the variable during the sampling interval when the sampling time is reached; change ratio sampling is not supported at present.
rising-threshold threshold-value1 event-entry1: Sets the rising threshold, where threshold-value1 represents the rising threshold, in the range –2,147,483,648 to +2,147,483,647, and event-entry1 represents the index of the event triggered when the rising threshold is reached. event-entry1 ranges from 0 to 65,535, with 0 meaning no corresponding event is triggered and no event action is taken when an alarm is triggered.
falling-threshold threshold-value2 event-entry2: Sets the falling threshold, where threshold-value2 represents the falling threshold, in the range –2,147,483,648 to +2,147,483,647 and event-entry2 represents the index of the event triggered when the falling threshold is reached. event-entry2 ranges from 1 to 65,535.
forever: Indicates that the lifetime of the private alarm entry is infinite.
cycle cycle-period: Sets the lifetime period of the private alarm entry, in the range 0 to 2,147,483,647 seconds.
owner text: Owner of the entry, a string of 1 to 127 characters. It is case sensitive and space is supported.
Description
Use the rmon prialarm command to create an entry in the private alarm table of RMON.
Use the undo rmon prialarm command to remove a private alarm entry from the private alarm table of RMON.
The following is how the system handles private alarm entries:
1) Samples the private alarm variables in the private alarm formula at the specified sampling interval.
2) Performs calculation on the sampled values with the formula.
3) Compares the calculation result with the predefined thresholds and does the following:
l If the result is equal to or greater than the rising threshold, triggers the event specified by the event-entry1 argument.
l If the result is equal to or smaller than the falling threshold, triggers the event specified by the event-entry2 argument.
l Before creating an alarm entry, define the events to be referenced in the event table with the rmon event command.
l When you create an entry, if the values of the specified alarm variable formula (prialarm-formula), sampling type (absolute changeratio or delta), rising threshold (threshold-value1) and falling threshold (threshold-value2) are identical to those of the existing alarm entry, the system considers their configurations are the same and the creation fails.
l You can create up to 50 pri-alarm entries.
Related commands: display rmon prialarm, rmon event, rmon history, rmon statistics.
Examples
# Create entry 5 in the private alarm table. Calculate the private alarm variables with the (1.3.6.1.2.1.16.1.1.1.6.1*100/.1.3.6.1.2.1.16.1.1.1.5.1) formula and sample the corresponding variables at intervals of 10 seconds. Rising threshold of 80 corresponds to event 1 (and record the event into the log table); falling threshold of 5 corresponds to event 2 (but neither log it nor send a trap). Set the lifetime of the entry to forever and owner to user1.
<Sysname> system-view
[Sysname] rmon event 1 log
[Sysname] rmon event 2 none
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rmon statistics 1
[Sysname-GigabitEthernet1/0/1] quit
[Sysname] rmon prialarm 1 (1.3.6.1.2.1.16.1.1.1.6.1*100/.1.3.6.1.2.1.16.1.1.1.5.1)
BroadcastPktsRatioOfGigabitEthernet1/0/1 10 absolute rising_threshold 80 1 falling_threshold 5 2 entrytype forever owner user1
1.3.6.1.2.1.16.1.1.1.6.1 is the OID of the node etherStatsBroadcastPkts.1, and 1.3.6.1.2.1.16.1.1.1.5.1 is the OID of the node etherStatsPkts.1. 1 indicates the serial number of the interface statistics entry. Therefore, if you execute the rmon statistics 5 command, you should use 1.3.6.1.2.1.16.1.1.1.6.5 and 1.3.6.1.2.1.16.1.1.1.5.5.
The above configuration implements the following:
l Sampling and monitoring interface GigabitEthernet1/0/1
l If the portion of broadcast packets received in the total packets is greater than or equal to 80%, the system will log the event; if the portion is less than or equal to 5%, the system will take no action.
You can view the event log using the display rmon eventlog command.
Syntax
rmon statistics entry-number [ owner text ]
undo rmon statistics entry-number
View
Ethernet interface view
Default Level
2: System level
Parameters
entry-number: Index of statistics entry, in the range 1 to 65535.
owner text: Owner of the entry, a string of 1 to 127 characters. It is case sensitive and space is supported.
Description
Use the rmon statistics command to create an entry in the RMON statistics table.
Use the undo rmon statistics command to remove a specified entry from the RMON statistics table.
After an entry is created, the system continuously calculates the information of the interface. Statistics include number of collisions, CRC alignment errors, number of undersize or oversize packets, number of broadcasts, number of multicasts, number of bytes received, number of packets received. The statistics are cleared after the device reboots.
To display information for the RMON statistics table, use the display rmon statistics command.
l Only one statistics entry can be created on one interface.
l You can create up to 100 statistics entries.
Examples
# Create an entry in the RMON statistics table for interface GigabitEthernet1/0/1. The index of the entry is 20, and the owner of the entry is user1.
<Sysname> system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rmon statistics 20 owner user1
