Help Center/ Huawei Qiankun CloudService/ More Documents/ Device Alarm Handling/ V600 Device Alarms/ AR Alarms/ ALM-15795258 hwSPRInstanceReport
Updated on 2024-01-25 GMT+08:00
View PDF
Share

ALM-15795258 hwSPRInstanceReport

Description

The path of SPR instance changed. (DestSiteIndex = [DestSiteIndex], VpnInstance = [VpnInstance], PolicyName = [PolicyName], PreviousLink = [PreviousLink], PreviousLinkLoss = [PreviousLinkLoss], PreviousLinkDelay = [PreviousLinkDelay], PreviousLinkJitter = [PreviousLinkJitter], PreviousLinkCMI = [PreviousLinkCMI], CurrentLink = [CurrentLink], ChangedReason = [ChangedReason])

The path of the SPR instance changed.

Attribute

Alarm ID

OID

Alarm Severity

Alarm Type

15795258

1.3.6.1.4.1.2011.5.25.241.2.4.2

Minor

Quality of service alarm

Parameters

Name Meaning

DestSiteIndex

Name of the destination site.

VpnInstance

VPN instance name.

PolicyName

SPR policy name.

PreviousLink

Name of the link selected by the SPR instance before the link switchover.

PreviousLinkLoss

Packet loss rate of the link selected by the SPR instance before the link switchover.

PreviousLinkDelay

Delay of the link selected by the SPR instance before the link switchover.

PreviousLinkJitter

Jitter of the link selected by the SPR instance before the link switchover.

PreviousLinkCMI

Comprehensive metric value of the link selected by the SPR instance before the link switchover.

CurrentLink

Name of the link selected by the SPR instance after the link switchover.

ChangedReason

Cause of the link switchover

Impact on the System

  • This is a normal phenomenon and has no impact on the system.
  • This is a normal phenomenon and has no impact on the system.
  • This is a normal phenomenon and has no impact on the system.
  • This is a normal phenomenon and has no impact on the system.
  • This is a normal process and has no impact on the system.
  • This is a normal process and has no impact on the system.
  • This is a normal process and has no impact on the system.
  • This is a normal process and has no impact on the system.

Possible Causes

  • Cause 1: The link delay exceeded the threshold configured in the policy.
  • Cause 2: The link loss exceeded the threshold configured in the policy.
  • Cause 3: The link jitter exceeded the threshold configured in the policy.
  • Cause 4: The link cmi exceeded the threshold configured in the policy.
  • Cause 5: The link status changed.
  • Cause 6: The selected link was unavailable.
  • Cause 7: Traffic was switched back from a low-priority link to a high-priority link.
  • Cause 8: SPR chose the best link from poor quality.

Procedure

  • Cause 1: The link delay exceeded the threshold configured in the policy.
    1. Run the display spr-policy command to check whether the delay threshold in the SPR policy is correct.
      • If the configuration is incorrect, run the set delay threshold command to set a proper delay threshold, and then go to Step 4.
      • If the configuration is correct, go to Step 2.
    2. Checkthe status of the transport network.
      • If the network has a long delay, the link switchover is normal. Go to step 4.
      • If the fault is not caused by the network, go to Step 3.
    3. Collect alarm, log, and configuration information, and contact technical support personnel.
    4. End.
  • Cause 2: The link loss exceeded the threshold configured in the policy.
    1. Run the display spr-policy command to check whether the packet loss rate threshold in the SPR policy is correct.
      • If the configuration is incorrect, run the set loss threshold command to set a proper threshold for the policy, and then go to Step 4.
      • If the configuration is correct, go to Step 2.
    2. Checkthe status of the transport network.
      • If packet loss occurs on the network, the link switchover is normal. Go to step 4.
      • If the fault is not caused by the network, go to Step 3.
    3. Collect alarm, log, and configuration information, and contact technical support personnel.
    4. End.
  • Cause 3: The link jitter exceeded the threshold configured in the policy.
    1. Run the display spr-policy command to check whether the jitter threshold of the SPR policy is correct.
      • If not, run the set jitter threshold command to set a proper jitter threshold, and then go to step 4.
      • If the configuration is correct, go to Step 2.
    2. Checkthe status of the transport network.
      • If packet loss occurs on the network, the link switchover is normal. Go to step 4.
      • If the fault is not caused by the network, go to Step 3.
    3. Collect alarm, log, and configuration information, and contact technical support personnel.
    4. End.
  • Cause 4: The link cmi exceeded the threshold configured in the policy.
    1. Runthe display spr-policy command to check whether the jitter threshold of the SPR policy is correct.
      • If not, run the set jitter threshold command to set a proper jitter threshold, and then go to step 4.
      • If the configuration is correct, go to Step 2.
    2. Check the status of the transport network.
      • If the network quality is poor when the switchover occurs, the link switchover is normal. In this case, go to step 4.
      • If the fault is not caused by the network, go to Step 3.
    3. Collect alarm, log, and configuration information, and contact technical support personnel.
    4. End.
  • This alarm message is informational only, and no action is required.
  • This alarm message is informational only, and no action is required.
  • This alarm message is informational only, and no action is required.
  • This alarm message is informational only, and no action is required.

Clearing

The alarm needs to be cleared manually.

Parent topic: AR Alarms