Virtualization Manager™ Administrator Guide

VIRTUALIZATION MANAGER™ ADMINISTRATOR GUIDE

Version: V4.1 NOTICE

The information in this document is provided as is and without warranty of any kind and is subject to change without notice. Virtual Iron Incorporated assumes no responsibility, and shall have no liability of any kind arising from supply or use of this publication or any material contained herein.

This material is protected by the copyright laws of the United States and other countries. No part of this publication may be reproduced, distributed, or altered in any fashion by any entity without the express written consent of Virtual Iron® Inc.

Virtual Iron® Software, Inc. 900 Chelmsford Street Tower I, Floor 2 Lowell, MA 01851 http://www.virtualiron.com

TRADEMARKS

Virtual Iron®, Virtual Iron® Virtualization Manager™ and the Virtual Iron® logo are trademarks of Virtual Iron Software, Inc.

Other company and product names are trademarks and trade names or registered trademarks of their respective owners.

00100807R CONTENTS ......

Preface ...... vii Audience...... vii Conventions...... vii License Information ...... viii Redistributing GPL Source Files...... viii

1 Virtual Iron® Product Overview ...... 1 About Virtual Iron® ...... 2 Virtualization Manager ...... 2 Delivering Virtual Infrastructure ...... 3 Virtual Iron® Architecture...... 4 Product Requirements ...... 5 Object Relationships in Virtualization Manager ...... 6 Managed Nodes and Virtual Data Centers ...... 6 Virtual Data Centers and Virtual Servers ...... 7 Virtual Server Characteristics ...... 8 Processors ...... 8 Processing Priority ...... 8 Memory ...... 8 Network Connections...... 9 Disks ...... 9 Boot Methods...... 9

2 Installing Virtual Iron®...... 11 Installation Overview...... 12 Virtual Iron® Single Server Edition (SSE)...... 12 SSE RAID Considerations ...... 12 Virtual Iron® Enterprise Edition (EE) ...... 13 Hardware and Software Requirements...... 15 Managed Nodes, Minimum Requirements...... 15 Management Node, Minimum Requirements...... 15 Virtualization Manager Client Requirements...... 16 GOSs Supported by Virtual Servers ...... 16 Languages Supported...... 16 Product Configurations ...... 17 Management Operations...... 17 Product Configuration, Enterprise Edition...... 18

i Contents

PXE Booting Managed Nodes ...... 18 Managed Node Configuration...... 19 Virtualization Processor Settings of Each Node...... 19 Configure IPMI or ILO for each Node...... 19 Disabling Hyperthreading Support ...... 20 Site Preparation ...... 21 Define the Physical Infrastructure ...... 21 Defining Network Connections...... 21 Connecting Nodes to the SAN Infrastructure...... 23 Installing Virtual Iron®...... 24 Before installation...... 24 Virtualization Manager and Data Protection ...... 33

3 Configuring Networks...... 37 Connecting to the Virtualization Manager...... 38 Mapping Physical Ports to Logical Networks...... 40 Defining Networks in a Virtualized Environment ...... 40 Creating Networks ...... 43 Configuring Networks, EE and SSE...... 43 Default Management Network, Enterprise Edition .... 43 Default Public Network, Single Server Edition ...... 44 Configuring Ethernet Networks ...... 45 Configuring iSCSI Connectivity...... 47 Configuring VLANs...... 52

4 Using Administration Manager®...... 55 About the Administration Manager ...... 56 Using the Administration Manager...... 57 Applying a New License File ...... 58 Upgrading to a New Version of the Product...... 58 Put/Get Files on the Virtualization Manager...... 58 Backing up the Virtualization Manager Database ...... 60 Restoring to a Backup Version of the Database ...... 60 Restarting Virtualization Manager Services ...... 61 Reloading Virtualization Manager ...... 61 Running a Command on Virtualization Manager ...... 62

5 Using Virtualization Manager® ...... 63 Using the Integrated Tutorial ...... 64 Virtualization Manager Overview ...... 65 Using the Application Toolbar...... 66 Resource Center...... 66 Resource Center Tabs...... 66 Hardware...... 67 Policies and Reports ...... 67 Reports ...... 67 User Policies ...... 68 System Policies...... 68 Jobs...... 69

ii Virtualization Manager™ Administrator Guide ofgrn trg...... 85 Storage...... Configuring 6 H eoioy...... 101 ...... VHD Repository 99 Cloning Disks...... efrigJbOeain...... 81 Performing JobOperations...... xotn n motn...... 94 Exporting and Importing...... 90 ...... Configuring Logical Disks 88 Discovery and Management ofPhysical Disks...... 86 Configuring Storage...... bu h osFaeok...... 78 About the Jobs Framework...... 74 72 Using thePull-downMenusand Action Toolbar...... Navigation Tree xotn rIprigVDIaeFls...... 101 101 Exporting orImporting VHDImage Files...... VHD File Naming Conventions 99 Cloning Logical Disks...... lsn o as...... 84 ...... Tabs Closing Job 84 Determining the Cause of Job Failure...... 83 83 Aborting aJobinthe Jobs View...... Aborting Jobs 82 81 Starting aJob...... About theJobs View igeSre dto...... 97 Single Server Edition...... 94 Enterprise Edition...... 93 ...... Creating Logical Disks 91 90 Creating DiskGroups...... Disk GroupsandLogical Disks 89 LUNs and Aliases...... 87 Advantages ofManaged Storage...... osadRsuc okn...... 79 Jobs and Resource Locking...... 78 ...... Managing in aMulti-User Environment 76 Action Toolbar...... 75 ...... Accessing License Information 74 Pull-Down Menus...... 71 Users...... motn ita ik...... 98 ...... 97 Importing a virtualdisk ...... Exporting aVirtualdisk 96 ...... Importing a Virtualdisk 94 Exporting ALogical disk...... o tts...... 80 ...... 80 Job States ...... 80 Jobs and Events ...... Job Failure and Rollback 79 Locks and Multiple Users...... 78 78 Actions and Job Operations...... What’s in aJob? 75 Determining WhatYour LicenseSupports...... 74 ...... 74 View Menu ...... File Menu CONTENTS iii . . . . . Contents

7 Creating and Configuring Virtual Servers...... 103 Creating Virtual Data Centers...... 104 VDCs are Containers for VSs ...... 104 Assigning Nodes to Virtual Data Centers ...... 106 VDCs and Unassigned Virtual Servers...... 109 About Unassigned Virtual Servers ...... 109 Configuring Unassigned Virtual Servers ...... 110 Deploying an Unassigned Virtual Server ...... 110 Moving a VS to Unassigned...... 111 Virtual Servers ...... 112 Creating a Virtual Server...... 112 Cloning Virtual Servers ...... 119 Preparing a Windows VS for Cloning...... 119 Cloning Windows Virtual Servers...... 119 Cloning a Virtual Server ...... 120 Installing a Guest OS to a Logical Disk ...... 122 Installing VSTools on Guest OSs ...... 124 Installing VS Tools on Linux Guests ...... 124 Verifying that VS Tools are Installed ...... 127 Uninstalling VS Tools...... 127 Installing VS Tools for Windows® Virtual Servers ...... 127 VS Tools Silent Install ...... 130 Starting and Stopping Virtual Servers...... 130 Starting a Virtual Server...... 130 Stopping a Virtual Server ...... 130 Launching a Virtual Server Console ...... 132 Configuring Policies ...... 133 LiveCapacity™ ...... 133 LiveRecovery™...... 134 LiveMaintenance™ ...... 136 Moving Virtual Servers and Nodes ...... 138 The Role of the Resource Center ...... 138 Moving Nodes to a VDC...... 138 Moving a Node to Resource Center...... 140 Conditions for Virtual Server Movement ...... 141 LiveMigrate™ Requirements ...... 141 Moving a Virtual Server To a New Node or VDC. 141 Node Choices and Restrictions...... 142 Provisioning VSs with Gold Masters...... 144 Creating a Gold Master Logical Disk...... 144 Cloning and Booting from a Gold Master Logical Disk.... 145

8 Policies and Reports...... 147 About Policies and Reports ...... 148 Report Types ...... 150 Report Naming and Types ...... 150 Generating Reports...... 150 Report Examples...... 152 Event Report ...... 152

iv Virtualization Manager™ Administrator Guide efrigAmnsrtv ak ...... 161 ...... Tasks Administrative Performing 9 igeNd oMliNd ovrin...... 191 Single Nodeto Multi-Node Conversion...... nntligVrulzto aae ...... 193 ...... Uninstalling Virtualization Manager suigVrulzto aae ihAalblt...... 187 186 Assuring Virtualization Manager HighAvailability...... Configuring the 185 Archive Manager ...... Changing the Virtualization Manager IPAddress 183 ...... Performing Backup andRestoreOperations 181 Starting theVirtualization Manager...... efrac ttsis...... 175 Performance Statistics...... trigSse oiis...... 159 ...... Starting System Policies 155 User Policies...... ofgrn o-nls ebad...... 172 Configuring Non-English Keyboards...... 165 ...... Configuring LDAP 162 ...... Configuring UserAccounts ro oCnetn ...... 191 ...... Converting Prior to nntligfo iu...... 193 Uninstalling fromLinux...... High Availability Cons High Availability 183 Restoring the ConfigurationDatabase...... 183 Backing upthe Configuration Database...... 181 Starting the Virtualization Manager, Windows®...... Starting the Virtualizati cesn efrac ttsis...... 175 Accessing Performance Statistics...... ehia upr ...... 160 ...... Technical Support 159 LiveCapacity and AutoRecovery...... 155 ...... Configuring andStarting User Policies okrud...... 172 Workaround...... 171 ...... 166 Changing the LDAP Configuration .... 165 Configuring Virtual Iron To Authenticate with LDAP ...... 165 LDAP Component Information ...... LDAP Support andAdministration 165 About LDAPAuthentication...... 164 ...... Editing Account Information 163 Deleting UserAccounts...... 162 Creating Local User Accounts...... Converting SSEtoEEVirt ciePsieSre ofgrto...... 188 Active/Passive ServerConfiguration...... srCnetos...... 180 ...... User Connections 180 180 Active Policies...... License Usage 178 Virtual Server Performance...... 176 176 Node Performance...... 176 Errors Last 5 ...... Activity forthe Resource Center ofgr ebad...... 172 ...... Configure Keyboard 172 ...... Install Java 1.6 ita evrRpr ...... 154 ...... Virtual Server Report 154 153 Node Report...... Job Report drtos...... 188 iderations...... nMngr iu®...... 181 Linux®...... on Manager, aiainMngr.. 191 ualization Manager..... CONTENTS v . . . . . Contents

Uninstalling from Windows...... 193 Reassigning Unassigned DGs...... 194 Accessing Online Help...... 195 Accessing Technical Support ...... 197

vi Virtualization Manager™ Administrator Guide C A P ONVENTIONS UDIENCE REFACE ...... • • SAN set-up SAN and management, including Fibrenetwork Channel administra- • Network configuration • LINUX® or Windows® administration • Server cabling and configuration • following areas: This guideisforexperiencedITadmini tasks. Manager client tomanage virtualserv Iron® software components. Procedures define how tousethe Virtualization Instructional material describes the functional relationships between Virtual in an enterprise data center. graphical client.This guide describes how Virtual Iron® Virtualization Manager™ consists of a management server and a • This bookusesthe fo Light blue controls inthe Virtual Iron® management client. tion Bold type isused tocalloutthe nam text is used forhyper-textlinks. llowing conventions: ...... ers and howto performadministrative strators. Itassumesknowledge inthe es of fields, buttons, and navigation to install and configure Virtual Iron® PREFACE

Audience ...... vii

. . . . . Chapter PREFACE License Information

• Mono-spaced blue type is used for command examples. • Italicized text is used to define or emphasize key terms.

LICENSE INFORMATION

The following Third Party Software modules are incorporated in or shipped with the Virtual Iron® software and are subject to the following terms and conditions:

Linux® Linux® is a registered trademark of Linus Torvalds. Redistributing GPL Source Files

You can redistribute and/or modify General Public License (GPL) software under the terms of the GPL. You may obtain a copy of the source code corresponding to the binaries for the GPL Software (the “GPL Source Files”) by downloading the GPL Source Files from http://www.virtualiron.com/prod- ucts/open_source.cfm. This offer to obtain a copy of the GPL Source Files is valid for three years from the date you acquired this software product.

viii Virtualization Manager™ Administrator Guide 1

VIRTUAL IRON® PRODUCT OVERVIEW

......

Virtual Iron® ™ is a data center virtualization product that allows you to create and manage multiple functionally independent virtual servers (VSs) on one or more physical servers. This chapter provides an overview of the Virtual Iron product. This chapter contains the following sections: About Virtual Iron® ...... 2 Delivering Virtual Infrastructure ...... 3 Virtual Iron® Architecture ...... 4 Product Requirements...... 5 Object Relationships in Virtualization Manager ...... 6 Virtual Server Characteristics ...... 8

1 Chapter 1 VIRTUAL IRON® PRODUCT OVERVIEW About Virtual Iron®

ABOUT VIRTUAL IRON®

Virtual Iron® is a virtualization product that enables IT administrators to increase the efficiency and flexibility of physical server resources. Virtual Iron software: • Increases server utilization rates • Cuts management complexity and spiraling costs • Adapts to changing business needs • Allows modification and reallocation of server resources • Copes with failures without requiring human intervention. Virtual Iron® runs across a set of physical servers, or managed nodes. IT administrators partition node resources so that each node supports n-virtual servers. The goal is to use each physical node at maximum efficiency, in a framework that uses processing power where and when it is needed. Virtualization Manager Virtualization Manager comprises a management server and integrated database, and a graphical client user interface that supports multiple concurrent users. Virtualization Manager is an enterprise-class, transactional virtualization framework. Within this framework, one or more clients connect to the Virtual Iron® Virtualization Manager and manage the resources of a set of managed nodes.

2 Virtualization Manager™ Administrator Guide D ELIVERING V IRTUAL Figure 1. Virtual1.Figure Iron® DynamicInfrastructure Virtual Iron® solution. Figure 1 ness changes ondemand. cation workloads, whichcanbe conf set of physicalservers support anumber (physical machines) into avirtualinfrastructure. In thisflexibleframework, a At thehighestlevel, Virtual Iron® transformsasetof interconnected nodes work with nospecialconfigurationordriver support. into the latest Intel® andAMD® processors soapplications run inthis frame- greatly simplified. Virtual Iron®lever networks and SANs,and of redundant paths to guardagainst failure, are physicaloneers aremoved server from performance and other criteria.Asapplic Automated policies control the resource I provides ahigh-level viewofthe vi NFRASTRUCTURE VIRTUAL IRON® PRODUCT OVERVIEW PRODUCT VIRTUAL IRON® igured, deployed, and adapted tobusi- ages thevirtualization extensions built s usedbyvirtualservers, based on to another. Configuration of access to ofoperating systems (OS)and appli- ation demands change, virtualserv- rtual infrastructure built withthe Delivering Virtual Infrastructure

3 . . . . . Chapter 1 VIRTUAL IRON® PRODUCT OVERVIEW Virtual Iron® Architecture

VIRTUAL IRON® ARCHITECTURE

Virtual Iron® comprises three components. • Hypervisor—An abstraction layer that mediates between the physical hardware and the Virtualization Services component. • Virtual Iron® Virtualization Services—A software component that performs many functions ordinarily provided by standard operating systems. • The Virtual Iron® Virtualization Manager—A high-performance client/server management framework. Figure 2 shows a conceptual view of six virtual servers running on a single physical node.

Figure 2. Virtual Iron® Architecture

4 Virtualization Manager™ Administrator Guide P RODUCT R EQUIREMENTS Figure 3. Conceptual3.Figure View ofVirtual the Iron® Framework Virtual Iron’s management server, server linked toasetof physicalservers, or As with each node overadedicated ports the license youhave purchased. See number ofnodes you can manage isprocessor-dependent, andvaries with With Virtual Iron®, you may virtualizethe resources of one or more nodes. The public networks. this frameworkmayalso accessSANandnetwork resources via oneor more Figure 3 for informationon product licensing. shows,the Virtual Iron® fram VIRTUAL IRON® PRODUCT OVERVIEW PRODUCT VIRTUAL IRON® management network.Nodesmanaged in Virtualization Manager Determining What Your LicenseSup- ework requires asinglemanagement nodes , on an Ethernet network. ™, communicates Product Requirements

5 . . . . . Chapter 1 VIRTUAL IRON® PRODUCT OVERVIEW Object Relationships in Virtualization Manager

OBJECT RELATIONSHIPS IN VIRTUALIZATION MANAGER

Virtual Iron® manages a set of nodes, enabling the creation of virtual data centers (VDCs) and virtual servers. The sections that follow describe the relationships between managed nodes, VDCs, and virtual servers. Managed Nodes and Virtual Data Centers A Virtual Data Center (VDC) is an administrative container that refers to a group of managed nodes, their virtual servers, and applications. Each VDC houses a group of managed nodes used by a specific area of operations within an enterprise. Each VDC may need connections to specific networks and SANs within the enterprise. To illustrate what a VDC is and how to create and assign nodes to them, let’s say your company has several departments: Design and Test, Manufacturing, Finance, and Sales. Each of these departments has different responsibilities and each will likely run a set of applications specific to its aims. The Design and Test organization may run CAD and other programs that are not used elsewhere in the organization. Manufacturing may run programs that link its production goals with existing inventories of materials. Finance runs small- and large-scale accounting applications. Therefore, your enterprise may, for example, divide a set of 14 nodes among four administrative groups, as shown in Figure 4.

Figure 4. Nodes And Virtual Data Centers

6 Virtualization Manager™ Administrator Guide Virtual DataCenters Figure 5. VDCs, Nodes andVDCs, VSs 5.Figure simultaneously on asinglenode. JustaseachVDC may contain dent environments, orvirtual servers.Anumberof virtualserverscanrun With Virtual Iron®, each nodeis partitioned intoasetof functionally indepen- a VDCcanhost a setof virtualservers. ownsin nodeof asetnodes, each theresourcesVDC Just aseach cations. A virtual server isavirtualmachine thatruns anOSand its associated appli- tual servers. Sales andMarketing contains nodes 13and 14,whichhost two andthree vir- ers, whilenodes 11 and12 hostfourand twovirtual servers respectively. managed nodes—10, 11, and 12.Ofthese, node 10 contains no virtualserv- shows twoVDCs,Finance andSales and Marketing. Finance contains three the virtualservers thatrun onthese nodes,refer to To understand therelationship between VDCs,the nodes they contain, and each node may hostmultiple virtualservers. and VirtualServers VIRTUAL IRON® PRODUCT OVERVIEW PRODUCT VIRTUAL IRON® Object Relationshipsin Figure 5 Virtualization Manager . This illustration. This n -nodes,

7 . . . . . Chapter 1 VIRTUAL IRON® PRODUCT OVERVIEW Virtual Server Characteristics

VIRTUAL SERVER CHARACTERISTICS

A virtual server is an instance of an operating system and its applications. With Virtual Iron®, you can configure and run multiple virtual servers on each managed node. Virtualization Manager™ provides control of virtual server characteristics, such as: • Number of processors (default: 1) • Processing priority (default 5) • Memory (default: 256 MB) • Network connections • Disks (optional) • Boot method These characteristics are defined briefly below. For instructions on configuring them, see the integrated product tutorial. Processors Each virtual server uses some or all of the processors on the node hosting it. Virtual Iron® allows multiple virtual servers to share the same processors. If a node has four physical processors, the virtual servers configured on that node can each use part or all of them. You can assign the default minimum of one processor or assign a higher number. Virtual Iron® limits each virtual server to the number of processors available on its host node. Processing Priority When more than one virtual server is using the same processing resources, virtual servers assigned a higher priority are favored over another. For example, virtual servers A and B have the default priority of 5; C is assigned 9, the highest priority, Virtual Iron® allows C to run more frequently than A and B. Memory By default, each virtual server is allocated approximately one quarter Gigabyte (256 MB) of memory. You can increase or decrease the memory allocated to each virtual server to suit application requirements. Unlike processors, memory is not shared among virtual servers, but is allocated to virtual servers at configuration time. Memory allocated to one virtual server cannot be used or borrowed by another, even if it is unused. Instead, memory is apportioned among virtual servers administratively, with each allocated a specific amount of the total available. The total of allocated memory cannot exceed 100% of the available physical memory.

8 Virtualization Manager™ Administrator Guide Boot Methods Disks Network Connections vide thedesired access. HBA to theSANadministrator, so that switches maybe programmed to pro- must provide the worldwidenode numbers (WWNN)associated witheach use as aboot disk,and the orderinwhich LUNsarepresented tothe OS.You Server a networkboot device or fromaCDROM. See the steps in Virtual servers canboot fromlogicaldisksonaSAN, or localdisk, from As the Virtualization Manager administra Virtual Iron® license.See total number of VNICsyou can assign to server,to thatvirtualserver,is bound it other.used andcannot byany be The applications to access multiple networks. address. You can assign multiple VNICstoeach virtual server, enabling its card, Each virtual server uses asoftware objectcalleda The Virtual Iron®administrator controlswhich (HBA) or access toan iSCSInetwork,can connect toSANresources. hosting it.Virtual servershosted bya node containing a tual server toboot from,and access logical harddisks created onSANorlo tual server. Thesediskscanbe rawSAN(FibreChannel oriSCSI)volumes, or or for information on configuring boot parameters. VNIC, toconnecta specific subnet VIRTUAL IRON® PRODUCT OVERVIEW PRODUCT VIRTUAL IRON® Accessing LicenseInformation anydisksvisible to, themanaged node cal drives. You can configure eachvir- tor, youcanassign Once a VNIC is assigned to a virtual ais assigned to VNIC Oncea all virtualserversis limited byyour . EachVNIChasaunique MAC- logical unit number number unit logical virtual network interface Virtual Server Characteristics host busadapter . Creating a Virtual disks to each vir- (LUN) to

9 . . . . . Chapter 1 VIRTUAL IRON® PRODUCT OVERVIEW Virtual Server Characteristics

10 Virtualization Manager™ Administrator Guide 2

INSTALLING VIRTUAL IRON®

......

Installation Overview ...... 12 Hardware and Software Requirements ...... 15 Product Configurations ...... 17 Managed Node Configuration...... 19 Site Preparation...... 21 Installing Virtual Iron® ...... 24

11 Chapter 2 INSTALLING VIRTUAL IRON® Installation Overview

INSTALLATION OVERVIEW

Virtual Iron® can be configured to run on a single server or across multiple servers. Each of these installation scenarios is treated separately in the installation procedure in the last section of this chapter, Installing Virtual Iron®. Virtual Iron® Single Server Edition (SSE)

In a single-server configuration, Virtualization Manager and the Virtual Iron® software reside together on the managed server. Instead of being hosted by a commercial operating system, Virtualization Manager is hosted by the Virtual- ization Services layer. The relationship between these components is shown in Figure 6.

Figure 6. Virtual Iron® Management Framework, Single Server Configuration

SSE RAID CONSIDERATIONS When using RAID with SSE systems, consider the layout of the RAID set prior to SSE installation. If you are going to use RAID to configure your physical storage prior to Virtual Iron installation, configure one physical volume to be excluded from the RAID set and it will be used for the Virtual Iron install. Cre- ate another volume(s) with the remaining storage to store the virtual or logical disks for use by virtual servers.

12 Virtualization Manager™ Administrator Guide Virtual Iron® Enterprise Edition (EE) management servernode (the ager, ers called Virtual Iron® EnterpriseEdition runsonone ormoreIntel orAMD-based serv- disk, and create one 740GBRAID-set volume for storinglogicaldisks. large 1,000 GBvolume.Instead, use one250 GBvolume for theboot/install For example,if youhave four 250 GB this volume. Configure the remaining separate volumes for logical disks. Virt Instead, useone physicalvolume for Virtual Iron software and then create mal practice. your node, combining them intoone single large RAIDvolumeisnot anopti- this isatime-consuming process,if but itrequires thatthe drives areexportedto prior there-install process.Since disks on thatvolume.Logical diskscreated onthe bootvolumecan besaved, boot volume of thephysical server, so During theinstallation process,theSSE only bemanaged viaasingle dedicated management network. publicofconnected withanynumber be work, whichhosts a DHCPserver. With Virtual Iron®EE,managed nodes can Figure 7 nodes areinterconnectedby adedicated management network, asshown in When running Virtual Iron® EE,Virtualization Manager andallmanaged the web-based management application hostedbyaseparate . Note that the nodes in thisillustration areconnectedto apublic net- managed node s. These servers are managed by management node you have multiple physicalvolumes on physical volumes forlogical disks. disksin yoursystem,donot create one INSTALLING VIRTUALIRON® ual Iron recommends at least 36 GBfor it isnotrecommended tostorelogical networks. However, these nodes can installer clears all disk data onthe ). Installation Overview Virtualization Man-

. . . . . Chapter 2 INSTALLING VIRTUAL IRON® Installation Overview

Figure 7. Virtual Iron® Management Framework

14 Virtualization Manager™ Administrator Guide H ARDWARE Management Node, Minimum Requirements Managed Nodes, Mi

AND • • • • The management node hosts the Virtual Iron® Virtualization Manager. • • • • Managed nodes have thefollowing minimumrequirements. nodes. Virtualization(whichruns managed Manager) more interconnected withoneor Virtual Iron® can runon asingle node, orcan comprisea management node S CentOS4.4 - SUSELinux Enterprise Server9SP3 - Windows 2003 server - - RHEL4U4 and U5 OSs supported: Ethernet ports:2 30 GB hard drive 2 GBRAM Fibre channel card(optional) Ethernet ports: 2; ifusing iSCSI: 3 Local SATA and SCSIdrives. IDEdiskdrives are notsupported. Intel®-VT orAMD-V®based nodes OFTWARE nimum Requirements R EQUIREMENTS INSTALLING VIRTUALIRON® Hardware andSoft ware Requirements

. . . . . Chapter 2 INSTALLING VIRTUAL IRON® Hardware and Software Requirements

Virtualization Manager Client Requirements

The Virtualization Manager client manages physical and virtual objects. The client requires the 32-bit version of JRE 1.5.

Note: If you are installing Virtualization Manager on Linux, you must have glib installed on the management server to make use of the Network (Image) Boot feature. If your management server is running X Windows or Gnome you have glib installed. If glib is not installed, the following error message appears in the log:

/opt/VirtualIron/VirtualizationManager/system/log/nbd-server.log contains bin/nbd-server: error while loading shared libraries: libglib-2.0.so.0: cannot open shared object file: No such file or directory

GOSs Supported by Virtual Servers

Virtual Iron® Enterprise Edition enables administrators to configure and manage multiple guest operating systems (GOSs), of different types and versions, on a single managed node. Virtual Iron® supports virtual servers running the following OSs and versions. • RHEL3U8 32bit • RHEL4U4AS 32bit and 64bit • RHEL4U5AS 32bit and 64bit • Oracle Unbreakable Linux 4U4 32bit and 64bit • Oracle Unbreakable Linux4U5 32bit and 64bit • SLES9U3 32bit and 64bit • SLES9U3 64bit • Windows 2000 32bit • Windows XP Professional SP2 32bit • Windows 2003 server R2 32bit and 64bit • Windows Vista 32bit • Cent OS 4.4 Languages Supported

In addition to English, in this release, Virtual Iron supports installations on Jap- anese and German operating systems. Expanded and localized support will be available in future releases.

16 Virtualization Manager™ Administrator Guide P RODUCT Management Operations C ONFIGURATIONS • • used inthe explanations that follow. multiple nodes. To distinguish howthese scenarios differ, several terms are for virtualservertraffic. Thisscenari also configure theproduct touseone networkformanagement, andanother the mostoften usedif you are virtual configure the product to useasinglenetwork.Thisisthe simplest case, and The scenarios thatfollow describe how • • Edition. Virtual Iron® comes in twoeditions: the Single ServerEdition and Enterprise aged nodes tobe connected tothe samesubnet. connected witha management node. Itis vital for themanagement andman- When running Virtual Iron® EE,asetofone ormoremanaged nodes isinter- A boot the Virtual Iron® software oneach node. nodes. In this scenario, it isadvisabl to management traffic between Vi A node, running eitherWindows® or Linux®. When using thisproduct, Virtualization Manager isinstalled on aseparate Virtual Iron® EE virtualizes theresourcesof multiple managed nodes. another node asneeded. one node to another inthe event ofa failure,and move non-disruptively to of resources. Virtual serverscreated a management perspective, the product Virtual IronEnterpriseEdition(EE) specific setofapplications. ers on thisnode, eachrunning a separate guestoperating systemwith a managed node. You canconfigureand Virtual Iron®SingleServerEdition (SSE) one or morenodes. one public network dedicated management network isanetworkthatusedfor ordinary network traffic by o ismostoften thecase whenmanaging izing asingle managed node. You can rtualization Manager andmanaged INSTALLING VIRTUALIRON® runs onmultiple managed nodes. From e to use the dedicated networkto PXE- is a networkthatis to configureVirtual Iron®.You can in thisenvironmentcanmigrate from manage manydistinctvirtualserv- treats thesenodesasasingle pool isdesigned torun on asingle Product Configurations entirely dedicated

. . . . . Chapter 2 INSTALLING VIRTUAL IRON® Product Configurations

Product Configuration, Enterprise Edition

If you are virtualizing multiple nodes, connect each managed node to the management server (via the dedicated management network), and to one or more public networks. Figure 8 shows a typical configuration. In this case, three systems are connected by a dedicated management Ethernet network, which is used exclu- sively by Virtualization Manager to PXE-boot and manage these nodes. This network is shown as a dashed green line. The managed nodes are also connected to a public network; this connection is used by the virtual servers hosted on each managed node. It is never used for Virtual Iron® management traffic.

Figure 8. Three Managed Nodes, dedicated management network

PXE Booting Managed Nodes

To PXE-boot managed nodes, follow these steps: Step 1. Connect all nodes to the machine hosting Virtual Iron® Virtualization Manager. Step 2. Make sure the BIOS of each node is configured so that PXE or Net- work boot precedes other methods in the boot order. Step 3. Boot each managed node.

18 Virtualization Manager™ Administrator Guide M ANAGED Configure IPMIor Virtualization Processor N ODE tab. Then select To configureIPMIorILO for a node, click up and shut downthe node from Virtualization Manager™. protocols, you need toconfigure the node soVirtual Iron®isenabled tostart ornodesIf thenodemanaging youare Virtual with Iron®supporttheseof one However, some nodes do notsupport either ofthese protocols. gent Platform Management Interface) and ILO(Integrated Lights Out). sole. Two protocols commonlyusedto prov Some serversare designed tobe start sions for eachnode aresettoONwhenchecking thenode’s BIOSsettings. extensionsIntel®-VT node forthe aresettoOFF. Intel®-VT Besurethe exten- tualization technology (VT)support. In nodes soldby some vendors, the The Virtual Iron® frameworkoperates only inIntel® and AMD® nodes with vir- • • • include: perform foreach typeof node will vary, depending on thevendor. They specially prepared by editing theBIOSsetting of eachnode. The tasks you The managed nodes youwillusein theVirtual Iron®framework need tobe C Disabling Hyperthreading Support Configure IPMI or ILOforeach Node Virtualization Processor Settings of EachNode ONFIGURATION ILO foreachNode Edit Settings ofEachNode andprovide ILOorIPMIinformation. See INSTALLING VIRTUALIRON® ed up orshutdown fromaremotecon- Hardware ide this capability are IPMI (Intelli- Managed Node Configuration and selectthe Summary Figure 9 .

. . . . . Chapter 2 INSTALLING VIRTUAL IRON® Managed Node Configuration

Figure 9. Configuring IPMI or ILO Information

Disabling Hyperthreading Support

Virtual Iron® recommends that hyperthreading be set to OFF on Intel® nodes. To do this, restart your managed node and enter the BIOS on startup. Disable the hyperthreading support in BIOS. On most computers hyperthreading is located in the Main BIOS Settings menu. On HP servers it is in the Advanced menu-->Power-On Options submenu.

Note: Turning Hyperthreading ON may adversely affect the performance of certain classes of applications.

20 Virtualization Manager™ Administrator Guide S ITE Defining NetworkConnections Define thePhysicalInfrastructure P REPARATION each toLab 2,and so on. the same subnet—Eth0 connects each Note that each same-numbered Ethernet portineachnode isconnected to Figure 10 onnetworkB,C,orD. VDC, resources more efficiently, redeploythe application toanother node inthe cycles available on that node, butitis network A.Thisapplication normally For example, youmaybe runninga data agement, troubleshooting, and configuration ofphysical nodes. node cabledto its subnets usingthesame-numbered portsthe simplifies man- another node without losingaccess toits network(s).In addition, having each This schemegives you the flexibilityto on eachnode tosubnet A,Eth1to subnet B,and so on. node shouldhavethe sameconnection sc In eachVDC,attachnode eachsame subnets. tothe Asabestpractice, each administrative entities called In the open Virtual Iron® framework, virtualizednodes are partitioned into Some additional planning isneeded when shooting and adding, replacing, orupgrading nodes. Before setting upa lab, adopt a set ofcabling conventions tosimplifytrouble- nodes in the Virtual Iron® framework. The sectionsthatfollowcoverthe key c Details onplanningthese connections are in • • connected towhichsubnets. Usethese guidelines: To make efficient useofnetwork resources, map outwhichnodes/ports are resources. that all nodes in each VDCcan access the same networks, andthe same SAN up the physicalinfrastructure that underlieseachset ofvirtualizednodes so connections withinmake networkandSAN each VDCinaconsistent way. Set To derive maximumvalue fromyour virtualinfrastructure,itisimportant to Connect theport/slots in eachnode inthe same manner. Connect each node tothe samephysical subnets. showsthree nodes, each ofwhic virtual data centers consumes ahigh-percentage of the INSTALLING VIRTUALIRON® now runningat 5%of capacity. To use migrate a virtual server onone node to onsiderations relating node tosubnet Lab1, Eth1connects processing application on anode in heme. Forexample,connect Eth0 implementing virtual infrastructure. h isconnected to four subnets. cluded in thesectionsthatfollow. , orVDCs. to thecablingof Site Preparation

. . . . . Chapter 2 INSTALLING VIRTUAL IRON® Site Preparation

Figure 10. Network Connection Scheme for Managed Nodes

22 Virtualization Manager™ Administrator Guide Connecting Nodestoth Figure 11.Figure perVDC Scheme SAN Connection • • erations inmind. Before youconnect nodes to the SANinfr covery between existing nodes. gets/LUNs. Thisiswhat enables LiveMigration,LiveCapacity, and LiveRe- that thevirtualservershostedassures tar- byeachnodehave accesstoall Be sure thateach node isconnect switches. Adopt a consistent connection sc e SANInfrastructure heme between HBAs/ports and SAN ed to eachenterprise SANswitch.This INSTALLING VIRTUALIRON® astructure, bear the following consid- Site Preparation

. . . . . Chapter 2 INSTALLING VIRTUAL IRON® Installing Virtual Iron®

INSTALLING VIRTUAL IRON®

The following instructions describe how to install Virtual Iron® on multiple managed nodes. For instructions on installing the product on a single server, see the Virtual Iron® Virtualization Manager™ Single Server Edition Getting Started Guide. Before installation...

Before installing the product, interconnect the Virtualization Manager node with managed nodes in your data center, and set the managed nodes to PXE or network boot. See Managed Node Configuration for information on preparing managed nodes. Virtual Iron® runs on the Linux® and Windows® systems listed in Product Requirements. Install the software on the system designated as the management server node in Figure 7. This system hosts the Virtualization Manager®, which is used to configure, start, and manage virtual servers on one or more nodes. Before installing the product, check the requirements provided in Prod- uct Requirements. Then proceed as follows: Step 1. To install Virtual Iron®, proceed as follows.

For Linux: Execute the bin file as follows: # sh ./VirtualIronInstall4xx.bin

For Windows®: Double click this file: VirtualIronInstall4xx.exe The following screen appears as the installation begins.

24 Virtualization Manager™ Administrator Guide Step 3. Step 2. Next When the download completes, the introductory screen appears. Click In the next screen, choose the nextscreen, In ing the installation. Manager maynot function properly. Resolve thisissue before continu- Use windowinPort appears or TFTP warningDHCP thatVirtualization Enterprise Edition To PXE-bootmanagednodes At thispoint,the installation pr uct. DHCP port 67 orTFTP port69 is in useon the installation host. tobegin the installation. ), theseports are required. If either port is inuse,a Install (asexplainedin INSTALLING VIRTUALIRON® ocess checksto see whether standard foran initial installation of theprod- Product Configuration, Installing Virtual Iron®

. . . . . Chapter 2 INSTALLING VIRTUAL IRON® Installing Virtual Iron®

Choose Reconfiguration if you need to make changes to an existing configuration. Such changes may include changing the Admin password chosen during the original installation, changing the location of the installation, or changing information on networks. Step 4. Click Next.

Step 5. If you chose the install option, you are prompted to read and accept the Virtual Iron® license agreement. You must accept the agreement to continue the installation.

26 Virtualization Manager™ Administrator Guide Step 6. For Linux, you willsee thisscreen: Next, choose a locationfor the installation. You can enter apath for the /opt/VirtuaIIron installation, or choose the defau . After selectinga location, click INSTALLING VIRTUALIRON® lt folder. (ForLinux, thisis Next Installing Virtual Iron® .

. . . . . Chapter 2 INSTALLING VIRTUAL IRON® Installing Virtual Iron®

For Windows®, you will see this screen:

If a previous installation of the product is discovered, the following warning appears. Click Uninstall to remove the existing product and install the current version, or Exit Installation to exit the installation.

Step 7. Enter the location of the Virtual Iron license file. This file is not included in the distribution, but is sent to you by Virtual Iron®. (The example shown is from a Windows® installation.)

28 Virtualization Manager™ Administrator Guide Step 8. Reconfiguration Only Note: To change the adminpassword at alater time,re-run theinstaller in appears prompting youtoreenter the password. If your password and confirmation do not match, an error message Enter anAdminpassword for thesystem. The password andconfirma- tem later! long. tion password you choose must match, and mustbe 6-32 characters Remember this password as youwillneed it to log into thesys- mode. INSTALLING VIRTUALIRON® Installing Virtual Iron®

. . . . . Chapter 2 INSTALLING VIRTUAL IRON® Installing Virtual Iron®

Step 9. Choose HTTP or HTTPS for the connection type to use between the Virtualization Manager client and server.

30 Virtualization Manager™ Administrator Guide Step 10. If you choose If you select you to choose aport or use default port 80. choose an unusedport. the port isunavailable, apop-up window appears, informingyouto The installer validates the availabili vide passwords for thekeystore. also select your ownkeystore. Ifyouchoosetodo this,youmustpro- dow shown isfrom a Linux installation.) If you havechosen HTTPS, the following window appears. (The win- HTTPS HTTP , the window shownbelow appears. Thisallows , select a portor use default port443. You can INSTALLING VIRTUALIRON® ty ofthe portyouhave chosen.If Installing Virtual Iron®

. . . . . Chapter 2 INSTALLING VIRTUAL IRON® Installing Virtual Iron®

Step 11.If you chose a certificate keystore in the preceding step, enter passwords for the keystore and the certificate key. Step 12.The illustration that appears at this point shows a representative configuration of the management network. Note that two networks are present. The Virtual Iron management network is a private network between the Virtualization Manager and all managed nodes. These nodes are also connected to a public network.

Click Next to continue. Step 13.Assign the IP addresses that the Virtualization Manager uses to connect to the private management network and the public network.

32 Virtualization Manager™ Administrator Guide VIRTUALIZATION ANDDATA MANAGER PROTECTION Step 14. See to runregularly scheduled backups. ate the Virtualization Manager with aU a result,somecriticalAs version. data practiceis abestIt tooper- maybelost. To be fullyfunctional againmay requir most current statistics collection, co configured withwrite-caching isimproperlyshutdown. Thiscould affect the a lossof poweror a management server connected toa storage subsystem As with anydatabase-based product, database should be configured asanalways-on product. to run evenwhen the Virtualization Manager isnot, the Virtualization Manager capable ofmaintaining criticalapplic Virtualization Manager needs tobe deploy Performing Backup and Restore Operations gate to theDeviceManager: to store the Virtualization Manager database. Dothefollowing to navi- tection For systems running Windows, if youselect imum of 7200 RPM. affected, Virtualdisks capable Ironrecommends min- ofoperatingata disk before proceeding. To ensure that performance isnot adversely VirtualizationManager towait untilthedatato the iscompletely written Select restoring the database and could result inlost data. corruption in the event ofa powerinterruption. This would require If your systemisnotprotected byaUPS,there is a riskofdatabase Optimize fordata protection , youalsoneed todisablewriteca nfiguration changes, and logfileupdates. ations. Although Virtual Servers continue INSTALLING VIRTUALIRON® e restoring the database with a backup PS (uninterruptible powersupply)and ed and runningon aplatform that is to reducethisrisk. This causes corruption canoccur if there is for additional information. chingthe on used diskthat is Optimize fordata pro- Installing Virtual Iron®

. . . . . Chapter 2 INSTALLING VIRTUAL IRON® Installing Virtual Iron®

• Right-click My Computer and then click Properties. • Click the Hardware tab. • Click Device Manger. • Click the plus sign (+) next to the Disk Drives branch to expand it. • Right-click the drive on which you want to enable or disable disk- write caching, and then click Properties.

• Click the Policies tab.

• Click to clear (uncheck) the Enable write caching option.

34 Virtualization Manager™ Administrator Guide Step 16. Step 15. • matically. (Example: Windows® installation). Virtualization Manager starts auto- for aWindows®installation.) ceed withthe installation, click Manager Install windowdisplaysa When the installation is complete, click After makingyourdatabase optimization selection, the Virtualization Click OK . INSTALLING VIRTUALIRON® Install pre-installation summary. To pro- . (Theexample shownhere is Done to close the window. Installing Virtual Iron®

. . . . . Chapter 2 INSTALLING VIRTUAL IRON® Installing Virtual Iron®

36 Virtualization Manager™ Administrator Guide 3

CONFIGURING NETWORKS

......

Connecting to the Virtualization Manager...... 38 Mapping Physical Ports to Logical Networks...... 40 Creating Networks ...... 43 Configuring Ethernet Networks...... 45 Configuring iSCSI Connectivity ...... 47 Configuring VLANs ...... 52

37 Chapter 3 CONFIGURING NETWORKS Connecting to the Virtualization Manager

CONNECTING TO THE VIRTUALIZATION MANAGER

After installing Virtual Iron®, use a web browser to connect to the Virtualization Manager node (the node on which you installed the product). Step 1. For the URL, use the IP address assigned to the management Ether- net interface. Step 2. On the Virtual Iron® screen, click Virtualization Manager.

Figure 12. Initial Connection Screen

38 Virtualization Manager™ Administrator Guide Step 4. Step 3. Figure 13. Login Screen Virtualization Manager opens. Manager, and click Enter the Password you specified The application starts, andyouare pr OK . Connecting to the Virtualization Manager CONFIGURING NETWORKS CONFIGURING when you installed Virtualization esented withthislogin screen.

. . . . . Chapter 3 CONFIGURING NETWORKS Mapping Physical Ports to Logical Networks

MAPPING PHYSICAL PORTS TO LOGICAL NETWORKS

Before configuring networks, you will map all available ports to the set of logical Ethernet networks created within Virtualization Manager. This involves the following tasks: • Logically connecting all ports on each node in the Resource Center to the networks you want them to use. • Defining and specifying a name or alias for each network. The name should be a recognizable name that has to do with the network’s use. Defining Networks in a Virtualized Environment

When nodes boot in the Virtual Iron® framework, information about the components of each node is displayed on Virtualization Manager. Each managed node is shown on the Virtualization Manager user interface, along with its Ethernet cards and ports. Step 1. Connect a port to a network. Plug a managed node into a physical network you want it to use. In Virtualiza- tion Manager, click the Hardware button. Select the Networks tab. The port you connected shows up in the bottom of the Networks window with have a status of Up, as shown in Figure 14.

Figure 14. Ethernet card and port information

Port is Up

40 Virtualization Manager™ Administrator Guide Step 2. Figure 15. Adding Ethernet Network Names Network Ethernet 15. Adding Figure work name and click by selecting the work. Addthese logicalnames tothe Virtualization Manager database The symbolicnames you choose shouldrelateto the usesof thenet- Enter the names for physicalnetworks used by virtual servers. Networks Next . tab as shownin MappingPorts Physical CONFIGURING NETWORKS CONFIGURING Figure 15 to Logical Networks . Enter thenet-

. . . . . Chapter 3 CONFIGURING NETWORKS Mapping Physical Ports to Logical Networks

Step 3. Virtualization Manager displays the window shown in Figure 16. Use this window to assign the node you just connected (in this case, port 1 on node tst 111) to the symbolic Ethernet name chosen for that network. Select the network name from the pull-down.

Figure 16. Associate a physical card/port with a symbolic network name

Step 4. Repeat this procedure for each card/port, until you have assigned each physical port to one of the symbolic names chosen for your public networks.

42 Virtualization Manager™ Administrator Guide C REATING Configuring Networks,Enterprise DEFAULT MANAGEMENT NETWORK, ENTERPRISE EDITION NETWORK,ENTERPRISE MANAGEMENT DEFAULT N ETWORKS ment. of thisnetwork isits class C IP address. The typeofthis network is networkmanagement isdetectedanddisp over adedicated Ethernet network,in Virtual Iron EnterpriseEdition (EE)requires that you manage systemnodes tion you are using. View. The information that appears on this tab depends on the Virtual Iron edi- Begin the configuration process byselectingtheNetworkstab intheHardware • • • lowing sections. how toconfigureEthernet ports tosupport multiple VLANs.Itcontains the fol- This section describes how toconfigure Ethernet and iSCSI networks,and Configuring VLANs Configuring iSCSI Connectivity Configuring Ethernet Networks See example in Figure 17. Initial Network, Configuration - Enterprise Edition Figure 17 andSingleServerEditions . stead ofapublicnetwork.Thededicated CONFIGURING NETWORKS CONFIGURING layed for you. By default, the name Creating Networks Manage-

. . . . . Chapter 3 CONFIGURING NETWORKS Creating Networks

DEFAULT PUBLIC NETWORK, SINGLE SERVER EDITION If you are using Virtual Iron Single Server Edition (SSE), you are managing a single server over a public network. In this case, the name of this network is vi_public. The network’s type is Ethernet. An example is shown in Figure 18.

Figure 18. Initial Network, Configuration - Single Server Edition

44 Virtualization Manager™ Administrator Guide Configuring Ethernet Networks Step 2. Step 1. To configureEthernet networks, proceedasfollows. Step 3. Figure 19. Configuring Ethernet Networks the pop-up menuas shownin Select and right click In the Hardware view, selectthe In the Click mation on configuring iSCSI. ing on theiSCSI button. See are creating. Atthispoint, youcan Next>> Create Networks to continue. to Networks dialog box, enter a name for the network you Configuring iSCSIConnectivity Figure 19 , andchoose Networks CONFIGURING NETWORKS CONFIGURING mark the network as iSCSI by click- by iSCSI as network the mark . tab. Create Networks... Create Creating Networks forinfor- from

. . . . . Chapter 3 CONFIGURING NETWORKS Creating Networks

Step 4. The Assign Ports window shown in Figure 20 appears. To assign a port to the network, select the port in the Unassigned Ports pane. Then click Add>>. The port moves to the Assigned Ports pane on the right. Click Finish when all ports are assigned.-

Figure 20. Assigning Ports to Networks

The Ethernet network you have created appears in the Network tab (Figure 21). Its type is Ethernet. Note that the port you have assigned to the network appears in the Ports area.

46 Virtualization Manager™ Administrator Guide Configuring iSCSIConnectivity network LabNet-1 network Ethernet with Port associated LabNet-1 network Ethernet Step 2. Step 1. resources. To configure aniSCSInetwork and addiSCSI ports: Virtual Iron® supports iSCSIconnections between managed nodes and SAN storage traffic andbetter performance. work that isnotaccessible Note: HBA or other dedicated FC device. has distinct advantages. Sinceit runs over Ethernet, itdoes not requirean iSCSI performsthe same basic functi internet. Though itrunsatlower bandwidth than Fibre Channel networks, connection to data storage facilities over local and wide area networks and the Internet SCSI(iSCSI) isan IP-basedstorage networkingstandard that allows Virtual Iron® recommends that the iSCSInetwork is on a dedicated net- Figure 21. Configured Ethernet Network and Associated Port Network Associated and 21. Ethernet Configured Figure the pop-up menuas shownin Select and right click Click the Hardware to virtualservers. Thisassuresthesecurityof button. Select the Networks on asFibre Channel. However, iSCSI Figure 19 , andchoose CONFIGURING NETWORKS CONFIGURING Networks . Create Networks... Create tab. Creating Networks from

. . . . . Chapter 3 CONFIGURING NETWORKS Creating Networks

Figure 22. Configuring iSCSI Connections

Enter a Network name

Select iSCSI Network

48 Virtualization Manager™ Administrator Guide Step 3. Figure 23. Assigning Ports to iSCSI Connections shown in Check select the port in the you have finished assigning ports. port moves tothe iSCSI Network Figure 23 Assigned Ports appears. Toconnection, a porttotheiSCSI assign Unassigned Ports and click Next>> CONFIGURING NETWORKS CONFIGURING panethe on right. Click . The Assign Ports window paneclick and Creating Networks Add>> Next . The when

. . . . . Chapter 3 CONFIGURING NETWORKS Creating Networks

Step 4. Use the window shown in Figure 24 to change iSCSI port information as needed.

Figure 24. Adding iSCSI Port Information

Edit iSCSI port information

By default, DHCP is used to configure the IP address of the iSCSI port. An initiator name is provided by Virtualization Manager. You can use this window to assign a new initiator name, and/or a static IP address and mask. After making all changes, click OK to accept the changes and close the Edit window. Then click Next>. Step 5. Use the window that appears to add IP addresses of the iSCSI servers reachable on this connection. Add an alternative connection port for iSCSI servers as needed. Click Add to add a new connection, and key in the IP address. Click OK when finished.

50 Virtualization Manager™ Administrator Guide Step 6. Figure 25. Adding iSCSI Server Information After rebooting the node, theiSCS icon. In addition, thisnode isplaced in awarningstate, indicated by a yellow to reboot the node that ownstheiSCSIport you haveconfigured: The systemdisplays the followingmessage, indicating that you need CONFIGURING NETWORKS CONFIGURING I configurationiscomplete. Creating Networks

. . . . . Chapter 3 CONFIGURING NETWORKS Creating Networks

Configuring VLANs

Virtual Iron supports multiple Virtual LANs (VLANs) on the same port. Each VLAN is essentially an independent logical network operating with other VLANs over the same physical connection. Configuring VLANs involves creating one or more VLAN Groups, each of which can house multiple VLANs. Each VLAN is assigned a distinct VLAN identification. The VLAN ID is used by an attached VLAN switch to segregate traffic among the different VLANs operating on the same link. Once a VLAN is configured, it functions exactly like a separate physical connection. It is important to coordinate VLAN configuration with the administrator of attached VLAN switches, so that appropriate VLAN IDs are assigned to the VLANs you configure. Step 1. In the Hardware view, select the Networks tab. Step 2. Select and right click VLAN Groups, and choose Create Group... from the pop-up menu as shown in Figure 19.

Figure 26. Configuring VLAN Groups

52 Virtualization Manager™ Administrator Guide Step 4. Step 3. Figure 27. Assigning Ports to aVLAN Group Ports click VLAN Group, select the port inthe Click Select theVLANgroup youhave created and choose Enter aname for theVLANGroupand click Click to 4095. VLANmust beintherangeof2 connection,IDs VLAN andaVLAN ID. from the pop-up window asshownin Add>> Finish OK windowshownin . . The port movesport. The tothe whenyouhave finished assigning ports. Figure 27 CONFIGURING NETWORKS CONFIGURING appears. To assign aport tothe Unassigned Ports Assigned Ports Figure 28 Next>> . Addthe name ofthe . The pane ontheright. Creating Networks Create VLAN Create pane. Then Assign

. . . . . Chapter 3 CONFIGURING NETWORKS Creating Networks

Figure 28. Create VLAN

Step 5. The VLAN Group and VLAN you have created appear in the network window as shown in Figure 29. Repeat this process to add additional VLANs as required.

Figure 29. VLAN Created

54 Virtualization Manager™ Administrator Guide 4

USING ADMINISTRATION MANAGER®

......

Using the Administration Manager ...... 57 Applying a New License File ...... 58 Upgrading to a New Version of the Product ...... 58 Put/Get Files on the Virtualization Manager ...... 58 Backing up the Virtualization Manager Database...... 60 Restoring to a Backup Version of the Database...... 60 Restarting Virtualization Manager Services...... 61 Reloading Virtualization Manager...... 61 Running a Command on Virtualization Manager...... 62

55 Chapter 4 USING ADMINISTRATION MANAGER® About the Administration Manager

ABOUT THE ADMINISTRATION MANAGER

The Virtual Iron® Administration Manager application is available from the product launcher page. The Administration Manager offers different controls for the Single Server and Enterprise Editions of Virtual Iron®. The Enterprise Edition does not currently support Restart or Run Command via the Adminis- tration Manager. Figure 30 shows the controls available for each version of Virtual Iron®.

Figure 30. Administration Manager, Single Server and Enterprise Editions

Single Server Edition Enterprise Edition

56 Virtualization Manager™ Administrator Guide U tion Manager tion Administra- Launch SING

THE A DMINISTRATION during installation. your Admin user nameandpassword. Usethe nameand password chosen Edition. When you launch the AdministrationManager, you areprompted for in Access the AdministrationManager from • • • • • • Figure 31. Administration Figure Manager • • number ofkeytasks. Theseinclude: The Virtualization Manager Administra Figure 31 Running aCommand onVirtualization Manager Reloading Virtualization Manager Restarting Virtualization Manager Services Restoring to a BackupVersion ofthe Database Backing up theVirtualization Manager Database Put/Get Fileson theVirtualization Manager Upgrading toa New Version of the Product Applying a NewLicense File . Thisfigureshowsthe controls th M ANAGER USING ADMINISTRATION MANAGER® ADMINISTRATION USING (SSEonly) tion Manager providesaccesstoa the productlauncher page asshown (SSEonly) at appear inthe Single Server (SSEonly) Using the AdministrationUsing the Manager (SSEonly)

. . . . . Chapter 4 USING ADMINISTRATION MANAGER® Using the Administration Manager

Applying a New License File

Choose this option to apply the license provided by Virtual Iron®. Product licenses are available from www.virtualiron.com/free. Upgrading to a New Version of the Product

If you are using Virtual Iron® Single Server Edition (SSE), you can use this option to upgrade to a new version of the product.

Note: After an upgrade, it is a best practice to delete all previous versions of Virtualization Manager. From your computer’s Start menu, select Run, and enter javaws -viewer. Delete all previous versions.

Put/Get Files on the Virtualization Manager

To move files to and from Virtualization Manager, bring up the Administration Manager and click the down arrow to choose Put a file... or Get a file..., as shown. For example, you can move an iso to the NBD (Network Block Device) directory on Virtualization Manager, making this image available for booting by virtual servers.

Note: When performing put or get operations, proceed with caution. Adminis- tration Manager does not warn if moving a file will overwrite a file in either the source or destination directory.

58 Virtualization Manager™ Administrator Guide iso, andclick Choose adestination directory onthe Virtualization Manager serverforthe Open Browse the folders on your systemtofindan appropriate iso image.Click asshown. Save . Do not enter afilenamein thefilename field USING ADMINISTRATION MANAGER® ADMINISTRATION USING Using the AdministrationUsing the Manager .

. . . . . Chapter 4 USING ADMINISTRATION MANAGER® Using the Administration Manager

Backing up the Virtualization Manager Database

Choose Backup to create a backup of the current database. When the backup operation completes, you are informed of the filename as follows.

Restoring to a Backup Version of the Database

Choose Restore to restore a backed up database. You are provided with a list of available backup copies to choose from.

Note: If you are running Virtual Iron® Enterprise Edition, Restore is not supported in the Administration Manager. See Restoring the Configuration Data- base for instructions on restoring a backed-up system.

60 Virtualization Manager™ Administrator Guide Reloading VirtualizationManager Restarting VirtualizationManagerServices Restart server database and start with anew database. Access Use the the database remains intact. cally disconnects all clients connected to themanagement server. Alldata in restart Virtualization services. Restarting Manager’s these services automati- If youareusingVirtual Iron® SingleServ ing dialog. Reload action with caution and under special circumstances. When you attemptto Note: Information deleted from a database can notbe recovered. Take this , a warning appears. To proceed, click button asshown: Reload command if youwantto delete the current management USING ADMINISTRATION MANAGER® ADMINISTRATION USING er Edition(SSE),usethisoptionto OK Using the AdministrationUsing the Manager . To cancel, close thewarn- Reload from the from

. . . . . Chapter 4 USING ADMINISTRATION MANAGER® Using the Administration Manager

Running a Command on Virtualization Manager

If you are using Virtual Iron® SSE, use the Run Command option to run a command on the Virtualization Manager server.

Note: The ability to run commands on the management server is provided for advanced debugging purposes. It is not intended for day-to-day operations. This command requires familiarity with the UNIX operating system.

62 Virtualization Manager™ Administrator Guide 5

USING VIRTUALIZATION MANAGER®

......

Using the Integrated Tutorial ...... 64 Virtualization Manager Overview...... 65 Using the Application Toolbar ...... 66 Navigation Tree ...... 72 Using the Pull-down Menus and Action Toolbar ...... 74 About the Jobs Framework...... 78 Performing Job Operations...... 81

63 Chapter 5 USING VIRTUALIZATION MANAGER® Using the Integrated Tutorial

USING THE INTEGRATED TUTORIAL

Virtual Iron® includes a tutorial that opens when you first connect to Virtualiza- tion Manager. The tutorial provides a high-level look at the product, with instructions on how to configure and start a virtual server. The tutorial takes about 10 minutes and provides an introduction to the design of the management framework and the controls that make up the client interface. You can open or close the tutorial at any time by using the Show tutorial check box on the Help pulldown (see Figure 32).

Figure 32. Open the Tutorial

Product tutorial

64 Virtualization Manager™ Administrator Guide V tree Navigation menus Pull-down toolbar Action tion toolbar tion Applica- Panels Summary showing pane, ment Manage- IRTUALIZATION with the product. one another. Using theintegratedis thebest tutorial waytofamiliarize yourself The sectionsthatfollow describe each set of controls andtheir relationship to • • • • • Figure 33. Overview of Client Design ofClient 33. Overview Figure tion. Theclient organizes these controls infiveareas (see down menus,andtabs foraccess tovari The Virtualization Manager client provi and integrated database, and aweb-based management user interface. ager™, a transaction-based framework that agement for thisenvironmentisprovided which tocreate and manage Installing andconfiguring Virtual Iron® creates a M Management pane Application toolbar Navigation tree Action toolbar menus Pull-down ANAGER O VERVIEW USING VIRTUALIZATION MANAGER® VIRTUALIZATION USING virtual servers des asetofworkareas,buttons, pull- ous functions and areasofconfigura- by Virtual Iron® Virtualization Man- on a set of consists aVirtualization Manager Virtualization ManagerOverview virtualization environment managed nodes Figure 33 ): . Man- in

. . . . . Chapter 5 USING VIRTUALIZATION MANAGER® Using the Application Toolbar

USING THE APPLICATION TOOLBAR

The Application Toolbar buttons define the functional areas for operations performed in the Virtual Iron® framework. Resource Center

Click Resource Center in the Application toolbar to manage virtual data centers (VDCs), managed nodes, and virtual servers. It is in the Resource Center that you create VDCs, assign managed nodes to VDCs, and then create and configure virtual servers on the nodes. Resource Center is the top-level object in the navigation tree. A sample of the tree is shown in Figure 34.

Figure 34. Resource Center, Selected in Navigation Tree

RESOURCE CENTER TABS Click the tabs in the Resource Center management pane to configure and provide information on nodes, VDCs, and virtual servers. Click the Events tab for information on all objects in the Resource Center. See Figure 35.

Figure 35. Resource Center Tabs

66 Virtualization Manager™ Administrator Guide on port Information selected Port Policies andReports Hardware REPORTS the cardisdisplayed inthe Fibre Channel card. Inthiscase, anEthernet port isselected. Information on and tst119. Each of thesenodes has an Ethernet card, CDROMdrive, anda Figure 36 and their components, and to configure these components. • • • the outputformat.ues) for for somereports you may choose either HTML or CSV(comma separated val- environment ortogenerate reports according tocriteria youspecify. Notethat Select from theoptions toconfigurepolic scheduled. Note the PolicyKeyin titlebar, which indicates status. The Policiesand Reports pane show Reports, User Policies, and SystemPolicies arelisted in the navigation tree. When youclick Figure 36. Hardware Vi Click specific nodes in the virtual data center. In addition, youcanapply these NodeReport—In theSummarypane, specify report criteria for allnodesor a report thatshows all jobsperformedduring that period. JobReport—Use the Summarypane tosetthe frequency ordate range for date range, and event type to be reported: Informational, Warning, or Error. EventReport—Usetabs the with this option associated to set thefrequency, Hardware shows a samplea display shows oftheHardwareviewwithtwonodes,tst111 inthe Application toolbar forinformation on Policies and Reports ew, Ethernet Info USING VIRTUALIZATION MANAGER® VIRTUALIZATION USING pane. Port Selected s whichpolicies areconfigured and inthe Application toolbar, options for ies that affect virtualservers inthe Using the Application Toolbar managed nodes

. . . . . Chapter 5 USING VIRTUALIZATION MANAGER® Using the Application Toolbar

criteria to all or a selected virtual data center, and whether the report output is applied to groups, volumes, or virtual disks. • VirtualDisksReport—You may select various combinations of specific types and states of virtual disks. You may choose to limit output to groups, volumes, or virtual disks. • VirtualServerReport—You may select various combinations of criteria for virtual servers from all or a specific virtual data center.

USER POLICIES Configure these policies to alert a user of specific events, configure criteria for rebooting selected nodes, or scheduling backups. • EmailNotifier—Set up email notification for specified users whenever a specified node, virtual server, or virtual data center experiences a specified event category. • RebootDataCenter—Use this option to set reboot rules for all data centers or each data center. • SystemBackup—Use this option to set the location for a backed-up Virtual- ization Manager database, and the number of backups to retain.

SYSTEM POLICIES System policies apply to the environment as a whole. • AutoRecovery—Choose this option to schedule AutoRecovery frequency, from hourly to weekly, for the period you specify. • LiveCapacity—Choose this option to schedule LiveRecovery frequency, from hourly to weekly, for the period you specify. • TechnicalSupport—Select this option to access Virtual Iron Technical Sup- port via email. Figure 37 shows a sample of the Policies and Reports area. See About Poli- cies and Reports for more information.

68 Virtualization Manager™ Administrator Guide reports generate policies, Configure Jobs A sample of theJobsviewis shown in • • • • • Iron® database. Examplesofoperations include: operations made within the environment that havebeen entered to the Virtual that have been completed inthe environment.A job isasetof oneor more Click 37. Reports Policiesand Figure View Adding, changing, ordeleting policies Discovering physical resources ory, adding processors) Reconfiguring aVS(for example, in Adding, renaming, ordeleting aVDCorVS Adding ordeleting auser Jobs inthe Application toolbar forinformation oncurrentand past tasks USING VIRTUALIZATION MANAGER® VIRTUALIZATION USING creasing or decreasingallocated mem- Figure 38 . Using the Application Toolbar

. . . . . Chapter 5 USING VIRTUALIZATION MANAGER® Using the Application Toolbar

Figure 38. Jobs View

Get info on jobs

70 Virtualization Manager™ Administrator Guide accounts user Manage Users Figure 39. View Users Figure Iron® useraccounts. Eachuser ac Click the Users buttonApplication inthe toolbar tocreate andmanage Virtual USING VIRTUALIZATION MANAGER® VIRTUALIZATION USING count hasauniquename and password. Using the Application Toolbar

. . . . . Chapter 5 USING VIRTUALIZATION MANAGER® Navigation Tree

NAVIGATION TREE

The navigation tree shows the relationship between managed objects within the virtualization environment. These objects are both physical and virtual, and include managed nodes (and node components), virtual data centers, and virtual servers created with the software. The content of the navigation tree changes, depending on the button you click in the Application toolbar. A sample of the navigation tree for Resource Center is shown in Figure 40. This view shows the relationships between Virtual Data Centers (VDC), managed nodes, and the virtual servers (VS) hosted by those nodes. In this example, VDC Finance East contains three nodes, named Dell 380, Dell 430, and Supermicro.

Figure 40. Navigation Tree, Resource Center View

Virtual data center

Managed node

Virtual servers

Unassigned virtual servers

72 Virtualization Manager™ Administrator Guide view. Thisviewexposes thecomponents ofeachmanaged node. Figure 41. Navigation 41. Tree, Navigation Figure View Hardware Figure 41 Managed node Managed Node components Node shows asample navigationtreeasitmightappear in the USING VIRTUALIZATION MANAGER® VIRTUALIZATION USING Navigation Tree Hardware

. . . . . Chapter 5 USING VIRTUALIZATION MANAGER® Using the Pull-down Menus and Action Toolbar

USING THE PULL-DOWN MENUS AND ACTION TOOLBAR

The pull-down menus and Action Toolbar are used together to set the context for operations and to perform specific actions in the virtualization environment. Pull-Down Menus

Virtualization Manager contains a set of standard pull-down menus which are discussed briefly in the sections that follow. Some functions (Break-locks... and Verify Database... for example) are explained in detail in Performing Administrative Tasks.

Figure 42. Pull-down Menus

FILE MENU The File Menu supports the Archive Manager, VHD Repository, Update Man- ager and Exit. For information, see Configuring the Archive Manager, and VHD Repository. Use Exit to exit Virtualization Manager and exit the client UI.

Figure 43. File Menu Options

VIEW MENU The first five choices on the view menu are equivalent to the buttons in the application toolbar (see Using the Application Toolbar). • The first group of options in this menu open the same views as the icons on the toolbar. • Click Refresh to update the client UI with the latest information from the Virtualization Manager database. • Click Logs for access to node logs. These can be useful to Virtual Iron® customer support. Click Reports for an index of all reports stored in the database. See Report Types for information on generating reports.

74 Virtualization Manager™ Administrator Guide Accessing LicenseInformation DETERMINING WHATYOURDETERMINING SUPPORTS LICENSE tains one or more cores.Each and a set of shared execution resources (suchascacheand I/O). Note: The sample license shownin ports, choose To determine the type oflicense you have and the numberof sockets itsup- assigned toVSs to enable them to connect to distinct subnets. associated withvirtualNI (Media AccessControl) addresses for eachsocket. TheMAC addresses are contain asingle-core ormulti-core CPU.Eachlicense allocates10MAC Each Virtual Iron® license supports a Figure 44. View Menu Options • icons justbelow the pulldownmenus). Deselect In this context, each Applications Toolbar Help > About Cs (VNICs).During VSconfiguration, VNICsare socket USING VIRTUALIZATION MANAGER® VIRTUALIZATION USING . Selectthe Figure 45 core houses aprocessor: asingle chipthat con- to turn to off the Applicationtoolbar (the setof Using the Pull-downMenus and Action Toolbar consists ofone ormoreexecution units, specific numberof sockets thatmay supports atotal of40 sockets. License tab asshown in Figure 45

. 75

. . . . . Chapter 5 USING VIRTUALIZATION MANAGER® Using the Pull-down Menus and Action Toolbar

Figure 45. License Information

Action Toolbar

The Action Toolbar is positioned just below the pull-down menus. The icons in the Action Tool bar are arranged sequentially to support the work-flow required to create virtual servers. Use the button in the toolbar to create objects in the virtualization environment. Examples include: • Creating a virtual data center • Adding a node to a virtual data center • Creating a virtual server • Cloning a virtual server • Starting a virtual server • Creating a virtual server console • Finding an object in the environment See Figure 46.

76 Virtualization Manager™ Administrator Guide center datavirtual Create a center data virtual to a nodes Add Figure 46. Action Toolbar 46. Action Figure Icons server virtual Create a tual Server tual aVir-Clone server Start virtual server Stop virtual USING VIRTUALIZATION MANAGER® VIRTUALIZATION USING server console virtual a Open server ornode Restart virtual Using the Pull-downMenus and Action Toolbar object Find resource selected Delete interface Refresh pane jobs Hide Help Get

. . . . . Chapter 5 USING VIRTUALIZATION MANAGER® About the Jobs Framework

ABOUT THE JOBS FRAMEWORK

Virtualization Manager uses a Job Operations framework that supports a flexi- ble approach to the reconfiguration of physical and virtual objects. Managing in a Multi-User Environment

Virtualization Manager is designed for use in an environment in which a number of users may have access to the same objects. Virtualization Manager maintains an accurate and consistent view of the virtualization environment while users perform separate and simultaneous jobs. Each configuration change is a job—a transaction performed by a single user. The steps that follow describe how resources are locked and released at the start and conclusion of each job.

WHAT’S IN A JOB? A job is a configuration change that affects one or more physical or virtual objects. Examples of user operations that can be included in a job are: • Renaming a virtual data center or other object • Adding or deleting a virtual data center • Adding VNICs or to a Virtual Server • Moving a Virtual Server from one VDC to another • Deleting a Virtual Server • Changing the minimum and maximum values for a virtual server’s memory and/or CPUs ACTIONS AND JOB OPERATIONS A single job can contain one or many individual operations. The Job Operations framework employs Resource locks which appear on the management UI to show that a resource involved in a job is locked until the job completes. In Figure 47, note the yellow lock icons that mark the resources that are currently included in a job. Until the job completes, these resources are Under Construction. While in this state, they cannot be managed by any other user.

78 Virtualization Manager™ Administrator Guide locks Resource Jobs andResourceLocking LOCKS AND MULTIPLEUSERS LOCKS AND locked. Theobjects remain lockeduntil the jobs are completed. pane forhis jobs, and would seethe other’s izationUI (rather Manager™ thanviaanAPI),each would have aseparate job Commodities virtualanother data center. Atthesame time,UserB modifiesresources the of Finance-One are performedondifferentobjects. Forexample,created suppose A has User A number ofdifferent usersmayperformjobs simultaneously, providedthey boxes accessiblevia the management pane. tion tree, orinthein thedrop-down caseofFreeorUnassignednodes, combo stateThe locked a smalllockiconwhich isindicatedin thenaviga- appears by state of objects that are state of thevirtualization environmentis The state oflockedobjects cannot be known until thelocksare cleared. The accurate viewismaintained for allusers. mission level onthe objectcanunlock it.Thisassuresthat aconsistent and ronmentis completed until thejob orcancelled. Onlyauserwith thesame per- a Objectslocked to job are involvedina Figure 47. Management UI, Showing Resource Locks virtual data center andbegins ajobbymoving nodesinto virtualdata center. Assuming eachuser isworking attheVirtual- not locked. USING VIRTUALIZATION MANAGER® VIRTUALIZATION USING alwaysaccurately reflected bythe ll otherusersintheVirtualizationenvi- objects (as wellashisown) as About the Jobs Framework

. . . . . Chapter 5 USING VIRTUALIZATION MANAGER® About the Jobs Framework

Prior to completing a job, a lock can be cleared in two ways: • By logging out the user who initiated the lock. This action can be performed by the user, or by the virtualization environment administrator. • By direct action of the virtualization environment administrator. As a job completes, its progress is shown in the Jobs progress pane. All locks are cleared when a job completes. JOB FAILURE AND ROLLBACK Job operations are validated by the Virtualization Manager as they are added to the Job tab. The failure of any operation cancels the entire job and all other operations it specifies. The state of the virtualization environment is rolled back to what it had been prior to the start of the job. All locks in the operation are released.

JOBS AND EVENTS When a job operation fails, one or more events may be generated and displayed on the Virtualization Manager™ UI. Events are flagged with yellow icons in the navigation tree. See Job Failure and Rollback. To get information on failed events, click Events in the application toolbar. This displays the Virtualization Manager™ event log.

JOB STATES While a Job is in progress, the job tab can have any of the states defined in Table 1.

Table 1. Jobs Tab States

Job State Meaning

In Progress A Job is running. Complete The Job has completed. Failed The Job has Failed. The virtualization environment has been rolled-back to its previous state and all locks have been released. Aborting The Job has been Aborted via console Abort command. The virtualization environment has been rolled-back to its previous state and all locks have been released.

80 Virtualization Manager™ Administrator Guide P ERFORMING About theJobsView Sort Jobsbydate J OB Figure 48. Jobs 48. View Jobs Figure cancel a job inprogress. mation onjobs completed orabortedthe in past, orforAdministrativeusers,to The jobsviewisprimarilyused toget aglobalview on jobs, to evaluate infor- or byuser. tion is compiled in a time-stamped list. J (pending), and in-progress jobsinthe comprehensive The Jobs viewprovides • • • • alization environment™. The sectionsthatfollow explain how to O Closing JobTabs Jobs Aborting Starting aJob About the Jobs View PERATIONS Sort Jobsbyuser Sort Figure 48 USING VIRTUALIZATION MANAGER® VIRTUALIZATION USING shows the jobsview. shows virtualization environment. The informa- perform joboperations within the virtu- obs can be sorted and viewedby date information on all completed, queued Performing JobOperations

. . . . . Chapter 5 USING VIRTUALIZATION MANAGER® Performing Job Operations

Starting a Job

A job begins when you make any change within the virtualization environment. Each change you make appears in the Job Operations tab as a discrete operation. Job operations can be comparatively minor actions, such as renaming a virtual server. Operations may also have a wider scope, such as the creation of a new virtual data center or virtual server, or the movement of a node from one virtual data center to another. These actions include: • Creating Virtual Data Centers • Creating and Renaming Virtual Servers • Starting or stopping Virtual Servers • Changing virtual server processor or memory settings, or boot parameters Performing any of these actions changes the configuration of the virtualization environment. This starts a Job, and opens a Job Operations tab at the bottom of the management pane to show the job’s progress. See Figure 49. Note that if you click Details, the Jobs view shown in Figure 48 appears.

Figure 49. Job Operations Tab Containing an Operations Queue

Description of the operation

Managed object

Note that the nature of each operation is captured in the Description field. The Object field shows the object under management within a numbered operation. These objects are locked until the job completes, or the operation itself is cancelled. Objects are unlocked when a job completes or when a job is aborted. Until an object is unlocked, it cannot be managed by any other user in the virtualization environment.

82 Virtualization Manager™ Administrator Guide icon Abort job Selected job Selected state Job Aborting aJobintheJobsView Aborting Jobs Figure 51. Aborting an Under Construction Job Select thejob and click Locate the job inthe navigation tree. the Jobs view. If ajobisrunningor fails to complete Button Job 50. Abort Figure server, take longer. complete quickly. Others, suchasadjusting the memory used by a virtual the pre-job state. Note that some joboperations such asrenaming an object, If you abort ajob, alloperations queued in No displays a warningmessage. Click is it cancel ajobbefore you wantto If Before a job completes, the toallowthe job to runto completion. Abort USING VIRTUALIZATION MANAGER® VIRTUALIZATION USING Abort . button appears in theJobOperationsTab. Yes completed, theVirtualizationManager™ , anAdminuser canabort the jobfrom to continue with the Abort operation, or the JobOperations Performing JobOperations tab rollbackto

. . . . . Chapter 5 USING VIRTUALIZATION MANAGER® Performing Job Operations

Determining the Cause of Job Failure

If a job succeeds, all the operations associated with it are implemented in the virtualization environment. A Job Succeeded message appears in the Job tab. If the job fails, the state of the virtualization environment returns to its pre-job state. A job failure presents Error and Details buttons on the tab. Click Details to see high-level information on all operations in the job. Click Error to open a pop-up containing information on the specific operation that failed within the Job. Closing Job Tabs

When you create a job, the Job Operations tab remains on the management UI. To clear it, press the F5 key, or click the Job control icon shown in Figure 52.

Figure 52. Job Control Icon

Clear Job tabs

84 Virtualization Manager™ Administrator Guide 6

CONFIGURING STORAGE

......

Configuring Storage...... 86 Discovery and Management of Physical Disks...... 88 Configuring Logical Disks ...... 90 Exporting and Importing ...... 94 Cloning Disks...... 99 VHD Repository...... 101

85 Chapter 6 CONFIGURING STORAGE Configuring Storage

CONFIGURING STORAGE

Virtual Servers (VSs) can be configured to access two types of disks: • Logical disks—High-performance disks that can be assigned to one or more virtual servers. The size can be smaller than the underlying physical disk. Supported on Fibre Channel, iSCSI, and local storage. • Raw SAN disks—High performance. One or more virtual servers use one entire physical LUN.

Note: For best performance, Virtual Iron recommends that all storage be in logical disks.

The following table summarizes the functional differences between these disk types.

Feature Logical Raw

Shareable between VSs X X

High-performance X X

Supported on iSCSI SAN X X

Supported on Fibre Channel SAN X X

Supported on local storage X

Ability to subdivide physical disk X

Cloning capability X

Dynamic VHD file import

Fixed VHD file import X

Export capability X

86 Virtualization Manager™ Administrator Guide Advantages of Managed Storage or more manage logical diskson theSAN. Virtualization Manager administrator can ager. Following initialinformation exchange withthe SANadministrator, the advantages. Allphysical LUNscanbe Overlaying astorage framework onavai bilities isavailable in th copied (cloned) and exported for use by different VSs.Neitherof thesecapa- work, youcreate one or more SAN disks that are accessible to managed nodes and their VSs.In this frame- Virtualization Manager presents aunified frameworkfor controlling localor logical disks . Logical diskshaveadditional e management ofraw SAN disks. disk groups administered from Virtualization Man- lable physical storage hasdistinct use thisframework toconfigure and (DGs),and subdivide them into one CONFIGURING STORAGE utility in that theycan be Configuring Storage Configuring

. . . . . Chapter 6 CONFIGURING STORAGE Discovery and Management of Physical Disks

DISCOVERY AND MANAGEMENT OF PHYSICAL DISKS

Virtual Iron supports three types of physical disks: • Fibre Channel SAN disks • iSCSI SAN disks • SATA, SAS, or parallel SCSI node-local disks Local IDE drives are not supported. All physical disks are automatically discovered during the node boot process. If you reconfigure LUNs while a node is running, before adding them to the system, perform a Rescan to update the management server: In Virtualization Manager, right-click the managed node and select Rescan SAN Ports. This step assures synchronization between the management server and your environment. To access physical SAN resources, the managed node hosting it requires a host bus adapter (HBA) or network interface card (NIC). Each HBA has a unique WWNN or iqn, which you need to provide to your SAN or iSCSI administrator. The administrator makes specific LUNs visible to managed nodes in the Virtual Iron® framework. Once this information has been configured in your SAN infrastructure, SAN targets and LUNS become visible to the managed nodes programmed to access them.

88 Virtualization Manager™ Administrator Guide Disks tab SAN nodes to managed visible LUNs LUNs andAliases to aLUN assigned Alias disks tab. Asample view is shown in Then click on Hardwareat thetop ofthe navigation tree, and select the SAN ple isshownin umn beside itinthe To assign an aliasto aLUN,select theLUN and double-click inthe of aliasesare“Windows2003+SQLServer”or“SAPdata.” Virtualization Managerallows you toas Click the Figure 54. Alias assigned toaLUN 54. assigned Alias Figure Nodes Managed toAll 53. available LUNS Figure Hardware Figure 54 button to view the LUNs accessible to alltoaccessiblethe button managed LUNs toview nodes. SAN Disks . window. Enterthe alias inthe field.Anexam- Discovery and Management ofDisks Physical Figure 53 sign analias toeach LUN. Examples CONFIGURING STORAGE . Alias col-

. . . . . Chapter 6 CONFIGURING STORAGE Configuring Logical Disks

CONFIGURING LOGICAL DISKS

The Virtual Iron Virtualization Manager supports the creation and assignment of logical disks on local drives or SANs. Before you configure logical disks, read the following section to understand how logical disks are organized within disk groups (DGs). The illustration in Figure 55 shows the relationships between physical disks, DGs, and logical disks.

Figure 55. Virtual Iron® SAN Storage Management

Disk Groups and Logical Disks Each DG is essentially a storage container. DGs consist of a single SAN or local disk. Virtual Iron® enables you to make use of the storage contained in a DG by subdividing it into one or more logical disks. The process for creating logical disks on a local drive is the same as for creating them on a SAN. Logical disks can be copied (or cloned) for use by other VSs, and they can also by administratively exported or imported from a directory within Virtualiza- tion Manager. Once you create logical disks, they are visible to all VSs hosted on the VDC.

90 Virtualization Manager™ Administrator Guide selected disks Local Group Disk Create selected VDC Creating DiskGroups Step 1. you can assign them to VSslater in thisprocedure. Follow thisprocedure tocreate diskgr Step 2. Figure 56. DiskGroup Create Figure described in Begin by creating and assigningnodes to aVirtual Data Center as D. C. B. A. To create a diskgroup. been selected. Click Select either LocalDisksorSAN Select the Select theVDCin the navigation tree. Create Disk Group... Creating Virtual Data Centers Virtual Storage In tab. oups. After you create thedisk groups, Figure 56 CONFIGURING STORAGE . , alocal diskhas Configuring Logical Disks Configuring Logical

. . . . . Chapter 6 CONFIGURING STORAGE Configuring Logical Disks

Step 3. The Disk Group Wizard appears (Figure 57) with all nodes in the VDC listed in the Nodes pulldown. The DG Name New Disk Group is assigned to the group by default. In this example, the default name has been changed to Finance DG. Click Next>> to continue.

Figure 57. Begin DG Wizard

Step 4. Each DG must be mapped to a physical disk. In the next window (Fig- ure 58), choose the disk on which to place the DG. In Virtual Iron®, each physical disk can be allocated to one and only one DG.

Figure 58. Assigning a Disk to the DG

To assign a disk to the DG, select the disk in the Unassigned Disks pane. Then click Add>> and Finished. The new DG appears in the window as shown in Figure 61.

92 Virtualization Manager™ Administrator Guide Creating LogicalDisks Step 3. Step 2. Step 1. Figure 59. aNew Create Disk Logical Figure One LogicalvDisk1. tab. Inthiscase, thenew logicaldiskhas been renamed toFinance Click name assigned byVirtualization Manager is NewLogical Disk. Assign aname to the logical disk,and asize inGB.Bydefault, the ure 59 Click OK Create Logical Disk appears. . The new logical diskisadded to the tree inthe Logical Disks (see Figure 63 CONFIGURING STORAGE ). The window shown in Configuring Logical Disks Configuring Logical Fig-

. . . . . Chapter 6 CONFIGURING STORAGE Exporting and Importing

EXPORTING AND IMPORTING

Use the export and import functions to move VHD files on the Virtualization Manager from and to the disk groups in your data center. This is also useful if you want to move a logical disk to a new disk group in a different VDC. There are two types of VHD files, each of which is stored differently in the data center: • Dynamic—As data is written to the dynamic disk, the file grows as large as the maximum size that was specified when it was created. Unused space is not included in the image, reducing the size of the dynamic disk file. If you import a dynamic VHD, the file is imported to a virtual disk. • Fixed—A fixed-size hard drive is one in which space is allocated when the VHD is created. The size of the disk does not change when data is added or deleted. If you import a fixed VHD, the files are imported to a logical disk. Enterprise Edition Commonly used VHD files on the Virtualization Manager may be made available to multiple users. Use the import and export functions to move VHD files to the Virtualization Manager for use in virtual servers.

EXPORTING A LOGICAL DISK To export a logical disk using Virtual Iron® Enterprise Edition, proceed as follows: Step 1. Select the logical disk to be exported in the navigation pane and click the Virtual Storage tab. Step 2. Select the logical disk in the VDC pane. Step 3. Click Export.

94 Virtualization Manager™ Administrator Guide Disk Logical Disk Logical Export Step 4. Figure 60. Exporting a Logical Disk 60. aLogical Exporting Figure Click on the content of the Logical Disk intheNotes pane. logical diskdirectory on Virtua window shownin Virtualization Manager displays the Export to complete theoperation. Figure 61 . The window showsthecontents ofthe lization Manager. You may enter notes Export Virtual HardDisk Image CONFIGURING STORAGE Exporting and Importing

. . . . . Chapter 6 CONFIGURING STORAGE Exporting and Importing

Figure 61. Contents of Logical Disk Directory

Add optional notes on the exported Logical Disk

IMPORTING A VIRTUAL DISK Step 1. To perform an import operation, select the disk group into which you wish to import a cloned logical disk. Click the Import button as shown in Figure 62.

Figure 62. Importing a Logical Disk

Logical Disk selected for import

Import Log- ical Disk

Step 2. Virtualization Manager displays the Import Virtual Hard Disk window

96 Virtualization Manager™ Administrator Guide Fixed orDynamic Fixed Type: the Note Single ServerEdition EXPORTING AVIRTUALEXPORTING DISK Step 2. Step 1. tion Manager directory.the Use Administration Manager (see moves itfromone location onthe Virtualization Manager to thevirtual disks management, which isalso the Virtualization Manager. Exporting a logical disk In the Single Server Edition, alllo Note: VHD files cannot exceed 18 GB. Figure 63. Import Virtual HardDisk Image Window Management -> Get a File...Get a Management -> tion Manager (see tion Manager Navigate to the Virtual Iron® launcherpage, and start theAdministra- plete theoperation. Select thelogical disk and click Choose thelogicaldisk you wantto import, then click directory onthe Virtualization Manager. shown in ) toget the file from memory, and placeitina newlocation. Figure 63 Using the Administration Manager . The window shows the contents of the logical disk gical disksare stored onthe node under asshownin Export CONFIGURING STORAGE as shown in in shown as Put/Get Fileson theVirtualiza- Figure 64 Exporting and Importing . Figure 60 ). Choose Import to com- . File

. . . . . Chapter 6 CONFIGURING STORAGE Exporting and Importing

Figure 64. Getting a File from the Virtualization Manager

Step 3. Select the logical disk you had exported earlier, and click OK.

IMPORTING A VIRTUAL DISK Step 1. Select the logical disk and click Import as shown in Figure 62. Step 2. Navigate to the Virtual Iron® launcher page, and start the Administra- tion Manager (see Using the Administration Manager). Choose File Management -> Put a File... as shown in Figure 64.

98 Virtualization Manager™ Administrator Guide C LONING Cloning LogicalDisks D ISKS ure 65 To clone alogical disk,select thelogicaldisk in the window, as shown in Virtual disksmaybe cloned to logicaldisksorother virtualdisks. only becloned when they are not in usebyavirtualserver. tent to any other disk group under management. Note that logicaldisks can Virtual Iron® allows you to clone (copy) logicaldisksand their associated con- . Virtual Disk—Fixed Logical Disk—Fixed Logical Virtual Disk—Fixed Disk—Fixed Logical LogicalDisk—Fixed Virtual Disk—Dynamic Disk—Fixed Logical From: Virtual Disk—Dynamic or CONFIGURING STORAGE To: To: Cloning Disks Fig-

. . . . . Chapter 6 CONFIGURING STORAGE Cloning Disks

Figure 65. Cloning a Logical Disk

Cloning a Logical Disk

Choose parent volume

Choose a name for the logical disk, and use the pull-down menu to choose a volume for the cloned disk’s parent. Click OK. The cloned logical disk is created on the disk group you specified. Note that Virtualization Manager only presents volumes eligible to support the disk you are cloning. If a disk you are cloning has .5GB, only volumes with at least this much space are presented on the pull-down menu. The cloning operation may take several minutes. The progress bar that appears is updated every 10-15 seconds.

100 Virtualization Manager™ Administrator Guide VHD R Exporting orImportingVHDImageFiles VHD File Naming Conventions EPOSITORY Step 1. back tothe default VdisksDirectory. VHD directoriestoalocalcomputer,you changeNote thatif you canchange it disk. added tothe VHDrepository from a managed node, intoarepository’s virtual Importing from a repository allows youto repository. ate virtualdisks.You can’t import directly fromalocalcomputer toaVHD Exporting to arepository results in a VHD repository of theVHD files,youchange itfor allusers. your local computer. Note that when you change the directoryused as the export aVHDimage toor fromtheVirtualization Manager VHDrepository and operating systemandvirtual its computer’s applications. You mayimport or For Virtual IronEE,theVirtual HardDisk Figure 66. Virtual Hard Disk Repository Screen Showing VHD Image VHDImage File Showing 66. Screen Virtual DiskRepository Figure Hard following screen appears. In theVirtualization Manager VHD imagefile from whichyoucancre- File (VHD) image is a complete copy of aof copy (VHD)imageisacomplete save a VHD image file that has been file thathas save aVHDimage menu, select CONFIGURING STORAGE VHD Repository VHD Repository . The

101

. . . . . Chapter 6 CONFIGURING STORAGE VHD Repository

Step 2. Select a location from the pulldown menu, or click Change. Step 3. If you clicked Change, the following dialog box appears:

Figure 67. Change CHD Directory Dialog Box

Step 4. Enter a new directory location or click Default. • UNIX—For UNIX management servers, UNIX naming rules and directory separator characters apply. for example, to set the repository to the directory /opt/storage/vdisks: defaultVHDRepositoryPath = “/opt/storage/vdisks” • Windows—For Windows management servers, Windows-specific UNC syntax is required. This consists of the drive letter and colon, for \ characters (\\\), and the path. Specify subdirectories in the path with two \\ characters. For example, to set the VHD repository to the directory NAS Storage\VHD Repository on the g: drive: defaultVHDRepositoryPath = “g:\\\NAS Storage\\VHD Repository” If you specify a directory for the VHD repository, the directory is created after you restart the Virtualization Manager. If you specify an invalid directory, or if the directory can not be created, an error is logged and the directory remains set to the last valid directory.

102 Virtualization Manager™ Administrator Guide 7

CREATING AND CONFIGURING VIRTUAL SERVERS

......

This chapter explains how to create and configure VDCs and VSs. Creating Virtual Data Centers...... 104 Assigning Nodes to Virtual Data Centers ...... 106 VDCs and Unassigned Virtual Servers...... 109 Virtual Servers ...... 112 Cloning Virtual Servers...... 119 Installing a Guest OS to a Logical Disk ...... 122 Installing VSTools on Virtual Servers...... 124 Starting and Stopping Virtual Servers...... 132 Launching a Virtual Server Console ...... 134 Configuring Policies...... 135 Moving Virtual Servers and Nodes ...... 140 Provisioning VSs with Gold Masters...... 146

103 Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Creating Virtual Data Centers

CREATING VIRTUAL DATA CENTERS

A virtual data center (VDC) is an administrative entity that consists of one or more managed nodes. Each VDC functions as a true data center—a group of nodes that have been segregated to meet specific business needs. The hardware resources in each VDC are only available to the VSs hosted by them. In the same way, other VDCs function as a separate set of physical resources. The many VDCs into which you can separate all the nodes under management can be likened to the partitions into which a large computer might be divided. VDCs are Containers for VSs Before you create VSs, you need to create the VDC that will house them. Step 1. In the Application toolbar, click the Resource Center button. Click the Create new Virtual Data Center icon as shown.

Figure 68. Creating a VDC

Step 2. The new VDC appears in the navigation tree. The yellow lock icons indicate that you are creating or changing an object. While you are performing this operation, the objects cannot be managed by other users.

Figure 69. VDC in Navigation Tree

104 Virtualization Manager™ Administrator Guide Created Data Center VirtualNew folder Virtual Servers Unassigned Step 3. Figure 70. The Unassigned Virtual 70. Folder Unassigned The Servers Figure folder called The new Virtual Data Centerappears in the navigation tree. Another and Unassigned Virtual Servers VSs forlaterdeploymentmore information,Forin theVDC. see VSs that are shut down. It is also a staging area—a place to configure as storagefolderserves areaattached a place tomove a VDC.Itis to CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS Unassigned Virtual Servers . appears below the VDC.This Creating Virtual Data Centers VDCs

105

. . . . . Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Assigning Nodes to Virtual Data Centers

ASSIGNING NODES TO VIRTUAL DATA CENTERS

Now that you have created a VDC, add at least one managed node to it. Step 1. To add nodes to the VDC, select its name in the navigation tree and click the Assign Nodes icon.

Figure 71. Assign Nodes Icon

Step 2. The Assign Nodes dialog opens with information about all nodes that have been discovered by the Virtual Iron® management server that are not assigned to another VDC. (See Creating Virtual Data Centers.) To move the node to the VDC you have created, select the node and click Add >>. Then click OK.

Figure 72. Assigning Nodes to a VDC

106 Virtualization Manager™ Administrator Guide to VDC Added Node Information Performance Node Getting Step 3. Figure 73. Tab VDCSummary Figure in the After you assign a node to a VDC, information about the node appears VDC. time; its physical resourcescannot beshared by the VSsin anyother absolute. A node canused only bythe VSshosted inone VDC at a in mind, however, that the ownership ofanode byits parent VDCis pane. Youassign can asmanynodes The node movesfrom theAvailabl is associated colors. CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS Free Summary forusewithin the VDC. tabThe node asshownhere. isgreen toshowthatit Table 2 Assigning Nodes toVirtualData Centers e Nodestothe Assigned Nodes explains nodestates and their are available are toaVDC.Keep

107

. . . . . Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Assigning Nodes to Virtual Data Centers

Table 2. Node States and Colors

Node Color State Meaning

Green Free Available for use within the VDC.

Slate In Use The node is hosting at least one VS.

Yellow Warning Warning messages have been received.

Red Error The node is in error.

Click the Protected Node check box if you do not want VSs to be moved to it from other nodes during LiveMigrate™.See LiveCapac- ity™ for information on LiveMigrate™. Click the Display check boxes to see node resources and activity or performance data.

108 Virtualization Manager™ Administrator Guide VDC About Unassigned S

AND U NASSIGNED its parent VDC. Once created, unassigned VSs can be dragged and dropped on a node within Unassigned VSsare locatedinaseparate folder at the bottom ofeach VDC. parameters are mapped to thenode’s resources. tive VScannot berun untilitisassigned toa node. At thattime, its defined cessor parameters, network, and SAN access can bespecified, butan inac- in a VDC, but donot consume anyofthat VDC’s resources. Memory andpro- Unassigned virtualare servers fully orpartially configuredhoused VSsthatare . See. • • • automatically created inthe navigation tree. Use this folder to: When youcreate a virtual data center, an Store virtual server clones. associated withanynode inthe VDC Store virtual servers that are stopped, sothat theydonot use thememory Create and configure VSsforlaterdeployment in theVDC in the navigation tree. navigation the in VirtualUnassigned Servers Figure 74 Figure 74. Unassigned Virtual Tree in Folder Navigation 74. Servers Unassigned Figure CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS Virtual Servers V . IRTUAL S ERVERS Unassigned Virtual Servers folder is VDCs and UnassignedVDCs and Virtual Servers

109

. . . . . Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS VDCs and Unassigned Virtual Servers

Configuring Unassigned Virtual Servers To configure an unassigned virtual server: Step 1. Left-click on the Unassigned Virtual Servers folder in the navigation tree to select it. Then do one of the following: • Right-click the selected icon and select New Virtual Server. • Click the Create New Virtual Server icon in the action toolbar. Step 2. Configure the virtual server: select the VS and choose the Configura- tion tab in the Management pane. Then, follow the steps outlined in Creating a Virtual Server. Deploying an Unassigned Virtual Server After creating an unassigned VS, you can move the VS to a node and start it. Figure 75 shows the unassigned virtual server SAP data being moved to a node. Before the move is allowed, Virtualization Manager checks: • Memory and processing resources in the target node • Access to OS (on network or SAN) from the target node

Figure 75. Moving an Unassigned VS to a Node

The VS begins using the memory and processors configured for it as soon as it is moved to a node. If the target node does not have enough processors or memory, the UI disallows the operation.

110 Virtualization Manager™ Administrator Guide Moving aVStoUnassigned cient processing andmemoryresources, and start it. To use the VS,simplymoveitfromtheunassigned area toanode with suffi- memory. Allinformation associated with the VSismaintained. stopped VStothe unassigned VSarea prevents the VSfromusingany node that node’s available memory, whether ornot theVSisrunning. Moving a When aVSexistsallocatedcertainaconsumesand onanode,itis amount of The storage capability provided byUnas restart it.Or, reconfigure the VS, and then move ittoadifferent node. currently inuse.To run the VS,move itbackto its original parent node and Use the Unassigned Virtual Serversfolder topark virtual serversthat arenot CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS signed foldersisextremely useful. VDCs and UnassignedVDCs and Virtual Servers

111

. . . . . Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Virtual Servers

VIRTUAL SERVERS

Make sure you have completed the following before you create a VS: • Prepared nodes to be managed. See Managed Node Configuration. • Cabled all nodes properly. See Site Preparation. • Installed the Virtual Iron® software. See Installing Virtual Iron®. • Established a connection to the Virtual Iron® management server. • Defined connections between system nodes and physical networks. See Mapping Physical Ports to Logical Networks. • Created a Virtual Data Center (VDC). See Creating Virtual Data Centers. • Assigned a node to the VDC. See Assigning Nodes to Virtual Data Centers. Once you complete these tasks, you have created the basis for virtualizing the resources of one or more nodes. All that remains is to create virtual servers.

Note: If you are configuring a Windows Guest Operating System for your virtual server, and you wish to use more than 4 GB, you will need to add a “/PAE” switch to the boot.ini file.

Creating a Virtual Server This procedure describes how to create, configure and deploy a new virtual server on a managed node. Step 1. Select the node you added earlier. Click the Create Virtual Server icon on the application tool bar.

Figure 76. Create Virtual Server Icon

Step 2. The new virtual server appears under Unassigned Virtual Servers, and the New Virtual Server Wizard appears. See Figure 77.

112 Virtualization Manager™ Administrator Guide Step 8. Step 7. Step 6. Step 5. Step 4. Step 3. Figure 77. NewVirtual ServerWizard Click Select adisksize fromthe pull Type anamefor the newlogical disk. • • unconfigured systems, thedefault setting is Select orcreatestorage forthe virtualserver. See Click Server server later. Click its iconin NOTE: Choose Virtual Server The example showsthe default setting, named Options. Name the virtual server. In this CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS memory. Itwillboot, but you can not run applications. configure storage. Meanwhile,the virtualserverjustrunsin If you select ical disks. the default. The next screen that appears displays the list of log- If you havepreviously created logi Next Next window, click . . . Do notspecify storage Create aBasic Virtual Server Edit . the navigation pane. In the down menu.Default is10 Gigabytes. example, the virtual server has been cal disks, Use Ex , you can goback later to Create a fully configured Create NewDisks to

configure the virtual Figure 78 isting Disk is New Virtual Virtual Servers . For .

113

. . . . . Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Virtual Servers

Figure 78. New Virtual Server Wizard: Specify Storage

Step 9. Select the disk group in which the newly created logical disk will be placed. See Figure 79. Step 10.Click Next.

Figure 79. New Virtual Server Wizard: Select Disk Group

114 Virtualization Manager™ Administrator Guide Step 13. Step 12. Step 11. use more than one VNIC. See Note: communicate withmultiple networks. add morethan one VNICto eachVS,allowing the VStoconnectand work identification card (VNIC),associ Configure networkadaptors. Eachnetwork adapter consists ofa virtual net- Step 14. You need toinstall VSTools on anOSso theVSbooting that OScan Figure 80. NewVirtual ServerWizard: Network specific VNICfromthedrop-down list. navigation pane and editing Younetworkcan setupthecl by later If you havenotsetup anetwork yet,select • method forthe VS: options window, selectanoperating system and then choose a boot CDROM, orfrom a Network Boot Device. See CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS Select anEthernet network from the pulldownmenu. Click Select aVNICfromthe NetworkAdapter pulldown menu tochoosea Virtual Iron® enables VSsto boot ov If you choose device on the node wherethe VSislocated. Forexample, ifyou hard disk.Thisselection tellsthe VS to boot from the CDROM Next . CD/DVD Installing VSTools on Virtual Servers , select aspecific drive ifbooting froma its network configuration. Figure 80 ated with an externalsubnet. You can er a SAN, via NFS (PXE), from a (PXE), from er aSAN,viaNFS icking on the virtual server in theserver in icking onthevirtual . Do notspecify network Figure 81 . In theboot Virtual Servers or

115 ...... Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Virtual Servers

are installing a Windows Operating System onto a logical disk, as in Figure 81, select Microsoft Windows XP for the operating system. You will need a Microsoft Windows XP CD and license key later, when you install Windows onto a logical disk that you specify. • Choose Network Image Boot if to boot an iso from the Virtual Iron® Management Server. On Linux, iso images are located in /opt/virtualiron/nbd. On Windows™, they are located in C:\Pro- gram files\VirtualIron\nbd. • Choose Disk to boot from the logical disk or SAN assigned as the boot device for the VS. • Choose Network PXE Boot to PXE boot the VS from a public network. You will not be able to configure a LUN unless you have configured SAN access and designated a boot disk, as described in Discovery and Management of Physical Disks.

Note: See Installing VSTools on Virtual Servers to install VS Tools on an OS. A specific set of VS Tools are shipped for each guest OS supported by Virtual Iron. For enhanced performance and statistics gathering, Virtual Iron® strongly recommends that you use VS Tools.

Step 15.Click Next.

Figure 81. New Virtual Server Wizard: Boot Options

116 Virtualization Manager™ Administrator Guide Step 16. node. Note: virtual servers running onanode isbelow thetotal memoryavailable on that sumes a smallamount ofmemory. Forthis reason, the memory available to The virtualization services component running on a managed node con- Figure 82. NewVirtual Server Figure 82 server in relationto others runningon thesame managed node. See allocated tothe virtual server, and • • CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS Configureand theamountofnode thenumberofprocessors memory default formemory=256MB (.25 GB). available on a node, consult thenode's Virtual Servertab. The increased commensurately. To determine how much memoryis either AorB(orboth) are reduced, C’s allocation can be allocated upto 1GBof memory. If thememory allocations of and A and Bare each allocated 1GBof memory, Ccanonly be and Care created on a managed node with 3GBofmemory, cannot beoversubscribed. For example, ifVirtual ServersA,B, VS. Unlike processors, memory is not shared among VSs,and Memory—Specify theamount ofmemorytobe allocated tothis that istransparent toallofthem. Default for Processors =1. time-shares availableprocessorsamong theVSsina manner you can assign twoprocessors to each ofthem. Virtual Iron® on amanaged node. IftwoVSsarerunning onthe samenode, VS touse.NotethatmultipleVSscanthe share CPUsavailable Processors—Configure the number ofprocessors you wantthe . Eachofthe options isdescribed below. Wizard: Configuration Options schedule the priority of thisvirtual Virtual Servers

117

. . . . . Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Virtual Servers

• Priority—If more than one VS is running on the same managed node, use the Priority setting to give highest priority to one VS, and less (or equal) priority to others. Priority levels determine which VS is allowed to run first, in the event two are contending for the same physical processors. Set the Priority for a VS from lowest (1) to highest (100). Default for Priority = 50.

Note: To improve performance, If you are mixing iSCSI-based virtual servers with SAN or local disk virtual servers, set the priority of the CPU on the iSCSI virtual server higher than the SAN or local disk virtual server’s priority.

• VS Tools Installed—Check VS Tools Installed if you have installed the VS Tools package on the OS, and you wish to use VS Tools. A specific set of VS Tools is shipped for each guest OS supported by Virtual Iron®. Before enabling VS Tools for a guest OS, read Installing VSTools on Virtual Servers and follow the installation instructions for Windows® or Linux. • Mouse type—Depending on the operating system you specified earlier, Tablet, PS2 or USB is set as the default.

118 Virtualization Manager™ Administrator Guide C LONING Preparing a Windows VS for Cloning VSfor aWindows Preparing V CLONING WINDOWS VIRTUAL SERVERS IRTUAL Step 6. Step 5. Step 4. Step 3. Step 2. Step 1. computer. the same time, itmodifiesthelocal computer SIDtomakeitunique each Sysprepthe personalizes cloned computer created. Windows virtualserver, it that uniquely identifiesthe computer ing. Computers running Windowsoperat • • • Before cloninga virtual server: sufficient memoryto accommodate its needs. tainingthe originalVS.To startwithUnassigned a VDC toVS, moveitfrom the Use the Windows utility is automaticallyplacedinthe The VSclone unless thenetworks VDChasaccesstothe orstorage configured forthat VS. Virtualization Manager does not allowyou tomove acloned VSto aVDC to the clone (rather than theVNICused byits parent). not exact replicas of their originals; to the same logical disksassigned to theoriginal. However, cloned VSsare cessing, memory, andotheraccessoriginaltheof characteristics VS,andhas Cloning creates acopy of avirtual Make sure the virtual server is not assignedto alocal diskorraw disk. Assign aguest OSto the virtualserver. Stop thevirtual server. Running virtualserverscannot becloned. S ERVERS \support\tools\deploy.cab Create an answer file withsetupmgr.exe. server. from the Windows product CD to ane Copy the contents of Install desired applications InstallTools. VS See Apply allrelevantWindows service packs and updates. • • Create, install, and configure theWindows virtual server asdesired. CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS dialog box. If thevirtual server does nothave storage, you willnotsee the option displays a dialog box with options for cloningthe disks. If the virtual serveryou are cloning has storage disks, the clone sysprep is important to ensure that duplicate SIDsare not Installing VSTools on Windows® Virtual Servers toprepare aWindows virtual server forclon- and apply settings asneeded. server. The clonedVShas the samepro- the cloningoperation or domain, and user. When youclonea ing systems have a Security ID (SID) a SecurityID ing systemshave with characteristics you provide. At Unassigned w \sysprep folder inthe virtual folderof theVDCcon- Cloning Virtual Servers assigns anew VNIC

119 ...... Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Cloning Virtual Servers

Step 7. Run sysprep. This will shut down the virtual server when it completes. Step 8. Clone the newly created template into new virtual servers as required. Cloning a Virtual Server Step 1. Select the VS you want to clone, and choose Clone Virtual Server from the popup menu as shown in Figure 83.

Figure 83. Cloning a Virtual Server

120 Virtualization Manager™ Administrator Guide Step 2. Figure 84. Cloned VS in Unassigned Folder Unassigned 84. VS in Cloned Figure shown in The cloned VSappears intheUnassigned folder ofthe VDC,as name CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS . Figure 84 . Bydefault, thecloned VSiscalled Cloning Virtual Servers Copy ofVS

121

. . . . . Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Installing a Guest OS to a Logical Disk

INSTALLING A GUEST OS TO A LOGICAL DISK

You can install an operating system and applications to a virtual server's disks the same way you would on a physical server. Use a physical CDROM (and the installation media provided by your operating system provider) or a network ISO. For storage, use either a raw SAN LUN or a logical disk. Installing an OS from a CDROM involves: • Creating a virtual server, and moving it to a managed node that: - Contains a CDROM drive - Is connected to the disk on which you intend to install the OS • Starting the virtual server • Installing the OS on a specific disk, using your OS’s installation program Use the following steps to complete this task for Red Hat and SUSE Linux. Step 1. Within Virtualization Manager, create a virtual server. Step 2. Drag and drop this virtual server to a managed node with a CDROM drive. Choose CDROM Disk as the boot option for the virtual server. Do not choose Use VSTools. Step 3. Create a logical group and logical disk on the managed node. Then assign the logical disk to the virtual server. • See Configuring Logical Disks for instructions on creating a disk group and logical disk. • See Virtual Servers for instructions for assigning a logical disk to a virtual server. Step 4. Insert OS installation Disk 1 in the managed node in which you intend to run the VS. Note that this node must be connected to the disk to which you intend to install the OS. Step 5. Start the virtual server. This begins a standard installation from the CD. Step 6. Open a virtual server console as explained in Launching a Virtual Server Console. The OS installer takes you through available options. If installing Red Hat, or SUSE without networking, proceed to Step 4.

If Installing SUSE Linux Using a Network Installation... When prompted for installation components, do the following: Step 1. Choose Kernel Modules (Hardware Drivers) Step 2. Choose Load Network Card Modules Step 3. Select this driver: rt18139_cp This emulated network driver is included in the Virtual Iron Services layer. Figure 85 shows selection of this driver in the context of a SUSE installation.

122 Virtualization Manager™ Administrator Guide Step 5. Step 4. Step 6. Figure 85. Choose Hardware Driver, Hardware 85. Choose Figure Installation SUSELinux enable server boot optionto Before youreboot When the installation programcompletes, itinstructs youtoreboot. tion program. Continue theinstallation according to theinstructions inyour installa- disk youspecified. Reboot the OSas prompted bythe installer. The VSboots from the CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS VSTools Installed , useVirtualization Manager tochange thevirtual Disk Device . , as shownin Installingto aLogical Disk OS aGuest Figure 81 . Do not

123

. . . . . Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Installing VSTools on Virtual Servers

INSTALLING VSTOOLS ON VIRTUAL SERVERS

Virtual Iron® provides VSTools for use by guest operating systems. These tools provide increased performance and a set of enhanced capabilities that include: • Accelerated network and storage block drivers • The collection of virtual server statistics • Control of virtual servers (shutdown/restart) • LiveMigration™ of virtual servers To make use of these capabilities, install VS Tools on the disk from which the guest OS is booted. Installing VS Tools on Linux Virtual Servers

While the use of VS Tools is optional, Virtual Iron® strongly recommends that you install the VS Tools package on the OS disk. To copy and install VS Tools for a Linux virtual server, do the following: Step 1. Copy the appropriate VS Tools rpm from the management server node. It is important to select only the rpm associated with the OS. The tools are located in this directory: /opt/VirtualIron/VirtualizationManager/system/vstools/rpms The rpm kits supplied for each OS version are listed in Table 3. Note that the values for x.x.x-yy in the RPM kit files are release-dependent.

Table 3. Linux VS Tools Kits Provided with the Virtual Iron® Software

Supported OS RPM kit

SUSE Linux Enterprise virtualiron-2.6.5-7.244-bigsmp-x.x.x-yy.i386.rpm Server 9 SP3 32-bit virtualiron-2.6.5-7.244-smp-x.x.x-yy.i386.rpm

SUSE Linux Enterprise virtualiron-2.6.5-7.244-smp-x.x.x-yy.x86_64.rpm Server 9 SP3 64-bit virtualiron-2.6.5-7.244-smp-x.x.x-yy.x86_64.rpm

Red Hat Enterprise Linux 4 virtualiron-2.6.9-22.ELsmp-x.x.x-yy.i386.rpm Update 2 virtualiron-2.6.9-22.ELsmp-x.x.x-yy.x86_64.rpm

Red Hat Enterprise Linux 4 virtualiron-2.6.9-42.ELsmp-x.x.x-yy.i386.rpm Update 4 virtualiron-2.6.9-42.ELsmp-x.x.x-yy.x86_64.rpm Copy the appropriate rpm kit from the management server to the virtual server. You can do this from the virtual server console. In this example, the rpm is being copied from the management server (10.1.3.6) to the virtual server (vs037).

124 Virtualization Manager™ Administrator Guide Step 4. Step 2. Step 3. yy Figure 86. Sample Installation of RPM Kit # rpm-Uvh ager/system/vstools/rpms/v [root@vs037 ~]#scp10.1.3.6:/opt/VirtualIron/VirtualizationMan- ager. Select Open theVirtual Server bootoptions window inVirtualization Man- shown in A sample of theinstallation ofthe rpmforRedHat Linux (64 bit) is mand asfollows: Install the VSTools package on the virtual server, usingan rpm com- shown in After installing therpm,power off fromas theconsoleserver virtualthe Click CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS .x86_64.rpm. OK . Figure 86 Figure 86 Use VSTools . . forthevirtual serverasshownin irtualiron-2.6.9-22.ELsmp- Installing VSTools onVirtual Servers x.x.x- Figure 87

125 ...... Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Installing VSTools on Virtual Servers

Figure 87. Enable VSTools for a Virtual Server

Step 5. Start the virtual server as described in Installing a Guest OS to a Logi- cal Disk. Open a virtual server console and observe the boot process. When the virtual server starts, it will boot the VS Tools package you installed, as shown in Figure 88.

Figure 88. Virtual Server Startup, with VS Tools Installed

126 Virtualization Manager™ Administrator Guide Installing VSToolsonWi Uninstalling VSTools Verifying thatVSToolsareInstalled Step 2. Step 1. 2003, see figuration window). For automaticinst running Windows®withVSTools enabled (c tual servers.Follow these steps toinstall the toolsafter youhavecreateda VS Virtual Iron® providesasetofVSTools designed forusewith Windows® vir- boot the associated OS. Note: ating systemprompt: You can uninstall theVSTools package by issuingthis command atthe oper- To seewhether VSTools is instal Step 3. Step 4. If you uninstallVS tools,you un-check makesure VSTools for VSsthat Figure 89. VSTools Directory, Windows # rpm-qa|grepvirtualiron # rpm-e Virtual Iron Administration Manager and browsetothe Open abrowserwithinthe virtual server. Enterthe IPaddress ofthe Boot the Windows® VS,and Loginas Double-click the32- or64-bit directory, Setup Wizard. Launch the installer and followthe pr this file. and download itto your desktop or someother location. Double-click CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS VS Tools SilentInstall as shown in in shown as ndows® VirtualServers Figure 89 . led on aVS,issue thiscommand: VSTools-4.x.x-xx.msi allation ofWindows XPor Windows . hecked inthe Virtual Server Con- ompts in theVirtual Server Tools Installing VSTools onVirtual Servers Admin . file foryour system, /vstools/win /vstools/win

127

. . . . . Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Installing VSTools on Virtual Servers

Figure 90. Virtual Iron Setup Wizard

Step 5. The following wizard prompts you to install the drivers.

Figure 91. Virtual Iron Accelerated Drivers Wizard

Step 6. When the installer prompts you to shut down your virtual server, click Yes. Step 7. After the virtual server stops, open the VS Configuration window, and check VS Tools Installed. Click OK. Refer to Figure 92.

128 Virtualization Manager™ Administrator Guide for Windows® for drivers accelerated Virtual Iron® tp8 Start Step 8. Figure 93. Virtual Iron® Wi 92. VS ToolsFigure Installed Checkbox A. Ethernet driver. Inthe Found NewHardwareWizard, dothe following: B. under DeviceManager as shownin This completes installation ofthe Virtual Iron® drivers.Theseappear C. CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS update. Click Select Check Windows begins installing the network driver. theVS.Duringboot, Windows® discovers the Virtual Iron® No Notthistime Install Software Automatically Next . ndows Drivers, Manager Drivers, Device ndows whendrivera promptedtolookfor Figure 93 Installing VSTools onVirtual Servers . Click . Next .

129

. . . . . Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Installing VSTools on Virtual Servers

VS Tools Silent Install The following procedure automatically installs VS Tools for Windows XP and Windows 2003. Step 1. In Windows Start menu, select Run. Step 2. In the Run window, type cmd. Press Enter. Step 3. In the command console, click the VSTools-4.x.x.x-xx.msi icon and drag it into the console window. Step 4. The command string is automatically entered. Press the space bar. Step 5. In the console window, type /qn, as shown in Figure 94. Press Enter.

Figure 94. Windows Console, VS Tools Silent Install

Step 6. In Virtualization Manager, perform a Hard Reset on the VS. Open the VS Configuration window, and check VS Tools Installed. Click OK. Refer to Figure 92. SPECIAL CONSIDERATIONS FOR WINDOWS 2000 OS When a Windows 2000 system is idle, it will appear to be consuming no CPU resources. Task Manager will show that the CPU is idle. However, Windows 2000 is actually executing instructions in its idle loop. These cycles will not be available for use by other virtual servers on the same node. In order to get Windows 2000 to act like the other more recent Windows operating systems and actually relinquish the CPUs when idle, do the following: Step 1. Make sure VS Tools are loaded and running in the Windows 2000 virtual server. Step 2. Open a browser within the Windows 2000 virtual server, and navigate to the Virtualization Manager’s IP address. You will see the Virtual Iron Virtualization Manager home page. Step 3. Click the VS Tools Installers link. Step 4. Click the win /link.

130 Virtualization Manager™ Administrator Guide Step 5. Step 9. Step 6. A side-effect of theidleristhat it will appear that the Step 8. Step 7. turned on. restarting the Virtual Iron Service.Virtual Ironrecommends that the idler is Turn the idler off by double-clicking the idle cycles canbe used byother virtualservers. it isactuallyreleasing control to the consuming all idlecyclesin the virtual tual server. Dothe samefor Click the Find the Virtual Iron Service andright-click Double click Navigate to select On the Windows 2000 desktop. Right click the the Windows Registry. CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS Manage Win2000_idler_on.reg Services Win2000_idler_on.reg . and Applications >Services underlying virtualization services sothat Win2000_idler_off.reg server. In fact, it only appears thisway; Win2000_idler_off.reg link and download that file tothe vir- toread theidlerinformation into Installing VSTools onVirtual Servers Restart ViStats.exe My Computer . . . fileand then process is iconand

131

. . . . . Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Starting and Stopping Virtual Servers

STARTING AND STOPPING VIRTUAL SERVERS

Virtual servers that are running are marked with a green triangle in the navigation tree. Virtual servers in a Stopped state are marked with a red box in the navigation tree. Starting a Virtual Server To start a virtual server: Step 1. A stopped virtual server is marked with a red square in the navigation tree. Click the virtual server to select it, and perform one of the following actions: • Select the Start Virtual Server icon in the application toolbar. This icon is shown in Figure 95.

Figure 95. Start Virtual Server Icon

Start virtual server icon • Right click on the VS and select Start from the pop-up menu. Step 2. When you issue a Start command, the command appears as an operation in the Job Operations tab at the bottom of the management pane. Stopping a Virtual Server To stop a running virtual server: Step 1. Select the virtual server in the navigation tree. Step 2. Stop the server in by doing one of the following: • Click the stop icon in the application toolbar. • Select the server and choose Stop from the pop up menu as shown in Figure 96.

132 Virtualization Manager™ Administrator Guide Stopicon VS menu choice Stop pop-up Step 3. Figure 97. Virtual ServerStop Options Figure 96. Stopping a Virtual Server Figure 97 When you choose Stop, the UI presents you with the optionsshownin Shutdown • Virtual Iron Manager offers three options tostop a virtual server: •Restart Choose ashutdown optionfor theserver and click Hard Reset • CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS tual Servers VSTools installation, asexplained in have VS Tools installed. mands. You mayneedto perform ahard resetif aVSdoesnot when the VSdoes not respond toShutdown or Restart com- minated without informingthe OS. Perform a HardResetonly restart.tual server . —Performs an orderly OS —Performs anorderly OSshutdown. This requires — . Performs aforced stop. Thevirtual server is ter- Startingand Stopping Virtual Servers shutdown followed byavir- Installing VSTools onVir- OK .

133

. . . . . Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Launching a Virtual Server Console

LAUNCHING A VIRTUAL SERVER CONSOLE

To open a console for a virtual server: Step 1. Select the virtual server in the navigation tree. Step 2. Launch a console by doing one of the following: • Click the console icon in the application toolbar. See Figure 98.

Figure 98. Launch virtual server console icon, application toolbar

Launch virtual server console icon

• Right-click on a running virtual server and choose Launch console from the menu options as shown in Figure 99.

Figure 99. Launch virtual server option, pop-up menu

Step 3. Press Enter several times in the open console window to get focus at the OS prompt. The console can be resized, run in the background, and dismissed (closed) as needed. The virtual console shows the boot sequence for Red Hat Linux or the boot sequence for Window® XP Professional.

134 Virtualization Manager™ Administrator Guide C parameters LiveCapacity™ ONFIGURING LiveCapacity™ P ipate inthepolicy. old foreachVirtual Data Center,partic-choose thesetofnodestoand thatwill time. Virtualization Manager™ allows yo applicationsphysoneGOSs andtheir from reached,threshold is VirtualIron® LiveMigrate™technologyrunning relocates every virtualserver. The movement of LiveCapacity™ continuously samples performancedata from everynodeand fixed periodof time. server in aVDCifanyofthe server resources. Itautomatically moves runningvirtualserverstoanew physical LiveCapacity™ optimizes virtual serv enterprise data centers. more efficiently byreducingthe complexity and costs involved withoperating ical resources.This allows administr and otherfeaturesThese providepolic • • • tual servers. These features include: Virtual Iron® providesadvanced features OLICIES ing node fails. Automaticallymoving andrestarting virt to facilitatemachines operations maintenance The ability to moverunning virtual serversfromhostnodes to different machines Automatically balancing Figure 100. 100. LiveCapacity™ Configuration Figure CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS processing loads across a setof physical s exceeda specified CPUthresholdfora ators to manage and deliver services er useacrossashared pool of y-based automation ofvirtual andphys- virtual servers ispolicy-driven. When a u tospecify a LiveCapacity™ thresh- that support high-availability forvir- ual servers on a new node if a host- new nodeifa a servers on ual ical server to another without down Configuring Policies

135

. . . . . Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Configuring Policies

LiveRecovery™ LiveRecovery™ provides high availability for virtual servers by automatically moving them to a new physical server if their managed node fails. In contrast to LiveCapacity, which is enabled at the VDC level, LiveRecovery™ is enabled for each virtual server on a case-by-case basis. Once enabled, LiveRecovery checks the VSs as they start running to test whether they can respond to a ping to any of their IP addresses. If pings to any interface are successful, the VS is declared a candidate for LiveRecovery and the VS is shown as protected.

LiveRecovery Requirements For LiveRecovery to operate properly, certain conditions must be met for each virtual server (VS). • Assure that the VS is not configured with a network (image) boot device. • Check that the VS is reachable by the management server via at least one of its Ethernet networks, and that ICMP is enabled in the VS. ICMP is required to allow the VS to respond to a network ping. • Assure that at least one node that meets the following requirements is available in the VDC: - Enough free memory to accommodate the moved VS. - A running destination node. - The same as, or greater than, the number of CPUs in the VS. - Connectivity to all the disks assigned to the VS. This means that LiveRe- covery will not work on a VS with any local storage assigned to it. - Connectivity to the networks configured on the VS. LiveRecovery checks all the networks assigned to the VS’s VNICs, so a destination node must have all those networks configured on them.

136 Virtualization Manager™ Administrator Guide and does not perform a LiveRecovery. node. If anyinterfaces respond, thepolicy assumes thenode isstilloperating pinging all the networkinterfaces on all theVSs on the suspected inoperable Therefore,thechecks LiveRecovery policy of having twoVSswritingto the samesetof disks. NetworkManagementwould initiate LiveRecovery, withtheundesirable result is disabled. However, ifthiswere theonly determinant, apulled cable on the The LiveRecoverypolicyusestheManagementNetwork todetect that anode How LiveRecovery Works Figure 101. LiveRecovery CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS whether the node is really down by Configuring Policies

137

. . . . . Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Configuring Policies

Click the Virtual Server Policies tab to see the state of LiveRecovery for the VS:

State Meaning

Not Applicable The VS is unassigned and/or VS Tools is not enabled.

Not Enabled The LiveRecovery option is not selected for this VS.

Inactive The LiveRecovery policy is not running.

Policy Not Found The LiveRecovery policy was deleted or is missing.

Initializing LiveRecovery is attempting to ping the node on which the VS is running.

Not Protected Ping was unsuccessful; the VS will not be moved to a new node and restarted if the current node fails.

Protected Ping was successful; the VS will be moved to a new node and restarted if the current node fails.

Figure 102 shows how to configure a VS for LiveRecovery™.

Figure 102. LiveRecovery™ Configuration

Enabling LiveRecovery™ for a virtual server

LiveMaintenance™ LiveMaintainence™ moves virtual servers to a new machine based on administrative intervention in the event a host server needs service. Server maintenance can be performed outside of scheduled maintenance windows without application downtime.

138 Virtualization Manager™ Administrator Guide LiveMaintenance™ with servers virtual Moving ration before production deployment. patch management activities can betested tual servers isautomatically optimized. Operating systemandapplication any time. Thepool’s capacity changes dynamically and theplacement ofvir- With LiveMaintenance™, physical serverscan beremoved and reinstated at Figure 103. LiveMaintenance™ Control CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS with asnapshot ofa “live”configu- Configuring Policies

139

. . . . . Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Moving Virtual Servers and Nodes

MOVING VIRTUAL SERVERS AND NODES

Virtual Iron® can adapt on-demand to changing business requirements. In this framework, virtual servers and the managed nodes that host them can be moved to accommodate administrative requirements. Objects that can be moved are described in Table 4:

Table 4. Object Movement in the Virtual Iron® Framework

Object Type Movement From, To...

Node • VDC to VDC • VDC to Resource Center

Virtual Server • Node to node • Node to VDC • Node to Unassigned

The Role of the Resource Center

Resource Center is the top-level object in the navigation tree. This object contains all VDCs, nodes, and VSs under management by Virtual Iron. Within the Resource Center, you can create separate node groups called Virtual Data Centers (VDCs). Each VDC is an administrative entity that can contain one or more managed nodes and the VSs hosted by these nodes. Moving Nodes to a VDC

Virtualization Manager supports drag-and-drop control for managed nodes. Use drag- and-drop to move a node from one VDC to another, or to or from the Resource Center. An example is shown in Figure 104. To move a node: Step 1. Select the node you want to move by depressing a mouse key. Step 2. Drag the node to its new location, and release the mouse key. Figure 104 shows managed node Options Node 2 (located in Finance One VDC) being dropped on gregvdc.

140 Virtualization Manager™ Administrator Guide Figure 104. Dragging a Node to a New VDC New a to Node a Dragging 104. Figure CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS Moving VirtualMoving Servers and Nodes

141

. . . . . Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Moving Virtual Servers and Nodes

Moving a Node to Resource Center

Managed nodes can only be used to host virtual servers when they belong to a VDC. Moving a node to a VDC places the node under ownership of that VDC. Moving a node from a VDC to Resource Center frees the node, making it available for reassign- ment to another VDC. Since virtual servers consume node memory (even when offline), nodes that host virtual servers cannot be moved out of their current VDC. Any attempt to move a node that still hosts virtual servers produces the message shown in Figure 105.

Figure 105. Message: cannot Move Node with Virtual Servers

Figure 106 shows a node being moved from a VDC and dropped on Resource Center.

Figure 106. Node moved to Resource Center

142 Virtualization Manager™ Administrator Guide Conditions forVirt MOVING AVIRTUALMOVING TO SERVER ANEWNODEORVDC L IVE M IGRATE disallowed. ager allowsthe operation.Ifthey arenot me the source nodecanfunction onthe target managed node,VirtualizationMan- tion Manager checksthe LiveMigrate requirements. Ifthe virtual servers on Before youcanplace a virtual server • • If thevirtual server is running: • • • • • or toa new VDC,Virtualization Manager evaluates thefollowing: Beforeservercan move youfrom avirtual onemanaged nodetoanother node offline virtual server fromone physical serverto another withLiveMigrate In multi-node environments, Virtual Iron® allows you to movearunning or server fromits existing location toanother node or virtual data center. You maydosowithout affecting applications. Simply drag anddrop the virtual TheVSTools checkbox must bechecked. - Accelerated driversmust beinstalled on thevirtual server - VS Tools mustbe enabled The destination mode must be runningalso. needed by the virtualserver? Does the node haveaccesstothe same network and/or SANresources Is there accessto acommon physicaldiskpool? Are there the same or agreater numberof CPUs? AMD-to-AMD migration isallowed. Are theprocessors ofthe same proces node as intheoriginal node. server? There must be atleast the sameamount ofmemory in thetarget Doesnode themanaged haveenough memo ™ R ual ServerMovement CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS EQUIREMENTS Figure 107 shows Options VS ona different managed node, Virtualiza- beingmoved to sor family? OnlyIntel-to-Intel or t, movementt,of thevirtualserveris Moving VirtualMoving Servers and Nodes ry toaccommodate thevirtual gregvdc . ™

143 .

. . . . . Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Moving Virtual Servers and Nodes

Figure 107. Moving a VS to a New Node

NODE CHOICES AND RESTRICTIONS Virtualization manager disallows movement of a VS to a VDC that has no nodes. If you attempt this operation, the following message appears:

If a VDC contains more than one node that is eligible to host the VS you are moving, the dialog shown in Figure 108 appears. To complete the operation, select a node from the list of those available, and click OK.

144 Virtualization Manager™ Administrator Guide Figure 109. Available 109. No Figure by Virtual for use Nodes Servers dialog box appears. ory, processors,oraccessto therequired SANand Networks,the following If you attemptto moveaVSto newVDC that does not havesufficient mem- available No nodes Nodes Available Figure 108. Choosing a Node to host aVS tohost aNode 108. Choosing Figure CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS Moving VirtualMoving Servers and Nodes

145

. . . . . Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Provisioning VSs with Gold Masters

PROVISIONING VSS WITH GOLD MASTERS

It is useful to create a gold master for each GOS supported in your data center. This is a logical disk that serves as a container for an installed GOS. When you need to create a new VS running that GOS, simply clone the master logical disk and assign it to the LV. You can boot the VS without going through the OS installation process again. Simply create a new VS and assign the cloned master logical disk to it. If you need to rapidly provision new VSs on an ongoing basis, it makes sense to maintain a set of gold masters. This saves time, since you perform an installation of each GOS only once. Thereafter, you can clone the GOS to make use of it as often as needed. Since the cloning operation copies the entire content of a logical disk to a new location, you can copy applications as well as GOSs. For example, you can create a GOS with a specific Linux or Windows distribution and the set of applications required by a particular set of work requirements. As a result, you can automate the delivery of fully or partially configured systems to specific functional areas as needed.

Note: Before creating and using a gold master, you should familiarize yourself with license requirements that may apply to the use of OSs and applications.

Creating a Gold Master Logical Disk Follow these steps to create a gold master for any GOS supported by Virtual Iron®. Step 1. Create a VS and configure it. Assign a logical disk to it. At this time, the logical disk is empty. Its purpose is to hold a bootable gold master. Rename the logical disk in a way that distinguishes it as such. For example, Gold-Win2007-04-25. Step 2. Copy the OS iso files onto a publicly addressable web server. This makes the files available for boot later on. Step 3. Copy the disk1.iso of the OS to the NBD directory of the Virtual Iron® management server. Step 4. Configure the VS to boot from NBD as described in Creating a Virtual Server. Step 5. Boot the VS from the ISO file. Step 6. During the http installation process, you will be prompted for the location of the CD ISO. Point to the web server containing the additional ISOs. Step 7. The installation proceeds, and installs the OS on the logical disk. Step 8. Shut down the VS, clone the gold master to a new logical disk, and boot the VS from that logical disk, instead of the original master.

146 Virtualization Manager™ Administrator Guide Cloning andBootingfroma See cloned (alongwiththeir GOS)foruse by newVSs. You can alsoinstall applications onthe goldmaster, so that thesecanbe Step 5. Step 4. Step 3. Step 2. Step 1. the same GOS toanother VSproceedas follows: useFrom thispoint, thelogical master. diskasagold Wheninstallto youneed Cloning Disks Boot the VS. boot disk. In theVSConfiguration window, designate the logical diskcloneas the Assign the LV to theVS. Export the logical diskcloneto an LV. Clone the goldmaster to anew logical disk. CREATING ANDCREATING CONFIGURING VIRTUAL SERVERS forinformation oncloninglogicaldisks. Gold MasterLogicalDisk Provisioning VSs with GoldMasters Provisioning VSs

147

. . . . . Chapter 7 CREATING AND CONFIGURING VIRTUAL SERVERS Provisioning VSs with Gold Masters

148 Virtualization Manager™ Administrator Guide 8

POLICIES AND REPORTS

......

This chapter shows how to use Virtualization Manager to configure policies and generate reports.

About Policies and Reports ...... 150 Report Types ...... 151 User Policies...... 156 Starting System Policies ...... 160

149 Chapter 8 POLICIES AND REPORTS About Policies and Reports

ABOUT POLICIES AND REPORTS

Virtualization Manager™ supports a set of policies and reports that you configure in various templates. To access these policy and report templates or to view generated reports: • Click Policies & Reports in the application toolbar, or • In the View menu, select Reports menu option. This opens the summary view shown in Figure 110.

Figure 110. Policies and Reports, Main View

Policy tabs Policy states

Policies and Reports

This screen displays all the policies and reports available to you in the navigation tree. The Policies and Reports tab lists all policies and their current states. These states are denoted by color coded icons: • Not running: blue • Scheduled: gold • Running: green • Failed: red If a policy or report is scheduled to run at a specific time, the time is listed. Click the Events tab to see all user- or system-related events associated with configured policies or reports. Click any of the column headings in the Policies & Reports or Events windows to sort the data by time, type, or description.

150 Virtualization Manager™ Administrator Guide R EPORT Generating Reports Report Namingand Types T YPES and time. For example: Reports are namedwith the name of thetemplate you areusing and the date Table 5. Virtualization ReportsManager™ vided: scheduled, orrun asneeded. These pre-formatted report templates are pro- reportsHTML orCSVformat.Aswithotherpolicies, in eitherthe output be can A report isthe result of specifying criteria inareport template and displaying For example, to create aData Center Operations report: To generate areport, enter data into thepolicy template and run the report. reports directory, located at: All reports canbeexported in CSVor HTML format. These arestoredinthe itaSreRpr Specify allvirtual servers, or selectfrom a list that VirtualServerReport Specify allcriteria options, or select from alistthat VirtualDisksReport Specify allcriteria options, or select from alistthat Specify atimeinterval ordate range. NodeReport Specify timeinterval ordate range, event severity, JobReport EventReport Report Type /opt/VirtualIron/DataCent Report_05_28_2007_02_13pm.html /opt/VirtualIron/DataCenterManager/sy in allVDCs,oraspecificVDC Unassigned. You can runareport for virtual servers includes Running, Stopped, AutoRecovered, and Virtual Disks. VDCs, and limit theoutput to Groups, Volumes or report forvirtualdisksinall,aspecific,orunassigned Mounted, LocalDisks,and SAN disks. You can runa includes Assigned, Unassigned, Mounted, Not VDCs. or unassigned tion, youcanrun a report for includes Running, Stopped, andProtected. Inaddi- and optionaldescription. Purpose erManager/system/reports stem/reports/DataCenter Operations POLICIES AND REPORTS nodes inall,aspecific, Report Types

151

. . . . . Chapter 8 POLICIES AND REPORTS Report Types

Step 1. Click the Policies and Reports button. Step 2. In the navigation pane, under Reports, select the type of report you want to generate. In the sample shown in Figure 111, NodeReport has been selected.

Figure 111. Report Template

Report template selected

Policy Options

Step 3. The Node Report informs you of node operations such as running or stopped nodes, or in error or protected nodes, in any or all Virtual Data Centers. Choose from the listed criteria by checking the boxes in the Summary screen. Choose HTML or CSV (comma separated values) for the report output. Step 4. Select the Schedule tab. Click the Edit button in the popup window that appears. Step 5. In the Schedule Configuration window, specify a run schedule for the report. You can choose to run a report once (immediately), daily, weekly, or monthly. In the time dropdown menu, click to highlight the hour or minutes and use the up and down arrows to specify the time. See Figure 112. Step 6. Click OK.

152 Virtualization Manager™ Administrator Guide Report Examples EVENT REPORT EVENT the timespecified in the Schedule tab. This report providesdetails on theevent Step 7. plates suppliedwith theVirtual Iron™software. Following are sample reports generated with thepre-formatted support tem- Figure 113. Report Output Tab Figure 112. Scheduling a Report open it.Asample tab isshown in To access reports, select the Report Output s specifiedin theSummarytab, and Figure 113 POLICIES AND REPORTS . tab. Clickareport to Report Types

153

. . . . . Chapter 8 POLICIES AND REPORTS Report Types

Figure 114. Sample Event Report

JOB REPORT

Figure 115. Job Report

154 Virtualization Manager™ Administrator Guide NODE REPORT NODE VIRTUAL REPORT SERVER Following isa sample Virtual Server report. Figure 117.Figure Virtual Report Server 116.Figure Report Node POLICIES AND REPORTS Report Types

155

. . . . . Chapter 8 POLICIES AND REPORTS User Policies

USER POLICIES

User policies are administratively configured to perform specified actions in response to certain conditions. Supported policies are shown in Table 6:

Table 6. Virtualization Manager™ User Policies

User Policy Purpose

EmailNotifier Allows you to send email to one or more addresses in response to specified events. RebootDataCenter Use to specify which nodes to reboot in the selected Virtual Data Centers. Virtual servers that are running are stopped and restarted when their parent nodes return online. Virtual servers with VSTools installed are shut down; virtual servers without VSTools are that are starting up, are hard reset, if desired. However, it is preferable to shut down those virtual servers directly from within each guest. SystemBackup Allows you to specify where backups of the Virtu- alization Manager database are to be stored, and the number of copies to retain.

Configuring and Starting User Policies

A user policy instructs Virtualization Manager to perform certain actions in response to specified conditions, and schedules when those actions are to be taken. An email policy might be translated as: Send email to me and my colleague if any VS is in error. Another email policy might be: Send email to both of us if any node is in error, or if a warning message is issued in relation to a specific VDC. For example, to configure an email policy: Step 1. Click Policies & Reports. In the navigation pane under User Poli- cies, select EmailNotifier. Step 2. n the Summary screen, provide information on policy actions, as shown in Figure 118.

156 Virtualization Manager™ Administrator Guide criteria Add message actions associated Objects and Add recipients Step 3. Step 4. Figure 118. Options, Sample Email Policy Identify a recipient, Add these criteriabychoosing anobject type fromthe A specific node haserrorevents • A specific virtualdata center(NewVirtual Data Center) has • virtualserverisinerror Any • case, emailwillbesentwhen any of thesecriteriaaremet: and/or virtual objects, and thestates associated with them.Inthis warnings”) willbe sent. Specify these criteriabychoosing physical These criteria determine when the message (“data centerfailures, The basis ofthe policyisthecriteriathat trigger theemail message. the emailmessage (the latter is optional). menu, orcopythe template and rename it, as shownin Rename thetemplate if you wish. Select Click down and selecting an associated action fromthe warning events Add>> to addthe criteria tothe list. [email protected] POLICIES AND REPORTS , amailhost,and asubject for Rename from the pop up Has pull-down. Object Figure 119 User Policies pull-

157 .

. . . . . Chapter 8 POLICIES AND REPORTS User Policies

Figure 119. Copying and Renaming an Email Template

Step 5. Click the Schedule tab. In the Schedule Configuration window, specify a run schedule for the report. You can choose to run a report once (immediately), daily, weekly, or monthly. In the time dropdown menu, click to highlight the hour or minutes and use the up and down arrows to specify the time. See Figure 112. Step 6. Click OK. Step 7. Choose start and stop dates and (optionally) times from the pull down lists, and choose a schedule period. If you do not enter a parameter from Run this policy and click once, the policy runs immediately when you start it. A sample scheduling tab is shown in Figure 120.

158 Virtualization Manager™ Administrator Guide dates and and times dates Choose start andend ing parameters ing schedul- Choose now Start policy selected Policy Step 8. Figure 121. 121. StartingFigure aPolicyor Report Figure 120. Email Policy, Schedule Tab Start To start thepolicy, selectthepolicy in the navigationtree andclick as shown in Figure 121 . POLICIES AND REPORTS User Policies

159

. . . . . Chapter 8 POLICIES AND REPORTS Starting System Policies

STARTING SYSTEM POLICIES

System policies have system-wide application and run in the background according to specified parameters. Once started, they are always running. Vir- tual Iron® supports the system policies listed in Table 7.

Table 7. Virtualization Manager™ System Policies

System Policy Purpose

AutoRecovery™ Moves virtual servers on nodes that go offline to a healthy node and then restarts it in the event its host fails.The policy is run automatically by the system when LiveRecovery is enabled for a virtual server. LiveCapacity™ Balances CPU utilization across selected nodes in a virtual data center by using LiveMigrate to perform virtual server migration without downtime. To balance CPU utilization across selected nodes in a virtual data center, enable LiveCapac- ity on the virtual data center’s Live Capacity tab. Technical Support Access to Virtual Iron Technical Support.

System Policies differ from User policies in two ways. • They apply to all physical and virtual objects under management, rather than a subset of these objects. • They run at all times, rather than on a scheduled basis. LiveCapacity and AutoRecovery

LiveCapacity™ is a system-wide policy that enables load-balancing of VSs within VDCs. AutoRecovery™ is a system-wide policy that allows a VS to move and restart on a new node in the event its host node fails. To enable either of these system policies, select the policy in the navigation tree, and click Start. You may optionally choose start and stop dates and times from the pull down lists, and choose a schedule period. If you do not enter a parameter from Run this policy and click once, the policy runs immediately when you start it.

160 Virtualization Manager™ Administrator Guide policy policy St St policy the Select ar ar policy the Select t Technical Support t

th th e e Step 4. Step 3. Step 2. Step 1. To access Virtual Iron Technical Support: 122. Starting Figure Policy the AutoRecovery™ Figure 123. 123. StartingFigure aPolicyor Report 123 To sendthe data to Technical Support, click Type inthe requireddata. In the navigation pane, click Click the . Policies & ReportsPolicies & TechnicalSupport button. POLICIES AND REPORTS Start . Starting Policies System as shown in Figure

161

. . . . . Chapter 8 POLICIES AND REPORTS Starting System Policies

162 Virtualization Manager™ Administrator Guide 9

PERFORMING ADMINISTRATIVE TASKS

......

This chapter shows how to perform a number of administrative tasks. It contains the following sections.

Configuring User Accounts...... 164 Configuring LDAP...... 167 Configuring Non-English Keyboards ...... 174 Performance Statistics...... 177 Starting the Virtualization Manager...... 183 Performing Backup and Restore Operations...... 185 Changing the Virtualization Manager IP Address...... 187 Configuring the Archive Manager ...... 188 Assuring Virtualization Manager High Availability...... 189 Single Node to Multi-Node Conversion ...... 193 Uninstalling Virtualization Manager ...... 195 Reassigning Unassigned DGs...... 196 Accessing Online Help ...... 197 Accessing Technical Support...... 199

163 Chapter 9 PERFORMING ADMINISTRATIVE TASKS Configuring User Accounts

CONFIGURING USER ACCOUNTS

Virtualization Manager supports user accounts and associated passwords. These accounts can be local, or can exist on an LDAP server. The following section describes how to configure local accounts. See Configuring LDAP for information on configuring LDAP authentication. Creating Local User Accounts

Only an Admin user can create or delete Local user accounts. A default Admin account, with username and password Admin, is created during installation of the software (see Installing Virtual Iron®). To create additional accounts: Step 1. Log in to Virtualization Manager™ as Admin. Step 2. Click the Users button in the Application toolbar on the left. The Users accounts view opens. See Figure 124. Step 3. To create a new user account, click the Users icon in the Action toolbar, or right click Users in the navigation tree. See Figure 125.

Figure 124. User Account View

Users, Application Toolbar

164 Virtualization Manager™ Administrator Guide Click Users Icon Users Right Click Deleting User Accounts Action Toolbar: Delete Select theUseraccount inthe navigation tree and select Only personnel with Adminprivileges Step 4. iconinthe toolbar. See Figure 126. Deleting User Accounts User Deleting 126. Figure Account User a New 125. Creating Figure user. Click full name andthenthe user’s enter andconfirm a password forthe The default name OK . PERFORMING ADMINISTRATIVETASKS NewAccount User Figure 126 are allowed todeleteuseraccounts. . isassigned to the account. Enter Configuring UserAccounts Delete orclick the

165

. . . . . Chapter 9 PERFORMING ADMINISTRATIVE TASKS Configuring User Accounts

Editing Account Information

To edit user account information, select an account in the navigation tree and select Edit User Account. The dialog box shown in Figure 127 appears. Make the changes, and click OK.

Figure 127. Editing Account Information

166 Virtualization Manager™ Administrator Guide C ONFIGURING LDAP Component Information Component LDAP LDAP SupportandAdministration About LDAPAuthentication LDAP include thefollowing: mon set of components that areusedin specific ways. The components LDAPtories. Though implementations may differ slightly,com- athey preserve LDAP directories store data hierarchically, similartoDNStrees, orUnix direc- can be usedagain ifLDAPis disabled. However, local account information remains on themanagement serverand When LDAP isenabled, theuser accounts on thelocalserverare disabled. the javakeystore of the Virtualization Manager. Note: protocol on Virtualization M ToLDAP, use criteria andenableprovideto youneed theLDAP asetofLDAP interface). or open-source LDAPdirectory servers—even aDBMSserver withan LDAP to communicate withit.Theany servercanbenumberaof one commercial of to knowdo notneed whattypeof cations has the advantage of being platform-independent and standards-based. Appli- LDAP isa protocolused to store and access information inadirectory. LDAP Open LDAPforLinuxdistributions. Virtual Iron® supports both Microsoft ActiveDirectory (forWindows®) and base. authentication (Lightweight Directory AccessProtocol) via acentralized data- In addition tolocaluser accounts, Virtualization Manager supports LDAP configuration. allowed tolog intothe Virtualization Manager or makechanges to the LDAP To use LDAP over SSL,youmust import the LDAP SSLcertificate into PERFORMING ADMINISTRATIVETASKS anager. Only personnel with server is hostingtheLDAPdirectory server Admin Configuring LDAP privileges are

167

. . . . . Chapter 9 PERFORMING ADMINISTRATIVE TASKS Configuring LDAP

Component Abbreviation Definition Name

Distin- dn The top level of the LDAP directory tree is guished the base DN. Name Common cn When using LDAP to authenticate users of Name Virtual Iron®, the common name refers to a user’s full name. Organization o The organization component.

Domain dc The domain component. Component Organiza- ou Organizational units that further subdivide tional information in a dc. Unit

Configuring Virtual Iron To Authenticate with LDAP

LDAP authentication requires enabling Virtualization Manager to access user information stored on an LDAP server and enabling the LDAP protocol. You need to know which LDAP implementation is in use at your site. The implementation determines the proper syntax to use to pass LDAP credentials and search criteria to the LDAP server. For information on the LDAP components to pass and the proper syntax, contact your LDAP system administrator. To configure LDAP authentication for the Virtualization Manager: Step 1. Click Users on the application toolbar. Select the LDAP tab. The screen shown in Figure 128 appears.

168 Virtualization Manager™ Administrator Guide Step 2. Figure 128. LDAP Authentication Tab Authentication 128. LDAP Figure To do this,click Before youenable LDAP, enter LDAP Credentials and Search criteria. • • The LDAPtab has twopanes. In thisexample, LDAP information has been added. within theVirtual Iron®framework. to add someorall of themtothe listofthose that canmanage criteria to identify a set of users. Use the connectsLDAP tothe server, Virtualizationtheseuses Manager Manager applies the criteria youenter to filter thedata. Whenit the userdata stored inthe LDAPsearchbase. Virtualization Search Criteria the LDAPdirectory fromwhichyour LDAPsearch willbegin. within thatDN.The search base defines the specificlocation in distinguished name(D server’s Credentials —Records theURLof LDAPserver, the Setup... PERFORMING ADMINISTRATIVETASKS —Provides thecriteriausedtomatchagainst Thedialog shown in N), andthe LDAPsearch base Assign Users... Figure 129 Configuring LDAP is displayed. displayed. is dialog dialog

169

. . . . . Chapter 9 PERFORMING ADMINISTRATIVE TASKS Configuring LDAP

Figure 129. Entering LDAP Credentials and Search Criteria

Step 3. Enter LDAP credentials and search criteria. Click Test Data... to vali- date the data. Virtualization Manager connects with the LDAP server and uses the search criteria you provided to return a list of users. Fig- ure 130 shows a sample of the test results window. Click OK to accept the configuration.

Figure 130. Adding LDAP User Data to the Virtualization Manager Database

170 Virtualization Manager™ Administrator Guide Step 4. LDAP Full User Name: cn LDAP UserName: cn uid Search Filter: (& (cn={0})(objectClass=inetOrgPerson)) Search Criteria LDAP Search Base:ou=users,dc=qadev,dc=local DN Password: DN: cn=admin,cn=Users,dc=qatest,dc=com URL: ldap://123.45.67.23 Credentials Sample LDAPData, OpenLDAP LDAP Full User Name: sAMAccountName LDAP UserName: userPrinci Search Filter: (& sAMAccountName={0}(objectClass=User)) Search Criteria LDAP Search Base:cn=Users,dc=qadev,dc=local DN Password: DN: cn=Adminstrator,cn=Users,dc=qadev,dc=local URL:ldap://10.1.20.3/ Credentials Sample LDAPData, Active Directory the LDAPserver. A sample isshownin appears contains allofthe users Virtualization Manager hasfound on assign LDAP users.Click After the LDAPcredentials have been validated, you areready to LDAP inActive Directory, andOpenLDAP. Following are examplesof validparameters for the implementation of ment server,ment usethe To assign one ormore of theseusersto thelist stored onthe manage- the left to theright pane. Click password password PERFORMING ADMINISTRATIVETASKS Add>> Assign Users... and palName sAMAccountName name OK <

171

. . . . . Chapter 9 PERFORMING ADMINISTRATIVE TASKS Configuring LDAP

Figure 131. Adding LDAP User Data to the Virtualization Manager Database

Step 5. Click Enable LDAP as shown in Figure 132.

Figure 132. Enable LDAP

Enable LDAP Authentication

Step 6. The LDAP users you have assigned appear on the management UI. A green check mark next to the User icons identifies users authenticated with LDAP, as shown in Figure 133. The user names that appear in the navigation tree is data retrieved via LDAP based on the User Name attribute. The Full Name information is retrieved via LDAP based on the Full User Name Attribute.

172 Virtualization Manager™ Administrator Guide Changing theLDAPConfiguration Name LDAP Full From selected user LDAP Manager and manage resources. Note thatwhile LDAPisdisabled, loca check Setup... changes to thecriteria, uncheck the You cannot edit LDAPsearch criteria whileLDAPisenabled. To make ration. Only personnelc withAdminprivileges Virtualto the Added Database Iron Users 133. LDAP Figure Enable LDAP and make whatever changes are required. Test thechanges and tore-enable theprotocol. PERFORMING ADMINISTRATIVETASKS Enable LDAP l userscan connectVirtualization tothe an make changes to the LDAP configu- checkbox. Then click Configuring LDAP

173

. . . . . Chapter 9 PERFORMING ADMINISTRATIVE TASKS Configuring Non-English Keyboards

CONFIGURING NON-ENGLISH KEYBOARDS

You must use the US-English 101 keyboard in order to enter text for the Virtual Console. Non-English keyboards do not map their keys properly. Users of Japanese, German, and other non-English 101 keyboard types, can use the following procedure to set the Virtual Console’s keyboard. Workaround

Java 1.6 fixed a number of long standing key map/keyboard issues. Therefore, for Virtual Iron’s virtual server console to work with non-English keyboards, it must be run in a Java 1.6 runtime environment. Following are instructions for installing Java 1.6 on a client that has a non- English keyboard, and for configuring a guest OS and virtual server to use the corresponding key map.

INSTALL JAVA 1.6 Download the latest Java 1.6 from http://www.java.com/en/download/man- ual.jsp and install it on the computer used to run the Virtualization Manager. When you start the Virtualization Manager, check the first two lines of Java Console output to make sure that you're using the correct version. You should see something similar to the following: Java Web Start 1.6.0 Using JRE version 1.6.0 Java HotSpot (TM) Client VM

CONFIGURE KEYBOARD Configure the guest OS to use the correct keyboard. If it isn't already configured: • Start the virtual server (it will use the default en-us key map). • Start a virtual server console. • Configure the guest OS to use the correct keyboard. You must use the en- us key map to do this. For example, if you're using a German keyboard (QWERTZ not QWERTY—the Z and Y are swapped), and need to enter the letter Y, type the Z key (German keyboard, English key map). The API has methods to set and get the name of the key map used by virtual server consoles. The default key map name is en-us. It can be overridden at the foundry, virtual data center, or virtual server level. The key map names cor- respond to the names of the QEMU key map used by Xen. Each key map name consists of an ISO 639-1 language code: (http://www.loc.gov/standards/iso639-2/php/English_list.php) These are optionally followed by a dash and an ISO 3166-1 country code:

174 Virtualization Manager™ Administrator Guide rh si al lv pt-br fr-ch lt pt tr fr-ca ja pl th es fr-be en-us no it sv fr en-gb nl-be de-ch is sl fo nl de hu ru fi mk da hr et ar en1.html ( Use The followingkey mapnamesaresupported. http://www.iso.ch/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list- runner 'en-us' >>> vdc.getKeymapName() >>> vdc=vs.getAssociatedVirtualDataCenter() 'en-us' >>> vs.getKeymapName() >>> vs.setKeymapName(None) >>> #configure VS123 to inherit keymapfrom its VDC 'de' >>> vs.getKeymapName() >>> vs.setKeymapName('de') >>> #configure VS123 to useGerman keymap 'en-us' >>> vs.getKeymapName() >>> vs=cm.findObject(VirtualServer, 'VS123') >>> cm=VirtualizationManager.getConfigurationManager() >>> fromcom.virtualiron.vce.mg >>> fromcom.virtualiron.vce.mg >>> fromcom.virtualiron.vce.mgmt.apiimport* Virtualization Manager APIRunner: v3.0Interactive Mode # ./runner.sh ) toconfigurekey maps. For example: Supported KeyMapNames PERFORMING ADMINISTRATIVETASKS mt.api.virtual import* mt.api.physical import* Configuring Non-English Keyboards Configuring Non-English

175

. . . . . Chapter 9 PERFORMING ADMINISTRATIVE TASKS Configuring Non-English Keyboards

>>> vdc.setKeymapName('de') >>> vdc.getKeymapName() 'de' >>> # by default all virtual servers in this VDC will use 'de' >>> vs.getKeymapName() 'de' If a virtual server is running, restart it for the new key map to take effect. Note that there are still a few key map issues, even if you use Java 1.6, as when for example, a virtual server console displays a text console (the one that looks like a vt100 terminal). This is alleviated once you start up a graphical desktop such as Gnome. Only dead keys continue to be a problem when a graphical desktop is used. Using the virtual server console to interact with a graphical desktop on the guest OS, you can configure VNC or Remote Desktop. If you need to use dead keys to produce diacritical marks above letters, don’t use the virtual server console. Instead, switch to a native VNC or Remote Desktop client.

176 Virtualization Manager™ Administrator Guide P ERFORMANCE Accessing PerformanceStatistics S Step 2. Step 1. To viewperformance statistics in Center’s Each of thesedata categories areorganized inadashboard in theResource • • • • • • • Virtualization Manager collects and presents statistics for theseareas: Node statistics areavailable and virtual servers. Virtualization Manager provides perform Step 3. See able onlyifVStools has been installed on TATISTICS User Connections Active Policies License Usage Virtual ServerPerformance Node Performance Last 5Errors Activity forthe Resource Center Installing VSTools on Virtual Servers window opens withthe Select Click the the dashboard. See Click oneormore oftheperformance Summary Resource Center Resource Center screen. PERFORMING ADMINISTRATIVETASKS Figure 134 at alltimes;statistics on Summary in the navigation tree. The Resource Center inthenavigationtree.TheResource Virtualization Manager, do the following: button. . ance andactivity statistics on nodes forinformation. tab active. the virtualserver being monitored. statistics categories displayed in virtualserversare avail- Performance Statistics

177

. . . . . Chapter 9 PERFORMING ADMINISTRATIVE TASKS Performance Statistics

Figure 134. Resource Center Activity Screen, showing dashboard options

ACTIVITY FOR THE RESOURCE CENTER Figure 135 shows a close-up of the initial screen with Resource Center level data for Nodes, Virtual Servers, and LiveCapacity.

Figure 135. Resource and Activity Data

LAST 5 ERRORS To view the last five errors associated with the Resource Center, select Resource Center in the navigation tree. In the Summary screen, click the Last 5 Errors tab. Error data is displayed with a timestamp of the occurrence, the object, and a brief summary of the issue.

NODE PERFORMANCE You can view node performance by using the procedure described in Access- ing Performance Statistics. See Figure 136.

178 Virtualization Manager™ Administrator Guide tion tree, and then click To seethe performance ofa use. Relative Load played data from highest to lowest orvice versa. The mance pane. Clickany ofthe column hea Note thatyoucansetthenumber ofrows data displayed inthe Node Perfor- played in10-minute increments. See representation ofthe node’s disk,network, memory, and CPUusageare dis- Figure 136. Node Performance Detail Performance Node 136. Figure columnsare avisual representation in termsof percentage of Performance PERFORMING ADMINISTRATIVETASKS specific node, clickthe node iconin thenaviga- Figure 137 in the Summaryscreen. Agraphical dings toswitch theorder ofthe dis- . CPU Utilization Performance Statistics and

179

. . . . . Chapter 9 PERFORMING ADMINISTRATIVE TASKS Performance Statistics

Figure 137. Node Statistics

VIRTUAL SERVER PERFORMANCE Virtual Server statistics are available only if VSTools is enabled for the GOS booted by a virtual server. In addition to using the Summary screen to view all VS statistics, you can click a specific VS icon in the navigation tree to see its data. Note that you can set the number of rows of data displayed in the Virtual Server Performance pane. Click any of the column headings to switch the order of the displayed data from highest to lowest or vice versa. The CPU Uti- lization column is a visual representation in terms of percentage of use. See Figure 138

180 Virtualization Manager™ Administrator Guide CPU usageare displayed in 10-minute increments. See graphical representation ofthe virtual in the navigationtree, and thenclick To seetheperformance ofa Figure 139. 139. Virtual Figure StatisticsServer Detail 138. Virtual Figure Performance Server PERFORMING ADMINISTRATIVETASKS specific virtual server,the virtualclick servericon Performance server’s disk, network, memory, server’s and in theSummary screen. A Figure 139 Performance Statistics .

181

. . . . . Chapter 9 PERFORMING ADMINISTRATIVE TASKS Performance Statistics

LICENSE USAGE The License Usage pane shows how many resources are being used in relation to the total available for use. See Figure 140 for an example of the type of data displayed in the License Usage pane.

Figure 140. License Usage Detail

ACTIVE POLICIES Use the Active Policies pane to track which policies are scheduled and which are running. See Figure 141.

Figure 141. Active Policies Detail

USER CONNECTIONS The User Connections pane shows which users are connected and at what time they logged on.

182 Virtualization Manager™ Administrator Guide S TARTING Starting theVirtualization Manager, Windows® Starting theVirtualization Manager, Linux®

THE V Step 1. After completing an installation on Windows: ment node after installation. Note: You arepresented with ment node, type: After installing Virtual Iron® start the Virtualization Manager. Onthemanage- Server Edition, whichdoesnot requireahosting OS. ManagerTheseWindows®. onLinuxinstructions or donotapplytotheSingle tohowThe instructionsthatfollowexplain start theVirtualVirtualization Iron® server. IRTUALIZATION You can alsostart theVirtualization Manager byrebooting the manage- /etc/init.d/vivmgr Choose trator or Owner(inthe caseofWindows® XP). prompted for apassword. Enter the password of thesystemAdminis- Programs ->Virtualization Manager ->Install Service. Install and start the Virtualization Manager as aservice. Choose Programs ->Virtualization Manager ->Start Service M start PERFORMING ADMINISTRATIVETASKS ANAGER and stop options. Choose Starting the Virtualization Manager start.sh to start the You are All

183

. . . . . Chapter 9 PERFORMING ADMINISTRATIVE TASKS Starting the Virtualization Manager

Step 2. Navigate to Control Panel ->Administrative Tools-> Services. Virtu- alization Manager is listed as a service. Start the service as shown here.

184 Virtualization Manager™ Administrator Guide P ERFORMING now policy Start policy Backup Restoring the Configuration Database Configuration the Restoring Backing uptheCo B ACKUP Step 3. Step 2. Step 1. Perform backup operations by running a backup policyfrom the UI: objects. the Virtualization Manager. Backed up data includesthestate ofall virtual The Virtualization Manager database canbe backed upon thesystem hosting command. To run thescript,change directorytoth lation directory on the Vi you specify, and restarts theVirtualization Manager. The script is inthe instal- down the Virtual Iron Virtualization Ma To restore asaved configuration desk, r Figure 142. Running a Backup Policy back ups, see Start To run abackup policyimmediately, SystemBackup Click user sessions. vi allCancel currentclose all jobs, nfiguration Database

AND Policies and Reports as shown in R ESTORE Policies andReports asshown. PERFORMING ADMINISTRATIVETASKS rtualization Manager host. Figure 142 O PERATIONS in the application toolbar. Then select . To configure thesystemfor scheduled nager, untars and runsthe backup file Performing Backup and Restore Operations e installation directory. Then use this un the restore script. Thisscript shuts rtual console sessions, and closeconsole sessions, rtual all . select SystemBackup andclick

185

. . . . . Chapter 9 PERFORMING ADMINISTRATIVE TASKS Performing Backup and Restore Operations

LINUX: # /opt/VirtualIron/restore.sh backup/backup..tar WINDOWS: C:\Program Files\VirtualIron\restore.bat backup\backup. .tar

186 Virtualization Manager™ Administrator Guide C HANGING

THE V Step 5. Step 4. Step 3. Step 2. Step 1. Follow thesesteps tochange theVirtualization Manager IP address: Virtualization Manager to adifferent subnet after installation. It may sometimesbecomenecessaryto rearchitect the networkormove the IRTUALIZATION VirtualizationManager\etc\dhcpd.leases to VirtualizationManager\etc\dhcpd.leases_default VirtualizationManager\etc\dhcpd.conf to VirtualizationManager\etc\dhcpd.conf_default Start the Virtualization Manager andreboot allnodes. Copy the file: Copy the file: Manager system viathe hostoperating system. Change the IPaddress ofthe dedicated networkonthe Virtualization Stop theVirtualization Manager. M PERFORMING ADMINISTRATIVETASKS ANAGER Changingthe Virtualization ManagerAddress IP IPA DDRESS

187

. . . . . Chapter 9 PERFORMING ADMINISTRATIVE TASKS Configuring the Archive Manager

CONFIGURING THE ARCHIVE MANAGER

The archive manager is a background process that runs continuously. The archive manager moves all jobs and associated events that are older than a specified date to a secondary location in the Virtualization Manager database. This reduces the size of the working set of jobs and events stored in the Virtu- alization Manager’s primary database.

To configure the archive manager, proceed as follows: Step 1. Choose Archive Manager from the File pull down menu. This displays the window shown in Figure 143. By default, the archive manager runs every day at 2 am. The operation keeps 500 most recent jobs and associated events, and 10,000 most recent non-job events. Such events would include hardware failures and environmental events. The operation deletes all jobs, events, and statistics older than 90 days.

Figure 143. Archive Manager Defaults

Step 2. You can edit the defaults, as shown in Figure 143. You can run the archive manager at any time, but it is best to run it when activity on the Virtualization Manager is light.

188 Virtualization Manager™ Administrator Guide A SSURING V IRTUALIZATION no interruption of serviceforany of the hardware or software failure, thevirtual infrastructure continues torun; there is This assuresthatifthe Virtualization Manager isunavailable because ofa tion Manager, whichcontrolsvirtual in for failure scenarios. Use thefollowing procedure toassure thatthe Virtualiza- As you deploy Virtual Iron inproduction environments, you may want to plan al rsic Nodeappears Cable orswitch vices Virtualization ser- hsclsre Nodeappears Physical server server ager physical Virtualization Man- ager filesystem Virtualization Man- ager software Virtualization Man- Failure M ANAGER loss of control to be down; to be down Node appears to be down Manager Virtualization Cannot access Manager error Virtualization Manager Virtualization Cannot access PERFORMING ADMINISTRATIVETASKS Symptom H IGH Assuring VirtualizationAssuring frastructure, isreadilyavailable. A virtual machines inyour environment. ment network able inmanage- pathing not avail- switches; multi- cables or Replace faulty yl oepwrVirtual servers Cycle node power physical hardware physical servers to spare migrate virtual Manager to Use Virtualization sive server Fail over to pas- from backup Restore object tion Manager Restart Virtualiza- VAILABILITY Recovery Manager HighAvailability continue torun Virtual servers restarted must be restarted must be Virtual servers continue torun Virtual servers continue torun Virtual servers continue torun Virtual servers Result

189

. . . . . Chapter 9 PERFORMING ADMINISTRATIVE TASKS Assuring Virtualization Manager High Availability

High Availability Considerations

It is recommended that the Virtualization Manager database is backed up on a nightly basis. This assures that the database can be restored in the event of a disk failure. A network power controller and network monitoring software can fully automate Virtualization Manager failover. Network monitoring software monitors port 80 or 443 to check the status of Virtualization Manager. Alternatively, a heartbeat script can be written using the command /etc/init.d/vivmgr status. The active server can be powered off and the passive server powered on manually, or automatically, with a network power controller. Once this server boots, the Virtualization Manager is back online without any affect on the availability of any virtual server. If the management server fails while objects in the Resource Center are being modified, when the failover management server restarts, these objects may be locked. To remove the locks, abort any pending jobs. Operations in progress may be completed but errors could appear. No statistics are collected while the Virtualization Manager is down. This resets the interval that policies wait to perform actions based on resource utilization. ACTIVE/PASSIVE SERVER CONFIGURATION To decrease the time Virtualization Manager is offline, Virtual Iron recommends using Active/Passive clustering technology. The following steps describe how to configure your environment: Step 1. Configure two identical servers. Ensure they have the same hardware. Refer to Figure 144. Step 2. Install a supported server operating system—Windows 2003, Red Hat 4, or Novell SLES 9. Configure the servers to boot from the same SAN or iSCSI LUN. We recommend that the LUN is mirrored using hardware RAID. Do not boot the servers simultaneously; only one server can be active at a time. Step 3. Follow the steps in the Administrator's Guide to install the Virtualiza- tion Manager server on the Active server. Step 4. Go to one of these directories: /opt/VirtualIron/VirtualizationManager/etc Program Files\VirtualIron\VirtualizationManager\etc

190 Virtualization Manager™ Administrator Guide Step 9. Step 8. Step 7. Step 6. Step 5. intf =[‘00:0d:56:e7:15:49’,’00:90:96:a6:e3:6f’] intf =[‘00:0d:56:e7:15:49’,] # interface serving node commands intf =[‘00:0d:56:e7:15:49’,’00:90:96:a6:e3:6f’] intf =[‘00:0d:56:e7:15:49’,] # interface serving node commands intf =[‘00:0d:56:e7:15:49’,’00:90:96:a6:e3:6f’] intf =[‘00:0d:56:e7:15:49’,] # interface serving DHCP intf =[‘00:0d:56:e7:15:49’,’00:90:96:a6:e3:6f’] intf =[‘00:0d:56:e7:15:49’,] #interface serving TFTP intf =[‘00:90:96:a6:e3:6b’,’00:90:96:a6:e3:6f’] intf =[‘00:90:96:a6:e3:6b’,] # interface serving HTTP server after the comma. Forexample: Add the MAC from the management networkNIC on thepassive Open thetunnel.properties file andfind the line: server after the comma. Forexample: Add the MAC from the management networkNOC onthe passive Open theaction.properties fileand find the line: server after the comma. Forexample: Add the MAC from the management networkNIC on thepassive Open thedhcpd.properties file andfindthe line: server after the comma. Forexample: Add the MAC from the management networkNIC on thepassive Open thetftpd.properties fileand find theline: the comma.For example: Add the MAC fromthe Open theweb.properties file andfindthe line: PERFORMING ADMINISTRATIVETASKS public Assuring VirtualizationAssuring network NICon thePassive server after Manager HighAvailability

191

. . . . . Chapter 9 PERFORMING ADMINISTRATIVE TASKS Assuring Virtualization Manager High Availability

Figure 144. SLES Install Driver Window

192 Virtualization Manager™ Administrator Guide S INGLE Prior toConverting N CONVERTING SSETOEEVIRTUALIZATIONCONVERTING MANAGER ODE

TO Step 2. Step 1. NIC, and reboot before youperform the conversion procedure. If youneedtoinstall anad used. NIC port.Your SSEservermay already haveasecondportthat is not being ConvertingServer fromSingle Edition secondEnterpriseto Edition requiresa same. tual Iron Management software, and that thetimeand date settings arethe prise Edition Virtualization Managers are both running the same version of Vir- Note: Step 3. the Enterprise Editioninstall, itwillbe erased. WARNING Step 7. Step 6. Step 5. Step 4. Step 8. M ULTI Before converting, assure that yourSingle ServerEdition and Enter- named Backup and select In the Administration Manager, clickthe pulldown arrow nextto Virtualization Manager. Launch the Virtual Iron Administration Manager on your single node In the Administration Manager, clickthe the backup directory onyour multi-node Virtualization Manager. Management and select In the Administration Manager, clic server. Launch the Administration Manager on themulti-node management Make sure that theBIOSon formersinglenode issetto PXE boot. managedmanagement bythenewmulti-nodeinto thenetwork server. Take anew Ethernet cableand plug primary Ethernet portserver’s andplugitinto thesecondary port. Unplug the public Ethernet fromyour single node management product version number. backupDB.X.Y.tar Navigate to your backup directory and select your backupfilenamed and select Locate the : Beforeperforming thenext step,note thatifyouhave any data on -N ODE backupDB.X.Y.tar GetaFile fromtheVirtualization Manager backupDB.X.Y.tar C ONVERSION PERFORMING ADMINISTRATIVETASKS , whereXisthe dateof thebackup and Yisthe ditional NIC, shutdowntheSSEserver, install the Database Only Put aFileonto theVirtualization Manager . file on your localmachine and place itin k the pulldown arrow nexttoFile . This creates abackup .tar file Single Node to Multi-Node Conversion your primary network interface File Management . pulldown

193 ...... Chapter 9 PERFORMING ADMINISTRATIVE TASKS Single Node to Multi-Node Conversion

Step 9. On the command line in your management server console, type restore.sh/ .bat backupDB.datetime.4.x.x.tar Step 10.Restart the Enterprise Edition Virtualization Manager. Step 11.Power cycle the node that was originally the Single Server Edition Vir- tualization Manager. Step 12.On the Enterprise Edition Virtualization Manager, copy etc/dhcpd.conf_default to etc/dhcpd.conf Copy etc/dhcp.leases_default to etc/dhcpd.leases Step 13.Use the same password for your Enterprise Edition Virtualization Manager that you used for your Single Server Edition, and log in.

194 Virtualization Manager™ Administrator Guide U NINSTALLING Uninstalling fromWindows Uninstalling fromLinux V Step 4. Step 3. Step 2. Step 1. Follow thesesteps touninstall Virtualization Manager. To uninstall Virtualization Manager fromLinux, enter this command: dows®. Following are procedures foruninstalli IRTUALIZATION /opt/VirtualIron/Uninstall_VirtualizationManager to complete the Uninstall process. Navigate to Program Files. Selectthe Virtual Iron folder, and deleteit Uninstall alization Manager Select Remove Service Select window closeswhen theservice is stopped. A command windowisdisplayed as the service is beingstopped. The gate to As the Administrative Userthat installed Virtualization Manager, navi- Start >Programs >Virtualization Manager >Uninstall Virtu- Start >Programs > Virtualization Manager > Start >Programs Virtualization Manager>Stop Service to uninstall theVirtualization Manager. Click M PERFORMING ADMINISTRATIVETASKS ANAGER . . AVirtual Irondialog window is displayed. Click ng Virtual Iron®from LinuxandWin- Uninstalling Virtualization Manager Done .

195 ...... Chapter 9 PERFORMING ADMINISTRATIVE TASKS Reassigning Unassigned DGs

REASSIGNING UNASSIGNED DGS

If you need to upgrade to the next version of Virtual Iron®, it is recommended that you perform a system upgrade, rather than reinstall the software. Occa- sionally, it may be necessary to reinstall the software. If you reinstall the product, the associations between DGs created previously and the VDCs configured in the system’s database are lost. The information associated with the DGs still exists on the SAN. However, although Virtualiza- tion Manager can discover this information during the discovery phase, it can not determine which VDC(s) to associate with these orphan DGs. They appear at the Resource Center level in the Logical Disks tab. An example is shown in Figure 145.

Figure 145. Unassigned DGs

Unassigned DGs

Assign DG to a VDC

Choose a VDC from the list

For orphaned DGs to be of use, they must be reassigned to VDCs. To reassign VDCs, select each DG. Click Assign..., and choose the VDC from the pull down list. Click OK. Perform this procedure for each orphaned DG.

196 Virtualization Manager™ Administrator Guide A CCESSING option menu Help icon Help O NLINE Step 1. To access onlineHelp: Step 2. 147 H . Figure 147. Help Icon Help 147. Figure • Menu Pull-down Help 146. Figure • Perform one of the following actions. sample window isshown in The HTML-baseda separatein opens Help system browser window.A indexed entries. Use the tabs asneeded to searchHelp basedon text strings or Contents, Index, and Search. Help content is displayed bydefault. ELP Click on the Help iconin theap Select Help fromthe Help menupull-down, asshown in PERFORMING ADMINISTRATIVETASKS Figure 148 plication toolbar, as shownin . The left pane contains tabs for Accessing OnlineHelp Accessing Figure 146 Figure

197 ...... Chapter 9 PERFORMING ADMINISTRATIVE TASKS Accessing Online Help

Figure 148. Sample Help Window

Help tabs

Index

Search on strings

198 Virtualization Manager™ Administrator Guide A CCESSING T ECHNICAL Step 2. Step 1. To access technical support: Figure 150. Virtual Iron® Technical Support Home Page Technical 149. Accessing Figure Support sample of theconnection screen isshownin This connects you to theVirtual Iron® Technical Support database. A Select S UPPORT Technical Support PERFORMING ADMINISTRATIVETASKS fromtheHelppulldown menu. Accessing TechnicalAccessing Support Figure 150 .

199

. . . . . Chapter 9 PERFORMING ADMINISTRATIVE TASKS Accessing Technical Support

Use the tabs on the Support home page to access and search the Vir- tual Iron knowledge base, submit a question, or connect to your own area of the support site. To login, enter your User ID and Password in the fields provided, and click Login.

200 Virtualization Manager™ Administrator Guide INDEX ......

A configuring archive manager 188 Active/Passive Server Configuration 190 boot options 115 Application Toolbar 66 Ethernet networks 45 Hardware 67 LDAP 167 Jobs 69 logical disks 90 Policies and Reports 67 network adaptors 115 Resource Center 66 networks 43 Users 71 non-English keyboards 174 architecture, overview 4 policies 150 archive manager, configuring 188 processors, number of 117 assigning disks to virtual servers 113 server, active/passive 190 assigning nodes, virtual data centers 106 storage, Enterprise Edition 94 storage, Single Server Edition 97 B unassigned virtual servers 110 user accounts 164 backing up user policies 156 configuration database 185 virtual servers 110 management server database 60 VLANs 52 backup and restore operations 185 connecting to management server 38 boot methods 9 creating boot options 115 gold master 146 user accounts 164 C virtual data centers 104 changing management server IP address 187 VLAN groups 52 cloning logical disks 99 D virtual servers 119 Data protection, and Virtualization Manager 33 closing job tabs 84 dedicated management network 17 configuration database default management network, Enterprise backing up 185 Edition 43 restoring 185

1 Index

default public network, Single Server Edition 44 I defining networks 40 deleting user accounts 165 importing a virtual disk DHCP Enterprise Edition 96 IP address configuration 50 Single Server Edition 98 iSCSI port 50 importing VHD files 101 disk groups 90 installing disk groups,creating 91 Virtual Iron 12 disks, assigning to virtual servers 9 VSTools on guest OS 124 VSTools on Linux guests 124 E installing a guest OS to a logical disk 122 IP address configuraton 50 editing user accounts 166 IP address, changing management server’s 187 Edition 97 Enterprise Edition J default management network 43 exporting a logical disk 94 Job Operations tab 78 importing a logical disk 94 Job Report 154 importing a virtual disk 96 Job report 154 Ethernet networks, configuring 45 jobs Event Report 153 aborting 83 exporting a logical disk, Enterprise Edition 94 closing job tabs 84 exporting a virtual disk, Single Server Edition 97 determining cause of failure 84 exporting VHD files 101 events 80 failure of 80 F multi-user environment 78 operations 78 File menu 74 resource locks 78 states of 80 G Jobs, Application Toolbar 69 General Public License files viii L generating reports 151 gold master launching a virtual server console 134 creating for logical disk 146 LDAP provisioning virtual servers with 146 authentication 167 GPL source files viii changing configuration of 173 guest operating systems, supported 16 component Information 167 guest OS configuring 167 installing to a logical disk 122 support and administration 167 installing VSTools on 124 license accessing information about 75 H obtaining viii Linux, management server 183 Hardware, Application Toolbar 67 LiveCapacity 135 Help, accessing 197 LiveMaintenance 138 hiding job tabs 84 LiveMigrate requirements 143 high availability, Virtualization Manager 189 LiveRecovery 136 logical disk cloning 99

2 Virtualization Manager™ Administrator Guide policies performance monitoring P opening a virtual server console Online Help O non-English keyboards, configuring node statistics node states, colorindicators Node Report network connections, VNICs network adapters, configuring Navigation Tree N multi-user environment, managing in multiple-users, and jobs moving virtual servers moving nodestovirtual data center monitoring performance memory allocation memory management server management node, minimumrequirements Management managed nodes, overview managed nodes, minimumrequirements M configuing connecting to system Windows® starting Run command restarting reloading Linux® IP address, changing database,up backing overview importing, Enterprise Edition creating configuration 8 183 160 183 93 197 90 155 61 61 15 150 178 183 72 90 38 117 62 78 177 79 177 187 60 6 108 9 115 134 94 140 174 78 15 15 Resource Center reports reloading management server R public network product requirements processors, configuring numberof processors processing priority priority, settingofvirtual servers priority settings policy-based management Policies andReports, Application Toolbar Policies andReports tutorial, accessing technical support T policies system stopping a virtualserver statistics states, jobs starting the management server starting avirtual server console starting avirtual server Single Server Edition server configuration, active/passive S Run command restoring the configuration database restarting management server services resource locking Application Toolbar generating nodes configuring storage types user virtual server virtual data center Resource Center importing avirtualdisk exporting a virtualdisk default publicnetwork statistics 156 151 178 8 80 178 151 17 62 118 160 78 180 199 64 8 150 178 5 178 132 97 66 132 44 98 97 150 61 134 118 183 117 190 185 61 67

3 . . . . . Index

U moving to a new node 143 moving to a node 110 unassigned virtual servers 105 moving to Unassigned 111 and virtual data centers 109 priority options 118 configuring 110 processors 117 deploying 110 starting 132 overview 109 statistics 180 UPS protection 33 stopping 132 user accounts virtual server characteristics 8 configuring 164 boot methods 9 deleting 165 disks 9 editing 166 memory 8 User Policies 156 network connections 9 user policies 156 processing priority 8 Users, Application Toolbar 71 processors 8 Virtual Server Report 155 V virtual servers creating storage for 113 VHD files, importing and exporting 101 Virtualization 16, 187 View menu 74 Virtualization Manager virtual data center data protection 33 and unassigned virtual servers 105, 109 high availability 189 assigning nodes to 106 overview 2 creating 104 uninstalling from Linux 195 moving nodes to 140 uninstalling from Windows© 195 statistics 178 UPS protection 33 virtual disk Virtualization Manager, client requirements 16 importing, Enterprise Edition 96 VLAN importing, Single Server Edition 97, 98 configuraton 52 virtual infrastructure, overview 3 groups, creating 52 virtual server VS Tools on Linux guests, installing 124 assigning disks to 113 VS Tools silent install 130 cloning 119 console, opening 134 deploying 110 W memory allocation 117 Windows, management server 183 moving 78

4 Virtualization Manager™ Administrator Guide