Embed Size (px)
Citation preview
PN 71-008968 Rev A, May 2020
Procedures to guide the first-time user from installation through running a simple Layer 3 traffic test on a VMware® ESX Server.
Spirent TestCenter Virtual™Quick Start Guide
71- 006093
2
Copyright
© 2020 Spirent Communications, Inc. All Rights Reserved.
▪ All of the company names and/or brand names and/or product names referred to in this document, in particular, the name “Spirent” and its logo device, are either registered trademarks or trademarks of Spirent plc and its subsidiaries, pending registration in accordance with relevant national laws. All other registered trademarks or trademarks are the property of their respective owners. The information contained in this document is subject to change without notice and does not represent a commitment on the part of Spirent Communications. The information in this document is believed to be accurate and reliable, however, Spirent Communications assumes no responsibility or liability for any errors or inaccuracies that may appear in the document.
3
Contents
Virtual Controller Setup
VMware vSphere Client installation
vSphere Network Configuration
Installing Spirent TestCenter Virtual on a VMware ESX Host
Configuring a Spirent TestCenter Virtual Machine
Configuring the STCv VM Multi-port Option (Portgroupsize)
Configuring STCv VM PCI Passthrough and SR-IOV
Spirent TestCenter Mini Virtual Machine
Using Spirent TestCenter GUI for STC Virtual Ports
How to Contact Us
4
Virtual Controller Setup
Refer to the following guides for detailed instructions on how to set up these types of Virtual Controllers, and how to install the Virtual Licenses on the Virtual Controllers:
• Spirent TestCenter™ Virtual Controller Set up Guide (DOC10606)
• Spirent Virtual Controller – VM (USB dongle or UUID versions) Quick Start Guide (DOC10586)
These guides are available in the Spirent TestCenter Documentation installer on the CSC/Downloads page and on the CSC/Knowledge Base (https://support.spirent.com).
Important: Without proper installation of the Virtual Controller and Virtual Licenses, you will not be able to run tests on your virtual ports.
5
VMware vSphere Client Installation
6
vSphere Client - Install
Download and Install the vSphere Client
Open the IP address of the VMware ESXi Server in a web browser, so you can download the vSphere Client
7
vSphere Client - Connection
Launch the vSphere Client and connect to the ESXi Server IP using rootand the configured password
8
vSphere Network Configuration
• How to configure vSphere networking to work with Spirent TestCenter Virtual
9
VMware Management Network
This is the NIC that allows access to the virtual machines
The VMware management network must be accessible from the client PC that runs the Spirent TestCenter application
The VMware management network must also be able to communicate with the network where the Spirent TestCenter Virtual Controller resides
The setup is done by default, when ESXi is installed
10
Creating Test Network on Physical NICConfigure the physical NIC that you want the Spirent TestCenter Virtual VMs to use
11
Creating Test Network on Physical NIC (continued)
Select the physical NIC on which you want the test traffic to be generated
Provide a meaningful label, and if you want to send VLAN traffic, set the VLAN ID to 4095 (which means all VLANs)
12
Creating Test Network on Physical NIC (continued)
The new network is shown in the vSphere Client’s Networking view
13
Creating Test Network on Physical NIC (continued)
Click the Properties tab of the newly created switch
14
Creating Test Network on Physical NIC (continued)
Click the Edit button to open a new tab; select the NIC Teaming tab, and set Notify Switches to No.
15
Creating VM-to-VM Test NetworkThis example uses two VMs connected back to back
Use the Add Networking… link on the Networking page
Step through the wizard
Make sure to uncheck the physical NIC
16
Creating VM-to-VM Test Network (continued)
The new Network is shown in the vSphere Client Networking view
17
Installing Spirent TestCenter Virtual on a VMware ESX Host
18
Spirent TestCenter Virtual Image
Download the Spirent TestCenter Virtual ESX installer for VMware Image to your PC
19
Create Spirent TestCenter Virtual Ports
Create Spirent TestCenter virtual ports by selecting Create/Register VMand choose the Spirent TestCenter ESX ova file
20
Create Spirent TestCenter Virtual Ports (continued)
The Select Storage screen provides information about how where the virtual machine will be stored
21
Create Spirent TestCenter Virtual Ports (continued)
Deployment Options: Set the Network mappings (which ports to use) for the management and test networks, disk provisioning and if to power on after the OVA has been imported
22
Create Spirent TestCenter Virtual Ports (continued)
Review the configuration and click Finish to create the VM
23
Create Spirent TestCenter Virtual Ports (continued)
Deploying your virtual portsWhen the deployment is complete, you can create new or clone existing virtual ports in the same test network.
24
Configuring a Spirent TestCenter Virtual Machine
25
Configuring a Spirent TestCenter Virtual Controller
Select the Spirent TestCenter VM, click Power On and launch the Console
Wait for the login prompt and continue to the next page
26
Spirent TestCenter Virtual Admin
Each Spirent TestCenter Virtual instance acts as a Spirent TestCenter chassis
Login: admin/spt_admin
The commands are detailed on the next page
You must complete these steps:
Configure IP Address. This address must be reachable from the PC where the Spirent TestCenter GUI resides. It can be DHCP or Statically defined.
NTP Server. For time synchronization you must point this to an NTP Server. The License server is also an NTP server and can be used.
If Performance Port was purchased, set the speed to 10G; if Functional Port was purchased, set the speed to 100M, or you can change it to 1G.
After any changes, you must issue the activate command and then reboot the Spirent TestCenter Virtual Machine.
27
Spirent TestCenter Virtual Admin Commands
Address Mode – uses DHCP or static IP for the STCv VM
mode <none | static | dhcp>
IPv6 Address Mode – uses DHCP, static, or SLAAC IP for the STCv VM
ipv6mode <none | static | dhcp | auto>
IP Address – the IP address of the STCv VM (if mode is DHCP, this is automatically set)
ipaddress <ip>
IPv6 Address – the IPv6 address of the STCv VM (if mode is DHCP, this is automatically set)
ipv6address <ipv6>
IPv6 Prefix Length – the prefix length of the IPv6 address for the STCv VM
ipv6prefixlen <prefix_length> i.e. 64
IPv6 Gateway – the IPv6 gateway for the STCv VM (if mode is DHCP, this is automatically set)
ipv6gwaddress <ipv6>
28
Spirent TestCenter Virtual Admin Commands (continued)
Netmask - the netmask of the STCv VM (if mode is DHCP, this is automatically set)
Netmask <netmask> i.e. 255.255.255.0
Gateway - the gateway for the STCv VM (if mode is DHCP, this is automatically set)
gwaddress <ip>
NTP Server – the IP address of the NTP server used to synchronize the VM instances
ntp <ip> The STC virtual controller may be used as an NTP server.
Telnet Service – enables telnet access. The default is “off” - which only allows ssh access.
Telnetd <off|on>
Portgroupsize – the number of ports per portgroup that this STCv VM will support.
Note: If more than 1 port is needed, refer to the section titled Configuring the STCv VM Multi-port Option (Portgroupsize) before changing this parameter.
portgroupsize <1 - 9>
29
Spirent TestCenter Virtual Admin Commands (continued)
Driver Mode – sockets is the default, dpdk can be chosen for performance, fast option is currently not supported.
driver <sockets | dpdk>
Notes:• dpdk requires a minimum 1G of RAM and 2 CPU cores for each test port
• dpdk limits the vmxnet3 ESXi adapter type MTU size to =< 1500 bytes
Speed – the interface port speed that the STCv VM will support.
Speed <100M | 1G | 2.5G | 5G | 10G | 25G | 40G>
Promiscuous Mode – enables all traffic to be received regardless of MAC address
Promisc <on | off>
30
Spirent TestCenter Virtual Admin Notes
Make sure you configure the Virtual Controller properly. The Spirent TestCenter port VMs cannot be reserved unless you have a Virtual Controller available with valid Spirent TestCenter Virtual Platform, Port, and Feature licenses.
If you are using DHCP to resolve the Spirent TestCenter port VM’s management port IP, make sure you use the ESXi’s STC VM console to log in as admin and note the Spirent TestCenter port VM IP addresses. You will use these IP addresses as the STCv chassis IP addresses in the Spirent TestCenter GUI.
After you make any changes to the Spirent TestCenter port VMs, you must use the commands activate and then reboot to apply the changes.
31
Configuring the STCv VM Multi-port Option (Portgroupsize)
32
Minimum CPU and Memory STCv VM requirements
STCv 5GE & higher multi-port VM (where P is the number of ports):
Memory = P * 512MB
CPU = P * 2 + 1 cores or processors (=> 2Ghz)
STCv 1GE & 2.5GE multi-port VM (where P is the number of ports):
Memory = P * 512MB
CPU = P * 2 cores or processors (=> 2Ghz)
STCv 100M multi-port VM (where P is the number of ports):
Memory = P * 512MB
CPU = P * 1 cores or processors (=> 2Ghz)
Note: If the Driver Mode is dpdk, the minimum configuration is 1G RAM and 2 CPU cores per test port.
Example - 2 10GE port configuration on one STCv VM:
Memory: 2 * 512MB = 1024MB
CPU: 2 * 2 + 1 = 5 cores or processors
33
Shut Down and Edit the STCv VMSelect and shut down the STCv VM you want to modify for multi-port operation
Right-click and select Edit Settings on the selected VM
34
Modifying the STCv VM PropertiesSelect Memory on the Hardware tab. Change the Memory Size to match your requirements.
Select CPUs on the Hardware tab. Change the Number of virtual processors to match your requirements.
35
Adding Ethernet AdaptersClick Add on the Hardware tab.
Select Ethernet Adapter and click Next.
36
Adding Ethernet Adapters (continued)Click the drop-down icon for the Type field, and select adapter type VMXNET3.
Click the drop-down icon for the Network label field. Select the appropriate Test Network that you configured in the Network section of this guide. Click Next.
37
Adding Ethernet Adapters (continued)Review your options and click Finish.
Repeat this process for each additional port you want to add to the STCv VM. Click OK to complete the VM editing process.
38
Start up and Modify the STCv PortSelect and start the STCv VM
Select the Console tab. When the STCv port is up, log in as admin / spt_admin.
39
Start up and Modify the STCv Port (continued)
Use the portgroupsize and activate commands to set the port group size
Use the reboot command to bring up the multi-port configuration
40
Configuring the STCv VM PCI Passthrough and SR-IOV
41
PCI Passthrough / SR-IOV Requirements
For PCI Passthrough:
VT-d must be enabled in the host BIOS
STCv supports PCI passthrough only with driver dpdk.
DPDK requires minimum 1G RAM and 2 CPU cores per test port. Refer to Minimum CPU and Memory STCv VM Requirements.
Use the driver dpdk, activate, and reboot commands from STCv admin CLI to set the dpdk driver.
Use Intel NICs that supports pci passthrough
For SR-IOV:
All requirements listed above for pci passthrough apply to sr-iov
Sr-iov must be enabled in the server BIOS
Use Intel X520s NIC that supports sr-iov (Refer to your VMware ESXi documentation for enabling SR-IOV on the NIC)
42
Configuring Passthrough Devices on ESXi
In the Configuration tab, click Advanced Settings. The passthrough Configuration page lists the available passthrough devices.
Click Edit.
Select the devices and click OK.
When the devices are selected, they are marked with an orange icon. Reboot for the change to take effect. After rebooting, the devices are marked with a green icon and are enabled.
43
Adding PCI Devices to Spirent TestCenter Virtual
Select the Spirent TestCenter VM and click Edit Settings.
Select the Hardware tab and click Add.
Choose PCI Device and click Next.
44
Adding PCI Devices to Spirent TestCenter Virtual (continued)
Select the Device and click Next.
If SR-IOV is enabled on the NIC, you can choose a virtual function to do sr-iov passthrough.
45
Adding PCI Devices to Spirent TestCenter Virtual (continued)
Review your options and click Finish.
Repeat this process for each additional port you want to add to the Spirent TestCenter VM.
Click OK to complete the VM editing process.
46
Spirent TestCenter Mini Virtual Machine
• Spirent TestCenter Mini is a customized VM with small memory and cpu footprint.
• It is intended for high scalability with reduced functionality and performance. The default is 1 core and 256M memory for up to 9 test ports in the VM.
• Launcher: Spirent_TestCenter_VirtualMini_ESX_4.xx.xxxx.ova
• Download the file from the CSC/Downloads page, and then refer to Installing Spirent TestCenter Virtual on a VMware ESX Host in this guide.
• Spirent TestCenter Mini has the following limitations:
• - No upgrade through GUI
• - 4000 fps transmit rate per port
• - 63 transmit and receive streams per port
• - Capture memory is 4096 bytes per port
• - Only access protocols are supported
• - Advanced features such as dpdk and passthrough are not supported
• - Recommend using only the VMXNET3 network interface
47
Using Spirent TestCenter GUI for Spirent TestCenter Virtual Ports
48
TCP/UDP ports used by the STC GUI and STCv
Ensure that the following TCP/UDP ports have been opened in any firewall between the Spirent TestCenter VM and GUI/BLL:
Ingress TCP port ranges:
▪ TCP port 40004: chassis-level
▪ TCP port 51204: port group-level
▪ TCP port 1666: for Spirent TestCenter upgrade through
STC UI (use Authentication mode to lock down this
port if required by your IT dept)
▪ TCP port 9090: for chassis controller REST API (was
used by some TEMEVA apps)
▪ TCP port 22: SSH for admin console access
Egress TCP and UDP port ranges:
▪ UDP port 123: NTP
▪ TCP ports 49100 – 65535: Ephemeral TCP/UDP port range
49
Connect to STC Port VMs using the STC GUI
Launch a compatible Spirent TestCenter GUI version
Add the chassis IP of the Spirent TestCenter Port VMs
Select the STCv ports and reserve them
50
Use Physical MAC Address on Devices
You must select the Use Source MAC address from Physical Interface option to successfully send traffic across the vSwitch. This option will populate the Source MAC from ESXi instead of STC, when you use the Start MAC Learning option below. The GUI option is shown below.
Right-click on the selected device(s) and use the Start MAC Learningoption prior to running traffic, or right-click on All Devices in the tree, and select Start MAC Learning on All Devices
51
How to Contact Us• To obtain technical support for any Spirent Communications
product, please contact our Support Services department
using any of the following methods:
• Americas
• E-mail: [email protected]
• Web: https://support.spirent.com
• Toll Free: +1 800-SPIRENT (+1 800-774-7368) (North America)
• Phone: +1 818-676-2616
• Hours: Monday through Friday, 05:00 to 17:00, Pacific Time
• Europe, Middle East, Africa
• E-mail: [email protected]
• Web: https://support.spirent.com
• Phone: +33 (1) 6137 2270 (France)
• Phone: +44 1803 546333 (UK)
• Hours: Monday through Thursday, 09:00 to 18:00, Friday,
• 09:00 to 17:00, Paris Time
• Asia Pacific
• E-mail: [email protected]
• Web: https://support.spirent.com
• Phone: +86 (400) 810-9529 (toll-free mainland China only)
• Phone: +86 (10) 8233 0033 (China)
• Hours: Monday through Friday, 09:00 to 18:00, Beijing Time
• The Spirent Customer Service Center
(https://support.spirent.com) is designed to serve your
technical information needs. The Knowledge Base gives
you access to tens of thousands of documents that help
answer your network analysis and measurement
questions.
• Information about Spirent Communications and its
products and services can be found on the main company
website at https://www.spirent.com
• Company Address
• Spirent Communications, Inc.
27349 Agoura Road
Calabasas, CA 91301
USA
