1 .. This work is licensed under a Creative Commons Attribution 4.0 International
3 .. http://creativecommons.org/licenses/by/4.0
4 .. (c) OPNFV, 2018 Intel Corporation.
6 *********************************************************
7 Yardstick Test Case Description: NSB EPC SAEGW RELOCATION
8 *********************************************************
10 +-----------------------------------------------------------------------------+
11 |NSB EPC SAEGW throughput with relocation test case |
13 +--------------+--------------------------------------------------------------+
14 |test case id | tc_epc_saegw_tput_relocation_landslide |
17 +--------------+--------------------------------------------------------------+
18 |metric | All metrics provided by Spirent Landslide traffic generator |
20 +--------------+--------------------------------------------------------------+
21 |test purpose | The Spirent Landslide product provides one box solution which|
22 | | allows to fully emulate all EPC network nodes including |
23 | | mobile users, network host and generate control and data |
26 | | This test allows to check processing capability of EPC |
27 | | handling large amount of subscribers X2 handovers between |
28 | | different eNBs while UEs are sending traffic. |
30 | | It's easy to replace emulated node or multiple nodes in test |
31 | | topology with real node or corresponding vEPC VNF as DUT and |
32 | | check it's processing capabilities under specific test case |
33 | | load conditions. |
35 +--------------+--------------------------------------------------------------+
36 |configuration | The EPC SAEGW throughput with relocation tests are listed |
39 | | * tc_epc_saegw_tput_relocation_landslide.yaml |
43 | | * is set as 60sec (specified in test session profile); |
53 | | Traffic transaction rate: |
57 | | Number of mobile subscribers: |
61 | | Number of default bearers per subscriber: |
69 | | Mobility time (timeout after sessions were established after |
70 | | which handover will start): |
74 | | Handover start type: |
76 | | * When all sessions started; |
80 | | * Single handoff; |
84 | | * 120 subscribers/s. |
86 | | The above fields and values are the main options used for the|
87 | | test case. Other configurable options could be found in test |
88 | | session profile yaml file. All these options have default |
89 | | values which can be overwritten in test case file. |
91 +--------------+--------------------------------------------------------------+
92 |test tool | Spirent Landslide |
94 | | The Spirent Landslide is a tool for functional & performance |
95 | | testing of different types of mobile networks. It emulates |
96 | | real-world control and data traffic of mobile subscribers |
97 | | moving through virtualized EPC network. |
98 | | Detailed description of Spirent Landslide product could be |
99 | | found here: https://www.spirent.com/Products/Landslide |
101 +--------------+--------------------------------------------------------------+
102 |applicability | This EPC UE SERVICE REQUEST test cases can be configured with|
105 | | * packet sizes; |
106 | | * traffic transaction rate; |
107 | | * number of subscribers sessions; |
108 | | * handover type; |
109 | | * mobility rate; |
110 | | * mobility time; |
111 | | * mobility mode; |
112 | | * handover start condition; |
113 | | * subscribers disconnection rate; |
115 | | Default values exist. |
117 +--------------+--------------------------------------------------------------+
118 |references | ETSI-NFV-TST001 |
122 +--------------+--------------------------------------------------------------+
123 | pre-test | * All Spirent Landslide dependencies are installed (detailed |
124 | conditions | installation steps are described in Chapter 13- |
125 | | nsb-installation.rst and 14-nsb-operation.rst file for NSB |
126 | | Spirent Landslide vEPC tests; |
128 | | * The pod.yaml file contains all necessary information |
129 | | (TAS VM IP address, NICs, emulated SUTs and Test Nodes |
130 | | parameters (names, types, ip addresses, etc.). |
132 +--------------+--------------------------------------------------------------+
133 |test sequence | description and expected result |
135 +--------------+--------------------------------------------------------------+
136 |step 1 | Spirent Landslide components are running on the hosts |
137 | | specified in the pod file. |
139 +--------------+--------------------------------------------------------------+
140 |step 2 | Yardstick is connected with Spirent Landslide Test |
141 | | Administration Server (TAS) by TCL and REST API. The test |
142 | | will resolve the topology and instantiate all emulated EPC |
145 +--------------+--------------------------------------------------------------+
146 |step 3 | Test scenarios run, which performs the following steps: |
148 | | * Start emulated EPC network nodes; |
149 | | * Establish subscribers connections to EPC network (default |
151 | | * Start run traffic; |
152 | | * After specified in test case mobility timeout, start |
153 | | handover process on specified mobility rate; |
154 | | * Disconnect subscribers at the end of the test. |
156 +--------------+--------------------------------------------------------------+
157 |step 4 | During test run, all the metrics provided by Spirent |
158 | | Landslide are stored in the yardstick dispatcher. |
160 +--------------+--------------------------------------------------------------+
161 |test verdict | The test case will create the test session in Spirent |
162 | | Landslide with the test case parameters and store the |
163 | | results in the database for benchmarking purposes. The aim |
164 | | is only to collect all the metrics that are provided by |
165 | | Spirent Landslide product for each test specific scenario. |
167 +--------------+--------------------------------------------------------------+