<<

Spirent TestCenter™ Virtual Hyper-V Quick Start Guide

Procedures to guide the first-time user from installation through running a simple Layer 3 traffic test in a Hyper-V Virtual Machine.

PN 71-008971 Rev A, May 2020

71- 006093 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.

2 Contents Virtual Controller Setup Hyper-V Requirements Limitations Hyper-V Network Configuration Installing Spirent TestCenter Virtual on a Hyper-V host Connect to Spirent TestCenter Port VMs using the GUI How to Contact Us

3 Virtual Controller Setup

• Refer to Spirent TestCenter™ Virtual Controller Set up Guide (DOC10606) for detailed instructions on how to set up the virtual controller. • The guide is 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, you will not be able to run tests on your virtual ports.

4 Hyper-V Requirements

Spirent TestCenter Virtual in Hyper-V requires: Hyper-V 10.0 or greater Windows 2016 or greater All power saving (SpeedStep, C1 states, etc.) and turbo boost options should be disabled on the host system. Running Spirent TestCenter with these options enabled on the host system may cause incorrect transmit and receive rates.

5 Limitations

Spirent TestCenter Hyper-V cannot be upgraded via the Spirent TestCenter GUI. Spirent TestCenter Hyper-V does not support PCI passthrough Spirent TestCenter Hyper-V does not support DPDK Stacked VLAN tags (Q-in-Q) are not supported on Hyper-V

6 Hyper-V Network Configuration

How to configure Hyper-V networking to work with Spirent TestCenter Virtual

7 Hyper-V Management Network

This is the NIC that allows access to the Spirent TestCenter Virtual VMs The Hyper-V management network must be accessible from the client PC that runs the Spirent TestCenter application The Hyper-V management network must also be able to communicate with the network where the Spirent TestCenter Virtual Controller resides

8 Hyper-V Management Network (cont.)

For the Spirent TestCenter Virtual VMs to be accessible to clients on other machines, the management network virtual switch must be configured as an External network

9 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 The firewall rules can be configured in the following path from the Windows 16 server where Hyper-V Manager is installed. \All Control Panel Items\Administrative Tools\ and Advanced Security.

10 Creating VM-to-VM Test Network

For VM-to-VM testing, a Private network test switch should be added

11 Creating Test Network on Physical NIC

To send test traffic over a physical NIC, an External network test switch should be added and the correct NIC chosen from the drop-down. The “Allow management …” checkbox should be left *UNCHECKED*.

12 Spirent TestCenter Virtual VHD Image

Download the Spirent TestCenter Virtual Hyper-V .zip file: Spirent_TestCenter_Virtual_HyperV_X.XX.XXXX.zip where X.XX.XXXX is the version number When unzipped, this .zip file contains a Spirent_TestCenter_Virtual_HyperV_X.XX.XXXX directory which in turn contains a stcv-X.XX.XXXX.vhd file. Ensure that the stcv-X.XX.XXXX.vhd file can be accessed by the Hyper-V Manager app.

13 Installing Spirent TestCenter Virtual on a Hyper-V host

14 Create Spirent TestCenter Virtual Ports Create new Virtual Machine by clicking on the New action and selecting Virtual Machine…

15 Create Spirent TestCenter Virtual Ports (cont.) Create new Virtual Machine by clicking on the New action and selecting Virtual Machine… In the New Virtual Machine Wizard, enter a name for the VM

16 Create Spirent TestCenter Virtual Ports (cont.) Specify at least 512MB of RAM for the VM. Add the management network interface.

17 Create Spirent TestCenter Virtual Ports (cont.) Choose an existing virtual hard disk and specify the stcv-X.XX.XXXX.vhd file. Click Finish.

18 Create Spirent TestCenter Virtual Ports (cont.) Select the newly created VM in the Virtual Machines list and click on

19 Create Spirent TestCenter Virtual Ports (cont.) Select Add Hardware and add a Network Adapter. Connect the newly created Network Adapter to the test network interface

20 Configure Network Adapter

Check the Enable MAC address spoofing option, in the Network Adapter Advanced Features section, to support sending packets with MAC addresses other than the NIC’s.

21 Configuring a Spirent TestCenter Virtual Controller

Select the STCv VM and click Start. Click Connect… to launch the console.

22 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 (or an IPv6 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.

23 Spirent TestCenter Virtual Admin Commands

Address Mode – uses DHCP or static IP for the STCv VM mode IPv6 Address Mode – uses DHCP, static, or SLAAC IP for the STCv VM ipv6mode IP Address – the IP address of the STCv VM (if mode is DHCP, this is automatically set) ipaddress IPv6 Address – the IPv6 address of the STCv VM (if mode is DHCP, this is automatically set) ipv6address IPv6 Prefix Length – the prefix length of the IPv6 address for the STCv VM ipv6prefixlen i.e. 64 IPv6 Gateway – the IPv6 gateway for the STCv VM (if mode is DHCP, this is automatically set) ipv6gwaddress Netmask - the netmask of the STCv VM (if mode is DHCP, this is automatically set) Netmask

24 Spirent TestCenter Virtual Admin Commands (cont.)

Gateway - the gateway for the STCv VM (if mode is DHCP, this is automatically set) gwaddress NTP Server – the IP address of the NTP server used to synchronize the VM instances ntp 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 Speed – the interface port speed that the STCv VM will support. Speed <100M | 1G | 10G | 40G> Promiscuous Mode – enables all traffic to be received regardless of MAC address Promisc

25 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 management port IP, make sure you use the Hyper-V 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.

26 Connect to Spirent TestCenter Port VMs using the GUI Launch a compatible Spirent TestCenter GUI version Add the IP addresses of the VMs Select the STCv ports and reserve them

27 How to Contact Us

• To obtain technical support for any Spirent Communications• The Spirent Customer Service Center product, please contact our Support Services department (https://support.spirent.com) is designed to serve your using any of the following methods: technical information needs. The Knowledge Base • Americas includes an easy-to-use browse mode and an intelligent search. • E-mail: [email protected] • Web: https://support.spirent.com • Toll Free: +1 800-SPIRENT (+1 800-774-7368) (North America)• Information about Spirent Communications and its products and services can be found on the main company • Phone: +1 818-676-2616 website at http://www.spirent.com • Hours: Monday through Friday, 05:00 to 17:00, Pacific Time • Europe, Middle East, Africa • Company Address • E-mail: [email protected] • Spirent Communications, Inc. • Web: https://support.spirent.com 27349 Agoura Road • Phone: +33 (1) 6137 2270 (France) Calabasas, CA 91301 USA • 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