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.

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

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

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

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

The FTP service was not enabled.

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

Procedure

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.
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.
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.
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.
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.
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.
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.
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.
Collect alarm information and configuration information, and then contact technical support personnel.
End.

Related Information

None