Cisco Videoscape Distribution Suite, Internet …...using Openstack, Deploying the VDS-IS Virtual Appliance without Openstack April 16, 2014 Modified the use case illustrations. Use

Cisco Videoscape Distribution Suite, Internet Streamer Virtualization GuideAugust 07, 2015

Cisco Systems, Inc.www.cisco.com

Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices.

http://www.cisco.com

http://www.cisco.com/go/offices

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to thisURL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnershiprelationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

Cisco Videoscape Distribution Suite, Internet Streamer Virtualization Guide© 2015 Cisco Systems, Inc. All rights reserved.

http://www.cisco.com/go/trademarks

C O N T E N T S

Preface v

Document Revision History v

Audience vi

Objective vi

Document Organization vi

Related Documentation vi

Obtaining Documentation and Submitting a Service Request vii

C H A P T E R 1 Introduction 1-1

Use cases 1-1

Use Case 1 - Virtualizing CDN Manager and Routing Components at Headend/Data Center 1-2

Use Case 2 - Virtualizing Content Acquirer Layer at Head-End/Data Center 1-2

Use Case 3 - Virtualizing VDS Internet Streamer at Edge POP Center 1-3

C H A P T E R 2 Installing Videoscape Distribution Suite, Internet Streamer Software Using vSphere 2-1

Software Requirements 2-1

System Requirements 2-2

Installing VDS-IS Virtual Appliance 2-2

Deploying the VDS-IS Virtual Appliance using vCenter 2-3

Deploying the VDS-IS Virtual Appliance without vCenter 2-9

Deploying the VDS-IS Virtual Appliance using PowerCLI 2-14

Replacing Virtual Machines across OVA Releases 2-15

Replacing a CDSM 2-15

Replacing an Internet Streamer 2-16

Replacing a Service Router 2-17

Tuning the Performance of VDS-IS in VMWare 2-18

Upgrade Procedure 2-19

C H A P T E R 3 Installing Videoscape Distribution Suite, Internet Streamer Using NAS 3-1

Introducing NAS Based Storage 3-1

Network Attached Storage 3-1

Network File System 3-2

Getting Started 3-2

iiiCisco Videoscape Distribution Suite, Internet Streamer Virtualization Guide

Contents

Hardware Requirements 3-2

Mounting an NFS Datastore 3-2

Connecting vSphere to NFS 3-3

Deploying OVA File Using NFS 3-3

C H A P T E R 4 Installing Videoscape Distribution Suite, Internet Streamer Software Using Openstack 4-1

Software Requirements 4-1

Installing VDS-IS Virtual Appliance 4-1

Deploying the VDS-IS Virtual Appliance using Openstack 4-1

Creating an Image for Openstack 4-1

Installing the image on the Openstack 4-4

Deploying the VDS-IS Virtual Appliance without Openstack 4-6

Before you Begin 4-6

Installing the VDS-IS from ISO File 4-7

Installing the VDS-IS from QCOW2 Image 4-8

Installing the VDS-IS in Expert Mode 4-9

Creating the QCOW2 image 4-9

A P P E N D I X A Troubleshooting A-1

Common Troubleshooting Scenarios A-1

Unable to deploy VM or VM is deployed but unable to power on the VM A-1

Unable to deploy VM with disk size greater than 8TB A-1

Unable to ping the external switch connected to portchannel A-2

Unable to connect even with equal number of interfaces in port channel and external switch A-2

Unable to Install VM on an external NAS storage A-2

Failed to define domain cause domain with same name already exists A-2

Failed to start domain for permission issue for disk files A-3

Troubleshooting Tips to Improve Performance A-3

Using KVM A-3

PCI pass-through / VhostNet A-3

Raw Image Format A-3

SMP IRQ Affinity Setting A-4

Using VMWare A-4

PCI Pass-through / VMNet3 for Network Interfaces A-4

SMP IRQ Affinity Setting A-4

Using CLI A-5

Using Esxtop A-5

Using vSphere A-6

ivCisco Videoscape Distribution Suite, Internet Streamer Virtualization Guide

Contents

A P P E N D I X B Commands B-1

Best Practices B-2

vCisco Videoscape Distribution Suite, Internet Streamer Virtualization Guide

Contents

viCisco Videoscape Distribution Suite, Internet Streamer Virtualization Guide

Preface

This preface describes the audience, organization and objective of the Cisco Videoscape Distribution Suite, Internet Streamer Virtualization Guide. It also references related documentation and describes how to obtain documentation and submit a service request.

• Document Revision History, page v

• Audience, page vi

• Objective, page vi

• Document Organization, page vi

• Related Documentation, page vi

• Obtaining Documentation and Submitting a Service Request, page vii

Document Revision HistoryThe Document Revision History table below records technical changes to this document.

Date Change Summary Location

August 7, 2015

Added references to VDS-IS 4.2.1 documents Preface

July 8, 2015

Added the note The max size for one virtual disk is 2T in few chapters.

Chapter 2, Chapter 3, Chapter 4

March 27, 2015

Modified the Troubleshooting Tips to Improve Performance

Using KVM,

Using VMWare

August 15, 2014

Introduced a set of instructions to install VDS-IS using Openstack.

Deploying the VDS-IS Virtual Appliance using Openstack,

Deploying the VDS-IS Virtual Appliance without Openstack

April 16, 2014

Modified the use case illustrations. Use cases

December 2013

This is the first version of this document. —

vCisco Videoscape Distribution Suite, Internet Streamer Virtualization Guide

AudienceThis publication is designed for the installer and user with a working knowledge of the Cisco Videoscape Distribution Suite for Internet Streamer (VDS-IS) software. Users of this publication might also include network administrators and other people responsible for setting up and maintaining the Content Delivery Engines (CDEs).

ObjectiveThis guide describes how to install your VDS-IS, or how to configure software features on your system. It also does not provide detailed information about commands that have been created or changed for use by the CDEs. For hardware installation information, see the hardware installation guide for your CDE. For software information, see the software configuration guide and the command reference for this release, which are listed in the “Related Documentation” section on page vi.

Document Organization

Related DocumentationThese documents provide complete information about the VDS-IS and are available from the Cisco.com

site:

• Cisco Videoscape Distribution Suite, Internet Streamer 4.2.1 Software Configuration Guide

Chapter Description

Chapter 1, “Introduction” Describes some of the use cases when virtualizing the VDS-IS software applications.

Chapter 2, “Installing Videoscape Distribution Suite, Internet Streamer Software Using vSphere”

Describes the software and system requirements for installing VDS-IS in virtualized enviornment. It also provides instructions for installing the VDS-IS software.

Chapter 3, “Installing Videoscape Distribution Suite, Internet Streamer Using NAS”

Describes the installation of VDS-IS using NAS Datastore.

Chapter 4, “Installing Videoscape Distribution Suite, Internet Streamer Software Using Openstack”

Describes the software and system requirements for installing VDS-IS in an openstack. It also provides instructions for installing the VDS-IS software without using openstack.

Appendix A, “Troubleshooting” Describes the common troubleshooting scenarios and the various ways to troubleshoot and monitor VDS-IS Virtual Machine functioning and performance.

Appendix B, “Commands” Describes the vdsis install command and the best practices to install the VDS-IS in a Virtual Machine.

viCisco Videoscape Distribution Suite, Internet Streamer Virtualization Guide

• Cisco Videoscape Distribution Suite, Internet Streamer 4.2.1 Command Reference

• Cisco Videoscape Distribution Suite, Internet Streamer 4.2.1 Alarms and Error Messages Guide

• Release Notes for Cisco Videoscape Distribution Suite, Internet Streamer 4.2.1.1

• Cisco Videoscape Distribution Suite, Internet Streamer 4.0-4.1 Software Installation Guide for non-CDEs

• Cisco Videoscape Distribution Suite, Internet Streamer Virtualization Guide

• Cisco Videoscape Distribution Suite, Internet Streamer 4.2.1 API Guide.

• Cisco Content Delivery Engine 205/220/250/420/460/470 Hardware Installation Guide

• Regulatory Compliance and Safety Information for Cisco Content Delivery Engines

• Open Sources Used in VDS-IS Release 4.2.1

You can access the software documents at the following URL:

http://www.cisco.com/en/US/products/ps7127/tsd_products_support_series_home.html

You can access the hardware documents for the CDEs at the following URL:


You can access the hardware documents for non-CDEs at the following URLs:

• Cisco UCS C200 Installation and Service Guide

http://www.cisco.com/en/US/docs/unified_computing/ucs/c/hw/C200M1/install/c200M1.html

• Cisco UCS C210 Installation and Service Guide

http://www.cisco.com/en/US/docs/unified_computing/ucs/c/hw/C210M1/install/C210M1.html

Obtaining Documentation and Submitting a Service RequestFor information on obtaining documentation, submitting a service request, and gathering additional

information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and

revised Cisco technical documentation, at the following URL:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feedand set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

viiCisco Videoscape Distribution Suite, Internet Streamer Virtualization Guide



http://www.cisco.com/en/US/docs/unified_computing/ucs/c/hw/C200M1/install/c200M1.html

http://www.cisco.com/en/US/docs/unified_computing/ucs/c/hw/C210M1/install/C210M1.html

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

viiiCisco Videoscape Distribution Suite, Internet Streamer Virtualization Guide

Cisco Videoscape Distri

C H A P T E R 1
Introduction
The Cisco Videoscape Distribution Suite, Internet Streamer (VDS-IS) is an integrated system with a network based architecture that transcends existing streaming solutions. It allows service providers to extend their video managed content to their customers' IP enabled devices such as PCs, tablets, game consoles, and Wi-Fi connected mobile phones by using sophisticated service routing and content distribution intelligence. The VDS-IS software is installed on a Cisco Content Delivery Engine (CDE) appliance as well as Cisco high performance Unified Computing System TM (Cisco UCS®) servers and blades, providing a flexible and cost effective solution to service providers who plan to build content delivery networks.

Starting from VDS-IS 3.3.0, the Cisco VDS-IS software applications are optimized to meet the cloud environment needs. The VDS-IS software applications can be fully virtualized and can operate on a cloud platform built of COTS server. Virtualizing the VDS-IS software applications, provides a scaled solution to meet the increasing demand for online video content. It provides an efficient solution to reduce the operational costs in addition to an effective model to increase streaming capacity as demand grows (Flash Crowds for Live and VOD Events).

The Cisco VDS-IS software applications can virtualize on top of VMware hypervisor and soon planned to be supported with KVM and open stack.

Virtualizing the Cisco VDS-IS software applications provide the following benefits:

• Cost reduction—Co-resident VDS-IS applications on a virtualized machine reduce hardware requirements at headend, data center and POP sites. Site requirement costs are reduced because power, temperature, and space requirements are reduced when number of servers or appliances are optimized.

• Flexible CDN deployment—A wide variety of server configurations (CPU, memory, drives) provide you with a flexible CDN deployment that meets the CDN dynamic needs (flash crowds for Live and VOD Events).

• Minimal time for deployment in the event a new server is introduced in the system..

• Ability to leverage VMware built-in capability for NAS storage extension

VDS-IS 3.3 supports VMWare, enabling virtualization on COTS hardware. Performance will vary based on hardware type and resource allocation to VDS-IS applications.

Use casesThis section describes some of the use cases when virtualizing Cisco VDS-IS software applications.

1bution Suite, Internet Streamer Virtualization Guide

Chapter 1 Introduction

Use Case 1 - Virtualizing CDN Manager and Routing Components at Headend/Data Center

In this use case, a Service Router (SR), and a Content Delivery System Manager (CDSM) can virtualize and co-exist on the same Server. This ensures a reduction in cost and site requirements such as: power, space, temperature and so on. In a scenario that a N+1 redundancy is applied, the cost saving is higher.

Use Case 2 - Virtualizing Content Acquirer Layer at Head-End/Data Center

In this use case, a Content Acquirer (CA) can virtualize at the head-end or data center. In addition, it can leverage a remote storage NAS unit for expanding the storage size needed at the content acquirer layer

VM1 - SR VM1 - CDSM 3818

92

Cisco UCS Blade Systems

3818

93

VM1 - CA1NAS Storage

VM2 - CA2


Head-End or Data Center

2Cisco Videoscape Distribution Suite, Internet Streamer Virtualization Guide


Use Case 3 - Virtualizing VDS Internet Streamer at Edge POP Center

In this use case, VDS-IS can be virtualized at Edge POP centers, thus enabling the service providers to use the POP center compute resource for CDN video content delivery in addition to other virtualized applications. This common infrastructure can provide wide flexibility and short operation time during flash crowds for Live and VOD Events.

Note The external virtualized NAS storage unit can also be leveraged to extend the storage size of the virtual streamers at the edge. This ensures an efficient model to increase streaming capacity and storage needs.

3818

94

VM1 - VStreamer 1 VM2 - VStreamer 2 VM3 - VStreamer 3


National & Regional Data Center





C H A P T E R 2
Installing Videoscape Distribution Suite, Internet Streamer Software Using vSphere
This chapter describes the software and system requirements for installing Videoscape Distribution Suite, Internet Streamer (VDS-IS) in virtualized enviornment. It also provides instructions for installing the VDS-IS software.

Starting from 3.3 release, the VDS-IS software can be installed using Open Virtual Appliance (OVA).

Note It is not recommended to change the OVA properties manually during the installation process. If you want to change it, be aware that the max size of one virtual disk is 2T.

Software RequirementsThe following are requirements to deploy VDS-IS in a virtualized environment:

• Device Mode: Streaming Engine (SE), Service Router (SR), Content Delivery Service Manager (CDSM)

• Virtualization Software: ESXi 5.1, vSphere 5.x, vCenter 5.x

• Images: Open Virtual Appliance (OVA), Ruby.bin, Mfg/Rescue CDROM iso

The VDS-IS virtual appliance is supported for production use on VMware ESXi 5.1 and can be accessed or managed using vSphere client of VMware. The VDS-IS virtual appliance is installed using the Open Virtualization Format (OVF) package.

Connecting through vCenter provides more capabilities than connecting directly to ESXi. A vCenter server that is available and associated with the ESXi installation will be used during installation.

2-1bution Suite, Internet Streamer Virtualization Guide

Chapter 2 Installing Videoscape Distribution Suite, Internet Streamer Software Using vSphereSystem Requirements

System RequirementsTable 2-1 consists of multiple profiles that are part of the OVA, planned on specific products namely the Streaming Engine, Service Router, and Content Delivery System Manager.

Installing VDS-IS Virtual ApplianceThis section explains the procedures to deploy VDS-IS using vCenter, without using vCenter, and with Power CLI scripts.

Table 2-1 System Requirements

VM Products Cores RAM Disk Size Number of Disks Network

Streaming Engine

Content Acquirer - low-end

8 28 GB 8 x 1 TB Ten 10GEth

Content Acquirer - medium-end

16 28 GB 80 GB 8 x 1 TB Ten 10GEth

Content Acquirer - high-end

16 56 GB 80 GB 8 x 1 TB Ten 10GEth

SE-VOD - 1.5TB 8 14 GB 80 GB 6 x 256 GB Ten 10GEth

SE-VOD - 4TB 16 28 GB 80 GB 8 x 512 GB Ten 10GEth

SE-VOD - 8TB 16 28 GB 80 GB 8 x 1 TB Ten 10GEth





SE-LIVE - low-end 8 56 GB 80 GB 512 GB Ten 10GEth

SE-LIVE - medium-end

16 56 GB 80 GB 512 GB Ten 10GEth

SE-LIVE - high-end 16 112 GB 80 GB 512 GB Ten 10GEth

Service Router

SR 8 14 GB 80 GB — Ten 10GEth

Content Delivery System Manager

CDSM 8 14 GB 80 GB — Ten 10GEth

2-2Cisco Videoscape Distribution Suite, Internet Streamer Virtualization Guide

Chapter 2 Installing Videoscape Distribution Suite, Internet Streamer Software Using vSphereInstalling VDS-IS Virtual Appliance

Deploying the VDS-IS Virtual Appliance using vCenter

Note Before deploying the virtual appliance, verify that your VMware server is running on VMware supported hardware. If you are not sure whether your environment can support a 64-bit guest operating system, you can verify by downloading and running the VMware “CPU Identification Utility” which indicates 64-bit VMware support. This utility can be found on the VMware site at: http://www.vmware.com/download/shared_utilities.html

Note It is assumed that you are familiar with VMware VSphere software

To install the VDS-IS virtual appliance, you must first download the correct installation file namely cdsis_4_0_rel_01.ova.

Before you install a Cisco VDS-IS local virtual appliance you must identify the IP address of the regional cluster to which it will connect to receive the license information.

Using vSphere, connect directly to the ESXi installation or the vCenter server, and select the ESXi installation where the OVA is to be deployed.

If you have a vCenter server available, you can connect the ESXi hypervisor to your existing vCenter server and manage it through that vCenter server. Managing all your VMware hypervisors through a common vCenter server provides many benefits.

To deploy VDS-IS Virtual Appliance using vCenter:

Step 1 From vSphere menu, choose File > Deploy OVF Template.

The Deploy OVF Template Source page appears.


http://www.vmware.com/download/shared_utilities.html


Figure 2-1 Deploy OVF Template Source Page

Step 2 To import the OVA file from hard disk, click Browse and choose the OVA file (.ova) available in the local machine where the vSphere is running, cdsis_4_0_rel_01.ova in the directory in which you unzipped the file earlier. You can also enter a URL to download and install the OVA package from the internet.

Note You cannot browse for URLs and you must enter the full path to the .ova file.

Step 3 Click Next.

The OVF Template Details page appears. It displays the product name, the size of the OVA file, and the amount of disk space that needs to be available for the virtual appliance.

Step 4 Verify the OVF template details and click Next.

The End User License Agreement page appears.

Step 5 Accept the End User License Agreement.

The Name and Location page appears.



Figure 2-2 Name and Location Page

Step 6 Enter the name of the new virtual appliance. If you are using vCenter to manage the virtual machine, you have the option of selecting the location of the inventory too. Click Next to continue.

The default name is generic. You may want to change it to something more specific, such as VDS-IS 3.3 Local or VDS-IS 3.3 Regional.

Note You can change the name of the virtual machine running the virtual appliance after the virtual appliance is deployed. However, while the name of the virtual machine will change, the original name (entered in Step 6) continues to be used as the location of the disk files that describe the virtual machine. Thus, confusion may arise in the future as whatever name you enter on this page remains for the life of the virtual machine and the virtual machine name and the disk file names will differ. Thus, choosing a descriptive name now that you will not need to change later will provide some benefits in maintainability of this installation.

Step 7 From the Configuration drop-box, select the device mode or the device profile.



Figure 2-3 Deployment Configuration Page

Step 8 Choose the destination host on which you want to deploy the virtual machine and click Next.

The Storage page appears.

Figure 2-4 Storage Page

Step 9 Select the storage datastore to install the VM on and click Next to continue.

The Disk Format page appears.



Figure 2-5 Disk Format Page

Step 10 Choose the Thick Provision Eager Zeroed format. Click Next to continue.

Note It is recommended that you choose Thick Provision Eager Zeroed format.

The Network Mapping page appears.

Figure 2-6 Network Mapping Page

Step 11 Select the Network for each adapter of the VM. Click Next.



Note Different adapters can be put into different networks.

The Properties page appears.

Figure 2-7 Properties Page

Step 12 Enter the following details as required:

Note These values are optional and can be configured later.

These properties can also be set in the configuration mode as shown in Step 18 below.

• Host name: The hostname of a device can be set before powering on the device.

• Management Role: Sets the CDS-IS Management role (only needed in CDS-IS Management mode)

• Set Primary Interface: Select this checkbox if you want the VDS-IS to use the interface details which you provide in the CDSM IP field.

Note The primary interface cannot be assigned if the interface is configured for DHCP. This interface is used only with static IP address.

Note The customized values chosen in Step 8 will be used to set VM configuration only at first boot of the VM. These values will not be used to overwrite the configuration during successive reboots.

• CDSM IP: Enter the IP address.

• Networking Parameters



Note The IP address, subnet and gateway can be configured for each interface. If these details are not entered the details provided by DHCP server are used.

Step 13 Verify the options in the Ready to Complete page, then click Finish to start the deployment.

This will create the VM.

Step 14 Right-click the virtual appliance, and choose Power > Power On. The virtual appliance console appears.

Step 15 Right-click the virtual appliance, and select the Open Console and login to the VM using the user admin with the password default.

Step 16 Select the Open Console and login to the VM using the user admin with the default password.

Step 17 Change the prompt to configuration mode using the following commands.

SE# configure

SE(config)#

Step 18 Run the following commands in the configuration mode. In case the properties from Step 12 are not set they can be reset using the configuration mode.

• To configure interface IP address:

SE(config)# ip address <ip> <subnet>

• If you want to use DHCP addresses, enter the following command:

SE(config)# ip address dhcp client-id <id>

• To configure default gateway:

SE(config)# ip default gateway <ip>

You must ensure that the default gateway is reachable.

• To configure CDSM IP address:

SE(config)# cdsm ip <ip>

• To enable Centralized Management System (CMS):

SE(config)# cms enable

The configuration is complete. You can launch the VDS-IS through web interface.

Deploying the VDS-IS Virtual Appliance without vCenterTo deploy VDS-IS Virtual Appliance without vCenter:







Step 3 Click Next.




Step 5 Accept the End User Licensing Agreement.

The Name and Location page appears




Step 6 Enter the name of the new virtual appliance. If you are using vCenter to manage the virtual machine, you have the option of selecting the location of the inventory too. Click Next to continue.

The default name is generic. You may want to change it to something more specific, such as VDS-IS 3.3 Local or VDS-IS 3.3 Regional.

Note You can change the name of the virtual machine running the virtual appliance after the virtual appliance is deployed. However, while the name of the virtual machine will change, the original name (entered in Step 6) continues to be used as the location of the disk files that describe the virtual machine. Thus, confusion may arise in the future as whatever name you enter on this page remains for the life of the virtual machine and the virtual machine name and the disk file names will differ. Thus, choosing a descriptive name now that you will not need to change later will provide some benefits in maintainability of this installation.

The Deployment Configuration page appears.




Step 7 From the Configuration drop-box, select the device mode or the device profile.


Figure 2-10 Disk Format Page

Step 8 Choose the Thick Provision Eager Zeroed format.

Note It is recommended you choose Thick Provision Eager Zeroed.





Step 9 Select the Network for each adapter of the VM. Click Next.


Step 11 Finish and deploy the OVA. This will create the VM.

Step 12 Power on the virtual machine by right-clicking the virtual appliance and choosing Power > Power On.

The virtual appliance console appears.

Step 13 Select the Open Console and login to the VM using the user admin with the default password.

Step 14 Change the prompt to configuration mode using the following commands.

SE# configure

SE(config)#

Step 15 Run the following commands in the configuration mode.

• To configure interface IP address:

SE(config)# ip address <ip> <subnet>

• If you want to use DHCP addresses, enter the following command:

SE(config)# ip address dhcp client-id <id>

• To configure default gateway:

SE(config)# ip default gateway <ip>

You must ensure that the default gateway is reachable.

• To configure CDSM IP address:

SE(config)# cdsm ip <ip>

• To enable Centralized Management System (CMS):


The configuration is complete. You can launch the VDS-IS through web interface.



Deploying the VDS-IS Virtual Appliance using PowerCLIThe PowerCLI script can be used to customize the virtual machine properties. The following example sets the Device Mode to SE.

#Sample Script for setting OVA properties##

Function Wait-vShieldBoot {do {

$VM = Get-VM $VosHostNameSleep 5

} until ($VM.ToolsStatus -eq "toolsOK")

}

$Newproperty = New-VIProperty -Name ToolsStatus -ObjectType VirtualMachine -Value {param($vm)$vm.ExtensionData.Guest.ToolsStatus

} -Force## Set parameters#

$VosOVA = "C:\Users\bhagatyj\Documents\work\vmware\packaging\ovfs\vos_ovf.ova"$VosHostName = "Vos-120"$vShieldFQDN = "vshield.virtu-al.local"$VosDS = "phy-ds-2"$VosUser = "admin"$VosPass = "default"$vCenter = "deming-vc.cisco.com"$vcUsername = "root"$vcPass = "vmware"

## Execution starts here#

Write-Host "Connecting to vCenter"$Connect = Connect-VIServer $vCenter -User $vcUsername -Password $vcPass

Write-Host "Importing the OVF file"$va = Import-VApp -Name $VosHostName -Datastore $VosDS -VMHost bhagatyj-ucs2.cisco.com -Source $VosOVA$vm = Get-VM -Name $VosHostName$spec = New-Object VMware.Vim.VirtualMachineConfigSpec$spec.VAppConfig = New-Object VMWare.Vim.VmConfigSpec$newProp = New-Object VMWare.Vim.VAppPropertySpec$newProp.Operation = "edit"$prop = $vm.ExtensionData.Config.VAppConfig.Property | where {$_.Id -eq "devicemode"}$prop.Value = "se"$newProp.Info = $prop$spec.VAppConfig.Property += $newProp$vm.ExtensionData.ReconfigVM($spec)Write-Host "Starting the vShield VM"$Start = Start-VM $VosHostName -Confirm:$false

#Write-Host "Waiting until the vShield VM has started"#Wait-vShieldBoot

Write-Host "Configuration Complete"


Chapter 2 Installing Videoscape Distribution Suite, Internet Streamer Software Using vSphereReplacing Virtual Machines across OVA Releases

Replacing Virtual Machines across OVA ReleasesThe OVA file contains the hardware definition of the VM. Under certain circumstances, the hardware definition could change from one software release to another. For example, the pre-beta OVA defines two hard disks whereas the beta OVA defines four hard drives.

For new releases, software is released both in OVA and image (ruby.bin) formats. The OVA should be used for new VM deployment and the image format should be used for upgrading existing VMs. However, if the OVA's hardware definition has changed in a particular release and you would like to move to the newer definition, you should follow the steps in the Cisco Videoscape Distribution Suite, Internet Streamer 4.0 Software Configuration Guide under sub-section "Replacing a Device" in the section "Maintaining the VDS-IS".

This section has the following sub sections:

• Replacing a CDSM, page 2-15

• Replacing an Internet Streamer, page 2-16

• Replacing a Service Router, page 2-17

Replacing a CDSMTo replace a CDSM in a CDS, the new CDSM must be added into the network as a standby CDSM. For procedural information, see the "Configuring Primary and Standby CDSMs" topic in VDS-IS configuration guide.

Note • After the standby CDSM has been added, wait at least two polling intervals (10 minutes) for the databases to synchronize before the upgrade procedure can begin.

• After the standby CDSM is activated using the primary CDSM web interface and the device is shown as online in the Devices Table page, wait at least two polling intervals (10 minutes) before changing roles to ensure that the standby CDSM has a record of the most recent configuration changes.

To promote the standby CDSM to primary, first stop the primary CDSM using the cdsm role standby command. For procedural information, see the "Configuring Primary and Standby CDSMs" topic in the VDS-SE configuration guide.

After the primary CDSM has been stopped, and the standby CDSM has taken the role of primary, wait at least two polling intervals (10 minutes) before logging in to the new primary CDSM. The new primary CDSM is accessible by entering the IP address of the CDSM with port 8443 in a web browser. For example, if the IP address of CDSM is 192.168.0.236, enter https://192.168.0.236:8443.

It is now safe to deactivate the old primary CDSM in the CDSM web interface and remove it from the CDS network.

Note Do not try to take a backup of the old CDSM database and restore it on the new CDSM. This may lead to problems.



Replacing an Internet StreamerTo replace an IS, do the following:

Step 1 Open an SSH session to the device being replaced.

Step 2 In global configuration mode, enter the no cms enable command to disable CMS on the device that needs to be replaced.

SE# configure

SE(config)# no cms enable

Step 3 From the CDSM, choose Devices > Devices > Device Activation. The Device Activation page is displayed.

Step 4 Uncheck the Activate check box and click Submit. The page refreshes and displays a Replaceable check box.

Step 5 Check the Replaceable check box and click Submit.

Step 6 Choose System > Configuration > System Properties. The System Properties page is displayed.

Step 7 Click the edit icon next to the System.devivce.recovery.key property. The Modify Config Property page is displayed.

Step 8 In the Value field, enter a key and click Submit. The default value is default.

Follow the instructions to configure a device using the setup utility. The instructions can be found in Cisco Content Delivery Engine Hardware Installation Guide that is applicable to the device.

Note When prompted by the setup utility, configure the basic network settings.

a. Use the same hostname of the device being replaced. For example, if the old device has a hostname of "SE1," the new device must have a hostname of "SE1."

b. Configure the IP address of the CDSM in the SE.

Step 9 Open an SSH session to the new device.

Step 10 In EXEC mode, enter the cms recover identity command with the key parameter set in Step 8.

SE# cms recover identity <key>

On successful registration to the CDSM, a message similar to the following is displayed:

DT-7326-4#cms recover identity sbRegistering this node as Service Engine... Sending identity recovery request with key sb Node successfully registered with id CrConfig_291 Registration complete.

Step 11 Register the device with the CDSM by using the cms enable command in global configuration mode.

SE# configure



Step 13 Check the Activate check box and click Submit.


http://www.cisco.com/en/US/docs/video/cds/cde/cde205_220_420/installation/guide/cde205_220_420_hig.html


After a few minutes, approximately two polling intervals, the device status shows online and all configurations (delivery service assignments, programs, and so on) are the same as those on the device that was replaced.

Step 14 Once the new device is up and running, as noted by the online status, the old device can be removed from the VDS-IS network.

Replacing a Service RouterTo replace a VDS-IS, do the following:

Step 1 Open an SSH session to the device being replaced.

Step 2 In global configuration mode, enter the no cms enable command to disable CMS on the device that needs to be replaced.

SR# configure

SR(config)# no cms enable


Step 4 Uncheck the Activate check box and click Submit. The page refreshes and displays a Replaceable check box.

Step 5 Check the Replaceable check box and click Submit.

Step 6 Choose System > Configuration > System Properties. The System Properties page is displayed.

Step 7 Click the edit icon next to the System.devivce.recovery.key property. The Modify Config Property page is displayed.

Step 8 In the Value field, enter a key and click Submit. The default value is default.

Follow the instructions to configure a device using the setup utility. The instructions can be found in Cisco Content Delivery Engine Hardware Installation Guide that is applicable to the device.

Note When prompted by the setup utility, configure the basic network settings.

a. Use the same hostname of the device being replaced. For example, if the old device has a hostname of "SE1," the new device must have a hostname of "SE1."

b. Configure the IP address of the CDSM in the SE.

Step 9 Open an SSH session to the new device.

Step 10 In EXEC mode, enter the cms recover identity command with the key parameter set in Step 8.

SR# cms recover identity <key>

On successful registration to the CDSM, a message similar to the following is displayed:

DT-7326-4#cms recover identity sbRegistering this node as Service Engine... Sending identity recovery request with key sb Node successfully registered with id CrConfig_291 Registration complete.


http://www.cisco.com/en/US/docs/video/cds/cde/cde205_220_420/installation/guide/cde205_220_420_hig.html

Chapter 2 Installing Videoscape Distribution Suite, Internet Streamer Software Using vSphereTuning the Performance of VDS-IS in VMWare

Step 11 Register the device with the CDSM by using the cms enable command in global configuration mode.

SR# configure

SR(config)# cms enable


Step 13 Check the Activate check box and click Submit.

After a few minutes, approximately two polling intervals, the device status shows online and all configurations (delivery service assignments, programs, and so on) are the same as those on the device that was replaced.

Step 14 Once the new device is up and running, as noted by the online status, the old device can be removed from the VDS-IS network.

Tuning the Performance of VDS-IS in VMWareThe network interface should use VMNet3 driver for a better performance. You can reach a better performance by following the steps below. If the performance is not as you expected, you can use pass-through technology.

Note The presence of PCI NIC passthrough will prevent many commands on the virtual machine. The virtual machine cannot be restored, suspended, participate in vMotion, or does not allow screenshots to be taken.

To configure the VMXNET3 driver for a better performance, follow these steps:

Step 1 Portchannel is not required on VM, just one logic NIC on VM to vSwitch.

Step 2 Configure one Port Channel for 4 10 Gig links in vSwitch and external switch.

• Set the NIC teaming Load Balancing property to "Route based on IP Hash" in the vSwitch.

• Set the Bond Load Balancing property to "src-dest-ip" in the external switch.

Step 3 Configure txqueuelen to 10000 for the NIC inside IS:

ifconfig ethx txqueuelen 10000

To configure pass-through and furthermore, improve the performance of VDS-IS, follow these steps:

Step 1 Configure Passthrough for Network Interface

• Configure pass through devices on a Host:

– From the Inventory Panel of the vSphere Client, select a host.

– On the Configuration tab, click Advanced Settings.

The Passthrough Configuration page appears, listing all available passthrough devices.


Chapter 2 Installing Videoscape Distribution Suite, Internet Streamer Software Using vSphereUpgrade Procedure

A green icon indicates that a device is enabled and active. An orange icon indicates that the state of the device has changed and the host must be rebooted before the device can be used.

– Click Edit.

– Select the devices to be used for passthrough, and click OK.

• Configure a PCI Device on a Virtual Machine:

Note We reccomend that you add a DirectPath device to a virtual machine. This reserves memory equivalent to the memory size of the virtual machine.

– From the Inventory Panel of the vSphere Client, select a virtual machine.

– From the Inventory menu, choose Virtual Machine > Edit Settings.

– On the Hardware tab, click Add.

– Select the PCI Device, and click Next.

– Select the passthrough device to use, and click Next.

– Click Finish.

Step 2 Configure one Port Channel for 4 10 Gig links inside virtual machine and external switch.

Step 3 Configure txqueuelen to 10000 for 4 NIC inside IS:

ifconfig ethx txqueuelen 10000

Step 4 Configure SMP IRQ Affinity

• Get the IRQ for network interface:

#>cat /proc/interrupts CPU0 CPU10: 2445 0 IO-APIC-edge timer... ...56: 250906 0 PCI-MSI-edge eth0-rxtx-057: 39681 0 PCI-MSI-edge eth1-rxtx-0

• Set the SMP IRQ affinity:

#>echo 1 > /proc/irq/56/smp_affinity;#>echo 2 > /proc/irq/57/smp_affinity;... ...

Upgrade ProcedureThe process of upgrading Virtual Machines is similar to the upgrade process used in real machines in the case of minor release. The CLI "copy http install" can be used for upgrading. The CLI format is

copy http install <http-server-ip-addr> <dir-name> <filename>

Note However, there could be major releases where the OVA definition is changed. In these cases, the old VM should be removed and new VM should be deployed using the OVA.


Chapter 2 Installing Videoscape Distribution Suite, Internet Streamer Software Using vSphereUpgrade Procedure



C H A P T E R 3
Installing Videoscape Distribution Suite, Internet Streamer Using NAS
Introducing NAS Based StorageNetwork-based storage can improve availability and scalability by providing shared access to large amounts of data. This faster NAS growth is explained in part by its lower cost and its convenient file System interface, which is richer, easier to manage, and more flexible than the block-level SAN interface.

The rapid expansion of virtualization and NAS has lead to explosive growth in the number of virtual disk images being stored on NAS servers. Encapsulating file systems in virtual disk image files simplifies the implementation of features such as migration, cloning, and snapshotting, since they naturally map to existing NAS functions. In A a disk image addition, non-virtualized hosts can co-exist peacefully with virtualized ones that use the same NAS interface, which permits a gradual migration of services from physical to virtual machines.

File stored on Network Attached Storage (NAS), which we call VM-NAS, The host's hypervisor passes I/O requests from the virtual machine to an NFS. This in turn then access a disk image file stored on an external file server. The hypervisor is completely unaware of the storage architecture behind the NAS interface. NAS provides the scalability, reliability, and data mobility needed for efficient VM management.

Network Attached StorageA simple and relatively inexpensive way to add more storage to your network is to use network attached storage, also known as NAS. A NAS device is a self-contained file server that's preconfigured and ready to run. All you have to do to set it up is take it out of the box, plug it in, and turn it on.

Network-attached storage (NAS) is a dedicated hard disk storage device that is set up with its own network address and provides file-based data storage services to other devices on the network. A network-attached storage device is attached to a local area network and assigned an IP address, allowing both application programming and files to be served faster because they are not competing for processor resources.

Network-attached storage consists of hard disk storage, including multi disk RAID systems. NAS software can usually handle a number of network protocols, including Microsoft's Internetwork Packet Exchange and NetBEUI, Novell's Netware Internetwork Packet Exchange, and Sun Microsystems' Network File System.


Chapter 3 Installing Videoscape Distribution Suite, Internet Streamer Using NASGetting Started

Network File SystemThe Network File System (NFS) is a client/server application that lets a computer user view and optionally store and update file on a remote computer as though they were on the user's own computer. The user's system needs to have an NFS client and the other computer needs the NFS server. Both of them require that you also have TCP/IP installed since the NFS server and client use TCP/IP as the program that sends the files and updates back and forth.

Using NFS, the user or a system administrator can mount all or a portion of a file system. The portion of your file system that is mounted (designated as accessible) can be accessed with whatever privileges go with your access to each file (read-only or read-write).

Getting StartedThis section explains how to install the Cisco Videoscape Distribution Suite, Internet Streamer (VDS-IS) using NAS Datastore.

Hardware Requirements• ESXI 5.1

• VSphere client 5.1

• Vcenter 5.1

• NAS SERVER

• Ensure that enough disk space available for deploy OVA with NFS Data store.

• Ensure that the NFS client on the vSphere host(s) is enabled. Select ESXi-configuration-Security profile Click Properties and scroll down to the NFS client.

• Ensure that the NFS storage is configured to export a mount point accessible to the vSphere hosts on a trusted network. The user must ensure that they are using NFS over TCP rather than UDP. For example, if UDP is used, vSphere provides a descriptive message indicating that this is not possible. Similarly, when mounting a share using a version of NFS that is not version 3, vSphere also provides a descriptive message stating that this version of NFS is not supported. VMware currently supports NFS version 3 over TCP only.

• The vSphere host has root access to the Datastore

Note The vSphere host has root access to the Datastore—This is typically done on NFS servers using the no_root_squash option in the /etc/exports file. If you do not grant root access, you might still be able to mount the NFS datastore on the vSphere host. However, you will not be able to create any virtual machines on the datastore. It will fail with an unable to access file error message.

Mounting an NFS DatastoreDo the following to mount an NFS Datastore:

Step 1 Log in to VCenter or directly to the host using the VI Client.



Step 2 Select a host from the left pane, and then click the Configuration tab on the right.

Step 3 Select Storage in the left column of the center pane.

Step 4 Click the Add Storage hyperlink

Step 5 Navigate to Network File System, and click Next.

Step 6 In the Server field, enter in the server name or IP address.

Step 7 In the Folder field, enter in the folder path for the NFS share.

Step 8 Check the Mount NFS read only checkbox, if you want to mount the NFS volume as read only

Step 9 In the Datastore Name field, enter a name for the datastore and click Next.

Step 10 Click Finish.

The new NFS datastore should now appear in the Datastores view

Connecting vSphere to NFSDo the following to connect vSphere to an NFS:

Step 1 Click the ESXi Host, and select the Configuration tab.

Step 2 From the Hardware menu select Add Storage.

Step 3 Check the Network File System checkbox, to create a network file system.

The Network File System page appears.

Step 4 In the Server field, enter the server IP Address.

Step 5 In the Folder field, enter the folder that will be used as a vSphere Datastore.

Step 6 In the Datastore Name filed, enter the hostname of the NFS.

Step 7 Click Next.

Step 8 Verify the options in the Summary page, and click Finish.

The NFS datastore is created for ESXi under configuration Tab

Deploying OVA File Using NFSTo deploy VDS-IS Virtual Appliance using NFS:





Figure 3-1 Deploy OVF Template Source Page



Step 3 Click Next.


Note The max size of one virtual disk is 2T.



Step 5 Accept the End User Licensing Agreement.

The Name and Location page appears.




Step 6 Enter the name of the new virtual appliance. Click Next to continue.

The Deployment Configuration page appears.


Note The default name is generic. You may want to change it to something more specific, such as VDS-IS 3.2 Local or VDS-IS 3.2 Regional.



Step 7 From the Configuration drop-box, select the device configuration. Click Next to continue.

The Storage page appears.

Step 8 Select NAS as the destination storage for the virtual machine file. Click Next to continue.


Step 9 Choose the Thick Provision Lazy Zeroed format.

Note It is recommended you choose Thick Provision Lazy Zeroed.



Step 10 Select the Network for each adapter of the VM.

The Properties page appears.



Figure 3-5 Properties Page

Step 11 Enter the following details as required:

Note These values can be configured later, by logging into the VM.

• Host name: The hostname of a device can be set before powering on the device.

• Management Role: Sets the CDS-IS Management role (only needed in CDS-IS Management mode).

• Set Primary Interface: Select this checkbox if you want the VDS-IS to use the interface details which you provide in the CDSM IP field.

Note The primary interface cannot be assigned if the interface is configured for DHCP. This interface is used only with Static IP address.

Note The customized values chosen in Step 8 will be used to set VM configuration only at first boot of the VM. These values will not be used to overwrite the configuration during successive reboots

• CDSM IP: Enter the IP Address.

• Networking Parameters

Note The IP address, subnet and gateway can be configured for each interface. If these details are not entered the details provided by DHCP server are used.




After the VM is successfully deployed, check the whether VM (Device) is present in the VM Summary Storage page.



C H A P T E R 4
Installing Videoscape Distribution Suite, Internet Streamer Software Using Openstack
This chapter describes the software and system requirements for installing Videoscape Distribution Suite, Internet Streamer (VDS-IS) in an open stack. It also provides instructions for installing the VDS-IS software.

Starting with Release 4.0, the VDS-IS software can be installed using Open Stack.

Software RequirementsThe following are requirements to deploy VDS-IS in an open stack:

• Virtualization Software: Openstack environment, Virtual Manager

• Images: Mfg CDROM iso

• Packages: VDS-IS Cloud package

Installing VDS-IS Virtual ApplianceThis section explains the procedures to deploy VDS-IS using openstack, andwithout using openstack.

Deploying the VDS-IS Virtual Appliance using Openstack

Creating an Image for Openstack

Installing the ISO into a Virtual Image

Pre-Requisites

To install the mfg iso into an virtual image, the following conditions should be satisfied:

• Install the mfg iso image on a machine with Openstack and Virt-manager.

• A minimum disk capacity of 85GB is required.

To install the mfg iso into an virtual image, follow these steps:


Chapter 4 Installing Videoscape Distribution Suite, Internet Streamer Software Using OpenstackInstalling VDS-IS Virtual Appliance

Step 1 Create a virtual image with name and size:

$ sudo qemu-img create -f raw <image_name> <image_size>

Note • The max size of one virtual disk is 2T.

• We highly recommend that the size of the image (image_size) is bigger than 80G.

Step 2 Launch the Virtual Machine manager:

$virt-manager

Step 3 To create a new VM, click the Create icon from the Virtual Machine Manager tool bar.

The Create a new virtual machine page is displayed.

• Enter the following details as required:

– In the Name field, enter the name of the Virtual Machine.

– To install the operating system, and click the Local install media radio button.

Click Forward to continue.

• Click the Use ISO image radio button and use the Browse button to locate the iso image.

From the OS Type drop-down list, select Linux as the operating system type.

From the Version drop-down list, select Red Hat Enterprise Linux 6 as the version. Click Forward to continue.

• Enter the following details as required:

– In the Memory field, enter the memory settings.

– In the CPUs field, enter the CPU settings.

Click Forward to continue.

Note We highly recommend that you set the memory settings to 8192 MB and the CPU settings to 4.

• Click the Select managed or other existing storage radio button and use the Browse button to locate the iso image that was created in Step 1.

• Check the Customize configuration before install check box, to customize the congifuration. Click Finish.

Step 4 Customize the Virtual Machine (VM):

• From the left-panel menu, navigate to Disk 1, and enter the following details as required:

– From the Disk bus drop down list, select Virtio.

– From the Storage format drop down list, select raw.

– Click Apply.

• From the left-panel menu, navigate to NIC, and enter the following details as required:

– From the Source device drop down list, select Specify shared device name as device name.

– In the Bridge name field, enter br100 as the name of the bridge.



– From the Device model drop down list, select Virtio as the device model.

– Click Apply.

Step 5 Click Begin Installation and after the installation, shut down the Virtual Machine.

Tip If you want to see the installation process, choose View > Text Console > Serial 1 from the Virtual Machine Manager menu.

Step 6 Click the i tool from the Virtual machine manager toolbar, and from the left-panel menu, select IDE CDROM 1.

• Click Disconnect, to disconnect the CDROM.

Installing the cloudinit, puppet agent, and heat-cfntools

To install the cloudinit, puppet, and heat-cfntools packages into the image, follow these steps:

Note Installing the cloudinit, puppet, and heat-cfntools packages is optional.

Step 1 Boot the VDS-IS VM created in the “Installing the ISO into a Virtual Image” section on page 4-1.

Step 2 Configure the IP address and default gateway for the VDS-IS VM, and they should be an openstack private IP address:

(config)# interface TenGigabitEthernet 1/0 ip address <ip> <subnet_mask>(config)# ip default-gateway <ip>

Step 3 On a host machine or another VM, download the cloudpackage for VDS-IS, and put it onto a ftp server that with an openstack private IP, example 10.0.0.1.

Step 4 Enter the debug shell of the VDS-IS VM.

Step 5 Download the cloudpackage into VDS-IS VM.

Step 6 On VDS-IS VM, unpack the cloudpackage, and start the installation script

debugshell#tar xvf cloudpackage.tardebugshell#cd cloudpackagedebugshell#./install_all.sh

Step 7 On VDS-IS VM, unconfigure the IP address and default gateway:

(config)# no interface TenGigabitEthernet 1/0 ip address <ip> <subnet_mask>(config)# no ip default-gateway <ip>

Step 8 Shutdown the VDS-IS VM.

Note The puppet agent by default assumes the puppet master to have a domain name "puppet".

Therefore, to use a puppet to manage your VM, follow these steps:

• Set up a DNS server on openstack

• Add an entry for "puppet.novalocal" with the IP of puppet master.

• Set the VDS-IS VM's nameserver to be the DNS server.



However, you can use cloudinit to set the VDS-IS VM’s nameserver.

Converting image to qcow2

You can convert the image to the format qcow2 by using the following command:

$ sudo qemu-img convert -f raw -O qcow2 <image_name> <qcow2_name>

Installing the image on the Openstack

After preparing the VDS-IS image for Open stack, follow these steps:

Step 1 Upload qcow2 on the openstack:

$ glance image-create --name=<ImageName>--is-public=true --container-format=ovf --disk-format=qcow2 < <ImagePath>

Step 2 Create a VDS-IS instance:

$ nova boot --flavor <FlavorName> --image <ImageName> <InstanceName>

A VDS-IS instance will start.

Note If you want to use cloudinint, make sure that CloudInit has been installed it in your VDS-IS image and uploaded it to Glance.

• Create a Cloudinit data file:

#!/usr/bin/env bashpathofconf=/tmp/startup.configrm $pathofconfecho "cloud init script running"#Writing to StartUp Config filecat <<EOF >$pathofconf(your configuration here…)EOFecho "startup modified">/tmp/cloudinit.startup /ruby/bin/bs_set_config < $pathofconf

Use the user-data option when creating a VDS-IS instance:

$ nova boot --flavor <FlavorName> --image <ImageName> <InstanceName> --user-data <UserdataFile>

If you want to use puppet, make sure the nameserver is configured. Cloudinit is used to configure the nameserver of VDS-IS.

The following example shows the user data file for cloudinit to configure the hostname, interface, IP address, the nameserver:

#!/usr/bin/env bashpathofconf=/tmp/startup.configrm $pathofconfecho "cloud init script running"#Writing to StartUp Config filecat <<EOF >$pathofconfdevice mode content-delivery-system-managerinterface TenGigabitEthernet 1/0



ip address dhcpexitprimary-interface TenGigabitEthernet 1/0ftp enableEOFecho "startup modified">/tmp/cloudinit.startup/ruby/bin/bs_set_config < $pathofconf

Note : The hostname will be set to the machine name of the instance on Openstack by default. The static IP of DHCP should be set to an interface. If using DHCP, the instance will also set the name server by default. Otherwise, a name server should be set to reserver puppet master’s IP address.

If you want to use heat, you must have enabled heat service on your openstack and installed heat-cfntools in VDS-IS image.

The following example shows how to deploy a content delivery system manager instance and a service engine, then set the CDSM of the service engine :

heat_template_version: 2013-05-23

description: Simple template to deploy a CDSM instance and a SE instance

resources: cdsm_instance: type: OS::Nova::Server properties: name: "heat-cdsm" image: cdsis_vm12 flavor: m1.large user_data: str_replace: template: | #!/usr/bin/env bash pathofconf=/tmp/startup.config rm $pathofconf echo "cloud init script running" #Writing to StartUp Config file cat <<EOF >$pathofconf device mode content-delivery-system-manager interface TenGigabitEthernet 1/0 ip address dhcp exit primary-interface TenGigabitEthernet 1/0 cms enable EOF echo "startup modified">/tmp/cloudinit.startup /ruby/bin/bs_set_config < $pathofconf se_instance: type: OS::Nova::Server properties: name: "heat-se" image: cdsis_vm12 flavor: m1.large user_data: str_replace: template: | #!/usr/bin/env bash sleep 100 pathofconf=/tmp/startup.config rm $pathofconf echo "cloud init script running"



#Writing to StartUp Config file cat <<EOF >$pathofconf device mode service-engine interface TenGigabitEthernet 1/0 ip address dhcp exit primary-interface TenGigabitEthernet 1/0 cdsm ip heat-cdsm cms enable EOF echo "startup modified">/tmp/cloudinit.startup /ruby/bin/bs_set_config < $pathofconf

You can use the following command to start the stack:

heat stack-create <stackName> -f <heatTemplateFile>

After that, you can manage your VDS-IS instance integrated with Cloudinit and Puppet.

Deploying the VDS-IS Virtual Appliance without Openstack

Before you Begin

You need the following to install theVDS-IS Virtual Appliance without openstack:

• KVM/QEMU & Libvirt

KVM/QEMU—KVM/QEMU is the target hypervisor for the deployment. KVM can utilize the hardware virtualization features by loading the kernelmodule into memory

Libvirt—Libvirt is an open source API, daemon, and management tool for managing the platform virtualization. It can be used to manage KVM, Xen, VMware ESX, QEMU and other virtualization technologies.

We highly recommend that you install libvirt using yum to resolve the dependencies:

#>yum install qemu-kvm#>yum install libvirt

• CTemplate & gflags—The CTemplate and gflags libraries is required for the deployment tool. CTemplate is a simple but powerful template language. The deployment tool uses it to generate the virtual machine definition file. The gflags is a library that implements command line flags processing.

For more information about CTemplate and gflags, see the following:

– CTemplate— https://code.google.com/p/ctemplate/

– gflags— https://code.google.com/p/gflags/

To install CTemplate and gflags, follow these steps:

#>rpm -i ctemplate-2.2-0.x86_64.rpm#>rpm -i gflags-1.6-0.x86_64.rpm

• VDSIS

The current VDS-IS distribution is available in various package formats, including RPM package for Redhat, Fedora Linux and tar/gzip format for compiling under other Linux distributions.


https://code.google.com/p/ctemplate/

https://code.google.com/p/gflags/


For RPM package:

#>rpm -i vdsis-1.0.0-0.x86_64.rpm

• After the installation is complete, use the vdsis -h command to check the installation:

#>vdsis -h

Installing the VDS-IS from ISO File

The “vdsis install iso …” command is used to install VDS-IS from an ISO image. The rescue image and the manufacture image is supported.

To install the VDS-IS from ISO file, follow these steps:

Step 1 Create hard disks for VDS-IS:

#>qemu-img create -f qcow2 disk1.qcow2 100G


Step 2 Install VDS-IS as Kernel based Virtual Machine (KVM):

#>vdsis install iso /path/to/rescue-cdrom.iso --name=cdsis --cpu=1 --memory=1048576 --nic_1=virbr0 --disk_1=~/disk1.qcow2

Install VDS-IS from ISO /root/cdsis-rescue-cdrom.iso ...Domain cdsis startedConnected to domain cdsisEscape character is ^]Linux version 2.6.32.61-cds-64 (qiuhan@bgl-ads-2014) (gcc version 4.5.2 (GCC) ) #1 SMP Command line: BOOT_IMAGE=/boot/dmd-bzImage root=0100 rw console=ttyS0,9600n8 ramdisk_size=384000 init=/sbin/run_installer.sh ide=nodma apic isouuid=444dcfd2-c6ca-11e3-94fb-0050569c0393

… …

1. Configure Hardware2. Install all software3. ExitChoice: 2

Choosing this option will delete all software and data on your systemDo u wish to continue? [Y/N] Y

Invoking unmount-all-filesystemsunmounting /boot... doneInvoking whack-all-drivesErasing disks[WARNING] Provisioning disk00 as a new SYSTEM driveTarget psql version: 9.0.6##############################################################################801227638 bytes transferred in 34.8 seconds (21.98 MBps)

Installing system image to flashGenerating platform.confInvoking ruby_upgrade applyInstalling application components...[ap] [di] [li] [me] [pe] [to] [un]

Running post-install hooks...



Syncing filesystems...Successfully installed product image.Software status : Successfully installed

1. Configure Hardware2. Install all software3. Exit

Choice: 3unmounting /sw... doneunmounting /boot... doneRestarting system.

This will install the system from the ISO file to the hard disk. And VDS-IS will shut down after the command completed.

Step 3 Start the VDS-IS Virtual Machine:

#>virsh start cdsis

Installing the VDS-IS from QCOW2 Image

To install the VDS-IS from QCOW2 Image, follow these steps:

Step 1 Create non-system hard disks for VDS-IS:

#>qemu-img create -f qcow2 disk2.qcow2 100G


Step 2 Install VDS-IS as a KVM:

#>vdsis install qcow2 /root/template.qcow2 --name=cdsis2 --disk_1=/root/disk1.qcow2 --disk_2=/root/disk2.qcow2 --nic_1=virbr0 --nic_2=virbr0

start to install vdsis from qcow2:///root/template.qcow2 ...info: creating boot disk '/root/disk1.qcow2' from template '/root/template.qcow2' (100.00/100%)Linux version 2.6.32.61-cds-64 (qiuhan@bgl-ads-2014) (gcc version 4.5.2 (GCC) ) #2 SMP PREEMPT Thu Jul 3 01:30:22 PDT 2014Command line: BOOT_IMAGE=/dmd-bzImage root=0100 rw console=ttyS0,9600n8 ramdisk_size=384000 apic acpi_irq_nobalance… …Automap interfaces boot flag detected:Automapping network interfacesAutomap disk(s) boot flag detected: Re-mapping disksAutomapping drivesNew disks detectedChecking if existing SYSTEM disk layout is optimalConverting SYSTEM disk to a non-merged policyAutomapping flash… …BOOT: entering runlevel 200 (full operations)!BOOT: System Initializing, please wait...........

Service Engine Console

NO-HOSTNAME login:admin



Step 3 Check if all the disks and nic(s) are available:

NO-HOSTNAME#sh disks details disk00: Normal (h00 c00 i00 l00 - virtio) 102400MB(100.0GB) disk00-01: LINUX 4096MB( 4.0GB) mounted internally disk00-02: SW 5120MB( 5.0GB) mounted internally disk00-04: SWSTORE 3072MB( 3.0GB) mounted internally disk00-05: STATE 12288MB( 12.0GB) mounted internally disk00-06: SYSFS 77812MB( 76.0GB) mounted internallydisk01: Normal (h00 c00 i00 l00 - virtio) 102400MB(100.0GB) disk01-01: CDNFS 102391MB(100.0GB) mounted internallyNO-HOSTNAME#show interface all -----TenGigabitEthernet 1/0-----Type:Ethernet... …-----TenGigabitEthernet 2/0-----Type:Ethernet… …

Installing the VDS-IS in Expert Mode

To install the VDS-IS in expert mode, follow these steps:

Step 1 Prepare the libvirt VM definition XML file and all disks:

The definition file should contain a CDROM and insert the VDS-IS ISO (manufacture or rescue).

Check the boot order of the VM and make the VM boot from the CDROM.

Step 2 Define the VM and launch VDS-IS installation.

Step 3 Shutdown the VDS-IS VM after the installation completed.

Step 4 Remove the ISO from the CDROM in VDS-IS VM:

#>virsh edit cdsis… …

Step 5 Startup the VDS-IS VM.

Creating the QCOW2 image

Note We recommend that you create QCOW2 image from the Manufature ISO. You can customize the QCOW2 image as per your requirements.

Creating the QCOW2 Image from Manufacture ISO:

Note The max size for one virtual disk is 2T.

#>qemu-img create -f qcow2 template.qcow2 100G#>vdsis install iso /root/mfg-cdrom.iso --name=cdsis --disk_1=/root/template.qcow2start to install vdsis from iso:///root/mfg-cdrom.iso ...



Linux version 2.6.32.61-cds-64 (gcc version 4.5.2 (GCC) ) #2 SMP PREEMPT Thu Jul 3 01:30:22 PDT 2014Command line: BOOT_IMAGE=/boot/dmd-bzImage root=0100 rw console=ttyS0,9600n8 ramdisk_size=384000 init=/sbin/run_installer.sh --mfg ide=nodma apic isouuid=ae86164a-0291-11e4-a791-0050569c0393… …GENERIC hardware detected

No existing installation has been detectedCreating config based on devices currently in the chassisValidating the chassis has enough hardware to continueInstalling product software...Invoking unmount-all-filesystemsInvoking whack-all-drivesErasing disks[WARNING] Provisioning disk00 as a new SYSTEM driveInvoking flash manufactureFormatting flashInstalling rescue image… …Successfully installed product image.Interfaces will be re-mapped during the next boot.Disks will be re-mapped during the next boot.unmounting /swstore... doneunmounting /sw... done… Manufacture completed successfully!Please remove the CD and reboot

#>virsh destroy cdsisThe disk file template.qcow2 is successfully created as a qcow2 image for VDS-IS installation.

Creating and Customizing the QCOW2 Image:

Step 1 Install VDS-IS as a QCOW2 Disk as its System Disk.

Step 2 Customize the VDS-IS.

Step 3 Create a Boot Flag for Automap:

zzdebugshell>mkdir -p /boot/etc/boot/flagszzdebugshell>mkdir -p /boot/etc/boot/flags/AUTOMAP_INTERFACESzzdebugshell>mkdir -p /boot/etc/boot/flags/AUTOMAP_DISKS

Step 4 Shutdown the Virtual Machine.

Step 5 Save the QCOW2 Disk as a QCOW2 Image.


Cisco Videoscape Distribution

A

P P E N D I X A
Troubleshooting
Common Troubleshooting ScenariosThis section explains the common troubleshooting scenarios and the various ways to troubleshoot and monitor VDS-IS 3.3 Virtual Machine functioning and performance.

Note The troubleshooting can be done either via CLI, or the esxtop command (by logging in to the ESXi shell), or the vSphere GUI.

Unable to deploy VM or VM is deployed but unable to power on the VMThe error can appear for one of the following reasons :

• The VM is being attempted to be deployed, or was deployed on insufficient datastore memory.

Check the size of the total disk of the VM, and see if the available space on datastore is enough. One might not run into the disk storage insufficiency if using Thin provisioning to create disks since it occupies only 2GB memory for the VM, however it is strongly recommended to use Thick provisioning of virtual disks to get good VM performance.

Unable to deploy VM with disk size greater than 8TB

Step 1 In the hypervisor settings, click on the Configuration tab.

Step 2 From the Software menu, select Advanced Settings.

The Advanced Settings page appears.

Step 3 Select VMFS3.

Step 4 In the VMFS3.MaxHeapSizeMB feild, enter 256 as the maximum heap size.

Note The default value set in the VMFS3.MaxHeapSizeMB is 80MB.

Step 5 Click Ok, and save the changes.

A-1Suite, Internet Streamer Virtualization Guide

Appendix A TroubleshootingCommon Troubleshooting Scenarios

Step 6 Reboot the ESXi Host.

Unable to ping the external switch connected to portchannelLet us consider that, four interfaces from an external switch are configured with port channel that run into a vswitch on the hypervisor. On the other hand the VM has a number of logical interfaces configured in portchannel that are not equal to 4. The VM and external switch will not be able to ping each other in this case and connectivity not established.

The reason for this is that the number of interfaces in port channel at either ends should be equal. If there are 4 interfaces from the external switch in port channel as in the example above, the VM should also have a corresponding 4 interfaces in port channel.

Unable to connect even with equal number of interfaces in port channel and external switch

Step 1 In the hypervisor settings, click on the Configuration tab.

Step 2 From the Hardware menu, select Networking.

Step 3 Click on the Properties link located to the right of 'Virtual Switch: vSwitch1'.

A 'vSwitch1 Properties' page will appear.

Step 4 Select vSwitch from the vSwitch properties page.

Step 5 From the Load Balancing drop-box, Select Route based on IP hash.

Step 6 Click Ok, and save the changes.

Step 7 Reboot the ESXi Host.

Unable to Install VM on an external NAS storageThe probable reason to see errors while installing a VM on external NAS storage can stem from one of the following:

1. Not enough storage space on the external NAS to accommodate the VM disks.

2. The directory of the file path under which the VM is being created does not have necessary read, write and execute permissions.

After setting the above right, installing VM on NAS should work.

Failed to define domain cause domain with same name already exists#>vdsis install iso /root/ rescue-cdrom.iso --name=cdsis -- disk_1=/root/disk1.qcow2start to install vdsis from iso:///root/cdsis-rescue-cdrom.iso ...error: Failed to define domainerror: operation failed: domain 'cdsis' already exists with uuid d4f651c6-2e13-22b7-160b-2bfec540eb28

A-2Cisco Videoscape Distribution Suite, Internet Streamer Virtualization Guide

Appendix A TroubleshootingTroubleshooting Tips to Improve Performance

The issue is caused by another virtual machine with the same name has been defined in the libvirt. You have options to undefine the existed virtual machine or modify your virtual machine to another name.

#>virsh undefined cdsis

or

#>vdsis install iso /root/ rescue-cdrom.iso --name=cdsis2 -- disk_1=/root/disk1.qcow2

Failed to start domain for permission issue for disk files#>vdsis install iso /root/ rescue-cdrom.iso --name=cdsis -- disk_1=/root/disk1.qcow2start to install vdsis from iso:///root/cdsis-rescue-cdrom.iso ...error: Failed to start domainerror: internal error Process exited while reading console log output: char device redirected to /dev/pts/1qemu-kvm: -drive file=/root/disk1.qcow2,if=none,id=drive-virtio-disk0,format=qcow2: could not open disk image /root/disk1.qcow2: Permission denied

#>vi /etc/libvirt/qemu.confuser = "root" /* uncomment this line */group = "root" /* uncomment this line */

#>service libvirtd restart

Troubleshooting Tips to Improve Performance

Using KVM

PCI pass-through / VhostNet

PCI pass-through can achieve the best performance while sacrificing some useful features such as live migration.

However, Vhost is a preferred solution cause it loses no useful features. Vhost puts virtio emulation code into the kernel, therefore expects a much higher performance compared to virtio.

To increase the network bandwidth, it is highly recommended to use the port channel to group several physical Ethernet links.

Raw Image Format

Using raw image format improves the disk performace. However, you will lose additional features that the qcow2 images bring, including the base images, snapshots, compression and the encryption.



SMP IRQ Affinity Setting

The CPU and an Input/Output device communicate through interrupts. On multiple CPU systems, each CPU call handles an interrupt request. It improves the performance, if the network card interrupts are distributed across all the processors on the SMP system.

The following example shows how to set up the smp_affinity of network inerface interrupt:

Note This allows the VDS-IS to deliver network interrupts to all the cores and also perform load balancing between them.

debugshell# cat /proc/interrupts

CPU0 CPU1 CPU2 CPU3 0: 121 0 0 0 IO-APIC-edge timer 25: 68683 0 0 0 PCI-MSI-edge virtio0-input 28: 68700 0 0 0 PCI-MSI-edge virtio1-input 31: 68889 0 0 0 PCI-MSI-edge virtio2-input 34: 69777 0 0 0 PCI-MSI-edge virtio3-input

echo 1 > /proc/irq/25/smp_affinity;echo 2 > /proc/irq/28/smp_affinity;echo 4 > /proc/irq/31/smp_affinity;echo 8 > /proc/irq/34/smp_affinity;

… …

Using VMWare

PCI Pass-through / VMNet3 for Network Interfaces

The presence of PCI NIC passthrough prevents many commands on the virtual machine. It will not be able to be suspended, to have snapshots taken or restored, or to participate in vMotion.

There are several different virtual network adapters available: E1000, E1000E and VMXNET3. the VMXNET3 network adapter is a para-virtualized network adapter which can deliver better network throughtput performance than the E1000 and E1000E network adapters.

To increase the network bandwidth, it is highly recommended to use the port channel to group several physical Ethernet links.

SMP IRQ Affinity Setting

The CPU and an Input/Output device communicate through interrupts. On multiple CPU systems, each CPU call handles an interrupt request. It would improve the performance if the network cards interrupts are distributed across all the processors on the SMP system.

For more information, see “SMP IRQ Affinity Setting” section on page A-4



Using CLI

For the VM that is deployed, we can use several CLI commands to do troubleshooting especially for performance. These have been traditionally used for VDS-IS bare metal testing too. However in case of virtual machines, the esxtop is more recommended for certain statistics checking.

Note For all the below commands, the user has to be logged in to debug shell mode on the VM.

CPU Usage

An example command to be run to check CPU usage on the VM can be of the form:

#mpstat -P ALL 5

The command lists CPU usage for the virtual CPU’s and the total average of all usage.

top -H -p `pidof web-engine`

The command lists web-engine CPU usage.

Disk Usage

A typical command to check disk usage every 5 seconds will be as follows:

iostat -dmx 5 | grep -v '^[sh]d[a-z]+[0-9]

This will display several statistics of each of the virtual disks that are being used in the VM.

Memory usage

This can be checked using the top command. Simply run the following:

#top

The output will display several parameters relating to the memory usage and also per process resource usage.

The show web-engine health command and the show web-engine memory usage command is used check the web-engine memory usage.

Using Esxtop

Esxtop helps to check the hypervisor usage of the physical machine. The interactive esxtop utility can be used to provide I/O metrics over various devices attached to a VMware ESX host, mainly for CPU usage, disk usage, network usage, memory usage and others.

To run esxtop:

Step 1 First make sure to enable SSH option in ESXi options. (For UCS you need to access the ESXi via the CIMC KVM console and enable this option.)

Step 2 Using a secure shell (SSH), log on to the ESX Server machine as root. Then run the command:

esxtop



or

TERM=xterm esxtop

The esxtop tool includes several interactive commands.

Step 3 Enter h, to view a list of the interactive commands.

Toggle between views displayed by esxtop to see different parameters.

Step 4 Enter the following to view some associated views:?c = cpu?, m = memory?, n = network?, d = disk adapter, and more.

Check details for interpreting esxtop outputs here:

https://communities.vmware.com/docs/DOC-9279

Step 5 Enter q, to exit esxtop.

Using vSphere

The vSphere GUI has several options that allow to monitor the performance of VM's running on the hypervisor. Select the "Performance" tab among the VM options and click "Chart Options" to set the appropriate fields to monitor.


https://communities.vmware.com/docs/DOC-9279

Cisco Videoscape Distribution

A

P P E N D I X B
Commands
This appendix provides information on the CLI commands used to install the Cisco Videoscape Distribution Suite, Internet Streamer (VDS-IS).

The vdsis install command is available to install VDS-IS from an ISO image file. The syntax for the command is list as belows:

vdsis install <type> <media> [--cdrom] <vmdef>

Syntax Description

The following example shows the VM definition file:

#>cat /usr/local/etc/vdsis/cdsis.def--name=cdsis--cpu=1--memory=1048576--nic_1=virbr0--nic_2=virbr0--disk_1=cdsis.qcow2--vnc_port=5902

The following example shows how to use the --flagfile to include another definition file:

#>cat ~/myvm.def--name=cdsis--disk_1=diskx.qcow2

install Installs VDS-IS as a virtual machine.

type <iso|qcow2> Installs from ISO file or qcow2 image.

media <string> Path for ISO file or qco2 image. The absolute path is required.

--cdrom Specifies the device name for cdrom, such as hdc, etc.

vmdef Defines the Virtual Machine.

--name Name for the virtual machine.

--cpu Number of CPU. The default value is 1.

--memory Memory size in KB. The default value is 1048576

--nic_x Bridge name for NIC to attach and x starts from 1, maximum 5 NIC(s).

--disk_x Disk path and x starts from1, maximum 5 disk(s).

--vnc_port VNC port. The default value is 5900.

--flagfile Base VM definition file. The options will be overriden by outside definitions. See the /usr/local/etc/vdsis/cdsis.def for an example.

B-1Suite, Internet Streamer Virtualization Guide

Appendix B Commands

--vnc_port=5903--flagfile=/usr/local/etc/vdsis/cdsis.def

Best PracticesThis section describes the best practises that you must follow while installing the VDS-IS software:

• Install with VM definition in the command line.

#>vdsis install iso /path/rescue-cdrom.iso --name=cdsis --cpu=1 --memory=1048576 --nic_1=virbr0 --disk_1=~/disk1.qcow2

#>vdsis install qcow2 /path/is-template.qcow2 --name=cdsis --cpu=1 --memory=1048576 --nic_1=virbr0 --disk_1=~/disk1.qcow2

• Install with VM definition file.

#>vi ~/vm.def --name=cdsis --cpu=1 --memory=1048576 --nic_1=virbr0 --disk_1=cdsis.qcow2 --vnc_port=5902#>vdsis install iso /path/rescue-cdrom.iso --flagfile=~/vm.def

• Install with command options along with VM definition file.

#>vdsis install iso /path/rescue-cdrom.iso --name=vm01 --vnc_port=5904 --disk_1=~/disk1.qcow2 --flagfile=~/vm.def

B-2Cisco Videoscape Distribution Suite, Internet Streamer Virtualization Guide