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

Reminder

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

upgrade

Alarm Handling

AR100-S, AR110-S, AR120-S, AR150-S, AR160-S, AR200-S, AR1200-S, AR2200-S, and AR3200-S V200R009

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).
NQA_1.3.6.1.4.1.2011.5.25.111.6.10 nqaJitterStatsTestFailed

NQA_1.3.6.1.4.1.2011.5.25.111.6.10 nqaJitterStatsTestFailed

Description

NQA/4/JITTERTESTFAIL:OID [oid] NQA entry test failed. (OwnerIndex=[OCTET], TestName=[OCTET])

Indicates that the number of testing failures in a test instance reached the set threshold. The value of the default threshold was 1. The test-failtimes command could modify the threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.111.6.10 Warning environmentalAlarm(6)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

OwnerIndex

Indicates the administrator of an NQA test.

TestName

Indicates the name of an NQA test instance.

Impact on the System

None.

Possible Causes

This trap occurs in the NQA test.

1.

The destination address was inexistent and unreachable. The number of continuous test failures in a test reached the set threshold.

2.

The destination address existed, but the route was unreachable. The number of continuous test failures in a test reached the set threshold.

3.

The destination port was not correctly configured, which led to the connection failure.

NOTE:

The Jitter Version 1 did not check the destination port. Whether the server was configured or not, the test succeeded.

Procedure

  1. Run the display this command in the NQA test view to check whether the destination address is correctly configured. If not, run the destination-address command in the NQA test view to modify the destination address.

    Perform the test again to check whether the alarm is cleared.
    • If so, go to Step 8.
    • If not, go to Step 2.

  2. Run the ping command in the NQA test view to check whether the route is reachable.

    • If the destination address is correctly configured, but the route is not reachable, run the display ip routing-table command to check and routing table and rectify the routing fault. If the test fails again, go to Step 7.
    • If the route is reachable, go to Step 3.

  3. Run the display this command in the NQA test view to check whether the destination port is correctly configured. If not, run the destination-port command in the NQA test view to modify the related parameters.

    Perform the test again to check whether the alarm is cleared.
    • If so, go to Step 8.
    • If not, go to Step 4.

  4. Run the display this command in the system view to check the Jitter's version.

    • If the Jitter's version is 1, go to Step 7.
    • If the Jitter's version is 2, go to Step 5.

  5. Run the display nqa-server command in the System view to check whether the server port is correctly configured.

    • If so, go to Step 7.
    • If not, go to Step 6.

  6. Run the nqa-server udpecho in the system view to modify the server. Restart the test instance.

    Perform the test again to check whether the alarm is cleared.
    • If so, go to Step 8.
    • If not, go to Step 7.

  7. Collect alarm information and configuration information, and then contact technical support personnel.
  8. End.

Related Information

None

Translation
Download
Updated: 2019-05-06

Document ID: EDOC1000174085

Views: 131973

Downloads: 20

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next