Documente Academic
Documente Profesional
Documente Cultură
Set Up Guide
TeraVM Version 12.1
Part no: 47090/390
Help and Support
Note
You can also contact support using the mail alias for your region:
TeraVMSupport.CN@aeroflex.com (China)
TeraVMSupport.EMEA@aeroflex.com (EMEA)
TeraVMSupport.JP@aeroflex.com (Japan)
TeraVMSupport.KO@aeroflex.com (Korea)
TeraVMSupport.IND@aeroflex.com (India)
Table of Contents
TeraVM Terminology ..................................................................................................................................................... iii
TeraVM Terminology
The following terminology is used in TeraVM documents:
• TeraVM Executive: The Executive hosts a number of central services for TeraVM such as the Centralized Test
Library, License Tracker, Pool Manager, User Authentication and Licensing.
• TeraVM Controller (TVM-C): The Controller sets up a TeraVM test, directs TeraVM test modules to generate
and receive IP traffic, executes the test and processes results.
• Pool Manager: The Pool Manager allocates test interfaces (test modules) to one or multiple TeraVM controllers.
• TeraVM Test Module (TVM): A Test Module is a virtual machine that generates and receives IP traffic. It
contains one or multiple Test Agents. Each Test Module has one or more Network Interfaces.
• Test Agent: This is an IP traffic generator/receptor. Each Test Module has one or more Test Agents. Each Test
Agent has one or more Test Interfaces, associated with virtual network adapters through which traffic flows to/
from the SUT.
• System Under Test (SUT): The users' device/network/system under test. May be multiple SUTs in one TeraVM
system.
• Test Bed: a logical test structure to test one or more SUTs: consists of one or more TeraVM Controllers and one
or more Test Modules.
• Test Group, test case: Test containing multiple entities such as hosts and applications. Only one instance of a test
group can be run by a user at a given time.
Chapter 1. Introduction
The Cobham TeraVM Appliance is a fully virtualized IP test and measurement solution that can emulate and measure
millions of unique application flows.
The Appliance is pre-installed on an ESXi Hypervisor and includes all the hardware, software, and license files
required to run a stand-alone test system. TeraVM is pre-installed and pre-configured with your required test bed set
up, allowing you to quickly create and run tests.
This guide contains:
• A brief introduction to TeraVM concepts. For more details, see the TeraVM User Guide.
Figure 2-1. TeraVM Appliance Architecture with Test Module Type TVM-5 Configuration
ESXi Hypervisor
TeraVM Management Network
Executive
Controller
(with Pool Manager)
Test Modules
One of four types of test module is pre-configured on your Appliance, based on your test requirements. In the example
above, the Appliance has four test modules (numbered 3 to 6) of type TVM-5.
The configurations for each test module type are shown in the table below.
• Usually one CPU core in each TVM is used for processing overhead, but in the case of TVM-8 and TVM-16, half
of the cores are required for overhead. The other cores are used for running tests and are called Test Agents.
Test Interfaces
Each test agent of your test modules has a Test Interface that is mapped to a Physical Test Port or Gigabit Ethernet
Interface configured on your Appliance. Examples are shown in the table below, which assumes one test interface
per test agent. For TVM-2, one test interface is connected to each physical port; for TVM-5, four test interfaces are
connected to each port and so on.
Note
Test Interfaces are numbered by using the format <test module instance #>/<test agent #>/<test interface #>,
where instance refers to the test module number. For example, a TVM-5 with an instance number of 3 has four
test agents, whose test interfaces are named: 3/1/3, 3/2/3, 3/3/3, 3/4/3. For an Appliance with four test modules
of type TVM-5, the interface naming goes up to 6/1/3, 6/2/3, 6/3/3 and 6/4/3, as indicated in the table. Test
module instance numbering and test interface numbering always starts with 3.
In each case, there are four test module instances, except for TVM-16 which has only two instances, and hence only
two ports are used. The virtual interface listed is the one from the highest numbered test agent of the test module
instance.
With the TeraVM Pool Manager, you can create elastic test beds, where the size of the test bed, and hence resource
usage, is determined by an individual test's run-time requirements. Multiple logical test beds (corresponding to Pool
Manager topologies), each with a separate System Under Test (SUT), are possible from one physical network.
TeraVM test modules are managed by the Pool Manager and allocated to the controller at test run-time.
Each test module has one or more test interfaces for generating and receiving network traffic. When a TeraVM
controller starts a test, it requests the Pool Manager for available test interfaces. The way the interfaces are assigned
depends on which interface selection mode is in force:
• Pool Manager Mode: Interface selection is based on a user-defined set of topologies and categories. If test
modules with those interface types are available, the Pool Manager assigns those test modules to the TeraVM
controller at run-time.
• Classic Mode: This corresponds to pre-12.0 operation: in this mode, it is still possible to select interfaces directly,
for example 3/1/3.
Note
Your TeraVM Appliance is pre-configured in Classic Mode but you can change this to Pool Manager
Mode later, as described in the TeraVM User Guide.
2. Management Connectivity.
Set Up Hardware
Set Up Complete
2. Set Up Hardware.
6. Set new Executive IP address from the Controller HTML5 UI login page.
Note
Your Appliance comes with pre-configured static management IP addresses on the Host and TeraVM
components. You can change these to other addresses when setting up the Appliance.
3.1. Prerequisites
Before you begin setting up the TeraVM Appliance, you need to have access to:
• A PC running a standard web browser, such as Internet Explorer, Firefox, Safari or Chrome.
– The PC must be assigned a static IP address. This address must be between 192.168.0.1 and 192.168.0.251
with a subnet of 255.255.255.0.
Your Appliance is of type TVM-630, which uses one management port to connect to the network. Connecting a PC to
this port allows you to set up management IP addresses for your TeraVM components. After you have configured the
IP addresses, you will connect this port to your Local Area Network.
Test Ports
In the example shown, the Appliance is configured with 4x10GbE SFP test ports (on two dual port Network Interface
Cards), labelled from right to left, starting at Port 3. These are the ports that you will connected to your System Under
Test.
• 1 x Ready Rails Kit II 1U, A7, DP/N – 09D83F with Rack Installation Instructions
• Plug one end of a network Ethernet Cable into the Management Port, and the other end into the PC.
Note
At least one of the four physical test ports (Ports 3-6) must be connected to another test port or a system under
test for traffic generation purposes.
Figure 3-4. Dell PowerEdge R630 Monitor and USB Cables (Front View)
Figure 3-5. Dell PowerEdge R630 – Front View with Power Button
Powering up the system takes approximately five minutes. Once it has booted successfully the ESXi home screen is
displayed.
Note
It is important not to change any ESXi settings other than the IP address. Otherwise the system may not operate
as expected.
2. Login with:
• Username - root
• Password - lambay3456
Note
The screen views may differ depending on your configuration.
3. Use the arrow button to scroll down to Configure Management Network and press Enter.
• Scroll down to Set static IP address and network configuration and press space bar to select.
• Scroll down to IP Address and type the new IP address of the ESXi Host.
• Scroll to Default Gateway and enter the IP address of the default gateway.
• Click Enter.
• Scroll down to Use dynamic IP address and network configuration and press space bar to select.
• Click Enter.
1. Open a web browser and go to the default TeraVM Controller Management IP address: http://192.168.0.252. This
will open the TeraVM Controller UI login screen. If prompted, you may have to set the IP address of the TeraVM
Executive first.
Note
The first time you log in, any username and password is accepted. Refer to the TeraVM User Guide for
information on setting up Microsoft Active Directory.
• Username – diverAdmin
• Password – diversifEye
6. To change the IP address to a statically assigned address, select Static IP Address under Address Assignment
and enter the new Host Name, Host IP Address, Netmask and Default Route details for your controller and click
Save.
7. Alternatively, to change to a dynamic IP address (DHCP), select Dynamic (DHCP) Address under Address
Assignment and click Save.
8. When the controller has finished rebooting, proceed to the next step.
Note
The first time you log in to the Executive, any username and password is accepted. Refer to the TeraVM
User Guide for information on setting up Microsoft Active Directory.
5. Alternatively, set up a dynamic IP address (DHCP) as described in Change the TeraVM Controller Management
IP Address. The network service will restart.
6. Connect the Management Port on the Appliance to your Local Area Network.
Note
If you select DHCP addressing, the addresses will be assigned when you connect your Appliance to the
LAN. In order to find out what IP addresses have been assigned to your Controller and Executive, you
will need to download vSphere and click on the Controller and Executive console tabs. You can download
vSphere from the Host IP address.
2. Enter the new Management IP Address of the TeraVM Executive here, and click Set IP.
3. You are brought to the Controller UI login screen. Enter your username and password and click Sign In.
• Refer to the TeraVM Java Client User Guide for details on how to download the Java Client and run tests from
there.
4.1. Licenses
Licenses are required to run your tests. The TeraVM Appliance is pre-configured with a system-specific license. It is
possible to add new licenses or migrate these licenses to a dedicated License Server.
The system-specific license includes basic applications to enable multicast and TeraFlow UDP and TCP traffic profiles.
Additional licenses can be obtained (for example, licenses for running VoIP tests) via Cobham Sales.
A.1. Introduction
If you have purchased TVM-630s to be used in the TeraVM Test Bed Management configuration, you can pool
multiple TVM-630s as a combined system in different ways. A set of TVM-630s can act as a single test bed or multiple
individual (or local) test beds, where the smaller test beds have two or four physical ports. The single Test Bed uses
a Master Controller which can control all test ports. When a test port is assigned to the Master Controller, it is not
available to an individual test bed.
• A TVM-630 with 2 test beds has 2 test modules each with 1x10GE Test Port (Total 4 Test Ports)
• A TVM-630 with 1 test bed has 4 test modules each with 1x10GE Test Ports (Total 4 Test Ports)
• The Master TVM-Controller can manage test modules from some or all of the other TVM-630s
• The maximum number of TVM-630s is 12. In this guide, however, 4 TVM-630s are used for illustration purposes.
If you have 4 Dell R630s configured with 2 test beds each, for example, the Test Bed Management system could be set
up as 8 independent test beds with each one using 2 test modules. Alternatively, if you require 4 independent test beds,
1 test bed could have 10 test modules while the 3 remaining test beds could use 2 test modules each.
Note
The Test Bed Management solution requires an external hub/switch. This switch provides connectivity between
all the TeraVM Comms ports on the TVM-630s.
The Test Bed Management solution does not create any port group or vSwitch.
The following is an example of a possible Test Bed Management configuration using 4 TVM-630s with an external
hub/switch.
The above shows several independent test beds using local Controllers, and one (the first test bed in Slave_3),
dependent on the Master Controller.
Once all of the appropriate physical connections are made, assign an IP address to each Hypervisor or Host. Please
refer to Changing ESXi Host IP Address.
To access the web interface open a web browser and enter http://<Master Controller IP Address>/TeraVM", where
Master Controller IP Address is the IP Address assigned to the Master Controller. Click on TeraVM.
Click Test Bed Management at the end of the TeraVM Menu page to open the Test Bed Management page.
In the Add New Host section provide the details for each host being deployed in the Test Bed Management
configuration and click Add:
• Host Label
– This is pre-configured and physically labelled by Cobham to indicate what order the servers are to be
mounted on the rack. The first TVM-630 host is given the Host Label ‘Master’ and each subsequent
TVM-630 has the label ‘Slave_#’ where ‘#’ is the incremented number.
– In the designated Master Host, the first Controller is the Master Controller.
Note
The servers should be mounted in this order: Master, Slave_1, Slave_2 and so on.
• Host Address
– The Host Address is the IP address or Hostname of the TVM-630 on the rack.
• Hypervisor Port
– The port used to connect to the hypervisor. This is given the default value of 443.
• Username
Note
You need to check the host labelling to determine the number of test beds present on the host. Example of
Labelling:
Slave_1 --> IP address = 10.10.10.3 --> Test Bed A and Test Bed B
Once a new host is added, an authentication connection to the hypervisor installed on the host is attempted to check that
there is connectivity and that the credentials provided are correct. If the connection succeeds the host is added to a table
that is displayed on the same page above the “Add New Host” section.
If the connection attempt to the hypervisor fails, a Host Not Found error message appears at the top of the Test Bed
Management page.
Once the addition of the new host is successful the Host Label field automatically changes to the next label type. For
example, if the Master has been added successfully, the Host Label in the Add New Hosts section changes to “Slave_1”
and if a new host has been added successfully as Slave_1, then the Host Label changes to “Slave_2” and so on.
The following is an example of the Test Bed Management page with a Master host and several Slave hosts added.
In the Hosts TVMs Assignment Table there are two sections with two columns each.
• Host Address: the host network address (IP or hostname) as entered by you.
• Testbed A: Choose whether the test modules in the first Test Bed (Testbed A) in the host are assigned to the
host’s own “Local” controller or the “Master” controller.
• Testbed B: Choose whether the test modules in the second Test Bed (Testbed B) in the host are assigned to the
host’s own “Local” controller or the “Master” controller.
Note
Both Testbed A and Testbed B drop-down assignment options are only active if the Number of Testbeds = 2
when adding the host.
• “Unchanged”: This is the default value and means that no changes have been made on the host since the last
applied change to Test Bed Management. If the assignment was previously changed from the TeraVM Controller
Administration Interface, and “Unchanged” is selected, the previous selected value will be displayed as soon as
the page is refreshed.
This is also the default value given when the hosts are mounted in the Test Bed Management configuration
for the first time. This is because the system is not able to determine the actual configuration and so it is set to
“Unchanged” by default.
• “Master”: If selected, the test modules part of the test bed will be “assigned” to the Master Controller, that is the
network configuration will be changed on the test modules to use the TeraVM Comms Master network. See the
example in TeraVM Overview.
• “Local”: If selected, the test modules part of the test bed are “assigned” to the Local controller, that is the
network configuration will be changed on the test modules to use the TVM_Comms_1 for TestBed A or the
TVM_Comms_2 for the TestBed B.
Note
You must stop all tests on the controller affected by the change before you apply the modification. Failing to
stop a test before applying the changes could result in inconsistent behavior of the controller. If this occurs,
restart the affected controller.
Click Apply once a change has been made to the test modules assignment (label 2 in TVMs Assignment). This calls the
required services on the controller to contact the hypervisors on the hosts and performs the required changes.
Note
On TestBed A of the Master Host, it is not possible to change the TVMs Assignment. The combo box is set to
“Master” and cannot be changed. This is because the test modules for that test bed are always assigned to the
Master controller.
Also, when adding information on a new host, if you have selected “1” as Number of Testbeds for that host, the TVM
Assignment combo box of the TestBed B is disabled for that host as there is only one test bed.
In the following example, Slave_3 host has the test modules in Testbed A reassigned to ‘Local’ while the test modules
in Testbed B are reassigned to ‘Master’.
Once the change is successful, a notification appears at the top of the Test Bed Management page reporting on what has
changed.
Note
If you modify the host configuration using the hypervisor, the solution will no longer be synchronized.
To do this click Update Hosts Information at the top of the Hosts section of the Test Bed Management page.
The Update Hosts Information page allows you to modify the hosts’ Host Address, Hypervisor Port, Username,
Password and the Number of Testbeds assigned to the port.
Click Save to enforce a change on the host or Reset to remove changes made to fields before they are enforced.
You should be aware that changing a host’s test beds from two to one means that it will now only be possible to assign
one test bed. So, if a host has one test bed, the test modules in the host can only be assigned to either a local controller
or a Master Controller. This is because in effect there is only a Testbed A or a Testbed B.
Note
The number of test beds configured in the Update Hosts Information section of the Test Bed Management
Hosts Information web page must correspond to the actual configuration of the installed host. Changing the
number in the Number of Testbeds drop-down list will not change the number of test beds actually installed in
the host.
In the above example Slave_1 is being changed so that it has only one test bed.
When you try and apply a change to the test modules assignment on Testbed B in Slave_1, an error appears informing
you that this is an invalid configuration.
Note
By default, there are two test beds per host. However, if the configuration of the host has been modified outside
of the web interface and only one test bed exists on the host, the second test bed in that host is greyed out in the
web interface.
A.4.1. Introduction
All of the equipment required to setup and install the TeraVM Test Bed Management solution is provided by Cobham.
This includes between 2 and 12 TVM-630 servers (using Dell PowerEdge R630), depending on requirements.
Note
The Master Server must be a TVM-630.
Figure A-11. TVM-630 Management Ethernet Port and Comms Ethernet Port
1. Select Shutdown Controller from the Admin menu in the TeraVM Java Client.
3. You are given the option to Shutdown or Shutdown And Restart (reboot).
4. Once the controller has shutdown, you can power down the Appliance.
TeraVM Access TeraVM Controller with web Controller IP Address diverAdmin diversifEye
Controller browser, and click on Utilities.
Administration
Interface
TeraVM Java TeraVM Java Client Application. Java Client username diversifEye
Client Username and password shown needed (for
for: shutdown),
otherwise N/
1. Admin Tab
A
2. Shutdown/Restart from GUI
For normal login, use username.
ESXi Host Install Appliance. Access via VGA ESXi Host IP Address root lambay3456
monitor
Hard Drive • HDD: 500GB 7.2 RPM SATA 6Gbps 2.5in cabled.
• SSD: Kingston SSDNOW E50, model:
SE50S37/480G (with caddy: 2.5" SFF Hot-Swap
SCSI/SAS/SATA Tray Caddy For Dell 0G176J)
Test Network Interface Card (options) • Broadcom 5719 QP 1Gb Network Interface Card
• Intel Ethernet I350 QP 1Gb Network Daughter Card
• Dual Port 10GBASE-T Server Adapter, Low Profile
(Intel Ethernet X540)
• Dual Port 10Gb DA/SFP+ Server Adapter, Low
Profile (Intel Ethernet X520)
• Mellanox ConnectX-4 40GbE VPI Adapter Card
(should be placed in NIC slots 3 and 1 only)