Feature #1687
closedRoute inheritance test scenario
100%
Description
Develop a integration test for route inheritance flags.
Topology¶
B---A---C
|
D
Edges represent logical links (UDP tunnels).
Steps¶
- start NFD on A,B,C,D
- set multicast strategy for root namespace on A
- run traffic generator server on B,C,D each with these prefixes
- ndn:/A/P
- ndn:/A/B/C/Q
- ndn:/D/R
- ndn:/S
- add routes on A
- ndn:/ , nexthop=hostB, CHILD_INHERIT=yes, CAPTURE=no
- ndn:/ , nexthop=hostC, CHILD_INHERIT=no, CAPTURE=no
- ndn:/A , nexthop=hostB, CHILD_INHERIT=yes, CAPTURE=no
- ndn:/A/B/C , nexthop=hostD, CHILD_INHERIT=yes, CAPTURE=no
- ndn:/D , nexthop=hostC, CHILD_INHERIT=yes, CAPTURE=yes
- ndn:/D , nexthop=hostD, CHILD_INHERIT=yes, CAPTURE=no
- run traffic generator client on A to send 20 Interests to each of:
- ndn:/A/P
- ndn:/A/B/C/Q
- ndn:/D/R
- ndn:/S
- stop traffic generator server on B,C,D
- in traffic generator server reports, verify the number of served Interests of each traffic pattern, fail the test case if any condition is violated
- traffic generator server on B
- ndn:/A/P , >=18
- ndn:/A/B/C/Q , >=18
- ndn:/D/R , =0
- ndn:/S , >=18
- traffic generator server on C
- ndn:/A/P , =0
- ndn:/A/B/C/Q , =0
- ndn:/D/R , >=18
- ndn:/S , >=18
- traffic generator server on D
- ndn:/A/P , =0
- ndn:/A/B/C/Q , >=18
- ndn:/D/R , >=18
- ndn:/S , =0
- traffic generator server on B
Files
Updated by Junxiao Shi over 10 years ago
- Subject changed from Basic integrated tests for NRD with flags to Route inheritance test scenario
- Description updated (diff)
- Estimated time set to 6.00 h
Updated by Junxiao Shi over 10 years ago
- Related to Task #1325: Generate FIB updates added
Updated by Junxiao Shi over 9 years ago
- Tracker changed from Task to Feature
- Target version changed from v0.3 to v0.4
Updated by Hila Ben Abraham about 9 years ago
- Assignee changed from Vince Lehman to Hila Ben Abraham
Updated by Hila Ben Abraham almost 9 years ago
- Status changed from New to In Progress
Updated by Hila Ben Abraham over 8 years ago
- File client.log client.log added
- File serverB.log serverB.log added
Is there a way to set ndn-traffic to send a fixed number of interests per name (without running ndn-traffic separately for each name)? The test fails occasionally when the number of interests sent for one of the names is less than 18. (See attached files)
Updated by Junxiao Shi over 8 years ago
Is there a way to set ndn-traffic to send a fixed number of interests per name (without running ndn-traffic separately for each name)?
No. In step 4, you may run four traffic generator client instances in parallel.
The test fails occasionally when the number of interests sent for one of the names is less than 18.
If traffic generator client is configured to send 80 Interests, and there are four traffic patterns each with 25% share, it's supposed to send exactly 20 Interests per traffic pattern.
Otherwise, this should be a bug of traffic generator.
Step 7 specifies "at least 18" to accommodate packet loss.
Updated by Hila Ben Abraham over 8 years ago
- File NDNTrafficClient.conf NDNTrafficClient.conf added
If traffic generator client is configured to send 80 Interests, and there are four traffic patterns each with 25% share, it's supposed to send exactly 20 Interests per traffic pattern.
Otherwise, this should be a bug of traffic generator.
Then I believe it is a bug. See attached client config file (and previously uploaded client.log).
Updated by Hila Ben Abraham over 8 years ago
- Status changed from In Progress to Code review
- % Done changed from 80 to 100
No. In step 4, you may run four traffic generator client instances in parallel.
I uploaded a draft patchset that uses 4 instances of traffic generator to avoid the issue. It can be easily changed later.
Updated by Hila Ben Abraham over 8 years ago
- File 20160209230045.tgz 20160209230045.tgz added
20160209230045.tgz indicates that all tests passed successfully except of test-remote-register.
Updated by Junxiao Shi over 8 years ago
- File 20160215233745.tgz 20160215233745.tgz added
Updated by Junxiao Shi over 8 years ago
- File 20160224213124.tgz 20160224213124.tgz added
- Status changed from Code review to Closed