Contents

RMON commands· 1

display rmon alarm·· 1

display rmon event 3

display rmon eventlog· 4

display rmon history· 5

display rmon prialarm·· 8

display rmon statistics· 10

rmon alarm·· 12

rmon event 14

rmon history· 15

rmon prialarm·· 16

rmon statistics· 18

 

RMON commands

display rmon alarm

Use display rmon alarm to display entries in the RMON alarm table.

Syntax

display rmon alarm [ entry-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

entry-number: Specifies an alarm entry index in the range of 1 to 65535. If you do not specify an entry, the command displays all entries in the RMON alarm table.

Examples

# Display all entries in the RMON alarm table.

<Sysname> display rmon alarm

AlarmEntry 1 owned by user1 is VALID.

  Sample type          : absolute

  Sampled variable     : 1.3.6.1.2.1.16.1.1.1.4.1<etherStatsOctets.1>

  Sampling interval (in seconds)     : 10

  Rising threshold      : 50(associated with event 1)

  Falling threshold     : 5(associated with event 2)

  Alarm sent upon entry startup  : risingOrFallingAlarm

  Latest value          : 0

Table 1 Command output

Field	Description
AlarmEntry entry-number owned by owner is status.	Alarm entry owner and status: ·     entry-number—Alarm entry index (MIB object alarmIndex). ·     owner—Entry owner (MIB object alarmOwner). ·     status—Entry status (MIB object alarmStatus): ¡     VALID—The entry is valid. ¡     UNDERCREATION—The entry is invalid. The status field is not configurable at the CLI. All alarm entries created from the CLI are valid by default. The display rmon alarm command can display invalid entries, but the display current-configuration and display this commands do not display their settings.
Sample type	Sample type (MIB object alarmSampleType): ·     absolute—RMON compares the value of the variable with the rising and falling thresholds at the end of the sampling interval. ·     delta—RMON subtracts the value of the variable at the previous sample from the current value, and then compares the difference with the rising and falling thresholds.
Sampled variable	Monitored variable (MIB object alarmVariable).
Sampling interval	Interval (in seconds) at which data is sampled and compared with the rising and falling thresholds. The MIB object for this field is alarmInterval.
Rising threshold	Alarm rising threshold (MIB object alarmRisingThreshold). A rising alarm will be generated when the following conditions are met: ·     The current sampled value is greater than or equal to this threshold. ·     The value at the previous sampling interval was less than this threshold. A rising alarm will also be generated when the following conditions are met: ·     The first sample after this entry becomes valid is greater than or equal to this threshold. ·     The associated alarmStartupAlarm instance is equal to risingAlarm or risingOrFallingAlarm.
associated with event	Event index (EventEntry) associated with the alarm: ·     MIB object alarmRisingEventIndex stores the event index that is used when the rising threshold is crossed. ·     MIB object alarmFallingEventIndex stores the event index that is used when the falling threshold is crossed.
Falling threshold	Alarm falling threshold (MIB object alarmFallingThreshold). A falling alarm will be generated when the following conditions are met: ·     The current sampled value is less than or equal to this threshold ·     The value at the previous sampling interval was greater than this threshold. A falling alarm will also be generated when the following conditions are met: ·     The first sample after this entry becomes valid is less than or equal to this threshold. ·     The associated alarmStartupAlarm is equal to fallingAlarm or risingOrFallingAlarm.
Alarm sent upon entry startup	Alarm that can be generated when the entry becomes valid (MIB object alarmStartupAlarm): ·     risingAlarm—Generates a rising alarm if the first sample after the entry becomes valid is greater than or equal to the rising threshold. ·     fallingAlarm—Generates a falling alarm if the first sample after the entry becomes valid is less than or equal to the rising threshold. ·     risingOrFallingAlarm—Generates a rising alarm or falling alarm if the first sample after the entry becomes valid crosses the rising threshold or falling threshold. The default is risingOrFallingAlarm.
Latest value	Most recent sampled value (MIB object alarmValue).

 

Related commands

rmon alarm

display rmon event

Use display rmon event to display RMON event entries.

Syntax

display rmon event [ entry-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

entry-number: Specifies an event entry index in the range of 1 to 65535. If you do not specify an entry, the command displays all event entries.

Usage guidelines

An event entry includes the following information:

·     Event index.

·     Event owner.

·     Event description.

·     Action triggered by the event (such as logging the event or sending an SNMP notification).

·     Last time when the event occurred (seconds that elapsed since the system startup).

Examples

# Display all RMON event entries.

<Sysname> display rmon event

EventEntry 1 owned by user1 is VALID.

  Description: N/A

  Community: Security

  Take the action log-trap when triggered, last triggered at 0days 00h:02m:27s uptime.

Table 2 Command output

Field	Description
EventEntry entry-number owned by owner is status.	Event entry owner and status: ·     entry-number—Event entry index (MIB object eventIndex). ·     owner—Entry owner (MIB object eventOwner). ·     status—Entry status (MIB object eventStatus): ¡     VALID—The entry is valid. ¡     UNDERCREATION—The entry is invalid. The status field is not configurable at the CLI. All alarm entries created from the CLI are valid by default. The display rmon event command can display invalid entries, but the display current-configuration and display this commands do not display their settings.
Description	Event description (MIB object eventDescription).
Community	SNMP community name for the RMON event (MIB object eventCommunity). You can specify an SNMP community name when you create an RMON event entry, but the setting does not take effect. The system always uses the settings configured with the SNMP feature when it sends RMON event notifications.
Take the action action when triggered	Actions that the system takes when the event occurs (MIB object eventType): ·     none—Takes no action. ·     log—Logs the event. ·     trap—Sends an SNMP notification. ·     log-trap—Logs the event and sends an SNMP notification.
last triggered at time uptime	Last time when the event occurred, which is represented as the amount of time that elapsed since the system startup. The MIB object for this field is eventLastTimeSent.

 

Related commands

rmon event

display rmon eventlog

Use display rmon eventlog to display event log entries.

Syntax

display rmon eventlog [ entry-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

entry-number: Specifies an event entry index in the range of 1 to 65535. If you do not specify an entry, the command displays log entries for all event entries.

Usage guidelines

If the log action is specified for an event, the system adds a record in the event log table each time the event occurs. Each record contains the log entry index, time when the event was logged (the amount of time that elapsed since system startup), and event description.

The system can maintain a maximum of 10 records for an event. The most recent record replaces the oldest record if the number of records reaches 10.

Examples

# Display the RMON log for event entry 99.

<Sysname> display rmon eventlog 99

EventEntry 99 owned by ww is VALID.

  LogEntry 99.1 created at 50days 08h:54m:44s uptime.

  Description: The 1.3.6.1.2.1.16.1.1.1.4.5 defined in alarmEntry 77,

     uprise 16760000 with alarm value 16776314. Alarm sample type is absolute.

  LogEntry 99.2 created at 50days 09h:11m:13s uptime.

  Description: The 1.3.6.1.2.1.16.1.1.1.4.5 defined in alarmEntry 77,

     less than(or =) 20000000 with alarm value 16951648. Alarm sample type is absolute.

  LogEntry 99.3 created at 50days 09h:18m:43s uptime.

  Description: The alarm formula defined in prialarmEntry 777,

     less than(or =) 15000000 with alarm value 14026493. Alarm sample type is absolute.

  LogEntry 99.4 created at 50days 09h:23m:28s uptime.

  Description: The alarm formula defined in prialarmEntry 777,

     uprise 17000000 with alarm value 17077846. Alarm sample type is absolute.

This example shows that the event log table has four records for event 99:

·     Two records were created when event 99 was triggered by alarm entry 77.

·     Two records were created when event 99 was triggered by private alarm entry 777.

Table 3 Command output

Field	Description
EventEntry entry-number owned by owner is status.	Event log entry owner and status: ·     entry-number—Event log entry index (MIB object logEventIndex), which is the same as the event entry index for which this log entry is generated. ·     owner—Entry owner (MIB object eventOwner). ·     status—Entry status (MIB object eventStatus): ¡     VALID—The entry is valid (default value). ¡     UNDERCREATION—The entry is invalid. The status field is not configurable at the CLI. All event log entries are valid by default. The display rmon eventlog command can display invalid entries, but the display current-configuration and display this commands do not display their settings.
LogEntry entry-number created at created-time uptime.	Time when an event record was created: ·     entry-number—Event record index (represented as logEventIndex.logIndex), which uniquely identifies the record among all records for the event. ·     created-time—Time when the event entry was created (MIB object logTime).
Description	Record description (MIB object logDescription).

 

Related commands

rmon event

display rmon history

Use display rmon history to display RMON history control entries and history samples of Ethernet statistics for Ethernet interfaces.

Syntax

display rmon history [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, the command displays history samples for all interfaces that have an RMON history control entry.

Usage guidelines

RMON uses the etherHistoryTable object to store the history samples of Ethernet statistics for Ethernet interfaces.

To collect history samples for an Ethernet interface, you must first create a history control entry on the interface.

To configure the number of history samples that can be displayed and the history sampling interval, use the rmon history command.

Examples

# Display the RMON history control entry and history samples for Ten-GigabitEthernet 1/1/1.

<Sysname> display rmon history ten-gigabitethernet 1/1/1

HistoryControlEntry 6 owned by user1 is VALID.

  Sampled interface     : Ten-GigabitEthernet 1/1/1 <ifIndex.117>

  Sampling interval     : 8(sec) with 3 buckets max

  Sampling record 1 :

    dropevents        : 0         , octets               : 5869

    packets           : 54        , broadcast packets    : 9

    multicast packets : 23        , CRC alignment errors : 0

    undersize packets : 0         , oversize packets     : 0

    fragments         : 0         , jabbers              : 0

    collisions        : 0         , utilization          : 0

  Sampling record 2 :

    dropevents        : 0         , octets               : 5367

    packets           : 55        , broadcast packets    : 1

    multicast packets : 7         , CRC alignment errors : 0

    undersize packets : 0         , oversize packets     : 0

    fragments         : 0         , jabbers              : 0

    collisions        : 0         , utilization          : 0

  Sampling record 3 :

    dropevents        : 0         , octets               : 936

    packets           : 10        , broadcast packets    : 0

    multicast packets : 6         , CRC alignment errors : 0

    undersize packets : 0         , oversize packets     : 0

    fragments         : 0         , jabbers              : 0

    collisions        : 0         , utilization          : 0

HistoryControlEntry 7 owned by user1 is VALID.

  Sampled interface     : Ten-GigabitEthernet 1/1/1 <ifIndex.117>

  Sampling interval     : 9(sec) with 1 buckets max

  Sampling record 1 :

    dropevents        : 0         , octets               : 1150

    packets           : 12        , broadcast packets    : 0

    multicast packets : 8         , CRC alignment errors : 0

    undersize packets : 0         , oversize packets     : 0

    fragments         : 0         , jabbers              : 0

    collisions        : 0         , utilization          : 0

Table 4 Command output

Field	Description
HistoryControlEntry entry-number owned by owner is status.	Status and owner of the history control entry: ·     entry-number—History control entry index (MIB object historyControlIndex). ·     owner—Entry owner (MIB object historyControlOwner). ·     status—Entry status (MIB object historyControlStatus): ¡     VALID—The entry is valid. ¡     UNDERCREATION—The entry is invalid. The status field is not configurable at the CLI. All history control entries created from the CLI are valid by default. The display rmon history command can display invalid entries, but the display current-configuration and display this commands do not display their settings.
Sampled Interface	Sampled interface (MIB object historyControlDataSource).
Sampling interval	Sampling interval in seconds (MIB object historyControlInterval).
buckets max	Maximum number of samples that can be saved for the history control entry (MIB object historyControlBucketsGranted). If the expected bucket size specified with the rmon history command exceeds the available history table size, RMON sets the bucket size as closely to the expected bucket size as possible. If the bucket has been full, RMON overwrites the oldest sample with the new sample.
Sampling record	History sample index (MIB object etherHistorySampleIndex).
dropevents	Total number of events in which packets were dropped during the sampling interval (MIB object etherHistoryDropEvents). NOTE: This statistic is the number of times that a drop condition occurred. It is not necessarily the total number of dropped packets.
octets	Total number of octets received during the sampling interval (MIB object etherHistoryOctets).
packets	Total number of packets (including bad packets) received during the sampling interval (MIB object etherHistoryPkts).
broadcast packets	Number of broadcasts received during the sampling interval (MIB object etherHistoryBroadcastPkts).
multicast packets	Number of multicasts received during the sampling interval (MIB object etherHistoryMulticastPkts).
CRC alignment errors	Number of packets received with CRC alignment errors during the sampling interval (MIB object etherHistoryCRCAlignErrors).
undersize packets	Number of undersize packets received during the sampling interval (MIB object etherHistoryUndersizePkts). Undersize packets are shorter than 64 octets (excluding framing bits but including FCS octets).
oversize packets	Number of oversize packets received during the sampling interval (MIB object etherHistoryOversizePkts). Oversize packets are longer than 1518 octets (excluding framing bits but including FCS octets).
fragments	Number of undersize packets with CRC errors received during the sampling interval (MIB object etherHistoryFragments).
jabbers	Number of oversize packets with CRC errors received during the sampling interval (MIB object etherHistoryJabbers).
collisions	Number of colliding packets received during the sampling interval (MIB object etherHistoryCollisions).
utilization	Bandwidth utilization (in hundreds of a percent) during the sampling period (MIB object etherHistoryUtilization).

 

Related commands

rmon history

display rmon prialarm

Use display rmon prialarm to display entries in the private RMON alarm table.

Syntax

display rmon prialarm [ entry-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

entry-number: Specifies an alarm entry index in the range of 1 to 65535. If you do not specify an entry, the command displays all private alarm entries.

Examples

# Display all private alarm entries.

<Sysname> display rmon prialarm

PrialarmEntry 1 owned by user1 is VALID.

  Sample 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.Ten-GigabitEthernet1/1/1

  Sampling interval (in seconds)     : 10

  Rising threshold      : 80(associated with event 1)

  Falling threshold     : 5(associated with event 2)

  Alarm sent upon entry startup  : risingOrFallingAlarm

  Entry lifetime : forever

  Latest value          : 85

Table 5 Command output

Field	Description
PrialarmEntry entry-number owned by owner is status.	Alarm entry owner and status: ·     entry-number—Alarm entry index (MIB object hh3cRmonExtAlarmIndex). ·     owner—Entry owner (MIB object hh3cRmonExtAlarmOwner). ·     status—Entry status (MIB object hh3cRmonExtAlarmStatus): ¡     VALID—The entry is valid. ¡     UNDERCREATION—The entry is invalid. The status field is not configurable at the CLI. All alarm entries created from the CLI are valid by default. The display rmon prialarm command can display invalid entries, but the display current-configuration and display this commands do not display their settings.
Sample type	Sample type (MIB object hh3cRmonExtAlarmSampleType): ·     absolute—RMON compares the calculation result of the variable formula with the rising and falling thresholds at the end of the sampling interval. ·     delta—RMON subtracts the calculation result of the variable formula for the previous sampling interval from the current calculation result, and then compares the difference with the rising and falling thresholds.
Variable formula	Variable formula (MIB object hh3cRmonExtAlarmVariable).
Description	Description of the alarm entry (MIB object hh3cRmonExtAlarmSympol.
Sampling interval	Interval (in seconds) at which data is sampled and compared with the rising and falling thresholds. The MIB object for this field is hh3cRmonExtAlarmInterval.
Rising threshold	Alarm rising threshold (MIB node hh3cRmonExtAlarmRisingThreshold). A rising alarm is generated when the following conditions are met: ·     The current sampled value is greater than or equal to this threshold. ·     The value at the previous sampling interval was less than this threshold. A rising alarm is also generated when the following conditions are met: ·     The first sample after this entry becomes valid is greater than or equal to this threshold. ·     The associated hh3cRmonExtAlarmStartupAlarm instance is equal to risingAlarm or risingOrFallingAlarm.
Falling threshold	Alarm falling threshold (MIB object hh3cRmonExtAlarmFallingThreshold). A falling alarm is generated when the following conditions are met: ·     The current sampled value is less than or equal to this threshold. ·     The value at the previous sampling interval was greater than this threshold. A falling alarm is also generated when the following conditions are met: ·     The first sample after this entry becomes valid is less than or equal to this threshold. ·     The associated hh3cRmonExtAlarmStartupAlarm instance is equal to fallingAlarm or risingOrFallingAlarm.
associated with event	Event index associated with the alarm: ·     MIB object hh3cRmonExtAlarmRisingEvtIndex stores the event index that is used when the rising threshold is crossed. ·     MIB object hh3cRmonExtAlarmFallingEvtIndex stores the event index that is used when the falling threshold is crossed.
Alarm sent upon entry startup	Alarm that can be generated when the entry becomes valid (MIB object hh3cRmonExtAlarmStartupAlarm): ·     risingAlarm—Generates a rising alarm if the first sample after the entry becomes valid is greater than or equal to the rising threshold. ·     fallingAlarm—Generates a falling alarm if the first sample after the entry becomes valid is less than or equal to the rising threshold. ·     risingOrFallingAlarm—Generates a rising alarm or falling alarm if the first sample after the entry becomes valid crosses the rising threshold or falling threshold. The default is risingOrFallingAlarm.
Entry lifetime	Lifetime of the entry (MIB objects hh3cRmonExtAlarmStatType and hh3cRmonExtAlarmStatCycle). ·     If the lifetime is set to forever, the entry never expires. ·     If the lifetime is set to an amount of time, the entry is removed when the timer expires.
Latest value	Most recent sampled value (MIB object hh3cRmonExtAlarmValue).

 

NOTE: The prefix of the MIB objects varies by device brands.

 

Related commands

rmon prialarm

display rmon statistics

Use display rmon statistics to display RMON statistics.

Syntax

display rmon statistics [ interface-type interface-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify an interface, the command displays RMON statistics for all interfaces.

Usage guidelines

This command displays the cumulative interface statistics for the period from the time the statistics entry was created to the time the command was executed. The statistics are cleared when the device reboots.

Examples

# Display RMON statistics for Ten-GigabitEthernet 1/1/1.

<Sysname> display rmon statistics ten-gigabitethernet 1/1/1

EtherStatsEntry 1 owned by user1 is VALID.

  Interface : Ten-GigabitEthernet1/1/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

  Incoming packets by size:

  64     : 0         ,  65-127  : 0         ,  128-255  : 0

  256-511: 0         ,  512-1023: 0         ,  1024-1518: 0

Table 6 Command output

Field	Description
EtherStatsEntry entry-number owned by owner is status.	Statistics entry owner and status: ·     entry-number—Statistics entry index (MIB object etherStatsIndex). ·     owner—Entry owner (MIB object etherStatsOwner). ·     status—Entry status (MIB object etherStatsStatus): ¡     VALID—The entry is valid. ¡     UNDERCREATION—The entry is invalid. The status field is not configurable at the CLI. All alarm entries created from the CLI are valid by default. The display rmon statistics command can display invalid entries, but the display current-configuration and display this commands do not display their settings.
Interface	Interface on which statistics are gathered (MIB object etherStatsDataSource).
etherStatsOctets	Total number of octets received on the interface (MIB object etherStatsOctets).
etherStatsPkts	Total number of packets received on the interface (MIB object etherStatsPkts).
etherStatsBroadcastPkts	Total number of broadcast packets received on the interface (MIB object etherStatsBroadcastPkts).
etherStatsMulticastPkts	Total number of multicast packets received on the interface (MIB object etherStatsMulticastPkts).
etherStatsUndersizePkts	Total number of undersize packets received on the interface (MIB object etherStatsUndersizePkts).
etherStatsOversizePkts	Total number of oversize packets received on the interface (MIB object etherStatsOversizePkts).
etherStatsFragments	Total number of undersize packets received with CRC errors on the interface (MIB object etherStatsFragments).
etherStatsJabbers	Total number of oversize packets received with CRC errors on the interface (MIB object etherStatsJabbers).
etherStatsCRCAlignErrors	Total number of packets received with CRC errors on the interface (MIB object etherStatsCRCAlignErrors).
etherStatsCollisions	Total number of colliding packets received on the interface (MIB object etherStatsCollisions).
etherStatsDropEvents	Total number of events in which packets were dropped (MIB object etherStatsDropEvents). NOTE: This statistic is the number of times that a drop condition occurred. It is not necessarily the total number of dropped packets.
Incoming packets by size:	Incoming-packet statistics by packet length: ·     64—Number of 64-byte packets. The value is stored in the MIB node etherStatsPkts64Octets. ·     65-127—Number of 65- to 127-byte packets. The value is stored in the MIB node etherStatsPkts65to127Octets. ·     128-255—Number of 128- to 255-byte packets. The value is stored in the MIB node etherStatsPkts128to255Octets. ·     256-511—Number of 256- to 511-byte packets. The value is stored in the MIB node etherStatsPkts256to511Octets. ·     512-1023—Number of 512- to 1023-byte packets. The value is stored in the MIB node etherStatsPkts512to1023Octets. ·     1024-1518—Number of 1024- to 1518-byte packets. The value is stored in the MIB node etherStatsPkts1024to1518Octets.

 

Related commands

rmon statistics

rmon alarm

Use rmon alarm to create an entry in the RMON alarm table.

Use undo rmon alarm to remove an entry from the RMON alarm table.

Syntax

rmon alarm entry-number alarm-variable sampling-interval { absolute | delta } [ startup-alarm { falling | rising | rising-falling } ] rising-threshold threshold-value1 event-entry1 falling-threshold threshold-value2 event-entry2 [ owner text ]

undo rmon alarm entry-number

Default

The RMON alarm table does not contain any entries.

Views

System view

Predefined user roles

network-admin

Parameters

entry-number: Specifies an alarm entry index in the range of 1 to 65535.

alarm-variable: Specifies an alarm variable, a string of 1 to 255 characters. You can only specify variables that can be parsed as an ASN.1 INTEGER value (INTEGER, INTEGER32, Unsigned32, Counter32, Counter64, Gauge, or TimeTicks) for the alarm-variable argument. The alarm variables must use one of the formats in Table 7.

Table 7 Alarm variable formats

Format	Examples
Dotted OID format: entry.integer.instance	1.3.6.1.2.1.2.1.10.1
Object name.instance	etherStatsOctets.1 etherStatsPkts.1 etherStatsBroadcastPkts.1 ifInOctets.1 ifInUcastPkts.1 ifInNUcastPkts.1

 

sampling-interval: Sets the sampling interval in the range of 5 to 65535 seconds.

absolute: Specifies absolute sampling. RMON compares the value of the variable with the rising and falling thresholds at the end of the sampling interval.

delta: Specifies delta sampling. RMON subtracts the value of the variable at the previous sample from the current value, and then compares the difference with the rising and falling thresholds.

startup-alarm: Specifies alarms that can be generated when the alarm entry becomes valid. If you do not specify an alarm, RMON can generate a rising alarm or a falling alarm depending on the first sample.

rising: Generates a rising alarm if the first sample after the entry becomes valid is greater than or equal to the rising threshold.

falling: Generates a falling alarm if the first sample after the entry becomes valid is less than or equal to the rising threshold.

rising-falling: Generates a rising alarm if the first sample crosses the rising threshold, or generates a falling alarm if the first sample crosses the falling threshold.

rising-threshold threshold-value1 event-entry1: Sets the rising threshold. The threshold-value1 argument represents the rising threshold in the range of –2147483648 to +2147483647. The event-entry1 argument represents the index of the event that is triggered when the rising threshold is crossed. The value range for the event-entry1 argument is 0 to 65535. If 0 is specified, the alarm does not trigger any event.

falling-threshold threshold-value2 event-entry2: Sets the falling threshold. The threshold-value2 argument represents the falling threshold in the range of –2147483648 to +2147483647. The event-entry2 argument represents the index of the event that is triggered when the falling threshold is crossed. The value range for the event-entry2 argument is 0 to 65535. If 0 is specified, the alarm does not trigger any event.

owner text: Specifies the entry owner, a case-sensitive string of 1 to 127 characters.

Usage guidelines

Before you create RMON alarm entries, you must enable the SNMP agent.

You can create a maximum of 60 entries in the RMON alarm table.

Each alarm entry must have a unique alarm variable, sampling interval, sample type, rising threshold, or falling threshold. You cannot create an alarm entry if all these parameters for the entry are the same as an existing entry.

To trigger the event associated with an alarm condition, you must create the event with the rmon event command.

RMON samples the monitored alarm variable at the specified sampling interval, compares the sampled value with the predefined thresholds, and does one of the following:

·     Triggers the event associated with the rising alarm if the sampled value is equal to or greater than the rising threshold.

·     Triggers the event associated with the falling alarm if the sampled value is equal to or less than the falling threshold.

Examples

# Create an alarm entry to perform absolute sampling on the number of octets received on Ten-GigabitEthernet 1/1/1 (object instance 1.3.6.1.2.1.16.1.1.1.4.1) at 10-seconds intervals. If the sampled value reaches or exceeds 5000, log the rising alarm event. If the sampled value is equal to or less than 5, take no actions.

<Sysname> system-view

[Sysname] rmon event 1 log

[Sysname] rmon event 2 none

[Sysname] interface ten-gigabitethernet 1/1/1

[Sysname-Ten-GigabitEthernet1/1/1] rmon statistics 1

[Sysname-Ten-GigabitEthernet1/1/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

In this example, you can replace 1.3.6.1.2.1.16.1.1.1.4.1 with etherStatsOctets.1, where 1 is the statistics entry index for the interface. If you execute the rmon statistics 5 command, you can use etherStatsOctets.5 to replace 1.3.6.1.2.1.16.1.1.1.4.5.

Related commands

·     display rmon alarm

·     rmon event

rmon event

Use rmon event to create an entry in the RMON event table.

Use undo rmon event to remove an entry from the RMON event table.

Syntax

rmon event entry-number [ description string ] { log | log-trap security-string | none | trap security-string } [ owner text ]

undo rmon event entry-number

Default

No entry exists in the RMON event table.

Views

System view

Predefined user roles

network-admin

Parameters

entry-number: Specifies an event entry index in the range of 1 to 65535.

description string: Configures an event description, a case-sensitive string of 1 to 127 characters.

log: Logs the event when it occurs.

log-trap: Logs the event and sends an SNMP notification when the event occurs.

security-string: Represents the SNMP community name, a case-sensitive string of 1 to 127 characters.

none: Performs no action when the event occurs.

trap: Sends an SNMP notification when the event occurs.

owner text: Specifies the entry owner, a case-sensitive string of 1 to 127 characters.

 

NOTE: The SNMP community name setting for the security-string argument does not take effect even though you can configure it with the command. Instead, the system uses the settings you configure with SNMP when it sends RMON SNMP notifications. For more information about SNMP notifications, see Network Management and Monitoring Configuration Guide.

 

Usage guidelines

You can create a maximum of 60 event entries.

You can associate an event entry with a standard or private alarm entry to specify the action to take when an alarm condition occurs. Depending on your configuration, the system logs the event, sends an SNMP notification, does both, or does neither.

You can associate an event with multiple alarm entries.

Examples

# Create event 10 in the RMON event table.

<Sysname> system-view

[Sysname] rmon event 10 log owner user1

Related commands

·     display rmon event

·     rmon alarm

·     rmon prialarm

rmon history

Use rmon history to create an entry in the RMON history control table.

Use undo rmon history to remove an entry from the RMON history control table.

Syntax

rmon history entry-number buckets number interval sampling-interval [ owner text ]

undo rmon history entry-number

Default

The RMON history control table does not contain any entries.

Views

Ethernet interface view

Predefined user roles

network-admin

Parameters

entry-number: Specifies a history control entry index in the range of 1 to 65535.

buckets number: Specifies the expected maximum number of samples to be retained for the entry, in the range of 1 to 65535. RMON can retain a maximum of 50 samples for each history control entry. If the expected bucket size exceeds the available history table size, RMON sets the bucket size as closely to the expected bucket size as is possible. However, the granted bucket size will not exceed 50. For example, the bucket size for a history control entry will be 30 if the expected bucket size is set to 55, but the available bucket size is only 30.

interval sampling-interval: Specifies the sampling interval in the range of 5 to 3600 seconds.

owner text: Specifies the entry owner, a case-sensitive string of 1 to 127 characters.

Usage guidelines

You can create RMON history control entries only for Layer 2 or Layer 3 Ethernet interfaces.

The system supports a maximum of 100 history control entries.

If an Ethernet interface has a history control entry, RMON periodically samples packet statistics on the interface and stores the samples to the history table. When the bucket size for the history control entry is reached, RMON overwrites the oldest sample with the most recent sample.

You can configure multiple history control entries for one interface. Make sure their entry numbers and sampling intervals are different.

Examples

# Create RMON history control entry 1 for Ten-GigabitEthernet 1/1/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/1/1

[Sysname-Ten-GigabitEthernet1/1/1] rmon history 1 buckets 10 interval 5 owner user1

Related commands

display rmon history

rmon prialarm

Use rmon prialarm to create an entry in the private alarm table.

Use undo rmon prialarm to remove an entry from the private alarm table.

Syntax

rmon prialarm entry-number prialarm-formula prialarm-des sampling-interval { absolute | delta } [ startup-alarm { falling | rising | rising-falling } ] rising-threshold threshold-value1 event-entry1 falling-threshold threshold-value2 event-entry2 entrytype { forever | cycle cycle-period } [ owner text ]

undo rmon prialarm entry-number

Default

The private alarm table does not contain any entries.

Views

System view

Predefined user roles

network-admin

Parameters

entry-number: Specifies a private alarm entry index in the range of 1 to 65535.

prialarm-formula: Configures a private alarm variable formula, a string of 1 to 255 characters. The variables in the formula must be represented in OID format that starts with a dot (.), for example, (.1.3.6.1.2.1.2.1.10.1)*8. You can configure a formula to perform the basic math operations of addition, subtraction, multiplication, and division on these variables. To get a correct calculation result, make sure the following conditions are met:

·     The values of the variables in the formula are positive integers.

·     The result of each calculating step is in the value range for long integers.

prialarm-des: Configures an entry description, a case-sensitive string of 1 to 127 characters.

sampling-interval: Sets the sampling interval in the range of 10 to 65535 seconds.

absolute: Specifies absolute sampling. RMON compares the value of the variable with the rising and falling thresholds at the end of the sampling interval.

delta: Specifies delta sampling. RMON subtracts the value of the variable at the previous sample from the current value, and then compares the difference with the rising and falling thresholds.

startup-alarm: Specifies alarms that can be generated when the alarm entry becomes valid. If you do not specify an alarm, RMON does the following:

·     Generates a rising alarm if the first sample crosses the rising threshold.

·     Generates a falling alarm if the first sample crosses the falling threshold.

rising: Generates a rising alarm if the first sample after the entry becomes valid is greater than or equal to the rising threshold.

falling: Generates a falling alarm if the first sample after the entry becomes valid is less than or equal to the rising threshold.

rising-falling: Generates a rising alarm or falling alarm if the first sample after the entry becomes valid crosses the rising threshold or falling threshold.

rising-threshold threshold-value1 event-entry1: Sets the rising threshold. The threshold-value1 argument represents the rising threshold in the range of –2147483648 to +2147483647. The event-entry1 argument represents the index of the event that is triggered when the rising threshold is crossed. The value range for the event-entry1 argument is 0 to 65535. If 0 is specified, the alarm does not trigger any event.

falling-threshold threshold-value2 event-entry2: Sets the falling threshold. The threshold-value2 argument represents the falling threshold in the range of –2147483648 to +2147483647. The event-entry2 argument represents the index of the event that is triggered when the falling threshold is crossed. The value range for the event-entry2 argument is 0 to 65535. If 0 is specified, the alarm does not trigger any event.

forever: Configures the entry as a permanent entry. RMON retains a permanent private alarm entry until it is manually deleted.

cycle cycle-period: Sets the lifetime of the entry, in the range of 0 to 4294967 seconds. RMON deletes the entry when its lifetime expires.

owner text: Specifies the entry owner, a case-sensitive string of 1 to 127 characters.

Usage guidelines

Before you can create RMON private alarm entries, you must enable the SNMP agent.

You can create a maximum of 50 private alarm entries.

Each alarm entry must have a unique alarm variable, sampling interval, sample type, rising threshold, or falling threshold. You cannot create an alarm entry if all these parameters for the entry are the same as an existing entry.

To trigger the event associated with an alarm condition, you must create the event with the rmon event command.

The RMON agent samples variables and takes an alarm action based on a private alarm entry as follows:

1.     Periodically samples the variables specified in the private alarm formula.

2.     Processes the sampled values with the formula.

3.     Compares the calculation result with the predefined thresholds, and then takes one of the following actions:

¡     Triggers the event associated with the rising alarm event if the result is equal to or greater than the rising threshold.

¡     Triggers the event associated with the falling alarm event if the result is equal to or less than the falling threshold.

Examples

# Add a permanent private alarm entry to monitor the ratio of incoming broadcasts to the total number of incoming packets on Ten-GigabitEthernet 1/1/1. Log the rising alarm event when the ratio exceeds 80%, and take no actions when the ratio drops to 5%. The formula is (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), where 1.3.6.1.2.1.16.1.1.1.6.1 is the OID of the object instance etherStatsBroadcastPkts.1, and 1.3.6.1.2.1.16.1.1.1.5.1 is the OID of the object instance etherStatsPkts.1.

<Sysname> system-view

[Sysname] rmon event 1 log

[Sysname] rmon event 2 none

[Sysname] interface ten-gigabitethernet 1/1/1

[Sysname-Ten-GigabitEthernet1/1/1] rmon statistics 1

[Sysname-Ten-GigabitEthernet1/1/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) BroadcastPktsRatioOfXGE1/1/1 10 absolute rising-threshold 80 1 falling-threshold 5 2 entrytype forever owner user1

The last number in the OID forms of variables must be the same as the statistics entry index for the interface. For example, if you execute the rmon statistics 5 command, you must replace 1.3.6.1.2.1.16.1.1.1.6.1 and 1.3.6.1.2.1.16.1.1.1.5.1 with 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, respectively.

Related commands

·     display rmon prialarm

·     rmon event

rmon statistics

Use rmon statistics to create an entry in the RMON statistics table.

Use undo rmon statistics to remove an entry from the RMON statistics table.

Syntax

rmon statistics entry-number [ owner text ]

undo rmon statistics entry-number

Default

No entry exists in the RMON statistics table.

Views

Ethernet interface view

Predefined user roles

network-admin

Parameters

entry-number: Specifies a statistics entry index in the range of 1 to 65535.

owner text: Specifies the entry owner, a case-sensitive string of 1 to 127 characters.

Usage guidelines

You can create RMON statistics entries only for Layer 2 or Layer 3 Ethernet interfaces.

You can create one statistics entry for each Ethernet interface, and a maximum of 100 statistics entries on the device.

Each RMON statistics table entry provides a set of cumulative traffic statistics collected up to the present time for an 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, and number of packets received. The statistics are cleared at a reboot.

To display the RMON statistics table, use the display rmon statistics command.

Examples

# Create an RMON statistics entry for Ten-GigabitEthernet 1/1/1. The index is 20 and the owner is user1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 1/1/1

[Sysname-Ten-GigabitEthernet1/1/1] rmon statistics 20 owner user1

Related commands

display rmon statistics