About Test Server Configuration
Each test server comes equipped with Ethernet interfaces (The total number of Ethernet Interfaces depends on the TS hardware): one interface, the designated management port, is used to communicate with the TAS, and the other interfaces are used for IP communications with SUTs, other interfaces, or other test servers during test operations. Interfaces that are used for testing are referred to generally as test ports. The test system's ability to simulate thousands of devices in the network is achieved by associating a pool of addresses with each test port and with the local (loopback) interface.
|
NOTE: If the Test Server is not in Kernel mode, we no longer limit the number of IP addresses defined per interface in TS Configuration to < 2000 per port or <~ 24000 total. |
These addresses are normally assigned to emulators that simulate the network nodes that interact with the simulated mobile nodes and the SUTs. The only limit on the address pool assigned to the local interface is the range of contiguous addresses available in the network's address space. These addresses are normally used for the MN home addresses when the test simulates an HA or GGSN, for MN co-located care-of addresses, or for Client Node addresses. See Configuring the Interface Ports and NTP for more information regarding IP address management.
You can configure various routing options on a test server and define static routes. The routing configuration that you define for a test server is considered its default routing. The emulators that are included in the test definition will use the test server's default routing unless you specify a different route in the emulator definition.
VPN enabled Test Servers and TASs
To configure a VPN connection between a TAS and Test Server, follow the steps outlined in topic Configure VPN between TAS and Test Server.
The Configuration Window
The management port is configured on each test server during the initial installation process. With the Test Server Configuration window, System Administrators can configure the test ports after installation, and save several different configurations for a test server. A test server can then be quickly re-configured by applying a saved configuration. The interfaces and addresses are configured on the Main tab, and the routing options are configured on the Routing tab.
-
The window title displays the test server's management IP address and indicates the type of configuration that is displayed. Note: As of release 19.8, you can no longer change the TS password from the GUI. See topic Changing the cfguser Password.
-
An option to configure Advanced Security was added to the ipcfg script for virtual machines. When enabled "Advanced Security is On" will be displayed on the Main screen (see below) otherwise you will see "Advanced Security is Off". Advanced Security is only supported on TAS only or TS only systems. It is not supported on ES systems (TAS+TS).Additional details can be found in this document - Advanced_Security.
IMPORTANT:
- Either ALL the TSs and TAS use Advanced Security or none of them should as there could be potential communication errors between the TAS and the TSs.
- After changing password for spcoast in Advanced Security, please restart or reboot the TAS to take effect.
-
The configuration control buttons provide the following options:
-
-
Refresh displays the current configuration.
-
Backup stores a backup of the test server configuration on the TAS. Only one backup file is maintained per test server, so subsequent backups will overwrite the existing file for the test server. The backup file's creation date/time appears directly above the configuration control buttons.
-
Restore restores the backup of the test server configuration from the TAS. (This button is enabled only if a backup file exists.)
-
Open displays a saved configuration that you select from a list of saved configurations. A configuration is saved only when you apply it.
-
Apply applies the displayed configuration to the test server and saves the configuration definition.
-
Close closes the window.
Configuration Warnings: A TAS will indicate Configuration Warnings when a newer Test Server indicates features that the current TAS version does not support.
Configuration with IPv4 IP Address:
-
-
-
-
Configuration with IPv6 IP Address: Additional fields such as Alternate IPv4 Address, Alternate IPv4 Mask, Alternate IPv4 Gateway are displayed.
-
-
-
-
A tab Time Sync is available to configure NTP or PTP.
-
The TAS IP Address and Platform / OS are now displayed on the Test Server Configuration screen.
-
Connect to TAS TCP Port - See Proxy between TAS and TS Server. Use to point the Test Server to use the TCP port configured in TAS’s ipcfg.
-
Enable Remote Test/Auto TS Mode : Note : This option is no longer supported. Enable for Remote test, Auto TS Mode. Select for a single test server test session to be scheduled to run many times remotely on a test server, without the TAS sequencing the test sessions themselves. If the TAS and Test Server lose connectivity between each other, the tests will continue to run on schedule. When the connectivity is re-established, the TAS will catch up and retrieve the test results for any tests that completed while disconnected. The number of TS Processes must be 1. You must enable this option in the "Test Session" - Select "Remote Test, Auto TS Mode". Additional details can be found in the About the Test Session Window.
-
UE Info Level : Default = 10. Select level 10 to get all the VisionWorks Results that are used by the Landslide Test Analytics Reporting. Select Level = 3 to see only the UE IP Address and main State transitions. Remaining values are for future use. Additional configuration details can be found in the topic VisionWorks Solution.
-
NOTE: May get NULL Values for items that are not reported by your test case. When setting a UE Info Level X (1 to 10), that means that the UE Info component will include fields A, B, and C. But that does not mean the test will always report B or C, thus the UE Info report will show a column for B or C and it would be null. for example, if using level 9 and you do not do a POLQA on Default Bearer, you will get POLQA columns, but they will always be null.
-
Use the Management Port configuration fields to modify the address pool, the IPv6 settings, and the speed and duplex settings for the management port. If an IPv6 Management Port address is used, additional fields will be displayed: Alternate IPv4 Address, Alternate IPv4 Mask, Alternate IPv4Gateway are displayed. The MTU is now displayed on this screen. See Configuring the Interface Ports and NTP for more information regarding IP address management.
|
NOTE: If there are any connection issues when connecting (for e.g., the Dell servers) to a 100Mb infrastructure, setting the speed and duplex may resolve this issue. |
-
Use the Local Interface configuration fields to modify the IPv4 and IPv6 address pools associated with the local interface. See Configuring the Interface Ports and NTP for more information regarding IP address management.
-
Use Data Gen Performance to indicate the threading mode used to run the test server. Currently, there are three Data Gen Performance modes, Legacy, Max and Fireball.
|
NOTE: Data Gen performance Mode is supported on Landslide C100 M4. |
|
Legacy |
In Legacy mode there is a balance of allocated processor resources between data and control plane processes. |
|
|
Max |
In Max mode there is an allocation bias toward data plane processes with increased isolation between data and control plane processes. |
|
|
Fireball |
In Fireball mode there is an allocation bias toward maximum data plane performance for certain basic DMF data types and transport protocols. This performance increase comes at the expense of DMF functionality and flexibility and restricted support for transport protocols/technologies. Fireball Mode is used in conjunction with the Fireball checkbox which is supported in several test cases including MME Nodal and SGW Nodal. Fireball is a DMF threading model that provides optimized data performance.
Processes - Click on box for pop-up to enable Fireball per process. Currently up to four processes are supported.
A Process can either be enabled for Fireball or Reserved for POLQA/PEVQ/IVR/Digital Signal Processing (DSP), not both. To provision some Processes for Fireball and others to Reserve Resources for POLQA/VMAF/IVR/Digital Signal Processing (DSP): (TS must be Licensed for these features)
When you click Apply with Fireball or POLQA/VMAF/IVR/DSP, EXT Apps resources enabled, you will get this warning dialog, explaining the impacts and requirements of your configuration:
If you check the "Do Not Show" you will never see this dialog again. If your configuration changes were successful, you will get this message:
If your configuration changes were NOT successful, your configuration may revert back to Max mode (Review Real Time Logs and Warning/Errors Tab of Test Server Administration for warnings/errors). Select to Fireball and Reserve Fireball Cores (s) on test server to support test cases with mixed Fireball checkbox and Regular DMFs. Several kinds of Fireball DMF are supported : fb_udp, fb_tcp, fb_quic, fb_http, fb_https and RTP traffic with Fireball enabled. See this table for supported options. Go to Test Server Administration Window to view your TS Configuration. |
-
Reserve Resources to Perform: (POLQA/VMAF/IVR or Digital Signal Processing) - Select to allocate CPU core to perform POLQA and/or PEVQ Calculation or IVR (Voice Recognition) or Digital Signal Processing (Ringtone detection). For addition information go to About VoLTE POLQA Testing and About VoLTE VMAF Testing. For additional information on Ringtone Detection go to RTP.
-
Reserve External Apps Cores : Options : 1 or 4, Default = 1. Any VM with less than 8 Cores, allow 1 Reserve External Apps Cores. Any VM with 8 or more Cores, allow 4 Reserve External Apps Cores. Select to reserve thread (s) on the test server to process External Apps. Only valid when a TS-process is not in Fireball Mode or Fireball Mode with Hybrid vTS License (TS-License must be selected for resources to be reserved). A tooltip will indicate how many data cores are available - example : Data Cores Available: 4 . Note : Multiple reboots may happen after applying the configuration.
-
Reserve Fireball Cores : Options : 1 or 4, Default = 1. Select to reserve Fireball Cores (s) on test server to support test cases with mixed Fireball and Regular DMFs. Only applicable when using standard Fireball mode. (see above). The available range depends on TS configuration. For example, TS is M4 with 8 cores per process: if CPA is enabled, 3 cores will be occupied for control plane, 1 core for collect data on eth port, 4 cores for data, valid range for “Reserve Fireball Cores” will be 1-3. If CPA is not enabled, 1 core for control plane, 1 core for collect data on eth port, 6 cores for data , valid range for “Reserve Fireball Cores” will be 1-5.
-
When clicking Apply (or Close) when any of the above checkboxes are selected, you will see this Information pop-up:
-
Other Ethernet DPDK-1 Tab
-
Use the Other Ethernet (DPDK-1) tab shown above to modify the IP address, the address pool, Mask, # of IPs, Network Interface Card Type, the interface status, the speed, Limit ETH MTU to 2K bytes (default=off), Hybrid , Hybrid Type , Promiscuous, VLANs and VLAN ID Ranges, Disable V6 Route Advert and duplex settings for each of the test server's Ethernet test ports. IPv4 (ethn) and IPv6 (ethnv6) configurations for each interface are displayed on separate rows.
-
Wi-FI Tab - Select to define Wi-FI information associated with the Test Server.
-
UE Tab - Select to configure information for the UEs available on the UE Node Test Case.
-
OTA Tab - Select to configure the OTA devices for the UE Node Test Case.
-
Time Sync tab - Configuring the Interface Ports and NTP
-
Use the NTP Sync Status configuration fields to change the NTP server address, to observe the synchronization status, and to synchronize the test server with its time server. The NTP server assigned to the TAS can also be changed using the ipcfg script and via Configuring the Interface Ports and NTP.
-
Status Color Description N/A White If there is no trace reported Not-In-Sync Red If first row of trace contains stratum15 or stratum16 or stratum 16 In-Sync White If there are more than 2 rows In-Sync (See trace) Green If there are 2 or fewer rows
|
NOTE: Use the TAS Manager Console to view the TAS NTP status and synchronize the TAS. |
-
Add support for PTP (Precision Time Protocol - IEEE-1588 - it can achieve clock accuracy to the sub-microsecond range).
-
Available on Test Servers with Ubuntu > = 20.04. If a test server supports PTP, "timeSyncProtocol" will appear in the .tsConfig file with a value of "ntp" or "ptp".
-
Select PTP Transport Mode - "Ipv4" or Ethernet. If Ipv4 is selected then configure PTP IP Mode.
-
Configure PTP IP Mode - Select Multicast or Unicast or Hybrid.
-
Configure PTP Master IP - available if Unicast is selected. Enter Valid IPv4 address with no mask.
-
Configure the routing options that the test server will support. Click Add and then double-click to configure Destination IP, mask (format: n.n.n.n/n::n also supported), and Gateway IP.
Related Topics