Installing diversifeye on Linux KVM Hypervisors Setup and Configuration Guide

Transcription

1 diversifeye N ETW O R K T EST S YST E MS Installing diversifeye on Linux KVM Hypervisors Setup and Configuration Guide

2 S /W V E R S IO N 8. 3 Page ii of 22 Revision 2.0 Confidential Draft

3 Copyright Copyright 2012 Shenick Network Systems Limited. All rights reserved, subject to change without notice. The material contained in this document is for general information purposes only and does not constitute technical or professional advice. diversifeye and serviceye are trademarks of Shenick Vendor Trademarks diversifeye and serviceye are registered trademarks of Shenick Network Systems Ltd. Adobe, the Adobe logo, and the HTTP Dynamic Streaming logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Silverlight is a registered trademark of the Microsoft group of companies. Microsoft, Windows and Windows NT are trademarks of Microsoft Corporation in the United States, other countries or both. The term "Linux" is a registered trademark of Linus Torvalds, the original author of the Linux kernel.

4

5 Table of Contents Copyright... i Vendor Trademarks... i Table of Contents... i Audience... 1 Further Reading... 1 Deploying diversifeye on Linux KVM Hypervisors... 2 diversifeye Distributed Deployment... 2 Prerequisites to Staging KVM Environment vswitches... 2 System Requirements... 3 Installing CentOS and KVM... 3 Install CentOS Prepare the KVM Environment... 4 Installing Fedora and KVM... 5 Install Fedora Prepare Your KVM Environment... 6 Installing diversifeye on a KVM... 8 Create the Virtual Switches... 8 Import the diversifeye OVA/OVF (Create the VMC)... 9 Install the diversifeye RPM Configure the VMC for the Test Blades Deploy the VMPP Import the XML Files to the KVM Validating the Configuration Sample network-scripts Interface Configurations Configuring Virtual to Physical Interfaces Physical Test Ports Internal VM to VM Bridges: Scripts to Bridge a Physical NIC to Manage VMs and KVM Hypervisor Original ifcfg script (ifcfg-em3)

6 Bridge configuration (ifcfg-vmnet) Scripts to Bridge a Physical NIC Test Port to Virtual Ports on VMPP Bridge configuration (ifcfg-10g0): Scripts for Internal Loopbacks (diversifeye_backplane and test blades) Page ii of 22 Revision 2.0 Confidential Draft

7 S C O P E Scope This Shenick Network Systems Internal Sales Engineer installation guides describe how to install diversifeye on different hypervisors: VMware ESX, Citrix Xen, KVM, and Microsoft Hyper V. This guide describes a diversifeye KVM hypervisor installation. Shenick does not endorse any one hypervisor over another. Audience It is assumed that readers of this document have a working knowledge of virtual machines and diversifeye configurations. Further Reading The following documents provide further reference material when using diversifeye: diversifeye Getting Started Guide ( diversifeye User Guide ( 1

8 Deploying diversifeye on Linux KVM Hypervisors This document describes installing diversifeye on Linux KVM hypervisors. This document is written for a Fedora 17 operating system KVM. diversifeye Distributed Deployment A diversifeye distributed deployment has diversifeye deployed on a hypervisor as a virtual master controller (VMC), using a virtual switch as the backplane, and one or more virtual switches as test blades or packet processors (pp). Use this type of deployment for testing multiple individual flows. When configuring this type of deployment, first ensure that the KVM hypervisor is properly installed on your system, then configure the KVM hypervisor and prepare it for diversifeye, and finally deploy diversifeye onto the KVM hypervisor and configure the diversifeye software. Prerequisites to Staging KVM Environment vswitches Hypervisor installed with and running KVM on CentOS or Fedora 17. Latest approved diversifeye appliance Open Virtualization Archive (OVA) image. Deploying this creates the diversifeye virtual master controller (VMC). Latest release or engineering build of diversifeye RPM or upload.tgz upgrade file. Deploying this creates the virtual master packet processor (VMPP) test ports. Computer running HTTP Web Server to download diversifeye RPMs and OVA images. Page 2 of 22 Revision 2.0 Confidential Draft

9 You need to configure the following: Management network interface cards (NICs) NICs used as test ports for testing physical devices under test (DUTs) You need to create the following: An internal bridge for the diversifeye_backplane virtual switch (the diversifeye network) An internal bridge for the diversifeye_loopback test ports A bridge to the management ports A bridge to the test ports System Requirements diversifeye Distributed Deployment: VMC: 1GHz 1 x CPU core and 1GB Memory VMPP: 1GHz 1 x CPU core and 1GB Memory diversifeye Virtual Appliance Deployment: VMAPP: 2GHz x 2 CPU core and 2GB Memory Installing CentOS and KVM Before you begin, get the name of the LAN network interface (for example, Em1) and ensure that you have Internet connectivity. Install CentOS Insert the CentOS CD into the drive and follow the installation wizard: a. Installation Type: Select Install. b. Disk Test: Skip. c. Language: Set appropriately. d. Storage: Select Basic Storage. e. Name and Location: Name the server (for example, Shenick KVM). f. Timezone: Set appropriately. g. Password: Set appropriately. h. Installation Type: Select Use All Space. i. Writing storage configuration to disk: Select Write changes to disk. j. Additional software to install: Accept Minimal and click Customize Now. 2. For the Customize Now options, select and customize the following at a minimum: a. Base System: Select Base, Networking Tools, and Performance Tools. b. Desktops: Select KDE Desktop, X Window System, and Graphical Administration Tools. c. Servers: Select System Administration Tools, Server Platform, and FTP Server. d. System Management: Select System Management.

10 e. Virtualization: Select Virtualization (also Optional Package qemu-kvm-tools EL6.X86), Virtualization Client, Virtualization Platform (also Optional Package all libvirt options), and Virtualization Tools. Click Finish. The installation takes between five and ten minutes. 3. Reboot. 4. Configure CentOS, accepting most defaults and setting user login credentials, date and time, and accepting the default Kdump enabled setting. When finished, reboot. Prepare the KVM Environment Before doing this, ensure that you have connectivity to the Internet. 1. Log in with the password you configured and open a terminal window by right-clicking and going to Konsole. 2. Check to see if the KVM modules loaded into Kernel (if they did not, run modprobe kvm or reboot): lsmod grep kvm kvm_intel kvm kvm_intel 3. Install KVM: yum -y install qemu-kvm libvirt python-virtinst bridge-utils 4. Start libvirtd and ensure it starts on its own when the server is rebooted: chkconfig level 345 libvirtd on service libvirtd start 5. Optional: Get rid of NetworkManager so you can control the network scripts with the network utility instead: a. Prevent NetworkManager from starting after a reboot: systemctl disable NetworkManager.service b. Set the network service to start after a reboot: systemctl enable network.service c. Shut down NetworkManager in the current session: systemctl stop NetworkManager.service d. Start the network service in the current session: systemctl start network.service 6. Configure bridge networking. Change directories: cd /etc/sysconfig/network-scripts 7. Create the ifcfg-vmnet file as a bridge to the physical ethernet port (for example, your VM network vswitch): vi /etc/sysconfig/network-scripts/ifcfg-vmnet DEVICE="vmnet" TYPE="Bridge" BOOTPROTO="dhcp" Page 4 of 22 Revision 2.0 Confidential Draft

11 DELAY="0" NM_CONTROLLED="no" 8. Configure the LAN network interface (get which device to configure from the customer; for example Em1). While still in the /etc/sysconfig/network-scripts directory, run these commands, ensuring the BRIDGE entry: vi /etc/sysconfig/network-scripts/ifcfg-em3 DEVICE="em3" NM_CONTROLLED="no" BOOTPROTO="none" HWADDR="00:23:7D:DC:0F:FC" BRIDGE="vmnet" 9. Set up the internal bridge (for example, diversifeye control backplane or internal loopback) by creating a new file: vi /etc/sysconfig/network-scripts/ifcfg-divctl NM_CONTROLLED="no" BOOTPROTO="none" IPADDR=" " DEVICE="divctl" TYPE="Bridge" IPV6INIT="no" USERCTL="no" PREFIX="8" 10. Reboot the server and review the network settings: brctl show bridge name bridge id STP enabled interfaces 10g no <===Physical 10G interface 0 10g no <===Physical 10G interface 1 divctl no <===Internal loopback diveye control1 divctl no <===Internal loopback diveye control2 loopback no virbr c278 yes virbr0-nic <===Default bridge vmnet ddc0ffc no em3 <===VM network tied into physical port Installing Fedora and KVM Before you begin, get the name of the LAN network interface (for example, Em1) and ensure that you have Internet connectivity. Versions of the installed software packages that build a KVM-based Hypervisor with no issues: Linux Distro Used: Fedora 17 Linux Kernel Version: fc17.x86_64 Python Version: Python Virsh version (Command line based VM Manager): libvirt version: libvirtd (libvirt) QEMU version (Hardware Emulator): QEMU emulator version 1.0,1 (qemu-kvm ), Copyright (c) Fabrice Bellard

12 bridge-utils version (Linux Bridge Networking) : bridge-utils, 1.5 virt-manager version (GUI based VM Manager utility): Virtual Machine Manager Install Fedora 17 We recommend a clean install. You can download the Fedora 17 installer from the Burlingame File Server at the following directory: /opt/vm/hypervisors/fedora Configure the installer to suit your needs; for example, choose XFCE, LXDE, Gnome for your desktop if you'd like to use the virt-manager graphical user interface (GUI). When you reboot your system, ensure that you have all virtualization options enabled in your BIOS. After you finish the Fedora 17 installation, run the yum update command to update all software. Prepare Your KVM Environment 1. Install KVM: yum -y install qemu-kvm libvirt python-virtinst bridge-utils 2. Check to see if KVM modules loaded into Kernel (if they did not, run modprobe kvm or reboot): lsmod grep kvm kvm_intel kvm kvm_intel 3. Start libvirtd and ensure it starts on its own when the server is rebooted: systemctl start libvirtd.service chkconfig libvirtd on 4. Optional: Get rid of NetworkManager so you can control the network scripts with the network utility instead: a. Prevent NetworkManager from starting after a reboot: systemctl disable NetworkManager.service b. Set the network service to start after a reboot: systemctl enable network.service c. Shut down NetworkManager in the current session: systemctl stop NetworkManager.service d. Start the network service in the current session: systemctl start network.service 5. Configure bridge networking. Change directories: cd /etc/sysconfig/network-scripts 6. Create the ifcfg-vmnet file as a bridge to the physical ethernet port (for example, your VM network vswitch): vi /etc/sysconfig/network-scripts/ifcfg-vmnet DEVICE="vmnet" Page 6 of 22 Revision 2.0 Confidential Draft

13 TYPE="Bridge" BOOTPROTO="dhcp" DELAY="0" NM_CONTROLLED="no" 7. Configure the LAN network interface (get which device to configure from the customer; for example Em1). While still in the /etc/sysconfig/network-scripts directory, run these commands, ensuring the BRIDGE entry: vi /etc/sysconfig/network-scripts/ifcfg-em3 DEVICE="em3" NM_CONTROLLED="no" BOOTPROTO="none" HWADDR="00:23:7D:DC:0F:FC" BRIDGE="vmnet" 8. Set up the internal bridge (for example, diversifeye control backplane or internal loopback) by creating a new file: vi /etc/sysconfig/network-scripts/ifcfg-divctl NM_CONTROLLED="no" BOOTPROTO="none" IPADDR=" " DEVICE="divctl" TYPE="Bridge" IPV6INIT="no" USERCTL="no" PREFIX="8" 9. Reboot the server and review the network settings: brctl show bridge name bridge id STP enabled interfaces 10g no <===Physical 10G interface 0 10g no <===Physical 10G interface 1 divctl no <===Internal loopback diveye control1 divctl no <===Internal loopback diveye control2 loopback no virbr c278 yes virbr0-nic <===Default bridge vmnet ddc0ffc no em3 <===VM network tied into physical port 10. Check the network configuration: Ifconfig

14 Installing diversifeye on a KVM Create the Virtual Switches Import the diversifeye OVA/OVF (Create the VMC) Install the diversifeye RPM Configure the VMC for the Test Blades Deploy the VMPP Import the XML Files to the KVM Before you install diversifeye on the KVM, prepare the system: Obtain the diversifeye OVA file Obtain an IP address, Netmask, and Gateway for the VMC Obtain a location on the target system for the KVM files Create the Virtual Switches Create two virtual switches using the KVM command line: 1. Go to /etc/sysconfig/network-scripts and use vi to create the backplane switch (name the switch ifcfg-divctl): vi ifcfg-divctl Add the following lines to the file you just created and then save the file: NM_CONTROLLED="yes" BOOTPROTO="none" IPADDR=" " DEVICE="divctl" TYPE="Bridge" IPV6INIT="no" USERCTL="no" PREFIX="8" 2. Repeat to create the loopback switch (change DEVICE value): vi ifcfg-loopback NM_CONTROLLED="yes" BOOTPROTO="none" IPADDR=" " DEVICE="loopback" TYPE="Bridge" IPV6INIT="no" USERCTL="no" PREFIX="8" 3. Restart the bridges: service network restart Page 8 of 22 Revision 2.0 Confidential Draft

15 Import the diversifeye OVA/OVF (Create the VMC) Importing the diversifeye OVA creates the virtual master controller (VMC). Before importing the OVA, obtain the OVA zip file, install it locally, and un-compress it to reveal one image file and one XML file. 1. Obtain the OVA file from the Burlingame server in this directory: /opt/vm/templates/kvm 2. Un-compress the zip file to /home/kvm/images on the KVM into an image file and an XML file: tar xzvf <filename>.tgz 3. If needed, edit the KVM-vmc-<date> XML file, changing the source file value, to the XML file location:

16 4. Create the KVM VMC with the configurations provided in the XML file: virsh define KVM-vmc-<Date>.xml 5. Turn on the VMC: virsh start KVM-vmc-<Date> 6. Go to the VMC console to watch it boot: virsh console <VMC_ID> Exit the console by typing Ctrl+]. 7. Using the VMC console, or a new session to the VMC, and go to the directory with the license files, VMC_License.txt and VMC_Eval_License.txt: cd /etc/shenick NOTE: The KVM console can be problematic to use. Unless you have experience with the KVM console, we recommend opening a new session to the VMC using the configured IP address. Page 10 of 22 Revision 2.0 Confidential Draft

17 8. Edit the VMC_License.txt file: Enter the VMC Eth1 MAC address into the MAC1 field Enter the controller IP address to the IP1 field Save the modified file. 9. Edit the VMC_Eval_License.txt file. Change the number for license days as appropriate. For example, change the number to 365 for a year-long evaluation license. Save the modified file. Install the diversifeye RPM Before beginning this procedure, ensure that you have access (SFTP, WinScp, and so forth) to a diversifeye RPM file. 1. Using a console session to the VMC, go to the RPMS directory: cd /opt/rpms 2. Copy a diversifeye RPM into that directory using the tool of your choice. Tip: Issue the ls command and see if the file is already there. 3. Install the diversifeye RPM file with this command: rpm ivh <RPM file> Configure the VMC for the Test Blades Prepare the controller to work with the virtual test blades that you install next. 1. Using the VMC console session, make a copy of the script in the root directory and un-compress it there: cp sh_vm_install.tgz / cd / tar xzvf sh_vm_install.tgz This creates a netvmboot directory with various scripts. 2. Go to the new directory s scripts sub-directory: cd /netvmboot/scripts Find these two scripts: setup_diversifeye_feature_licenses.sh: This script sets up licenses for the diversifeye features. vm_install_script.sh: This script sets up the licensing for the test blades. 3. Modify vm_install_script.sh by un-commenting (removing the hash characters) the appropriate hypervisor lines under the Example how to install four licenses heading. Add new lines if necessary for additional test blades. Save the modified file. 4. Execute the scripts:./setup_diversifeye_feature_licenses.sh./vm_install_script.sh This creates a license card for each virtual test blade that you intend to add.

18 5. Verify the configuration. In a browser, go to <VMC IP address>/netvmboot. The page has a licenses link and a deployment files link. Deploy the VMPP Deploying the VMPP allows you to create the test blades/packet processors. 1. Go to the VMC using a browser pointed to the IP address you configured: 2. Download the KVM zip file to the KVM by clicking the link. Once it is downloaded, copy it to the KVM images directory, and un-compress it with the tar xzvf command. 3. Copy the vmpp-template.xml file for each test blade that you want, renaming the file appropriately. cp <template_name> <new_file_name>. NOTE: It is very important that you name the files with this convention: vmpp-0<number>-0.xml, and name the first file vmpp-03-0.xml. 4. Modify all of the files you just created except the vmpp-03-0.xml file as it is already configured as test blade 03. Make these changes to each file: NAME: Change this to match the vmpp name (for example, vmpp-04-0) Page 12 of 22 Revision 2.0 Confidential Draft

19 UUID: Append with the identifier for the vmpp (for example, 04) MAC address: Append with the identifier for the vmpp (for example, 11:00:04) Import the XML Files to the KVM To import the VMPP files to the KVM, use this command: virsh define <vmpp_template>.xml Validating the Configuration To validate the configuration, do the following. 1. After starting the diversifeye server in the VMC and starting your packet processor VM's, open the diversifeye client in your diversifeye server: a. Open a web browser to the VMC IP address. b. Click Download diversifeye Client. c. Once the client downloads, right-click it and go to Run as Administrator and follow the installation wizard. d. Once installation completes, go to Start > diversifeye. The default login User Name is demo and for the Server Host enter the IP address of the VMC. e. Using the KVM session window, reset the vm-pp blades by selecting each and entering virsh reset <vm-pp ID>. 2. On the Nodes tab of the diversifeye client, ensure that all of the card's (three with two interfaces per TeraVM PP, and one with four interfaces per distributed diversifeye PP) that you have configured display.

20 Sample network-scripts Interface Configurations Use examples here as references; make modifications as needed. Configuring Virtual to Physical Interfaces Use these scripts to configure the management port to manage both the KVM hypervisor server and the VMs connecting to the LAN. Original GigE ifcfg script generated from installation of Fedora 17: ifcfg-em3 Script to map the virtual port on the VMC to physical GigE port to connect VMC to the LAN: ifcfg-vmnet Physical Test Ports Original 10G ifcfg scripts generated from installation of Fedora 17: ifcfg-eth4 ifcfg-eth5 Scripts to map virtual ports on a VMPP to physical 10G ports on the server: ifcfg-10g0 ifcfg-10g1 Internal VM to VM Bridges: Configuration script for the diversifeye_backplane (divctl) bridge to connect the VMC and the virtual master packet processor (VMPP): ifcfg-divctl Configuration script for a bridge to loop back virtual test ports on the VMPP internally: ifcfg-loopback Scripts to Bridge a Physical NIC to Manage VMs and KVM Hypervisor In the following script examples, italicized text indicates variables. Bold text indicates new items that must you must add to existing ifcfg configuration files. Original ifcfg script (ifcfg-em3) This script is included with the Fedora 17 operating system. DEVICE="em3" UUID="037c a-4c80-97c1-888ced58d531" NM_CONTROLLED="no" BOOTPROTO="static" IPADDR=" " (Static IP Address to manage server) NETMASK=" " (Netmask for server IP) GATEWAY=" " (Gateway for server IP) HWADDR="00:23:7D:DC:0F:FC" (MAC address of port must match the MAC on the physical Interface!) Page 14 of 22 Revision 2.0 Confidential Draft

21 DNS1=" " (DNS server configuration) DOMAIN="us.shenick.com" (domain configuration) TYPE="Ethernet" IPV6INIT="no" USERCTL="no" PREFIX="24" BRIDGE="vmnet" (ADD THIS! Must match the name of the bridge used for the VM network.) Bridge configuration (ifcfg-vmnet) You must create this file. After the server is rebooted, you can manage your KVM hypervisor server and virtual machines (VMs) through this interface. You can use vi ifcfg-vmnet and copy and paste the following: DEVICE="vmnet" TYPE="Bridge" BOOTPROTO="dhcp" DELAY="0" NM_CONTROLLED="no" Scripts to Bridge a Physical NIC Test Port to Virtual Ports on VMPP This is an example of the original ifcfg script (ifcfg-eth4, one of two 10G interface on the server). The Fedora 17 operating system includes most of these configurations. Use these guidelines to verify existing settings. UUID="0b9ef066-d654-42ef-a1a4-c9039bda0ede" NM_CONTROLLED="yes" HWADDR="00:1B:21:12:4E:79" (MAC address has to match that of the physical port) BOOTPROTO="none" (Ensure this is none ) IPADDR=" " (No IP address configuration!) DEVICE="eth4" TYPE="Ethernet" IPV6INIT="no" USERCTL="no" PREFIX="8" BRIDGE="10g0" (Add this line! Must match the bridge name used for the VM test ports)

22 Bridge configuration (ifcfg-10g0): You must create this file. Associate the VMPP vnics to this bridge to utilize the 10G ports. You can use vi ifcfg-10g0 and copy and paste the following: NM_CONTROLLED="yes" BOOTPROTO="none" DEVICE="10g0" IPADDR=" " (No IP address configuration!) TYPE="Bridge" IPV6INIT="no" USERCTL="no" PREFIX="8" Reboot the server in order for the configuration to take effect. Scripts for Internal Loopbacks (diversifeye_backplane and test blades) You can use this script to configure needed virtual switches. Ensure that: BOOTPROTO= none IPADDR= TYPE="Bridge" NM_CONTROLLED="yes" BOOTPROTO="none" IPADDR=" " DEVICE="divctl" TYPE="Bridge" IPV6INIT="no" USERCTL="no" PREFIX="8" Page 16 of 22 Revision 2.0 Confidential Draft