No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.

Configuration Guide - Network Management and Monitoring
S1720, S2700, S5700, and S6720 V200R011C10

This document provides the configurations of network management and monitoring features supported by the product, including SNMP, RMON and RMON2, LLDP, Performance Management, iPCA, NQA, Service Diagnosis, Mirroring, Packet Capture, NetStream, sFlow, TWAMP Light, and NETCONF.

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring RMON Alarm

Configuring RMON Alarm


The RMON alarm involves event definition and alarm threshold setting.

Set the alarm threshold to monitor key indexes during system running. When an error occurs in the system, the related event is triggered. The event definition function determines whether to log the event or send a trap to the NMS.

If the variables configured in the RMON alarm are MIB variables defined in the statistics or history group, the Ethernet or history statistics collection must be configured on the monitored Ethernet interface first.


  1. Run system-view

    The system view is displayed.

  2. Run rmon event entry-number [ description string ] { log | trap object | log-trap object | none } [ owner owner-name ]

    The event definition function is configured and an entry is added to an event table.

  3. Configure the alarm threshold function.
    1. Run rmon alarm entry-number alarm-OID sampling-time { absolute | changeratio | delta } rising-threshold threshold-value1 event-entry1 falling-threshold threshold-value2 event-entry2 [ startup-alarm { falling | rising | risingorfalling } ] [ owner owner-name ]

      An alarm table is configured and an entry is added to the table.

    2. Run rmon prialarm entry-number prialarm-formula description-string sampling-interval { absolute | changeratio | delta } rising-threshold threshold-value1 event-entry1 falling-threshold threshold-value2 event-entry2 entrytype { cycle entry-period | forever } [ owner owner-name ]

      An extended alarm table is configured and an entry is added to the table.

      If the events (event-entry1, event-entry2) corresponding to the alarm rising and falling thresholds are not configured in the event table, no alarm will be generated even if the alarm conditions are met. In this situation, the alarm record status is undercreation, but not valid.

      After either event is configured, the alarm is generated if the alarm conditions are met and the alarm status is valid. If an incorrect alarm variable is created, such as a nonexistent OID being specified, the alarm is in the undercreation state and no alarm is generated.

  4. (Optional) Run snmp-agent trap enable feature-name rmon [ trap-name { fallingalarm | risingalarm | rmon_pri_fallingalarm | rmon_pri_risingalarm } ]

    The alarm is enabled for the RMON module.

    By default, all alarms for the RMON module are enabled.

Updated: 2020-02-06

Document ID: EDOC1000178174

Views: 226358

Downloads: 859

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next