From: Maryam Tahhan Date: Wed, 8 Apr 2015 08:07:30 +0000 (+0000) Subject: Merge "TestSpec: Add LTD.Throughput.RFC2889.AddressLearningRate" X-Git-Tag: brahmaputra.1.0~168 X-Git-Url: https://gerrit.opnfv.org/gerrit/gitweb?a=commitdiff_plain;h=ca6d6350503c1813c32dde953a24340aa5298c21;hp=8137a2790e79cb01f4afe49f4da043c4741f8e0d;p=vswitchperf.git Merge "TestSpec: Add LTD.Throughput.RFC2889.AddressLearningRate" --- diff --git a/test_spec/vswitchperf_ltd.md b/test_spec/vswitchperf_ltd.md index 98cf489d..e7a8d528 100755 --- a/test_spec/vswitchperf_ltd.md +++ b/test_spec/vswitchperf_ltd.md @@ -814,6 +814,31 @@ The following represents possible deployments which can help to determine the pe - Physical → virtual switch → physical. +
+ - #####Test ID: LTD.Throughput.RFC2889.AddressLearningRate + **Title**: RFC2889 Address Learning Rate Test + + **Prerequisite Test**: LTD.Memory.RFC2889.AddressCachingCapacity + + **Priority**: + + **Description**: + + The aim of this test is to determine the rate of address learning of the DUT for a constant load (fixed length frames at a fixed interval time). The selected frame sizes are those previously defined under [Default Test Parameters](#DefaultParams), traffic should be sent with each IPv4/IPv6 address incremented by one. The rate at which the DUT learns a new address should be measured. The maximum caching capacity from LTD.Memory.RFC2889.AddressCachingCapacity should be taken into consideration as the maximum number of addresses for which the learning rate can be obtained. + + **Expected Result**: + It may be worthwhile to report the behaviour when operating beyond address capacity - some DUTS may be more friendly to new addresses than others. + + **Metrics collected**: + + The following are the metrics collected for this test: + + - The address learning rate of the DUT. + + **Deployment scenario**: + + - Physical → virtual switch → physical. +
[RFC1242]:(http://www.ietf.org/rfc/rfc1242.txt) [RFC2544]:(http://www.ietf.org/rfc/rfc2544.txt)