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

S9300, S9300E, and S9300X V200R013C00

This document provides the explanations, causes, and recommended actions of alarms on the product.
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

NQA

NQA_1.3.6.1.2.1.80.0.1 pingProbeFailed

Description

NQA/4/DISMANPINGPROBEFAIL:OID [oid] Ping entry probe failed. (Admin=[OCTET], Tag=[OCTET])

The trap was generated when the number of continuous probe failures in a test reached the set threshold. The default threshold was 1. You can run the probe-failtimescommand to modify the threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.80.0.1

Warning

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

Admin

Indicates the index of the test administrator.

Tag

Indicates the index of a test name.

Impact on the System

None.

Possible Causes

This trap occurred in the NQA test.

1.

The destination address was inexistent and the route was unreachable.

2.

The destination address existed, but the route was unreachable.

3.

Because of the network delay, the Round Trip Time (RTT) of the packet was longer than the set timeout period.

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 5.
    • 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 the routing table and rectify the routing fault. If the test fails again, go to Step 4.
    • If the route is reachable, go to Step 3.

  3. Run the timeout command in the NQA test view to modify the timeout period according to the status of the current network. It is recommended that you modify the timeout period to the default value, that is, three seconds. The value of the timeout period ranges from 1 second to 60 seconds. You can run the display this command in the NQA test view to view the current timeout period.

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

  4. Collect alarm information and configuration information, and then contact technical support personnel.
  5. End.

Related Information

None

NQA_1.3.6.1.2.1.80.0.2 pingTestFailed

Description

NQA/4/PINGFAIL:OID [oid] Ping entry test failed. (Admin=[OCTET], Tag=[OCTET])

The trap was generated when the number of continuous test failures reached the threshold. The default threshold was 1. You can run the test-failtimes command to modify the threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.2.1.80.0.2 Warning communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

Admin

Indicates the index of the test administrator.

Tag

Indicates the index of the test name.

Impact on the System

None.

Possible Causes

This trap occurred in the NQA test.

1.

The destination address was inexistent and the route was unreachable.

2.

The destination address existed, but the route was unreachable.

3.

Because of the network delay, the RTT of the packet was longer than the set timeout period.

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 5.
    • 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 the routing table and rectify the routing fault. If the test fails again, go to Step 4.
    • If the route is reachable, go to Step 3.

  3. Run the timeout command in the NQA test view to modify the timeout period according to the status of the current network. It is recommended that you modify the timeout period to the default value, that is, three seconds. The value of the timeout period ranges from 1 second to 60 seconds. You can run the display this command in the NQA test view to view the current timeout period.

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

  4. Collect alarm information and configuration information, and then contact technical support personnel.
  5. End.

Related Information

None

NQA_1.3.6.1.2.1.80.0.3 pingTestCompleted

Description

NQA/4/PINGCOMPLETE:OID [oid] Ping entry test completed. (Admin=[OCTET], Tag=[OCTET])

A test succeeded.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.2.1.80.0.3 Warning communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

Admin

Indicates the index of the test administrator.

Tag

Indicates the index of the test name.

Impact on the System

None.

Possible Causes

This trap occurred in the NQA test.

The ping test succeeded.

Procedure

  1. This trap message is informational only, and no action is required.

Related Information

None

NQA_1.3.6.1.2.1.81.0.2 traceRouteTestFailed

Description

NQA/4/TRACEROUTETESTFAIL:OID [oid] TraceRoute entry test failed. (Admin=[OCTET], Tag=[OCTET])

The trap was generated when the trace test failed.

Attribute

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

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

Admin

Indicates the index of the test administrator.

Tag

Indicates the index of the test name.

Impact on the System

None.

Possible Causes

This trap occurred in the NQA test.

1.

The destination address was inexistent and the route was unreachable.

2.

The destination address existed, but the route was unreachable.

3.

The destination address existed and the route was reachable, but the number of hops between the start and the destination exceeded the set number of the maximum hops.

4.

Because of the network delay, the RTT of the trace packet was longer than the set timeout period.

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 6.
    • 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 the routing table and rectify the routing fault. If the test fails again, go to Step 5.
    • If the route is reachable, go to Step 3.

  3. Run the tracert-livetime command in the NQA test view to change the Time to Live (TTL) of packets according to the actual packet forwarding status. (Run the display this command in the NQA test view to view the current TTL value.) The TTL value ranges from 1 to 255. It is recommended that the maximum number be 255.

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

  4. Run the timeout command in the NQA test view to modify the timeout period according to the status of the current network. It is recommended that you modify the timeout period to the default value, that is, three seconds. The value of the timeout period ranges from 1 second to 60 seconds. You can run the display this command in the NQA test view to view the current timeout period.

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

  5. Collect alarm information and configuration information, and then contact technical support personnel.
  6. End.

Related Information

None

NQA_1.3.6.1.2.1.81.0.3 traceRouteTestCompleted

Description

NQA/4/TRACEROUTECOMPLETE:OID [oid] TraceRoute entry test completed. (Admin=[OCTET], Tag=[OCTET])

A trap was generated when the trace test succeeded.

Attribute

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

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

Admin

Indicates the index of the test administrator.

Tag

Indicates the index of the test name.

Impact on the System

None.

Possible Causes

The NQA traceroute test succeeded.

Procedure

  1. This trap message is informational only, and no action is required.

Related Information

None

NQA_1.3.6.1.4.1.2011.5.25.111.6.1 nqaResultsProbeFailed

Description

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

Indicates that the number of continuous probe failures in a test reaches the set threshold. The value of the default threshold was 1. The probe-failtimes command could modify the threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.111.6.1 Warning processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

OwnerIndex

Indicates the administrator of an NQA test instance.

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.

2.

The destination address exists, but the route was unreachable.

3.

Because of the network latency, the RTT of the packet was longer than the set timeout period.

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 5.
    • 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 4.
    • If the route is reachable, go to Step 3.

  3. Run the timeout command in the NQA test view to modify the timeout period according to the status of the current network. It is recommended that you modify the timeout period to the default value, that is, three seconds. The value of the timeout period ranges from 1 second to 60 seconds. You can run the display this command in the NQA test view to see the current timeout period.

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

  4. Collect alarm information and configuration information, and then contact technical support personnel.
  5. End.

Related Information

None

NQA_1.3.6.1.4.1.2011.5.25.111.6.2 nqaResultsTestFailed

Description

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

Indicates that the number of continuous testing failures in a test instance reached the set threshold. The value of the default threshold was 1, that is, a trap was generated right after each test failure. The test-failtimes command can modify the threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.111.6.2 Warning processingErrorAlarm(5)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

OwnerIndex

Indicates the administrator of an NQA test instance.

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.

2.

The destination address existed, but the route was unreachable.

3.

Because of the network latency, the RTT of the Trace packet was longer than the set timeout period.

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 5.
    • 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 4.
    • If the route is reachable, go to Step 3.

  3. Run the timeout command in the NQA test view to modify the timeout period according to the status of the current network. It is recommended that you modify the timeout period to the default value, that is, three seconds. The value of the timeout period ranges from 1 second to 60 seconds. You can run the display this command in the NQA test view to see the current timeout period.

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

  4. Collect alarm information and configuration information, and then contact technical support personnel.
  5. End.

Related Information

None

NQA_1.3.6.1.4.1.2011.5.25.111.6.3 nqaResultsTestCompleted

Description

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

Indicates that a test succeeded.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.111.6.3 Warning processingErrorAlarm(6)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

OwnerIndex

Indicates the administrator of an NQA test instance.

TestName

Indicates the name of an NQA test instance.

Impact on the System

None.

Possible Causes

This trap occurred in the NQA test.

The test succeeded.

Procedure

  1. This trap message is informational only, and no action is required.

Related Information

None

NQA_1.3.6.1.4.1.2011.5.25.111.6.4 nqaResultsThresholdNotification

Description

NQA/4/THRESHOLD:OID [oid] NQA entry over threshold. (OwnerIndex=[OCTET], TestName=[OCTET])

Indicates that the period of a test exceeded the set threshold. The threshold could be set by the user. The threshold rtd could modify the threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.111.6.4 Warning processingErrorAlarm(6)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

OwnerIndex

Indicates the administrator of an NQA test instance.

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 threshold was set too small.

2.

The network was busy.

Procedure

  1. Run the display cpu-usage command in the system view to check whether the CPU has an excessive usage.

    • If so, go to Step 3.
    • If not, go to Step 2.

  2. In the NQA test view, run the display this command to know the current threshold. Then run the threshold rtd command to modify the threshold as required. The recommended value is 20 ms.

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

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

Related Information

None

NQA_1.3.6.1.4.1.2011.5.25.111.6.5 nqaHTTPStatsProbeFailed

Description

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

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

Attribute

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

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

OwnerIndex

Indicates the administrator of an NQA test instance.

TestName

Indicates the name of an NQA test instance.

Impact on the System

None.

Possible Causes

This alarm occurs in the NQA test.

1.

The destination address is inexistent and unreachable, causing the number of consecutive probe failures reaches the threshold.

2.

The destination address exists but is unroutable, causing the number of consecutive probe failures reaches the threshold.

3.

The destination address is an incorrect URL address, causing the connection establishment to be failed.

4.

The destination address is a URL address but the DNS server is incorrectly configured, causing the DNS resolution to be failed.

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 6.
    • 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 5.
    • If the destination address is a URL address and the route is reachable, go to Step 3.

  3. Run the display this command in the NQA test view to check whether the http-url is correctly configured. If not, run the http-url 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 6.
    • If not, go to Step 4.

  4. Run the display this command in the NQA test view to check whether the DNS server is correctly configured. If not, run the dns-server 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 6.
    • If not, go to Step 5.

  5. Collect alarm information and configuration information, and then contact technical support personnel.
  6. End.

Related Information

None

NQA_1.3.6.1.4.1.2011.5.25.111.6.6 nqaHTTPStatsTestFailed

Description

NQA/4/HTTPTESTFAIL: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.6 Warning environmentalAlarm(7)

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 alarm occurs in the NQA test.

1.

The destination address is inexistent and unreachable, causing the number of consecutive probe failures reaches the threshold.

2.

The destination address exists but is unroutable, causing the number of consecutive probe failures reaches the threshold.

3.

The destination address is an incorrect URL address, causing the connection establishment to be failed.

4.

The destination address is a URL address but the DNS server is incorrectly configured, causing the DNS resolution to be failed.

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 6.
    • 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 5.
    • If the destination address is a URL address and the route is reachable, go to Step 3.

  3. Run the display this command in the NQA test view to check whether the http-url is correctly configured. If not, run the http-url 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 6.
    • If not, go to Step 4.

  4. Run the display this command in the NQA test view to check whether the DNS server is correctly configured. If not, run the dns-server 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 6.
    • If not, go to Step 5.

  5. Collect alarm information and configuration information, and then contact technical support personnel.
  6. End.

Related Information

None

NQA_1.3.6.1.4.1.2011.5.25.111.6.7 nqaHTTPStatsTestCompleted

Description

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

Indicates that a test succeeded.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.111.6.7 Warning environmentalAlarm(8)

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 occurred in the NQA test.

The test succeeded.

Procedure

  1. This trap message is informational only, and no action is required.

Related Information

None

NQA_1.3.6.1.4.1.2011.5.25.111.6.8 nqaHTTPStatsThresholdNotification

Description

NQA/4/HTTPTHRESHOLD:OID [oid] NQA entry over threshold. (OwnerIndex=[OCTET], TestName=[OCTET])

Indicates that the period of a test exceeded the set threshold. The threshold could be set by the user. The threshold rtd command could modify the threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.111.6.8 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 occurred in the NQA test.

1.

The threshold was set too small.

2.

The network was busy.

Procedure

  1. Run the display cpu-usage command in the system view to check whether the CPU has an excessive load.

    • If so, go to Step 3.
    • If not, go to Step 2.

  2. In the NQA test view, run the display this command to know the current threshold. Then run the threshold rtd command to modify the threshold as required. The recommended value is 20 ms.

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

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

Related Information

None

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

NQA_1.3.6.1.4.1.2011.5.25.111.6.11 nqaJitterStatsTestCompleted

Description

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

Indicates that a test succeeded.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.111.6.11 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 occurred in the NQA test.

The test succeeded.

Procedure

  1. This trap message is informational only, and no action is required.

Related Information

None

NQA_1.3.6.1.4.1.2011.5.25.111.6.12 nqaFTPStatsProbeFailed

Description

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

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

Attribute

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

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

OwnerIndex

Indicates the administrator of an NQA test instance.

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, and thus the number of continuous probe failures in a test reached the set threshold.

2.

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

3.

The source address was incorrect, and thus the number of continuous probe failures in a test reached the set threshold.

4.

The user name or password was incorrect; the file name was inexistent.

5.

The FTP service was not enabled.

6.

The file was oversized, and could not be transmitted within a specified period.

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 10.
    • 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 3.
    • If the route is reachable, go to Step 3.

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

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

  4. Run the display this command in the NQA test view to check whether the FTP user name is correctly configured. If not, run the ftp-username 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 10.
    • If not, go to Step 5.

  5. Run the display this command in the NQA test view to check whether the FTP password is correctly configured. If not, run the ftp-password 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 6.

  6. Run the display this command in the NQA test view to check whether the FTP file name is correctly configured. If not, run the ftp-filename 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 10.
    • If not, go to Step 7.

  7. Run the display ftp-server command on the FTP server to check whether the FTP service is enabled. If not, run the ftp server enable command in the system to enable the FTP service.

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

  8. The file is oversized, and cannot be transmitted within a specified period. Run the timeout command in the NQA test view to modify the timeout period. The value ranges from 1 to 60. You can run the display this command in the NQA test view to view the current timeout period. Restart the test instance.

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

  9. Collect alarm information and configuration information, and then contact technical support personnel.
  10. End.

Related Information

None

NQA_1.3.6.1.4.1.2011.5.25.111.6.13 nqaFTPStatsTestFailed

Description

NQA/4/FTPFAIL: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.13 Warning environmentalAlarm(7)

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 user name or password was incorrect; the file name was inexistent.

4.

The FTP service was not enabled.

5.

The file was oversized, and could not be transmitted with a specified period.

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 9.
    • 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 4.
    • If the route is reachable, go to Step 3.

  3. Run the display this command in the NQA test view to check whether the FTP user name is correctly configured. If not, run the ftp-username 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 9.
    • If not, go to Step 4.

  4. Run the display this command in the NQA test view to check whether the FTP password is correctly configured. If not, run the ftp-password 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 9.
    • If not, go to Step 5.

  5. Run the display this command in the NQA test view to check whether the FTP file name is correctly configured. If not, run the ftp-filename 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 9.
    • If not, go to Step 6.

  6. Run the display ftp-server command on the FTP server to check whether the FTP service is enabled. If not, run the ftp server enable command in the system to enable the FTP service.

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

  7. The file is oversized, and cannot be transmitted within a specified period. Run the timeout command in the NQA test view to modify the timeout period. The value ranges from 1 to 60. You can run the display this command in the NQA test view to view the current timeout period.

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

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

Related Information

None

NQA_1.3.6.1.4.1.2011.5.25.111.6.14 nqaFTPStatsTestCompleted

Description

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

Indicates that a test succeeded.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.111.6.14 Warning environmentalAlarm(8)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

OwnerIndex

Indicates the index of an NQA test instance.

TestName

Indicates the name of an NQA test instance.

Impact on the System

None.

Possible Causes

This trap occurred in the NQA test.

The test succeeded.

Procedure

  1. This trap message is informational only, and no action is required.

Related Information

None

NQA_1.3.6.1.4.1.2011.5.25.111.6.15 nqaFTPStatsThresholdNotification

Description

NQA/4/FTPTHRESHOLD:OID [oid] NQA entry over threshold. (OwnerIndex=[OCTET], TestName=[OCTET])

Indicates that the period of a test exceeded the set threshold. The threshold could be set by the user. The threshold rtd command could modify the threshold.

Attribute

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

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

OwnerIndex

Indicates the index of an NQA test instance.

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 threshold was set too small.

2.

The network was busy.

Procedure

  1. Run the display cpu-usage command in the system view to check whether the CPU has an excessive load.

    • If so, go to Step 3.
    • If not, go to Step 2.

  2. In the NQA test view, run the display this command to know the current threshold. Then run the threshold rtd command to modify the threshold as required. The recommended value is 20 ms.

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

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

Related Information

None

NQA_1.3.6.1.4.1.2011.5.25.111.6.16 nqaJitterStatsRTDThresholdNotification

Description

NQA/4/RTDTHRESHOLD:OID [oid] NQA entry RTD over threshold. (OwnerIndex=[OCTET], TestName=[OCTET])

Indicates that the period of a test exceeded the set threshold. The threshold could be set by the user. You can run the threshold rtd command to modify the threshold.

Attribute

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

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

OwnerIndex

Indicates the index of an NQA test instance.

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 threshold was set too small.

2.

The network was busy.

Procedure

  1. Run the display cpu-usage command in the system view to check whether the CPU has an excessive load.

    • If so, go to Step 3.
    • If not, go to Step 2.

  2. In the NQA test view, run the display this command to know the current threshold. Then run the threshold rtd command to modify the threshold as required. The recommended value is 20 ms.

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

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

Related Information

None

NQA_1.3.6.1.4.1.2011.5.25.111.6.17 nqaJitterStatsOWDThresholdNotificationSD

Description

NQA/4/SDTHRESHOLD:OID [oid] NQA entry OWD-SD over threshold. (OwnerIndex=[OCTET], TestName=[OCTET])

Indicates that the period of a test exceeded the set threshold. The threshold could be set by the user. The threshold owd-sd command could modify the threshold.

Attribute

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

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

OwnerIndex

Indicates the index of an NQA test instance.

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 threshold was set too small.

2.

The network was busy.

Procedure

  1. Run the display cpu-usage command in the system view to check whether the CPU has an excessive load.

    • If so, go to Step 3.
    • If not, go to Step 2.

  2. In the NQA test view, run the display this command to know the current threshold. Then run the threshold owd-sd command to modify the threshold as required. The recommended value is 20 ms.

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

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

Related Information

None

NQA_1.3.6.1.4.1.2011.5.25.111.6.18 nqaJitterStatsOWDThresholdNotificationDS

Description

NQA/4/DSTHRESHOLD:OID [oid] NQA entry OWD-DS over threshold. (OwnerIndex=[OCTET], TestName=[OCTET])

Indicates that the period of a test exceeded the set threshold. The threshold could be set by the user. The threshold owd-ds command could modify the threshold.

Attribute

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

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

OwnerIndex

Indicates the index of an NQA test instance.

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 threshold was set too small.

2.

The network was busy.

Procedure

  1. Run the display cpu-usage command in the system view to check whether the CPU has an excessive load.

    • If so, go to Step 3.
    • If not, go to Step 2.

  2. In the NQA test view, run the display this command to know the current threshold. Then run the threshold owd-ds command to modify the threshold as required. The recommended value is 20 ms.

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

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

Related Information

None

NQA_1.3.6.1.4.1.2011.5.25.111.6.20 nqaRisingAlarmNotification

Description

NQA/3/RISING_TRAP: OID [oid] The sampling value of alarming in the alarm table is over rising-threshold or equal to rising-threshold. (OwnerIndex=[OCTET], TestName=[OCTET], AlarmEntryNumber=[INTEGER],alarm value=[INTEGER], alarm sampling type=[INTEGER], sampling value=[INTEGER], rising-threshold=[INTEGER])

The value of the monitored node was greater than the upper threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.111.6.20

Minor

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

OwnerIndex

Indicates the name of the administrator for an NQA test instance.

TestName

Indicates the name of an NQA test instance.

AlarmEntryNumber

Indicates the index of a trap entry.

alarm value

Indicates the monitored trap variable.

alarm sampling type

Indicates the type of the sampled alarm:
  • 1: Average round trip delay
  • 2: Packet loss ratio
  • 3: Number of packets discarded from the source to the destination
  • 4: Number of packets discarded from the destination to the source
  • 5: Average jitter value
  • 6: Average jitter value from the source to the destination
  • 7: Average jitter value from the destination to the source.

sampling value

Indicates the sample value.

rising-threshold

Indicates the upper threshold.

Impact on the System

None.

Possible Causes

The value of the monitored node was greater than the upper threshold.

Procedure

  1. Run the display nqa-agent command in the user view and check the type of the sampled alarm. Run the display nqa results command based on this type and check the test result. Check whether the upper threshold is set too low.

    • If the upper threshold is set too low, go to step 2.
    • If the upper threshold is proper, go to Step 3.

  2. Run the alarm command to set a proper upper threshold.

    Perform the test again to check whether the alarm is cleared.
    • If the alarm is cleared, go to step 5.
    • If the alarm persists, go to Step 3.

  3. The alarm is triggered due to the entire network. Therefore, check that network configurations and services are proper. Then check whether the alarm is cleared.

    • If the alarm is cleared, go to step 5.
    • If the alarm persists, go to Step 4.

  4. Collect alarm information and configuration information, and then contact technical support personnel.
  5. End.

Related Information

None.

NQA_1.3.6.1.4.1.2011.5.25.111.6.21 nqaFallingAlarmNotification

Description

NQA/3/FALLING_TRAP: OID [oid] The sampling value of alarming in the alarm table is less than falling-threshold or equal to falling-threshold. (OwnerIndex=[OCTET], TestName=[OCTET], AlarmEntryNumber=[INTEGER], alarm value=[INTEGER], alarm sampling type=[INTEGER], sampling value=[INTEGER], falling-threshold=[INTEGER])

The value of the monitored node was smaller than the lower threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.111.6.21

Minor

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

OwnerIndex

Indicates the name of the administrator for an NQA test instance.

TestName

Indicates the name of an NQA test instance.

AlarmEntryNumber

Indicates the index of a trap entry.

alarm value

Indicates the monitored trap variable.

alarm sampling type

Indicates the type of a sampled alarm.

sampling value

Indicates the sample value.

falling-threshold

Indicates the lower threshold.

Impact on the System

None.

Possible Causes

The value of the monitored node was smaller than the lower threshold.

Procedure

  1. Run the display nqa-agent command in the user view and check the type of the sampled alarm. Run the display nqa results command based on this type and check the test result. Check whether the upper threshold is set too high.

    • If the upper threshold is set too high, go to step 2.
    • If the upper threshold is proper, go to Step 3.

  2. Run the alarm command to set a proper upper threshold.

    Perform the test again to check whether the alarm is cleared.
    • If the alarm is cleared, go to step 5.

    • If the alarm persists, go to Step 3.

  3. The alarm is triggered due to the entire network. Therefore, check that network configurations and services are proper. Then check whether the alarm is cleared.

    • If the alarm is cleared, go to step 5.

    • If the alarm persists, go to Step 4.

  4. Collect alarm information and configuration information, and then contact technical support personnel.
  5. End.

Related Information

None.

NQA_1.3.6.1.4.1.2011.5.25.111.6.22 nqaFtpSaveRecordNotification

Description

NQA/4/SAVED_TO_FTP_TRAP: OID [oid] The latest test's result record has saved to FTP server. (FileName=[OCTET])

The NQA test results were saved to the FTP server.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.111.6.22 Warning communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

FileName

Indicates the name of the saved file.

Impact on the System

None.

Possible Causes

The NQA test results were saved to the FTP server.

Procedure

  1. This trap message is informational only, and no action is required.

Related Information

None.

NQA_1.3.6.1.4.1.2011.5.25.111.6.28 nqaResultsTestResultChange

Description

NQA/4/TESTRESULTCHANGE:OID [oid] NQA entry test result changed. (OwnerIndex=[OCTET], TestName=[OCTET], ResultsIndex=[INTEGER], ResultsHop=[INTEGER], LastRecentResult=[INTEGER], CurrentResult=[INTEGER])

ICMP test results changed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.111.6.28 Warning environmentalAlarm(5)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
OwnerIndex Manager of the NQA test instance
TestName Name of the NQA test instance
ResultsIndex Index of the NQA test result table
ResultsHop Hop table index of the NQA test instance
LastRecentResult Last-time NQA test results
CurrentResult Current NQA test results

Impact on the System

The system will not be affected.

Possible Causes

ICMP test results changed.

Procedure

  1. If the status of a test instance changes from succeeded to failed, check whether the link has been interrupted.
  2. Collect alarm information and configuration information, and then contact technical support personnel.
  3. End.
Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065855

Views: 5172

Downloads: 6

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