ESX Server 3i Embedded Setup Guide

ESX Server 3i Embedded Setup Guide
ESX Server 3i version 3.5 Embedded and VirtualCenter 2.5
ESX Server 3i Embedded Setup Guide Revision: 20090612 Item: VI-ENG-Q407-446
You can find the most up-to-date technical documentation on our Web site at http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: docfeedback@vmware.com
20072009 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware, the VMware boxes logo and design, Virtual SMP and VMotion are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. VMware VirtualCenter 2.5 is distributed with certain third party technology licensed from Tom Sawyer Software. Tom Sawyer Visualization (c) 2004 Tom Sawyer Software, Oakland, California. All Rights Reserved.
VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com

2 VMware, Inc.
Contents
AboutThisBook
1 IntroductiontoVMwareInfrastructure 13
VMwareInfrastructureataGlance AboutESX Server 3i 16 14
2 SettingUpESX Server 3i 19
NetworkAccesstoYourESXServer3iHost 20 SettinguptheDirectConsoleUserInterface 21 ConfiguringtheKeyboardLayout 21 ConfiguringaSecurityBannerfortheDirectConsole ConfiguringESX Server 3iBootSettings 22 SelectingtheBootDevice 22 ConfiguringtheBootSettingforESX Server 3i 23 ConfiguringtheBootSettingforAnotherMode 23 ConfiguringtheBootSettingforVirtualMedia 24 ConfiguringNetworkSettings 25 ChoosingNICSfortheManagementNetwork 25 SettingtheVLANID 25 ConfiguringIPSettings 26 ConfiguringDNS 27 ConfiguringDNSSuffixes 28 TestingNetworkConnectivity 28 ConfiguringStorageBehavior 29 ConfiguringtheScratchPartition 29 ConfiguringESX Server 3iSecurity 31 RecordingtheESX Server 3iSerialNumber 31 ConfiguringtheAdministrativePassword 32 ConfiguringLockdownMode 32 ResettingtheConfigurationDefaults 33 ManagingESX Server 3iRemotely 34 RestartingManagementAgents 35 ViewingSystemLogs 35
VMware, Inc.
22
3 BackingUpandRestoringESX Server 3i 37
AboutBackingUpandRestoringanESX Server 3iConfiguration 38 ConsiderationsWhenUsingtheRemoteCLIVirtualAppliance 38 BackingUpESX Server 3iConfigurationData 39 RestoringESX Server 3iConfigurationData 40 RecoveringtheESX Server 3i EmbeddedSoftware 41 RemovingESX Server 3ifromtheHost 42
4 AddingESX Server 3itoVMwareInfrastructure 43

VirtualCenter 43 VirtualMachines 44 VirtualMachineTools 44 ESXServerUpgrades 44
5 VMwareInfrastructureSystemRequirements 45
VirtualCenterRequirements 45 VirtualCenterHardwareRequirements 46 VirtualCenterSoftwareRequirements 46 VirtualCenterDatabaseRequirements 47 EndofSupportLifeforMicrosoftAccessandMSDEDatabases VI ClientHardwareRequirements 47 VI ClientSoftwareRequirements 48 LicenseServerRequirements 48 SupportedGuestOperatingSystems 49 VirtualMachineRequirements 49 VirtualProcessor 49 VirtualChipSet 49 VirtualBIOS 50
47
6 VirtualCenterandESX Server 3iLicensingOverview 51

LicensingTerminology 52 ESX Server 3iEditions 52 VirtualCenter ServerEditions 54 VirtualCenterandESX Server 3iLicensingModel 54 SingleHostandCentralizedLicenseTypes 54 CentralizedLicensing 56 SingleHostLicensing 56
VMware, Inc.
Contents
LicenseKeyFunctionality 57 PerProcessorLicensing 58 PerInstanceLicensing 60 LicenseExpirationConsiderations 60 LicenseServerAvailability 60 UsinganExistingFLEXnetLicenseServer 64 ContactingSupport 65
7 RunningVMwareVirtualCenterandVMware ESX Server

in EvaluationMode 67
UsingEvaluationModeforESX Server 67 UsingEvaluationModeforVirtualCenter 68 LicensingVirtualCenterandESX ServerAftertheEvaluationPeriodExpires 68 ConsiderationswhenSwitchingESX ServerandVirtualCentertoLicensed Modes 69
8 LicensingVirtualCenterandESX Server 3i 71
LicensingProcess 72 ObtainingLicenseFiles 75 SettingUpCentralizedLicensing 75 InstallingLicenseFiles 75 LocationoftheLicenseServer 76 ConfiguringCentralizedLicensing 76 DefaultLicenseServerPorts 79 ChangingfromSingleHosttoCentralizedLicensing 79 SettingUpSingleHostLicensing 80 ConfiguringanESX Server 3iMachinetoUseaHostBasedSerialNumber 80 ConfiguringanESX ServerMachineforHostBasedLicensing 80 SingleHostandCentralizedLicensingintheSameEnvironment 81 ConfiguringLicensingforaMixedESX Server2.xandESX Server3.x Environment 82 ChangingfromCentralizedtoSingleHostLicensing 82 LicenseFileContents 83 LicenseFileLocations 85 AddingNewLicenseFilestoLicenseServers 85 AddingNewLicenseFilestoSingleHosts 86 InstallingaLicenseServer 87 TroubleshootingLicensing 88 ReceivingLicenseActivationCodes 88 CheckingtheLicenseServer 88
VMware, Inc. 5
CheckingtheLicenseFile 90 CheckingLicenseConfiguration 91
9 InstallingVMwareInfrastructureManagement 93
PreparingtheVirtualCenter ServerDatabase 93 ConfiguringYourVirtualCenterDatabase 94 ConfiguringanOracleConnectiontoWorkLocally 94 ConfiguringanOracleConnectiontoWorkRemotely 95 ConfiguringaSQLServerODBCConnection 96 ConfiguringMicrosoftSQLServer2005Express 98 MaintainingYourVirtualCenterDatabase 99 InstallingVMwareInfrastructureManagementSoftware 99 VirtualCenterInstallationPrerequisites 99 ComponentsInstalled 100 InstallationProcedure 101 ConfiguringCommunicationBetweenVirtualCenterComponents 103 ConnectingtoYourVirtualCenter ServerThroughaFirewall 104 ConnectingtoYourManagedHostsThroughaFirewall 104 ConnectingHostswiththeLicenseServerThroughaFirewall 105 UninstallingVMwareInfrastructureComponents 105 InstallingVirtualCenteronaVirtualMachine 106
10 MaintainingESX Server 3iandtheVI Client 107

PerformingMaintenancewithInfrastructureUpdate 107 SystemRequirementsforInfrastructure Update 108 SchedulingAutomaticUpdateNotifications 108 SelectingHoststoBeManaged 109 InstallingAvailableUpdates 109 DisablingAutomaticUpdateNotifications 110 ManuallyCheckingforAvailableUpdates 110 UsingRemovableMediatoInstallUpdates 110 PerformingMaintenanceWiththevihostupdateUtility 111 HowthevihostupdateMaintenanceUtilityInstallsSoftwareUpdates 112 OptionsforthevihostupdateUtility 113 Examples:thevihostupdateUtility 113 RollingBackanUpdate 114
VMware, Inc.
Contents
11 MonitoringtheConditionofESX Server 3i 115

Appendix:ESXServer3iHardwareConsiderations
MinimumHardwareConfigurations 117 EnhancedPerformanceRecommendations 119 HardwareandSoftwareCompatibility 120
117
Index 121
VMware, Inc.
VMware, Inc.
About This Book
Thismanual,theESXServer3iEmbeddedSetupGuide,describeshowtoinstallnew configurationsofVMware VirtualCenterandESX Server 3i. TheESXServer3iEmbeddedSetupGuidediscussesESX Server 3ionly.Toreadabout ESX Server 3.5,seehttp://www.vmware.com/support/pubs/vi_pubs.html. Foreaseofdiscussion,thisbookusesthefollowingproductnamingconventions: FortopicsspecifictoESXServer3.5,thisbookusesthetermESXServer3. FortopicsspecifictoESXServer3iversion3.5,thisbookusestheterm ESX Server 3i. Fortopicscommontobothproducts,thisbookusesthetermESXServer. Whentheidentificationofaspecificreleaseisimportanttoadiscussion,thisbook referstotheproductbyitsfull,versionedname. WhenadiscussionappliestoallversionsofESXServerfor VMware Infrastructure 3,thisbookusesthetermESXServer3.x.
Intended Audience
ThismanualisintendedforanyonewhoneedstosetuporuseESX Server 3i. The informationinthismanualiswrittenforexperiencedWindowsorLinuxsystem administratorswhoarefamiliarwithvirtualmachinetechnologyanddatacenter operations.
VMware, Inc.
Document Feedback
VMwarewelcomesyoursuggestionsforimprovingourdocumentation.Ifyouhave comments,sendyourfeedbackto: docfeedback@vmware.com
VMware Infrastructure Documentation

TheVMwareInfrastructuredocumentationconsistsofthecombinedVMware VirtualCenterandESXServerdocumentationset.
Abbreviations Used in Figures

ThefiguresinthismanualusetheabbreviationslistedinTable 1. Table 1. Abbreviations
Abbreviation database datastore dsk# hostn SAN tmplt user# VC VM# Description VirtualCenterdatabase Storageforthemanagedhost Storagediskforthemanagedhost VirtualCentermanagedhosts Storageareanetworktypedatastoresharedbetweenmanagedhosts Template Userwithaccesspermissions VirtualCenter Virtualmachinesonamanagedhost
Technical Support and Education Resources

Thefollowingsectionsdescribethetechnicalsupportresourcesavailabletoyou.You canaccessthemostcurrentversionsofthismanualandotherbooksbygoingto: http://www.vmware.com/support/pubs
10
VMware, Inc.
About This Book
Online and Telephone Support

Useonlinesupporttosubmittechnicalsupportrequests,viewyourproductand contractinformation,andregisteryourproducts.Goto http://www.vmware.com/support. Customerswithappropriatesupportcontractsshouldusetelephonesupportforthe fastestresponseonpriority1issues.Goto http://www.vmware.com/support/phone_support.html.
Support Offerings
FindouthowVMwaresupportofferingscanhelpmeetyourbusinessneeds.Goto http://www.vmware.com/support/services.
VMware Education Services

VMwarecoursesofferextensivehandsonlabs,casestudyexamples,andcourse materialsdesignedtobeusedasonthejobreferencetools.Formoreinformationabout VMwareEducationServices,gotohttp://mylearn1.vmware.com/mgrreg/index.cfm.
VMware, Inc.
11
12
VMware, Inc.
Introduction to VMware Infrastructure
ThisbookdescribesVMwareESX Server 3iandVMwareVirtualCenter.Thischapter describesthecomponentsindividually,tohelpyoudecidewhichcomponentstoinstall. ThefollowingsectionsintroduceVMwareESX Server 3iandVirtualCenter. VMwareInfrastructureataGlanceonpage 14 AboutESX Server 3ionpage 16
VMware, Inc.
13
VMware Infrastructure at a Glance

Figure 11illustratesthesixbasiccomponentsofVMwareInfrastructure.Thefigure showsthelicenseserveronaseparatemachine.Youcaninstallthelicenseserveronthe samemachinethathostsVirtualCenter. Figure 1-1. VMware Infrastructure Components
VMware Infrastructure Client
license server
ESX Server 3i hosts
VirtualCenter
database
OneVirtualCenter ServermanagesmultipleESX Server 3ihosts. Eachshadedblockrepresentsaseparateinstallerorprocedure.TheVMware InfrastructureClient(VI Client)appearstwice,becauseyoucanrunitonmultiple workstations.
14
VMware, Inc.
Chapter 1 Introduction to VMware Infrastructure
ThemajorcomponentsofVMwareInfrastructureare: VMwareESX Server 3iProvidesavirtualizationlayerthatabstractsthe processor,memory,storage,andnetworkingresourcesofthephysicalhostinto multiplevirtualmachines.YoudonotneedtoinstallESX Server 3ibecauseitis embeddedasfirmwareonaserverplatformthatyoupurchasefromahardware vendor. VMwareVirtualCenter Server(VirtualCenter)InstallsonaWindowsmachine, eitherphysicalorvirtual,tocentrallymanageyourVMwareESX Server 3ihosts. VirtualCenterallowstheuseofadvancedVMwareInfrastructurefeaturessuchas VMwareDRS,VMwareHA,andVMwareVMotion. AVMwareSDKWebserviceisinstalledwithVirtualCenter.SeeConfiguring CommunicationBetweenVirtualCenterComponentsonpage 103. VirtualCenterPluginsOptionalapplicationsthatprovideadditional capabilitiesandfeaturestoVirtualCenter.Generally,pluginsarereleased separately,installontopofVirtualCenter,andcanbeupgradedindependently. Youcaninstallservercomponentsofpluginsonthesamecomputerwherethe VirtualCenter Serverresides,oronaseparateone.Aftertheservercomponentofa pluginisinstalled,youcanactivatethepluginsclientcomponent,which enhancestheVI ClientwithappropriateUIoptions. Documentationprovidedwitheachpluginoffersinformationabouthowserver componentsofpluginsareinstalled. Forinformationabouthowtoinstalltheclientcomponent,verifywhichplugins arealreadyinstalled,andhowtodisableoruninstallpluginsthatyouarenot using,seeBasicSystemAdministration. Thefollowingpluginsareavailable: VMwareConverterConvertsphysicalorvirtualmachinesinto ESX Server 3ivirtualmachines.Afterconvertingthevirtualmachines,you canaddthemtoyourVirtualCenterinventory. VMwareUpdateManagerProvidessecuritymonitoringandpatching supportforESX Server 3ihostsandvirtualmachines. Inadditiontoanindependentservercomponentinstallation,thisrelease supportsthecombinedinstallationfortheVirtualCenter Serverand Update Manager.FormoreinformationoninstallingtheVMwareUpdate ManagerservercomponentalongwithVirtualCenter,seeConfiguring CommunicationBetweenVirtualCenterComponentsonpage 103.If upgrading,seetheUpgradeGuide.ForgeneralinformationonUpdate Manager,seetheVMwareUpdateManagerAdministrationGuide.
VMware, Inc. 15
VI ClientInstallsonaWindowsmachineandistheprimarymethodof interactionwithVMwareInfrastructure.TheVI Clientactsas: Aconsoletooperatevirtualmachines. AnadministrationinterfaceintotheVirtualCenter ServerandESX Server 3i hosts. LicenseserverInstallsonaWindowssystemtoauthorizeVirtualCenterhosts andESX Server 3ihostsappropriatelyforyourlicensingagreement. AdministratorsmakechangestosoftwarelicensesusingtheVI Client.SeeSetting UpCentralizedLicensingonpage 75. DatabaseVirtualCenterusesadatabasetoorganizealltheconfigurationdatafor theVMwareInfrastructureenvironment.Forsmalldeployments,thebundled MicrosoftSQLServer2005Expressdatabaseletsyousetupalimitednumbersof hostsandvirtualmachines(5hostsand50virtualmachines).VirtualCenter supportsseveralotherdatabaseproductsforlargerdeployments.SeePreparing theVirtualCenter ServerDatabaseonpage 93.
About ESX Server 3i

AnESXServer3ihostisaphysicalserverthatcontainsanESXServerimage preinstalledasfirmwareinthefactory. WhenyoufirstbootuptheESX Server 3ihost,youusethedirectconsoleuserinterface forinitialconfigurationandtroubleshootingoftheESXServersoftware.Thedirect consoleappearsifyouattachamonitortothehost.IfyouinstalltheVMware InfrastructureManagementsoftware,youcanalsousetheVMwareInfrastructure clientapplicationstomanagethehost. WhenyoupowerontheESXServer3ihostforthefirsttime(orwhenyoupoweronthe hostafteryouresetthehosttotheconfigurationdefaults),thehostentersabootup phaseduringwhichsystemnetworkandstoragedevicesareconfiguredwithdefaults. ThedefaultbehaviorfornetworkingisfortheDynamicHostConfigurationProtocol (DHCP)toconfigureIP.Thedefaultbehaviorforstorageisforallvisibleblankinternal diskstobeformattedwiththevirtualmachinefilesystem(VMFS)sothatvirtual machinescanbestoredonthedisks. Afterthehostcompletesthebootupphase,thedirectconsoleappearsontheattached monitor.Usingakeyboardandmonitorattachedtothehost,youcanexaminethe defaultnetworkconfigurationappliedduringthebootupphaseandchangeany settingsthatarenotcompatiblewithyournetworkenvironment.
16
VMware, Inc.
Chapter 1 Introduction to VMware Infrastructure
Keyoperationsavailabletoyouinthedirectconsoleinclude: ConfiguringESX Server 3ihostdefaults Settingupadministrativeaccess TroubleshootingESX Server 3i ForinformationaboutsettingupyourESX Server 3ihostandusingthedirectconsole, seeSettingUpESX Server 3ionpage 19.
VMware, Inc.
17
18
VMware, Inc.
Setting Up ESX Server 3i
Thischapterprovidesinformationaboutusingthedirectconsoleuserinterfaceand configuringdefaultsforESX Server 3i.Itincludesthefollowingsections: NetworkAccesstoYourESXServer3iHostonpage 20 SettinguptheDirectConsoleUserInterfaceonpage 21 ConfiguringESX Server 3iBootSettingsonpage 22 ConfiguringNetworkSettingsonpage 25 ConfiguringStorageBehavioronpage 29 ConfiguringESX Server 3iSecurityonpage 31 ResettingtheConfigurationDefaultsonpage 33 ManagingESX Server 3iRemotelyonpage 34 RestartingManagementAgentsonpage 35 ViewingSystemLogsonpage 35
VMware, Inc.
19
Network Access to Your ESX Server 3i Host

ThedefaultbehaviorfornetworkingisforDHCPtoconfigureIP.Youcanacceptthe defaultbehavior,preventthedefaultbehaviorfromtakingeffectduringthebootup phase,oroverridethedefaultbehaviorafterittakeseffect.Youcanchangeanysettings thatarenotcompatiblewithyournetworkenvironment.Table 21summarizesthe scenariosandapproachesfornetworkconfigurationthatESX Server 3isupports. Table 2-1. Network Configuration Scenarios and Approaches
Scenario Youwanttoacceptthe DHCPconfiguredIP settings. Oneofthefollowingistrue: Youdonothavea DHCPserver. TheESX Server 3ihost isnotconnectedtoa DHCPserver. YourconnectedDHCP serverisnot functioningproperly. TheESX Server 3ihostis connectedtoafunctioning DHCPserver,butyoudo notwanttousethe DHCPconfiguredIP address. Approach NotetheIPaddressthatDHCPassignsandusetheVI Clientoranother desktopclientinterfacetoconnecttotheESX Server 3ihost. Duringtheinitialbootupphase,thesoftwareassignsadefaultIPaddress (169.254.0.1/16). IfyouareconnectingtotheESX Server 3ihostremotelythroughthe VI Clientoranotherdesktopclientinterface,youcanmaketheinitial connectionbyusingthedefaultIPaddress.Thenyoucanconfigureastatic IPaddress. IfyouarelocaltotheESX Server 3ihost,youcanoverridethedefaultIP addressbyconfiguringastaticIPaddressusingthedirectconsole. Duringtheinitialbootupphase,thesoftwareassignsaDHCPconfigured IPaddress. IfyouareconnectingtotheESX Server 3ihostremotelythroughthe VI Clientoranotherdesktopclientinterface,Aftertheinitialconnectionis made,youcanmaketheinitialconnectionbyusingthedefaultIPaddress. ThenyoucanconfigureastaticIPaddress. IfyouarelocaltotheESX Server 3ihost,youcanoverridethe DHCPconfiguredIPaddressbyconfiguringastaticIPaddressusingthe directconsole. Yoursecuritydeployment policiesdonotpermit unconfiguredhoststobe poweredonthenetwork. Setupprocedure: 1 2 3 4 5 6 7 Makesurethatnonetworkcablesareconnectedtothehost. Poweronthehost. Usethedirectconsoletoconfiguretheadministrativepassword. UsethedirectconsoletoconfigureastaticIPaddress. Connectanetworkcabletothehost. UsetheVI ClienttoconnecttoVirtualCenter. AddthehosttotheVirtualCenterinventory.
20
VMware, Inc.
Chapter 2 Setting Up ESX Server 3i
Setting up the Direct Console User Interface

ThedirectconsoleissimilartotheBIOSofacomputerwithakeyboardonlyuser interface.Table 22liststhekeysyoucanusetonavigateandperformactionsinthe directconsole. Table 2-2. Navigating in the direct console
Actions Viewandchangeconfiguration Shutdownorrestartthehost Movethehighlightbetweenselection fields Selectamenuitem Toggleavalue Confirmsensitivecommands,suchas resettingconfigurationdefaults Saveandexit Exitwithoutsaving Exitsystemlogs Keys F2 F12 Arrowkeys Enter Spacebar F11 Enter Esc q
Configuring the Keyboard Layout

Youcanconfigurethelayoutforthekeyboardthatyouusewiththedirectconsole. To configure the keyboard layout 1 2 3 4 Fromthedirectconsole,selectConfigureKeyboardandpressEnter. Selectthelayouttouse. Pressthespacebartotoggleselectionsonandoff. PressEnter.
VMware, Inc.
21
Configuring a Security Banner for the Direct Console

AsecuritybannerisamessagethatisdisplayedontheWelcomescreenofthedirect console. To add a security banner to the direct console 1 2 3 4 LogintothehostfromtheVIClient. FromtheConfigurationtab,selectAdvancedSettings. FromtheAdvancedSettingswindow,selectAnnotations. Enterasecuritymessage. ThemessageisdisplayedonthedirectconsoleWelcomescreen.
Configuring ESX Server 3i Boot Settings

WhenyoupowerontheESX Server 3ihostforthefirsttime(orwhenyoupoweronthe hostafteryouresetthehosttotheconfigurationdefaults),thehostentersabootup phaseduringwhichyoucanselectabootdevice.Youcanalwaysbootinto ESX Server 3imodeorintoanothermode.Duringthebootupphase,systemnetwork andstoragedevicesareconfiguredwithdefaults. Afterthehostcompletesthebootupphase,thedirectconsoleuserinterfaceappearson theattachedmonitor.Usingakeyboardandmonitorattachedtothehost,youcanuse thedirectconsoletoconfiguretheESX Serverhost,toexaminethedefaultnetwork configurationappliedduringthebootupphase,andtotroubleshoottheESX Server software.
Selecting the Boot Device

Thebasicinput/outputsystem(BIOS)bootconfigurationdeterminesinwhichmode yourserverboots.Generally,theUSBflashdeviceislistedfirstintheBIOSbootsettings onthemachinethathostsESX Server 3i.Theabilitytochangethebootsettingishelpful ifyouhaveothersupportedoperatingsystemsonthehost.Youcanchangetheboot settingbyconfiguringthebootorderintheBIOSduringstartuporbyselectingaboot devicefromtheBootOptionsmenu. WhenyouchangethebootorderintheBIOS,thenewsettingaffectsthecurrentboot andallsubsequentreboots.Whenyouselectabootdevicefromthebootoptionmenu, theselectionaffectsthecurrentbootonly.TheBootOptionsmenuisusefulforonetime bootswhenyoudonotwanttochangethedefaultBIOSsettings.
22
VMware, Inc.
SomeserversdonothaveaBootOptionsmenu,inwhichcaseyoumustchangethe bootorderintheBIOS,evenforonetimeboots,andthenchangeitbackagainduring thesubsequentreboot. NOTETheBootOptionsmenudiscussedinthissectionisdifferentfromthesystem bootoptionsthatyoucanconfigurebyloggingintotheVI Client,selectingahost,and clickingConfiguration>Processors>BootOptions. ThissectiondiscussesthesystemBIOSBootOptionsmenu.Thebootoptionsinthe VI Clientonlyallowyoutoconfigurethebootsequenceforfloppy,CDROM,andthe harddisk(C:drive).Forsomeservers,thesystemBIOShastwooptions.Oneisforthe bootsequence(floppy,CDROM,harddisk)andanotherfortheharddiskbootorder (USBkey,localharddisk).WhenyouareusingtheVIClient,thebootoptions correspondtotheBIOSbootsequence(floppy.CDROM,harddisk).
Configuring the Boot Setting for ESX Server 3i

SomeESX Server 3ihostsmightnotbepreconfiguredintheBIOStobootinto ESX Server 3imode. To configure the boot setting for ESX Server 3i mode 1 WhiletheESX Server 3ihostispoweringon,pressthekeyrequiredtoenteryour hostsBIOSSetuppage. Dependingonyourserverhardware,thekeymightbeF1,F2,F10,F11,F12,orDel. TheoptiontoopentheBIOSSetuppagemightbedifferentforyourserver. 2 SelecttheUSBflashdeviceandmoveittothefirstpositioninthelist. ThehostpowersoninESX Server 3imode.Ifthehostdoesnotpoweronin ESX Server 3imode,youmightneedtoreimagetheUSBflashasdescribedin RecoveringtheESX Server 3i EmbeddedSoftwareonpage 41.
Configuring the Boot Setting for Another Mode

Ifyouuseyourserverformultiplepurposes,youcanchangethebootconfigurationas appropriate. Followtheprocedureforonetimebootsifyourserverhasabootoptionmenuandyou donotwanttochangethedefaultbootorder.Thefollowingprocedureisusefulfor bootingfromvirtualmedia,forexample. Ifyourserverdoesnothaveabootoptionmenuorifyouwanttochangethedefault bootorder,followtheproceduretochangethebootorder.
VMware, Inc.
23
To select a one-time boot option 1 2 Reboottheserver. Whiletheserverispoweringon,openthebootoptionmenu. Forexample,onsomeserversyoucanselectF11toopenthebootmenuoption. 3 Fromthisbootoptionmenu,followtheinstructionstoselectadevicefromwhich toboot. Theserverbootsintheconfiguredmodeonetimeandgoesbacktothedefaultboot orderforsubsequentreboots. To change the boot order 1 2 Reboottheserver. Whiletheserverispoweringon,pressthekeyrequiredtoenteryourhostsBIOS Setuppage. Dependingonyourserverhardware,thekeymightbeF1,F2,F10,F11,F12,orDel. TheoptiontoopentheBIOSSetuppagemightbedifferentforyourserver. 3 Changethebootorderbyselectingadeviceandmovingittothefirstpositionin thelist. Thehostpowersonintheconfiguredmodeforthisbootandforallsubsequent reboots.
Configuring the Boot Setting for Virtual Media

Virtualmediaisaccessstoragemedia(suchasflashmemory,externaldrive,USB, floppy,orCDROM)thatcanbemadeavailabletoanymachineonanetwork. To boot from virtual media 1 Connectmediatothevirtualdevice. Forexample,ifyouareusingaDellserver,logintotheDellRemoteAccess Controller(DRAC)(orasimilarremotemanagementinterface)andselecta physicalfloppyorCDROMdrive,orprovideapathtoafloppyimageor CDROMimage.ThenclickConnecttoconnecttheselectedmediatothevirtual device. 2 Reboottheserver. Whiletheserverispoweringon,configurethebootsettingtobootfromthevirtual mediadevice.SeeConfiguringtheBootSettingforAnotherModeonpage 23.
24
VMware, Inc.
Configuring Network Settings

YoumustsetupyourIPaddressbeforeyourESX Server 3ihostisoperational. To configurebasicnetworksettings,usethedirectconsoleortheVIClient.
Choosing NICS for the Management Network

TrafficbetweenanESX Server 3ihostandanyexternalmanagementsoftwaremovesin andoutthroughanEthernetnetworkinterfacecard(NIC)onthehost.Examplesof externalmanagementsoftwareincludetheVI Client,VirtualCenter,andSNMPclient software.NICsonthehostarenamedvmnic<N>,whereNisthenumberoftheNIC(for example,vmnic0,vmnic1,andsoforth.) Duringthebootupphase,theESX Server 3ihostchoosesvmnic0formanagement traffic.YoucanoverridethedefaultchoicebymanuallychoosingtheNICthatcarries managementtrafficforthehost.Insomecases,forbestavailability,youmightwantto useaGigabitEthernetNICforyourmanagementtraffic.Anotherwaytohelpensure availabilityistoselectmultipleNICsformanagementtraffic.ChoosingmultipleNICs enablesloadbalancingandfailovercapabilities. To choose NICs 1 2 3 4 5 Fromthedirectconsole,selectConfigureManagementNetworkandpressEnter. SelectNetworkAdaptersandpressEnter. SelectaNIC. PressthespacebartotoggleNICselectionsonandoff. PressEnter.
Afterthenetworkisfunctional,youcanusetheVI ClienttoconnecttotheESX Server 3i host.
Setting the VLAN ID

Optionally,youcansetthevirtualLAN(VLAN)IDnumberoftheESX Server 3ihost. To set the VLAN ID 1 2 3 Fromthedirectconsole,selectConfigureManagementNetworkandpressEnter. SelectVLAN(optional)andpressEnter. EnteraVLANIDnumber. VLANIDnumbersrangefrom1through4094.
VMware, Inc.
25
Configuring IP Settings
YoucanchooseeithermanualorautomaticIPconfigurationoftheESX Server 3ihost. Bydefault,IPconfigurationisautomatic.TheautomaticsettingenablesDHCPtoset theIPaddress,subnetmask,anddefaultgateway.ThedirectconsoledisplaystheIP addressthatDHCPassignstothehost.Forfuturereference,VMwarerecommendsthat youwritedownthisIPaddress. ForDHCPtowork,yournetworkenvironmentmusthaveaDHCPserver.IfDHCPis notavailableornotdesirable,thehostmightbeassignedthebuiltindefaultIPaddress, whichis169.254.0.1/16.Youcanusethisdefaultaddresstoconnectinitiallyandthen configureastaticnetworkaddress.Thedefaultsubnetmaskis255.255.0.0.Thedefault gatewayisblank.IftwohostspowerupwithnoDHCPservice,bothhostsreceivethe default169.254.0.1IPaddress.NooutboundtrafficisallowedthroughthisIPaddress. ThisiswhythedefaultIPaddressisnotalongtermalternativetoDHCP.Itprovidesa temporarymethodtoconnecttothehostsothatyoucanconfigurestaticIPsettings. Ifyouarenotlocaltothehost,youcanusetheVI ClienttoconfigurestaticIPsettings, ifyouareonthesamephysicalsubnetandyouconfiguretheVIClientIPtobeonthe 169.254.0.xnetwork. Ifyouarelocaltothehost,youcanusethedirectconsoletoconfigurestaticIPsettings, includingtheIPaddress,subnetmask,anddefaultgateway. To configure static IP settings from the direct console 1 2 3 4 5 6 7 Fromthedirectconsole,selectConfigureManagementNetworkandpressEnter. SelectIPConfigurationandpressEnter. NavigatetoSetstaticIPaddressandnetworkconfiguration. Pressthespacebartoselectthehighlighteditem. SelectanddeletethecurrentIP address,subnetmask,anddefaultgateway. EnterastaticIPaddress,subnetmask,anddefaultgateway. PressEnter.
To configure static IP settings from the VI Client 1 2 3 4 FromtheVI Client,selectthehostintheinventory. SelecttheConfigurationtabandclickNetworking. ClickPropertiesnexttoVirtualSwitch:vSwitch0. SelectManagementNetworkandclickEdit.
26
VMware, Inc.
5 6 7
OntheGeneraltab,clickUsethefollowingIPsettings. EnterastaticIPaddress,subnetmask,anddefaultgateway. ClickOK.
Configuring DNS
YoucanchooseeithermanualorautomaticDomainNameSystem(DNS)configuration oftheESX Server 3ihost.Bydefault,DNSconfigurationisautomatic.Theautomatic settingenablesaDHCPservertoacquireDNSinformation.ForautomaticDNSto work,yournetworkenvironmentmusthaveaDHCPserverandaDNSserver. InnetworkenvironmentswhereautomaticDNSisnotavailableornotdesirable,you canconfigurestaticDNSinformation,includingahostname,aprimarynameserver,a secondarynameserver,andDNSsuffixes. Ifyouarenotlocaltothehost,youcanusetheVI ClienttoconfigureDNSinformation. Ifyouarelocaltothehost,youcanusethedirectconsoletoconfigureDNSinformation. To configure DNS settings from the direct console 1 2 3 4 5 6 7 Fromthedirectconsole,selectConfigureManagementNetworkandpressEnter. SelectDNSConfigurationandpressEnter. NavigatetoUsethefollowingDNSserveraddressesandhostname. Pressthespacebartoselectthehighlighteditem. Selectanddeletethecurrentprimaryserver,alternateserver,andhostname. Enterastaticprimaryserver,alternateserver,andhostname. PressEnter.
To configure DNS settings from the VI Client 1 2 3 4 5 6 FromtheVI Client,selectthehostintheinventory. SelecttheConfigurationtabandclickNetworking. ClickPropertiesnexttoVirtualSwitch:vSwitch0. SelectManagementNetworkandclickEdit. OntheGeneraltab,clickUsethefollowingIPsettings. ClickEditnexttoVMkernelDefaultGateway.
VMware, Inc.
27
7 8
OntheDNSConfigurationtab,enterastaticprimaryserver,alternateserver,host name,andDNSsuffixes. ClickOK.
Configuring DNS Suffixes

Bydefault,DHCPacquirestheDNSsuffixes. To configure the DNS suffixes 1 2 3 4 5 Fromthedirectconsole,selectConfigureManagementNetwork. SelectCustomDNSSuffixesandpressEnter. PresstheBackspacekeytodeletethecurrentDNSsuffixes. EnternewDNSsuffixes. PressEnter.
Testing Network Connectivity

Youcanusethedirectconsoletoperformsomesimplenetworkconnectivitytests.By default,thedirectconsolepreformsthefollowingtests: Pingsthedefaultgateway PingstheprimaryDNSnameserver PingsthesecondaryDNSnameserver ResolvestheDNShostname To test the management network 1 2 Fromthedirectconsole,selectTestManagementNetworkandpressEnter. PressEntertostartthetest.
TheESX Server 3ihosttestsyournetworkconfiguration. To test connectivity to other devices or networks 1 2 3 4 Fromthedirectconsole,selectTestManagementNetworkandpressEnter. Selectanddeleteoneormoredefaultaddressesorthedefaulthostname. TypeotheraddressestopingoranotherDNShostnametoresolve. PressEntertostartthetest.
28
VMware, Inc.
Configuring Storage Behavior

WhenyoupoweronESX Server 3i,thehostentersaninitialbootupphaseduring whichsystemstoragedevicesareconfiguredwithdefaults.Thedefaultbehaviorfor storageisforthesoftwaretoformatallvisibleblankinternaldiskswithVMFS,soyou canstorevirtualmachinesonthedisks. OntheharddrivefromwhichtheESXServer3ihostisbooting,thediskformatting softwareretainsexistingdiagnosticpartitionsthatarecreatedbythehardwarevendor. Intheremainingspace,thesoftwarecreates: One4GBVFATscratchpartitionforsystemswap,ifthispartitionisnotpresenton anotherdisk.SeeConfiguringtheScratchPartitiononpage 29. One110MBdiagnosticpartitionforcoredumps,ifthispartitionisnotpresenton anotherdisk. OneVMFS3partitionontheremainingfreespace. TheVFATscratchanddiagnosticpartitionsarecreatedonlyonthediskfromwhichthe ESX Server3ihostisbooting.Onotherdisks,thesoftwarecreatesoneVMFS3partition perblankdisk,usingthewholedisk.Thesoftwareformatsblankdisksonly. Youmightwanttooverridethisdefaultbehaviorif,forexample,yourpolicyistouse sharedstoragedevicesinsteadoflocalstorage. Topreventautomaticdiskformattingfromoccurring,detachlocalstoragedevicesfrom thehostbeforeyoupoweronthehostforthefirsttime(orbeforeyoupoweronthehost afteryouresetthehosttotheconfigurationdefaults).Theautomaticdiskformatting occursthefirsttimeyoupoweronthehostandwhenyoupoweronthehostafteryou resetthehosttotheconfigurationdefaults.Forsubsequentreboots,youdonotneedto detachlocalstoragedevices.Ifautomaticdiskformattingalreadyoccurredandyou wanttooverridetheVMFSformatting,youcanremovethedatastore.Seethe Server ConfigurationGuide.
Configuring the Scratch Partition

ThefirsttimeyoupowerontheESXServer3ihost(andwhenyoupoweronthehost afteryouresetthehosttotheconfigurationdefaults),thesoftwarecreatesandenables one4GBVFATscratchpartitionforsystemswap,ifthispartitionisnotpresenton anotherdisk.Thehostusessystemswapforitsownoperation.Systemswapisdifferent fromvirtualmachineswap. Ifthehostdoesnothaveascratchpartition,thehostuses512MBmorememorythanit wouldotherwiseuse.Ifyoudonotwantthehosttousethisadditionalmemory,keep thescratchpartitionenabled.Ifthescratchpartitionisdisabled,youcanenableit.
VMware, Inc.
29
Beforeyoucanenablethescratchpartition,youmusthaveaccesstoamachinethatis runningtheRemoteCommandLineInterface(CLI).For informationaboutimporting orinstallingtheRemote CLI,seetheRemoteCommandLineInterfacesappendixof theESXServer3iConfigurationGuide. To enable the scratch partition 1 PowerontheRemoteCLIandlogin. Youdonotneedtotypethepasswordonthecommandline.Ifnopasswordis specified,thetoolpromptsyouforthepasswordwithoutechoingtheoutputtothe terminal.Thismeansthepasswordyoutypeisnotvisibleinthewindowasyou runthecommand. YoucancreateasecureconnectiontotheRemoteCLIbyusingtheRemoteCLIIP address.IfyouareusingtheVI Client,youcanrightclicktheRemoteCLIand selectOpenConsole. IftheRemoteCLIisinstalledonyourWindowsorLinuxsystem,youcanusethe installedapplication,inwhichcaseyoudonotneedtologin. 2 Togetthecurrentstate,runthefollowingreadonlycommands:
vicfg-advcfg.pl --server <ip-address> --username root --password <password> -s /ScratchConfig/CurrentScratchLocation vicfg-advcfg.pl --server <ip-address> --username root --password <password> -s /ScratchConfig/ConfiguredSwapState
Runthefollowingcommandstoenableordisablesystemswap: Toenableswap:
vicfg-advcfg --server <ip-address> --username root --password <password> -s true ScratchConfig.ConfiguredSwapState
Todisableswap:
vicfg-advcfg --server <ip-address> --username root --password <password> -s false ScratchConfig.ConfiguredSwapState
Ifyouenabledsystemswap,runthefollowingcommandtoenterthelocationofa datastoreonwhichtocreateandenablethesystemswappartition:
vicfg-advcfg --server <ip-address> --username root --password <password> -s "/vmfs/volumes/<NameOfDatastore>/<DirectorySpecificToHost>" ScratchConfig.ConfiguredScratchLocation
Theconfigureddirectorymustbeuniqueacrosshosts.
30
VMware, Inc.
Toretrievetheswapstate:
vicfg-advcfg -server <ip-address> --username root --password <password> -g ScratchConfig.ConfiguredSwapState
Toretrievescratchlocation:
vicfg-advcfg --server <ip-address> --username root --password <password> -g ScratchConfig.ConfiguredScratchLocation
Tomakethechangestakeeffect,rebootthehost.
Configuring ESX Server 3i Security

Theproceduresinthissectiondescribehowtosettheadministratorusernameand passwordtosecureyourESX Serverhostandtoconfigurehostlockdownmode,which preventsremotepersonnelfromloggingintotheESX Server 3ihostbyusingtheroot loginname.Inaddition,itdescribeshowtodeterminetheESX Server 3iserialnumber, whichisrequiredforrecoveryoperations,ifnecessary.
Recording the ESX Server 3i Serial Number

IftheESX Server 3ihostislicensedtousetheStandaloneedition,aserialnumberis assignedtothehost.VMwarerecommendsthatyouwritedowntheserialnumberand tapeittotheserver,ifpossible,orputtheserialnumberinasecure,easilyaccessible location.YoucanaccesstheserialnumberfromthedirectconsoleortheVI Client. Whenyouperformaconfigurationbackup,theserialnumberisbackedupwiththe configurationandisrestoredwhenyourestoretheconfiguration. To access the ESX Server 3i serial number from the direct console Fromthedirectconsole,selectViewSupportInformation. ThelicenseserialnumberappearsintheformXXXXXXXXXXXXXXXX. Thephysicalmachineserialnumberalsoappears.Donotconfusethelicenseserial numberwiththephysicalmachineserialnumber. To access the ESX Server 3i serial number from the VI Client 1 2 FromtheVI Client,selectthehostintheinventory. SelecttheConfigurationtabandclickLicensedFeatures. TheserialnumberislistedunderLicenseSource.Iftheserialnumberisnotlisted, anotherhostlicensesourceisconfigured.
VMware, Inc.
31
Configuring the Administrative Password

TheadministrativeusernamefortheESX Server 3ihostisroot. Bydefault,theadministrativepasswordisnull,meaningthereisnoadministrative password. To create an administrative password 1 2 Fromthedirectconsole,selectConfigureRootPassword. Ifpromptedforanoldpassword,pressEnter. Ifyouaresettingthepasswordforthefirsttime,youarenotpromptedforanold password. 3 4 Enteranewpassword. RetypethenewpasswordandpressEntertosavethepasswordconfiguration.
Configuring Lockdown Mode

LockdownmodepreventsremotepersonnelfromloggingintotheESX Server 3ihost byusingtherootloginname.Ifyouconfigurelockdownmodeandyoudonot configureotherlocalhostuseraccounts,directhostaccessisrestricted.Thismeans standalonehostaccessthroughtheVI Client,accessthroughtheVIAPI,andtheremote commandlineinterface(CLI)arenotallowedforuserroot. Whenlockdownmodeisenabled,userscanstillaccessthehostthroughthedirect consoleorthroughanauthorizedcentralizedmanagementapplication,suchas VirtualCenter.Bydefault,lockdownmodeisdisabled. Whenlockdownmodeisenabled,youcancreateauser(otherthanroot)with administratorprivilegestoconnecttoastandalonehost.Donotusethisapproachin environmentswithnumeroushostsbecausemaintainingseparateuserpassword databasesforeachhostmightbedifficulttomanage. EnablelockdownmodeonlyafteryouaddthehosttotheVirtualCenterinventory.The operationtoenablelockdownmodefailsifyoutryitbeforeyouaddthehostto VirtualCenter.InVirtualCenter,youcanchoosetoenablelockdownmodewhenyou addthehosttotheVirtualCenterinventory.Ifyoudoso,youdonotneedtoenable lockdownmodeinthedirectconsole.
32
VMware, Inc.
To configure lockdown mode 1 2 3 4 AddtheESXServer3ihosttotheVirtualCenterinventory. Fromthedirectconsole,selectConfigureLockdownModeandpressEnter. PressthespacebartoselectEnableLockdownModeandpressEnter. PressEnter.
Resetting the Configuration Defaults

Whenyouresettheconfigurationdefaults,thesoftwareoverridesallconfiguration changesthatyouhavemade,deletestheadministrativepassword,andrebootsthehost. Someconfigurationchangesthatyourhardwarevendormighthavemadeinthe factoryaredeletedaswellwhenyouresettheconfigurationdefaults.Thesechanges includeIPaddresssettingsandlicenseconfiguration. Beforeyouresettheconfigurationdefaults,firstbackuptheESX Serverconfiguration. Afteryouresettheconfigurationdefaults,youcanusethebackupfiletorestoreyour configuration. Resettingtheconfigurationdefaultsdoesnotremoveanyvirtualmachinesthatareon theESX Server 3ihost.Virtualmachinesarestoredonthedatastore,notontheUSB flash.Afteryouresettheconfigurationdefaults,thevirtualmachinesarenotvisible, butyoucanretrievethembyreconfiguringstorage(ifthehostdoesntrecognizeand configurestorageduringthereboot),andreregisteringthevirtualmachines. CAUTIONWhenyouresettheconfigurationdefaults,usersaccessingthishostthrough theVI ClientorVirtualCenterloseconnectivity. To reset configuration defaults 1 2 3 (Recommended)BackuptheconfigurationbyrunningtheRemoteCLI vicfg-cfgbackupcommand. Fromthedirectconsole,selectResetCustomizedSettingsandpressEnter. PressF11toconfirm. Thesystemprocessorrebootstheserverafterallsettingsarereset. 4 (Optional)Torestoreoverriddenconfigurationdata,usetheRemoteCLItorunthe vicfg-cfgbackupcommand.
SeeAboutBackingUpandRestoringanESX Server 3iConfigurationonpage 38.
VMware, Inc.
33
Managing ESX Server 3i Remotely

AftertheESX Server 3ihostisbootedintothedirectconsole,youcanmanagethehost byusingtheVI ClientandVirtualCenter.Todothis,installbothapplicationsona computerservingasamanagementstationwithnetworkaccesstotheESX Server 3i host.YoucaninstallVirtualCenterinlicensedmodeorinevaluationmode. YoucandownloadVirtualCenterfromwww.vmware.comorusetheVMware InfrastructureManagementInstallerCD.YoucandownloadtheVI Clientdirectlyfrom theESXServer3ihostorusetheVMwareInfrastructureManagementInstallerCD. FollowingarebriefinstructionsforinstallingtheVI ClientandVirtualCenter: VI ClientUsetheVI ClienttoconnecttoasingleESX Server 3ihostorto VirtualCenter. ToinstalltheVI Client,useabrowsertopointtotheIPaddressoftheESX Server 3i host(http://ESXhostIPaddress).OntheWelcomepage,clickDownloadthe VI Client.Alternatively,youcanusetheVMwareInfrastructureManagement InstallerCD,whichisincludedwithESX Server 3i. AfteryouinstalltheVI Client,youcanconnecttotheESX Server 3ihostbyusing theESX Server 3ihostIPaddresswithusernamerootandnopassword.Ifyou configureanadministrativepassword(asdescribedinConfiguringthe AdministrativePasswordonpage 32),usetheconfiguredpassword.Fordetailed informationaboutinstallingtheVI Client,seeInstallingVMwareInfrastructure Managementonpage 93. VirtualCenterIfyouhavemultipleESX Serverhosts,considerusing VirtualCenter,whichletsyoumanageallhostsfromasingleinterfaceanduse advancedfeatures,suchasVMwareHA,DRS,andVMotion. ToinstallVirtualCenter,downloadthelatestversionfrom http://www.vmware.com/download/vi/.Alternatively,youcanusetheVMware InfrastructureManagementInstallerCD,whichisincludedwithESX Server 3i. AfteryouinstallVirtualCenter,youcanmanageallofyourESX Serverhosts (includingESX Server 3i)fromasingleinterface.ToaccessVirtualCenter,usethe VI ClienttoconnecttotheVirtualCenterIPaddresswithyourWindowslogin usernameandpassword.Specifically,usethelogincredentialsappropriatetothe WindowsmachineonwhichVirtualCenterisinstalled.TheVirtualCenter usernameandpasswordmightbedifferentthantheusernameandpasswordyou useforESX Server 3i. FordetailedinformationaboutinstallingVirtualCenter,seeInstallingVMware InfrastructureManagementonpage 93.
34
VMware, Inc.
AfteryouinstalltheVI ClientandVirtualCenter,youcanconvertaphysicalmachine intoavirtualmachine.Alternatively,youcandownloadsamplevirtualmachinesat http://www.vmware.com/appliances/.Forinformationaboutimportingvirtual machines,seetheBasicSystemAdministrationGuide.
Restarting Management Agents

AmanagementagentissoftwarethatsynchronizesVMwarecomponentsandletsyou accesstheESX Server 3ihostthroughtheVI ClientorVirtualCenter.Itisinstalledwith theVMwareInfrastructureManagementsoftware.Youmightneedtorestartthe managementagentsifremoteaccessisinterrupted. Whenyourestartmanagementagents,thesoftwarerestartsallmanagementagentsand servicesthatareinstalledandrunningin/etc/init.dontheESXServerhost. Typically,theseagentsincludehostd,ntpd,sfcbd,slpd,andwsmand.Thesoftwarealso restartstheAutomatedAvailabilityManager(AAM)ifitisinstalled. CAUTIONWhenyourestartmanagementagents,usersaccessingthishostthroughthe VI ClientorVirtualCenterloseconnectivity. To restart management agents 1 2 Fromthedirectconsole,selectRestartManagementAgentsandpressEnter. PressF11toconfirmtherestart.
TheESX Server 3ihostrestartsthemanagementagents.
Viewing System Logs

Systemlogsprovidedetailedinformationaboutsystemoperationalevents. To view system logs 1 2 Fromthedirectconsole,selectViewSystemLogs. Pressacorrespondingnumberkeytoviewalog: 1Messages 2Configuration 3ManagementAgent(hostd) 4VirtualCenterAgent(vpxa) VirtualCenterAgent(vpxa)logsappearifyouaddthehosttoVirtualCenter.
VMware, Inc.
35
3 4
PressEnterorthespacebartoscrollthroughthemessages. (Optional)Performaregularexpressionsearch: a b c Presstheslashkey(/). Typethetexttofind. PressEnter. Thefoundtextishighlightedonthescreen.
Pressqtoreturntothedirectconsole.
To redirect system log files to a remote host 1 2 3 4 FromtheVI Client,selectthehostintheinventory. SelecttheConfigurationtabandclickAdvancedSettings. ClickSyslog. ForSyslog.Remote.Hostname,enterahostnametowhichsyslogdatacanbe forwarded.
36
VMware, Inc.
Backing Up and Restoring ESX Server 3i
ThischapterprovidesinformationaboutbackingupandrestoringtheESX Server 3i configurationandrecoveringtheESX Server 3ibootimageifitbecomesdamaged. Inaddition,itdescribeshowtoremoveESX Server 3ifromthehost. Thischaptercontainsthefollowingsections: AboutBackingUpandRestoringanESX Server 3iConfigurationonpage 38 RecoveringtheESX Server 3i EmbeddedSoftwareonpage 41 RemovingESX Server 3ifromtheHostonpage 42 ForinformationoninstallingVMwareInfrastructureManagementsoftware,see InstallingVMwareInfrastructureManagementonpage 93.Forinformationabout usingthedesktopclients,seetheVMwareInfrastructure3documentationset.
VMware, Inc.
37
About Backing Up and Restoring an ESX Server 3i Configuration

YoucanbackuptheESX Server 3ihostconfigurationdataafterpreliminarytasksare completed.VMwarerecommendsthatyoubackupyourhostconfigurationafteryou changetheconfigurationorupgradetheESX Serverimage. Whenyouperformaconfigurationbackup,theserialnumberisbackedupwiththe configurationandisrestoredwhenyourestoretheconfiguration.However,theserial numberisnotpreservedwhenyouruntherecoveryCD.Forthisreason,the recommendedprocedureistofirstbackuptheconfiguration,runtherecoveryCD if needed,thenrestoretheconfiguration. Youperformthebackupbyusingthevicfg-cfgbackupcommand,whichyourun fromtheRemoteCommandLineInterface(RemoteCLI).TheRemoteCLIisavailable intwoforms: AsavirtualappliancethatyouimportintoESXServer,VMwareWorkstation,or VMwarePlayer. AsapackagethatyouinstallonMicrosoftWindowsandLinuxmachines. Yourunthevicfg-cfgbackupcommandfromtheServiceConsoleofthevirtual applianceorfromacommandpromptonthesystemwhereyouinstalledthe Remote CLIs.YourunCLIcommandsonanESX Server 3ihosttowhichyouconnect remotely. ForinformationaboutsettingupandusingtheRemoteCLI,seetheESXServer3i ConfigurationGuideappendices.
Considerations When Using the Remote CLI Virtual Appliance

Whenyoubackupthehostconfiguration,youcanrunthevicfg-cfgbackup commandfromaRemoteCLIvirtualappliancethatisrunningonthetargethost(the hostyouarebackinguporrestoring),oryoucanrunitfromaremotehost.However, torestoreaconfigurationonthetargethost,youmustruntheRemoteCLIvirtual appliancefromaremotehost. Whenyourestoretheconfiguration,thetargethostmustbeinmaintenancemode, whichmeansallvirtualmachines(includingtheRemoteCLIvirtualappliance)must bepoweredoff. Forexample,supposeyouhavetwoESX Server 3ihosts(host1andhost2)andyou importthevirtualapplianceintobothhosts.Tobackupthehost1configuration,run thevicfg-cfgbackupcommandintheRemoteCLIoneitherhost1orhost2andpoint tohost1inthe-servercommandlineoption.
38 VMware, Inc.
Chapter 3 Backing Up and Restoring ESX Server 3i
Likewise,tobackupthehost2configuration,youcanrunthevicfg-cfgbackup commandintheRemoteCLIoneitherhost1orhost2andpointtohost2inthe-server commandlineoption.Torestorethehost1configuration,runthevicfg-cfgbackup commandintheRemoteCLIonhost2andpointtohost1inthe-servercommandline option.Torestorethehost2configuration,runthevicfg-cfgbackupcommandinthe RemoteCLIonhost1andpointtohost2inthe-servercommandlineoption.
Backing Up ESX Server 3i Configuration Data

To back up host configuration data 1 StarttheRemoteCLIandlogin. Youdonotneedtotypethepasswordonthecommandline.Ifnopasswordis specified,thetoolpromptsyouforthepasswordwithoutechoingtheoutputtothe terminal.Thismeansthepasswordyoutypeisnotvisibleinthewindowasyou runthecommand. YoucancreateasecureconnectiontotheRemoteCLI,byusingtheRemoteCLIIP address.IfyouareusingtheVI Client,youcanrightclicktheRemoteCLIand selectOpenConsole.IftheRemoteCLIisinstalledonyourWindowsorLinux system,youcanusetheinstalledapplication,inwhichcaseyoudonotneedtolog in. 2 Runthevicfg-cfgbackupcommandwiththe-sflagtosavethehost configurationtothespecifiedbackupfilename.
vicfg-cfgbackup --server <3i-host-ip> --portnumber <port_number> --protocol <protocol_type> --username root --password <root_password> -s <backup-filename>
The-portnumberand-protocoloptionsareoptional.Ifyouexcludethem,the defaultsareport443andprotocolHTTPS. Ifyouradministrativepasswordincludesspecialcharacters,suchas$or&,youmust includeabackslashescapecharacter(\)beforeeachspecialcharacter. Forthebackupfilename,includethebuildnumberthatiscurrentlyrunningonthehost thatyouarebackingup.IfyouarerunningtheRemoteCLIasavirtualappliance,the backupfileissavedlocallyonthevirtualappliance.Localstorageforbackupfilesis safebecausevirtualappliancesarestoredinthe/vmfs/volumes/<datastore> directory,whichisseparatefromtheESX Server 3iimageandconfigurationfiles.
VMware, Inc.
39
Restoring ESX Server 3i Configuration Data

YoucanrestoretheESX Server 3ihostconfigurationdataifyouhavecreatedabackup. To restore host configuration data 1 Poweroffanyvirtualmachinesthatarerunningonthehostthatyouwantto restore. Whenyourunthevicfg-cfgbackup -lcommand,thesoftwareplacesthehost intomaintenancemode.Thehostcannotbeplacedintomaintenancemodeunless youfirstpoweroffallvirtualmachinesthatarerunningonthehost. 2 (Optional)RestorethehosttotheESX Serverbuildthatwasrunningwhenyou createdtheconfigurationbackup. Whenyourestoreconfigurationdata,thebuildnumbercurrentlyrunningonthe hostmustbethesameasthebuildnumberthatwasrunningwhenyoucreatedthe backupfile.Youcanoverridethisrequirementbyincludingthe-f(force)flagwith thevicfg-cfgbackupcommand. 3 Onahostotherthanthehostyouarerestoring,powerontheRemoteCLIandlog in. Youdonotneedtotypethepasswordonthecommandline.Ifnopasswordis specified,thetoolpromptsyouforthepasswordwithoutechoingtheoutputtothe terminal.Thismeansthepasswordyoutypeisnotvisibleinthewindowasyou runthecommand. YoucancreateasecureconnectiontotheRemoteCLIbyusingtheRemoteCLIIP address.IfyouareusingtheVI Client,youcanrightclicktheRemoteCLIand selectOpenConsole.IftheRemoteCLIisinstalledonyourWindowsorLinux system,youdonotneedtologin. 4 Runthevicfg-cfgbackupcommandwiththe-lflagtoloadthehost configurationfromthespecifiedbackupfile.
vicfg-cfgbackup --server <3i_host_IP> --portnumber <port_number> --protocol <protocol_type> --username root --password '<root_password> -l <backup_filename>
Thehostyouarerestoringrebootsandthebackupconfigurationisrestored. The-portnumberand-protocoloptionsareoptional.Ifyouexcludethem,the defaultsareport443andprotocolHTTPS. Ifyouradministrativepasswordincludesspecialcharacters,suchas$or&,youmust includeabackslashescapecharacter(\)beforeeachspecialcharacter.
40
VMware, Inc.
Chapter 3 Backing Up and Restoring ESX Server 3i
Recovering the ESX Server 3i Embedded Software

IfthehostdoesnotbootupinESX Server 3imode,eventhoughtheBIOSisconfigured tobootfromtheUSBflash,thefilepartitionsontheUSBflashmightbecorrupted. To resolvethisproblem,youcanrestorethesoftwarebyrunningtheESX Server 3i recoveryCD(ifyouhaveone).Yourhardwarevendormightprovideinstructionsfor recoveringyourESXServer3i,ormightincludearecoveryCDwiththeserver platform.IfyoudonothavearecoveryCD,contactyourhardwarevendororVMware CustomerServicetoobtaintheappropriateISOfile.AfteryouobtaintheISOfile,you canburnitontoablankCD. RunningtherecoveryCDoverwritesallconfigurationdatawithmostofthesystem defaults.Theserialnumberthatyourhardwarevendorinstalledislostwhenyourun therecoveryCD.Whenyouperformaconfigurationbackup,theserialnumberis backedupwiththeconfigurationandisrestoredwhenyourestoretheconfiguration. Forthisreason,therecommendedprocedureistofirstbackuptheconfiguration,run therecoveryCDifneeded,thenrestoretheconfiguration.Youcannotbackupthe configurationunlessthehostbootsintoESX Server3imodeatleastonce,soitisnot alwayspossibletofollowtherecommendedprocedure.Whenthereisnoconfiguration backup,callyourhardwarevendorstechnicalsupporttoretrievetheserialnumber. To restore ESX Server 3i 1 2 InserttherecoveryCDintotheESX Server 3ihost. UsethesystemBIOStochangethebootordersothattheCDROMdriveislisted first.Tomodifythebootsequence: a b c Rebootthehost. Whilethehostispoweringon,pressF11orF12toopentheBIOSSetuppage. SelecttheCDROMdriveandmoveittothefirstpositioninthelist.
TheoptiontoopentheBIOSSetuppagemightbedifferentforyourserver. You mightneedtoopentheBIOSconfigurationscreenstomodifythebootsetting. Asthehostcontinuestopoweron,therecoveryCDWelcomescreenappears. 3 PressEntertocontinuethroughthescreens. Tocanceltherecoveryoperation,presstheEsckey.IfyoupresstheEsckey,the hostrebootsandthedatacontainedonyourserversembeddedUSBflashremains intact. IfyoupressEnterthroughallthescreensandtherecoveryoperationbegins,you cannotcancelorundotherecovery.
VMware, Inc.
41
4 5 6 7
PressEntertorebootthehost. RemovetheCDROMfromtheCDROMdrive. ReopenthesystemBIOStochangethebootordersothattheUSBflashislisted first. VerifythatthehostbootsintoESX Server 3imode.
Afterthereboot,anewESX Serversoftwarebuildisinstalledandallconfigurationdata islost.IfyoubackeduptheESX Serverconfiguration,youcanrestoreit.Whenyou performaconfigurationbackup,theserialnumberisbackedupwiththeconfiguration andisrestoredwhenyourestoretheconfiguration.Torestoreconfigurationdata,first upgradetotheESX Serverbuildthatwasrunningwhenyoucreatedthebackup.Then usetheRemoteCLItorunthevicfg-cfgbackupcommand. Afteryourestorethehostfirmware,virtualmachinesonthathostmightnotbelisted inthehostinventory.Thisdoesnotmeanthatthevirtualmachinesarelostor destroyed.AnyvirtualmachinesthatyouaddedtothehostremainintheVMFS datastoreunlessyouexplicitlyremovethem.Forinformationaboutreturningavirtual machinetotheVirtualCenterinventory,seetheBasicSystemAdministrationGuide. SeealsoAboutBackingUpandRestoringanESX Server 3iConfigurationonpage 38.
Removing ESX Server 3i from the Host

IfyoudonotwantyourservertobeanESX Server 3ihost,youcandeactivatethe ESX Server 3isetup.Todothis,youdothefollowing: RemoveVMFSdatastoresontheinternaldiskssothattheinternaldisksareno longersetuptostorevirtualmachines.SeeConfiguringStorageBehavioron page 29. ChangethebootsettingintheBIOSsothatthehostnolongerstartsupin ESX Server 3imode.SeeConfiguringtheBootSettingforAnotherModeon page 23.
42
VMware, Inc.
Adding ESX Server 3i to VMware Infrastructure
Thischapterdiscussestherequirementsandrecommendationsforadding ESX Server 3ihoststoadatacenterthathasexistingVMwareInfrastructure components,suchasESX ServerhostsandVirtualCenter Server. Specifically,thischapterdiscussestheimplicationsforVirtualCenter,virtualmachines, virtualmachinetools,andESXupgrades,whenyouaddESX Server 3itoyourVMware Infrastructure. UpgradingVMwareInfrastructurecomponentsfromearlierversionsisamultistage processinwhichproceduresmustbeperformedinaparticularorder.Theupgrade pathdependsonyourESX Serveranddatastoreconfigurations.Fordetailed informationaboutpreparingforandexecutingVMwareInfrastructureupgrades,see theUpgradeGuideforESX Server 3.5andVirtualCenter 2.5.
VirtualCenter
IfyouhaveanolderversionofVirtualCenterandyouwanttouseVirtualCenterto manageESX Server 3i(orESX Server 3),youmustupgradetheVirtualCenter softwaretoversion2.5. ESX Server 3iversion3.5hostsandESX Server 3.5hoststhataremanagedtogether inVirtualCentercanrunthesamevirtualmachines,useVMotiontomigrate virtualmachinesbetweenthehosts,andaccessthesamedatastores. YoucanmanageESX Server 3.0hostsinthesameclusterwithESX Server 3iand ESX Server 3.5hosts. YoucanmanageESX Server2.0.xasstandalonehostsinVirtualCenter. ESX Server 2.0.xhostscannotbeaddedtoclusters.
VMware, Inc.
43
Virtual Machines
Ingeneral,virtualmachinesthatyoucreateonESX Server 3i(orESX Server 3) hostsaresupportedonESX Server 3.0.xhosts.Thiscapabilitymeansthatyoucan migratethevirtualmachinesbetweenthehostsanduseVMotion.Ifyoucreate virtualmachinesthatuseparavirtualization(VMI)oranenhancednetworking device(vmxnet),VMotionisnotsupported.Inthiscase,youcanmovethevirtual machinetotheESX Server 3.0.xhostifthevirtualmachineispoweredoff. VirtualmachinesthatyoucreateonESX Server 3i(orESX Server 3.5)hostsarenot supportedonESX Server2.xhosts.
Virtual Machine Tools

ForESXServer3iversion3.5,thereisavirtualhardwareupgradeandaVMware Toolsupgrade.TheVMwareToolsupgradeisnotrequiredbutisavailablefor version2.xandversion3.xvirtualmachines. IfyouupgradeVMwareToolsforavirtualmachinetoVMwareToolsversion3.5, youcanusetheupgradedvirtualmachineonanESX Server 3.0.xhost.Ifyoudo migratethevirtualmachinetoanESX Server3.0.xhost,VMwarerecommendsthat youuninstalltheESX Server3.5ToolsandinstallESX Server3.0.xTools.
ESX Server Upgrades

UpgradesfromearlierversionsofESX ServertoESX Server 3ihavenoinplace upgrade,butyoucanmigrateexistingvirtualmachinesanddatastores. ToreplaceESX Server 3iversion3.5withESX Server3,youcandisable ESX Server 3i(as describedinRemovingESX Server 3ifromtheHoston page 42)andtheninstallESX Server3inplace.Alternatively,youcanmigrate virtualmachinesfromanESX Server3ihosttoanESX Server 3host. ESXServer3iversion3.5isthefirstreleaseofESXServer3i.Thereiscurrentlyno ESXServer3iupgradeavailable.
44
VMware, Inc.
VMware Infrastructure System Requirements
YoucanmanageastandaloneVMwareESX ServerwithoutVirtualCenter Server. However,ifyouhavemultipleESX Serverhostsandyouwanttomanagethem centrally,considerinstallingtheVirtualCenter Server.Thisserverinstallsona Windowsmachine,eitherphysicalorvirtual.VirtualCenterallowstheuseofadvanced VMwareInfrastructurefeaturessuchasVMwareDRS,VMwareHA,andVMotion. Thischapterdescribesthehardwareandoperatingsystemrequirementsforhosts runningVirtualCenterandotherVMwareInfrastructurecomponents.Usethe informationinthischaptertoensurethatyourenvironmentmeetstherequirementsfor installation.Topicscoveredhereare: VirtualCenterRequirementsonpage 45 VI ClientHardwareRequirementsonpage 47 VI ClientSoftwareRequirementsonpage 48 LicenseServerRequirementsonpage 48 SupportedGuestOperatingSystemsonpage 49 VirtualMachineRequirementsonpage 49
VirtualCenter Requirements
VirtualCentermanagesESX Serverhostsbyusingaserverandthreetypesofremote managementclients.TheVirtualCenter Serverisaphysicalmachineorvirtualmachine configuredwithaccesstoasupporteddatabase.
VMware, Inc.
45
VirtualCenter Hardware Requirements

VirtualCenterhardwaremustmeetthefollowingrequirements: Processor2.0GHzorlaterIntelorAMDx86processor.Processorrequirements canbelargerifyourdatabaseisrunonthesamehardware. Memory2GBRAMminimum.RAMrequirementscanbelargerifyourdatabase isrunonthesamehardware. Diskstorage560MBminimum,2GBrecommended.Youmusthave245MBfree onthedestinationdriveforinstallationoftheprogram,andyoumusthave315MB freeonthedrivethatcontainsyour%temp%directory. NOTEStoragerequirementscanbelargerifyourdatabaserunsonthesame hardwareastheVirtualCentermachine.Thesizeofthedatabasevarieswiththe numberofhostsandvirtualmachinesyoumanage.Usingdefaultsettingsfora yearwith25hostsand8to16virtualmachineseach,thetotaldatabasesizecan consumeupto2.2GB(SQL)or1.0GB(Oracle). MicrosoftSQLServer2005ExpressdiskrequirementsThebundleddatabase requiresupto2GBfreediskspacetodecompresstheinstallationarchive. However,approximately1.5GBofthesefilesaredeletedaftertheinstallationis complete. NetworkingGigabitrecommended.
VirtualCenter Software Requirements

VirtualCenterissupportedonthe32bitversionsoftheseoperatingsystems: Windows2000ServerSP4withUpdateRollup1(DownloadUpdateRollup1at http://www.microsoft.com/windows2000/server/evaluation/news/bulletins/rollu p.mspx) WindowsXPProSP2 Windows2003ServerSP1 Windows2003ServerR2 VirtualCenter 2.xinstallationisnotsupportedon64bitoperatingsystems. TheVirtualCenterinstallerrequiresInternetExplorer5.5orlater.
46
VMware, Inc.
Chapter 5 VMware Infrastructure System Requirements
VirtualCenter Database Requirements

VirtualCentersupportsthedatabaseformatslistedinTable 51. Table 5-1. Supported Database Formats
Database Type MicrosoftSQLServer2000Standard MicrosoftSQLServer2000Enterprise Service Pack, Patch, and Driver Requirements SP4 ForWindows2000andWindowsXP,apply MDAC2.8SP1totheclient. UseSQLServerdriverfortheclient. SP1orSP2 ForWindows2000andWindowsXP,apply MDAC2.8SP1totheclient. UseSQLnativeclientdriverfortheclient. ForWindows2000andWindowsXP,apply MDAC2.8SP1totheclient. UseSQLnativeclientdriverfortheclient. Applypatch9.2.0.8.0totheserverandclient. None Firstapplypatch10.2.0.3.0totheclientandserver. Thenapplypatch5699495totheclient.(SEEUPDATE)
MicrosoftSQLServer2005Enterprise
MicrosoftSQLServer2005ExpressSP2
Oracle9irelease2Standard Oracle9irelease2Enterprise Oracle10gStandardRelease1(10.1.0.3.0) Oracle10gEnterpriseRelease1(10.1.0.3.0) Oracle10gStandardRelease2(10.2.0.1.0) Oracle10gEnterpriseRelease2(10.2.0.1.0)
Eachdatabaserequiressomeconfigurationadjustmentsinadditiontothebasic installation.SeePreparingtheVirtualCenter ServerDatabaseonpage 93.
End of Support Life for Microsoft Access and MSDE Databases

SupportforMicrosoftAccesswasdiscontinuedwithVMwareVirtualCenter version 2.0.SupportforMSDEisdiscontinuedwithVMwareVirtualCenterversion 2.5. VirtualCenter 2.5includesabundledversionofMicrosoftSQLServer2005Express,for useinsmalldeploymentsofupto5hostsand50virtualmachines.
VI Client Hardware Requirements

TheVI Clienthardwaremustmeetthefollowingrequirements: Processor266MHzorfasterIntelorAMDx86processor(500MHz recommended). Memory256MBRAMminimum,512MBrecommended.
VMware, Inc.
47
DiskStorage150MBfreediskspacerequiredforbasicinstallation.Youmust have55MBfreeonthedestinationdriveforinstallationoftheprogram,andyou musthave100MBfreeonthedrivethatcontainsyour%temp% directory. NetworkingGigabitrecommended.
VI Client Software Requirements

TheVI Clientisdesignedfortheseoperatingsystems: Windows2000ProSP4 Windows2000ServerSP4withUpdateRollup1(DownloadUpdateRollup1at http://www.microsoft.com/windows2000/server/evaluation/news/bulletins/rollu p.mspx) WindowsXPProSP2 Windows2003SP1(allreleasesexcept64bit) Windows2003ServerR2 WindowsVistaBusiness(including64biteditions) WindowsVistaEnterprise(including64biteditions) TheVI ClientrequirestheMicrosoft.NETFramework.Ifyoursystemdoesnthaveit installed,theVI Clientinstallerinstallsit.
License Server Requirements

Thissectiondescribesthelicenseserverrequirements. Thelicenseserverhardwaremustmeetthefollowingrequirements: Processor266MHzorfasterIntelorAMDx86processor. Memory256MBRAMminimum,512MBrecommended. DiskStorage25MBfreediskspacerequiredforbasicinstallation. NetworkingGigabitrecommended. VMwarerecommendsthatyouinstallthelicenseserveronthesamemachineasyour VirtualCenter Servertoensureconnectivity.TheVMwareInfrastructureManagement InstallationCDinstallsalicenseserverwhenyouinstallVirtualCenter.
48
VMware, Inc.
Chapter 5 VMware Infrastructure System Requirements
Thelicenseserversoftwareissupportedonthe32bitversionsofthefollowing operatingsystems: Windows2000ServerSP4 WindowsXPPro(atanySPlevel) Windows2003(allreleasesexcept64bit)
Supported Guest Operating Systems

TheVMwareGuestOperatingSystemInstallationGuideincludesinformationon supportedguestoperatingsystems.Thisdocumentisavailablefordownloadat: http://www.vmware.com/support/pubs/vi_pubs.html ESX Serverversion3.5offerssupportforanumberof64bitguestoperatingsystems. Foracompletelist,seetheGuestOperatingSystemInstallationGuide. A64bitguestoperatingsystemrequiresspecifichardware.ForAMDOpteronbased systems,theprocessorsmustbeOpteronRevEandlater.ForIntelXeonbasedsystems, theprocessorsmustincludesupportforIntelsVirtualizationTechnology(VT).Many serversthatincludeCPUswithVTsupportmighthaveVTdisabledbydefault,andVT mustbeenabledmanually.IfyourCPUssupportVT,butyoudonotseethisoptionin theBIOS,contactyourvendortorequestaBIOSversionthatletsyouenableVT support. Todeterminewhetheryourserverhasthenecessarysupport,youcanuseaCPU CompatibilityToolathttp://www.vmware.com/download/vi/drivers_tools.html.
Virtual Machine Requirements

EachESX Servervirtualmachinehastherequirementsspecifiedinthissection.
Virtual Processor
IntelPentiumIIorlater(dependentonsystemprocessor) One,two,orfourprocessorsforeachvirtualmachine Ifyouplantocreateatwoprocessorvirtualmachine,yourESX Servermachinemust haveatleasttwophysicalprocessors.Forafourprocessorvirtualmachine,your ESX Servermachinemusthaveatleastfourphysicalprocessors.
Virtual Chip Set

Intel440BXbasedmotherboardwithNS338SIOchip
VMware, Inc. 49
Virtual BIOS
PhoenixBIOS4.0Release6
50
VMware, Inc.
VirtualCenter and ESX Server 3i Licensing Overview
ThischapterdescribesthelicensingmodelsavailablewithESX Server 3iand VirtualCenter. Thischaptercontainsthefollowingsections: LicensingTerminologyonpage 52 ESX Server 3iEditionsonpage 52 VirtualCenter ServerEditionsonpage 54 VirtualCenterandESX Server 3iLicensingModelonpage 54 LicenseKeyFunctionalityonpage 57 LicenseExpirationConsiderationsonpage 60 LicenseServerAvailabilityonpage 60 UsinganExistingFLEXnetLicenseServeronpage 64 ContactingSupportonpage 65
VMware, Inc.
51
Licensing Terminology
Youmightencounterthefollowingtermsduringthelicenseredemptionand configurationprocess: LicenseactivationcodeAlicenseactivationcode(LAC)isauniquecodethatis associatedwithoneormoreVMwareproductspurchased.Youreceivethiscode afteryourorderisprocessed,unlessyoupurchasedyourproductsfroman authorizedVMwarereseller,inwhichcaseyoureceiveapartneractivationcode. PartneractivationcodeApartneractivationcodeisauniquecodeidentifying ordersplacedthroughVMwarepartners.IfyoupurchasedVMware Infrastructure 3fromanauthorizedVMwarereseller,youusethiscodetoregister yourpurchasetoyourVMwarestoreaccount. LicenseactivationportalThelicenseactivationportalisaselfserviceWebportal thatyoucanusetoredeemyourlicenseactivationcodesanddownloadlicensefiles forVMwareInfrastructure3. PartneractivationportalApartneractivationportalisaselfserviceWebportal usedtoregisterapurchasemadefromanauthorizedVMwareresellertoyour VMwarestoreaccount.Youenteryourpartneractivationcodeintotheportaland downloadyourlicensefilesfromthelicenseactivationportal.
ESX Server 3i Editions

DependingontheeditionofVMwareInfrastructuresoftwareyoupurchased,you mightbeentitledtodifferentESX Server 3ilicencetypes. SomeeditionsincludelimitedaccesstothefeaturesetofESX Server 3i.Certain standardfunctionalityisavailableonlywithanoptionaladdonlicense,atadditional cost.OthereditionsincludefullaccesstothefullfeaturesetofESX Server 3i. LicensesfrompreviousreleasesofESXServerworkwithESX Server 3iversion 3.5. However,licensingcapabilitiesaddedtoESXServer3iversion3.5editions (for example,VMwareConsolidatedBackup)arenotsupportedwithpreviouseditions ofESXServer.
52
VMware, Inc.
Chapter 6 VirtualCenter and ESX Server 3i Licensing Overview
Table 61displaysESX Server 3ifeaturesarrangedbyedition. Table 6-1. Edition Features for ESX Server 3i Machines
Feature Licensetype ESX Server 3i Standalone Serialnumber VI Foundation Flexlicensefiles (centralizedor singlehost) Yes Yes Yes Yes Addon Addon Addon VI Standard Flexlicensefiles (centralizedor singlehost) Yes Yes Yes Yes Yes Addon Addon VI Enterprise Flexlicensefiles (centralizedor singlehost) Yes Yes Yes Yes Yes Yes Yes
VMFS VirtualSMPsupport VMwareConsolidated Backup(VCB) VMwareUpdateManager VMwareHA ServerVMotionand Storage VMotion VMwareDRSandDPM (DistributedResource Managementand DistributedPower Management) Guidedserver consolidation, with purchaseof VirtualCenter Server Manageablebythe VI Client
Yes Yes No No No No No
No
Yes
Yes
Yes
Oneinstanceof theVI Client canmanagea hostatany giventime. Restricted Addon
Unrestricted
Unrestricted
Unrestricted
RemoteCLIaccess Manageableby VirtualCenter in productionmode Manageableby VirtualCenterinevaluation mode VirtualCenterManagement Agent
Yes Yes
Yes Yes
Yes Yes
Yes
Yes
Yes
Yes
Addon
Yes
Yes
Yes
VMware, Inc.
53
VirtualCenter Server Editions

AtleastoneinstanceofaVirtualCenterlicenseisrequiredforVIFoundation, VI Standard,andVIEnterpriseeditions.ThefollowingVirtualCentereditionsare available: VirtualCenterFoundationLetsyoumanageuptothreeESX Serverhosts.Ifyou needtomanagemorethanthreehosts,upgradetoVirtualCenteredition. VirtualCenterAnenterpriseleveleditionthatletsyoumanageuptothesystem maximumnumberofhosts.Forinformationaboutsystemmaximums,see ConfigurationMaximumsforVMwareInfrastructure3. VirtualCentereditionsrequireflex,centralizedlicensefiles.Youcanconvert VirtualCenterFoundationeditiontoVirtualCentereditionbyaddinganappropriate licensefileandswitchingtheeditions.Thesoftwaredoesntneedtobereinstalled.For informationaboutswitchingbetweentheeditions,seeToconfigurecentralized licensingforVirtualCenteronpage 76. YoucanconvertVirtualCenterFoundationeditiontoVirtualCenterFulleditionby simplyaddinganappropriatelicensefileandswitchingtheeditions.Thesoftware doesntneedtobereinstalled.Forinformationonswitchingbetweentheeditions,see ToconfigurecentralizedlicensingforVirtualCenteronpage 76.
VirtualCenter and ESX Server 3i Licensing Model

ForESX Server 3i,theStandaloneeditionletsyouperformmostoperations.Touse someadvancedoperations,youcanuseevaluationmodeoryoucanpurchasean upgradedlicense. ForVirtualCenter,unlessyouareusingevaluationmode,asoftwarelicenseisrequired formostoperations,suchasaddinghoststoyourVirtualCenterinventory.However, youcaninstall,launch,andconfigureVirtualCenterversion2.5withoutasoftware license. Twomodesoflicensingareavailable:singlehostandcentralized.Bothsinglehostand centralizedlicensesarebasedonFLEXnetmechanisms.Aflexlicenseiseitherserved (centralized)orunserved(singlehost).
Single-Host and Centralized License Types

Forsinglehostlicenses,theserialnumberorlicensefilesarestoredonindividual ESX Serverhosts.Centralizedlicensesarestoredonalicenseserver,whichmakesthese licensesavailabletooneormorehosts.Youcanrunamixedenvironmentemploying bothsinglehostandcentralizedlicensing.
54
VMware, Inc.
VirtualCenterandfeaturesthatrequireVirtualCenter,suchasVMotion,musthave centralizedlicensing.ESX Serverspecificfeaturescanbelicensedforeithercentralized orsinglehostlicensing. Figure 61illustratesthethreetypesoflicenseenvironments. Figure 6-1. License File Locations in Single-Host, Mixed, and Centralized Licensing Environments
single-host licensing
VI Client ESX host license file ESX host license file ESX host serial number
mixed: single-host and centralized licensing

VI Client ESX host license file ESX host license file VirtualCenter (recommended) ESX host ESX host
centralized licensing
VI Client ESX host
ESX host
VirtualCenter (recommended)
license server
license server
license file
license file
VMware, Inc.
55
Centralized Licensing
Centralizedlicensingsimplifieslicensemanagementinlarge,dynamicenvironments byallowingaVMwarelicenseservertoadministerlicenses.Withcentralizedlicensing, youmaintainallofyourVirtualCenter ServerandESX Serverlicensesfromone console. Withcentralizedlicensing,alicenseservermanagesalicensepool,whichisacentral repositoryholdingyourentirelicensedentitlement.Whenahostrequiresaparticular licensedfunctionality,thelicenseforthatentitlementischeckedoutfromthelicense pool.Licensekeysarereleasedbacktothepoolwhentheyarenolongerbeingusedand areavailableagaintoanyhost. Theadvantagesofcentralizedlicensinginclude: Youadministeralllicensingfromasinglelocation. NewlicensesareallocatedandreallocatedbyusinganycombinationofESX Server formfactors.Forexample,youcanusethesame32processorlicenseforsixteen 2processorhosts,eight4processorhosts,four8processorhosts,two16processor hosts,oranycombinationtotaling32processors. Ongoinglicensemanagementissimplifiedbyallowinglicensestobeassignedand reassignedasneeded.Assignmentchangesastheneedsofanenvironment change,suchaswhenhostsareaddedorremoved,orpremiumfeatureslike VMotion,DRS,orHAaretransferredamonghosts. Duringperiodsoflicenseserverunavailability,althoughnewlicensescannotbe issued,existingVirtualCenter Serverlicensedfunctionalitycontinuestooperate indefinitelyandexistingESX Serverlicensedfunctionalitycontinuestooperate withina14daygraceperiod.SeeLicenseServerAvailabilityonpage 60. VMwarerecommendsthatyouusecentralizedlicensingforlarge,changing environments.
Single-Host Licensing
Therearetwoscenariosforsinglehostlicensing: HostbasedserialnumberFortheESXServer3iStandaloneedition,eachhost hasaserialnumberthatissuppliedbythehardwarevendorandistypically preinstalled.Iftheserialnumberisnotpreinstalled,itmightbeenclosedona stickeroracard. HostbasedlicensefileForallotherESXServer3ieditionsincludingVI3 Foundation,VI3Standard,andVI3 Enterpriseeachhosthasalicensefile.
56
VMware, Inc.
Forhostbasedlicensefiles,thefollowingrulesapply: Yourtotalentitlementforpurchasedfeaturesisdividedamongseparatelicense filesresidingonESX ServerhostsandtheVirtualCenter Server. Whensomeoneactivatesalicensedfeature,thefeatureforthatentitlementmust resideinthelicensefileonthathost. YoumaintainseparatelicensefilesoneachESX Serverhost.Distributionofunused licensesisnotautomatic,andyoudonotdependonanexternalconnectionfor licensing. Theadvantagesofhostbasedlicensefilesinclude: SinglehostfilesrequirenolicenseservertobeinstalledforESX Serverhostonly environments. InaVirtualCenterandlicenseserverenvironment,hostbasedlicensefilesallows ESX Serverhostlicensestobemodifiedduringperiodsoflicenseserver unavailability.
License Key Functionality

LicensekeysdeterminespecificentitlementtorunVMwaresoftware.Dependingon theESX ServerandVirtualCenterfeaturesyouwanttouse,youpurchasesuchkeys basedononeofthefollowingcriteria: PerprocessorbasisToactivateafeature,ahostrequiresafeaturelicenseforeach ofitsprocessors. PerinstancebasisToactivateasingleinstanceofacertainfeature,asinglelicense isrequiredregardlessofhowmanyprocessorsareused. Licensedfeaturesalsodifferintheiroperationbasedonwhethertheyareconsideredto beESX ServerorVirtualCenterfeatures.YoucanlicenseESX Serverfeaturesbyusing eithersinglehostorcentralizedlicensing.TheydonotrequireVirtualCenterora licenseserver.VirtualCenterfeaturesrequirecentralizedlicensing.ESX Serverfeatures andVirtualCenterfeaturesalsodifferintheirbehaviorwhenthelicenseserverisnot available.SeeLicenseServerAvailabilityonpage 60.
VMware, Inc.
57
Table 62summarizesthelicensefeaturetypesforVMwareInfrastructure3. Table 6-2. Summary of License Feature Types

Feature ESX Server VirtualCenter Server VirtualCenterAgentforESX Server VMwareConsolidatedBackup(VCB) ServerVMotionandStorageVMotion VMwareHA VMwareDRSandDPM ESX Server or VirtualCenter ESX Server VirtualCenter VirtualCenter ESX Server VirtualCenter VirtualCenter VirtualCenter Per-Processor or Per-Instance PerProcessor PerInstance PerProcessor PerProcessor PerProcessor PerProcessor PerProcessor
Per-Processor Licensing
FormostVMwareInfrastructureproducts,youpurchaselicensesonaperprocessor basis,whichmeansthatyouneedtoindicatethetotalnumberofprocessors,nothosts, thatwillruntheproducts.Youcanthendeployandredeploythepurchasedprocessor capacity,soldinincrementsoftwoprocessors,onanycombinationofhosts. Forexample,youpurchaseESX ServerlicensesfortenprocessorsandVMotionlicenses forsixprocessors.Youcanthendeploythoselicensesonanyofthefollowing combinationsofservers: ESX Serveronfive2processorhosts.EnableVMotiononthreehosts. ESX Serveronthree2processorhostsanda4processorhost.EnableVMotionon three2processorhosts,oronone2processorhostanda4processorhost. ESX Serverontwo4processorhostsandone2processorhost.EnableVMotionon one4processorhostandone2processorhost. ESX Serveronone8processorhostandone2processorhost.VMotionbetween thesetwohostscannotbeenabledunlessyoupurchaseanadditional4processor VMotionlicense.
58
VMware, Inc.
Specialconsiderationsinclude: Dualcoreandquadcoreprocessors,suchasIntelx86processorsthatcombinetwo orfourindependentcentralprocessingunitsonasinglechip,countasone processor. Youcannotpartiallylicenseamultiprocessorhost.Forexample,a4CPUhost requiresalicensewiththecapacityforfourprocessors. Singleprocessorlicensingissupportedforserverbasedlicenses.Ingeneral,for serverbasedlicensing,checkoutoflicensesinoddquantitiesissupported. However,hostbasedfilescannotbegeneratedwithoddquantities.Theymustbe generatedinmultiplesoftwo. Thefollowingfeaturesarelicensedonaperprocessorbasis: ESX ServerTopoweronavirtualmachine,ahostmusthavelicensingona perprocessorbasis.Thismeansadualprocessorhostrequirestwomatching ESX Serverlicenses.AfourprocessormachinerequiresfourmatchingESX Server licenses.SeeESX Server 3iEditionsonpage 52. VMwareConsolidatedBackup(VCB)TousetheConsolidatedBackup capabilitiesandbackupofallvirtualmachinesrunningonanESX Serverhosta VCBlicensekeymustbeavailableforeachprocessorwithinthathost.Fora descriptionofthisfeature,seetheVirtualMachineBackupGuide. VirtualCenterAgentforESX ServerThisagentisinstalledonanESX Server hostwhenitisaddedtotheVirtualCenter Server.Youmusthaveoneagentlicense keyforeachESX ServerprocessortobeaddedtoVirtualCenter. ServerVMotionandStorageVMotionTomigrateapoweredonvirtualmachine betweenhosts,eachESX ServerprocessorinvolvedmusthaveaVMotionlicense key.Forexample,ifyouuseVMotionfromadualprocessorESX Serverhostto anotherdualprocessorhost,youmusthavefourVMotionlicenses.SeeBasic SystemAdministration. VMwareHATorestartvirtualmachineswhoseESX Serverhosthasfailed,the VirtualCenter ServermusthaveanHAlicensekeyforeachESX Serverprocessor intheHAcluster.Foradescriptionofthisfeature,seetheResourceManagement Guide. VMwareDRSandDPMToprovideautomaticloadbalancingofvirtual machinesamonghostsanddistributedpowermanagement,the VirtualCenter ServermusthaveaDRSandDPMlicensekeyforeachESX Server processorintheDRScluster.Asaprerequisite,DRSrequiresappropriateVMotion licensekeysforallhostsintheDRScluster.Foradescriptionofthisfeature,seethe ResourceManagementGuide.
VMware, Inc. 59
Per-Instance Licensing
Featuresthatarelicensedonaperinstancebasisrequireonlyonelicensekeyforeach featureinstance,regardlessofthenumberofprocessorsused.TheVirtualCenter Server iscurrentlytheonlyfeaturelicensedonaperinstancebasis.Forinformationabout differenteditionsofVirtualCenter,seeVirtualCenter ServerEditionsonpage 54.
License Expiration Considerations

WhentheFLEXnetlicenseserverexpiresalicense,theVIClientdoesnotdisplaya messagethatthelicenseisexpiringunlessyouusetheVIClienttomanageyourvirtual machines,forexampletopowerthemonorresetthem. ThemessageappearseverytimeyouusetheVIClienttoperformanoperationona virtualmachine.
License Server Availability

VMwareprovidesthefollowingmechanismsthathelppreventthelicenseserverfrom beingasinglepointoffailure.Thelicenseserveractsprimarilyasalicensedistribution mechanism.Ifyourlicenseserverbecomesunavailable,youcannotissueanynew licensestoenablenewhostsornewfeatures.However,alllicensedfunctionality currentlyoperatingatthetimethelicenseserverbecomesunavailablecontinuesto operateasfollows: AllVirtualCenterlicensedfeaturescontinuetooperateindefinitely,relyingona cachedversionofthelicensestate.Thisincludesnotonlybasic VirtualCenter Serveroperation,butlicensesforVirtualCenteraddons,suchas VMotionandDRS. ESX Serverlicensedfeatureshavea14daygraceperiodduringwhichhosts continueoperation,relyingonacachedversionofthelicensestate,evenacross reboots.Afterthegraceperiodexpires,certainESX Serveroperations,suchas poweringonvirtualmachines,becomeunavailable.
60
VMware, Inc.
DuringtheESX Servergraceperiod,whenthelicenseserverisunavailable,the followingoperationsareunaffected: Virtualmachinescontinuetorun.YoucanusetheVI Clienttoconfigureand operatevirtualmachines. ESX Serverhostscontinuetorun.YoucanconnecttoanyESX Serverhostinthe VirtualCenterinventoryforoperationandmaintenance.Connectionsto VirtualCenterremain.YoucanusetheVI Clienttooperateandmaintainvirtual machinesfromthehosteveniftheVirtualCenter Serverconnectionisalsolost. Duringthegraceperiod,restrictedoperationsinclude: AddingESX ServerhoststotheVirtualCenterinventory.Youcannotchange VirtualCenteragentlicensesforhosts. Addingorremovinghostsfromacluster.Youcannotchangehostmembershipfor thecurrentVMotion,HA,orDRSconfiguration. Addingorremovinglicensekeys. Whenthegraceperiodexpires,cachedlicenseinformationisnolongerstored.Asa result,virtualmachinescannolongerbepoweredon.Runningvirtualmachines continuetorunbutcannotberebooted. Whenthelicenseserverbecomesavailableagain,hostsreconnecttothelicenseserver. Norebootingormanualactionisrequiredtorestorelicenseavailability.Thegrace periodtimerisresetwheneverthelicenseserverbecomesavailableagain.
VMware, Inc.
61
Table 63displaysESX Serverlicensedoperationspermittedwhilethelicenseserveris unavailable.Operationsthatarenotpermittedareoperationsthatrequirethe acquisitionofnewlicensesfromthelicenseserver. Table 6-3. Permitted ESX Server Operations When the License Server Is Unavailable
During Grace Period Permitted Permitted Permitted Permitted Permitted Permitted Permitted Permitted Permitted NotPermitted After Grace Period Expires NotPermitted Permitted Permitted Permitted Permitted Permitted Permitted Permitted NotPermitted NotPermitted
Component Virtualmachine
Attempted Action Poweron Createanddelete Suspendandresume ConfigurevirtualmachinewithVI Client
ESX Serverhost
Continueoperations Poweronandpoweroff ConfigureESX ServerhostwithVI Client Modifylicensefileforsinglehostlicensing Restartvirtualmachineswithinthefailed hostsHAcluster Addorremovelicensekeys
62
VMware, Inc.
Table 64listsVirtualCenterlicensedoperationsthatarepermittedwhenthelicense serverisunavailable.Operationsthatarenotpermittedareoperationsthatrequirethe acquisitionofnewlicensesfromthelicenseserver. Table 6-4. Permitted VirtualCenter Operations When the License Server Is Unavailable
When License Server Is Unavailable Permitted NotPermitted Permitted Permitted Permitted Permitted NotPermitted Permitted Permitted Permitted NotPermitted
Component VirtualCenter Server
Attempted Action RemoveanESX Serverhostfrominventory(see nextentry) AddanESX Serverhosttoinventory ConnectandreconnecttoanESX Serverhostin inventory Moveapoweredoffvirtualmachinebetween hostsininventory(coldmigration) MoveanESX Serverhostamongfoldersin inventory MoveanESX Serverhostoutofa VMotionDRSHAcluster(seenextentry) MoveanESX Serverhostintoa VMotionDRSHAcluster ConfiguretheVirtualCenter Serverwith VI Client StartVMotionbetweenhostsininventory ContinueloadbalancingwithinaDRScluster Addorremovelicensekeys
CAUTIONIfyoureleaselicensesforlicensedfeatureswhilethelicenseserveris unavailable,thereleasedlicensescannotberedistributeduntilthelicenseserver becomesavailableagain.Forexample,ifyouremovethenetworkadapterassociated withVMotionwhilethelicenseserverisunavailable,thatVMotionlicenseisreleased andisunavailableuntilthelicenseserverisavailableagain.Removingahostfromthe VirtualCenterinventoryorremovingahostfromaclusterhasasimilareffect.
VMware, Inc.
63
VirtualCenterusesaheartbeatmechanismtocheckwhetherthelicenseserveris reachableandtoseeifthereareanychangesinthelicensefile.Theheartbeatintervalis fiveminutes.Therefore,itmighttakeVirtualCenteraslongasfiveminutestodetect licensechangesorifthelicenseserverhasbecomeunavailable. Whenthelicenseserverbecomesunavailable,orifachangeinthelicensefilecausesa checkedoutlicensetoberemoved,VirtualCentermarkstheaffectedlicensesas UnlicensedUse,andthelicensedfeaturescontinuetooperateaspreviously described.Whenthelicenseserverbecomesavailableagain,orwhenlicensesareadded tothelicensefileagain,VirtualCenterchecksoutthelicensesagainandrevertsthemto theLicensedstate.Ifalicensecannotbecheckedout,thelicenseremainsinthe UnlicensedUsestate. Iflicenseserveravailabilityisaparticularconcerninyourenvironment,considerone ofthefollowingstrategies: InstallthelicenseserveronthesamemachineastheVirtualCenter Server.Thisis thedefaultoptionthattheVirtualCenterinstallerprovides. Installthelicenseserveronavirtualmachine,andplacethatvirtualmachineinan HAcluster.VMwareHArestartsthelicenseservermachineonanotherESX Server hostincaseoffailure. UsesinglehostlicensefilesonESX Serverhosts.
Using an Existing FLEXnet License Server

Inmostcases,VMwarerecommendsinstallingthelicenseserveronthesamemachine astheVirtualCenter Server.However,ifyoualreadyhaveaFLEXnetlicenseserverin yourenvironmentprovidinglicensesforotherproducts,youmightwanttoinstallthe VMwarelicenseserveronthatsystem. TheVMwarelicenseserverissupportedonlyonWindowsoperatingsystems.You cannotinstalltheVMwarelicenseserveronaLinuxbasedFLEXnetserver.SeeLicense ServerRequirementsonpage 48. ToinstalltheVMwarelicenseserveronyourexistingFLEXnetserver,usethe standalonelicenseserverinstallerasdescribedinInstallingaLicenseServeron page 87.ThisinstallstheVMwarelicenseservervendordaemon,whichcancoexist withothervendordaemonsalreadyinstalledontheserver.
64
VMware, Inc.
Contacting Support
Ifyourequireassistancewithlicensing,contactVMwareforsupportasfollows: IfyoudidnotreceivelicenseactivationcodesforyourVI3purchaseorhave difficultiesinusingyourlicenseactivationcodestoobtainlicensefiles,email vihotline@vmware.com. Ifyouhavelicensefilesandhavedifficultyconfiguringortroubleshootinglicensed features,fileasupportrequestathttp://www.vmware.com/support.
VMware, Inc.
65
66
VMware, Inc.
Running VMware VirtualCenter and VMware ESX Server in Evaluation Mode
Thischapterprovidesinformationabouthowtoevaluateanupgradedlicenseof VirtualCenter 2.5andESX Serverversion3.5andhowtoobtainlicenseswhenthe evaluationmodeexpires.Thischaptercontainsthefollowingtopics: UsingEvaluationModeforESX Serveronpage 67 UsingEvaluationModeforVirtualCenteronpage 68 LicensingVirtualCenterandESX ServerAftertheEvaluationPeriodExpireson page 68
Using Evaluation Mode for ESX Server

ESX Server 3igenerallyincludesastandaloneeditionserialnumber.Youcanrun ESX Server 3iwiththepreinstalledserialnumber,purchaseandactivateanupgraded license,orevaluateanupgradedlicense.WhenyourunESX Server 3iinevaluation mode,intendedfordemonstrationandevaluationpurposes,yoursoftwareis completelyoperational,doesnotrequireanylicensingconfiguration,andprovidesfull functionalityofESX Serverfor60daysfromthetimeyoufirstactivatethesoftware. Duringthe60dayevaluation,thesoftwarenotifiesyouofthetimeremaininguntilthe evaluationmodeexpires.Theevaluationperiodcannotbepausedanditcannotbe restarted. IftheESXServer3ihostdoesnothaveaserialnumberpreinstalledatboottime,the hostbootsupinevaluationmode.
VMware, Inc.
67
Using Evaluation Mode for VirtualCenter

YoucanuseESX ServerwithoutVirtualCenter.However,ifyouhavemultiple ESX Serverhostsandyouwanttomanagethemcollectively,VMwarerecommendsthat youuseVirtualCenter.BeforepurchasingandactivatinglicensesforVirtualCenter 2.5, youcaninstallandrunVirtualCenterinevaluationmode.Whenruninevaluation mode,intendedfordemonstrationandevaluationpurposes,yoursoftwareis completelyoperationalimmediatelyafterinstallation,doesnotrequireanylicensing configuration,andprovidesfullfunctionalityofVirtualCenterfor60daysfromthe timeyoufirstinstallVirtualCenter.Duringthe60dayevaluation,thesoftwarenotifies youofthetimeremaininguntiltheevaluationmodeexpires.Theevaluationperiod cannotbepausedanditcannotberestarted.
Licensing VirtualCenter and ESX Server After the Evaluation Period Expires
Afterthe60dayevaluationperiodexpires,unlessyouobtainlicensesforyour software,youcannotperformmostoperationsinVirtualCenterandESX Server.For example,youcannotpoweronvirtualmachines,addnewhosts,oruseadvanced ESX ServerandVirtualCenterfeatures. IfyoudonotlicenseVirtualCenterbeforetheevaluationperiodexpires,allofthehosts intheVirtualCenterinventoryaredisconnected. NOTEReinstallingtheVirtualCenter Serverafterthe60dayevaluationexpiresdoesnt restartevaluationmode. Table 71detailstheESX Serverbehaviorafterevaluationmodeexpires.Theoperations thatarenotpermittedrequiretheacquisitionofnewlicenses. Table 7-1. ESX Server Operations After the 60-Day Evaluation Period
Component Virtualmachine Attempted Action Poweron Createanddelete Suspendandresume ConfigurevirtualmachinewiththeVI Client After 60 Days NotPermitted Permitted Permitted Permitted
68
VMware, Inc.
Chapter 7 Running VMware VirtualCenter and VMware ESX Server in Evaluation Mode
Table 7-1. ESX Server Operations After the 60-Day Evaluation Period (Continued)
Component ESX Serverhost Attempted Action Continueoperationsonexistinghosts Poweronandpoweroff ConfigureESX ServerhostwiththeVI Client Restartvirtualmachineswithinthefailed hostsHAcluster Addorremovelicensekeys After 60 Days Permitted Permitted Permitted NotPermitted Permitted
Considerations when Switching ESX Server and VirtualCenter to Licensed Modes

WhenyouswitchVirtualCenterandESX Serverfromevaluationmodetothelicensed mode,keepinmindthefollowingitems: IfthenumberofESX Serverhostsyouaddtoyourinventoryexceedsthenumber thatyourcurrentlicensingtypeallows,youcannotmanagetheexcesshosts.You candeletethemfromtheVirtualCenterinventoryorusetheVI Clienttodirectly accessthehostsandconfiguretheirlicensing. Makesureallrequiredlicensesareonyourlicenseserver.
VMware, Inc.
69
70
VMware, Inc.
Licensing VirtualCenter and ESX Server 3i
Thischapterprovidesproceduresforredeeminglicensefilesandconfiguringlicense options. Thischaptercontainsthefollowingsections: LicensingProcessonpage 72 ObtainingLicenseFilesonpage 75 SettingUpCentralizedLicensingonpage 75 SettingUpSingleHostLicensingonpage 80 LicenseFileContentsonpage 83 LicenseFileLocationsonpage 85 AddingNewLicenseFilestoLicenseServersonpage 85 AddingNewLicenseFilestoSingleHostsonpage 86 InstallingaLicenseServeronpage 87 TroubleshootingLicensingonpage 88
VMware, Inc.
71
Licensing Process
Figure 81summarizesthelicenseconfigurationprocessesforESX Server 3i. Figure 8-1. License Configuration Process for ESX Server 3i
Purchase the ESX Server 3i host
Power on the host
Yes
Preinstalled serial number?
No
ESX Server 3i host starts in evaluation mode
ESX Server 3i host is licensed as Standalone edition
Install the serial number
Yes
Did the hardware vendor enclose a serial number to install? No
Did you purchase an upgrade to a VI3 edition?
No
Continue running as Standalone edition
Continue running in evaluation mode
Yes See the hardware vendors instructions to activate
72
VMware, Inc.
Chapter 8 Licensing VirtualCenter and ESX Server 3i
Figure 82summarizesthelicenseconfigurationprocessesfortheVirtualCenter Server. Figure 8-2. License Configuration Process for VirtualCenter
Acquire VirtualCenter installer Purchase licenses
Evaluate VirtualCenter? Yes Run installer
No
Receive email from VMware or VMware partner
Follow email instructions to redeem licenses
Select Evaluation check box
Run installer
VirtualCenter 60-day evaluation
Deselect Evaluation check box
Install license server
Yes
Install license server?
No
Enter path to existing license server and VirtualCenter edition
Select license file that contains purchased licenses
(optional) Change license server configuration VirtualCenter is licensed
Copy purchased licenses to license directory
VMware, Inc.
73
AfteryoupurchaseVMwareInfrastructuresoftware,dothefollowingtoobtainanduse yourlicenses: 1 Decidewhichlicensetypetouse. ForESXServer3iStandaloneaddition,youcanuseahostbasedserialnumber. VI3 editionsofESXServerandVirtualCenteruseFLEXnetlicensing,whichoffers achoiceoflicensetypes:centralized,singlehost,ormixed.See VirtualCenterand ESX Server 3iLicensingModelonpage 54. 2 Registeryourpurchase. WhetheryoupurchasedVMwareInfrastructure3fromanauthorizedVMware resellerordirectlyfromVMware,youmustregisteryourpurchasetoyour VMwarestoreaccount.SeeObtainingLicenseFilesonpage 75. 3 Obtainlicensefiles. Afteryourpurchaseisregistered,usetheWebbasedlicenseactivationportalto generateanddownloadlicensefilesappropriatetothelicensetypeyouchosein Step 1.SeeObtainingLicenseFilesonpage 75. 4 5 InstallVirtualCenter. ConfigureyourlicensingaccordingtothelicensetypeyouchoseinStep 1: Toconfigurecentralizedlicensing,seeSettingUpCentralizedLicensingon page 75. Toconfigurelicensingforasinglehost,seeSettingUpSingleHost Licensingonpage 80. Toconfigureamixedlicenseenvironment,seeSingleHostandCentralized LicensingintheSameEnvironmentonpage 81.
74
VMware, Inc.
Obtaining License Files

Theprocessofobtaininglicensefilesvariesslightlydependingonhowyoupurchased VMwareInfrastructure3.Thefirststepinobtaininglicensefilesistoobtainoneormore licenseactivationcodes,whichyoureceiveinoneofthefollowingways: IfyoupurchasedVMwareInfrastructure3withyourESXServer3ienabled machinefromanauthorizedVMwarereseller,suchasDell,HewlettPackard,or IBM,youreceiveanemailmessagecontaininginstructionsonhowtoredeemand activateyourlicenses.Entereithertheserialnumberorapartneractivationcode intothepartneractivationportaltoregisteryourpurchase. ForothernewpurchasesofVMwareInfrastructure3,youreceiveanemailthat containsalicenseactivationcode. Whenyoureceivetheemailthatcontainsyouractivationcodes,followtheinstructions intheemailtoregisterlicenseactivationcodesandgeneratelicensefilesthroughthe Webbasedlicenseactivationportal. SeethelicenseactivationportalonlineHelp.
Setting Up Centralized Licensing

Youcanconfigurecentralizedlicensingatinstallationtime.Afterinstallation,youcan makechangestolicensingthroughtheVI Client.
Installing License Files

Afteryouobtainyourlicensefiles,savethemasASCIItextfilesinadirectoryyoucan accessfromyourlicenseservermachine.Usethe.licextensionwhensavingyour licensefiles.Thefileextension.licisrequired. WhenyouinstalltheVMwarelicenseserver,youcanthenimportthelicensefilesinto yourlicenseserver.Centralizedlicensefilesareplacedatthefollowingdefaultlocation onthemachinerunningthelicenseserver:
C:\Program Files\VMware\VMware License Server\Licenses
Forinstructionsregardingtherecommendedlicenseserverinstallation,see ConfiguringCommunicationBetweenVirtualCenterComponentsonpage 103. Forinstructionsoninstallingastandalonelicenseserver,seeInstallingaLicense Serveronpage 87.
VMware, Inc.
75
Location of the License Server

VMwarerecommendsthatyoufollowthedefaultinstallationandplaceyourlicense serveronthesamemachineasyourVirtualCenter Server.Thislocationhasthe advantageofsimplicityofsetup,aswellasguaranteeingVirtualCentertolicense servercommunications.Changethisonlyifyouhaveagoodreason,suchasanexisting FLEXnetlicenseserver. Toaccessthelicenseserverdocumentation,chooseStart>Programs>VMware> VMware License ServerandselecttheVMwareLicenseServerUserGuide.
Configuring Centralized Licensing

Thefirstprocedureinthissectiondescribestheconfigurationforcentralizedlicensing. IfyourenvironmentusesthedefaultVirtualCenterinstallation,orifyouhaveno VirtualCenter Server,godirectlytoToconfigurecentralizedlicensingforan ESX Serverhostonpage 77. To configure centralized licensing for VirtualCenter 1 2 3 4 FromtheVI Client,chooseAdministration>VirtualCenterManagementServer Configuration. ClickLicenseServerinthelistontheleft. ClickUsetheFollowingLicenseServer. Enterthemachinenameand,optionally,aport. Ifyoudonotspecifyaport,thedefaultport,27000,isused. Forexample,withthedefaultlicenseserverport27000onalicenseservercalled license,yourentrymightlooklikethis:
license.vmware.com:27000
IfyouwanttochangetheVirtualCenterServeredition,selectoneofthefollowing: VCFoundationEdition VCFullEdition FormoreinformationontheVirtualCentereditions,seeVirtualCenter Server Editionsonpage 54.
76
VMware, Inc.
(Optional)IfyoudonotwantVirtualCentertooverridethehostscurrentlicense setting,deselectChangehostlicenseserversettingstomatchVirtualCenters settingwhentheyareaddedtoinventory. SelectingthischeckboxcausesVirtualCentertooverridethehostscurrentlicense settingandinsteadusethelicenseserverthatVirtualCenteruses.
ClickOKtosaveyourchanges. Youdonotneedtochangeanyothersettingstoenablecentralizedlicensing.
Thetotalnumberoflicensesconsumedandavailableonthelicenseserverare summarizedontheLicensestabintheAdminviewoftheVI Clientconnectedto VirtualCenter.ThistabwaslabeledLicenseViewerinearlierversionsof VirtualCenter. NOTEIfyoudidnotselectthecheckboxfortheoptionalsetting,seeToconfigure centralizedlicensingforanESX Serverhostonpage 77tomanuallyconfigure ESX Serverhoststousecentralizedlicensing. To configure centralized licensing for an ESX Server host 1 2 3 4 FromtheVI Client,selectthehostintheinventory. ClicktheConfigurationtab. UnderSoftware,clickLicensedFeatures. Tosetthelicenseserver: a b ClickEdittotherightofLicenseSources. ClickUseLicenseServer. Thisisthedefaultconfiguration. c EntertheportnumberandlicenseservermachinenameintheAddressfield, asinport@host. Forexample,withthedefaultlicenseserverport27000onalicenseserver calledlicense1,yourentrymightlooklikethis:
27000@license-1.vmware.com
ClickOKtoclosethedialogboxandsaveyourchanges.
VMware, Inc.
77
SettheESX Serveredition: a b ClickEdittotherightofESX ServerLicenseType. Specifytheeditionforthehost,orselectUnlicensedtoreleasethishosts licensesbacktothelicenseserver.TheESX ServerLicenseTypedialogbox displaysonlythoseeditionsthatareavailabletoyourESX Serverhost. ClickOKtoclosethedialogboxandsaveyourchanges.
c 6
Toconfigureaddonlicenses: a b ClickEdittotherightofAddOns. SelecttheaddonproductstouseandclickOK.
Thetotalnumberoflicensesconsumedandavailableonthelicenseserverare summarizedontheLicensestabintheAdminviewoftheVI Clientconnectedto VirtualCenter.ThistabwaslabeledLicenseViewerinearlierversionsof VirtualCenter. To configure local license server licensing for VirtualCenter 1 2 3 4 FromtheVI Client,chooseAdministration>VirtualCenterManagementServer Configuration. ClickLicenseServerinthelistontheleft. ClickUselicenseservicesonthisVirtualCenter Server. IfyouwanttochangetheVirtualCenterServeredition,selectoneofthefollowing: VCFoundationEdition VCFullEdition FormoreinformationontheVirtualCentereditions,seeVirtualCenter Server Editionsonpage 54. 5 (Optional)IfyoudonotwantVirtualCentertooverridethehostscurrentlicense setting,deselectChangehostlicenseserversettingstomatchVirtualCenters settingwhentheyareaddedtoinventory. SelectingthischeckboxcausesVirtualCentertooverridethehostscurrentlicense settingandinsteadusethelicenseserverthatVirtualCenteruses. MakesurethatyouuseanIPaddressthatisaccessiblefromtheESX Serverhost. IfyouconfigureVirtualCentertousealocallicenseserverandthehostnameofthe locallicenseserver(theVirtualCenterhost)isnotresolvablefromtheESX Server host,thentheESX Serverhostcannotacquirelicensesfromthelocallicenseserver.
78
VMware, Inc.
ClickOKtosaveyourchanges. Youdonotneedtochangeanyothersettingstoenablelocallicenseserver licensing.
Thetotalnumberoflicensesconsumedandavailableonthelicenseserverare summarizedontheLicensestabintheAdminviewoftheVI Clientconnectedto VirtualCenter.ThistabwaslabeledLicenseViewerinearlierversionsof VirtualCenter. NOTEIfyoudidnotselectthecheckboxfortheoptionalsetting,seeToconfigure centralizedlicensingforanESX Serverhostonpage 77tomanuallyconfigure ESX Serverhoststousecentralizedlicensing.
Default License Server Ports

Bydefault,VirtualCenterandESX Serversoftwareisconfiguredtousethe27000and 27010TCP/IPportstocommunicatewiththelicenseserver.ForESXServer3i,youneed tousethedefaultportnumbersforthelicenseserver.
Changing from Single-Host to Centralized Licensing

YoucanchangeyourESX Serverhostsfromsinglehostlicensingtocentralized licensing.Todothis,youmustgenerateanewlicensefile,installalicenseserver(ifyou donothaveoneinstalled),andconfigureyourhoststousethenewlicensetype. To change ESX Server hosts from single-host licensing to centralized licensing 1 UsetheVMwarelicenseactivationportaltogenerateanddownloadacentralized licensefilethatcontainsthelicensesforyourESX Serverhostsandanyassociated VirtualCenter Serverfeatures.Thelicenseactivationportalletsyougenerate singlehostandcentralizedlicensefilesfromthesamelicenseactivationcode. Ifyoudidnotalreadyinstallalicenseserver,dosoasfollows: ToinstallalicenseserveraspartofaVirtualCenterinstallation,seeChapter 9, InstallingVMwareInfrastructureManagement,onpage 93. Toinstallastandalonelicenseserver,seeInstallingaLicenseServeron page 87. TouseanexistingFLEXnetlicenseserveralreadyinstalledinyour environment,seeUsinganExistingFLEXnetLicenseServeronpage 64. 3 ConfigureyourVirtualCenter ServerandESX Serverhostsasdescribedin ConfiguringCentralizedLicensingonpage 76.
VMware, Inc.
79
Setting Up Single-Host Licensing

Therearetwoscenariosforsinglehostlicensing: HostbasedserialnumberFortheESXServer3iStandaloneedition,eachhost hasaserialnumberthatissuppliedbythehardwarevendorandistypically preinstalled.Iftheserialnumberisnotpreinstalled,itmightbeenclosedona stickeroracard. HostbasedlicensefileForallotherESXServer3ieditionsincludingVI3 Foundation,VI3Standard,andVI3 Enterpriseeachhosthasalicensefile.
Configuring an ESX Server 3i Machine to Use a Host-Based Serial Number

IfyoureceiveanESX Server 3iserialnumberfromyourhardwarevendor,youcanuse theVI Clienttoinstalltheserialnumber. To use the VI Client to install a host-based serial number 1 2 3 4 5 6 7 FromtheVI Client,selectthehostintheinventory. ClicktheConfigurationtab. UnderSoftware,clickLicensedFeatures. ClickEdittotherightofLicenseSources. ClickUseSerialNumber. Entertheserialnumber. ClickOKtosaveyourchanges.
Configuring an ESX Server Machine for Host-Based Licensing

HostbasedlicensingrequiresavalidlicensefileoneachESX Serverhost. Whenyoureceiveyourlicensefile,renameittovmware.licandplaceitonafilesystem youcanaccessfromyourVI Client.Thefileextension.licisrequired. To use the VI Client to configure host-based licensing 1 2 3 4
80
FromtheVI Client,selectthehostintheinventory. ClicktheConfigurationtab. UnderSoftware,clickLicensedFeatures. ClickEdittotherightofLicenseSources.

VMware, Inc.
5 6
ClickUseHostLicenseFile. ClickBrowseandlocatethelicensefile. Thisfilemustbelocatedontheclientmachine,notontheESX Serverhost. Files musthavea.licextensiontoappearinthefilebrowser.
ClickOKtosaveyourchanges.
Single-Host and Centralized Licensing in the Same Environment

UsingsinglehostlicensesforESX Serverfeaturesandcentralizedlicensingfor VirtualCenterfeaturesinthesameenvironmentispermitted.Doingsorequires changestothedefaultVirtualCenterconfigurationsettings.Ifyoudonotchangethe VirtualCentersettings,thesettingscanoverridesinglehostlicensefiles: WhenVirtualCenterrestarts WhenthesinglehostESX Servermachinesareaddedtoinventoryagain AnysinglehostlicensefileontheESX Servermachineremainsunchangedbutignored. CAUTIONIfyourestoreanESX Servermachinetosinglehostlicensingwithout changingtheVirtualCenterdefaultconfiguration,VirtualCentersettingsmight overridethesinglehostsettingsontheESX Servermachine. TheESXServer3iStandaloneeditionisnotlicensedforVirtualCentermanagement. ThismeansthatthecombinationofserialnumberhostlicensingandVirtualCenter managementisnotanoption. To change VirtualCenter settings to allow single-host ESX Server licensing 1 2 3 4 5 FromtheVI Client,chooseAdministration>ServerSettings. ClickLicenseServerinthelistontheleft. DeselectthecheckboxforChangehostlicenseserversettingstomatch VirtualCenterssettingwhentheyareaddedtoinventory. ClickOKtosaveyourchanges. RemoveandAddanyaffectedESX Servermachineintheinventory.
NowitissafetoreconfiguresinglehostlicensingonanychangedESX Server machines.SeeConfiguringanESX ServerMachineforHostBasedLicensingon page 80.
VMware, Inc.
81
Configuring Licensing for a Mixed ESX Server 2.x and ESX Server 3.x Environment
YoucanusetheVirtualCenter Server2.xtomanageamixedenvironmentofboth ESX Server2.xandESX Server3.xhosts.Youreceivelicenseactivationcodeswith purchasesofVMwareInfrastructure3.Youcanredeemthecodesforboth ESX Server 2.xserialnumbersandVMwareInfrastructure3licensefiles. To configure licensing for the ESX Server 2.x hosts in the mixed environment 1 2 LeavethelicensingunchangedonexistingESX Server2.xhoststhatuseserial numbers. FornewESX Server2.xinstallations,redeemyourlicenseactivationcodesonthe licenseactivationportalforESX Server2.xserialnumbers. Providetheseserialnumbersatthetimeofinstallationorconfiguration. 3 Redeemyourlicenseactivationcode(s)togenerateacentralizedlicensefilethat containslicensesforVirtualCenter Server,VirtualCenterManagementAgents, VMotion,andESX Server3.x. Ifnecessary,combinemultiplegeneratedlicensefilestoproduceasinglefile. YourgeneratedlicensefilecanincludeESX Serverversion3.xlicensesforthe ESX Serverversion2.xhoststhatyouobtainedESX Server2.xserialnumbersforin Step 2.Thisletsyoueasilydistributelicensestothesehostsiftheyarelater upgradedtoESX Server3.x. 4 InstallandconfiguretheVirtualCenter Server2.xtousethelicenseserver.
ForinformationaboutinstallingVirtualCenter,seeChapter 9,InstallingVMware InfrastructureManagement,onpage 93.
Changing from Centralized to Single-Host Licensing

YoucanchangeyourESX Serverhostsfromcentralizedlicensingtosinglehost licensing.VirtualCenterandadditionalfeaturessuchasVMotion,VMwareDRS,and VMwareHAmusthavecentralizedlicensing.Tochangethelicensetypeforyour ESX Serverhosts,youmustgeneratenewlicensefilesforeachhostandconfigurethe hoststousethenewlicensetype.
82
VMware, Inc.
To change ESX Server hosts from centralized licensing to host-based licensing 1 UsetheVMwarelicenseactivationportaltogenerateanddownloadnew singlehostlicensefilesforeachESX Serverhost. Thelicenseactivationportalletsyougeneratebothsinglehostandcentralized licensefilesfromthesamelicenseactivationcode.Forhostbasedlicensing,you needonelicensefileforeachESX Serverhost. 2 IfyouareusingVirtualCenter,changeyourVirtualCenter Serversettingssothat VirtualCenterdoesnotoverridehostlicensesettings,asdescribedinSingleHost andCentralizedLicensingintheSameEnvironmentonpage 81. ConfigureyourESX ServerhostasdescribedinConfiguringanESX Server MachineforHostBasedLicensingonpage 80.
License File Contents

Bothcentralizedandsinglehostoperationrequirelicensefiles.LicensefilesareASCII textfilesthatcontaintwotypesofinformation:thelicensetypeandlicensekeys. LicensetypesectionSpecifiestheTCP/IPportsthatusethelicenseserverto communicatewithESX Serverhosts.VMwarerecommendsthatyounotmodify thesedefaultports.Ifyoudoneedtochangetheports,useanASCIItexteditorand validateyoureditedlicensefileathttp://www.vmware.com/checklicense/. Alicensetypeheaderlookssimilartothefollowing:
SERVER this_host ANY 27000 VENDOR VMWARELM port=27010 USE SERVER
Thissectionappearsonlyinalicenseserverfileandindicatesthatlicensekeys shouldbeservedonalicenseserver.Singlehostlicensefileshavenotypesection. LicensekeysectionContainsencryptedlicensekeys,oneforeachfeatureto whichyouareentitled.Table 81liststheavailablelicensekeys. Table 8-1. License Keys

Feature Name ESX ServerFoundationedition ESX ServerStandardedition ESX ServerEnterpriseedition VMwareConsolidatedBackup VirtualCenter ServerFoundation License File Key PROD_ESX_STARTER PROD_ESX_FULL ESX_FULL_BACKUP PROD_VC_EXPRESS License Type Available Centralizedorsinglehost Centralizedorsinglehost Centralizedorsinglehost Centralizedonly
VMware, Inc.
83
Table 8-1. License Keys (Continued)

Feature Name VirtualCenter Server VirtualCenterManagementAgent VMwareServerVMotion VMwareStorageVMotion VMwareDRS VMwareDPM VMware HA License File Key PROD_VC VC_ESXHOST VC_VMOTION VC_DRS VC_DAS License Type Available Centralizedonly Centralizedonly Centralizedonly Centralizedonly Centralizedonly
Centralizedfilesandsinglehostfilescanbedifferentiatedbythefollowing distinguishingfeatures: Singlehostlicensefilescontainnolicensetypesection.Centralizedfilescontaina licensetypesectionasthefileheader. SinglehostlicensefilescontainthestringlicenseType=Hostaspartofeach licensekeyblockinthefile.Centralizedlicensefilescontainthestring licenseType=Serveraspartofeachlicensekeyblockinthefile,asshowninthe followingexamples. Example 81showsatypicalsinglehostlicensekey. Example 8-1. Single-Host License Key
INCREMENT PROD_ESX_FULL VMWARELM 2005.05 31-dec-2008 uncounted \ VENDOR_STRING="licenseType=Host;vmodl=esxFull;desc=ESX Server \ Enterprise;capacityType=cpuPackage;gp=14;exclude=BACKUP;count=8" \ HOSTID=ANY ISSUED=06-AUG-2007 \ NOTICE="FulfillmentId=777;Name=VMware Internal" TS_OK \ SIGN="095A 14A7 ..."
Example 82showsatypicalcentralizedlicensekey. Example 8-2. Centralized License Key

INCREMENT PROD_ESX_FULL VMWARELM 2005.05 31-dec-2008 8 \ VENDOR_STRING="licenseType=Server;vmodl=esxFull;desc=ESX Server \ Enterprise;capacityType=cpuPackage;gp=14;exclude=BACKUP" \ ISSUED=06-AUG-2007 NOTICE="FulfillmentId=1201;Name=VMware \ Internal" TS_OK SIGN="1F7F 98D5 ..."
84
VMware, Inc.
License File Locations

AlicensefileresidesoneveryESX Servermachineoreverylicenseserver,depending onwhetheryouusecentralizedorhostbasedlicensing: Centralizedlicensefilesareplacedatthefollowingdefaultlocationonthe machinerunningtheVMwarelicenseserver:
NOTEInVirtualCenter 2.0,thedefaultlocationofthelicensefilewas C:\Documents and Settings\All Users\Application Data\VMware\ VMware License Server\vmware.lic.Thislocationnolongerexists. Youcanaddnewlicensefilestothelicensedirectory.SeeAddingNewLicense FilestoLicenseServersonpage 85. Singlehostlicensefilesareplacedatthefollowingdefaultlocationonthe machinerunningESX Server.
/etc/vmware/vmware.lic
NOTEIncentralizedlicensing,thisfileexistsontheESX Servermachine,but containsnolicensekeys. Youcanaddnewlicensestothesinglehostbyusingthelicenseactivationportal. SeeAddingNewLicenseFilestoSingleHostsonpage 86.
Adding New License Files to License Servers

Thelicenseserversupportsalicensedirectoryformultiplelicensefiles.Ifyouobtained multiplelicensefiles(forexample,fromseparateorders)andyouwanttomanageall oftheselicensesfromthesamelicenseserver,addthemtothelicenseserverdirectory andthenrestarttheserver. To add new licenses to the license server directory 1 Addthenewlicensefiletothefollowingdefaultdirectoryonthemachinerunning theVMwarelicenseserver:
RestarttheVMwareLicenseServerservice.
ThefollowingprocedureisforWindows2000Professional.Themenusandcommands forotherversionsofWindowscanvary.
VMware, Inc.
85
To restart the license server Windows Service 1 2 3 4 ChooseStart>Settings>ControlPanel. DoubleclickAdministrativeTools. DoubleclickServices. Scrolldown,rightclickVMwareLicenseServer,andchooseRestart.
Youcanchangethedefaultlocationofyourcentralizeddirectory,oryourlicensefile. To change the default location of the license directory 1 2 3 Onthecomputerthatrunsthelicenseserverapplication,chooseStart>Programs >VMware>VMwareLicenseServer>VMwareLicenseServerTools. ClicktheConfigServicestab. ClickBrowsenexttothePathtolicensefilefield,andchoosealicensefilefrom thelicensedirectory. Ifyouwantthelicenseservertousetheentirelicensedirectory,manuallyremove thenameofthefile,leavingonlythenameofthedirectory. 4 5 6 7 ClicktheStart/Stop/Rereadtab. ClickStop. ClickStart. ClickReReadLicenseFiletoloadthenewlicensefiles.
Adding New License Files to Single-Hosts

Hostbasedlicensingdoesnotsupportamultiplelicensefiledirectory.Ifyouhave multiplelicensefiles,youneedtocombinethemintoasinglelicensefilebyusingthe licenseactivationportal.Forexample,youcanaddnewlypurchasedlicensestoan existinglicensefile,orcombineentitlementsfromtwoseparatepurchasesintoasingle licensefile.Youcancombineevaluationlicensesandproductionlicensesinasinglefile, butproductsmightrequireconfigurationchangeswhentheevaluationlicensesexpire. YoucancombinethefilesbyusingtheVMwareWebbasedlicenseactivationportal. Forexample,youcancombinetwoESX Serverlicensefilesintoasinglelicensefile. See ObtainingLicenseFilesonpage 75.
86
VMware, Inc.
Installing a License Server

Thissectiondescribesanindependentinstallationofthelicenseserver.Youcanskip thissectionifyouareusingtheVMwareInfrastructureManagementInstaller,as describedinInstallingVMwareInfrastructureManagementSoftwareonpage 99. TheVMwareInfrastructureManagementInstallerinstallsalicenseserver. Tocheckwhetheralicenseserverisalreadyinstalled,chooseStart>Programs> VMwareandlookforVMwareLicenseServer.Ifalicenseserverisinstalled,VMware recommendsreinstallingorupgradingthelicenseservertothelatestversion. Youcanusethefollowingprocedurewithanyinstallationtohaveastandalonelicense serveronamachineotherthanyourVirtualCenter Serverhost. YoucaninstallthelicenseserveronthesamemachinewheretheVirtualCenter Server residesoronaseparatemachine.Toensurethebestpossiblelicensepoolavailability, VMwarerecommendsinstallingthelicenseserveronthesamemachinewherethe VirtualCenter Serverresides. ToinstalltheVMwarelicenseserversoftware,youmusthave: HardwarethatmeetsVMwareInfrastructureSystemRequirementsonpage 45 AstaticIPaddressormachinenamethatyourlicenseservercanuse ThefollowingprocedureassumesthatyouhaveAdministratorprivilegesona Windowssystem. To install a VMware license server 1 InserttheVMwareInfrastructureInstallationCD. IftheVMwareInfrastructureManagementInstallerappears,clickcanceltoexit. 2 3 4 5 6 Navigatetothe\vpxfolderontheinstallationCDanddoubleclick VMwarelicenseserver.exe. VerifythatyouareinstallingthelicenseserverandclickNext. Toacceptthelicenseagreement,selectIacceptthetermsinthelicenseagreement andclickNext. SelectthefolderinwhichyouwanttoinstallthelicenseserverandclickNext. TypethefullpathtoyourlicensefileorclickBrowsetolocatethisfileandclick Next. Thelicensefileshouldbelocatedinadirectoryyoucanaccessfromyourlicense servermachine.
VMware, Inc.
87
7 8
ClickInstalltobegintheinstallation. ClickFinishtocompletethelicenseserverinstallation.
Afteryouinstallthelicenseserver,youcanaccessdetailedinformationaboutusingand configuringtheserverbyclickingStart>Programs>VMware>VMwareLicense ServerandselectingtheVMwareLicenseServerUserGuide.
Troubleshooting Licensing
Thissectionprovidesguidelinesfortroubleshootingyourlicensesetup.Ifyouarenot abletoresolveyourproblemswithlicensingbyusingtheinformationgiveninthis section,contactVMwareforsupportasfollows: IfyoudidnotreceivelicenseactivationcodesforyourVI3purchaseorhave difficultiesinusingyourlicenseactivationcodestoobtainlicensefiles,email vihotline@vmware.com. Ifyouhavelicensefilesandhavedifficultiesinconfiguringortroubleshooting licensedfeatures,fileasupportrequestathttp://www.vmware.com/support.
Receiving License Activation Codes

VMwaresendslicenseactivationcodesandlicensinginformationtothelicense administratorlistedforaparticularpurchase.Ifyouarenotthelicenseadministrator, contactyourorganizationslicenseadministratorforyourlicenseactivationcodes. Ifyouneedtochangethelicenseadministratorforyourorder,contact vihotline@vmware.com.Includetherelevantordernumbersinyouremail. IfyoupurchasedVMwareInfrastructure3fromanauthorizedVMwarereseller,you mustregisteryourpurchasebyusingthepartneractivationcode(s)suppliedbythe partnertogenerateyourlicensefiles.
Checking the License Server

Ifyouarehavingtroublecommunicatingwithyourlicenseserver,checkthefollowing: ThelicenseserverWindowsserviceisrunning. Thelicenseserverislistening. Thelicenseserverstatus.
88
VMware, Inc.
To check that the license server Windows service is running 1 2 3 Onthemachineonwhichthelicenseserverisinstalled,chooseStart>Control Panel>AdministrativeTools>ServicestodisplaytheServicescontrolpanel. VerifythattheStatuscolumnfortheVMwareLicenseServerentryreadsStarted. IftheVMwareLicenseServerisnotstarted,startitbyrightclickingontheservice andchoosingStart.
To check that the license server is listening 1 2 3 Onthemachineonwhichthelicenseserverisinstalled,chooseStart>Command Prompt. Typenetstat -abatthecommandline. Verifythatthelmgrd.exeprocessislisteningonport27000andthatthe VMWARELM.exeprocessislisteningonport27010. Ifnot,thelicenseservermightnotbeinstalledormightnotbestarted.
VMware, Inc.
89
To check the license server status 1 Onthemachineonwhichthelicenseserverisinstalled,chooseStart>Programs> VMware>VMwareLicenseServer>VMwareLicenseServerToolstolaunchthe LMTOOLSutility. ClicktheServerStatustabtodisplaytheServerStatuspage. ClickPerformStatusInquiry. Licenseserverinformation,includingthelocationofthelicensefile,appearsatthe bottomofthepage.
2 3
Checking the License File

Ifyourlicenseserverisoperatingproperly,orifyouareusinghostbasedlicensing,but youstillcannotuselicensedfeatures,yourlicensefilemighthaveaproblem.Checkthe following: Validateyourlicensefileathttp://www.vmware.com/checklicense/. Ensurethatyouareusingthecorrecttypeoflicensefile.Ifyouareusingalicense server,useacentralizedfile.Ifyouareusinghostbasedlicensing,makesurethat youareusingasinglehostlicensefileoneachhost. Filesforcentralizedlicensingcontainablockofheadertextatthetop,andthe stringVENDOR_STRING=licenseType=Serverappearsineachlicensekeyinthe file.Singlehostlicensefileshavenoheadertext,andthestring VENDOR_STRING=licenseType=Hostappearsineachlicensekeyinthefile. Ifyouareusingacentralizedlicensefile,checkthatthelicensetypeheader informationappearsonlyonce,atthetopofthefile. Checkthatthelicensefilecontainsthecorrectkeysforthefeaturesyouwanttouse. Foralistofkeys,seeTable 81,LicenseKeys,onpage 83. Ifyoueditedthelicensefile,checkthatyoudidnotmixcentralizedandsinglehost keysinasinglefile.
90
VMware, Inc.
Checking License Configuration

Ifyourlicenseserver(ifused)appearstobeworkingcorrectly,andyourlicensefileis correct,usetheVI Clienttocheckthatyoucorrectlyconfiguredlicensingforyourhosts: Ifyouareusingcentralizedlicensing,followtheinstructionsinConfiguring CentralizedLicensingonpage 76. Ifyouareusingsinglehostlicensing,followtheinstructionsConfiguringan ESX ServerMachineforHostBasedLicensingonpage 80.
VMware, Inc.
91
92
VMware, Inc.
Installing VMware Infrastructure Management
ThischapterdescribeshowtoprepareyourVirtualCenterdatabase,installVMware InfrastructureManagementsoftware,andconfigurecommunicationbetween components.YoucaninstallVMwareInfrastructureManagementsoftwareona physicalsystemoronavirtualmachinerunningonanESX Serverhost. Thischaptercontainsthefollowingtopics: PreparingtheVirtualCenter ServerDatabaseonpage 93 InstallingVMwareInfrastructureManagementSoftwareonpage 99 ConfiguringCommunicationBetweenVirtualCenterComponentsonpage 103 UninstallingVMwareInfrastructureComponentsonpage 105 InstallingVirtualCenteronaVirtualMachineonpage 106
Preparing the VirtualCenter Server Database

ToinstallVirtualCenter,youmustalsoinstalladatabase.VirtualCenter Serverrequires adatabasetostoreandorganizeserverdata.VirtualCenterversion2.5supportsOracle, SQLServer,andMicrosoftSQLServer2005Express. TheVirtualCenter Serverrequiresadministrationcredentials(IDandpassword)tolog intoanOracleorSQLdatabase.ContactyourDBAforthesecredentials,orinstallthe bundledMicrosoftSQLServer2005Expressdatabaseforsmallerdeployments. NOTEMicrosoftSQLServer2005Expressissupportedonlyforsmalldeployments withupto5hostsand50virtualmachines.
VMware, Inc.
93
Configuring Your VirtualCenter Database

Thissectiondiscussesconfigurationrequirementsforallsupporteddatabases.
Configuring an Oracle Connection to Work Locally

TouseanOracledatabaseasyourVirtualCenterdatabaseandhaveVirtualCenter accessthedatabaselocally,usethefollowingprocedure. Beforeyoubeginthisprocedure,reviewtherequireddatabasepatchesspecifiedin Table 51,SupportedDatabaseFormats,onpage 47.Ifyoudonotprepareyour databasecorrectly,theVirtualCenterinstallermightdisplayerrorandwarning messages. To prepare an Oracle database to work locally with VirtualCenter 1 FromtheOracledatabasemachine,installandprepareOracle: a b c d 2 DownloadOracle9iorOracle10gfromtheOracleWebsite,installit,and createadatabase(VirtualCenter). DownloadOracleODBCfromtheOracleWebsite. InstalltheOracleODBCcorrespondingdriverthroughtheOracleUniversal Installer(directionsareprovidedwiththedriver). Increasethenumberofopencursorsforthedatabase.Addtheentry open_cursors = 300totheC:\Oracle\ADMIN\VPX\pfile\init.orafile.
ConnectOraclelocally: a CreateanewtablespacespecificallyforVirtualCenterbyusingthefollowing SQLstatement:

CREATE TABLESPACE "VPX" DATAFILE 'C:\Oracle\ORADATA\VPX\VPX.dat' SIZE 1000M AUTOEXTEND ON NEXT 500K;
Createauser,suchasvpxAdmin,foraccessingthistablespacethroughODBC:
CREATE USER vpxAdmin IDENTIFIED BY vpxadmin DEFAULT TABLESPACE vpx;
94
VMware, Inc.
Chapter 9 Installing VMware Infrastructure Management
Eithergrantdbapermissiontotheuser,orgrantthefollowingpermissionsto theuser:
grant grant grant grant grant grant grant grant connect to <user> resource to <user> create view to <user> create any sequence to <user> # For VirtualCenter upgrade only create any table to <user> # For VirtualCenter upgrade only execute on dbms_job to <user> execute on dbms_lock to <user> unlimited tablespace to <user> # To ensure space limitation is not an issue
CreateanODBCconnectiontothedatabase.Thefollowingareexample settings:
Data Source Name: VMware VirtualCenter TNS Service Name: VPX User Id: vpxAdmin
Configuring an Oracle Connection to Work Remotely

TouseanOracledatabaseasyourVirtualCenterdatabaseandhaveVirtualCenter accessthedatabaseremotely,usethefollowingprocedure. Beforeyoubeginthisprocedure,reviewtherequireddatabasepatchesspecifiedin Table 51,SupportedDatabaseFormats,onpage 47.Ifyoudonotprepareyour databasecorrectly,theVirtualCenterinstallermightdisplayerrorandwarning messages. To prepare an Oracle database to work remotely with VirtualCenter 1 2 InstalltheOracleclientontheVirtualCenter Servermachine. ConnecttoOracleremotely: a b DownloadandinstalltheODBCdriver. Editthetnsnames.orafilelocatedatOra9Ior10g,asappropriate:
C:\Oracle\Oraxx\NETWORK\ADMIN
Inthisexample,xxiseither 9Ior10g.
VMware, Inc.
95
UsetheNet8ConfigurationAssistanttoaddthefollowingentry:
VPX = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS=(PROTOCOL=TCP)(HOST=vpxd-Oracle)(PORT=1521)) ) (CONNECT_DATA = (SERVICE_NAME = VPX) ) ) HOST =
Inthisexample,HOSTisthemanagedhosttowhichtheclientneedstoconnect.
Configuring a SQL Server ODBC Connection

WhenyouinstallVirtualCenter,youcanestablishaconnectionwithaSQLServer database.ThefollowingproceduredescribeshowtoconfigureaSQLServerODBC connection. ForspecificinstructionsabouthowtoconfiguretheSQLServerODBCconnection,see yourMicrosoftSQLODBCdocumentation. IfyouuseSQLServerforVirtualCenter,donotusethemasterdatabase. NOTEMicrosoftWindowsNTauthenticationisnotsupportedwithremoteSQL Server. Beforeyoubeginthisprocedure,reviewtherequireddatabasepatchesspecifiedin Table 51,SupportedDatabaseFormats,onpage 47.Ifyoudonotprepareyour databasecorrectly,theVirtualCenterinstallermightdisplayerrorandwarning messages. To prepare a SQL Server database to work with VirtualCenter 1 OnyourMicrosoftSQLServer,performthefollowingtasks: a b CreateaSQLServerdatabasebyusingEnterpriseManagerontheSQLServer. CreateaSQLServerdatabaseuserwithdatabaseoperator(DBO)rights. ThedefaultdatabasefortheDBOuseriswhatyoudefinedinStep a. Makesurethedatabaseuserhaseitherasysadminserverroleorthe db_ownerfixeddatabaseroleontheVirtualCenterdatabaseandtheMSDB database.(SEEUPDATE)Thedb_ownerroleontheMSDBdatabaseisrequired forinstallationandupgradeonly.Thisrolecanberevokedafterthe installationorupgradeprocessiscompleted.
96 VMware, Inc.
2 3 4 5
OnyourVirtualCenter Server,opentheWindowsODBCDataSource Administrator. ClickSettings>ControlPanel>AdministrativeTools>DataSources(ODBC). ClicktheSystemDSNtab. TomodifyanexistingSQLServerODBCconnection: a b SelecttheappropriateODBCconnectionfromtheSystemDataSourcelist. ClickConfigure. ProceedwithStep 7.
TocreateaSQLServerODBCconnection: a b ClickAdd. ForSQLServer2000,selectSQLServerandclickFinish. ForSQLServer2005,selectSQLNativeClientandclickFinish.
TypeanODBCdatastorename(DSN)nameintheNamefield. Forexample,typeVMware VirtualCenter.
8 9
(Optional)TypeanODBCDSNdescriptionintheDescriptionfield. SelecttheservernamefromtheServerdropdownmenu. TypetheSQLServermachinenameinthetextfieldifyoucannotfinditinthe dropdownmenu.
10 11
ClickNext. Selectoneoftheauthenticationmethods: IfyouareusinglocalSQLServer,selectWindowsNTauthentication. WindowsNTauthentication,alsoknownastrustedauthentication,is supportedonlyiftheSQLServerisrunningonthesamesystemas VirtualCenter. IfyouareusingremoteSQLServer,selectSQLServerauthentication. WindowsNTauthenticationisnotsupportedonremoteSQLservers.
VMware, Inc.
97
Toidentifytheauthenticationtype: a b c OpenSQLServerEnterpriseManager. ClickthePropertiestabtoviewproperties. Checkthemode. ThemodeindicateseitherWindowsNTorSQLServerauthenticationtype. 12 TypeyourSQLServerloginnameandpassword. Askyourdatabaseadministratorforthisinformation. 13 14 15 16 ClickNext. SelectthedatabasecreatedforVirtualCenterfromtheChangethedefault databasetomenuandclickNext. ClickFinish. FromtheODBCMicrosoftSQLServerSetupmenu,chooseTestDataSource. Ifthetestdatasourceisacceptable,clickOK.Ifitisnotacceptable,clickBackand reconfigureanyincorrectitems. 17 18 ToclosetheODBCDataSourceAdministrator,clickClose. EnsurethattheSQLAgentisrunningonyourdatabaseserver. ThisappliestoSQLServer2000andSQLServer2005editions.
Configuring Microsoft SQL Server 2005 Express

VirtualCentersupportsbothMicrosoftSQLServer2005Express(32bit)andMicrosoft SQLServer2005Express(64bit).TheMicrosoftSQLServer2005Expressdatabase packageisinstalledandconfiguredwhenyouselectMicrosoftSQLServer2005Express asyourdatabaseduringVirtualCenterinstallationorupgrade.Thisisshownin ConfiguringCommunicationBetweenVirtualCenterComponentsonpage 103.No additionalconfigurationisrequired. IfMicrosoftSQLServer2005Expressisalreadyinstalled,reviewtherequireddatabase patchesspecifiedinVirtualCenterDatabaseRequirements(SEEUPDATE)onpage 47. Ifyoudonotprepareyourdatabasecorrectly,theVirtualCenterinstallermightdisplay errorandwarningmessages. Seewww.microsoft.com/sql/editions/express/default.mspx. NOTEVMwaredoesnotsupportMicrosoftSQLServer2005Expressfordeployments withmorethan5hostsand50virtualmachines.
98
VMware, Inc.
Maintaining Your VirtualCenter Database

AfteryourVirtualCenterdatabaseinstanceandVirtualCenterareinstalledand operational,performstandarddatabasemaintenanceprocesses.Theseinclude: Monitoringthegrowthofthelogfileandcompactingthedatabaselogfile,as needed.Seethedocumentationforthedatabasetypeyouareusing. Schedulingregularbackupsofthedatabase. BackingupthedatabasebeforeanyVirtualCenterupgrade. Formoreinformationonbackingupyourdatabase,seeyourdatabasedocumentation.
Installing VMware Infrastructure Management Software

ThissectiondescribeshowtoinstallmanagementsoftwarebyusingtheVMware InfrastructureManagementCDordownloadpackage.TheVMwareInfrastructure ManagementCDallowsyoutochoosethecomponentsyouwanttoinstallandinstalls allselectedcomponentsinasingleprocedure.
VirtualCenter Installation Prerequisites

IfyouchoosetoinstallVirtualCenter,firstdothefollowing: EnsurethatyourhardwaremeetsVMwareInfrastructureSystemRequirements onpage 45. MakesurethatthesystemyouuseforyourVirtualCenterinstallationbelongstoa domainratherthanaworkgroup.Ifassignedtoaworkgroup,your VirtualCenter Servercannotdiscoveralldomainsandsystemsavailableonthe networkwhenusingsuchfeaturesasVirtualCenterConsolidation.Todetermine whetherthesystembelongstoaworkgrouporadomain,rightclickMyComputer andclickPropertiesandtheComputerNametab.TheComputerNametab displayseitheraWorkgrouplabeloraDomainlabel. CreateaVirtualCenterdatabase,unlessyouwanttouseSQLServer2005Express. SeePreparingtheVirtualCenter ServerDatabaseonpage 93. ObtainandassignastaticIPaddressandhostnametotheWindowsserverthat willhostVirtualCenterandthelicenseserver.ThisIPaddressmusthaveavalid (internal)DNSregistrationthatresolvesproperlyfromallmanagedESX Server hosts.Forbestresults,ensurethattheWindowsservernameisexactlythesameas theDNShostname.
VMware, Inc.
99
YoucandeployVirtualCenterbehindafirewall.However,makesurethereisno NetworkAddressTranslation(NAT)firewallbetweenVirtualCenterandthehosts itwillmanage. Theinstallerautomaticallyinstallsalicenseserverforyou,unlessyouenterapath toanexistinglicenseserver. Ifyouwanttouseanexistinglicenseserver,obtainthehostnameorIP address. Ifyouaregoingtoallowtheinstallertoinstallalicenseserver,youneeda validservedlicensefile. Becausethelicenseserverdoesnotsupportlicensefilesonanetworkshare, placeyourlicensefilesinadirectoryonasystemwhereyouareinstallingthe licenseserver.
Components Installed
TheVMwareInfrastructureManagementinstallerincludesthefollowingcomponents: VMwareVirtualCenterServerAWindowsservicetomanageESXServerhosts. VIClientAclientapplicationusedtoconnectdirectlytoanESXServeror indirectlytoanESXServerthroughaVirtualCenterServer. Microsoft.NETFrameworkSoftwareusedbytheVirtualCenterServer,Database Upgradewizard,andtheVIClient. MicrosoftSQLServer2005ExpressAfreeversionoftheMicrosoftSQLServer databaseforsmallerscaleapplications.Ifyouenterapathtoanexistingdatabase, theinstallerdoesnotinstallMicrosoftSQLServer2005Express. VMwareUpdateManager(optional)AVirtualCenterpluginthatprovides securitymonitoringandpatchingsupportforESXServerhostsandvirtual machines. VMwareConverterEnterpriseforVirtualCenterServer(optional)A VirtualCenterpluginthatenablesyoutoconvertyourphysicalmachinestovirtual machines. VMwarelicenseserverAWindowsserviceallowingallVMwareproductstobe licensedfromacentralpoolandmanagedfromoneconsole.Ifyouenterapathto anexistinglicenseserver,theinstallerdoesnotinstallalicenseserver.
100
VMware, Inc.
Installation Procedure
ThefollowingproceduredescribeshowtoinstallallVMwareInfrastructure managementcomponents. To install VMware Infrastructure Management 1 2 AsAdministratorontheWindowssystem,inserttheinstallationCD. WhentheVMwareInfrastructureManagementInstallerscreenappears,click Next. IftheVMwareInfrastructureManagementInstallerscreendoesnotappear, doubleclicktheautorun.exeicon. 3 4 5 6 ReadtheIntroductionpageandclickNext. SelectIacceptthetermsinthelicenseagreementandclickNext. TypeyourusernameandcompanynameandclickNext. SelectoneoftheinstallationtypesandclickNext. Thechoicesare: InstalltheVI Client. InstallVirtualCenter. Chooseacustominstallationtoinstallmultiplecomponents. 7 Selecttheoptioncorrespondingwiththedatabaseyouconfigured. Ifyouhavenotconfiguredasupporteddatabase,clickInstallMicrosoftSQL Server2005Express.Thisdatabaseissuitableforsmalldeploymentsofupto 5 hostsand50virtualmachines. Ifyouhaveconfiguredasupporteddatabase,clickUseanexistingdatabaseand enteryourdatabaseconnectioninformation: a Typethedatasourcename(DSN)associatedwithyourdatabase. ThismustbeasystemDSN. b IfyourdatabaseisalocalSQLServerdatabaseusingWindowsNT authentication,leavetheusernameandpasswordfieldsblank.Otherwise, typetheusernameandpasswordassociatedwiththedatasourcenameand clickNext. Ifyourconnectionfails,awarningappears.ClickOKandreenteryour databaseconnectioninformationuntilyoucancontinue.
VMware, Inc.
101
Selectoneofthefollowingoptions: TouseVirtualCenterinevaluationmode,selectIwanttoevaluate VirtualCenterServerandclickNext. Ifyouchoosethisoption,theenterpriseleveleditionofVirtualCenteris installedinevaluationmode.TheVMwareLicenseServerisalsoinstalledso thatyoucanswitchtolicensedmodeduringoraftertheevaluationperiod. TouseVirtualCenterinlicensedmodewithanexistinglicenseserver: i ii iii SelectUseanexistingLicenseServer. Enterthepathtoyourexistinglicenseserver. SelecttheVirtualCentereditionthatyoupurchasedandclickNext.
Ifyouchoosethisoption,theVMwareLicenseServerisnotinstalled. TouseVirtualCenterinlicensedmodewhenyoudonothaveanexisting licenseserver: i ii Leavebothcheckboxesunselected. SelecttheVirtualCentereditionthatyoupurchasedandclickNext.
Ifyouchoosethisoption,theVMwareLicenseServerisinstalled. 9 Entertheportandproxyinformationthatyouwanttouseoracceptthedefault informationshownonscreenandclickNext.Thisstepappliesonlytocustom installations. ThedefaultportforHTTPSis443.IfyouconfigureVirtualCentertouseadifferent portforHTTPS,youmustusetheconfiguredportnumberwhenyouloginto VirtualCenterinthisformat:<ipaddress>:<portnumber> 10 EnterinformationaboutthesystemonwhichyouareinstallingVirtualCenterand clickNext. Enter: TheIPaddressordomainnameofthesystemonwhichyouareinstalling VirtualCenter. Theloginandpasswordthatyouusetologintothesystemonwhichyouare installingVirtualCenter. 11 ForVMwareUpdateManager,youcanusethesamedatabasethatyouusefor VirtualCenter,oryoucanuseanotherdatabase.SeeStep 7.
102
VMware, Inc.
12
ForVMwareUpdateManager,entertheportandproxyinformationthatyouwant touseoracceptthedefaultinformationshownonscreen.Thisstepappliesonlyto custominstallations. ForVMwareConverter,entertheportinformationthatyouwanttouseoraccept thedefaultinformationshownonscreen.Thisstepappliesonlytocustom installations. ClickNexttocontinuethroughthedeploymentoptionsscreens.
13
14
AcceptthedefaultdestinationfoldersandclickNext. Ifyoudonotwanttoacceptthedefaultdestinationfolders: ForVMwareInfrastructure,clickChangetoselectanotherlocationandclick Next. Fordownloadingpatches,clickChangetoselectanotherlocationandclick Next. CAUTIONToinstalltheVMwareInfrastructurecomponentsonadriveotherthan theC:drive,verifythereisenoughspaceintheC:\WINDOWS\Installerfolderto installtheMicrosoftWindowsInstaller.msifile.Ifyoudonothaveenoughspace, becauseofaknownissuewithWindowsInstaller,yourVMwareInfrastructure installationmightfail.
15
ClickInstall. Installationmighttakeseveralminutes.Multipleprogressbarsappearduring installationoftheselectedcomponents.
16
ClickFinishtocompletetheVMwareInfrastructureinstallation.
Configuring Communication Between VirtualCenter Components

VirtualCentermustbeabletosenddatatoeveryVirtualCentermanagedhostand receivedatafromeachVI Client.Toenableanymigrationorprovisioningactivities betweenVirtualCentermanagedhosts,thesourceandtargethostsmustbeableto receivedatafromeachother.(SEEUPDATE)
VMware, Inc.
103
Duringnormaloperations,VirtualCenterislisteningfordatafromitsmanagedhosts andclientsondesignatedports.Additionally,VirtualCenterassumesthatitsmanaged hostsarelisteningfordatafromVirtualCenterondesignatedports.Ifafirewallis betweenanyoftheseelements,anopeningmustbecreatedtoallowdatatransferto thesedesignatedports. Thefollowingsectionsdescribehowtofacilitatethiscommunication.Forinformation aboutSDKcommunications,seetheVMwareSDKdocumentation.Foramore thoroughdiscussionoffirewallconfiguration,seetheServerConfigurationGuide.
Connecting to Your VirtualCenter Server Through a Firewall

ThedefaultportsthatVirtualCenterusestolistenforconnectionsfromtheVI Clientare ports80,443,and902.VirtualCenteralsousesport443tolistenfordatatransferfrom SDKclients. IfyouhaveafirewallbetweenyourVirtualCenter Serveranditsclients,youmust configureameansforVirtualCentertoreceivedatafromthem. ToenableVirtualCentertoreceivedatafromtheVI Client,openports80,443,and902 inthefirewalltoallowdatatransferfromtheVI ClienttoVirtualCenter.Toenable VirtualCentertoreceivedatafromSDKclients,openport443inthefirewall.For additionalinformationonconfiguringportsinafirewall,seeyourfirewallsystem administrator. IfyouwantVirtualCentertouseadifferentporttoreceiveVI Clientdata,seeBasic SystemAdministration. TotunneltheVI ClientdatathroughthefirewalltothereceivingportonVirtualCenter, seeBasicSystemAdministration.VMwarerecommendsthatyounotusethismethod becauseitdisablestheVirtualCenterconsolefunction.
Connecting to Your Managed Hosts Through a Firewall

ThedefaultportthatVirtualCenterusestosenddatatothemanagedhostsisport902. IfyouhaveafirewallbetweenyourVirtualCenter ServerandVirtualCentermanaged host,youmustconfigureameansforVirtualCentertosenddatatothe VirtualCentermanagedhost. IfyouhaveafirewallbetweentwoVirtualCentermanagedhostsandyouwantto performanysourceortargetactivities,suchasmigrationorcloning,youmust configureameansforthemanagedhoststoreceivedata. ManagedhostsalsosendaregularheartbeatoverUDPport902toVirtualCenter. Firewallsmustnotblockthisport.
104
VMware, Inc.
To enable a VirtualCenter-managed host to receive data on the default port Openport902inthefirewalltoallowdatatransfertotheVirtualCentermanagedhost fromVirtualCenteroranotherVirtualCentermanagedhost.Foradditionalinformation onconfiguringtheports,seeyourfirewallsystemadministrator.
Connecting Hosts with the License Server Through a Firewall

ThedefaultportsthatthelicenseserverusestocommunicatewithESX Serverhostsare 2700and27010.IfyouareusingcentralizedlicensingwithyourESX Serverhosts,and haveafirewallbetweenyourESX Serverhostsandyourlicenseserver,openthese ports. Youcanchangethedefaultportsbyeditingthelicensefile.Whenyoueditthelicense file,useanASCIItexteditor.Validatetheeditedlicensefileat http://www.vmware.com/checklicense/.Afterchangingtheports,openthenewports youchoseinthefirewall.Consultyourfirewallsystemadministratorforadditional informationonconfiguringtheports.ForinformationonconfiguringtheESX Server firewall,seetheServerConfigurationGuide.
Uninstalling VMware Infrastructure Components

TheVMwareInfrastructurecomponentsareuninstalledseparately,eveniftheyareon thesamemachine.YoumusthaveAdministratorprivilegestouninstallthe VirtualCentercomponent. CAUTIONIfyoutrytouninstallVirtualCenterwhileitisrunning,youmustconfirm thatyouwanttotakeaction.Uninstallinginthiswaycausesadisruptiontoany VI Clientsconnectedtotheservice.Thiscancausedataloss. UninstallingtheVMwareInfrastructurecomponentsdoesnotuninstalltheMicrosoft .NETFramework.DonotuninstalltheMicrosoft.NETFrameworkifyouhaveother applicationsonyoursystemthatdependuponit. To uninstall a VMware Infrastructure Component using the Add/Remove Programs Tool 1 2 AsAdministratorontheWindowssystem,chooseStart>Settings>ControlPanel >Add/RemovePrograms. ToselectaVMwareInfrastructurecomponent,scrollthroughthelistofinstalled programs,selectthecomponenttoremove,andclickChangeorRemove.
VMware, Inc.
105
3 4
ClickYestoconfirmthatyouwanttoremovetheprogram. ClickFinish.
Installing VirtualCenter on a Virtual Machine

YoucaninstallyourVirtualCentercomponentsonaWindowsvirtualmachine,which runsonanESX Serverhost.DeployingVirtualCenteronavirtualmachinehasthe followingadvantages: RatherthandedicatingaseparateservertoVirtualCenter,youcaninstallitona virtualmachinerunningonthesameESX Serverhostwhereyourothervirtual machinesrun. YoucanprovidehighavailabilityforVirtualCenterbyusingVMwareHA. YoucanmigratethevirtualmachinethatcontainsVirtualCenterfromonehostto another,enablingmaintenanceandotheractivities. YoucancreatesnapshotsoftheVirtualCentervirtualmachineandusethemfor backups,archiving,andsoon. To install VirtualCenter on a virtual machine 1 2 OnanymachinethathasnetworkaccesstoyourESX Serverhost,installthe VI Client. UsingtheVI Client,accesstheESX Serverhostdirectlytocreatethevirtual machineforhostingVirtualCenter. Forinformationaboutcreatingvirtualmachines,seeBasicSystemAdministration. 3 Onthevirtualmachine,installVirtualCenter.
SeeInstallingVMwareInfrastructureManagementSoftwareonpage 99. FormoredetailsoninstallingandrunningVirtualCenteronavirtualmachine,see RunningVirtualCenterinaVirtualMachineatwww.vmware.com/pdf/vi3_vc_in_vm.pdf
106
VMware, Inc.
10
Maintaining ESX Server 3i and the VI Client
10
Softwareupdatesmightbepatchesforaddressingcriticalsecurityissuesorurgentbug fixes,ortheymightbegeneralupdatesormaintenancereleases.Theymightbelocated onthelocalfilesystemoronanNFS,FTP,orHTTPserver.Eachupdateconsistsofa descriptorfileandasetofpackages.Thedescriptorcontrolstheinstallationprocessand checksthatrequirementsaremet.Forexample,youmightberequiredtopoweroffall virtualmachinesrunningontheserveryouareabouttoupdate,oryoumightneedto reboottheserveraftertheupdate. Thischapterdiscussestwoutilitiesyoucanusetoapplysoftwareupdatestothe VI ClientandESX Server 3isoftware.TheVMwareInfrastructureUpdateisagraphical userinterface(GUI)application.Thevihostupdateutilityisaremotecommandline interface(CLI)tool.Theseutilitiesarediscussedinthefollowingsections: PerformingMaintenancewithInfrastructureUpdateonpage 107 PerformingMaintenanceWiththevihostupdateUtilityonpage 111 RollingBackanUpdateonpage 114
Performing Maintenance with Infrastructure Update

WhenyouinstalltheVI Client,thesoftwareinstallsInfrastructure Update. Infrastructure Updateletsyoulearnabout,download,andinstallmaintenanceand patchreleases,whichprovidesecurity,stability,andfeatureenhancementsforVMware Infrastructure.
VMware, Inc.
107
TheInfrastructure Updateperiodicallychecksfornewupdatesthatareapplicableto ESX Server 3ihostsconnectedtotheVI Client.Ifnewupdatesarediscovered, Infrastructure Updatedownloadstheimageandthecompanionsoftwareinthe background,andcachesthedownloadedupdatesinalocalrepository. NOTESoftwareupgradesaredifferentfromupdates.Upgradesareformajorreleases ofthetypex.0andminorsoftwarereleasesofthetypex.y.Forexample,ESX Server 2.0 andESX Server 2.5. VMwareupdatesareformaintenancereleasesofthetypex.y.zandpatches.For example,ESX Server2.5.3andESX Server2.5.3Patch2.Updatesarediscussedinthis chapter. Seehttp://www.vmware.com/download.
System Requirements for Infrastructure Update

TouseInfrastructure Update,youmusthave: AworkstationorlaptopwiththeVI Clientinstalled. YoucaninstalltheVI ClientbyusingtheVMwareInfrastructureManagementCD distributedwiththeESX Server 3ihost.Alternatively,youcandownloadthe VI Clientathttp://<ipaddressofyour3ihost>. AnetworkconnectionbetweentheESX Server 3ihostandthecomputerthatis runningtheVI Client.
Scheduling Automatic Update Notifications

Bydefault,automaticupdatenotificationisenabled.Ifyoukeepautomaticupdate notificationsenabled,youdonothavetosearchfornewupdatesorworrythat somethingimportantmightbemissing.Infrastructure Updatechecksforavailable updatesforthefollowingsoftwarecomponents: ESX Server 3i RemoteCLI VI Client VMwareTools VMwareUpdate Thedefaultdayandtimefortheupdateservicetocheckforavailableupdatesisevery Sundayat12:00a.m.
108
VMware, Inc.
Chapter 10 Maintaining ESX Server 3i and the VI Client
To schedule a different day and time for update checks 1 2 ChooseStart>Programs>VMware>Infrastructure Update. OntheUpdatestab,enteradifferentdayandtime.
Selecting Hosts to Be Managed

Infrastructure UpdatecompilesalistofESXhostsinyourdatacenter.Thislistofhosts hasasubsetofhoststhatarecurrentlyreachable.Bydefault,theservicemanages reachablehostsbyperiodicallycheckingthemforavailableupdates. To configure the list of managed hosts 1 2 ChooseStart>Programs>VMware>VMwareInfrastructure Update. OntheHoststab,selectthehoststomanageandclickApply. Infrastructure Updateverifiesthattheselectedhostsarereachable.
Installing Available Updates

Infrastructure Updatedownloadsavailableupdates.Thedownloadsarebackground tasksanddonotdisruptnormaloperation.Theupdateservicedoesnotinstallupdates foryou.Instead,theupdateservicedisplaysalistofavailableupdatesthatyoucan choosetoinstall. Whennewupdatesareavailable,thesystemtrayiconforInfrastructure Update displaysanotification.Thenotificationsappearonlyifyoukeepautomaticupdate notificationsenabled. To install available updates 1 2 3 ChooseStart>Programs>VMware>VMwareInfrastructure Update. OntheHoststab,selectahostandclickApply. Entertheusernameandpasswordfortheselectedhost. Aninstallationwizardletsyouchoosethesoftwarepackagestoinstallandguides youthroughtheinstallationprocess. 4 5 ClickContinuetoinstallavailableupdatesonthenexthost. RepeatStep 3andStep 4untilallhostsareupdated.
Afterallupdatesareapplied,VMwareUpdaterestartsallaffectedservices.
VMware, Inc.
109
Disabling Automatic Update Notifications

WhenyouusetheVI Clienttoconnecttoahostdirectly,theVI Clientchecksfor availableupdatesandnotifiesyouwhenupdatesareavailable. To disable automatic update notifications 1 2 ChooseStart>Programs>VMware>VMwareInfrastructure Update. OntheUpdatestab,deselectAutomaticallycheckforrecommendedupdatesand clickOK.
Manually Checking for Available Updates

Youcanmanuallycheckwhetherupdatesareavailableforthereachablehostsinyour datacenter. To manually check for updates 1 2 3 ChooseStart>Programs>VMware>VMwareInfrastructure Update. OntheHoststab,selectthehoststocheckforupdates. OntheUpdatestab,clickCheckNow.
Theupdateservicerepliestoyourquery,indicatingeitherthatanupdateisavailableor thatthereisnoupdate. Forinformationabouthowtoinstallupdates,seeInstallingAvailableUpdateson page 109.
Using Removable Media to Install Updates

Optionally,youcanmanuallydownloadandburnupdatefilesontoremovablemedia, suchasaCDROMorDVD,andthenusetheremovablemediatoupdatearemote system.ThisoptionisusefulwhenyouupdateESX Server 3ihoststhatarenot connectedtotheInternet. To install software that is stored on removable media 1 2 3 4
110
Fromhttp://www.vmware.com/download,downloadoneormorepackageZIP files. Burnthefilesontoremovablemedia,suchasaCDROMorDVD. InserttheremovablemediaintoaworkstationorlaptopwiththeVI Client installed. ConnecttheVI Clienttothehostthatneedstobeupdated.

VMware, Inc.
5 6 7
ChooseStart>Programs>VMware>VMwareInfrastructure Update. OntheUpdatestab,clickAddFiles. NavigatetotheremovablemediaandselectaZIPfile. ThisactionaddstheZIPfiletotheinstallationcache.Ifapplicableupdatesare availableforhoststhattheupdateserviceismanaging,aninstallwizardguides youthroughtheinstallationprocess.Toupdatehoststhatarenotalreadybeing managed,addthemtothemanagedhostslist.
To add hosts to the managed hosts list 1 2 3 ChooseStart>Programs>VMware>VMwareInfrastructure Update. OntheHoststab,selectthehoststocheckforupdates. OntheUpdatestab,clickCheckNow.
Performing Maintenance With the vihostupdate Utility

YoucanusethevihostupdateRemoteCLIutilityformaintenanceofyourESX Server 3i hostsandtheVI Client.Thecommandcaninstallsoftwareupdates,enforcesoftware updatepolicies,andtrackinstalledsoftware.Onlytherootusercanrunthecommand. NOTEIncontrasttomostotherRemoteCLIcommands,youmustrunthiscommand ontheESX Server 3ihostdirectly,thatis,the--vihostoptionisnotsupported. TheRemoteCLIisavailableintwoforms: AsavirtualappliancethatyoucanimportintoESX Server,VMwareWorkstation, orVMwarePlayer. AsapackagethatyoucaninstallonMicrosoftWindowsandLinuxmachines. ForinformationaboutimportingorinstallingtheRemoteCLI,seetheRemote CommandLineInterfacesappendixoftheESX Server 3iConfigurationGuide. Beforeyoucanbackupyourhostconfigurationdata,youmusthaveaccesstoa machinethatisrunningtheRemoteCLI.AfteryoupowerontheRemoteCLI,ashell promptletsyourunCLIcommandsonanESX Server 3ihosttowhichyouconnect remotely.
VMware, Inc.
111
To update a host 1 Poweroffanyvirtualmachinesthatarerunningonthehosttoupdate. Whenyourunthevihostupdateutility,thesoftwareplacesthehostinto maintenancemode.Thehostcannotbeplacedintomaintenancemodeunlessyou firstpoweroffallvirtualmachinesthatarerunningonthehost. 2 Onahostotherthanthehostyouareupdating,powerontheRemoteCLIandlog in. Youdonotneedtotypethepasswordonthecommandline.Ifnopasswordis specified,thetoolpromptsyouforthepasswordwithoutechoingtheoutputtothe terminal.Thismeansthepasswordyoutypeisnotvisibleinthewindowasyou runthecommand. YoucancreateasecureconnectiontotheRemoteCLI,byusingtheRemoteCLIIP address.IfyouareusingtheVI Client,youcanrightclicktheRemoteCLIand selectOpenConsole.IftheRemoteCLIisinstalledonyourWindowsorLinux system,youcanusetheinstalledapplication,inwhichcaseyoudonotneedtolog in. 3 4 5 DownloadthefileandcopyittotheRemoteCLIfilesystem. Runthevihostupdateutility. Rebootthehostfortheupdatestotakeeffect.
Forcommandsyntaxexamples,seeExamples:thevihostupdateUtilityonpage 113.
How the vihostupdate Maintenance Utility Installs Software Updates

Duringtheinstallationprocess,thevihostupdateutilityproceedsasfollows: 1 2 3 Checksforprerequisites.Forexample,checkswhetherthecorrectversionofthe ESX Serverhostisinstalledorwhetherallvirtualmachinesarepoweredoff. UpdatesanESXServer3ihostwithavailableupdates.Youmustensurethatthe updatebundleisinadirectorythatisaccessiblefromthevihostupdatetool. InstallsthreeseparatecomponentsincludingtheESXServer3ifirmware, VMware Toolsforvirtualmachines,andaVI Clientinstaller.
112
VMware, Inc.
Options for the vihostupdate Utility

YoucanrunthevihostupdateutilitywiththeoptionsshowninTable 101.For informationaboutgeneraloptionsavailablewiththeRemoteCLIcommands,seethe RemoteCommandLineInterfacesappendixoftheESXServer3iConfigurationGuide. Table 10-1. Options for the vihostupdate utility
Option --bundle <bundle_file_name> --install --b --i Description UnpackthedownloadedZIPfile.Ifyouspecifythisoption, youcannotspecify--metadata. Patchthehostwithapplicablepackagesintheupdate bundle.Thisoptiontakesnoarguments,butyoumustalso includeeither-btospecifyabundleor-mtospecifya metadatafile. Pathtothemetadata.xmlfilethatcontainsinformation abouttheupdatebundle.Ifyouspecifythisoption,you cannotspecify--bundle. Listinstalledpackagesonthehost.Thisoptionreturns versioninformationfortheESX Serverhost,aswellasall packagesinstalledandtheirversionnumbers.
--metadata <metadata_xml_file> --query
--m
--q
Examples: the vihostupdate Utility

Assumethepathtoafileis<mypatch>.zip.Ifyouthengotothedirectorywhereyou copiedthatfile,youcanexecutethecommandsshowninTable 102. Table 10-2. Examples for the vihostupdate utility
Example vihostupdate --server <3i-host-ip> --username root --password <password> --i --b mypatch.zip vihostupdate --server <3i-host-ip> --username root --password <password> --b mypatch.zip vihostupdate --server <3i-host-ip> --username root --password <password> --i --m mypatch/metadata.xml Description Unpacksthefileand patchesthehost. Unpacksthefile,butdoes notpatchthehost. Patchesthehost.
VMware, Inc.
113
Rolling Back an Update

EachESX Server 3ihostcanstoretwobuilds,onebootbuildandonestandbybuild.The bootbuildistheonefromwhichthesystemisbooted. Foreachupdate,theupdateutilityupdatesthestandbybuild.Aftertheupdate,you thenrebootthehost.Onreboot,thenewlyupdatedbuildbecomesthebootbuild.Ifthe updateissuccessful,thehostcontinuestobootfromthenewbootbuilduntilthenext update.Uponthenextupdate,theupdateserviceupdatesthestandbybuild,andthe standbybuildbecomesthenewbootbuild. Forexample,supposethecurrentbootbuildis52252andthestandbybuildis51605. Whenyouupdatethehosttobuild52386,theupdateprocessreplacesbuild51605with build52386andmakesbuild52252thestandbybuild.Iftheupdateissuccessful,you continuetobootfrombuild52386untilthenextupdate. IfanupdatefailsandtheESX Server 3ihostcannotbootfromthenewbuild,thehost revertstobootingfromtheoriginalbuildthenexttimeyoureboot. Duringthebootprocess,youcanmanuallybootintothestandbybuild.Thiscausesan irreversiblerollback.Inotherwords,whenyoumanuallyselectthestandbybuild,the standbybuildbecomesthenewbootbuildandremainsthebootbuilduntilyou performanotherupdateormanuallyselectthestandbybuild. Iftheupdateprocessisinterrupted,theupdatefails.Forexample,supposeyou performedanupdateandyouarerebootingtheESX Server 3ihost.Thebootmenu displaysBuildXXXXX(upgrading).Ifaninterruptionoccurs,forexamplearebootor apowerfailure,theupdatefails. To switch to the standby build 1 2 3 ReboottheESX Server 3ihost. Whenyouseethepagethatdisplaysthecurrentbootbuild,pressShiftrtoselect thestandbybuild. PressShiftytoconfirmtheselectionandpressEnter.
114
VMware, Inc.
11
Monitoring the Condition of ESX Server 3i
11
ESX Server 3imonitoringletsyouchecktheconditionofthefollowinghost components: CPUprocessors Fans Memory Storage Temperature To monitor the condition of a host 1 2 LogontotheVI Clientandselecttheserverfromtheinventorypanel. ClicktheConfigurationtabandclickHealthStatus.
Ifacomponentisfunctioningnormally,thestatusindicatorisgreen.Theindicator changestoyelloworredifasystemcomponentviolatesaperformancethresholdoris notfunctioningproperly.Generally,ayellowindicatorsignifiesdegradedperformance. Aredindicatorsignifiesthatacomponenthasstoppedoperatingorhasexceededthe highestthreshold. TheReadingcolumndisplaysthecurrentvaluesforthesensors.Forinstance,this columndisplaysrotationsperminute(RPM)forfansanddegreesCelsiusfor temperature. IfyouareusingVMwareDistributedResourceScheduler(DRS)andVMwareHigh Availability(HA),theseservicescantakeactionwhenhardwareeventsoccur.
VMware, Inc.
115
116
VMware, Inc.
Appendix: ESX Server 3i Hardware Considerations
YourESXServer3ihostcomesfromthehardwarevendorinastatethatisreadytouse. Forreference,thisappendixprovidesthesystemrequirements. Thisappendixcoversthefollowingtopics: MinimumHardwareConfigurationsonpage 117 EnhancedPerformanceRecommendationsonpage 119 HardwareandSoftwareCompatibilityonpage 120
Minimum Hardware Configurations

Thissectiondiscussestheminimumhardwareconfigurationssupportedby ESX Server 3iversion3.5. YouneedthefollowinghardwareandsystemresourcestouseESX Server. OneormoreEthernetcontrollers.Supportedcontrollersinclude: BroadcomNetXtreme570xGigabitcontrollers IntelPRO/1000adapters NOTEThe3Com3c990driverdoesnotsupportallrevisionsofthe3c990.For example,3CR990Bisincompatible.
VMware, Inc.
117
ASCSIadapter,FibreChanneladapter,orinternalRAIDcontroller: BasicSCSIcontrollersareAdaptecUltra160andUltra320,LSILogic FusionMPT,andmostNCR/SymbiosSCSIcontrollers. FibreChannel.SeetheStorage/SANCompatibilityGuide. RAIDadapterssupportedareHPSmartArray,DellPercRAID(Adaptec RAIDandLSIMegaRAID),andIBM(Adaptec)ServeRAIDcontrollers. ASCSIdisk,FibreChannelLUN,orRAIDLUNwithunpartitionedspace.This diskorRAIDisusedforthevirtualmachines. ForhardwareiSCSI,adiskattachedtoaniSCSIcontroller,suchastheQLogic qla405x. ForSATA,adiskconnectedthroughsupporteddualSASSATAcontrollersthatare usingSASdrivers. ESX Serversupportsthefollowingstoragesystems: ATAdiskdrivesStorageofvirtualmachinesiscurrentlynotsupportedonATA drivesorRAIDs.VirtualmachinesmustbestoredonVMFSvolumesconfigured onaSCSIorSATAdrive,aSCSIRAID,oraSAN. SerialATA(SATA)diskdrivesSharingVMFSdatastoresonSATAdisksacross multipleESX Serverhostsisnotsupported. SCSIdiskdrivesSCSIdiskdrivescanstorevirtualmachinesonVMFS partitions. Storageareanetworks(SANs)SANs,bothFibreChannelandiSCSI,are supportedforstoringvirtualmachinesonVMFSdatastores. NOTETheminimumsupportedLUNcapacityforVMFS3is1200MB.
118
VMware, Inc.
Appendix: ESX Server 3i Hardware Considerations
Enhanced Performance Recommendations

TheconfigurationslistedintheprevioussectionsareforabasicESX Server 3i configuration.Inpractice,youcanusemultiplephysicaldisks,whichincludeSCSI disks,RAIDLUNs,andsoon. Thefollowingarerecommendationsforenhancedperformance: RAMHavingsufficientRAMforallofyourvirtualmachinesisimportantfor achievinggoodperformance.ESX ServerhostsrequiremoreRAMthantypical servers.AnESX ServerhostmustbeequippedwithsufficientRAMtorun concurrentvirtualmachines. Forexample,operatingfourvirtualmachineswithRed Hat Enterprise Linuxor Windows XPrequiresthatyourESX Serverhostbeequippedwithoverone gigabyteofRAMforbaselineperformance(1024MBforthevirtualmachines [256MBminimumforeachoperatingsystemasrecommendedbyvendors4]). Runningtheseexamplevirtualmachineswithamorereasonable512MBRAM requirestheESX Serverhosttobeequippedwithatleast2GBRAM(2048MBfor thevirtualmachines[512MB 4]). Thesecalculationsdonottakeintoaccountsystemuseandvariableoverhead memoryforeachvirtualmachine.SeetheResourceManagementGuide. DedicatedfastEthernetadaptersforvirtualmachinesDedicatedGigabit Ethernetcardsforvirtualmachines,suchasIntelPRO/1000adapters,improve throughputtovirtualmachineswithhighnetworktraffic. DisklocationForbestperformance,alldatathatyourvirtualmachinesuse shouldbeonphysicaldisksallocatedtovirtualmachines.Thesephysicaldisks shouldbelargeenoughtoholddiskimagesthatallofthevirtualmachinescanuse. ProcessorsFasterprocessorsimproveESX Serverperformance.Forcertain workloads,largercachesimproveESX Serverperformance. HardwarecompatibilityToensurethebestpossibleI/Operformanceand workloadmanagement,VMwareESX Serverprovidesitsowndriversfor supporteddevices.Besurethatthedevicesyouplantouseinyourserverare supported.ForadditionaldetailonI/Odevicecompatibility,downloadthe ESX ServerI/OCompatibilityGuidefromtheVMwareWebsiteat www.vmware.com/support/pubs/vi_pubs.html.
VMware, Inc.
119
Hardware and Software Compatibility

Forspecificinformationonsupportedhardwareandsoftware,downloadthe ESX ServerCompatibilityGuidesfromtheVMwareWebsiteat www.vmware.com/support/pubs/vi_pubs.html. SystemscompatibilityListsthestandardoperatingsystemsandserver platformsagainstwhichVMwaretests. I/OcompatibilityListsdevicesthatareaccesseddirectlythroughdevicedrivers intheESX Serverhost. StoragecompatibilityListsindetailthecombinationsofHBAsandstorage devicescurrentlytestedbyVMwareanditsstoragepartners. BackupsoftwarecompatibilityDescribesthespecificbackuppackagestestedby VMware.
120
VMware, Inc.
Index
Numerics
27000, port 79 27010, port 79
Consolidated Backup, licensing 53, 59 corrupted software, restoring 41 CPU processors, health 115
A
access, restricting 32 activation code, license 75 administrative password 32 applying patches 111 ATA disks 118 automatic updates 107
D
databases Oracle 94 preparing 93 SQL Server 96 deactivating ESX Server 3i 42 default storage behavior 29 DHCP 25 DHCP, direct console 26, 27 direct console 19, 37 alternatives 34 boot setting 23 configuring the keyboard 21 DHCP 26, 27 DNS 27 DNS suffixes 28 IP addressing 26, 28 management network 25 navigating 21 network adapters 25 network settings 25 NICs 25 password configuration 32 security banner 22 static addressing 26, 27, 28 testing management network 28 VLAN ID 25 DNS suffixes, direct console 28
B
backing up a configuration 38, 39 virtual machines 53, 59 banner, security 22 BIOS 23 boot setting 23 build numbers 114
C
CD-ROM, booting from virtual 24 centralized licensing configuring 76 description 56 clients, firewall 103 configuration backup and restore 38, 39, 40 configuration defaults, resetting 33 configuring the keyboard 21 configuring, ports 103 connectivity 35
VMware, Inc.
121
DPM, by edition 53 DRS, by edition 53
E
editions 59 ESX Server 3i backing up and restoring the configuration 38 deactivating 42 editions 59 restoring the firmware 41 update, rolling back 114 ESX Server hardware considerations 117 evaluation licenses 86
Oracle database 94 updates 109, 110 VI Client 34 VirtualCenter Server 34, 103 IP 25 IP addressing, direct console 26, 27, 28 iSCSI licensing 53
K
keyboard, localizing 21
L
LAC 52 license activation code 52, 75 license files installing 75 locations of 85 obtaining 75 license keys 56 license pool 56 license server availability 60 grace period 60 install 87 license types ESX Server 52 VirtualCenter Server 54 licenses, evaluation 86 licensing centralized 56 single-host 56 listening ports 103 local Oracle database 94 localizing, keyboard 21 lockdown mode 32
F
factory defaults, restoring 33 fan RPMs 115 file partitions, restoring 41 firewall 103 floppy, booting from virtual 24
G
grace period, license server 60 guest operating systems 49
H
HA, by edition 53 health monitoring 115 hosts firewall 103 hosts, updates 109
I
IDE disks 118 installing license server 87 on SANs 118
122
VMware, Inc.
Index
M
management agent, restarting 35 management network direct console 25 testing 28 manual updates 110 message, security 22 Microsoft Access database end of support life 47 monitoring, health 115 MSDE, preparing database 98
R
RCLI 38, 111 recovery CD 41 reimaging the USB flash 41 reinstalling VirtualCenter 105 remote access, restricting 32 management clients 34, 45 Oracle database 94 Remote CLI 38, 111 removable media, updates 110 removing VirtualCenter 105 resetting configuration defaults 33 restarting management agent 35 restoring a configuration 38, 40 ESX Server 3i firmware 41 factory defaults 33 restricting access 32 rolling back an ESX Server 3i update 114 root access, restricting 32 RPMs, fans 115
N
NAS, licensing 53 navigating, direct console 21 network settings, direct console 25 NICs, direct console 25 notifications for updates, disabling 110
O
ODBC databases 96 operating systems, guest 49 Oracle, preparing database 94
P
PAC 52 partitions 29 partner activation code 52 partner activation portal 52 password, administrative 32 patching 111 ports 27000 79 27010 79 configuring 103 firewall 103 license server 79 processor health 115
S
SATA disks 118 scheduling, updates 108 scratch storage 29 SCSI 118 SCSI disks 118 SDK 15 security banner 22 serial number 31, 80 single-host licensing configuring 80 description 56 SMP, licensing 53
VMware, Inc.
123
specifications ESX Server hardware considerations 117 performance recommendations 119 SQL Server, preparing database 96 static addressing about 25 direct console 26, 28 static DNS, direct console 27 storage 29 support information 31 support, guest operating system 49 system requirements license server 48 updates 108 VirtualCenter database 47 system swap 29
USB 41 using the RCLI 39, 40
V
VCB 53, 59 VI Client connectivity 35 installing 34 vihostupdate 111 bundle option 113 examples 113 install option 113 metadata option 113 query option 113 scan option 113 vihost option 111 virtual appliance, RCLI 38 virtual machines adapters for 119 backing up 59 disk location and size 119 high availability 59 installing VirtualCenter on 106 migrating 44 powering on 60 RAM requirements 119 resource management 59 small deployments 47, 93 specifications 49 storage of 118 upgrading tools 44 virtual media 24 VirtualCenter connectivity 35 installing 34 VLAN ID, direct console 25 VMFS 29 VMotion, licensing 59
T
TCP/IP ports 27000 79 27010 79 temperature 115 testing management network direct console 28 troubleshooting 33, 35
U
uninstalling VirtualCenter 105 updates automatic 107 disabling notifications 110 installing 109, 110 manual 107, 110 removable media 110 scheduling 108 selecting hosts 109 system requirements 108
124
VMware, Inc.
Index
VMware Consolidated Backup 53, 59 DRS, licensing 59 HA, licensing 59 Infrastructure Update 107
VMware, Inc.
125
126
VMware, Inc.
Updates for the ESX Server 3i Embedded Setup Guide
LastUpdated:June12,2009 ThisdocumentprovidesupdatestotheESXServer3iversion3.5Embeddedand VirtualCenter2.5versionoftheESXServer3iEmbeddedSetupGuide.Updated descriptions,procedures,andgraphicsareorganizedbypagenumbersothatyoucan easilylocatetheareasoftheguidethathavechanges.Ifthechangespansmultiple sequentialpages,thisdocumentprovidesthestartingpagenumberonly. ThefollowingisalistofupdatestotheESXServer3iEmbeddedSetupGuide: UpdatesfortheTableofSupportedDatabaseFormatsonPage 47 UpdatesfortheToprepareaSQLServerdatabasetoworkwithVirtualCenter ProcedureonPage 96 UpdatesfortheConfiguringCommunicationBetweenVirtualCenterComponents SectiononPage 103
Updates for the Table of Supported Database Formats on Page 47

ThefollowingrowshouldappearinTable 51:
MicrosoftSQLServer2005Standard InstallSP1orSP2forMicrosoftSQLServer2005. ForWindows2000andWindowsXP,apply MDAC2.8SP1totheclient. UsetheSQLNativeClientdriverfortheclient.
VMware, Inc.
Update1
Updates for the ESX Server 3i Embedded Setup Guide
Table 51doesnotmentionsupportforversionslaterthan10.2.0.3.0ofOracle10g EnterpriseRelease2,andthesupportfortwonewOraclepatches.Therowshould appearasfollows:

OracleDatabase10gRelease2 (10.2.0.1.0)StandardEdition OracleDatabase10gRelease2 (10.2.0.1.0)EnterpriseEdition Afterapplyingpatch10.2.0.3.0totheclientand server,applypatch5699495totheclient.Also applypatches6085625and6452485totheserver.
Note:VMwaresupports10.2.0.3.0andlater versionsofOracleDatabase10gRelease2.
Updates for the To prepare a SQL Server database to work with VirtualCenter Procedure on Page 96
ThefollowingtextshouldappearinToprepareaSQLServerdatabasetoworkwith VirtualCenter: Makesurethatthedatabaseuserhasthefollowingpermissions: MicrosoftSQLServer2000Makesurethatthedatabaseuserhasthedb_owner fixeddatabaseroleontheVirtualCenterdatabaseandtheMSDBdatabase.The db_ownerroleontheMSDBdatabaseisrequiredforinstallationandupgradeonly. Youcanrevokethisroleaftertheinstallationorupgradeprocessiscompleted. Do notgranttheSystemAdministratorsserverroletothedatabaseuser.However, iftheSystemAdministratorsrolewaspreviouslygrantedwhilethedatabasewas usedwithVirtualCenterServer2.0.x,donotrevoketheSystemAdministrators role.Leaveitasis. MicrosoftSQLServer2005Makesurethatthedatabaseloginhaseitherthe sysadminserverroleorthedb_ownerfixeddatabaseroleontheVirtualCenter databaseandontheMSDBdatabase.Thedb_ownerroleontheMSDBdatabaseis requiredforinstallationandupgradeonly.Youcanrevokethisroleafterthe installationorupgradeprocessiscomplete.
Updates for the Configuring Communication Between VirtualCenter Components Section on Page 103
ThefollowingtextshouldappearintheConfiguringCommunicationBetween VirtualCenterComponentssection: Port443isrequiredforcommunicationfromVirtualCentertoESXServerhosts.
Update2
VMware, Inc.

ESX Server 3i Embedded Setup Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ESX Server 3i Embedded Setup Guide

Uploaded by

Copyright:

Available Formats

ESX Server 3i Embedded Setup Guide

ESX Server 3i version 3.5 Embedded and VirtualCenter 2.5