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).
SPR_1. hwSPRServiceReport

SPR_1. hwSPRServiceReport


SPR/4/SERVICEMAP_LINKCHANGE:OID [oid] SPR Service-map Link changed. ServiceIndex = [integer], ServiceName = [octet], ServiceCurLinkName = [octet], System Name = [string], Original Ip address = [string].

The current link of the SPR service profile changed.


Alarm ID Alarm Severity Alarm Type Warning qualityOfServiceAlarm(3)


Name Meaning

Indicates the MIB object ID of the alarm.

ServiceIndex Indicates an entry index. The value ranges from 1 to 65535.
ServiceName Indicates the name of a service profile.
ServiceCurLinkName Indicates the current link name of the service profile.
System Name Indicates the system name.
Original Ip address Indicates the link IP address used before link switching.

Impact on the System

  • If the SPR service profile has just been configured, it is normal that this alarm is sent. This will not affect the system.
  • If the alarm of a service profile is sent occasionally, normal link switching may have occurred. This will not affect the system.
  • If the alarm of a service profile is sent frequently, the link to which the service profile is bound may flap.

Possible Causes

  1. Traffic is switched between links properly.
  2. The service profile configuration is incorrect.
  3. The service threshold configuration is incorrect.
  4. The link to which the service profile is bound is faulty.


  1. Run the display smart-policy-route link-state command to view the link status.

    • Check whether the packet loss ratio is 1000. If so, the link is faulty. Go to step 3.
    • Check whether the delay, jitter, loss ratio, and Composite Measure Indicator (CMI) are correct. If so, go to step 2.

  2. Run the display smart-policy-route service-map name command to view thresholds for link quality parameters.

    • Check whether the link meets service requirements based on the link status. If the link does not meet service requirements, services may be switched between links. Go to step 4.
    • Check whether the thresholds for link quality parameters are correct. If not, set correct thresholds for link quality parameters and then go to step 4.
      • Run the set delay threshold threshold-value command to set the service delay threshold.
      • Run the set jitter threshold threshold-value command to set the service jitter threshold.
      • Run the set loss threshold threshold-value command to set the packet loss ratio threshold.
      • Run the set cmi threshold threshold-value command to set the CMI threshold.
      • Run the cmi-method cmi-method command to set the CMI calculation formula.

  3. Collect alarm information, log information, and configuration, and contact technical support personnel.
  4. End.

Related Information


Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 102153

Downloads: 61

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next