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.


Alarm Handling

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

This document provides the trap description, attributes, parameters, impact on the system, possible causes, procedures, and references. This document provides a complete set of traps, through which intended readers are kept of the running status of the device so as to locate faults.

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).
RMON_1. pririsingAlarm

RMON_1. pririsingAlarm


RMON/3/RISING:OID [OID] Private alarm table [alarm-line-index] monitors [description] with the sample type being [sample-type], and the sampled alarm value [alarm-value] is greater than or equal to [alarm-upper-limit].

The value of the alarm entity was higher than prialarmRisingThreshold.


Alarm ID Alarm Severity Alarm Type Minor communicationsAlarm(2)


Name Meaning


Indicates the MIB object ID of the alarm.


Indicates the index of the alarm entry.


Indicates the description of the alarm entry


Indicates the type of the sampled alarm.


Indicates the alarm value.


Indicates the upper threshold of the alarm.

Impact on the System


Possible Causes

Cause 1:

If the current sampled value was greater than or equal to this threshold, and the last sampled value was less than this threshold, the alarm was generated.

Cause 2:

When this alarm entry became valid, the first sampled value was greater than or equal to this threshold, and prialarmStartupAlarm was equal to risingAlarm and risingOrFallingAlarm, the alarm was generated.


  • This alarm is triggered only when the upper alarm monitoring threshold configured using the rmon prialarm command is reached. It is a user-configured monitoring alarm and does not affect services. Therefore, no action is required.

Related Information


Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 102704

Downloads: 61

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next