Vi3!35!25 U2 Installation Guide

ESX Server 3 and VirtualCenter
Installation Guide
Update 2 Release for
ESX Server 3.5 and VirtualCenter 2.5
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com
2 VMware, Inc.
ESX Server 3 and VirtualCenter Installation Guide
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
2007, 2008 VMware, Inc. All rights reserved. Protected by one or more of U.S. Patent Nos. 6,397,242,
6,496,847, 6,704,925, 6,711,672, 6,725,289, 6,735,601, 6,785,886, 6,789,156, 6,795,966, 6,880,022,
6,944,699, 6,961,806, 6,961,941, 7,069,413, 7,082,598, 7,089,377, 7,111,086, 7,111,145, 7,117,481,
7,149,843, 7,155,558, 7,222,221, 7,260,815, 7,260,820, 7,269,683, 7,275,136, 7,277,998, 7,277,999,
7,278,030, 7,281,102, 7,290,253, 7,356,679, 7,409,487, 7,412,492, 7,412,702, 7,424,710, 7,428, 636,
7,433,951, and 7,434,002; patents pending.
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.
Revision: 20081017
Item: EN-000027-01
VMware, Inc. 3
Contents
AboutThisBook 7
1 IntroductiontoVMwareInfrastructure 11
VMwareInfrastructureataGlance 12
WhatsNewforInstallation 15
WhatsNewAboutInstallingVirtualCenterVersion 2.5 15
WhatsNewAboutInstallingESX Server 3.5 15
2 SystemRequirements 17
VMwareInfrastructureRequirements 17
VirtualCenter ServerRequirements 17
HardwareRequirements 17
VirtualCenter ServerSoftwareRequirements 18
VirtualCenterDatabaseRequirements 19
EndofSupportLifeforMicrosoftAccessDatabases 19
VI ClientRequirements 20
VI ClientHardwareRequirements 20
VI ClientSoftwareRequirements 20
VirtualCenterVIWebAccessRequirements 20
LicenseServerRequirements 21
LicenseServerHardwareRequirements 21
LicenseServerSoftwareRequirements 21
ESX Server 3Requirements 21
MinimumServerHardwareRequirements 21
EnhancedPerformanceRecommendations 24
HardwareandSoftwareCompatibility 25
SupportedGuestOperatingSystems 25
VirtualMachineRequirements 26
4 VMware, Inc.
3 VirtualCenterandESX Server 3LicensingOverview 27
LicensingTerminology 28
ESX Server 3Editions 28
VirtualCenter ServerEditions 30
VirtualCenterandESX Server 3LicensingModel 30
SingleHostandCentralizedLicenseTypes 30
CentralizedLicensing 31
SingleHostLicensing 32
LicenseKeyFunctionality 33
PerProcessorLicensing 33
PerInstanceLicensing 35
LicenseExpirationConsiderations 35
LicenseServerAvailability 35
UsinganExistingFLEXnetLicenseServer 39
ContactingSupport 40
4 RunningVMwareVirtualCenterandVMware ESX Server
in EvaluationMode 41
UsingESX ServerandVirtualCenterinEvaluationMode 41
LicensingVirtualCenterandESX ServerAftertheEvaluationPeriodExpires 42
ConsiderationsWhenYouSwitchESX ServerandVirtualCentertoLicensed
Modes 43
5 LicensingVirtualCenterandESX Server 45
LicensingProcess 46
ObtainingLicenseFiles 48
SettingUpCentralizedLicensing 49
InstallingLicenseFiles 49
LocationoftheLicenseServer 49
ConfiguringLicenseServerLicensing 50
ChangingtheDefaultLicenseServerPorts 52
ChangingfromSingleHosttoCentralizedLicensing 53
SettingUpSingleHostLicensing 53
ConfiguringanESX ServerMachineforSingleHostLicensing 53
SingleHostandCentralizedLicensingintheSameEnvironment 54
ConfiguringLicensingforaMixedESX Server 2.xandESX Server 3.x
Environment 55
ChangingfromCentralizedtoSingleHostLicensing 56
VMware, Inc. 5
Contents
LicenseFileContents 56
LicenseFileLocations 58
AddingNewLicenseFilestoLicenseServers 59
AddingNewLicenseFilestoSingleHosts 60
InstallingaLicenseServer 60
TroubleshootingLicensing 61
ReceivingLicenseActivationCodes 62
CheckingtheLicenseServer 62
CheckingtheLicenseFile 64
CheckingLicenseConfiguration 64
6 InstallingVMwareInfrastructureManagement 65
PreparingtheVirtualCenter ServerDatabase 65
ConfiguringanOracleConnectiontoWorkLocally 66
ConfiguringanOracleConnectiontoWorkRemotely 67
ConfiguringaSQLServerODBCConnection 68
ConfiguringMicrosoftSQLServer2005Express 71
MaintainingYourVirtualCenterDatabase 72
InstallingVMwareInfrastructureManagementSoftware 72
VirtualCenter ServerPrerequisites 72
ComponentsInstalled 73
InstallationProcedure 74
ConfiguringCommunicationBetweenVirtualCenterComponents 76
ConnectingtoYourVirtualCenter ServerThroughaFirewall 77
ConnectingtoYourManagedHostsThroughaFirewall 77
ConnectingHostswiththeLicenseServerThroughaFirewall 78
UninstallingVMwareInfrastructureComponents 78
InstallingVirtualCenterinaVirtualMachine 79
7 InstallingVMwareESX ServerSoftware 81
PreparingtoInstall 81
InstalledComponents 81
InstallationMethods 82
UsingRemoteManagementApplications 82
InstallationonSATADrives 82
LUNRequirements 83
6 VMware, Inc.
InstallingESX Server 83
NavigationintheInstaller 84
ESX ServerInstallationProcedure 84
MouseSelection 88
RecommendedPartitioning 88
AdvancedPartitioning 89
SettingYourTimeZone 92
PostinstallationConsiderations 93
LocatingtheInstallationLogs 93
AssigningNewHardwareontheServer 93
InstallingAdditionalDriversfromtheVMwareDriverDisk 93
VerifyingYourDeviceDriverMappings 94
DownloadingtheVI Client 94
InstallingaLanguagePackontheESXServerHost 94
A ESX ServerPartitioning 97
RequiredPartitions 97
OptionalPartitions 101
B RemoteandScriptedInstallations 103
ScriptingYourInstallations 103
EnablingScriptedInstallation 104
SettingUptheScript 105
CreatingaScriptUsingVIWebAccess 106
RunningaScriptedInstallationfromtheKickstartFile 109
EditingtheKickstartConfigurationFile 110
%includeSection 110
CommandSection 110
%packagesSection 115
%preSection 115
%postSection 115
%vmlicense_textSection 115
SampleKickstartFile 115
Index 117
VMware, Inc. 7

Thismanual,theInstallationGuide,describeshowtoinstallnewconfigurationsof
VMware
VirtualCenterandESX Server 3.
TheInstallationGuidecoversESXServer3.5.ToreadaboutESX Server 3iversion3.5,
see http://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.
WhenadiscussionappliestoallversionsofESXServerforVMware
Infrastructure 3,thisbookusesthetermESXServer3.x.
Intended Audience
ThismanualisintendedforanyonewhoneedstoinstallESX Server 3.5and
VirtualCenter2.5.TheinformationinthismanualiswrittenforexperiencedWindows
orLinuxsystemadministratorswhoarefamiliarwithvirtualmachinetechnologyand
datacenteroperations.
About This Book
8 VMware, Inc.

Document Feedback
VMwarewelcomesyoursuggestionsforimprovingourdocumentation.Ifyouhave
comments,sendyourfeedbackto:
docfeedback@vmware.com
VMware Infrastructure Documentation
TheVMwareInfrastructuredocumentationconsistsofthecombinedVMware
VirtualCenterandESXServerdocumentationset.
Abbreviations Used in Figures
ThefiguresinthisbookusetheabbreviationslistedinTable 1.
Technical Support and Education Resources
Thefollowingsectionsdescribethetechnicalsupportresourcesavailabletoyou.
Toaccessthecurrentversionsofthisbookandotherbooks,goto:
http://www.vmware.com/support/pubs
Table 1. Abbreviations
Abbreviation Description
database VirtualCenterdatabase
datastore Storageforthemanagedhost
dsk# Storagediskforthemanagedhost
hostn VirtualCentermanagedhosts
SAN Storageareanetworktypedatastoresharedbetweenmanagedhosts
tmplt Template
user# Userwithaccesspermissions
VC VirtualCenter
VM# Virtualmachinesonamanagedhost
VMware, Inc. 9
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,goto:
http://mylearn1.vmware.com/mgrreg/index.cfm
10 VMware, Inc.

VMware, Inc. 11
1
ThisbookdescribeseachseparateinstallerforsettingupVMwareESX Server 3and
VirtualCentercomponents.Thischapterdescribesthecomponentsindividually,soyou
knowwhichyouneedtoinstall.
Thischaptercontainsthefollowingtopics:
VMwareInfrastructureataGlanceonpage 12
WhatsNewforInstallationonpage 15
Introduction to VMware
Infrastructure 1
12 VMware, Inc.
VMware Infrastructure at a Glance
Figure 11illustratesthesixbasiccomponentsofVMwareInfrastructure.
Figure 1-1. VMware Infrastructure Components
OneVirtualCenter ServermanagesmultipleESX Serverhosts.
Eachshadedblockrepresentsaseparateinstallerorprocedure.TheVI Clientappears
twice,becauseyoucandownloaditfromaVirtualCenter ServerorESX Serverhost.
VMware Infrastructure Client
Web browser
license server
ESX
Server
hosts
VirtualCenter
database
VMware, Inc. 13
Chapter 1 Introduction to VMware Infrastructure
ThemajorcomponentsofVMwareInfrastructureare:
ESX ServerESX Serverprovidesavirtualizationlayerthatabstractsthe
processor,memory,storage,andnetworkingresourcesofthephysicalhostinto
multiplevirtualmachines.
ESX Server 3installationincludesdocumentationintheformofmanpages
availablefromtheserviceconsole.See InstallingVMwareESX ServerSoftware
onpage 81.
VirtualCenterServerThisserverinstallsonaWindowsmachine,eitherphysical
orvirtual,tocentrallymanageyourVMwareESX Serverhosts.
TheVirtualCenter ServerallowstheuseofadvancedVMwareInfrastructure
featuressuchasVMwareDRS,VMware HA,andVMotion.
AVMwareSDKWebserviceisinstalledwiththeVirtualCenter Server.
See InstallingVMwareInfrastructureManagementSoftwareonpage 72.
VirtualCenterPluginsOptionalapplicationsthatprovideadditionalcapabilities
andfeaturestoVirtualCenter.Generally,pluginsarereleasedseparately,installon
topofVirtualCenter,andcanbeupgradedindependently.Youcaninstallserver
componentsofpluginsonthesamecomputerwheretheVirtualCenter Server
resides,oronaseparateone.Aftertheservercomponentofapluginisinstalled,
youcanactivatethepluginsclientcomponent,whichenhancestheVI Clientwith
appropriateUIoptions.
Documentationprovidedwitheachpluginoffersinformationonhowserver
componentsofpluginsareinstalled.
Forinformationonhowtoinstalltheclientcomponent,verifywhichpluginsare
installed,andhowtodisableoruninstallpluginsthatyouarenotusing,seeBasic
SystemAdministration.
14 VMware, Inc.
Thefollowingpluginsareavailable:
VMwareConverterEnablesyoutoconvertphysicalorvirtualmachinesinto
ESX Servervirtualmachines.Afterconvertingthevirtualmachines,youcan
addthemtoyourVirtualCenterinventory.
VMwareUpdateManagerProvidessecuritymonitoringandpatching
supportforESX Serverhostsandvirtualmachines.
Inadditiontoanindependentservercomponentinstallation,thisrelease
supportsthecombinedinstallationfortheVirtualCenter ServerandUpdate
Manager.See InstallingVMwareInfrastructureManagementSoftwareon
page 72.Ifyouareupgrading,seetheUpgradeGuide.Forinformationon
UpdateManager,seetheUpdate ManagerAdministrationGuide.
VI ClientTheVI ClientinstallsonaWindowsmachineandistheprimary
methodofinteractionwithVMwareInfrastructure.TheVI Clientactsas:
Aconsoletooperatevirtualmachines.
AnadministrationinterfaceintotheVirtualCenter ServersandESX Server
hosts.
TheVI ClientisdownloadablefromtheVirtualCenter ServerandESX Server
hosts.TheVI Clientinstallationincludesdocumentationforadministratorsandfor
consoleusers.See InstallingVMwareInfrastructureManagementonpage 65.
WebAccessAbrowserletsyoudownloadtheVI Clientfromthe
VirtualCenter ServerorESX Serverhosts.Whenyouhaveappropriatelogin
credentials,WebAccessalsoletsyouperformlimitedmanagementofyour
VirtualCenter ServerandESX Serverhosts.
LicenseserverThisserverinstallsonaWindowssystemtoauthorizethe
VirtualCenter ServersandESX Serverhostsappropriatelyforyourlicensing
agreement.AdministratorsmakechangestosoftwarelicensesusingtheVI Client.
See SettingUpCentralizedLicensingonpage 49.
DatabaseTheVirtualCenter Serverusesadatabasetoorganizeallthe
configurationdatafortheVMwareInfrastructureenvironment.Forsmall
deployments,thebundledMicrosoftSQLServer2005Expressdatabaseletsyouset
upalimitednumbersofhostsandvirtualmachines(5hostsand50virtual
machines).VirtualCentersupportsseveralotherdatabaseproductsforlarger
deployments.See PreparingtheVirtualCenter ServerDatabaseonpage 65.
VMware, Inc. 15
Chapter 1 Introduction to VMware Infrastructure
Whats New for Installation
Thissectiondescribesproceduresforinstallingandupgradingpreviousversionsof
VirtualCenterandESX Server.Thissectionisnotacomprehensivelistofnewfeatures.
Whats New About Installing VirtualCenter Version 2.5
NewfeaturesintroducedinVirtualCenter2.5include:
AninstallationwizardthatinstallsVirtualCenter,theVIClient,andplugin
components
Newevaluationmode
Newlicenseserversupportofamultiplelicensefiledirectory
AfeaturethatdetectspluginsinstalledonaVirtualCenter Serverduringa
VI Clientinstallation
Othernewfeaturesdonothaveanimpactonanyinstallationorupgradeprocesses.
Whats New About Installing ESX Server 3.5
NewfeaturesintroducedinESX Server 3.5include:
NewevaluationmodeofferingfullaccesstoallESX Serverfeaturesforalimited
time
SATAdiskdrivessupportforESX Server 3.5installation
NewfeaturesintroducedinESX Serverversion 3.0.1includeanewupgradefeature
thatallowsmigrationupgradeswithoutvirtualmachinedowntime.
NewfeaturesintroducedinESX Serverversion 3.0include:
OnscreenHelpnolongerintheinstaller
VMFS3,anewfilesystem
VM3,anewvirtualmachineformat
UpdatedVMwareTools
NewVI Clientinstallation,downloadablefromachangedWebinterface
Othernewfeaturesdonothaveanimpactonanyinstallationorupgradeprocesses.
16 VMware, Inc.
VMware, Inc. 17
2
Thischapterdescribesthehardwareandoperatingsystemrequirementsforhosts
runningVirtualCenterandESX Server 3.Usetheinformationinthischaptertoensure
thatyourenvironmentmeetstherequirementsforinstallation.
VMwareInfrastructureRequirementsonpage 17
ESX Server 3Requirementsonpage 21
SupportedGuestOperatingSystemsonpage 25
VMware Infrastructure Requirements
VirtualCentermanagesESX Serverhostsusingaserverandthreetypesofremote
managementclients.
VirtualCenter Server Requirements
TheVirtualCenter Serverisaphysicalmachineorvirtualmachineconfiguredwith
accesstoasupporteddatabase.
Hardware Requirements
TheVirtualCenter Serverhardwaremustmeetthefollowingrequirements:
Processor2.0GHzorhigherIntelorAMDx86processor.Processorrequirements
canbelargerifyourdatabaseisrunonthesamehardware.
Memory2GBRAMminimum.RAMrequirementscanbelargerifyourdatabase
isrunonthesamehardware.
System Requirements 2
18 VMware, Inc.
Diskstorage560MBminimum,2GBrecommended.Youmusthave245MBfree
onthedestinationdriveforinstallationoftheprogram,andyoumusthave315MB
freeonthedrivecontainingyour%temp%directory.
MicrosoftSQLServer2005ExpressdiskrequirementsThebundleddatabase
requiresupto2GBfreediskspacetodecompresstheinstallationarchive.
However,approximately1.5GBofthesefilesaredeletedaftertheinstallationis
complete.
NetworkingGigabitrecommended.
VirtualCenter Server Software Requirements
TheVirtualCenter Serverissupportedasaserviceonthe32bitversionsofthese
operatingsystems:
Windows2000ServerSP4withUpdateRollup1(downloadUpdateRollup1from
http://www.microsoft.com/windows2000/server/evaluation/news/bulletins/rollu
p.mspx)
WindowsXPProSP2
Windows2003ServerSP1andSP2(allreleasesexcept64bit)
Windows2003ServerR2
VirtualCenter 2.xinstallationisnotsupportedon64bitoperatingsystems.
TheVirtualCenterinstallerrequiresInternetExplorer5.5orhighertorun.
NOTEStoragerequirementscanbelargerifyourdatabaserunsonthesame
hardwareastheVirtualCenter Servermachine.Thesizeofthedatabasevarieswith
thenumberofhostsandvirtualmachinesyoumanage.Usingdefaultsettingsfor
ayearwith25hostsand8to16virtualmachineseach,thetotaldatabasesizecan
consumeupto2.2GB(SQL)or1.0GB(Oracle).
NOTEForanyoperatingsystemexceptWindowsServer2003SP1,installMicrosoft
WindowsInstaller3.1,otherwiseyourVirtualCenterinstallationcanfail.
See http://support.microsoft.com/?id=893803forinformationondownloading
WindowsInstaller3.1.
VMware, Inc. 19
Chapter 2 System Requirements
VirtualCenter Database Requirements
VirtualCentersupportsthedatabaseformatslistedinTable 21.
Eachdatabaserequiressomeconfigurationadjustmentsinadditiontothebasic
installation.See PreparingtheVirtualCenter ServerDatabaseonpage 65.
End of Support Life for Microsoft Access Databases
SupportforMicrosoftAccesswasdiscontinuedwithVMwareVirtualCenter
version 2.0.VirtualCenter 2.5comeswithabundledversionofMicrosoftSQL
Server2005Expressforsmalldeployments(upto5hostsand50virtualmachines).
Table 2-1. Supported Database Formats
Database Type Service Pack, Patch, and Driver Requirements
MicrosoftSQLServer2000Standard
MicrosoftSQLServer2000Enterprise
SP4
ForWindows2000andWindowsXP,apply
MDAC2.8SP1totheclient.
UseSQLServerdriverfortheclient.
MicrosoftSQLServer2005Standard SP1orSP2
UseSQLNativeClientdriverfortheclient.
MicrosoftSQLServer2005Enterprise SP1orSP2
UseSQLnativeclientdriverfortheclient.
MicrosoftSQLServer2005ExpressSP2 ForWindows2000andWindowsXP,apply
UseSQLnativeclientdriverfortheclient.
Oracle9irelease2Standard
Oracle9irelease2Enterprise
Applypatch9.2.0.8.0totheserverandclient.
Oracle10gStandardRelease1(10.1.0.3.0)
Oracle10gEnterpriseRelease1(10.1.0.3.0)
None
Oracle10gStandardRelease2(10.2.0.1.0)
Oracle10gEnterpriseRelease2(10.2.0.1.0)
Firstapplypatch10.2.0.3.0totheclientandserver.
Then applypatch5699495totheclient.
20 VMware, Inc.
VI Client Requirements
ThefollowingsectionslistVI Clienthardwareandsoftwarerequirements.
VI Client Hardware Requirements
TheVI Clienthardwaremustmeetthefollowingrequirements:
Processor266MHzorhigherIntelorAMDx86processor(500MHz
recommended).
Memory256MBRAMminimum,512MBrecommended.
DiskStorage150MBfreediskspacerequiredforbasicinstallation.Youmust
have55MBfreeonthedestinationdriveforinstallationoftheprogram,andyou
musthave100MBfreeonthedrivecontainingyour%temp% directory.
VI Client Software Requirements
TheVI Clientisdesignedforthe32bitversionsoftheseoperatingsystems:
Windows2000ProSP4
Windows2000ServerSP4withUpdateRollup1(downloadUpdateRollup1from
http://www.microsoft.com/windows2000/server/evaluation/news/bulletins/rollu
p.mspx)
WindowsXPProSP2
Windows2003SP1andSP2(allreleasesexcept64bit)
Windows2003ServerR2
WindowsVistaBusiness
WindowsVistaEnterprise
TheVI ClientrequirestheMicrosoft.NET2.0Framework.Ifyoursystemdoesnothave
itinstalled,theVI Clientinstallerinstallsit.
VirtualCenter VI Web Access Requirements
TheVIWebAccessclientisdesignedforthesebrowsers:
WindowsInternetExplorer6.0orhigher,NetscapeNavigator7.0,Mozilla1.X,
Firefox1.0.7andhigher.
LinuxNetscapeNavigator7.0orlater,Mozilla1.x,Firefox1.0.7andhigher.
VMware, Inc. 21
License Server Requirements
Thissectiondescribesthelicenseserverrequirements.
License Server Hardware Requirements
Thelicenseserverhardwaremustmeetthefollowingrequirements:
Processor266MHzorhigherIntelorAMDx86processor.
Memory256MBRAMminimum,512MBrecommended.
DiskStorage25MBfreediskspacerequiredforbasicinstallation.
VMwarerecommendsthatyouinstallthelicenseserveronthesamemachineasyour
VirtualCenter Servertoensureconnectivity.TheVMwareInfrastructureManagement
InstallationCDinstallsalicenseserverwhenyouinstallVirtualCenter.
License Server Software Requirements
Thelicenseserversoftwareissupportedonthe32bitversionsofthefollowing
operatingsystems:
Windows2000ServerSP4
WindowsXPPro(atanySPlevel)
Windows2003(allreleasesexcept64bit)
ESX Server 3 Requirements
Thissectiondiscussestheminimumandmaximumhardwareconfigurations
supportedbyESX Server 3version 3.5.
Minimum Server Hardware Requirements
YouneedthefollowinghardwareandsystemresourcestoinstallanduseESX Server 3.
Atleasttwoprocessors:
1500 MHzIntelXeonandlater,orAMDOpteron(32bitmode)for
ESX Server 3
1500 MHzIntelXeonandlater,orAMDOpteron(32bitmode)for
VirtualSMP
1500 MHzIntelViivorAMDA64x2dualcoreprocessors
22 VMware, Inc.
1GBRAMminimum.
OneormoreEthernetcontrollers.Supportedcontrollersinclude:
BroadcomNetXtreme570xgigabitcontrollers
IntelPRO/100adapters
Forbestperformanceandsecurity,useseparateEthernetcontrollersfortheservice
consoleandthevirtualmachines.
ASCSIadapter,FibreChanneladapter,orinternalRAIDcontroller:
BasicSCSIcontrollersareAdaptecUltra160andUltra320,LSILogic
FusionMPT,andmostNCR/SymbiosSCSIcontrollers.
FibreChannel.SeetheStorage/SANCompatibilityGuide.
RAIDadapterssupportedareHPSmartArray,DellPercRAID(Adaptec
RAIDandLSIMegaRAID),andIBM(Adaptec)ServeRAIDcontrollers.
ASCSIdisk,FibreChannelLUN,orRAIDLUNwithunpartitionedspace.Ina
minimumconfiguration,thisdiskorRAIDissharedbetweentheserviceconsole
andthevirtualmachines.
ForhardwareiSCSI,adiskattachedtoaniSCSIcontroller,suchastheQLogic
qla405x.
ForSATA,adiskconnectedthroughsupporteddualSASSATAcontrollersthatare
usingSASdrivers.
NOTEThe3Com3c990driverdoesnotsupportallrevisionsofthe3c990.
For example,3CR990Bisincompatible.
VMware, Inc. 23
ESX Server 3supportsinstallingandbootingfromthefollowingstoragesystems:
ATAdiskdrivesInstallingESX Server 3onanATAdriveorATARAIDis
supported.However,ensurethatyourspecificdrivecontrollerisincludedinthe
supportedhardware.
StorageofvirtualmachinesiscurrentlynotsupportedonATAdrivesorRAIDs.
VirtualmachinesmustbestoredonVMFSvolumesconfiguredonaSCSIorSATA
drive,aSCSIRAID,oraSAN.
SerialATA(SATA)diskdrivesSATAdiskdrives,pluggedintodualSATA/SAS
controllers,aresupportedforinstallingESX Server 3andforstoringvirtual
machinesonVMFSpartitions.EnsurethatyourSATAdrivesareconnected
throughsupportedSATA/SAScontrollers:
mptscsi_pcieLSI1068E(LSISAS3442E)
mptscsi_pcixLSI1068(SAS5)
aacraid_esx30IBMserveraid8kSAScontroller
ccissSmartArrayP400/256controller
megaraid_sasDellPERC5.0.1controller
SCSIdiskdrivesSCSIdiskdrivesaresupportedforinstallingESX Server 3.
TheycanalsostorevirtualmachinesonVMFSpartitions.
Storageareanetworks(SANs)SANs,bothFibreChannelandiSCSI,are
supportedforinstallingESX Server 3.Theycanalsostorevirtualmachineson
VMFSdatastores.Forinformationaboutpreinstallationandconfigurationtasks
andknownissueswithinstallingandbootingfromFibreChannelSANs,seethe
SANConfigurationGuideatwww.vmware.com/support/pubs/vi_pubs.html.
BeforedeployingESX Server 3onaSAN,seethelatestversionoftheESX ServerSAN
CompatibilityGuideatwww.vmware.com/support/pubs/vi_pubs.html.
NOTESharingVMFSdatastoresonSATAdisksacrossmultipleESX Server 3hosts
isnotsupported.
NOTETheminimumsupportedLUNcapacityforVMFS3is1200MB.
24 VMware, Inc.
Enhanced Performance Recommendations
ThelistsinprevioussectionssuggestabasicESX Server 3configuration.Inpractice,
youcanusemultiplephysicaldisks,whichincludeSCSIdisks,FibreChannelLUNs,
RAIDLUNs,andsoon.
Herearesomerecommendationsforenhancedperformance:
RAMHavingsufficientRAMforallyourvirtualmachinesisimportantto
achievinggoodperformance.ESX Server 3hostsrequiremoreRAMthantypical
servers.AnESX Server 3hostmustbeequippedwithsufficientRAMtorun
concurrentvirtualmachines,plusruntheserviceconsole.
For example,operatingfourvirtualmachineswithRed Hat Enterprise Linuxor
Windows XPrequiresyourESX Server 3hostbeequippedwithoveragigabyteof
RAMforbaselineperformance:
1024MBforthevirtualmachines(256MBminimumperoperatingsystemas
recommendedbyvendors 4)
272MBfortheESX Server 3serviceconsole
Runningtheseexamplevirtualmachineswithamorereasonable512MBRAM
requirestheESX Server 3hosttobeequippedwithatleast2.2GBRAM.
2048MBforthevirtualmachines(512MB 4)
272MBfortheESX Server 3serviceconsole
Thesecalculationsdonottakeintoaccountvariableoverheadmemoryforeach
virtualmachine.See theResourceManagementGuide.
DedicatedfastEthernetadaptersforvirtualmachinesDedicatedgigabit
Ethernetcardsforvirtualmachines,suchasIntelPRO/1000adapters,improve
throughputtovirtualmachineswithhighnetworktraffic.
DisklocationForbestperformance,alldatausedbyyourvirtualmachines
shouldbeonphysicaldisksallocatedtovirtualmachines.Thesephysicaldisks
shouldbelargeenoughtoholddiskimagestobeusedbyallthevirtualmachines.
VMFS3partitioningForbestperformance,useVI ClientorVIWebAccesstoset
upyourVMFS3partitionsratherthantheESX Server 3installer.UsingVI Clientor
VIWebAccessensuresthatthestartingsectorsofpartitionsare64Kaligned,
whichimprovesstorageperformance.
NOTETheESX Server 3hostmightrequiremoreRAMfortheserviceconsoleif
youarerunningthirdpartymanagementapplicationsorbackupagents.
VMware, Inc. 25
ProcessorsFasterprocessorsimproveESX Server 3performance.Forcertain
workloads,largercachesimproveESX Server 3performance.
HardwarecompatibilityToensurethebestI/Operformanceandworkload
management,VMwareESX Server 3providesitsowndriversforsupported
devices.Besurethatthedevicesyouuseinyourserveraresupported.For
additionaldetailsonI/Odevicecompatibility,downloadtheESX ServerI/O
CompatibilityGuidefromwww.vmware.com/support/pubs/vi_pubs.html.
Hardware and Software Compatibility
Formoreinformationonsupportedhardwareandsoftware,downloadtheESX Server
CompatibilityGuidesfromwww.vmware.com/support/pubs/vi_pubs.html.
SystemscompatibilityListsthestandardoperatingsystemsandserver
platformsagainstwhichVMwaretests.
I/OcompatibilityListsdevicesthatareaccesseddirectlythroughdevicedrivers
intheESX Serverhost.
StoragecompatibilityListsthecombinationsofHBAsandstoragedevices
currentlytestedbyVMwareanditsstoragepartners.
BackupsoftwarecompatibilityDescribesthebackuppackagestestedby
VMware.
Supported Guest Operating Systems
TheVMwareGuestOperatingSystemInstallationGuideincludesinformationon
supportedguestoperatingsystems.Youcandownloadthisdocumentat:
http://www.vmware.com/support/pubs/vi_pubs.html
ESX Serverofferssupportforanumberof64bitguestoperatingsystems.See theGuest
OperatingSystemInstallationGuideforacompletelist.
Therearespecifichardwarerequirementsfor64bitguestoperatingsystemsupport.
ForAMDOpteronbasedsystems,theprocessorsmustbeOpteronRevEandlater.For
IntelXeonbasedsystems,theprocessorsmustincludesupportforIntelVirtualization
Technology(VT).ManyserversthatincludeCPUswithVTsupportmightshipwithVT
disabledbydefault,andVTmustbeenabledmanually.IfyourCPUssupportVTbut
youdonotseethisoptionintheBIOS,contactyourvendortorequestaBIOSversion
thatletsyouenableVTsupport.
Todeterminewhetheryourserverhasthenecessarysupport,youcanuseaCPU
CompatibilityToolathttp://www.vmware.com/download/vi/drivers_tools.html.
26 VMware, Inc.
Virtual Machine Requirements
EachESX Servermachinehasthefollowingrequirements.
Virtualprocessor
IntelPentiumIIorlater(dependentonsystemprocessor)
One,two,orfourprocessorspervirtualmachine
VirtualchipsetIntel440BXbasedmotherboardwithNS338SIOchip
VirtualBIOSPhoenixBIOS4.0Release6
NOTEIfyoucreateatwoprocessorvirtualmachine,yourESX Servermachine
musthaveatleasttwophysicalprocessors.Forafourprocessorvirtualmachine,
yourESX Servermachinemusthaveatleastfourphysicalprocessors.
VMware, Inc. 27
3
ThischapterdescribesthelicensingmodelsavailablewithESX Server 3and
VirtualCenter.
LicensingTerminologyonpage 28
ESX Server 3Editionsonpage 28
VirtualCenter ServerEditionsonpage 30
VirtualCenterandESX Server 3LicensingModelonpage 30
LicenseKeyFunctionalityonpage 33
LicenseExpirationConsiderationsonpage 35
LicenseServerAvailabilityonpage 35
UsinganExistingFLEXnetLicenseServeronpage 39
ContactingSupportonpage 40
VirtualCenter and
ESX Server 3 Licensing
Overview 3
28 VMware, Inc.
Licensing Terminology
Termsyoumightencounterduringthelicenseredemptionandconfigurationprocess
aredefinedbelow:
LicenseactivationcodeAlicenseactivationcode(LAC)isauniquecodethatis
associatedwithoneormoreVMwareproductspurchased.Youreceivethiscode
afteryourorderisprocessed,unlessyoupurchasedyourproductsfroman
authorizedVMwarereseller,inwhichcaseyoureceiveapartneractivationcode.
PartneractivationcodeApartneractivationcodeisauniquecodeidentifying
ordersplacedthroughVMwarepartners.IfyoupurchasedVMware
Infrastructure 3fromanauthorizedVMwarereseller,usethiscodetoregisteryour
purchasetoyourVMwarestoreaccount.
LicenseactivationportalThelicenseactivationportalisaselfserviceWebportal
thatyoucanusetoredeemyourlicenseactivationcodesanddownloadlicensefiles
forVMwareInfrastructure 3.
PartneractivationportalApartneractivationportalisaselfserviceWebportal
youusetoregisterapurchasemadefromanauthorizedVMwareresellertoyour
VMwarestoreaccount.Youenteryourpartneractivationcodeintotheportaland
downloadyourlicensefilesfromthelicenseactivationportal.
ESX Server 3 Editions
DependingontheeditionofVMwareInfrastructuresoftwareyoupurchased,you
mightbeentitledtodifferentESX Server 3licencetypes.
AfeweditionsincludelimitedaccesstothefeaturesetofESX Server 3.Certain
standardfunctionalityisavailableonlywithanoptionaladdonlicense,atadditional
cost.OthereditionsincludefullaccesstothefullfeaturesetofESX Server 3.
ESXServereditionsrequireFLEXnetlicensefilesthatcanbecentralizedoronasingle
host.Whenconfiguringyourhost,specifythelicencetypeforyourESX Server 3.For
instructions,seeToconfigurecentralizedlicensingforanESX Serverhostonpage 51.
LicensesfrompreviousreleasesofESXServerworkwithESXServer3.5.However,
licensingcapabilitiesaddedtoESXServer3.5editions(forexample,VMware
ConsolidatedBackup)arenotsupportedwithpreviouseditionsofESXServer.
VMware, Inc. 29
Chapter 3 VirtualCenter and ESX Server 3 Licensing Overview
Table 31displaysESX Server 3featuresarrangedbyedition.
Table 3-1. Edition Features for ESX Server 3 Machines
Feature VI Foundation VI Standard VI Enterprise
Licensetype Flexlicensefiles
(centralizedor
singlehost)
Flexlicensefiles
(centralizedor
singlehost)
Flexlicensefiles
(centralizedor
singlehost)
VMFS Yes Yes Yes
VirtualSMPsupport Yes Yes Yes
VMwareConsolidatedBackup
(VCB)
Yes Yes Yes
VMwareUpdateManager Yes Yes Yes
VMwareHA Addon Yes Yes
ServerVMotionand
Storage VMotion
Addon Addon Yes
VMwareDRSandDPM
(DistributedResource
SchedulerandDistributed
PowerManagement)
Addon Addon Yes
Guidedserverconsolidation,
with purchaseof
VirtualCenterServer
Yes Yes Yes
ManageablebytheVI Client Yes Yes Yes
RemoteCLIaccess Yes Yes Yes
ManageablebyVirtualCenter
in productionmode
Yes Yes Yes
ManageablebyVirtualCenter
inevaluationmode
Yes Yes Yes
VirtualCenterManagement
Agent
Yes Yes Yes
30 VMware, Inc.
VirtualCenter Server Editions
AtleastoneinstanceofaVirtualCenterlicenseisrequiredforVIFoundation,
VI Standard,andVIEnterpriseeditions.ThefollowingVirtualCentereditionsare
available:
VirtualCenterFoundationThiseditionletsyoumanageuptothreeESX Server
hosts.Ifyouneedtomanagemorethanthreehosts,upgradetoVirtualCenter
edition.
VirtualCenterThisisanenterpriseleveleditionthatletsyoumanageuptothe
systemmaximumnumberofhosts.Forinformationaboutsystemmaximums,see
ConfigurationMaximumsforVMwareInfrastructure 3.
TwotypesofFLEXnetlicensingareavailable:singlehostandcentralized.
For VirtualCenter,alllicensesmustbecentralized.
YoucanconvertVirtualCenterFoundationeditiontoVirtualCentereditionbyadding
anappropriatelicensefileandswitchingtheeditions.Thesoftwaredoesnotneedtobe
reinstalled.Forinformationonswitchingbetweentheeditions,seeToconfigure
centralizedlicensingfortheVirtualCenter Serveronpage 50.
VirtualCenter and ESX Server 3 Licensing Model
Unlessyouareusingevaluationmode,softwarelicensesarerequiredformost
operationsinVirtualCenterandESX Server 3,suchasaddinghoststoyour
VirtualCenterinventory.However,youcaninstall,launch,andconfigureVirtualCenter
andESX Serverwithoutasoftwarelicense.See RunningVMwareVirtualCenterand
VMware ESX Serverin EvaluationModeonpage 41.Twomodesoflicensingare
available:singlehostandcentralized.
Single-Host and Centralized License Types
Forsinglehostlicenses,thelicensefilesarestoredonindividualESX Serverhosts.
Centralizedlicensesarestoredonalicenseserver,whichmakestheselicensesavailable
tooneormorehosts.Youcanrunamixedenvironmentusingbothsinglehostand
centralizedlicensing.
VirtualCenterandfeaturesthatrequireVirtualCenter,suchasVMotion,mustbe
licensedincentralizedmode.ESX Serverfeaturescanbelicensedineithercentralized
orsinglehostmode.
VMware, Inc. 31
Figure 31illustratesthethreetypesoflicenseenvironments.
Figure 3-1. License File Locations in Single-Host, Mixed, and Centralized Environments
Centralized Licensing
Centralizedlicensingsimplifieslicensemanagementinlarge,dynamicenvironments
byallowingaVMwarelicenseservertoadministerlicenses.Withcentralizedlicensing,
youmaintainallyourVirtualCenter ServerandESX Serverlicensesfromoneconsole.
CentralizedlicensingisbasedonFLEXnetmechanisms.Withcentralizedlicensing,a
licenseservermanagesalicensepool,whichisacentralrepositoryholdingyourentire
licensedentitlement.
ESX host
license
file
ESX host
license
file
VI Clients
host-based
licensing
mixed: host-based &
server-based licensing
ESX host
license
file
ESX host
license
file
VI Clients
ESX host
ESX host
VirtualCenter
(recommended)*
license
server
license
file
server-based
licensing
VI Clients
ESX host
ESX host
VirtualCenter
(recommended)*
license
server
license
file
* Features such as VMotion and VMware HA require VirtualCenter.
32 VMware, Inc.
Whenahostrequiresaparticularlicensedfunctionality,thelicenseforthatentitlement
ischeckedoutfromthelicensepool.Licensekeysarereleasedbacktothepoolwhen
theyarenolongerbeingusedandareavailableagaintoanyhost.
Theadvantagesofcentralizedlicensinginclude:
Youadministeralllicensingfromasinglelocation.
NewlicensesareallocatedandreallocatedusinganycombinationofESX Server
formfactors.For example,youcanusethesame32processorlicenseforsixteen
2processorhosts,eight4processorhosts,four8processorhosts,two16processor
hosts,oranycombinationtotaling32processors.
Ongoinglicensemanagementissimplifiedbyallowinglicensestobeassignedand
reassignedasneeded.Assignmentchangesastheneedsofanenvironment
change,suchaswhenhostsareaddedorremoved,orpremiumfeatureslike
VMotion,DRS,orHAaretransferredamonghosts.
Duringperiodsoflicenseserverunavailability,althoughnewlicensescannotbe
issued,existingVirtualCenter Serverlicensedfunctionalitycontinuestooperate
indefinitelyandexistingESX Serverlicensedfunctionalitycontinuestooperate
withina14daygraceperiod.See LicenseServerAvailabilityonpage 35.
VMwarerecommendsusingthecentralizedlicensetypeforlarge,changing
environments.
Single-Host Licensing
Withsinglehostlicensing,yourtotalentitlementforpurchasedfeaturesisdivided
amongseparatelicensefilesresidingonESX ServerhostsandtheVirtualCenter Server.
Withsinglehostlicensing,whensomeoneactivatesalicensedfeature,thefeaturefor
thatentitlementmustresideinthelicensefileonthathost.Withsinglehostlicensing,
youmaintainseparatelicensefilesoneachESX Serverhost.Distributionofunused
licensesisnotautomatic,andthereisnodependenceonanexternalconnectionfor
licensing.SinglehostlicensefilesareplaceddirectlyonindividualESX Serverhosts
andreplacetheserialnumbersusedbypreviousversionsofESX Serverversion 2.x.
Theadvantagesofsinglehostlicensinginclude:
SinglehostfilesrequirenolicenseservertobeinstalledforESX Serverhostonly
environments.
InaVirtualCenterandlicenseserverenvironment,singlehostlicensingallows
ESX Serverhostlicensestobemodifiedduringperiodsoflicenseserver
unavailability.
VMware, Inc. 33
License Key Functionality
SpecificentitlementtorunVMwaresoftwareisdeterminedbylicensekeys.Depending
ontheESX ServerandVirtualCenterfeaturesyouwanttouse,purchasekeysbasedon
oneofthefollowing:
PerprocessorbasisToactivateafeature,ahostrequiresafeaturelicenseforeach
ofitsprocessors.
PerinstancebasisToactivateasingleinstanceofcertainfeature,asinglelicense
isrequiredregardlessofhowmanyprocessorsareused.
Licensedfeaturesalsodifferintheiroperationbasedonwhethertheyareconsideredto
beESX ServerorVirtualCenterfeatures.ESX Serverfeaturescanbelicensedusing
eithersinglehostorcentralizedlicensingmechanisms.Theydonotrequire
VirtualCenteroralicenseservertouse.VirtualCenterfeaturesrequirecentralized
licensing.ESX ServerfeaturesandVirtualCenterfeaturesalsodifferintheirbehavior
whenthelicenseserverisnotavailable.See LicenseServerAvailabilityonpage 35.
Table 32summarizesthelicensefeaturetypesforVMwareInfrastructure 3.
Per-Processor Licensing
FormostVMwareInfrastructureproducts,youpurchaselicensesonaperprocessor
basis,whichmeansthatyouneedtoindicatethetotalnumberofprocessors,nothosts,
thatwillruntheproducts.Youcandeployandredeploythepurchasedprocessor
capacity,soldinincrementsoftwoprocessors,onanycombinationofhosts.
Table 3-2. Summary of License Feature Types
Feature
ESX Server or
VirtualCenter
Per-Processor or
Per-Instance
ESX Server ESX Server PerProcessor
VirtualCenter Server VirtualCenter PerInstance
VirtualCenterAgentforESX Server VirtualCenter PerProcessor
VMwareConsolidatedBackup(VCB) ESX Server PerProcessor
ServerVMotionandStorageVMotion VirtualCenter PerProcessor
VMware HA VirtualCenter PerProcessor
VMwareDRSandDPM VirtualCenter PerProcessor
34 VMware, Inc.
For example,youpurchaseESX ServerlicensesfortenprocessorsandVMotionlicenses
forsixprocessors.Youcanthendeploythoselicensesonanyofthefollowing
combinationsofservers:
ESX Serveronfive2processorhosts.EnableVMotiononthreehosts.
ESX Serveronthree2processorhostsandone4processorhost.EnableVMotion
onthree2processorhosts,oronone2processorhostanda4processorhost.
ESX Serverontwo4processorhostsandone2processorhost.EnableVMotionon
one4processorhostandone2processorhost.
ESX Serveronone8processorhostandone2processorhost.VMotionbetween
thesetwohostscannotbeenabledunlessyoupurchaseanadditional4processor
VMotionlicense.
Specialconsiderationsinclude:
Dualcoreandquadcoreprocessors,suchasIntelx86processorsthatcombinetwo
orfourindependentcentralprocessingunitsonasinglechip,countasone
processor.
Youcannotpartiallylicenseamultiprocessorhost.For example,a4CPUhost
requiresalicensewiththecapacityforfourprocessors.
Singleprocessorlicensingissupportedforserverbasedlicenses.Ingeneral,for
serverbasedlicensing,checkoutoflicensesinoddquantitiesissupported.
However,hostbasedfilescannotbegeneratedwithoddquantities.Theymustbe
generatedinmultiplesoftwo.
Thefollowingfeaturesarelicensedonaperprocessorbasis:
ESX ServerTopoweronavirtualmachine,ahostmusthavelicensingona
perprocessorbasis.Thismeansadualprocessorhostrequirestwomatching
ESX Serverlicenses.AfourprocessormachinerequiresfourmatchingESX Server
licenses.See ESX Server 3Editionsonpage 28.
VMwareConsolidatedBackup(VCB)ToleveragethenewConsolidated
BackupcapabilitiesandbackupofallvirtualmachinesrunningonanESX Server
hostaVCBlicensekeymustbeavailableforeachprocessorwithinthathost.
See theVirtualMachineBackupGuideforadescriptionofthisfeature.
VirtualCenterAgentforESX ServerThisagentisinstalledonanESX Server
hostwhenitisaddedtoyourVirtualCenter Server.Youmusthaveoneagent
licensekeyforeachESX Serverprocessortobeaddedtoyour
VirtualCenter Server.
VMware, Inc. 35
ServerVMotionandStorageVMotionTomigrateapoweredonvirtual
machinebetweenhosts,eachESX ServerprocessorinvolvedmusthaveaVMotion
licensekey.For example,ifyouuseVMotionfromadualprocessorESX Server
hosttoanotherdualprocessorhost,youmusthavefourVMotionlicenses.
See BasicSystemAdministration.
VMware HATorestartvirtualmachineswhoseESX Serverhosthasfailed,the
VirtualCenter ServermusthaveanHAlicensekeyforeachESX Serverprocessor
intheHAcluster.See theResourceManagementGuide.
VMwareDRSandDPMToprovideloadbalancingofvirtualmachinesamong
hostsanddistributedpowermanagement,theVirtualCenter Servermusthavea
DRSlicensekeyforeachESX ServerprocessorintheDRScluster.See theResource
ManagementGuide.Asaprerequisite,DRSrequiresappropriateVMotionlicense
keysforallhostsintheDRScluster.
Per-Instance Licensing
Featuresthatarelicensedonaperinstancebasisrequireonlyonelicensekeyper
featureinstance,regardlessofthenumberofprocessorsused.TheVirtualCenter Server
iscurrentlytheonlyfeaturelicensedonaperinstancebasis.
ForinformationondifferenteditionsofVirtualCenter,seeVirtualCenter Server
Editionsonpage 30.
License Expiration Considerations
WhentheFLEXnetlicenseserverexpiresalicense,theVIClientdoesnotimmediately
displayamessageinformingyouthatthelicenseisexpiring.Themessagecanappear
anytimeinthe24hoursaftertheFLEXnetlicenseserverexpiresthelicense.
IfyouchangethelicenseserversystemtimewhiletheVI Clientisrunning,the
VI Clientmightnotreportthelicenseexpiration.
License Server Availability
VMwareprovidesthefollowingmechanismsthathelppreventthelicenseserverfrom
beingasinglepointoffailure.Thelicenseserveractsprimarilyasalicensedistribution
mechanism.Ifyourlicenseserverbecomesunavailable,youcannotissueanynew
licensestoenablenewhostsornewfeatures.
36 VMware, Inc.
However,alllicensedfunctionalitycurrentlyoperatingatthetimethelicenseserver
becomesunavailablecontinuestooperateasfollows:
AllVirtualCenterlicensedfeaturescontinuetooperateindefinitely,relyingona
cachedversionofthelicensestate.ThisincludesnotonlybasicVirtualCenter
operation,butlicensesforVirtualCenteraddons,suchasVMotionandDRS.
ForESX Serverlicensedfeatures,thereisa14daygraceperiodduringwhichhosts
continueoperation,relyingonacachedversionofthelicensestate,evenacross
reboots.Afterthegraceperiodexpires,certainESX Serveroperations,suchas
poweringonvirtualmachines,becomeunavailable.
DuringtheESX Servergraceperiod,whenthelicenseserverisunavailable,the
followingoperationsareunaffected:
Virtualmachinescontinuetorun.VI Clientscanconfigureandoperatevirtual
machines.
ESX Serverhostscontinuetorun.YoucanconnecttoanyESX Serverhostinthe
VirtualCenterinventoryforoperationandmaintenance.Connectionstothe
VirtualCenter Serverremain.VI Clientscanoperateandmaintainvirtual
machinesfromtheirhosteveniftheVirtualCenter Serverconnectionisalsolost.
Duringthegraceperiod,restrictedoperationsinclude:
AddingESX ServerhoststotheVirtualCenterinventory.Youcannotchange
VirtualCenteragentlicensesforhosts.
Addingorremovinghostsfromacluster.Youcannotchangehostmembershipfor
thecurrentVMotion,HA,orDRSconfiguration.
Addingorremovinglicensekeys.
Whenthegraceperiodhasexpired,cachedlicenseinformationisnolongerstored.
Asaresult,virtualmachinescannolongerbepoweredon.Runningvirtualmachines
continuetorunbutcannotberebooted.
Whenthelicenseserverbecomesavailableagain,hostsreconnecttothelicenseserver.
Norebootingormanualactionisrequiredtorestorelicenseavailability.Thegrace
periodtimerisresetwheneverthelicenseserverbecomesavailableagain.
VMware, Inc. 37
Table 33displaysESX Serverlicensedoperationspermittedwhilethelicenseserveris
unavailable.
Operationsthatarenotpermittedareoperationsthatrequiretheacquisitionofnew
licensesfromthelicenseserver.
Table 3-3. Permitted ESX Server Operations When the License Server Is Unavailable
Component Attempted Action
During Grace
Period
After Grace
Period
Expires
Virtualmachine Poweron. Permitted NotPermitted
Createanddelete. Permitted Permitted
Suspendandresume. Permitted Permitted
Configurevirtualmachinewith
VI Client.
Permitted Permitted
ESX Serverhost Continueoperations. Permitted Permitted
Poweronandpoweroff. Permitted Permitted
ConfigureESX Serverhostwith
VI Client.
Permitted Permitted
Modifylicensefileforsinglehost
licensing.
Permitted Permitted
Restartvirtualmachineswithinthe
failedhostsHAcluster.
Permitted NotPermitted
Addorremovelicensekeys. NotPermitted NotPermitted
38 VMware, Inc.
Table 34listsVirtualCenterlicensedoperationsthatarepermittedwhenthelicense
serverisunavailable.
Operationsthatarenotpermittedareoperationsthatrequiretheacquisitionofnew
licensesfromthelicenseserver.
Table 3-4. Permitted VirtualCenter Operations When the License Server Is
Unavailable
Component Attempted Action
When
License
Server Is
Unavailable
VirtualCenter Server RemoveanESX Serverhostfrominventory(seenext
entry).
Permitted
AddanESX Serverhosttoinventory. NotPermitted
Connect/reconnecttoanESX Serverhostin
inventory.
Permitted
Moveapoweredoffvirtualmachinebetweenhosts
ininventory(coldmigration).
Permitted
MoveanESX Serverhostamongfoldersin
inventory.
Permitted
MoveanESX ServerhostoutofaVMotionDRSHA
cluster(seenextentry).
Permitted
MoveanESX ServerhostintoaVMotionDRSHA
cluster.
NotPermitted
ConfiguretheVirtualCenter ServerwithVI Client. Permitted
StartVMotionbetweenhostsininventory. Permitted
ContinueloadbalancingwithinaDRScluster. Permitted
Addorremovelicensekeys. NotPermitted
NOTEIfyoureleaselicensesforlicensedfeatureswhilethelicenseserveris
unavailable,thereleasedlicensescannotberedistributeduntilthelicenseserver
becomesavailableagain.For example,ifyouremovethenetworkadapterassociated
withVMotionwhilethelicenseserverisunavailable,thatVMotionlicenseisreleased
andisunavailableuntilthelicenseserverisavailableagain.Removingahostfromthe
VirtualCenterinventoryorremovingahostfromaclusterhasasimilareffect.
VMware, Inc. 39
TheVirtualCenter Serverusesaheartbeatmechanismtocheckwhetherthelicense
serverisreachableandtodetermineiftherehavebeenanychangesinthelicensefile.
Theheartbeatintervalisfiveminutes.ItmighttaketheVirtualCenter Serveruptofive
minutestodetectiftherearelicensechangesorifthelicenseserverhasbecome
unavailable.
Whenthelicenseserverbecomesunavailable,orifachangeinthelicensefilecausesa
checkedoutlicensetoberemoved,theVirtualCenter Servermarkstheaffectedlicenses
asUnlicensedUse,andthelicensedfeaturescontinuetooperateasdescribedabove.
Whenthelicenseserverbecomesavailableagain,orwhenlicensesarereaddedtothe
licensefile,theVirtualCenter Serverchecksoutthelicensesagainandrevertsthemto
theLicensedstate.Ifalicensecannotbecheckedout,thelicenseremainsinthe
UnlicensedUsestate.
Iflicenseserveravailabilityisaconcerninyourenvironment,consideroneofthe
followingstrategies:
InstallthelicenseserveronthesamemachineastheVirtualCenter Server.Thisis
thedefaultoptionprovidedbytheVirtualCenterinstaller.
Installthelicenseserverinavirtualmachine,andplacethatvirtualmachineinan
HAcluster.VMware HArestartsthelicenseservermachineonanotherESX Server
hostincaseoffailure.
UsesinglehostlicensefilesonESX Serverhosts.
Using an Existing FLEXnet License Server
Inmostcases,VMwarerecommendsinstallingthelicenseserveronthesamemachine
astheVirtualCenter Server.However,ifyouhaveaFLEXnetlicenseserverinyour
environmentprovidinglicensesforotherproducts,installtheVMwarelicenseserver
onthatsystem.
ToinstalltheVMwarelicenseserveronyourexistingFLEXnetserver,usethe
standalonelicenseserverinstallerasdescribedinInstallingaLicenseServeron
page 60.ThisinstallstheVMwarelicenseservervendordaemon,whichcancoexist
withothervendordaemonsinstalledontheserver.
NOTETheVMwarelicenseserverissupportedonlyonWindowsoperatingsystems.
YoucannotinstalltheVMwarelicenseserveronaLinuxbasedFLEXnetserver.
See LicenseServerSoftwareRequirementsonpage 21.
40 VMware, Inc.
Contacting Support
Ifyourequireassistancewithlicensing,contactVMwareforsupportasfollows:
IfyouhavenotreceivedlicenseactivationcodesforyourVI3purchaseorhave
difficultiesusingyourlicenseactivationcodestoobtainlicensefiles,sendemailto
vihotline@vmware.com.
Ifyouobtainlicensefilesandhavedifficultiesconfiguringortroubleshooting
licensedfeatures,fileasupportrequestathttp://www.vmware.com/support.
VMware, Inc. 41
4
ThischapterprovidesinformationonhowtoinstallandrunVirtualCenter 2.5and
ESX Server 3.5inanevaluationmodeandhowtoobtainlicenseswhentheevaluation
modeexpires.
UsingESX ServerandVirtualCenterinEvaluationModeonpage 41
LicensingVirtualCenterandESX ServerAftertheEvaluationPeriodExpireson
page 42
Using ESX Server and VirtualCenter in Evaluation Mode
BeforepurchasingandactivatinglicensesforyourESX Server 3.5and
VirtualCenter 2.5,youcaninstallbothproductsandruntheminevaluationmode.
Whenruninevaluationmode,intendedfordemonstrationandevaluationpurposes,
yoursoftwareiscompletelyoperationalimmediatelyafterinstallation,doesnotrequire
anylicensingconfiguration,andprovidesfullfunctionalityofESX Serverand
VirtualCenterfor60daysfromthetimeyouinstallthem.
Duringthe60dayevaluationperiod,thesoftwarenotifiesyouofthetimeremaining
untiltheevaluationexpires.Theevaluationperiodcannotbepausedanditcannotbe
restarted.
Running VMware
VirtualCenter and
VMware ESX Server
in Evaluation Mode 4
42 VMware, Inc.
Licensing VirtualCenter and ESX Server After the
Evaluation Period Expires
Afterthe60dayevaluationperiodexpires,unlessyouobtainlicensesforyour
software,youarenolongerabletoperformmostoperationsinVirtualCenterand
ESX Server.For example,youcannotpoweronvirtualmachines,addnewhosts,oruse
advancedESX ServerandVirtualCenterfeatures.
IfyoudonotlicenseVirtualCenterbeforetheevaluationperiodexpires,allofthehosts
intheVirtualCenterinventoryaredisconnected.
Table 41detailstheESX Serverbehaviorafterevaluationmodeexpires.Theoperations
thatarenotpermittedrequiretheacquisitionofnewlicenses.
NOTEReinstallingtheVirtualCenter Serverafterthe60dayevaluationexpiresdoes
notrestarttheevaluationperiodfromthebeginning.
Table 4-1. ESX Server Operations After the 60-Day Evaluation Period
Component Attempted Action After 60 Days
Virtualmachine Poweron NotPermitted
Create/delete Permitted
Suspend/resume Permitted
ConfigurevirtualmachinewithVI Client Permitted
ESX Serverhost Continueoperationsonexistinghosts Permitted
Poweron/poweroff Permitted
ConfigureESX ServerhostwithVI Client Permitted
Restartvirtualmachineswithinthefailed
hostsHAcluster
NotPermitted
Addorremovelicensekeys Permitted
VMware, Inc. 43
Chapter 4 Running VMware VirtualCenter and VMware ESX Server in Evaluation Mode
Considerations When You Switch ESX Server and VirtualCenter
to Licensed Modes
WhenyouswitchyourVirtualCenterandESX Serverfromevaluationmodetothe
licensedmode,considerthefollowing:
IfthenumberofESX Serverhostsyouaddtoyourinventoryexceedsthenumber
allowedbyyourcurrentlicensingtype,youcannolongermanagetheexcesshosts.
DeletetheextrahostsfromtheVirtualCenterinventoryorusetheVI Clientto
directlyaccessthehostsandconfiguretheirlicensing.
Haveallrequiredlicensesonyourlicenseserver,otherwiseyouwillnotbeableto
useallfeaturesavailabletoyouduringthe60dayevaluation.
44 VMware, Inc.
VMware, Inc. 45
5
Thischapterprovidesproceduresforredeeminglicensefilesandconfiguringlicense
options.
LicensingProcessonpage 46
ObtainingLicenseFilesonpage 48
SettingUpCentralizedLicensingonpage 49
SettingUpSingleHostLicensingonpage 53
LicenseFileContentsonpage 56
LicenseFileLocationsonpage 58
AddingNewLicenseFilestoLicenseServersonpage 59
AddingNewLicenseFilestoSingleHostsonpage 60
InstallingaLicenseServeronpage 60
TroubleshootingLicensingonpage 61
Licensing VirtualCenter and
ESX Server 5
46 VMware, Inc.
Licensing Process
Figure 51summarizesthelicenseconfigurationprocessesforESX Server 3.
Figure 5-1. License Configuration Process for ESX Server 3
ESX Server 3
host is licensed
Purchase and install
ESX Server 3
Power on
the host
Use in
evaluation mode
Set the edition and
add-on licenses
Install a local file
on the disk
(/etc/vmware/)
Change to
licensed mode?
Install a
license server or
enter path to .lic file
Served Local
VMware, Inc. 47
Chapter 5 Licensing VirtualCenter and ESX Server
Figure 52summarizesthelicenseconfigurationprocessesfortheVirtualCenter Server.
Figure 5-2. License Configuration Process for the VirtualCenter Server
Purchase licenses
Yes
Yes
No
Receive email from
VMware or VMware
partner
VirtualCenter is
licensed
Follow email instructions
to redeem licenses
Run installer
Deselect Evaluation
check box
Acquire VirtualCenter
installer
Run installer
Select Evaluation
check box
Install license server
Select license file
containing purchased
licenses
(optional)
Change license server
configuration
Enter path to existing
license server and your
VirtualCenter Server
edition
Copy purchased
licenses to license
directory
Evaluate
VirtualCenter?
Install
license server?
VirtualCenter
60-day evaluation
No
48 VMware, Inc.
AfteryoupurchaseVMwareInfrastructuresoftware,dothefollowingtoobtainanduse
yourlicenses:
1 Decidewhichlicensingmodeltouse.
VMwareInfrastructure3usesFLEXnetlicensing,whichoffersachoiceoflicense
types:centralized,singlehost,ormixed.See SingleHostandCentralizedLicense
Typesonpage 30.
2 Registeryourpurchase.
WhetheryoupurchasedVMwareInfrastructure 3fromanauthorizedVMware
resellerordirectlyfromVMware,registeryourpurchasetoyourVMwarestore
account.See ObtainingLicenseFilesonpage 48.
3 Obtainlicensefiles.
Afteryouregisteryourpurchase,usetheWebbasedlicenseactivationportalto
generateanddownloadlicensefilesappropriatetothelicensingmodelyouchose
inStep 1.See ObtainingLicenseFilesonpage 48.
4 InstallVirtualCenterandESX Server.
5 ConfigureyourlicensingaccordingtothelicensetypeyouchoseinStep 1:
Toconfigurecentralizedlicensing,see SettingUpCentralizedLicensingon
page 49.
Toconfiguresinglehostlicensing,see SettingUpSingleHostLicensingon
page 53.
Toconfigureamixedlicenseenvironment,see SingleHostandCentralized
LicensingintheSameEnvironmentonpage 54.
Obtaining License Files
Theprocessofobtaininglicensefilesvariesdependingonhowyoumadeyour
purchaseofVMwareInfrastructure 3.Thefirststepinobtaininglicensefilesistoobtain
oneormorelicenseactivationcodes,whichyoureceiveinoneofthreeways:
IfyoupurchasedVMwareInfrastructure3fromanauthorizedVMwarereseller,
suchasDell,HewlettPackard,orIBM,youreceiveanemailmessagecontaining
instructionsonhowtoredeemandactivateyourlicenses.Enterthepartner
activationcodeintothepartneractivationportaltoregisteryourpurchase.
ForothernewpurchasesofVMwareInfrastructure 3,youreceiveanemail
containingalicenseactivationcode.
VMware, Inc. 49
Whenyoureceivetheemailcontainingyouractivationcodes,followtheinstructionsin
theemailtoregisterlicenseactivationcodesandgeneratelicensefilesthroughthe
Webbasedlicenseactivationportal.
Foradditionalinformationonthelicenseactivationprocess,seethelicenseactivation
portalonlineHelp.
Setting Up Centralized Licensing
Youcanconfigurecentralizedlicensingatinstallationtime.Afterinstallation,youcan
makechangestolicensingthroughtheVI Client.
Installing License Files
Afteryouobtainyourlicensefiles,savethemasplaintextASCIIfilesinadirectoryyou
canaccessfromyourlicenseservermachine.Usethe.lic extensionwhensavingyour
licensefiles.
WhentheVMwarelicenseserverisinstalled,youcanimportthefilesintoyourlicense
server.Centralizedlicensefilesareplacedatthefollowingdefaultlocationonthe
machinerunningthelicenseserver:
C:\Program Files\VMware\VMware License Server\Licenses
See InstallingaLicenseServeronpage 60forinstructionsoninstallingastandalone
licenseserver.
See InstallingVMwareInfrastructureManagementSoftwareonpage 72for
instructionsregardingtherecommendedlicenseserverinstallation.
Location of the License Server
VMwarerecommendsthatyoufollowthedefaultinstallationandplaceyourlicense
serveronthesamemachineasyourVirtualCenter Server.Thishastheadvantageof
simplicityofsetup,aswellasguaranteeingVirtualCentertolicenseserver
communications.Changethisonlyifyouhaveagoodreason,suchasanexisting
FLEXnetlicenseserver.Toaccessthelicenseserverdocumentation,choose:
Start>Programs>VMware>VMware License Server>VMwareLicenseServerUser
Guide.
NOTEThefileextension.lic isrequired.
50 VMware, Inc.
Configuring License Server Licensing
ThefirstprocedureinthissectiondescribesVirtualCentercentralizedlicensing
configuration.IfyourenvironmentusesthedefaultVirtualCenterinstallation,orifyou
havenoVirtualCenter Server,godirectlytoToconfigurecentralizedlicensingforan
ESX Serverhostonpage 51.
To configure centralized licensing for the VirtualCenter Server
1 FromtheVI Client,chooseAdministration>VirtualCenterManagementServer
Configuration.
2 ClickLicenseServerinthelistontheleft.
3 ClicktheUsetheFollowingLicenseServerbutton.
4 Tosetthelicenseserver:
a ClickEdittotherightofLicenseSources.
b ClickUseLicenseServer.
Thisisthedefaultconfiguration.
c EntertheportnumberandlicenseservermachinenameintheAddressfield,
asinport@host.
Forexample,withthedefaultlicenseserverport27000onalicenseserver
calledlicense1,yourentrymightlooklikethis:
27000@license-1.vmware.com
d ClickOKtoclosethedialogboxandsaveyourchanges.
5 (Optional)IfyoudonotwantVirtualCentertooverridethehostscurrentlicense
setting,deselectthecheckboxforChangehostlicenseserversettingstomatch
VirtualCenterssettingwhentheyareaddedtoinventory.
SelectingthischeckboxcausestheVirtualCenter Servertooverridethehosts
currentlicensesettingandinsteadusethelicenseserverusedbyVirtualCenter.
6 ClickOKtosaveyourchanges.
Youdonothavetochangeanyothersettingstoenablecentralizedlicensing.
Thetotalnumberoflicensesconsumedandavailableonthelicenseserverare
summarizedontheLicensestabintheAdminviewoftheVI Clientconnectedtothe
VirtualCenter Server.(ThistabwaslabeledLicenseViewerinearlierversionsof
VirtualCenter.)
VMware, Inc. 51
Ifyoudidnotselectthecheckboxfortheoptionalsetting,followtheprocedureinthe
nextsectiontomanuallyconfigureESX Serverhoststousecentralizedlicensing.
To configure centralized licensing for an ESX Server host
1 FromtheVI Client,selectthehostintheinventory.
2 ClicktheConfigurationtab.
3 UnderSoftware,clickLicensedFeatures.
4 Tosetthelicenseserver:
a ClickEdittotherightofLicenseSources.
TheLicenseSourcesdialogboxappears.
b ClicktheUseLicenseServerbutton.
Thisisthedefaultconfiguration.
c Enterthelicenseservermachinenameand,optionally,aportintotheAddress
field.Ifyoudonotspecifyaport,thedefaultport,27000,isused.
For example,withthedefaultlicenseserverport27000 onalicenseserver
called license-1,yourentrymightlooklikethis:
license-1.vmware.com:27000
d ClickOKtoclosethedialogboxandsaveyourchanges.
5 SettheESX Serveredition:
a ClickEdittotherightofESX ServerLicenseType.
b Specifytheeditionforthehost,orselectUnlicensedtoreleasethishosts
licensesbacktothelicenseserver.TheESX ServerLicenseTypedialogbox
displaysonlythoseeditionsthatareavailabletoyourESX Serverhost.
c ClickOKtoclosethedialogboxandsaveyourchanges.
6 Toconfigureaddonlicenses:
a ClickEdittotherightofAddOns.
TheAddOnsdialogboxappears.
b SelecttheaddonproductsyouwanttouseandclickOK.
VirtualCenter.)
52 VMware, Inc.
To configure local license server licensing for the VirtualCenter Server
1 FromtheVI Client,chooseAdministration>VirtualCenterManagementServer
Configuration.
3 ClicktheUselicenseservicesonthisVirtualCenter Serverbutton.
4 (Optional)IfyoudonotwantVirtualCentertooverridethehostscurrentlicense
setting,deselectthecheckboxforChangehostlicenseserversettingstomatch
SelectingthischeckboxcausestheVirtualCenter Servertooverridethehosts
currentlicensesettingandinsteadusethelicenseserverusedbyVirtualCenter.
MakesurethatyouuseanIPaddressthatisaccessiblefromtheESX Serverhost.
IfyouconfigureVirtualCentertousealocallicenseserverandthehostnameofthe
locallicenseserver(VirtualCentershost)isnotresolvablefromtheESX Server
host,theESX Serverhostisnotabletoacquirelicensesfromthelocallicenseserver.
Youdonothavetochangeanyothersettingstoenablelocallicenseserver
licensing.
VirtualCenter.)
Changing the Default License Server Ports
Bydefault,VirtualCenterandESX ServersoftwareisconfiguredtouseTCP/IPports
27000and27010tocommunicatewiththelicenseserver.Ifyoudidnotusethedefault
portsduringlicenseserverinstallation,youmustupdatetheconfigurationoneach
ESX Serverhost.
Ifyouchangethedefaultportsforthelicenseserver,logintotheESX Serverhost
serviceconsoleandopentheportsyouwant.
NOTEIfyoudidnotselectthecheckboxfortheoptionalsetting,followtheprocedure
inToconfigurecentralizedlicensingforanESX Serverhostonpage 51tomanually
configureESX Serverhoststouselicenseserverlicensing.
VMware, Inc. 53
To open a specific port in the service console firewall
1 Logintotheserviceconsoleastherootuser.
2 Executethiscommand:
esxcfg-firewall --openPort <portnumber>,tcp,out,"License Server"
Changing from Single-Host to Centralized Licensing
YoucanchangeyourESX Serverhostsfromsinglehostlicensingtocentralized
licensing.Youmustgenerateanewlicensefile,installalicenseserver(ifyoudonot
haveoneinstalled),andconfigureyourhoststousethenewlicensetype.
To change ESX Server hosts from single-host licensing to centralized licensing
1 UsetheVMwarelicenseactivationportaltogenerateanddownloadanew
centralizedlicensefilecontainingallthelicensesforyourESX Serverhostsandany
associatedVirtualCenter Serverfeatures.
Thelicenseactivationportalletsyougeneratebothsinglehostandcentralized
licensefilesfromthesamelicenseactivationcode.
2 Ifyouhavenotinstalledalicenseserver,dosoasfollows:
TouseaFLEXnetlicenseserverinstalledinyourenvironment,see Usingan
ExistingFLEXnetLicenseServeronpage 39.
Toinstallastandalonelicenseserver,see InstallingaLicenseServeron
page 60.
ToinstallalicenseserveraspartofaVirtualCenterinstallation,see Chapter 6,
InstallingVMwareInfrastructureManagement,onpage 65.
3 ConfigureyourVirtualCenter ServerandESX Serverhostsasdescribedin
ConfiguringLicenseServerLicensingonpage 50.
Setting Up Single-Host Licensing
SinglehostlicensingrequiresavalidlicensefileoneachESX Serverhost.
Configuring an ESX Server Machine for Single-Host Licensing
Whenyoureceiveyourlicensefile,renameittovmware.licandplaceitonafile
systemyoucanaccessfromyourVI Client.
NOTEThefileextension.lic isrequired.
54 VMware, Inc.
To use the VI Client to configure single-host licensing
1 FromtheVI Client,selectthehostintheinventory.
2 ClicktheConfigurationtab.
3 UnderSoftware,clickLicensedFeatures.
4 ClickEdittotherightofLicenseSources.
TheLicenseSourcesdialogboxappears.
5 ClicktheUseHostLicenseFilebutton.
6 ClickBrowseandlocatethelicensefile.
Thisfilemustbelocatedontheclientmachine,notontheESX Serverhost.License
filesmusthavea.lic extensionappearinthefilebrowser.
Single-Host and Centralized Licensing in the Same
Environment
UsingsinglehostlicensesforESX Serverfeaturesandcentralizedlicensingfor
VirtualCenterfeaturesinthesameenvironmentispermitted.However,doingso
requireschangestothedefaultVirtualCenterconfigurationsettings.Ifyoudonot
changetheVirtualCentersettings,thesettingscanoverridesinglehostlicensefiles:
WhentheVirtualCenter Serverrestarts.
WhenthesinglehostESX Servermachinesareaddedtoinventoryagain.
AnysinglehostlicensefileontheESX Servermachineremainsunchangedbutignored.
To change VirtualCenter settings to allow single-host ESX Server licensing
1 FromtheVI Client,chooseAdministration>ServerSettings.
3 DeselectthecheckboxforChangehostlicenseserversettingstomatch
CAUTIONIfyourestoreanESX Servermachinetosinglehostlicensingwithout
changingtheVirtualCenterdefaultconfiguration,theVirtualCenter Serversettings
mightoverridethesinglehostsettingsontheESX Servermachine.
VMware, Inc. 55
5 RemoveandAddanyaffectedESX Servermachineintheinventory.
NowitissafetoreconfiguresinglehostlicensingonanychangedESX Server
machines.
Configuring Licensing for a Mixed ESX Server 2.x and
ESX Server 3.x Environment
YoucanusetheVirtualCenter Server2.xtomanageamixedenvironmentofboth
ESX Server 2.xandESX Server 3.xhosts.Youreceivelicenseactivationcodeswith
purchasesofVMwareInfrastructure 3StandardeditionandVMwareInfrastructure 3
EnterpriseeditionthatcanberedeemedforbothESX Server 2.xserialnumbersandfor
VMwareInfrastructure 3licensefiles.
To configure licensing for the ESX Server 2.x hosts in the mixed environment
1 LeavethelicensingonexistingESX Server 2.xhostsusingserialnumbers
unchanged.
2 FornewESX Server 2.xinstallations,redeemyourlicenseactivationcode(s)onthe
licenseactivationportalforESX Server 2.xserialnumbers.
Providetheseserialnumbersatthetimeofinstallationorconfiguration.
3 Redeemyourlicenseactivationcode(s)togenerateacentralizedlicensefile
containinglicensesforVirtualCenter Server,VirtualCenterManagementAgents,
VMotion,andESX Server 3.x.
YourgeneratedlicensefilecanincludeESX Server 3.xlicensesforthe
ESX Server 2.xhostsforwhichyouobtainedESX Server 2.xserialnumbersin
Step 2.Thisletsyoudistributelicensestothesehostsiftheyarelaterupgradedto
ESX Server 3.x.
4 InstallandconfiguretheVirtualCenter Server2.xtousethecentralizedlicensefile
yougenerated.
See Chapter 6,InstallingVMwareInfrastructureManagement,onpage 65.
56 VMware, Inc.
Changing from Centralized to Single-Host Licensing
YoucanchangeyourESX Serverhostsfromthecentralizedlicensetypetothe
singlehostlicensetype.TheVirtualCenter Serverandadditionalfeaturessuchas
VMotion,VMwareDRS,andVMware HAmustremainincentralizedmode.Tochange
thelicensetypeforyourESX Serverhosts,generatenewlicensefilesforeachhostand
configurethehoststousethenewlicensetype.
To change ESX Server hosts from a centralized license to a single-host license
1 UsetheVMwarelicenseactivationportaltogenerateanddownloadnew
singlehostlicensefilesforeachESX Serverhost.
Thelicenseactivationportalletsyougeneratebothsinglehostandcentralized
licensefilesfromthesamelicenseactivationcode.Forsinglehostlicensing,you
needonelicensefileforeachindividualESX Serverhost.
2 IfyouareusingtheVirtualCenter Server,changeyourVirtualCenter Server
settingssothattheVirtualCenter Serverdoesnotoverridehostlicensesettings,as
describedinSingleHostandCentralizedLicensingintheSameEnvironmenton
page 54.
3 ConfigureyourESX ServerhostasdescribedinConfiguringanESX Server
MachineforSingleHostLicensingonpage 53.
License File Contents
Licensefilesaretextfilescontainingtwotypesofinformation:licensetypeandlicense
keys.
LicensetypeSpecifiestheTCP/IPportsthelicenseserverusestocommunicatewith
ESX Serverhosts.VMwarerecommendsthatyounotmodifythesedefaultports.Ifyou
doneedtoedittheports,useanASCIItexteditorandvalidateyoureditedlicenseat
http://www.vmware.com/checklicense/.
Alicensetypeheaderlookssimilartothefollowing:
SERVER this_host ANY 27000
VENDOR VMWARELM port=27010
USE SERVER
Thissectionappearsonlyinalicenseserverfileandindicatesthatlicensekeysshould
beservedonalicenseserver.Thereisnomodesectioninsinglehostlicensefiles.
VMware, Inc. 57
LicensekeyContainsencryptedlicensekeys,oneforeachfeaturetowhichyouare
entitled.Table 51liststheavailablelicensekeys.
Centralizedfilesandsinglehostfilesaredifferentiatedbytwofeatures:
Singlehostlicensefilescontainnolicensetypesection.Centralizedfilescontaina
licensetypesectionasthefileheader.
SinglehostlicensefilescontainthestringlicenseType=Hostaspartofeach
licensekeyblockinthefile.Centralizedlicensefilescontainthestring
licenseType=Serveraspartofeachlicensekeyblockinthefile,asshowninthe
examplesbelow.
Example 51showsatypicalsinglehostlicensekey.
Table 5-1. License Keys
Feature Name License File Key License Type Available
ESX ServerFoundationedition PROD_ESX_STARTER Centralizedorsinglehost
ESX ServerStandardedition
ESX ServerEnterpriseedition
PROD_ESX_FULL Centralizedorsinglehost
VMwareConsolidatedBackup ESX_FULL_BACKUP Centralizedorsinglehost
VirtualCenter ServerFoundation PROD_VC_EXPRESS Centralizedonly
VirtualCenter Server PROD_VC Centralizedonly
VirtualCenterManagementAgent VC_ESXHOST Centralizedonly
VMwareServerVMotion
VMwareStorageVMotion
VC_VMOTION Centralizedonly
VMwareDRS
VMwareDPM
VC_DRS Centralizedonly
VMware HA VC_DAS Centralizedonly
Example 5-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 ..."
58 VMware, Inc.
Example 52showsatypicalcentralizedlicensekey.
License File Locations
AlicensefileresidesoneveryESX Servermachineoreverylicenseserver,depending
onwhetheryouusecentralizedorsinglehostlicensing:
Centralizedlicensefilesareplacedatthefollowingdefaultlocationonthe
machinerunningtheVMwarelicenseserver:
Youcanaddnewlicensefilestothelicensedirectory.See AddingNewLicense
FilestoLicenseServersonpage 59.
Singlehostlicensefilesareplacedatthefollowingdefaultlocationonthe
machinerunningESX Server.
/etc/vmware/vmware.lic
Youcanaddnewlicensestothesinglehostbyusingthelicenseactivationportal.
See AddingNewLicenseFilestoSingleHostsonpage 60.
Example 5-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 ..."
NOTEInVirtualCenter 2.0,thedefaultlocationofthelicensefilewas
C:\Documents and Settings\All Users\Application Data\VMware\
VMware License Server\vmware.lic.Thislocationnolongerexists.
NOTEIncentralizedmode,thisfileexistsontheESX Servermachinebutcontains
nolicensekeys.
VMware, Inc. 59
Adding New License Files to License Servers
Thelicenseserversupportsalicensedirectoryformultiplelicensefiles.Ifyouobtained
multiplelicensefiles(for example,fromseparateorders)andwanttomanageallthese
licensesfromthesamelicenseserver,addthemtothelicenseserverdirectoryand
restarttheserver.
To add new licenses to the license server directory
1 Addthenewlicensefiletothefollowingdefaultdirectoryonthemachinerunning
theVMwarelicenseserver:
2 RestarttheVMwareLicenseServerservice.
ThefollowingsequenceisforWindows2000Professional.Themenusandcommands
forotherversionsofWindowscanvary.
To restart the license server Windows Service
1 ChooseStart>Settings>ControlPanel.
2 DoubleclickAdministrativeTools.
3 DoubleclickServices.
4 ScrollandrightclickVMwareLicenseServer.
5 ChooseRestartfromthepopupmenu.
Youcanchangethedefaultlocationofyourcentralizeddirectory,oryourlicensefile.
To change the default location of the license directory
1 Onthecomputerthatrunsthelicenseserverapplication,launchVMwareLicense
ServerToolsbychoosingStart>Programs>VMware>VMwareLicenseServer>
VMwareLicenseServerTools.
2 ClicktheConfigServicestab.
3 ClickBrowsenexttothePathtolicensefilefield,andchoosealicensefilefrom
thelicensedirectory.
Ifyouwantthelicenseservertousetheentirelicensedirectory,manuallyremove
thenameofthefileleavingonlythenameofthedirectory.
4 ClicktheStart/Stop/Rereadtab.
5 ClickStop.
60 VMware, Inc.
6 ClickStart.
7 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 48.
Installing a License Server
Thissectiondescribesanindependentinstallationofthelicenseserver.Skipthissection
ifyouareusingtheVMwareInfrastructureManagementinstaller,asdescribedin
InstallingVMwareInfrastructureManagementSoftwareonpage 72.TheVMware
InfrastructureManagementinstallerinstallsalicenseserver.
Tocheckwhetheralicenseserverisinstalled,selectStart>Programs>VMwareand
lookforVMwareLicenseServer.Ifalicenseserverisinstalled,VMwarerecommends
reinstallingorupgradingthelicenseservertothelatestversion.
InstallthelicenseserveronthesamemachinewheretheVirtualCenter Serverresides,
oronaseparatemachine.Toensurethebestlicensepoolavailability,VMware
recommendsinstallingthelicenseserveronthesamemachinewherethe
VirtualCenter Serverresides.
Usethisprocedurewithanyinstallationwhenyouwanttohaveastandalonelicense
serveronamachineotherthanyourVirtualCenter Serverhost.
ToinstalltheVMwarelicenseserversoftware,youmusthave:
HardwarethatmeetsSystemRequirementsonpage 17.
AstaticIPaddressormachinenametobeusedbyyourlicenseserver.
ThefollowingprocedureassumesthatyouhaveAdministratorprivilegesona
Windowssystem.
VMware, Inc. 61
To install a VMware license server
1 InserttheVMwareInfrastructureInstallationCD.
IftheVMwareInfrastructureManagementInstallerappears,clickcanceltoexit.
2 Navigatetothe\vpxfolderontheinstallationCDanddoubleclick
VMwarelicenseserver.exe.
3 VerifythatyouareinstallingthelicenseserverandclickNext.
4 Toacceptthelicenseagreement,selectIacceptthetermsinthelicenseagreement
andclickNext.
5 SelectthefolderinwhichyouwanttoinstallthelicenseserverandclickNext.
6 TypethefullpathtoyourlicensefileorclickBrowsetolocatethisfileandclick
Next.
Thelicensefileshouldbelocatedinadirectoryyoucanaccessfromyourlicense
servermachine.
7 ClickInstalltobegintheinstallation.
8 ClickFinishtocompletethelicenseserverinstallation.
Afteryouinstallthelicenseserver,youcanaccessinformationaboutusingand
configuringtheserverbyclickingStart>Programs>VMware>VMwareLicense
Server>VMwareLicenseServerUserGuide.
See alsoObtainingLicenseFilesonpage 48andInstallingLicenseFilesonpage 49.
Troubleshooting Licensing
Thissectionprovidesguidelinesfortroubleshootingyourlicensesetup.Ifyoucannot
resolveyourproblemsusingtheinformationgiveninthissection,contactVMwarefor
supportasfollows:
IfyouhavenotreceivedlicenseactivationcodesforyourVI3purchaseorhave
difficultiesinusingyourlicenseactivationcodestoobtainlicensefiles,sendemail
tovihotline@vmware.com.
Ifyouobtainedlicensefilesandhavedifficultiesinconfiguringortroubleshooting
licensedfeatures,fileasupportrequestathttp://www.vmware.com/support.
62 VMware, Inc.
Receiving License Activation Codes
VMwaresendslicenseactivationcodesandlicensinginformationtothelicense
administratorlistedforaparticularpurchase.Ifyouarenotthelicenseadministrator,
contactyourorganizationslicenseadministratorforyourlicenseactivationcodes.
Ifyouneedtochangethelicenseadministratorforyourorder,contact
vihotline@vmware.com.Includetherelevantordernumbersinyouremail.
IfyoupurchasesVMwareInfrastructure 3fromanauthorizedVMwarereseller,
registeryourpurchaseusingthepartneractivationcode(s)suppliedbythepartnerto
generateyourlicensefiles.
Checking the License Server
Ifyouarehavingtroublecommunicatingwithyourlicenseserver,checkthefollowing:
CheckthatthelicenseserverWindowsserviceisrunning.
Checkthatlicenseserverislistening.
Checkthelicenseserverstatus.
To check that the license server Windows service is running
1 Onthemachineonwhichthelicenseserverisinstalled,chooseStart>Control
Panel>AdministrativeTools>ServicestodisplaytheServicescontrolpanel.
2 VerifythattheStatuscolumnfortheVMwareLicenseServerentryreadsStarted.
3 IftheVMwareLicenseServerisnotstarted,rightclicktheserviceandchoose
Start.
VMware, Inc. 63
To check that the license server is listening
1 Onthemachineonwhichthelicenseserverisinstalled,chooseStart>Command
Prompt.
2 Typenetstat -abatthecommandline.
3 Verifythatthelmgrd.exeprocessislisteningonport27000andthatthe
VMWARELM.exeprocessislisteningonport27010.
Ifnot,thelicenseservermightnotbeinstalledormightnotbestarted.
To check the license server status
1 Onthemachineonwhichthelicenseserverisinstalled,chooseStart>Programs>
VMware>VMwareLicenseServer>VMwareLicenseServerToolstolaunchthe
LMTOOLSutility.
2 ClicktheServerStatustabtodisplaytheServerStatuspage.
3 ClickPerformStatusInquiry.
Licenseserverinformation,includingthelocationofthelicensefile,appearsatthe
bottomofthepage.
64 VMware, Inc.
Checking the License File
Ifyourlicenseserverisoperatingproperlyorifyouareusingsinglehostlicensing,but
youcannotuselicensedfeatures,youhaveaproblemwithyourlicensefile.Checkthe
following:
Validateyourlicensefileathttp://www.vmware.com/checklicense/.
Ensurethatyouareusingthecorrecttypeoflicensefile.Ifyouareusingalicense
server,useacentralizedfile.Ifyouareusingsinglehostlicensing,makesurethat
youareusingasinglehostlicensefileoneachhost.
Centralizedfilescontainablockofheadertextatthetop,andthestring
VENDOR_STRING=licenseType=Serverappearsineachlicensekeyinthefile.
Singlehostlicensefileshavenoheadertext,andthestring
VENDOR_STRING=licenseType=Hostappearsineachlicensekeyinthefile.
Ifyouareusingacentralizedlicensefile,checkthatthelicensetypeheader
informationappearsonlyonceandatthetopofthefile.
Checkthatthelicensefilecontainsthecorrectkeysforthefeaturesyouwanttouse.
See Table 51,LicenseKeys,onpage 57foralistofkeys.
Ifyoueditedthelicensefile,checkthatyoudidnotmixcentralizedandsinglehost
keysinasinglefile.
Checking License Configuration
Ifyourlicenseserver(ifused)isworkingcorrectly,andyourlicensefileiscorrect,check
thatyoucorrectlyconfiguredlicensingforyourhostsusingtheVI Client:
Ifyouareusingcentralizedlicensing,followtheinstructionsinConfiguring
LicenseServerLicensingonpage 50.
Ifyouareusingsinglehostlicensing,followtheinstructionsConfiguringan
ESX ServerMachineforSingleHostLicensingonpage 53.
VMware, Inc. 65
6
ThischapterdescribeshowtoprepareyourVirtualCenterdatabase,installVMware
InfrastructureManagementsoftware,andconfigurecommunicationbetween
components.YoucaninstallVMwareInfrastructureManagementsoftwareona
physicalsystemoronavirtualmachinerunningonanESX Server 3host.
PreparingtheVirtualCenter ServerDatabaseonpage 65
InstallingVMwareInfrastructureManagementSoftwareonpage 72
ConfiguringCommunicationBetweenVirtualCenterComponentsonpage 76
UninstallingVMwareInfrastructureComponentsonpage 78
InstallingVirtualCenterinaVirtualMachineonpage 79
Preparing the VirtualCenter Server Database
TheVMwareVirtualCenter Serverrequiresadatabasetostoreandorganizeserver
data.VirtualCenterversion 2serversupportsOracle,SQLServer,andMicrosoftSQL
Server2005Express.
VirtualCenterrequiresadministrationcredentials(IDandpassword)tologintoan
OracleorSQLdatabase.ContactyourDBAforthesecredentials,orinstallthebundled
MicrosoftSQLServer2005Expressdatabase.
Installing VMware
Infrastructure Management 6
NOTEMicrosoftSQLServer2005Expressisintendedtobeusedforsmalldeployments
ofupto5hostsand50virtualmachines.
66 VMware, Inc.
Thedatabasetopicsarecoveredinthefollowingsections:
ConfiguringanOracleConnectiontoWorkLocallyonpage 66
ConfiguringanOracleConnectiontoWorkRemotelyonpage 67
ConfiguringaSQLServerODBCConnectiononpage 68
ConfiguringMicrosoftSQLServer2005Expressonpage 71
MaintainingYourVirtualCenterDatabaseonpage 72
Configuring an Oracle Connection to Work Locally
TouseanOracledatabaseasyourVirtualCenterdatabaseandhaveVirtualCenter
accessthedatabaselocally,usethefollowingprocedure.
Beforeyoubeginthisprocedure,reviewtherequireddatabasepatchesspecifiedin
Table 21,SupportedDatabaseFormats,onpage 19.Ifyoudonotprepareyour
databasecorrectly,theVirtualCenterinstallermightdisplayerrorandwarning
messages.
To prepare an Oracle database to work locally with VirtualCenter
1 DownloadOracle9iorOracle10gfromtheOracleWebsite,installit,andcreatea
database(VirtualCenter).
2 DownloadOracleODBCfromtheOracleWebsiteifyouareusingOracle9i.Ifyou
downloadedOracle10g,theODBCisincludedintheproductmedia.
3 InstalltheOracleODBCcorrespondingdriverthroughtheOracleUniversal
Installer(directionsareprovidedwiththedriver).
4 Increasethenumberofopencursorsforthedatabase.Addtheentry
open_cursors = 300totheC:\Oracle\ADMIN\VPX\pfile\init.orafile.
VMware, Inc. 67
Chapter 6 Installing VMware Infrastructure Management
To connect Oracle locally
1 CreateanewtablespacespecificallyforVirtualCenterusingthefollowingSQL
statement:
CREATE TABLESPACE "VPX" DATAFILE 'C:\Oracle\ORADATA\VPX\VPX.dat'
SIZE 1000M AUTOEXTEND ON NEXT 500K;
2 Createauser,suchasvpxAdmin,foraccessingthistablespacethroughODBC:
CREATE USER vpxAdmin IDENTIFIED BY vpxadmin DEFAULT TABLESPACE vpx;
3 Eithergrantdbapermissiontotheuser,orgrantthefollowingpermissionstothe
user:
grant connect to <user>
grant resource to <user>
grant create view to <user>
grant create any sequence to <user> # For VirtualCenter upgrade only
grant create any table to <user> # For VirtualCenter upgrade only
grant execute on dbms_job to <user>
grant execute on dbms_lock to <user>
grant unlimited tablespace to <user> # To ensure space limitation is not
an issue
4 CreateanODBCconnectiontothedatabase.Thefollowingareexamplesettings:
Data Source Name: VMware VirtualCenter
TNS Service Name: VPX
User Id: vpxAdmin
Configuring an Oracle Connection to Work Remotely
TouseanOracledatabaseasyourVirtualCenterdatabaseandhaveVirtualCenter
accessthedatabaseremotely,usethefollowingprocedure.
messages.
To prepare an Oracle database to work remotely with VirtualCenter
1 InstalltheOracleclientontheVirtualCenter Servermachine.
2 DownloadandinstalltheODBCdriver.
68 VMware, Inc.
3 Editthetnsnames.orafilelocatedatOra9Ior10g,asappropriate.
C:\Oracle\Oraxx\NETWORK\ADMIN
Inthisexample,xxiseither 9Ior10g.
4 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
WhenyouinstalltheVirtualCenter Server,youcanestablishaconnectionwithaSQL
Serverdatabase.ThefollowingproceduredescribeshowtoconfigureaSQLServer
ODBCconnection.
SeeyourMicrosoftSQLODBCdocumentationforspecificinstructionsregarding
configuringtheSQLServerODBCconnection.
IfyouuseSQLServerforVirtualCenter,donotusethemasterdatabase.
NOTEMicrosoftWindowsNTauthenticationisnotsupportedwithremote
SQLServer.
VMware, Inc. 69
messages.
To prepare a SQL Server database to work with VirtualCenter
1 OnyourMicrosoftSQLServer,createaSQLServerdatabaseusingEnterprise
ManagerontheSQLServer.
2 OnyourMicrosoftSQLServer,createaSQLServerdatabaseuserwithdatabase
operator(DBO)rights.
ThedefaultdatabasefortheDBOuseriswhatyoudefinedinStep 1.
(SEEUPDATE)Makesurethatthedatabaseuserhasthefollowingpermissions:
MicrosoftSQLServer2000Makesurethatthedatabaseuserhasthe
db_ownerfixeddatabaseroleontheVirtualCenterdatabaseandtheMSDB
database.Thedb_ownerroleontheMSDBdatabaseisrequiredfor
installationandupgradeonly.Youcanrevokethisroleaftertheinstallationor
upgradeprocessiscompleted.Do notgranttheSystemAdministratorsserver
roletothedatabaseuser.However,iftheSystemAdministratorsrolewas
previouslygrantedwhilethedatabasewasusedwithVirtualCenterServer
2.0.x,donotrevoketheSystemAdministratorsrole.Leaveitasis.
MicrosoftSQLServer2005Makesurethatthedatabaseloginhaseitherthe
sysadminserverroleorthedb_ownerfixeddatabaseroleontheVirtualCenter
databaseandontheMSDBdatabase.Thedb_ownerroleontheMSDB
databaseisrequiredforinstallationandupgradeonly.Youcanrevokethisrole
aftertheinstallationorupgradeprocessiscomplete.
3 OnyourVirtualCenter Server,opentheWindowsODBCDataSource
Administrator.
4 SelectSettings>ControlPanel>AdministrativeTools>DataSources(ODBC).
5 SelecttheSystemDSNtab.
6 TomodifyanexistingSQLServerODBCconnection:
a SelecttheappropriateODBCconnectionfromtheSystemDataSourcelist
andclickConfigure.
b ProceedwithStep 8.
70 VMware, Inc.
7 TocreateanewSQLServerODBCconnection:
a ClickAdd.
b ForSQLServer2000,selectSQLServerandclickFinish.
ForSQLServer2005,selectSQLNativeClientandclickFinish.
8 TypeanODBCdatastorename(DSN)nameintheNamefield.
For example,typeVMware VirtualCenter.
9 (Optional)TypeanODBCDSNdescriptionintheDescriptionfield.
10 SelecttheservernamefromtheServerdropdownmenu.
TypetheSQLServermachinenameinthetextfieldifyoucannotfinditinthe
dropdownmenu.
11 ClickNext.
12 Selectoneoftheauthenticationmethods:
IfyouareusinglocalSQLServer,selectWindowsNTauthentication.Itisalso
knownastrustedauthenticationandissupportedonlyiftheSQLServeris
runningonthesamesystemastheVirtualCenter Server.
IfyouareusingremoteSQLServer,selectSQLServerauthentication.
WindowsNTauthenticationisnotsupportedonremoteSQLservers.
13 TypeyourSQLServerloginnameandpasswordandclickNext.
Askyourdatabaseadministratorforthisinformation.
14 SelectthedatabasecreatedforVirtualCenterfromtheChangethedefault
databasetomenuandclickNext.
15 ClickFinish.
16 FromtheODBCMicrosoftSQLServerSetupmenu,chooseTestDataSource.
Ifthetestdatasourceisacceptable,clickOK.Ifitisnotacceptable,returnand
reconfigureanyincorrectitems.
ToclosetheODBCDataSourceAdministrator,clickClose.
17 EnsurethattheSQLAgentisrunningonyourdatabaseserver.
ThisappliestoSQLServer2000andSQLServer2005editions.
VMware, Inc. 71
To identify the authentication type
1 OpenSQLServerEnterpriseManager.
2 ClickthePropertiestabtoviewproperties.
3 Checkthemode.
ThemodeindicateseitherWindowsNTorSQLServerauthenticationtype.
Configuring Microsoft SQL Server 2005 Express
TheMicrosoftSQLServer2005Expressdatabasepackageisinstalledandconfigured
whenyouselectMicrosoftSQLServer2005Expressasyourdatabaseduring
VirtualCenterinstallationorupgrade.ThisisshowninInstallingVMware
InfrastructureManagementSoftwareonpage 72.Noadditionalconfigurationis
required.
IfMicrosoftSQLServer2005Expressisalreadyinstalled,reviewtherequireddatabase
patchesspecifiedinTable 21,SupportedDatabaseFormats,onpage 19.Ifyoudonot
prepareyourdatabasecorrectly,theVirtualCenterinstallermightdisplayerrorand
warningmessages.
See www.microsoft.com/sql/editions/express/default.mspx.
NOTEVMwarerecommendsMicrosoftSQLServer2005Expressforsmall
deploymentsonly(upto5hostsand50virtualmachines).
72 VMware, Inc.
Maintaining Your VirtualCenter Database
AfteryourVirtualCenterdatabaseinstanceandVirtualCenterareinstalledand
operational,performstandarddatabasemaintenanceprocesses.Theseinclude:
Monitoringthegrowthofthelogfileandcompactingthedatabaselogfile,as
needed.Seethedocumentationforthedatabasetypeyouareusing.
Schedulingregularbackupsofthedatabase.
BackingupthedatabasebeforeanyVirtualCenterupgrade.
Seeyourdatabasedocumentationforinformationonbackingupyourdatabase.
Installing VMware Infrastructure Management Software
ThissectiondescribeshowtoinstallmanagementsoftwarebyusingtheVMware
InfrastructureManagementCDordownloadpackage.TheVMwareInfrastructure
ManagementCDallowsyoutochoosethecomponentsyouwanttoinstallandinstalls
allselectedcomponentsinasingleprocedure.
VirtualCenter Server Prerequisites
Beforeyoubegintheinstallationprocedure,ensurethatyouhavedonethefollowing:
EnsurethatyourhardwaremeetsSystemRequirementsonpage 17.
MakesurethatthesystemyouuseforyourVirtualCenterinstallationbelongstoa
domainratherthanaworkgroup.Ifassignedtoaworkgroup,the
VirtualCenter Serverisnotabletodiscoveralldomainsandsystemsavailableon
thenetworkwhenusingsuchfeaturesasVirtualCenterConsolidation.To
determinewhetherthesystembelongstoaworkgrouporadomain,rightclick
My ComputerandclickPropertiesandtheComputerNametab.TheComputer
NametabdisplayseitheraWorkgrouplabeloraDomainlabel.
CreateaVirtualCenterdatabase,unlessyouwanttouseSQLServer2005Express.
See PreparingtheVirtualCenter ServerDatabaseonpage 65.
ObtainandassignastaticIPaddressandhostnametotheWindowsserverthat
willhosttheVirtualCenter Serverandthelicenseserver.ThisIPaddressmusthave
avalid(internal)DNSregistrationthatresolvesproperlyfromallmanaged
ESX Serverhosts.Forbestresults,ensurethattheWindowsservernameisexactly
thesameastheDNShostname.
VMware, Inc. 73
YoucandeployVirtualCenterbehindafirewall.However,makesurethereisno
NetworkAddressTranslation(NAT)firewallbetweenVirtualCenterandthehosts
itwillmanage.
Theinstallerautomaticallyinstallsalicenseserverforyou,unlessyouenterapath
toanexistinglicenseserver.
Touseanexistinglicenseserver,obtainthehostnameorIPaddress.
Toallowtheinstallertoinstallalicenseserver,youneedavalidservedlicense
file.
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.
74 VMware, Inc.
Installation Procedure
ThisproceduredescribeshowtoinstallallVMwareInfrastructuremanagement
components.
To install VMware Infrastructure Management
1 AsAdministratorontheWindowssystem,inserttheinstallationCD.
2 ChoosealanguagefortheinstallerandclickOK.
3 WhentheVMwareInfrastructureManagementInstallerscreenappears,click
Next.
IftheVMwareInfrastructureManagementInstallerscreendoesnotappear,
doubleclicktheautorun.exeicon.
4 ReadtheIntroductionpageandclickNext.
5 SelectIacceptthetermsinthelicenseagreementandclickNext.
6 TypeyourusernameandcompanynameandclickNext.
7 SelectoneoftheinstallationtypesandclickNext.
Thechoicesare:
InstalltheVI Client.
InstalltheVirtualCenter Server.
Chooseacustominstallationtoinstallmultiplecomponents.
8 Selecttheoptioncorrespondingwiththedatabaseyouconfigured.
Ifyouhavenotconfiguredasupporteddatabase,clickInstallMicrosoftSQL
Server2005Express.Thisdatabaseissuitableforsmalldeploymentsofupto
5hostsand50virtualmachines.
Ifyouhaveconfiguredasupporteddatabase,clickUseanexistingdatabaseand
enteryourdatabaseconnectioninformation:
a TypetheDSNassociatedwithyourdatabase.
ThismustbeasystemDSN.
b IfyourdatabaseisalocalSQLServerdatabaseusingWindowsNT
authentication,leavetheusernameandpasswordfieldsblank.Otherwise,
typetheusernameandpasswordassociatedwiththedatasourcenameand
clickNext.
VMware, Inc. 75
Ifyourconnectionfails,awarningappears.ClickOKandreenteryour
databaseconnectioninformationuntilyoucancontinue.
9 Selectoneofthefollowingoptions:
TouseVirtualCenterinevaluationmode,selectIwanttoevaluate
VirtualCenterServerandclickNext.
Ifyouchoosethisoption,theenterpriseleveleditionofVirtualCenteris
installedinevaluationmode.TheVMwareLicenseServerisalsoinstalledso
thatyoucanswitchtolicensedmodeduringoraftertheevaluationperiod.
TouseVirtualCenterinlicensedmodewithanexistinglicenseserver:
i SelectUseanexistingLicenseServer.
ii Enterthepathtoyourexistinglicenseserver.
iii SelecttheVirtualCentereditionthatyoupurchasedandclickNext.
Ifyouchoosethisoption,theVMwareLicenseServerisnotinstalled.
TouseVirtualCenterinlicensedmodewhenyoudonothaveanexisting
licenseserver:
i Leavebothcheckboxesdeselected.
ii SelecttheVirtualCentereditionthatyoupurchasedandclickNext.
Ifyouchoosethisoption,theVMwareLicenseServerisinstalled.
10 Entertheportandproxyinformationthatyouwanttouseoracceptthedefault
informationshownonscreenandclickNext.Thisstepappliesonlytocustom
installations.
ThedefaultportforHTTPSis443.IfyouconfigureVirtualCentertouseadifferent
portforHTTPS,youmustusetheconfiguredportnumberwhenyouloginto
VirtualCenter.
11 EnterinformationaboutthesystemonwhichyouareinstallingVirtualCenterand
clickNext.
Enter:
TheIPaddressordomainnameofthesystemonwhichyouareinstalling
VirtualCenter.
Theloginandpasswordthatyouusetologintothesystemonwhichyouare
installingVirtualCenter.
76 VMware, Inc.
12 ForVMwareUpdateManager,youcanusethesamedatabasethatyouusefor
VirtualCenter,oryoucanuseanotherdatabase.SeeStep 8.
13 ForVMwareUpdateManager,entertheportandproxyinformationthatyouwant
touseoracceptthedefaultinformationshownonscreen.Thisstepappliesonlyto
custominstallations.
14 ForVMwareConverter,entertheportinformationthatyouwanttouseoraccept
thedefaultinformationshownonscreen.Thisstepappliesonlytocustom
installations.
ClickNexttocontinuethroughthedeploymentoptionsscreens.
15 AcceptthedefaultdestinationfoldersandclickNext.
Ifyoudonotwanttoacceptthedefaultdestinationfolders:
ForVMwareInfrastructure,clickChangetoselectanotherlocationandclick
Next.
Fordownloadingpatches,clickChangetoselectanotherlocationandclick
Next.
16 ClickInstall.
Installationmighttakeseveralminutes.Multipleprogressbarsappearduring
installationoftheselectedcomponents.
17 ClickFinishtocompletetheVMwareInfrastructureinstallation.
Configuring Communication Between VirtualCenter
Components
TheVirtualCenter ServermustbeabletosenddatatoeveryVirtualCentermanaged
hostandreceivedatafromeachVI Client.Toenableanymigrationorprovisioning
activitiesbetweenVirtualCentermanagedhosts,thesourceandtargethostsmustbe
abletoreceivedatafromeachother.
CAUTIONToinstalltheVMwareInfrastructurecomponentsonadriveotherthan
theC:drive,verifythereisenoughspaceintheC:\WINDOWS\Installerfolderto
installtheMicrosoftWindowsInstaller.msifile.Ifyoudonothaveenoughspace,
becauseofaknownissuewithWindowsInstaller,yourVMwareInfrastructure
installationmightfail.
VMware, Inc. 77
Duringnormaloperations,VirtualCenterislisteningfordatafromitsmanagedhosts
andclientsondesignatedports.Additionally,themanagedhostsarelisteningfordata
fromVirtualCenterondesignatedports.Ifafirewallexistsbetweenanyofthese
elements,aholemustbecreatedtoallowdatatransfertothesedesignatedports.
Thefollowingsectionsdescribehowtofacilitatethiscommunication.Forinformation
onSDKcommunications,seetheVMwareSDKdocumentation.Foramorethorough
discussionoffirewallconfiguration,seetheServerConfigurationGuide.
Connecting to Your VirtualCenter Server Through a Firewall
ThedefaultportsthattheVirtualCenter Serverusestolistenforconnectionsfromthe
VI Clientareports80,443,and902.TheVirtualCenter Serveralsousesport443tolisten
fordatatransferfromtheVIWebAccessClientandotherSDKclients.
IfyouhaveafirewallbetweenyourVirtualCenter Serveranditsclients,youmust
configureameansfortheVirtualCenter Servertoreceivedatafromthem.
ToenabletheVirtualCenter ServertoreceivedatafromtheVI Client,openports80,
443,and902inthefirewalltoallowdatatransferfromtheVI Clienttothe
VirtualCenter Server.ToenabletheVirtualCenter ServertoreceivedatafromtheVI
WebAccessClient,openport443inthefirewall.Consultyourfirewallsystem
administratorforadditionalinformationonconfiguringportsinafirewall.
IfyouwanttheVirtualCenter ServertouseadifferentporttoreceiveVI Clientdata,see
BasicSystemAdministration.
TotunneltheVI Clientdatathroughthefirewalltothereceivingportonthe
VirtualCenter Server,seeBasicSystemAdministration.VMwaredoesnotrecommended
thismethodbecauseitdisablestheVirtualCenterconsolefunction.
Connecting to Your Managed Hosts Through a Firewall
Port902isthedefaultportthatVirtualCenterusestosenddatatothemanagedhosts.
IfyouhaveafirewallbetweenyourVirtualCenter ServerandVirtualCentermanaged
host,youmustconfigureameansfortheVirtualCenter Servertosenddatatothe
VirtualCentermanagedhost.
IfyouhaveafirewallbetweentwoVirtualCentermanagedhostsandyouwantto
performanysourceortargetactivities,suchasmigrationorcloning,youmust
configureameansforthemanagedhoststoreceivedata.
ManagedhostsalsosendaregularheartbeatoverUDPport902tothe
VirtualCenter Server.Thisportmustnotbeblockedbyfirewalls.
78 VMware, Inc.
To enable a VirtualCenter managed host to receive data on the default port
Openport902inthefirewalltoallowdatatransfertotheVirtualCentermanagedhost
fromtheVirtualCenter ServeroranotherVirtualCentermanagedhost.Consultyour
firewallsystemadministratorforadditionalinformationonconfiguringtheports.
Connecting Hosts with the License Server Through a Firewall
Ports27000and27010arethedefaultportsthatthelicenseserverusestocommunicate
withESX Serverhosts.IfyouareusingcentralizedlicensingwithyourESX Serverhosts
andhaveafirewallbetweenyourESX 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.
UninstallingtheVMwareInfrastructurecomponentsdoesnotuninstallthe
Microsoft.NETFramework.DonotuninstalltheMicrosoft.NETFrameworkifyou
haveotherapplicationsonyoursystemthatdependuponit.
To uninstall a VMware Infrastructure Component using the Add/Remove
Programs Tool
1 AsAdministratorontheWindowssystem,chooseStart>Settings>
ControlPanel>Add/RemovePrograms.
2 ToselectaVMwareInfrastructurecomponent,scrollthroughthelistofinstalled
programs,selectthecomponenttoremove,andclickChangeorRemove.
CAUTIONIfyoutrytouninstalltheVirtualCenter Serverwhileitisrunning,youmust
confirmthatyouwanttotakeaction.Uninstallinginthiswaycausesadisruptiontoany
VI Clientsconnectedtotheservice.Thiscancausedataloss.
VMware, Inc. 79
3 ClickYestoconfirmthatyouwanttoremovetheprogram.
4 ClickFinish.
Installing VirtualCenter in a Virtual Machine
YoucaninstallyourVirtualCentercomponentsinaWindowsvirtualmachine,which
runsonanESX Serverhost.DeployingyourVirtualCenterinthevirtualmachinehas
thefollowingadvantages:
RatherthandedicatingaseparateservertoyourVirtualCenter,youcanplaceitin
avirtualmachinerunningonthesameESX Serverhostwhereyourothervirtual
machinesrun.
YoucanprovidehighavailabilityfortheVirtualCenter Serverbyusing
VMware HA.
YoucanmigratethevirtualmachinecontainingyourVirtualCenterfromonehost
toanother,enablingmaintenanceandotheractivities.
YoucancreatesnapshotsoftheVirtualCentervirtualmachineandusethemfor
backups,archiving,andsoon.
To install VirtualCenter in a Virtual Machine
1 Onastandaloneserver,installtheESX Server.
See InstallingVMwareESX ServerSoftwareonpage 81.
2 OnanymachinethathasnetworkaccesstoyourESX Serverhost,installthe
VI Client.
ToinstallonlytheVI Client,performacustominstallationasdescribedinTo
installVMwareInfrastructureManagementonpage 74.
3 UsingtheVI Client,accesstheESX Serverhostdirectlytocreatethevirtual
machineforhostingVirtualCenter.
Forinformationoncreatingvirtualmachines,seeBasicSystemAdministration.
4 Inthevirtualmachine,installVirtualCenterfollowingproceduresdescribedinthis
chapter.
FormoredetailsoninstallingandrunningVirtualCenterinavirtualmachine,see
RunningVirtualCenterinaVirtualMachineat
www.vmware.com/pdf/vi3_vc_in_vm.pdf.
80 VMware, Inc.
VMware, Inc. 81
7
ThischapterdescribeshowtoinstallandconfigureESX Server.
PreparingtoInstallonpage 81
InstallingESX Serveronpage 83
PostinstallationConsiderationsonpage 93
DownloadingtheVI Clientonpage 94
InstallingaLanguagePackontheESXServerHostonpage 94
Preparing to Install
ThissectiondescribesthecomponentsthatareinstalledduringESX Serverinstallation,
describesthetwoavailableinstallationmethods.Italsodetailshowtoselectaboot
driveforinstallation.
Installed Components
TheVMwareESX Server 3.5installationincludesthefollowingcomponents:
VMwareESX ServerSoftwaretomanageandservevirtualmachines.
VMwareVIWebAccessSoftwaretoallowWebbrowseraccesstotheESX Server
host.
Installing VMware
ESX Server Software 7
82 VMware, Inc.
Installation Methods
TwoinstallationmodesareavailableforinstallingVMwareESX Serversoftware:
GraphicalmodeThisisagraphical,mousebasedinstallationprogramtoinstall
orupgradeESX Server.Thisistherecommendedinstallationmethod.
See InstallingESX Serveronpage 83.
TextmodeThisisatextbasedinterfacetoinstallorupgradeESX Server.Choose
thisinstallationmethodifyourvideocontroller,keyboard,ormousedoesnot
functionproperlyusingthegraphicalinstaller.See InstallingESX Serveron
page 83.
Using Remote Management Applications
IfyouuseremotemanagementapplicationssuchasIntegratedLightsOut(iLO),Dell
RemoteAccessCard(DRAC),IBMmanagementmodule(MM),orRemoteSupervisor
AdapterII(RSAII)toinstallESX Server,becarefulusingthevirtualCDfeature.You
mightencountercorruptionproblemsifyouusethisinstallationmethodwithsystems
underload.Ifyoumustusethismethod,runthemediatestprovidedbytheESX Server
Installer.
IfaremoteinstallationfromanISOimagefails,carryouttheremoteinstallationfrom
thephysicalCDROMmedia.
Installation on SATA Drives
WheninstallingESX ServerSATAdrives,considerthefollowingsituations:
EnsurethatyourSATAdrivesareconnectedthroughsupportedSAScontrollers:
mptscsi_pcieLSI1068E(LSISAS3442E)
mptscsi_pcixLSI1068(SAS5)
aacraid_esx30IBMserveraid8kSAScontroller
ccissSmartArrayP400/256controller
megaraid_sasDellPERC5.0.1controller
DonotuseSATAdiskstocreateVMFSdatastoressharedacrossmultiple
ESX Serverhosts.
See ESX Server 3Requirementsonpage 21forcompletehardwarerequirements.
See ESX ServerPartitioningonpage 97foradescriptionofpartitioning
requirements.
VMware, Inc. 83
Chapter 7 Installing VMware ESX Server Software
LUN Requirements
AlthoughESX Serversupportsupto256LUNsforoperation,theinstallersupportsa
maximumof128LUNs.Ifyouhavemorethan128LUNs,connectthemafterthe
installationiscomplete.TheminimumsupportedLUNcapacityforVMFS3is1200MB.
AnESX Serverhostsupportsonlythefirst256LUNsloadedatboottime.Yourboot
volumemustbeencounteredinthefirst256LUNs,ortheESX Serverhostcanstop
respondingatstartup.Ifyouhaveacontrollerloading256LUNsbeforetheboot
volume,reducethenumberofLUNsonthatcontrollerto256orless.
IfyouhavenotinstalledESX Serversoftware,arrangePCIcontrollercardstodetermine
theLUNorder.
VMwarerecommendsthatyoudonotrearrangedrivecontrollersamongPCIslotsafter
youinstalltheESX Serversoftware.
IfyouwantanESX ServerhosttobootfromaSAN,allocateanentireLUNtoeach
ESX Serverhost.See theSANConfigurationGuideforpostinstallationconfiguration.
See RequiredPartitionsonpage 97foradescriptionofVMFS.
ESX ServersoftwaredoesnotsupportbootingfromasharedLUN.Ifyouinstall
ESX ServersoftwareontoasharedLUN,youmightoverwritethedataontheshared
LUN.
YoumustdeterminethestatusofyouravailableLUNs.Theinstallercannotdetermine
ifaLUNisshared.
Installing ESX Server
See theUpgradeGuidetoupgradefromapreviousESX Serverversion.
PrepareforthisinstallationbyreadingPreparingtoInstallonpage 81.
CAUTIONVMwarerecommendsthatyoudisconnecttheSANbeforeyoubeginthe
ESX Serverinstallprocess.Thereisoneexception:IfyouarebootingfromaSAN,then
onlythesystemLUNshouldbepresentedtotheESX Server.AllotherLUNsshouldnot
bepresentedtotheESX Serverduringtheinstallprocess.
84 VMware, Inc.
Navigation in the Installer
TonavigateandperformactionsintheESX Serverinstaller,presstheTabkey,spacebar,
directionalarrows,orEnterkey.Youcan:
MovethehighlightbetweenselectionfieldswiththeTabkey.
Makeaselectionwithinafieldusingthearrowkeysorbytypingavalue.
PressTabuntilthehighlightisintheOKbox,andpresseitherthespacebaror
Enterkey.
ESX Server Installation Procedure
ThissectiondescribeshowtoinstalltheESX Serversoftwareonyourservermachine
usingeitherthegraphicalortextinstaller.
VerifythenetworkcableispluggedintotheEthernetadapterthatyouareusingforthe
serviceconsole.
TheESX Serverinstallerneedsalivenetworkconnectiontoproperlydetectcertain
networksettings,suchasthemachinenameunderDHCP.
To install ESX Server
1 PoweronthemachinewiththeVMwareESX ServerCDintheCDdrive.
TheESX Serverbeginsitsbootprocessuntilthemodeselectionpageappears.
Ifthispagedoesnotappear:
a Rebootthemachine.
b PressthekeyrequiredtoenteryourmachinesBIOSSetuppage.
ThiskeyisoftenF1,F2,orF10.
c SettheCDdriveasthefirstbootdevice.
d Rebootthemachine.
2 PressEntertostartthegraphicalinstaller,ortype esx textandpressEnterto
startthetextinstaller.
AseriesofinstallationmessagesscrollpastuntiltheCDMediaTestpageappears.
VMware, Inc. 85
3 ClickTesttohavetheinstallerinspecttheinstallationCDmediaforerrors.
IfyouclickSkip,continuenowwithStep 4.
IfyouclickTest,aprogressbarappears.TheCDmediaisbeingtestedfor
errors.Whentestingiscomplete,aMediaCheckResultdialogboxappears
andclickOK.
TheWelcomepageappears.
4 ClickNext(graphicalinstaller)orOK(textinstaller).
TheSelectKeyboardpageappears.
5 SelectyourkeyboardlanguagefromthelistandclickNext(graphicalinstaller)or
OK(textinstaller).
TheMouseConfigurationpageappears.
6 SelectyourmouseandclickNext(graphicalinstaller)orOK(textinstaller).
Mouseconfigurationisnotacriticalsetting.AfterESX Serverisinstalled,the
settingisignored.See MouseSelectiononpage 88.
7 Selectthetypeofinstallation.
TheSelectInstallationTypedialogboxappearsonlyiftheinstallerdetectsa
previousESX Serverinstallation.
InstallForacleaninstallationpreservingnoESX Serverconfigurationdata,
selectInstallandclickNext(graphicalinstaller)orOK(textinstaller).
UpgradeIfyouareupgrading,seetheUpgradeGuide.Donotcontinuewith
thisprocedure.
8 AccepttheVMwarelicenseagreement.
Youcannotinstallthisproductunlessyouacceptthelicenseagreement.
Ifyouareusingthegraphicalinstaller,readthroughtheenduserlicense
agreementandselectIacceptthetermsofthelicenseagreementandclick
Next.
Ifyouareusingthetextinstaller,readthroughtheenduserlicenseagreement
andselectAcceptEndUserLicenseandclickOK.
IfanydrivesorLUNsareinitialized,awarningdialogboxappears.
Ifyoudonothavedataonthedrive,clickOKtoallowpartitioningtooccur.
Youmustinitializeadrivetouseitduringinstallation.
86 VMware, Inc.
9 Selectapartitioningoption.
RecommendedConfiguresdefaultpartitions,basedonthecapacityofthe
harddrive.ContinuewithRecommendedPartitioningonpage 88.
AdvancedYouspecifyallpartitionsettings.ContinuewithAdvanced
Partitioningonpage 89.
10 SelecthowtheESX Serverwillboot:
Fromadrive(installontheMBRofthedrive)Usethisoptionformost
installations.
ThisdrivemustmatchthefirstbootdevicesetinthehostBIOS.Ifthese
settingsdonotmatch,thehostcannotbootintotheESX Serversoftware.
TobootanESX ServerhostfromaSAN,chooseaSANbasedLUNfromthe
dropdownmenu.Ifyouareusingthetextinstaller,clickOK.
FromapartitionUsethisoptionforlegacyhardwarethatstoresBIOS
informationintheMBR.
Ifyouareusingthetextinstaller,clickOK.
11 Toadddefaultoptionstothebootcommand,enterthemintotheGeneralkernel
parametersfield.
AnyoptionsyouenterarepassedtotheESX Serverkerneleverytimeitboots.
12 ClickNext(graphicalinstaller)orOK(textinstaller)tocontinuetheinstallation.
13 SelectthenetworkinterfaceforusebytheESX Serverconsole.Ifyouareusingthe
textinstaller,clickOK.
Virtualmachinenetworktrafficsharesthisnetworkadapteruntilyouconfigurea
virtualswitchforanothernetworkadapter.Youcanconfigureothernetwork
adaptersatalatertimefromtheVI Client.
14 ConfiguretheESX ServerhostnetworkIPaddress.Ifyouareusingthetext
installer,clickOK.
VMwarerecommendsthatyouuseastaticIPaddresstosimplifyclientaccess.
Ifyoudonothavetherequirednetworkconfigurationinformation,seeyour
networkadministratorforassistance.
VMware, Inc. 87
15 EntertheESX Serverhostname.Typethecompletemachinename,includingthe
domainwhereappropriate.
ThisoptionisavailableonlyifyouuseastaticIPaddress.
VI ClientscanuseeitherthehostnameortheIPaddresstoaccesstheESX Server
host.
16 IfyournetworkrequiresaVLANID,enteraVLANID.
17 SelectCreateadefaultnetworkforvirtualmachinestocreateadefaultportgroup
forvirtualmachines.Thisoptionisselectedbydefault.
IfyouselectCreateadefaultnetworkforvirtualmachines,yourvirtualmachines
shareanetworkadapterwiththeserviceconsole,whichisnottherecommended
configurationforoptimumsecurity.Ifyoudonotselectthisoption,createa
networkconnectionforyourvirtualmachinesasdescribedintheServer
ConfigurationGuide.
18 ClickNext(graphicalinstaller)orOK(textinstaller).
19 Setyourtimezone.See SettingYourTimeZoneonpage 92.
20 Enterarootpassword.
TypethesamepasswordintobothfieldsandclickNext(graphicalinstaller)orOK
(textinstaller).
Therootpasswordmustcontainatleastsixcharacters.Awarningappearsifthe
passwordsdonotmatch.
21 ConfirmyourinstallationconfigurationandclickNext(graphicalinstaller)orOK
(textinstaller).
Progressbarsappeartoshowthestatusoftheinstallation,andadialogbox
informsyouwhentheinstallationcompletes.
22 ClickFinishtoexit.
CAUTIONThisisyourlastopportunitytocancelandreturntoyourprevious
configuration.WhenyouclickNextorOK,theinstallerbeginspartitioningand
formattingthefilesystem.
88 VMware, Inc.
Mouse Selection
Herearesomemouseidentificationhints:
Iftheconnectorisround,yourmouseisaPS/2orabusmouse.
Iftheconnectoristrapezoidalwithnineholes,itisaserialmouse.
Iftheconnectorisaflatrectanglewithaslot,itisaUSBmouse.
TrytofindanexactmatchIfyoucannotfindanexactmatch,chooseamousetype
thatiscompatiblewithyours.Otherwise,choosetheappropriategenericmousetype.
ThreebuttonmouseemulationDuringtheinstallation,selectingthisboxenables
youtousemiddlemousebuttonfunctionalitybyclickingbothmousebuttonsatonce.
Recommended Partitioning
FollowthisproceduretoselectRecommendedasapartitioningoptioninToinstall
ESX Serveronpage 84.
To partition your hard drive using the recommended partitioning
1 SelectavolumeonwhichtoinstalltheESX Serversoftware.
2 TopreserveexistingVMFSpartitionswithexistingvirtualmachines,selectKeep
virtualmachinesandtheVMFS.
Thisusuallyappliesonlyifyouareinstallingontopofapreviousversionof
ESX Server.
3 SelectRecommendedpartitioningandclickNext(graphicalinstaller)orOK(text
installer).
Awarningdialogboxappears.
4 ClickYestocontinuewithyourpartitioningselection.
5 (Optional)Changethepartitionsettings:
NewSelectadiskandclickthisbuttontocreateanewpartition.
EditSelectapartitionandclickthisbuttontochangeanexistingpartition.
DeleteSelectapartitionandclickthisbuttontoremoveanexistingpartition.
ResetClickthisbuttontorestorethedefaultpartitioningscheme.
6 ClickNext(graphicalinstaller)orOK(textinstaller),andcontinuewithToinstall
VMware, Inc. 89
Advanced Partitioning
Withadvancedormanualpartitioning,theinstallerliststhedriveswithexisting
partitionsandtheamountofavailablespace.Youmustcreateallpartitions,
determiningaspecificmountpoint,filesystem,andcapacity.
EachESX Serverhostrequiresfivespecificpartitions.Ifthehosthasnetworkstorage,
onlythefirstthreerequiredpartitionsmustbeconfiguredonlocalstorage.
See ESX ServerPartitioningonpage 97fordescriptionsofrequiredandoptional
partitions.
FollowthisproceduretoselectAdvancedasapartitioningoptioninToinstall
ESX Serveronpage 84.Thisproceduredescribeshowtopartitionyourharddrive
usingmanualpartitioning.
To partition local storage
1 SelectavolumeonwhichtoinstalltheESX Serversoftware.
2 TopreserveexistingVMFSpartitionswithexistingvirtualmachines,selectKeep
virtualmachinesandtheVMFS.
Thisusuallyappliesonlyifyouareinstallingontopofapreviousversionof
ESX Server.
3 SelectAdvancedpartitioningandclickNext(graphicalinstaller)orOK(text
installer).
Awarningdialogboxappears.
4 ClickYestocontinuewithyourpartitioningselection.
5 Tocreateapartition,clickNew.
TheAddPartitiondialogboxappears.
6 Tocreateabootpartition,usethefollowingsettings:
MountPoint/boot
FileSystemext3
Size(MB)VMwarerecommends100MB
AdditionalSizeOptionsFixedsize
90 VMware, Inc.
7 Tocreateaswappartition,usethefollowingsettings:
MountPointNotapplicable.Thisdropdownmenuisdisabledwhenyou
selectswapforfilesystem.
FileSystemswap
Size(MB)VMwarerecommends544MB.
AdditionalsizeoptionsFixedsize
8 Tocreatearootpartition,usethefollowingsettings:
MountPoint/
FileSystemext3
Size(MB)VMwarerecommendsatleast5GBfortherootpartition,butyou
canfilltheremainingcapacityofthedrive.
AdditionalsizeoptionsFillallspaceupto(MB)
9 (Optional)Tocreatealogpartition(recommended),usethefollowingsettings:
MountPoint/var/log
FileSystemext3
Size(MB)500MBistheminimumsize.VMwarerecommends2000MBfor
thelogpartition
AdditionalsizeoptionsFillallspaceupto(MB)
10 (Optional)Createadditionallogicalpartitions.
Forbestperformance,useVI ClientorVIWebAccesstosetupyourVMFS3
partitionsratherthantheESX Serverinstaller.UsingVI ClientorVIWebAccess
ensuresthatthestartingsectorsofpartitionsare64Kaligned,whichimproves
storageperformance.
CAUTIONIfyoudonotformata /partition,theinstallationfailsatthelaststep.Format
allnecessarypartitionsbeforeproceedingtothenextstepoftheinstallation.
VMware, Inc. 91
IfyourESX Serverhosthasnonetworkstorageandonelocaldisk,youmustcreate
twomorerequiredpartitionsonthelocaldisk(foratotaloffiverequired
partitions):
vmkcoreAvmkcorepartitionisrequiredtostorecoredumpsfor
troubleshooting.VMwaredoesnotsupportESX Serverhostconfigurations
withoutavmkcorepartition.
vmfs3Avmfs3partitionisrequiredtostoreyourvirtualmachines.
Thesevmfsandvmkcorepartitionsarerequiredonalocaldiskonlyifthe
ESX Serverhosthasnonetworkstorage.
11 ClickNext(graphicalinstaller)orOK(textinstaller)tocontinuewithToinstall
92 VMware, Inc.
Setting Your Time Zone
Thegraphicalinstallerletsyouselectyourtimezoneusingamap,alistoflocations,or
alistoftimezones.
To set the time zone using the map
1 ClicktheMaptabtodisplaythemap.
2 Clickthemaponthecitynearesttoyourlocation.
3 SelectthecheckboxforusingUTC(CoordinatedUniversalTime)ifappropriate.
(Thisoptionisselectedbydefault.)
4 ClickNexttocontinuetheinstallationwithStep 20onpage 87.
To set the time zone using a location
1 ClicktheLocationtabtodisplayalistofcities.
2 Selectacityinyourtimezonefromthescrollinglist.
3 SelectthecheckboxforusingUTC,ifappropriate.
To set the time zone based on UTC offset from GMT
1 ClicktheUTCOffsettab.
2 Selectanoffsetfromthelist.
3 Selectthecheckboxtocompensatefordaylightsavingtime(ifappropriate).
To set the time zone using the text installer
2 Selectacityinyourtimezonefromthescrollinglist.
3 ClickOKtocontinuetheinstallationwithStep 20onpage 87.
VMware, Inc. 93
Postinstallation Considerations
Thissectiondiscussesinstallationlogsandhardwareanddriveradditions.
Locating the Installation Logs
Afteryouinstallandreboot,logintotheserviceconsoletoreadtheinstallationlogs:
/root/install.logisacompletelogoftheinstallation.
/root/anaconda-ks.cfgisakickstartfilecontainingtheselectedinstallation.
Assigning New Hardware on the Server
Afteryouinstallthenewhardwareonyoursystem,useVirtualCentertoassignthe
hardwaretothevirtualmachines.See BasicSystemAdministration.
Bootingorrebootingthemachinedoesnotmaketheserviceconsoledetectnewly
installedhardware.Tomaketheserviceconsoledetectsnewlyinstalledhardware,log
intotheserviceconsoleasroot,anddooneofthefollowing:
Runthecommandkudzuatacommandprompt.
Manuallyeditthe/etc/modules.conf file.
To run kudzu
1 Loginasrootontheserviceconsole.
2 Atacommandprompt,typekudzu.
3 Thekudzuutilitydetectsanynewhardwareandaddsappropriateentriestothe
/etc/modules.conffile.
To edit modules.conf
Ifyoueditthe/etc/modules.conffilebyhand,addanaliaslineforthenewdevice.
For example,ifyouareaddinganewSCSIadapterthatusesadrivernamed
adapXXXX,addthisline:
alias scsi_hostadapter adapXXXX
Installing Additional Drivers from the VMware Driver Disk
VMwareprovidesadriverdiskforadevicethatisnothandledbydriversinthisrelease
ofESX Server.Usedriverdiskstoupgradethedriversonanexistingsystemorinstall
newdriversontoanexistingsystem.
94 VMware, Inc.
Verifying Your Device Driver Mappings
Duringtheupgrade,theESX Serverinstallerrenamesthe
/etc/vmware/vmware-device.map.localfileto
/etc/vmware/vmware-device.map.local.orig.
Aftertheupgrade,comparethevmware-device.map.local.origfilewiththenewly
createdvmware-device.map.localfileandmakeanynecessarychanges.The
locationsofsomedrivershavechangedinESX Server 3.5.Withtheadditionofnew
driversinESX Server 3.5,furthercustomizationofvmware-device.map.localmight
notbenecessary.
Downloading the VI Client
TheVI ClientisaWindowsprogramthatyoucanusetoconfiguretheESX Serverhost
andtooperateitsvirtualmachines.YoucandownloadVI ClientfromanyESX Server 3
host.
YoumustobtaintheURLofanESX Serverhost.ThisistheIPaddressormachinename.
To download the client
1 FromaWindowsmachine,openaWebbrowser.
2 EntertheURLfortheESX Serverhost.
For example,enterhttp://testserver.vmware.com/
TheVMwareESX Serverwelcomepageappears.
3 ClicktheDownloadtheVI ClientlinkunderGettingStarted.
Asecuritywarningdialogboxappears.
4 ClickYes.
5 Installtheclient.
SeeToinstallVMwareInfrastructureManagementonpage 74.
Installing a Language Pack on the ESX Server Host
ForGerman,Japanese,orSimplifiedChineselanguagesupportwhenyouuseVirtual
InfrastructureWebAccessortheVIClientwithyourESXServerhost,youmustinstall
thelanguagepack.
VMware, Inc. 95
To install the language pack
1 DownloadtheVMwareESXlangpack<version><build>.zipfilefromthe
downloadsite.
2 ExtractthecontentsoftheZIPfileintoatemporarydirectory.
3 Copythefilesfromtheesx/hostd/directorytothehostdinstallationdirectoryon
yourESXServerhost(usuallyusr/lib/vmware/hostd/).
cp -pr esx/hostd/locale /usr/lib/vmware/hostd
4 Copythefilesfromtheesx/webAccess/directorytotheVIWebAccessinstallation
directoryonyourESXServerhost(usually
/usr/lib/vmware/webAccess/tomcat/apachetomcat<version>/webapps/).
cp -pr esx/webAccess/webapps/ui
/usr/lib/vmware/webAccess/tomcat/apache-tomcat-<version>/
webapps/
cp -pr esx/webAccess/webapps/WEB-INF
/usr/lib/vmware/webAccess/tomcat/apache-tomcat-<version>/
webapps/ui/
cp -pr esx/docroot /usr/lib/vmware/hostd/
5 Editthe/etc/vmware/hostd/config.xmlfiletoenablethecorrectdefaultlanguage:
ForGerman,addthefollowinglinestotheconfig.xmlfile:
<locale>
<DefaultLocale>de_DE</DefaultLocale>
</locale>
ForJapanese,addthefollowinglinestotheconfig.xmlfile:
<locale>
<DefaultLocale>ja_JP</DefaultLocale>
</locale>
ForSimplifiedChinese,addthefollowinglinestotheconfig.xmlfile:
<locale>
<DefaultLocale>zh_CN</DefaultLocale>
</locale>
6 TypethefollowingcommandstorestartVIWebAccessandhostagentservices:
service mgmt-vmware restart
service vmware-webAccess restart
96 VMware, Inc.
VMware, Inc. 97
A
ESX Serverhostshaverequiredandoptionalpartitions.
Thisappendixcontainsthefollowingtopics:
RequiredPartitionsonpage 97
OptionalPartitionsonpage 101
Required Partitions
AnESX Serverlocalbootvolumerequiresthreespecificpartitionsforoperation.
Inaddition,alocalorremoteVMFSpartitionisrequiredtostoreyourvirtualmachines,
anda vmkcore partitionisrequiredtoprovidecoredumpsfortechnicalsupport.
For/var/log,VMwarerecommendsaseparatepartitiontopreventunexpecteddisk
spaceconstraintsfromcompromisingESXServeroperations.Increasethispartitionby
512MBifyouuseKickstart,ortoperformaremoteorscriptedinstallationfromthe
ESXServermachine.
ESX Server Partitioning A
98 VMware, Inc.
Table A1describestherequiredpartitions.
Table A-1. ESX Server Required Partitions
Mount Point Type
Recommended Storage
by Host Disk Configuration
Partition Description
Internal
Disk with
External
SAN,
NAS, or
iSCSI SAN Only
Internal
Disk
Only
/boot ext3 100MB
Location:
internal
disk
100MB
Location:
LUN0
100MB Storesinformationrequiredtoboot
theESX Serverhostsystem.
For example,thisiswherethegrub
andLILObootloadersreside.
Thebootdriveusuallydefaultsto
thespecified/bootpartition
location.
Notapplicable swap 544MB
Location:
internal
disk
544MB
Location:
LUN0
544MB AllowsESX Servertousedisk
spacewhenmorememoryis
neededthanthephysicalRAM
allows.
Theminimumvalueis100MB.
Note:Donotconfusethe
ESX Serverswappartitionwith
virtualmachineswapspace.
See theResourceManagementGuide.
/ ext3 5GB
Location:
internal
disk
5GB
Location:
LUN0
5GB ContainstheESX Serveroperating
systemandservices,accessible
throughtheserviceconsole.Also
containsthirdpartyaddon
servicesorapplicationsyouinstall.
Note:Runningtheinstallation
scripttocopythecontentsofthe
ESX ServerinstallationCD
requiresabout460MBofspace.
VMware, Inc. 99
Appendix A ESX Server Partitioning
Notapplicable VMFS3 1.2GB 1.2GB 1.2GB AVMFSpartitionisrequired.
However,VMFSpartitionsdonot
needtobelocatedonalocalor
bootdrive.
VMFSpartitionscanbelocatedon
a:
LocalSCSIvolume
NetworkedSCSIvolume
SAN
Usedtostorevirtualmachine
virtualdisks.VMware
recommends8GBstorageper
virtualmachine.
Notes:
AnynumberofVMFSvolumes
canbecreatedoneachLUNas
longasthespaceisavailable.
VMFS2issupportedin
readonlymodetoimport
legacyvirtualmachines.
IfyouwanttheESX Server
hosttobootfromaSAN,read
LUNRequirementson
page 83forVMFSpartitioning
requirements.
Table A-1. ESX Server Required Partitions (Continued)
Mount Point Type
Recommended Storage
Internal
Disk with
External
SAN,
NAS, or
iSCSI SAN Only
Internal
Disk
Only
100 VMware, Inc.
Notapplicable vmkcore 100MB
Location:
anydisk
100MBper
host
sharing
theSAN
Location:
CoreLUN
100MB A100MBvmkcorepartitionis
requiredforeachESX Serverhost.
CanbelocatedonalocalSCSI
volume,anetworkedSCSIvolume,
oraSAN.Itcannotbelocatedona
softwareiSCSIvolume.
Usedtostorecoredumpsfor
debuggingandtechnicalsupport.
EachESX Serverhostmusthavea
vmkcorepartitionof100MB.If
multipleESX Serverhostssharea
SAN,configureavmkcore
partitionwith100MBforeachhost.
/var/log ext3 2000MB
Location:
internal
disk
2000MB
Location:
LUN0
2000MB Optional.
Usedtostorelogfiles.
Table A-1. ESX Server Required Partitions (Continued)
Mount Point Type
Recommended Storage
Internal
Disk with
External
SAN,
NAS, or
iSCSI SAN Only
Internal
Disk
Only
VMware, Inc. 101
Appendix A ESX Server Partitioning
Optional Partitions
Table A2describestheoptionalpartitions.
For/tmpand/home,VMwarerecommendsseparatepartitionstopreventunexpected
diskspaceconstraintsfromcompromisingESXServeroperations.
Table A-2. ESX Server Optional Partitions
Mount Point Type
Recommended Storage
Internal
Disk with
External
SAN/NAS/
iSCSI
SAN
Only
Internal
Disk Only
/home ext3 512MB Optional.
Usedforstoragebyindividual
users.
/tmp ext3 1024MB 1024MB
Location:
LUN0
1024MB Optional.
Usedtostoretemporaryfiles.
Notapplicable vfat anydisk Optional.
Usedtostoreavirtualmachine
usingaRAWdiskformat.
Notapplicable LVM NA ObsoletewithESX Server 3.0.
Removefromupgradedservers.
/vmimages ext3 NA ObsoletewithESX Server 3.0.
Removefromupgradedservers.
102 VMware, Inc.
VMware, Inc. 103
B
YoucaninstallESX Serverusingremoteandscriptedinstallations.
Thisappendixcontainsthefollowingtopics:
ScriptingYourInstallationsonpage 103
EnablingScriptedInstallationonpage 104
SettingUptheScriptonpage 105
EditingtheKickstartConfigurationFileonpage 110
Scripting Your Installations
AfteryouinstallESX Serveronasystem,youcanquicklydeployorprovisionmore
ESX Serversystemsthatsharethesameorsimilarconfigurations.Youcansetupa
scripttoaidintheinstallation.TheESX Serverscriptedinstallationmethodisbasedon
RedHatskickstartinstallationmethod.Thescriptisakickstartconfigurationfile,
whichconsistsofthechoicesyouwanttomakeduringtheinstallationoftheESX Server
software.
ForallofyourserverstohavethesameconfigurationastheoriginalESX Serversystem,
makethesamechoicesforthescriptthatyoumadewhenyouinstalledESX Serveron
theoriginalsystem.
Theinstallationcanrununattendedasintheoriginalinstallation,butiftheinstaller
encountersanunspecifiedsettingforthesystem,youmustrespondtothepromptthat
appears.
Remote and Scripted
Installations B
104 VMware, Inc.
Afteryousetupthescript,youcanuseittoinstallESX Serverfilesineitherofthe
followingways:
FromtheESX ServerCDinthelocalCDROMdriveofthenewsystem.
Acrossthenetwork,usinginstallationfilesthatarehostedonaremoteserver.
Enabling Scripted Installation
AfteryouinstallESX Serveronasystem,youmustenablethescriptedinstallation
featurebeforeyoucanuseWebAccesstocreateaninstallationscript.
To enable scripted installation
1 LogintotheESX Serverserviceconsoleasroot.
2 Openthefollowingfileinatexteditorsuchasvi:
/usr/lib/vmware/webAccess/tomcat/apache-tomcat-5.5.17/webapps/ui
/WEB-INF/struts-config.xml
3 Locatethescriptedsection.
4 Commentoutthelinereading:
<action path="/scriptedInstall"
type="org.apache.struts.actions.ForwardAction"
parameter="/WEB-INF/jsp/scriptedInstall/disabled.jsp" />
5 Uncommentthefollowinglines:

VMware, Inc. 105
Appendix B Remote and Scripted Installations
6 Saveandclosethefile.
7 Typeservice vmware-webAccess restart.
Setting Up the Script
AfteryouinstallESX Serverononesystemandenablescriptedinstallationsonthat
system,youcansetupascriptnecessaryforperformingascriptedinstallationof
ESX Serveronothersystems.
Whenyousetupthescript,choosethenetworkingmethod(staticIPorDHCP)forthe
serveronwhichyouwillinstallESX Server.Youcanspecifyuniquenetwork
identificationinformation,includingthestaticIPaddressandhostnameofeach
system,oryoucanuseDHCPinitiallytoquicklysetupanumberofESX Server
systems.Inaddition,youcaneditthekickstartconfigurationfiletocommentoutthe
networkcommand,whichcausestheinstallertopromptyoufornetworkinformation
duringtheinstallation.SeeEditingtheKickstartConfigurationFileonpage 110.
IfyouuseDHCPinitiallytocreateoneinstallationscriptthatisusedtodeploynew
ESX Serversystems,youmustthenconfigureeachsystemseparatelyandassigna
uniquehostnameandIPaddress.Thisrequirementisinadditiontoconfiguringthe
serverwiththeManagementInterfacewizard.
Youcanalsocreatemultiplescripts,eachcontaininguniquenetworkidentification
informationyouspecifywhenyousetupthescript.
Youmustcopythescriptgeneratedattheendofthesetupprocesstoafloppydiskor
toanetworkaccessibleserver.
Inaddition,youmustaccesstheESX Serverinstallationfiles.Thefilescanbeonthe
ESX ServerCDROMorstoredonaseparateserverandaccessedacrossthenetwork.
Tocreateyourscript,youcaneitherusetheVIWebAccessgraphicalinterfacetospecify
yourscriptoptions,oryoucanmanuallycreateandeditakickstartconfigurationfile.
106 VMware, Inc.
Creating a Script Using VI Web Access
TheVIWebAccessinterfaceletsyoucreateakickstartconfigurationfileusinga
graphicalinterface.
To set up the script
1 LaunchasupportedWebbrowserandentertheURLofyourESX Server
installationtoopenVIWebAccess.
TheWelcomepageappears.
2 ClickLogintotheScriptedInstaller.
TheScriptedInstallpageappears.
3 EntertheinformationthatthescriptneedstoconfigureanotherESX Serversystem:
a IntheInstallationTypelist,selectInitialInstallationtoperformanew
installation.SelectUpgradetoupgradeanexistingESX Serversystem.
b IntheInstallationMethodlist,selectfromthefollowingoptions:
SelectRemotetoperformaremotenetworkinstalloptionfromaHTTPorFTP
serverthatcontainstheESX Serverinstallationfiles.IntheRemoteServer
URLfield,typethedefaultdirectorylocationofyourrootfolderalongwith
thenameoftheserverthatcontainstheESX Serverinstallationfiles,likethis:
http://<hostname>:/default location
ftp://<hostname>:/default location
VMware, Inc. 107
Forexample:
ftp://<hostname>:/var/ftp/pub/build
where<hostname>isthenameassignedtotheHTTPorFTPserver.
SelectCDROMtoinstallfromtheCDonthelocalCDROMdriveonthenew
system.
SelectNFStoperformanetworkinstallusingtheNetworkFileSystem(NFS)
application.IntheRemoteServerURLentryfield,typethehostmachine
namealongwiththemountpoint,likethis:
<hostmachine>:<mountpoint>
c IntheNetworkMethodlist,selectDHCPiftheESX Serversystemwillhave
adynamicIPaddress.SelectStaticIPiftheESX Serversystemwillhavea
staticIPaddress.
VMwarerecommendsthateachESX Serversystemhaveitsownstatic
IPaddress.However,youcanuseDHCPtodeploynewESX Serversystems
fromthesamefloppyimage,andconfigureeachsystemseparatelyandassign
auniquehostnameandIPaddress.Oryoucancreatemultiplefloppyimages
containingthenetworkidentificationinformationyouspecifyhere.
d IfyournetworkrequiresaVLANID,typeoneintheVLANIDfield.
e SelectCreateadefaultnetworkforVMstocreateadefaultnetworkfor
virtualmachines.
Selectthisoptiontocreateaportgroupfortheserviceconsoleandaport
groupforthevirtualmachines.Ifyoudonotselectthisoption,onlytheservice
consoleportgroupiscreated,andyoumustcreatetheportgroupforthe
virtualmachinesmanually.
f IntheTimeZonelist,selectthetimezonefortheserveryouwillinstall.
ThelistdefaultstosettingoftheoriginalESX Servermachine.
g IntheRebootAfterInstallationlist,selectYestohavethesystemrebootafter
theinstallationiscomplete.
h UnderRootPassword,specifytherootpassword.Typetherootpasswordin
thePasswordfield.TypethispasswordasecondtimeintheAgainfield.
108 VMware, Inc.
4 ReadthroughtheenduserlicenseagreementandselecttheIhavereadandaccept
thetermsinthelicenseagreementcheckbox.
IftheESX ServersystemwillhaveastaticIPaddress,theNetworkingOptions
pageappears.
IftheESX ServersystemwilluseDHCP,skiptoStep 7.
5 EnterthehostnameintheHostnamefield,theIPaddressintheIPAddressfield,
thenetmaskintheNetmaskfield,thenetworkgatewayintheGatewayfield,and
thedomainnameserverintheNameserverfield.
Includethefulldomainnameifyouarerunningwithdomains.
6 ClickNexttocontinue.
ThePartitionConfigurationpageappears.
7 UnderPartitionConfiguration,specifythefollowingforeachpartitioninthe
serviceconsole:
IntheDrivelist,selectfromthelistofdisks.
IntheMountPointfield,specifythemountpoint.
Ataminimum,youshouldspecifytheboot(/boot)androot(/)mount
points.
IntheSizefield,specifythesizeofthepartitioninmegabytes(MB).Specify
anintegervaluehere,suchas500.DonotappendthenumberwithMB.
See Appendix A,ESX ServerPartitioning,onpage 97forrecommended
partitionsizes.
IntheTypelist,selectthetypeoffilesystem.Choosefromvmfs,vmcore,ext3,
andswap.Selectswapifthepartitionisaswappartition.Youmustcreatea
swappartition.
SelecttheGrowcheckboxifyouwantthepartitiontogrowuntilitfillsthe
availablespaceonthedisk(ifany),oruptothemaximumsizesetting.
VMwarerecommendsyoudonotletyourbootandswappartitionsgrow.
VMware, Inc. 109
8 FromtheLicensingModelist,specifyoneofthefollowing:
PostInstallChoosethisoptiontoconfigurelicensingmanuallyafter
installation.
UseLicenseServerChoosethisoptiontoretrievelicensesfromalicense
server.
UseHostLicenseFileChoosethisoptiontouploadalicensefile.
9 ClickNexttocontinue.
10 IfyouselectedtheLicenseServerlicensingtype,enterthecentralizedlicensing
information.
LicenseServerEnterthelicenseservertouse.
PortEntertheporttowhichtoconnect.
ESX ServerEditionSelecttheeditionyoupurchased.
11 IfyouselectedFileBasedlicensing,specifyorbrowseforthelicensetoupload.
12 ClickNexttocontinuetothenextconfigurationscreen.
13 ClickDownloadKickstartFiletocreateakickstartconfigurationfile.
Running a Scripted Installation from the Kickstart File
Afteryoucreateakickstartfile,useoneofthefollowingprocedurestorunyour
scriptedinstallation,dependingonwhetheryouselectedtoinstallfromanESX Server
installationCDROMorfrominstallationfileshostedonaremoteserver,suchas
Altiris.
To run a scripted installation using a CD
1 Copyyourkickstartfiletoafloppydisk.
2 Insertthefloppydiskintothefloppydriveofthemachineonwhichyouwantto
installESX Server.
3 InserttheESX ServerInstallationCDintotheCDROMdrive.
4 Bootupthemachine.
Themodeselectionpageappears.
5 Typeesx ks=floppy.
6 PressEntertostartthescriptedinstallation.
110 VMware, Inc.
To run a scripted installation using a PXE server
1 UploadyourkickstartfiletoanNFSorHTTPserver.
2 SpecifytheinstallationmethodinthePXEserverbootoptions,where<ksurl>is
theURLtoaccessthekickstartfileand<methodurl>istheURLtoaccessthe
uploadedinstallationfiles.
Editing the Kickstart Configuration File
Thekickstartconfigurationfileisatextfilecontainingtheoptionsspecifiedforthe
ESX Serverinstallation.Youcanedityourkickstartconfigurationfiletomodifythe
optionsyouspecifiedusingtheVIWebAccessinterface,ortospecifyadditional
optionsnotavailableinthatinterface.
See theRedHatEnterpriseLinux3:SystemAdministrationGuideavailableat
www.redhat.com/docs/manuals/enterprise/RHEL3Manual/pdf/rhelsagen.pdf.
%include Section
Usethe%includesectiontodirectthekickstartparsertoadditionalkickstartfilesthat
mightincludemorekickstartcommands.Thesectioncontainsthefollowingcommand:
%include </path/to/file>
Youcanaddseveral%includesectionstoyourkickstartfile.
Command Section
ThecommandsectioncontainstheoptionsspecifiedfortheESX Serverinstallation.
Thissectionisrequiredandmustappearfirstinthekickstartfile.
MostofthecommandsthatcanbeincludedinthissectionarestandardRedHat
kickstartcommands.SomecommandsareVMwarespecific.TheVMwarespecific
commandsarelistedinTable B1.SeetheRedHatEnterpriseLinux3:System
AdministrationGuideforinformationonoptionalcommandsthatarenotVMware
specific.
VMware, Inc. 111
Table B-1. Kickstart Commands for ESX Server Installation
Command Description
autostep(optional) Similartointeractive.Usemostlyfordebugging.
authorauthconfig(required) Setupauthenticationforthesystem.
--enablemd5 Usesmd5baseduserpasswords.
--enablenis EnablesNISsupport.Bydefault,thiscommanduseswhateverdomain
itfindsonthenetwork.
--nisdomain=<domain> SetstheNISdomain.Requires--enablenis.
--nisserver SetstheNISserver(broadcastsbydefault.)Requires--enablenis.
--useshadowor
--enableshadow
Enablesshadowpasswordfile.
--enablekrb5 EnablesKerberos5toauthenticateusers.
--krb5realm= SpecifiestheKerberos5realmtowhichyoursystembelongs.
--krb5kdc= SpecifiestheKDCsthatserverequestsfortherealm.Separatethe
namesofmultipleKDCswithcommas.
--krb5adminserver= SpecifiestheKDCinyourrealmthatisalsorunningtheKADM5
administrationserver.
bootloader (required) SetsuptheGRUBloader.
--append= Specifiesextrakernelparametersforwhenthesystemisbooting.
--driveorder= SpecifieswhichdriveisfirstintheBIOSbootorder.
--location=[mbr|partit
ion|none]
Specifieswherethebootloaderisinstalled.Thevaluesare:mbr(forthe
masterbootrecord),partition(forthefirstsectorofthepartition
withthevmnixkernel),ornone(donotinstallthebootloader).
--md5pass= SetstheGRUBbootloaderpasswordwiththemd5encrypted
password.
--password= SetstheGRUBbootloaderpassword.
--upgrade Upgradestheexistingbootloaderconfigurationandpreservesanyold
entries.
clearpart(optional) Removespartitionsfromthesystembeforecreatingnewpartitions.
Notrequiredifyouusetheupgradecommand.
--linux RemovesallLinuxpartitions.
--all Removesallpartitionsfromthesystem.
--drives= Specifieswhichdrivestoclearpartitionsfrom.
--initlabel Initializesthedisklabeltothedefaultforyourarchitecture.
112 VMware, Inc.
firewall(optional) Configuresfirewalloptionsinkickstart.
--enabled Rejectsallincomingconnectionsunlesstheyarearesponseto
outboundrequests.
--disabled Allowsallincomingconnections.
--high Deprecated;sameas--enabled.
--medium Deprecated;sameas--enabled.
--trust= Specifiesdeviceswhosetrafficisallowedtogothroughthefirewall.
--ssh Allowsthespecifiedservicetopassthroughthefirewall.
--telnet Allowsthespecifiedservicetopassthroughthefirewall.
--smtp Allowsthespecifiedservicetopassthroughthefirewall.
--http Allowsthespecifiedservicetopassthroughthefirewall.
--ftp Allowsthespecifiedservicetopassthroughthefirewall.
--port= Specifiesportsallowedthroughthefirewall.
install(optional) Specifiesthatthisisafreshinstallationratherthananupgrade.
<cdrom|nfs|url> Specifiesthetypeofinstallation.Thevaluesare:
cdrominstallsfromtheCDROMdrive
nfsinstallsfromthespecifiedNFSserver
urldownloadsacrossthenetwork
--server= SpecifieswhichNFSservertoconnectto.Usewithnfs.
--dir= SpecifieswhichdirectoryontheNFSservertomount.Usewithnfs.
<url> DefinesthelocationoftheWeaselruntimeenvironment.Usedwith
url (http/ftp).
interactive(optional) Usestheinformationprovidedinthekickstartfileduringthe
installation,butallowsforinspectionandmodificationofthegiven
values.
keyboard(required) Setsthekeyboardtypeforthesystem.
<keyboardType> Specifiesthekeyboardmapfortheselectedkeyboardtype.
lang (required) Setsthelanguagetouseduringinstallation.
<languageType> Specifiesthevaluefortheselectedlanguage,for examplelang en_US.
Table B-1. Kickstart Commands for ESX Server Installation (Continued)
Command Description
VMware, Inc. 113
langsupport (required) Setsthelanguage(s)toinstallonthesystem.
<languageType> Specifiesthevalueforthelanguagesupport.Usethesamelanguage
codesyouusedwithlang.
--default Specifieswhichlanguagewillbeadefaultwheninstallingmorethan
onelanguage.
mouse (required) Configuresthemouseforthesystem,bothinGUIandtextmodes.
<mouseType> Specifiesthetypeofmouse.
--device= Specifiesthedevicethemouseison.
--emulthree Letsyouuseatwobuttonmouseasathreebuttonmouse.
Simultaneousclicksontheleftandrightmousebuttonsare
recognizedasthemiddlemousebuttonbytheXWindowSystem.
network(optional) Configuresnetworkinformationforthesystem.
--addvmportgroup=<1 or
0> (VMwarespecific)
Ifsetto1(default),createsaportgroupforvirtualmachines.Ifyoudo
notwanttocreateaportgroup,setthevalueto0.
--vlanid=<vlanid>
(VMwarespecific)
SpecifiesaVLANtousefornetworking.Settoanintegerbetween0
and4095.
--bootproto=[dhcp|stat
ic]
Specifiesnetworksettings.
--device= SpecifiesanEthernetdeviceforinstallation.
--ip= SetsanIPaddressforthemachinetobeinstalled.
--gateway= DesignatesthedefaultgatewayasanIPaddress.
--nameserver= DesignatestheprimarynameserverasanIPaddress.
--nodns DirectsnottoconfigureaDNSserver.
--netmask= Specifiesnetmaskfortheinstalledsystem.
--hostname= Specifiesthehostnamefortheinstalledsystem.
partorpartition Createsapartitiononthesystem.
Notrequirediftheupgradecommandisused.
<mntpoint> Specifieswherethepartitionwillbemounted.
--size= Definestheminimumpartitionsizeinmegabytes.
--grow Specifiesthatthepartitioncangrowtofillanyavailablespaceorupto
themaximumsizesetting.
--maxsize= Specifiesthemaximumsizeinmegabytesforapartitiontogrow.
Command Description
114 VMware, Inc.
--ondisk=or--ondrive= Specifiesthediskonwhichpartitionswillbecreated.For example,
part --ondisk=sdacreatespartitionsonthefirstSCSIdriveonthe
system.
--fstype= Setsthefilesystemtypeforthepartition.
--badblocks Specifiesthatthepartitionshouldbecheckedforbadsectors.
reboot(optional) Rebootsthesystemafterscriptedinstallationisfinished.
rootpw (required) Setstherootpasswordforthesystem.
[--iscrypted] Specifiesthatthepasswordisencrypted.
<password> Specifiesthepasswordvalue.
text (optional) Performsthekickstartinstallationintextmode.
timezone (required) Setsthetimezoneforthesystem.
[--utc] SetsthesystemhardwareclocktoUTC(GreenwichMean)time.
<timezone> Specifiesthetimezoneforthesystem.
upgrade(optional) Upgradesthesystem.
vmaccepteula (required) AcceptstheESX Serverlicenseagreement.
vmlicense(optional) Specifieslicenseinformation.Ifyouspecifycentralizedlicensing,the
commandtakestheform:
vmlicense --mode=server --server=<server>
[--features=<features>]
[--edition=<edition>]
where<server>isthehostnameorIPaddressofthelicenseserverin
theformatport@hostname.<features>isanoptional,
commaseparatedlistoffeaturestorequestfromthelicensingserver,
and<edition>istheESX Serveredition.
Ifyouspecifysinglehostlicensing,thecommandtakestheform:
vmlicense --mode=file [--features=<features>]
[--edition=<edition>]
Thecontentsofthelicensefilemustbeincludedinthe
%vmlicense_textsectionofthekickstartfile.
zerombr(optional) Zeroesoutthemasterbootrecord.
Command Description
VMware, Inc. 115
%packages Section
Thissectionspecifiespackagesforinstallation.The%packagessectionisrequiredfor
successfulinstallationandmustfollowthecommandssection.Thesectionconsistsof
thefollowingtwolines:
%packages
@ base
%pre Section
The%presectionletsyouspecifyascripttorunpriortoinstallation.Thissectionis
optionalandmustcomeafterthecommandssection.See theRedHatEnterpriseLinux 3:
SystemAdministrationGuideformoreinformationonpreinstallationscripting.
%post Section
The%postsectionletsyouspecifyascripttorunafterinstallation.Thissectionis
optionalandmustcomeafterthecommandssection.See theRedHatEnterpriseLinux3:
SystemAdministrationGuideformoreinformationonpostinstallationscripting.
%vmlicense_text Section
ThissectioncontainsthelicensefilefortheESX Serverinstallation.Omitthissectionif
youdidnotspecifysinglehostlicensing.Thissectionmustcomeafterthecommands
section.
Sample Kickstart File
ThefollowingisasamplekickstartfileforanESX Serverinstallationusingalicense
server:
# Installation Method
cdrom
# root Password
rootpw --iscrypted $1$MpR$n9sgFQJweS1PeSBpqRRu..
# Authconfig
authconfig --enableshadow --enablemd5
# BootLoader ( The user has to use grub by default )
bootloader --location=mbr
# Timezone
timezone America/Los_Angeles
# X windowing System
skipx
# Install or Upgrade
install
116 VMware, Inc.
# Text Mode
text
# Network install type
network --device eth0 --bootproto dhcp
# Language
lang en_US
# Language Support
langsupport --default en_US
# Keyboard
keyboard us
# Mouse
mouse generic3ps/2 --device psaux
# Reboot after install ?
reboot
# Clear Partitions
clearpart --all --initlabel --drives=sda
# Partitioning
part /boot --fstype ext3 --size=100 --ondisk=sda
part / --fstype ext3 --size=1500 --ondisk=sda
part None --fstype vmkcore --size=100 --ondisk=sda
part None --fstype vmfs3 --size=900 --grow --maxsize=2500 --ondisk=sda
part swap --size=256 --grow --maxsize=512 --ondisk=sda
#VMware Specific Commands
vmaccepteula
vmlicense --mode=server --server=27000@license.vmware.com
--edition=esxFull --features= backup
%packages
@ base
%post
VMware, Inc. 117 VMware, Inc. 117
Index
Numerics
27000, port 52
27010, port 52
A
activation code, license 48
Altiris 110
ATA disks 23
B
backing up
virtual machines 29
backup 34
Consolidated Backup 34
BIOS 86
boot device 86
boot loader options 86
booting
from SAN 83, 86
kernel parameters 86
C
centralized licensing
configuring 50
description 31
Chinese
installing language pack 94
clients, firewall 76
configuring, ports 76
Consolidated Backup 34
Consolidated Backup, licensing 29
D
databases
Oracle 66
preparing 65
SQL Server 68
device driver mappings 94
device drivers 94
DPM, by edition 29
DRAC 82
driver disks 93
DRS, by edition 29
E
editions 34
end user license agreement 85
ESX Server, editions 34
EULA 85
evaluation licenses 60
F
firewall 76
G
German
grace period, license server 35
guest operating systems 25
H
HA, by edition 29
hosts firewall 76
118 VMware, Inc.
I
IDE disks 23
ILO 82
installation logs 93
installation script, creating 105
installing
ESX Server 83
license server 60
on SANs 23
Oracle database 66
VirtualCenter Server 72
internationalization 94
iSCSI
licensing 29
J
Japanese
K
kernel parameters, boot 86
kickstart commands 111
kickstart file, creating 105
kudzu utility 93
L
LAC 28
language packs 94
license activation code 28, 48
license files
installing 49
locations of 58
obtaining 40, 48
license keys 32
license pool 31
license server
availability 35
grace period 35
install 60
licenses, evaluation 60
licensing
centralized 31
single host 32
listening ports 76
local Oracle database 66
logs, installation 93
LUNs, shared 83
M
mappings, device driver 94
master boot record 86
memory, server requirements 22
Microsoft Access database
end of support life 19
modules.conf file 93
MSDE, preparing database 71
N
NAS, licensing 29
O
ODBC databases 68
operating systems, guest 25
Oracle, preparing database 66
P
PAC 28
partitioning
advanced 89
optional 101
options 86
recommended 88
required 97
partner activation code 28
partner activation portal 28
VMware, Inc. 119
Index
ports
27000 52
27010 52
configuring 76
firewall 76
license server 52
PXE 110
R
reinstalling VirtualCenter 78
remote Oracle database 66
removing VirtualCenter 78
RSA II 82
S
SANs
booting from 83, 86
SATA disks 23, 82
scripted installation 109
SCSI 22
SCSI adapters 93
SCSI disks 23
SDK 13
shared LUNs 83
single-host licensing
configuring 53
description 32
SMP, licensing 29
specifications
ESX Server system minimum 21
performance recommendations 24
SQL Server, preparing database 68
support, guest operating system 25
system requirements
ESX Server 21
license server 21
VI Client 20
VI Web Access 20
VirtualCenter database 19
VirtualCenter Server 17
T
TCP/IP ports
27000 52
27010 52
U
uninstalling VirtualCenter 78
upgrading device drivers 94
V
VCB 29, 34
VI Client, downloading 94
VMFS3 91
vmkcore 91
VMotion, licensing 35
VMware Consolidated Backup 29, 34
VMware DRS, licensing 35
VMware HA, licensing 35
120 VMware, Inc.
VMware, Inc. Update1
Updates for the ESX Server 3 and
VirtualCenter Installation Guide
LastUpdated:October17,2008
ThisdocumentprovidesanupdatetotheUpdate2releaseforESXServer3.5and
VirtualCenter2.5versionoftheESXServer3andVirtualCenterInstallationGuide.
The updateddescriptionislistedbypagenumbersothatyoucaneasilylocatethearea
oftheguidethathaschanges.Ifthechangespansmultiplesequentialpages,this
documentprovidesthestartingpagenumberonly.
ThefollowingisanupdatetotheESXServer3andVirtualCenterInstallationGuide:
UpdatefortheToPrepareaSQLServerDatabasetoWorkwithVirtualCenter
ProcedureonPage 69
Update for the To Prepare a SQL Server Database to Work
with VirtualCenter Procedure on Page 69
IntheToprepareaSQLServerdatabasetoworkwithVirtualCenterprocedure,the
descriptionoftherequireddatabaseuserpermissionsinStep1isincomplete.
The followinginformationshouldbeincluded:
MicrosoftSQLServer2000andSQLServer2005StandardandEnterprise
ForMicrosoftSQLServer,theVirtualCenterdatabaseloginwillneedthedb_ownerrole
fortheVirtualCenterandMSDBdatabases.
TheMSDBdb_ownerroleisusedduringtheVirtualCenterinstallationorupgradeto
addthreescheduledSQLServerAgentjobs.Duringnormaloperations,theSQLServer
Agentrunsthesejobstomaintainstatisticaldata.Aftertheinstallationorupgradeis
complete,youcanremovethedb_ownerrolefromtheMSDBdatabase.
Update2 VMware, Inc.

Importantupgradenotes:
DonotchangetheSystemAdministratorServerrole(sysadmin)forthe
VirtualCenterdatabaseloginaccountwhenyouupgradefromapreviousrelease
ofVirtualCenter.ChangingthesysadminroleonyourVirtualCenterdatabase
logintomeetpermissionsrequirementscancausetheupgradetofailandinstalla
newsetoftables.
Ifduringtheupgrade,thelicensescreenhasanoptionboxthatsaysIwantto
evaluatetheproductfirst,theinstallerdidnotcorrectlyrecognizetheprevious
VirtualCenterdatabase.PressBackandreviewyourdatabasepermissionsinSQL
Manager.Afteryouaresatisfied,pressNextagaintocontinuewiththeupgrade.

Vi3!35!25 U2 Installation Guide

Uploaded by

Document Information

Original Description:

Original Title

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

Vi3!35!25 U2 Installation Guide

Uploaded by

Copyright:

Available Formats

ESX Server 3 and VirtualCenter

You might also like