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
Knowledge Base

NQA track

Publication Date:  2017-04-19  |   Views:  1260  |   Downloads:  0  |   Author:  a84069511  |   Document ID:  EKB1000580145

Contents

Issue Description

The customer is having issues utilizing the nqa test instance to track and automatically remove a static route from the routing-table. He is loosing connectivity to host X.X.X.X

The NQA status is "no result" instead of "failed".

Handling Process

1. Asked for the full output of the command display diagnostic-information

2. Check the configuration file

Solution

 After we have checked the configuration file, we saw that there were some problems in the configuration.

The value of frequency must be larger than the product probe-count and interval.

If the value is smaller, the NQA will have a “No result” status.

The default value of probe-count is 3, and the default value of interval is 4.

1. On the first device, he has the configuration:

nqa test-instance iseek icmp
test-type icmp 
destination-address ipv4 xx.xx.187.1 
probe-failtimes 3 
send-trap testfailure 
fail-percent 50 
frequency 5 
probe-count 2 
start now

Frequency(5) < probe-count(2) * interval(4), so the NQA status is "No result".

2.On the second device:

nqa test-instance TEST TEST
test-type icmp
destination-address ipv4 xx.xx.4.4
frequency 10 
start now

Frequency(10) < probe-count(3) * interval(4)

To solve this issue we have recommanded to the client to use command “frequency interval” to change the value, to be sure than the frequency is larger.

On the first device, the value must be at least 10 seconds and on the second device 15 seconds.