Professional Documents
Culture Documents
ESX Server 3i Embedded Setup Guide
ESX Server 3i Embedded Setup 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
20072009 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware, the VMware boxes logo and design, Virtual SMP and VMotion are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. VMware VirtualCenter 2.5 is distributed with certain third party technology licensed from Tom Sawyer Software. Tom Sawyer Visualization (c) 2004 Tom Sawyer Software, Oakland, California. All Rights Reserved.
Contents
AboutThisBook
1 IntroductiontoVMwareInfrastructure 13
VMwareInfrastructureataGlance AboutESX Server 3i 16 14
2 SettingUpESX Server 3i 19
NetworkAccesstoYourESXServer3iHost 20 SettinguptheDirectConsoleUserInterface 21 ConfiguringtheKeyboardLayout 21 ConfiguringaSecurityBannerfortheDirectConsole ConfiguringESX Server 3iBootSettings 22 SelectingtheBootDevice 22 ConfiguringtheBootSettingforESX Server 3i 23 ConfiguringtheBootSettingforAnotherMode 23 ConfiguringtheBootSettingforVirtualMedia 24 ConfiguringNetworkSettings 25 ChoosingNICSfortheManagementNetwork 25 SettingtheVLANID 25 ConfiguringIPSettings 26 ConfiguringDNS 27 ConfiguringDNSSuffixes 28 TestingNetworkConnectivity 28 ConfiguringStorageBehavior 29 ConfiguringtheScratchPartition 29 ConfiguringESX Server 3iSecurity 31 RecordingtheESX Server 3iSerialNumber 31 ConfiguringtheAdministrativePassword 32 ConfiguringLockdownMode 32 ResettingtheConfigurationDefaults 33 ManagingESX Server 3iRemotely 34 RestartingManagementAgents 35 ViewingSystemLogs 35
VMware, Inc.
22
3 BackingUpandRestoringESX Server 3i 37
AboutBackingUpandRestoringanESX Server 3iConfiguration 38 ConsiderationsWhenUsingtheRemoteCLIVirtualAppliance 38 BackingUpESX Server 3iConfigurationData 39 RestoringESX Server 3iConfigurationData 40 RecoveringtheESX Server 3i EmbeddedSoftware 41 RemovingESX Server 3ifromtheHost 42
5 VMwareInfrastructureSystemRequirements 45
VirtualCenterRequirements 45 VirtualCenterHardwareRequirements 46 VirtualCenterSoftwareRequirements 46 VirtualCenterDatabaseRequirements 47 EndofSupportLifeforMicrosoftAccessandMSDEDatabases VI ClientHardwareRequirements 47 VI ClientSoftwareRequirements 48 LicenseServerRequirements 48 SupportedGuestOperatingSystems 49 VirtualMachineRequirements 49 VirtualProcessor 49 VirtualChipSet 49 VirtualBIOS 50
47
VMware, Inc.
Contents
8 LicensingVirtualCenterandESX Server 3i 71
LicensingProcess 72 ObtainingLicenseFiles 75 SettingUpCentralizedLicensing 75 InstallingLicenseFiles 75 LocationoftheLicenseServer 76 ConfiguringCentralizedLicensing 76 DefaultLicenseServerPorts 79 ChangingfromSingleHosttoCentralizedLicensing 79 SettingUpSingleHostLicensing 80 ConfiguringanESX Server 3iMachinetoUseaHostBasedSerialNumber 80 ConfiguringanESX ServerMachineforHostBasedLicensing 80 SingleHostandCentralizedLicensingintheSameEnvironment 81 ConfiguringLicensingforaMixedESX Server2.xandESX Server3.x Environment 82 ChangingfromCentralizedtoSingleHostLicensing 82 LicenseFileContents 83 LicenseFileLocations 85 AddingNewLicenseFilestoLicenseServers 85 AddingNewLicenseFilestoSingleHosts 86 InstallingaLicenseServer 87 TroubleshootingLicensing 88 ReceivingLicenseActivationCodes 88 CheckingtheLicenseServer 88
VMware, Inc. 5
CheckingtheLicenseFile 90 CheckingLicenseConfiguration 91
9 InstallingVMwareInfrastructureManagement 93
PreparingtheVirtualCenter ServerDatabase 93 ConfiguringYourVirtualCenterDatabase 94 ConfiguringanOracleConnectiontoWorkLocally 94 ConfiguringanOracleConnectiontoWorkRemotely 95 ConfiguringaSQLServerODBCConnection 96 ConfiguringMicrosoftSQLServer2005Express 98 MaintainingYourVirtualCenterDatabase 99 InstallingVMwareInfrastructureManagementSoftware 99 VirtualCenterInstallationPrerequisites 99 ComponentsInstalled 100 InstallationProcedure 101 ConfiguringCommunicationBetweenVirtualCenterComponents 103 ConnectingtoYourVirtualCenter ServerThroughaFirewall 104 ConnectingtoYourManagedHostsThroughaFirewall 104 ConnectingHostswiththeLicenseServerThroughaFirewall 105 UninstallingVMwareInfrastructureComponents 105 InstallingVirtualCenteronaVirtualMachine 106
VMware, Inc.
Contents
117
Index 121
VMware, Inc.
VMware, Inc.
Thismanual,theESXServer3iEmbeddedSetupGuide,describeshowtoinstallnew configurationsofVMware VirtualCenterandESX Server 3i. TheESXServer3iEmbeddedSetupGuidediscussesESX Server 3ionly.Toreadabout ESX Server 3.5,seehttp://www.vmware.com/support/pubs/vi_pubs.html. Foreaseofdiscussion,thisbookusesthefollowingproductnamingconventions: FortopicsspecifictoESXServer3.5,thisbookusesthetermESXServer3. FortopicsspecifictoESXServer3iversion3.5,thisbookusestheterm ESX Server 3i. Fortopicscommontobothproducts,thisbookusesthetermESXServer. Whentheidentificationofaspecificreleaseisimportanttoadiscussion,thisbook referstotheproductbyitsfull,versionedname. WhenadiscussionappliestoallversionsofESXServerfor VMware Infrastructure 3,thisbookusesthetermESXServer3.x.
Intended Audience
ThismanualisintendedforanyonewhoneedstosetuporuseESX Server 3i. The informationinthismanualiswrittenforexperiencedWindowsorLinuxsystem administratorswhoarefamiliarwithvirtualmachinetechnologyanddatacenter operations.
VMware, Inc.
Document Feedback
VMwarewelcomesyoursuggestionsforimprovingourdocumentation.Ifyouhave comments,sendyourfeedbackto: docfeedback@vmware.com
10
VMware, Inc.
Support Offerings
FindouthowVMwaresupportofferingscanhelpmeetyourbusinessneeds.Goto http://www.vmware.com/support/services.
VMware, Inc.
11
12
VMware, Inc.
ThisbookdescribesVMwareESX Server 3iandVMwareVirtualCenter.Thischapter describesthecomponentsindividually,tohelpyoudecidewhichcomponentstoinstall. ThefollowingsectionsintroduceVMwareESX Server 3iandVirtualCenter. VMwareInfrastructureataGlanceonpage 14 AboutESX Server 3ionpage 16
VMware, Inc.
13
license server
VirtualCenter
database
14
VMware, Inc.
ThemajorcomponentsofVMwareInfrastructureare: VMwareESX Server 3iProvidesavirtualizationlayerthatabstractsthe processor,memory,storage,andnetworkingresourcesofthephysicalhostinto multiplevirtualmachines.YoudonotneedtoinstallESX Server 3ibecauseitis embeddedasfirmwareonaserverplatformthatyoupurchasefromahardware vendor. VMwareVirtualCenter Server(VirtualCenter)InstallsonaWindowsmachine, eitherphysicalorvirtual,tocentrallymanageyourVMwareESX Server 3ihosts. VirtualCenterallowstheuseofadvancedVMwareInfrastructurefeaturessuchas VMwareDRS,VMwareHA,andVMwareVMotion. AVMwareSDKWebserviceisinstalledwithVirtualCenter.SeeConfiguring CommunicationBetweenVirtualCenterComponentsonpage 103. VirtualCenterPluginsOptionalapplicationsthatprovideadditional capabilitiesandfeaturestoVirtualCenter.Generally,pluginsarereleased separately,installontopofVirtualCenter,andcanbeupgradedindependently. Youcaninstallservercomponentsofpluginsonthesamecomputerwherethe VirtualCenter Serverresides,oronaseparateone.Aftertheservercomponentofa pluginisinstalled,youcanactivatethepluginsclientcomponent,which enhancestheVI ClientwithappropriateUIoptions. Documentationprovidedwitheachpluginoffersinformationabouthowserver componentsofpluginsareinstalled. Forinformationabouthowtoinstalltheclientcomponent,verifywhichplugins arealreadyinstalled,andhowtodisableoruninstallpluginsthatyouarenot using,seeBasicSystemAdministration. Thefollowingpluginsareavailable: VMwareConverterConvertsphysicalorvirtualmachinesinto ESX Server 3ivirtualmachines.Afterconvertingthevirtualmachines,you canaddthemtoyourVirtualCenterinventory. VMwareUpdateManagerProvidessecuritymonitoringandpatching supportforESX Server 3ihostsandvirtualmachines. Inadditiontoanindependentservercomponentinstallation,thisrelease supportsthecombinedinstallationfortheVirtualCenter Serverand Update Manager.FormoreinformationoninstallingtheVMwareUpdate ManagerservercomponentalongwithVirtualCenter,seeConfiguring CommunicationBetweenVirtualCenterComponentsonpage 103.If upgrading,seetheUpgradeGuide.ForgeneralinformationonUpdate Manager,seetheVMwareUpdateManagerAdministrationGuide.
VMware, Inc. 15
VI ClientInstallsonaWindowsmachineandistheprimarymethodof interactionwithVMwareInfrastructure.TheVI Clientactsas: Aconsoletooperatevirtualmachines. AnadministrationinterfaceintotheVirtualCenter ServerandESX Server 3i hosts. LicenseserverInstallsonaWindowssystemtoauthorizeVirtualCenterhosts andESX Server 3ihostsappropriatelyforyourlicensingagreement. AdministratorsmakechangestosoftwarelicensesusingtheVI Client.SeeSetting UpCentralizedLicensingonpage 75. DatabaseVirtualCenterusesadatabasetoorganizealltheconfigurationdatafor theVMwareInfrastructureenvironment.Forsmalldeployments,thebundled MicrosoftSQLServer2005Expressdatabaseletsyousetupalimitednumbersof hostsandvirtualmachines(5hostsand50virtualmachines).VirtualCenter supportsseveralotherdatabaseproductsforlargerdeployments.SeePreparing theVirtualCenter ServerDatabaseonpage 93.
16
VMware, Inc.
Keyoperationsavailabletoyouinthedirectconsoleinclude: ConfiguringESX Server 3ihostdefaults Settingupadministrativeaccess TroubleshootingESX Server 3i ForinformationaboutsettingupyourESX Server 3ihostandusingthedirectconsole, seeSettingUpESX Server 3ionpage 19.
VMware, Inc.
17
18
VMware, Inc.
Thischapterprovidesinformationaboutusingthedirectconsoleuserinterfaceand configuringdefaultsforESX Server 3i.Itincludesthefollowingsections: NetworkAccesstoYourESXServer3iHostonpage 20 SettinguptheDirectConsoleUserInterfaceonpage 21 ConfiguringESX Server 3iBootSettingsonpage 22 ConfiguringNetworkSettingsonpage 25 ConfiguringStorageBehavioronpage 29 ConfiguringESX Server 3iSecurityonpage 31 ResettingtheConfigurationDefaultsonpage 33 ManagingESX Server 3iRemotelyonpage 34 RestartingManagementAgentsonpage 35 ViewingSystemLogsonpage 35
VMware, Inc.
19
20
VMware, Inc.
VMware, Inc.
21
22
VMware, Inc.
SomeserversdonothaveaBootOptionsmenu,inwhichcaseyoumustchangethe bootorderintheBIOS,evenforonetimeboots,andthenchangeitbackagainduring thesubsequentreboot. NOTETheBootOptionsmenudiscussedinthissectionisdifferentfromthesystem bootoptionsthatyoucanconfigurebyloggingintotheVI Client,selectingahost,and clickingConfiguration>Processors>BootOptions. ThissectiondiscussesthesystemBIOSBootOptionsmenu.Thebootoptionsinthe VI Clientonlyallowyoutoconfigurethebootsequenceforfloppy,CDROM,andthe harddisk(C:drive).Forsomeservers,thesystemBIOShastwooptions.Oneisforthe bootsequence(floppy,CDROM,harddisk)andanotherfortheharddiskbootorder (USBkey,localharddisk).WhenyouareusingtheVIClient,thebootoptions correspondtotheBIOSbootsequence(floppy.CDROM,harddisk).
VMware, Inc.
23
To select a one-time boot option 1 2 Reboottheserver. Whiletheserverispoweringon,openthebootoptionmenu. Forexample,onsomeserversyoucanselectF11toopenthebootmenuoption. 3 Fromthisbootoptionmenu,followtheinstructionstoselectadevicefromwhich toboot. Theserverbootsintheconfiguredmodeonetimeandgoesbacktothedefaultboot orderforsubsequentreboots. To change the boot order 1 2 Reboottheserver. Whiletheserverispoweringon,pressthekeyrequiredtoenteryourhostsBIOS Setuppage. Dependingonyourserverhardware,thekeymightbeF1,F2,F10,F11,F12,orDel. TheoptiontoopentheBIOSSetuppagemightbedifferentforyourserver. 3 Changethebootorderbyselectingadeviceandmovingittothefirstpositionin thelist. Thehostpowersonintheconfiguredmodeforthisbootandforallsubsequent reboots.
24
VMware, Inc.
VMware, Inc.
25
Configuring IP Settings
YoucanchooseeithermanualorautomaticIPconfigurationoftheESX Server 3ihost. Bydefault,IPconfigurationisautomatic.TheautomaticsettingenablesDHCPtoset theIPaddress,subnetmask,anddefaultgateway.ThedirectconsoledisplaystheIP addressthatDHCPassignstothehost.Forfuturereference,VMwarerecommendsthat youwritedownthisIPaddress. ForDHCPtowork,yournetworkenvironmentmusthaveaDHCPserver.IfDHCPis notavailableornotdesirable,thehostmightbeassignedthebuiltindefaultIPaddress, whichis169.254.0.1/16.Youcanusethisdefaultaddresstoconnectinitiallyandthen configureastaticnetworkaddress.Thedefaultsubnetmaskis255.255.0.0.Thedefault gatewayisblank.IftwohostspowerupwithnoDHCPservice,bothhostsreceivethe default169.254.0.1IPaddress.NooutboundtrafficisallowedthroughthisIPaddress. ThisiswhythedefaultIPaddressisnotalongtermalternativetoDHCP.Itprovidesa temporarymethodtoconnecttothehostsothatyoucanconfigurestaticIPsettings. Ifyouarenotlocaltothehost,youcanusetheVI ClienttoconfigurestaticIPsettings, ifyouareonthesamephysicalsubnetandyouconfiguretheVIClientIPtobeonthe 169.254.0.xnetwork. Ifyouarelocaltothehost,youcanusethedirectconsoletoconfigurestaticIPsettings, includingtheIPaddress,subnetmask,anddefaultgateway. To configure static IP settings from the direct console 1 2 3 4 5 6 7 Fromthedirectconsole,selectConfigureManagementNetworkandpressEnter. SelectIPConfigurationandpressEnter. NavigatetoSetstaticIPaddressandnetworkconfiguration. Pressthespacebartoselectthehighlighteditem. SelectanddeletethecurrentIP address,subnetmask,anddefaultgateway. EnterastaticIPaddress,subnetmask,anddefaultgateway. PressEnter.
To configure static IP settings from the VI Client 1 2 3 4 FromtheVI Client,selectthehostintheinventory. SelecttheConfigurationtabandclickNetworking. ClickPropertiesnexttoVirtualSwitch:vSwitch0. SelectManagementNetworkandclickEdit.
26
VMware, Inc.
5 6 7
Configuring DNS
YoucanchooseeithermanualorautomaticDomainNameSystem(DNS)configuration oftheESX Server 3ihost.Bydefault,DNSconfigurationisautomatic.Theautomatic settingenablesaDHCPservertoacquireDNSinformation.ForautomaticDNSto work,yournetworkenvironmentmusthaveaDHCPserverandaDNSserver. InnetworkenvironmentswhereautomaticDNSisnotavailableornotdesirable,you canconfigurestaticDNSinformation,includingahostname,aprimarynameserver,a secondarynameserver,andDNSsuffixes. Ifyouarenotlocaltothehost,youcanusetheVI ClienttoconfigureDNSinformation. Ifyouarelocaltothehost,youcanusethedirectconsoletoconfigureDNSinformation. To configure DNS settings from the direct console 1 2 3 4 5 6 7 Fromthedirectconsole,selectConfigureManagementNetworkandpressEnter. SelectDNSConfigurationandpressEnter. NavigatetoUsethefollowingDNSserveraddressesandhostname. Pressthespacebartoselectthehighlighteditem. Selectanddeletethecurrentprimaryserver,alternateserver,andhostname. Enterastaticprimaryserver,alternateserver,andhostname. PressEnter.
To configure DNS settings from the VI Client 1 2 3 4 5 6 FromtheVI Client,selectthehostintheinventory. SelecttheConfigurationtabandclickNetworking. ClickPropertiesnexttoVirtualSwitch:vSwitch0. SelectManagementNetworkandclickEdit. OntheGeneraltab,clickUsethefollowingIPsettings. ClickEditnexttoVMkernelDefaultGateway.
VMware, Inc.
27
7 8
TheESX Server 3ihosttestsyournetworkconfiguration. To test connectivity to other devices or networks 1 2 3 4 Fromthedirectconsole,selectTestManagementNetworkandpressEnter. Selectanddeleteoneormoredefaultaddressesorthedefaulthostname. TypeotheraddressestopingoranotherDNShostnametoresolve. PressEntertostartthetest.
28
VMware, Inc.
VMware, Inc.
29
Beforeyoucanenablethescratchpartition,youmusthaveaccesstoamachinethatis runningtheRemoteCommandLineInterface(CLI).For informationaboutimporting orinstallingtheRemote CLI,seetheRemoteCommandLineInterfacesappendixof theESXServer3iConfigurationGuide. To enable the scratch partition 1 PowerontheRemoteCLIandlogin. Youdonotneedtotypethepasswordonthecommandline.Ifnopasswordis specified,thetoolpromptsyouforthepasswordwithoutechoingtheoutputtothe terminal.Thismeansthepasswordyoutypeisnotvisibleinthewindowasyou runthecommand. YoucancreateasecureconnectiontotheRemoteCLIbyusingtheRemoteCLIIP address.IfyouareusingtheVI Client,youcanrightclicktheRemoteCLIand selectOpenConsole. IftheRemoteCLIisinstalledonyourWindowsorLinuxsystem,youcanusethe installedapplication,inwhichcaseyoudonotneedtologin. 2 Togetthecurrentstate,runthefollowingreadonlycommands:
vicfg-advcfg.pl --server <ip-address> --username root --password <password> -s /ScratchConfig/CurrentScratchLocation vicfg-advcfg.pl --server <ip-address> --username root --password <password> -s /ScratchConfig/ConfiguredSwapState
Runthefollowingcommandstoenableordisablesystemswap: Toenableswap:
vicfg-advcfg --server <ip-address> --username root --password <password> -s true ScratchConfig.ConfiguredSwapState
Todisableswap:
vicfg-advcfg --server <ip-address> --username root --password <password> -s false ScratchConfig.ConfiguredSwapState
Ifyouenabledsystemswap,runthefollowingcommandtoenterthelocationofa datastoreonwhichtocreateandenablethesystemswappartition:
vicfg-advcfg --server <ip-address> --username root --password <password> -s "/vmfs/volumes/<NameOfDatastore>/<DirectorySpecificToHost>" ScratchConfig.ConfiguredScratchLocation
Theconfigureddirectorymustbeuniqueacrosshosts.
30
VMware, Inc.
Toretrievetheswapstate:
vicfg-advcfg -server <ip-address> --username root --password <password> -g ScratchConfig.ConfiguredSwapState
Toretrievescratchlocation:
vicfg-advcfg --server <ip-address> --username root --password <password> -g ScratchConfig.ConfiguredScratchLocation
Tomakethechangestakeeffect,rebootthehost.
VMware, Inc.
31
32
VMware, Inc.
VMware, Inc.
33
34
VMware, Inc.
VMware, Inc.
35
3 4
Pressqtoreturntothedirectconsole.
To redirect system log files to a remote host 1 2 3 4 FromtheVI Client,selectthehostintheinventory. SelecttheConfigurationtabandclickAdvancedSettings. ClickSyslog. ForSyslog.Remote.Hostname,enterahostnametowhichsyslogdatacanbe forwarded.
36
VMware, Inc.
ThischapterprovidesinformationaboutbackingupandrestoringtheESX Server 3i configurationandrecoveringtheESX Server 3ibootimageifitbecomesdamaged. Inaddition,itdescribeshowtoremoveESX Server 3ifromthehost. Thischaptercontainsthefollowingsections: AboutBackingUpandRestoringanESX Server 3iConfigurationonpage 38 RecoveringtheESX Server 3i EmbeddedSoftwareonpage 41 RemovingESX Server 3ifromtheHostonpage 42 ForinformationoninstallingVMwareInfrastructureManagementsoftware,see InstallingVMwareInfrastructureManagementonpage 93.Forinformationabout usingthedesktopclients,seetheVMwareInfrastructure3documentationset.
VMware, Inc.
37
The-portnumberand-protocoloptionsareoptional.Ifyouexcludethem,the defaultsareport443andprotocolHTTPS. Ifyouradministrativepasswordincludesspecialcharacters,suchas$or&,youmust includeabackslashescapecharacter(\)beforeeachspecialcharacter. Forthebackupfilename,includethebuildnumberthatiscurrentlyrunningonthehost thatyouarebackingup.IfyouarerunningtheRemoteCLIasavirtualappliance,the backupfileissavedlocallyonthevirtualappliance.Localstorageforbackupfilesis safebecausevirtualappliancesarestoredinthe/vmfs/volumes/<datastore> directory,whichisseparatefromtheESX Server 3iimageandconfigurationfiles.
VMware, Inc.
39
40
VMware, Inc.
TheoptiontoopentheBIOSSetuppagemightbedifferentforyourserver. You mightneedtoopentheBIOSconfigurationscreenstomodifythebootsetting. Asthehostcontinuestopoweron,therecoveryCDWelcomescreenappears. 3 PressEntertocontinuethroughthescreens. Tocanceltherecoveryoperation,presstheEsckey.IfyoupresstheEsckey,the hostrebootsandthedatacontainedonyourserversembeddedUSBflashremains intact. IfyoupressEnterthroughallthescreensandtherecoveryoperationbegins,you cannotcancelorundotherecovery.
VMware, Inc.
41
4 5 6 7
Afterthereboot,anewESX Serversoftwarebuildisinstalledandallconfigurationdata islost.IfyoubackeduptheESX Serverconfiguration,youcanrestoreit.Whenyou performaconfigurationbackup,theserialnumberisbackedupwiththeconfiguration andisrestoredwhenyourestoretheconfiguration.Torestoreconfigurationdata,first upgradetotheESX Serverbuildthatwasrunningwhenyoucreatedthebackup.Then usetheRemoteCLItorunthevicfg-cfgbackupcommand. Afteryourestorethehostfirmware,virtualmachinesonthathostmightnotbelisted inthehostinventory.Thisdoesnotmeanthatthevirtualmachinesarelostor destroyed.AnyvirtualmachinesthatyouaddedtothehostremainintheVMFS datastoreunlessyouexplicitlyremovethem.Forinformationaboutreturningavirtual machinetotheVirtualCenterinventory,seetheBasicSystemAdministrationGuide. SeealsoAboutBackingUpandRestoringanESX Server 3iConfigurationonpage 38.
42
VMware, Inc.
Thischapterdiscussestherequirementsandrecommendationsforadding ESX Server 3ihoststoadatacenterthathasexistingVMwareInfrastructure components,suchasESX ServerhostsandVirtualCenter Server. Specifically,thischapterdiscussestheimplicationsforVirtualCenter,virtualmachines, virtualmachinetools,andESXupgrades,whenyouaddESX Server 3itoyourVMware Infrastructure. UpgradingVMwareInfrastructurecomponentsfromearlierversionsisamultistage processinwhichproceduresmustbeperformedinaparticularorder.Theupgrade pathdependsonyourESX Serveranddatastoreconfigurations.Fordetailed informationaboutpreparingforandexecutingVMwareInfrastructureupgrades,see theUpgradeGuideforESX Server 3.5andVirtualCenter 2.5.
VirtualCenter
IfyouhaveanolderversionofVirtualCenterandyouwanttouseVirtualCenterto manageESX Server 3i(orESX Server 3),youmustupgradetheVirtualCenter softwaretoversion2.5. ESX Server 3iversion3.5hostsandESX Server 3.5hoststhataremanagedtogether inVirtualCentercanrunthesamevirtualmachines,useVMotiontomigrate virtualmachinesbetweenthehosts,andaccessthesamedatastores. YoucanmanageESX Server 3.0hostsinthesameclusterwithESX Server 3iand ESX Server 3.5hosts. YoucanmanageESX Server2.0.xasstandalonehostsinVirtualCenter. ESX Server 2.0.xhostscannotbeaddedtoclusters.
VMware, Inc.
43
Virtual Machines
Ingeneral,virtualmachinesthatyoucreateonESX Server 3i(orESX Server 3) hostsaresupportedonESX Server 3.0.xhosts.Thiscapabilitymeansthatyoucan migratethevirtualmachinesbetweenthehostsanduseVMotion.Ifyoucreate virtualmachinesthatuseparavirtualization(VMI)oranenhancednetworking device(vmxnet),VMotionisnotsupported.Inthiscase,youcanmovethevirtual machinetotheESX Server 3.0.xhostifthevirtualmachineispoweredoff. VirtualmachinesthatyoucreateonESX Server 3i(orESX Server 3.5)hostsarenot supportedonESX Server2.xhosts.
44
VMware, Inc.
YoucanmanageastandaloneVMwareESX ServerwithoutVirtualCenter Server. However,ifyouhavemultipleESX Serverhostsandyouwanttomanagethem centrally,considerinstallingtheVirtualCenter Server.Thisserverinstallsona Windowsmachine,eitherphysicalorvirtual.VirtualCenterallowstheuseofadvanced VMwareInfrastructurefeaturessuchasVMwareDRS,VMwareHA,andVMotion. Thischapterdescribesthehardwareandoperatingsystemrequirementsforhosts runningVirtualCenterandotherVMwareInfrastructurecomponents.Usethe informationinthischaptertoensurethatyourenvironmentmeetstherequirementsfor installation.Topicscoveredhereare: VirtualCenterRequirementsonpage 45 VI ClientHardwareRequirementsonpage 47 VI ClientSoftwareRequirementsonpage 48 LicenseServerRequirementsonpage 48 SupportedGuestOperatingSystemsonpage 49 VirtualMachineRequirementsonpage 49
VirtualCenter Requirements
VirtualCentermanagesESX Serverhostsbyusingaserverandthreetypesofremote managementclients.TheVirtualCenter Serverisaphysicalmachineorvirtualmachine configuredwithaccesstoasupporteddatabase.
VMware, Inc.
45
46
VMware, Inc.
MicrosoftSQLServer2005Enterprise
MicrosoftSQLServer2005ExpressSP2
VMware, Inc.
47
48
VMware, Inc.
Virtual Processor
IntelPentiumIIorlater(dependentonsystemprocessor) One,two,orfourprocessorsforeachvirtualmachine Ifyouplantocreateatwoprocessorvirtualmachine,yourESX Servermachinemust haveatleasttwophysicalprocessors.Forafourprocessorvirtualmachine,your ESX Servermachinemusthaveatleastfourphysicalprocessors.
Virtual BIOS
PhoenixBIOS4.0Release6
50
VMware, Inc.
ThischapterdescribesthelicensingmodelsavailablewithESX Server 3iand VirtualCenter. Thischaptercontainsthefollowingsections: LicensingTerminologyonpage 52 ESX Server 3iEditionsonpage 52 VirtualCenter ServerEditionsonpage 54 VirtualCenterandESX Server 3iLicensingModelonpage 54 LicenseKeyFunctionalityonpage 57 LicenseExpirationConsiderationsonpage 60 LicenseServerAvailabilityonpage 60 UsinganExistingFLEXnetLicenseServeronpage 64 ContactingSupportonpage 65
VMware, Inc.
51
Licensing Terminology
Youmightencounterthefollowingtermsduringthelicenseredemptionand configurationprocess: LicenseactivationcodeAlicenseactivationcode(LAC)isauniquecodethatis associatedwithoneormoreVMwareproductspurchased.Youreceivethiscode afteryourorderisprocessed,unlessyoupurchasedyourproductsfroman authorizedVMwarereseller,inwhichcaseyoureceiveapartneractivationcode. PartneractivationcodeApartneractivationcodeisauniquecodeidentifying ordersplacedthroughVMwarepartners.IfyoupurchasedVMware Infrastructure 3fromanauthorizedVMwarereseller,youusethiscodetoregister yourpurchasetoyourVMwarestoreaccount. LicenseactivationportalThelicenseactivationportalisaselfserviceWebportal thatyoucanusetoredeemyourlicenseactivationcodesanddownloadlicensefiles forVMwareInfrastructure3. PartneractivationportalApartneractivationportalisaselfserviceWebportal usedtoregisterapurchasemadefromanauthorizedVMwareresellertoyour VMwarestoreaccount.Youenteryourpartneractivationcodeintotheportaland downloadyourlicensefilesfromthelicenseactivationportal.
52
VMware, Inc.
Table 61displaysESX Server 3ifeaturesarrangedbyedition. Table 6-1. Edition Features for ESX Server 3i Machines
Feature Licensetype ESX Server 3i Standalone Serialnumber VI Foundation Flexlicensefiles (centralizedor singlehost) Yes Yes Yes Yes Addon Addon Addon VI Standard Flexlicensefiles (centralizedor singlehost) Yes Yes Yes Yes Yes Addon Addon VI Enterprise Flexlicensefiles (centralizedor singlehost) Yes Yes Yes Yes Yes Yes Yes
VMFS VirtualSMPsupport VMwareConsolidated Backup(VCB) VMwareUpdateManager VMwareHA ServerVMotionand Storage VMotion VMwareDRSandDPM (DistributedResource Managementand DistributedPower Management) Guidedserver consolidation, with purchaseof VirtualCenter Server Manageablebythe VI Client
Yes Yes No No No No No
No
Yes
Yes
Yes
Unrestricted
Unrestricted
Unrestricted
Yes Yes
Yes Yes
Yes Yes
Yes
Yes
Yes
Yes
Addon
Yes
Yes
Yes
VMware, Inc.
53
54
VMware, Inc.
VirtualCenterandfeaturesthatrequireVirtualCenter,suchasVMotion,musthave centralizedlicensing.ESX Serverspecificfeaturescanbelicensedforeithercentralized orsinglehostlicensing. Figure 61illustratesthethreetypesoflicenseenvironments. Figure 6-1. License File Locations in Single-Host, Mixed, and Centralized Licensing Environments
single-host licensing
VI Client ESX host license file ESX host license file ESX host serial number
centralized licensing
VI Client ESX host
ESX host
VirtualCenter (recommended)
license server
license server
license file
license file
VMware, Inc.
55
Centralized Licensing
Centralizedlicensingsimplifieslicensemanagementinlarge,dynamicenvironments byallowingaVMwarelicenseservertoadministerlicenses.Withcentralizedlicensing, youmaintainallofyourVirtualCenter ServerandESX Serverlicensesfromone console. Withcentralizedlicensing,alicenseservermanagesalicensepool,whichisacentral repositoryholdingyourentirelicensedentitlement.Whenahostrequiresaparticular licensedfunctionality,thelicenseforthatentitlementischeckedoutfromthelicense pool.Licensekeysarereleasedbacktothepoolwhentheyarenolongerbeingusedand areavailableagaintoanyhost. Theadvantagesofcentralizedlicensinginclude: Youadministeralllicensingfromasinglelocation. NewlicensesareallocatedandreallocatedbyusinganycombinationofESX Server formfactors.Forexample,youcanusethesame32processorlicenseforsixteen 2processorhosts,eight4processorhosts,four8processorhosts,two16processor hosts,oranycombinationtotaling32processors. Ongoinglicensemanagementissimplifiedbyallowinglicensestobeassignedand reassignedasneeded.Assignmentchangesastheneedsofanenvironment change,suchaswhenhostsareaddedorremoved,orpremiumfeatureslike VMotion,DRS,orHAaretransferredamonghosts. Duringperiodsoflicenseserverunavailability,althoughnewlicensescannotbe issued,existingVirtualCenter Serverlicensedfunctionalitycontinuestooperate indefinitelyandexistingESX Serverlicensedfunctionalitycontinuestooperate withina14daygraceperiod.SeeLicenseServerAvailabilityonpage 60. VMwarerecommendsthatyouusecentralizedlicensingforlarge,changing environments.
Single-Host Licensing
Therearetwoscenariosforsinglehostlicensing: HostbasedserialnumberFortheESXServer3iStandaloneedition,eachhost hasaserialnumberthatissuppliedbythehardwarevendorandistypically preinstalled.Iftheserialnumberisnotpreinstalled,itmightbeenclosedona stickeroracard. HostbasedlicensefileForallotherESXServer3ieditionsincludingVI3 Foundation,VI3Standard,andVI3 Enterpriseeachhosthasalicensefile.
56
VMware, Inc.
Forhostbasedlicensefiles,thefollowingrulesapply: Yourtotalentitlementforpurchasedfeaturesisdividedamongseparatelicense filesresidingonESX ServerhostsandtheVirtualCenter Server. Whensomeoneactivatesalicensedfeature,thefeatureforthatentitlementmust resideinthelicensefileonthathost. YoumaintainseparatelicensefilesoneachESX Serverhost.Distributionofunused licensesisnotautomatic,andyoudonotdependonanexternalconnectionfor licensing. Theadvantagesofhostbasedlicensefilesinclude: SinglehostfilesrequirenolicenseservertobeinstalledforESX Serverhostonly environments. InaVirtualCenterandlicenseserverenvironment,hostbasedlicensefilesallows ESX Serverhostlicensestobemodifiedduringperiodsoflicenseserver unavailability.
VMware, Inc.
57
Per-Processor Licensing
FormostVMwareInfrastructureproducts,youpurchaselicensesonaperprocessor basis,whichmeansthatyouneedtoindicatethetotalnumberofprocessors,nothosts, thatwillruntheproducts.Youcanthendeployandredeploythepurchasedprocessor capacity,soldinincrementsoftwoprocessors,onanycombinationofhosts. Forexample,youpurchaseESX ServerlicensesfortenprocessorsandVMotionlicenses forsixprocessors.Youcanthendeploythoselicensesonanyofthefollowing combinationsofservers: ESX Serveronfive2processorhosts.EnableVMotiononthreehosts. ESX Serveronthree2processorhostsanda4processorhost.EnableVMotionon three2processorhosts,oronone2processorhostanda4processorhost. ESX Serverontwo4processorhostsandone2processorhost.EnableVMotionon one4processorhostandone2processorhost. ESX Serveronone8processorhostandone2processorhost.VMotionbetween thesetwohostscannotbeenabledunlessyoupurchaseanadditional4processor VMotionlicense.
58
VMware, Inc.
Specialconsiderationsinclude: Dualcoreandquadcoreprocessors,suchasIntelx86processorsthatcombinetwo orfourindependentcentralprocessingunitsonasinglechip,countasone processor. Youcannotpartiallylicenseamultiprocessorhost.Forexample,a4CPUhost requiresalicensewiththecapacityforfourprocessors. Singleprocessorlicensingissupportedforserverbasedlicenses.Ingeneral,for serverbasedlicensing,checkoutoflicensesinoddquantitiesissupported. However,hostbasedfilescannotbegeneratedwithoddquantities.Theymustbe generatedinmultiplesoftwo. Thefollowingfeaturesarelicensedonaperprocessorbasis: ESX ServerTopoweronavirtualmachine,ahostmusthavelicensingona perprocessorbasis.Thismeansadualprocessorhostrequirestwomatching ESX Serverlicenses.AfourprocessormachinerequiresfourmatchingESX Server licenses.SeeESX Server 3iEditionsonpage 52. VMwareConsolidatedBackup(VCB)TousetheConsolidatedBackup capabilitiesandbackupofallvirtualmachinesrunningonanESX Serverhosta VCBlicensekeymustbeavailableforeachprocessorwithinthathost.Fora descriptionofthisfeature,seetheVirtualMachineBackupGuide. VirtualCenterAgentforESX ServerThisagentisinstalledonanESX Server hostwhenitisaddedtotheVirtualCenter Server.Youmusthaveoneagentlicense keyforeachESX ServerprocessortobeaddedtoVirtualCenter. ServerVMotionandStorageVMotionTomigrateapoweredonvirtualmachine betweenhosts,eachESX ServerprocessorinvolvedmusthaveaVMotionlicense key.Forexample,ifyouuseVMotionfromadualprocessorESX Serverhostto anotherdualprocessorhost,youmusthavefourVMotionlicenses.SeeBasic SystemAdministration. VMwareHATorestartvirtualmachineswhoseESX Serverhosthasfailed,the VirtualCenter ServermusthaveanHAlicensekeyforeachESX Serverprocessor intheHAcluster.Foradescriptionofthisfeature,seetheResourceManagement Guide. VMwareDRSandDPMToprovideautomaticloadbalancingofvirtual machinesamonghostsanddistributedpowermanagement,the VirtualCenter ServermusthaveaDRSandDPMlicensekeyforeachESX Server processorintheDRScluster.Asaprerequisite,DRSrequiresappropriateVMotion licensekeysforallhostsintheDRScluster.Foradescriptionofthisfeature,seethe ResourceManagementGuide.
VMware, Inc. 59
Per-Instance Licensing
Featuresthatarelicensedonaperinstancebasisrequireonlyonelicensekeyforeach featureinstance,regardlessofthenumberofprocessorsused.TheVirtualCenter Server iscurrentlytheonlyfeaturelicensedonaperinstancebasis.Forinformationabout differenteditionsofVirtualCenter,seeVirtualCenter ServerEditionsonpage 54.
60
VMware, Inc.
DuringtheESX Servergraceperiod,whenthelicenseserverisunavailable,the followingoperationsareunaffected: Virtualmachinescontinuetorun.YoucanusetheVI Clienttoconfigureand operatevirtualmachines. ESX Serverhostscontinuetorun.YoucanconnecttoanyESX Serverhostinthe VirtualCenterinventoryforoperationandmaintenance.Connectionsto VirtualCenterremain.YoucanusetheVI Clienttooperateandmaintainvirtual machinesfromthehosteveniftheVirtualCenter Serverconnectionisalsolost. Duringthegraceperiod,restrictedoperationsinclude: AddingESX ServerhoststotheVirtualCenterinventory.Youcannotchange VirtualCenteragentlicensesforhosts. Addingorremovinghostsfromacluster.Youcannotchangehostmembershipfor thecurrentVMotion,HA,orDRSconfiguration. Addingorremovinglicensekeys. Whenthegraceperiodexpires,cachedlicenseinformationisnolongerstored.Asa result,virtualmachinescannolongerbepoweredon.Runningvirtualmachines continuetorunbutcannotberebooted. Whenthelicenseserverbecomesavailableagain,hostsreconnecttothelicenseserver. Norebootingormanualactionisrequiredtorestorelicenseavailability.Thegrace periodtimerisresetwheneverthelicenseserverbecomesavailableagain.
VMware, Inc.
61
Table 63displaysESX Serverlicensedoperationspermittedwhilethelicenseserveris unavailable.Operationsthatarenotpermittedareoperationsthatrequirethe acquisitionofnewlicensesfromthelicenseserver. Table 6-3. Permitted ESX Server Operations When the License Server Is Unavailable
During Grace Period Permitted Permitted Permitted Permitted Permitted Permitted Permitted Permitted Permitted NotPermitted After Grace Period Expires NotPermitted Permitted Permitted Permitted Permitted Permitted Permitted Permitted NotPermitted NotPermitted
Component Virtualmachine
ESX Serverhost
62
VMware, Inc.
Table 64listsVirtualCenterlicensedoperationsthatarepermittedwhenthelicense serverisunavailable.Operationsthatarenotpermittedareoperationsthatrequirethe acquisitionofnewlicensesfromthelicenseserver. Table 6-4. Permitted VirtualCenter Operations When the License Server Is Unavailable
When License Server Is Unavailable Permitted NotPermitted Permitted Permitted Permitted Permitted NotPermitted Permitted Permitted Permitted NotPermitted
Attempted Action RemoveanESX Serverhostfrominventory(see nextentry) AddanESX Serverhosttoinventory ConnectandreconnecttoanESX Serverhostin inventory Moveapoweredoffvirtualmachinebetween hostsininventory(coldmigration) MoveanESX Serverhostamongfoldersin inventory MoveanESX Serverhostoutofa VMotionDRSHAcluster(seenextentry) MoveanESX Serverhostintoa VMotionDRSHAcluster ConfiguretheVirtualCenter Serverwith VI Client StartVMotionbetweenhostsininventory ContinueloadbalancingwithinaDRScluster Addorremovelicensekeys
VMware, Inc.
63
VirtualCenterusesaheartbeatmechanismtocheckwhetherthelicenseserveris reachableandtoseeifthereareanychangesinthelicensefile.Theheartbeatintervalis fiveminutes.Therefore,itmighttakeVirtualCenteraslongasfiveminutestodetect licensechangesorifthelicenseserverhasbecomeunavailable. Whenthelicenseserverbecomesunavailable,orifachangeinthelicensefilecausesa checkedoutlicensetoberemoved,VirtualCentermarkstheaffectedlicensesas UnlicensedUse,andthelicensedfeaturescontinuetooperateaspreviously described.Whenthelicenseserverbecomesavailableagain,orwhenlicensesareadded tothelicensefileagain,VirtualCenterchecksoutthelicensesagainandrevertsthemto theLicensedstate.Ifalicensecannotbecheckedout,thelicenseremainsinthe UnlicensedUsestate. Iflicenseserveravailabilityisaparticularconcerninyourenvironment,considerone ofthefollowingstrategies: InstallthelicenseserveronthesamemachineastheVirtualCenter Server.Thisis thedefaultoptionthattheVirtualCenterinstallerprovides. Installthelicenseserveronavirtualmachine,andplacethatvirtualmachineinan HAcluster.VMwareHArestartsthelicenseservermachineonanotherESX Server hostincaseoffailure. UsesinglehostlicensefilesonESX Serverhosts.
64
VMware, Inc.
Contacting Support
Ifyourequireassistancewithlicensing,contactVMwareforsupportasfollows: IfyoudidnotreceivelicenseactivationcodesforyourVI3purchaseorhave difficultiesinusingyourlicenseactivationcodestoobtainlicensefiles,email vihotline@vmware.com. Ifyouhavelicensefilesandhavedifficultyconfiguringortroubleshootinglicensed features,fileasupportrequestathttp://www.vmware.com/support.
VMware, Inc.
65
66
VMware, Inc.
Thischapterprovidesinformationabouthowtoevaluateanupgradedlicenseof VirtualCenter 2.5andESX Serverversion3.5andhowtoobtainlicenseswhenthe evaluationmodeexpires.Thischaptercontainsthefollowingtopics: UsingEvaluationModeforESX Serveronpage 67 UsingEvaluationModeforVirtualCenteronpage 68 LicensingVirtualCenterandESX ServerAftertheEvaluationPeriodExpireson page 68
VMware, Inc.
67
Licensing VirtualCenter and ESX Server After the Evaluation Period Expires
Afterthe60dayevaluationperiodexpires,unlessyouobtainlicensesforyour software,youcannotperformmostoperationsinVirtualCenterandESX Server.For example,youcannotpoweronvirtualmachines,addnewhosts,oruseadvanced ESX ServerandVirtualCenterfeatures. IfyoudonotlicenseVirtualCenterbeforetheevaluationperiodexpires,allofthehosts intheVirtualCenterinventoryaredisconnected. NOTEReinstallingtheVirtualCenter Serverafterthe60dayevaluationexpiresdoesnt restartevaluationmode. Table 71detailstheESX Serverbehaviorafterevaluationmodeexpires.Theoperations thatarenotpermittedrequiretheacquisitionofnewlicenses. Table 7-1. ESX Server Operations After the 60-Day Evaluation Period
Component Virtualmachine Attempted Action Poweron Createanddelete Suspendandresume ConfigurevirtualmachinewiththeVI Client After 60 Days NotPermitted Permitted Permitted Permitted
68
VMware, Inc.
Chapter 7 Running VMware VirtualCenter and VMware ESX Server in Evaluation Mode
Table 7-1. ESX Server Operations After the 60-Day Evaluation Period (Continued)
Component ESX Serverhost Attempted Action Continueoperationsonexistinghosts Poweronandpoweroff ConfigureESX ServerhostwiththeVI Client Restartvirtualmachineswithinthefailed hostsHAcluster Addorremovelicensekeys After 60 Days Permitted Permitted Permitted NotPermitted Permitted
VMware, Inc.
69
70
VMware, Inc.
Thischapterprovidesproceduresforredeeminglicensefilesandconfiguringlicense options. Thischaptercontainsthefollowingsections: LicensingProcessonpage 72 ObtainingLicenseFilesonpage 75 SettingUpCentralizedLicensingonpage 75 SettingUpSingleHostLicensingonpage 80 LicenseFileContentsonpage 83 LicenseFileLocationsonpage 85 AddingNewLicenseFilestoLicenseServersonpage 85 AddingNewLicenseFilestoSingleHostsonpage 86 InstallingaLicenseServeronpage 87 TroubleshootingLicensingonpage 88
VMware, Inc.
71
Licensing Process
Figure 81summarizesthelicenseconfigurationprocessesforESX Server 3i. Figure 8-1. License Configuration Process for ESX Server 3i
Purchase the ESX Server 3i host
Yes
No
Yes
No
72
VMware, Inc.
Figure 82summarizesthelicenseconfigurationprocessesfortheVirtualCenter Server. Figure 8-2. License Configuration Process for VirtualCenter
Acquire VirtualCenter installer Purchase licenses
No
Run installer
Yes
No
VMware, Inc.
73
AfteryoupurchaseVMwareInfrastructuresoftware,dothefollowingtoobtainanduse yourlicenses: 1 Decidewhichlicensetypetouse. ForESXServer3iStandaloneaddition,youcanuseahostbasedserialnumber. VI3 editionsofESXServerandVirtualCenteruseFLEXnetlicensing,whichoffers achoiceoflicensetypes:centralized,singlehost,ormixed.See VirtualCenterand ESX Server 3iLicensingModelonpage 54. 2 Registeryourpurchase. WhetheryoupurchasedVMwareInfrastructure3fromanauthorizedVMware resellerordirectlyfromVMware,youmustregisteryourpurchasetoyour VMwarestoreaccount.SeeObtainingLicenseFilesonpage 75. 3 Obtainlicensefiles. Afteryourpurchaseisregistered,usetheWebbasedlicenseactivationportalto generateanddownloadlicensefilesappropriatetothelicensetypeyouchosein Step 1.SeeObtainingLicenseFilesonpage 75. 4 5 InstallVirtualCenter. ConfigureyourlicensingaccordingtothelicensetypeyouchoseinStep 1: Toconfigurecentralizedlicensing,seeSettingUpCentralizedLicensingon page 75. Toconfigurelicensingforasinglehost,seeSettingUpSingleHost Licensingonpage 80. Toconfigureamixedlicenseenvironment,seeSingleHostandCentralized LicensingintheSameEnvironmentonpage 81.
74
VMware, Inc.
VMware, Inc.
75
76
VMware, Inc.
ClickOKtosaveyourchanges. Youdonotneedtochangeanyothersettingstoenablecentralizedlicensing.
Thetotalnumberoflicensesconsumedandavailableonthelicenseserverare summarizedontheLicensestabintheAdminviewoftheVI Clientconnectedto VirtualCenter.ThistabwaslabeledLicenseViewerinearlierversionsof VirtualCenter. NOTEIfyoudidnotselectthecheckboxfortheoptionalsetting,seeToconfigure centralizedlicensingforanESX Serverhostonpage 77tomanuallyconfigure ESX Serverhoststousecentralizedlicensing. To configure centralized licensing for an ESX Server host 1 2 3 4 FromtheVI Client,selectthehostintheinventory. ClicktheConfigurationtab. UnderSoftware,clickLicensedFeatures. Tosetthelicenseserver: a b ClickEdittotherightofLicenseSources. ClickUseLicenseServer. Thisisthedefaultconfiguration. c EntertheportnumberandlicenseservermachinenameintheAddressfield, asinport@host. Forexample,withthedefaultlicenseserverport27000onalicenseserver calledlicense1,yourentrymightlooklikethis:
27000@license-1.vmware.com
ClickOKtoclosethedialogboxandsaveyourchanges.
VMware, Inc.
77
SettheESX Serveredition: a b ClickEdittotherightofESX ServerLicenseType. Specifytheeditionforthehost,orselectUnlicensedtoreleasethishosts licensesbacktothelicenseserver.TheESX ServerLicenseTypedialogbox displaysonlythoseeditionsthatareavailabletoyourESX Serverhost. ClickOKtoclosethedialogboxandsaveyourchanges.
c 6
Thetotalnumberoflicensesconsumedandavailableonthelicenseserverare summarizedontheLicensestabintheAdminviewoftheVI Clientconnectedto VirtualCenter.ThistabwaslabeledLicenseViewerinearlierversionsof VirtualCenter. To configure local license server licensing for VirtualCenter 1 2 3 4 FromtheVI Client,chooseAdministration>VirtualCenterManagementServer Configuration. ClickLicenseServerinthelistontheleft. ClickUselicenseservicesonthisVirtualCenter Server. IfyouwanttochangetheVirtualCenterServeredition,selectoneofthefollowing: VCFoundationEdition VCFullEdition FormoreinformationontheVirtualCentereditions,seeVirtualCenter Server Editionsonpage 54. 5 (Optional)IfyoudonotwantVirtualCentertooverridethehostscurrentlicense setting,deselectChangehostlicenseserversettingstomatchVirtualCenters settingwhentheyareaddedtoinventory. SelectingthischeckboxcausesVirtualCentertooverridethehostscurrentlicense settingandinsteadusethelicenseserverthatVirtualCenteruses. MakesurethatyouuseanIPaddressthatisaccessiblefromtheESX Serverhost. IfyouconfigureVirtualCentertousealocallicenseserverandthehostnameofthe locallicenseserver(theVirtualCenterhost)isnotresolvablefromtheESX Server host,thentheESX Serverhostcannotacquirelicensesfromthelocallicenseserver.
78
VMware, Inc.
Thetotalnumberoflicensesconsumedandavailableonthelicenseserverare summarizedontheLicensestabintheAdminviewoftheVI Clientconnectedto VirtualCenter.ThistabwaslabeledLicenseViewerinearlierversionsof VirtualCenter. NOTEIfyoudidnotselectthecheckboxfortheoptionalsetting,seeToconfigure centralizedlicensingforanESX Serverhostonpage 77tomanuallyconfigure ESX Serverhoststousecentralizedlicensing.
VMware, Inc.
79
5 6
ClickOKtosaveyourchanges.
VMware, Inc.
81
Configuring Licensing for a Mixed ESX Server 2.x and ESX Server 3.x Environment
YoucanusetheVirtualCenter Server2.xtomanageamixedenvironmentofboth ESX Server2.xandESX Server3.xhosts.Youreceivelicenseactivationcodeswith purchasesofVMwareInfrastructure3.Youcanredeemthecodesforboth ESX Server 2.xserialnumbersandVMwareInfrastructure3licensefiles. To configure licensing for the ESX Server 2.x hosts in the mixed environment 1 2 LeavethelicensingunchangedonexistingESX Server2.xhoststhatuseserial numbers. FornewESX Server2.xinstallations,redeemyourlicenseactivationcodesonthe licenseactivationportalforESX Server2.xserialnumbers. Providetheseserialnumbersatthetimeofinstallationorconfiguration. 3 Redeemyourlicenseactivationcode(s)togenerateacentralizedlicensefilethat containslicensesforVirtualCenter Server,VirtualCenterManagementAgents, VMotion,andESX Server3.x. Ifnecessary,combinemultiplegeneratedlicensefilestoproduceasinglefile. YourgeneratedlicensefilecanincludeESX Serverversion3.xlicensesforthe ESX Serverversion2.xhoststhatyouobtainedESX Server2.xserialnumbersforin Step 2.Thisletsyoueasilydistributelicensestothesehostsiftheyarelater upgradedtoESX Server3.x. 4 InstallandconfiguretheVirtualCenter Server2.xtousethelicenseserver.
82
VMware, Inc.
To change ESX Server hosts from centralized licensing to host-based licensing 1 UsetheVMwarelicenseactivationportaltogenerateanddownloadnew singlehostlicensefilesforeachESX Serverhost. Thelicenseactivationportalletsyougeneratebothsinglehostandcentralized licensefilesfromthesamelicenseactivationcode.Forhostbasedlicensing,you needonelicensefileforeachESX Serverhost. 2 IfyouareusingVirtualCenter,changeyourVirtualCenter Serversettingssothat VirtualCenterdoesnotoverridehostlicensesettings,asdescribedinSingleHost andCentralizedLicensingintheSameEnvironmentonpage 81. ConfigureyourESX ServerhostasdescribedinConfiguringanESX Server MachineforHostBasedLicensingonpage 80.
VMware, Inc.
83
Centralizedfilesandsinglehostfilescanbedifferentiatedbythefollowing distinguishingfeatures: Singlehostlicensefilescontainnolicensetypesection.Centralizedfilescontaina licensetypesectionasthefileheader. SinglehostlicensefilescontainthestringlicenseType=Hostaspartofeach licensekeyblockinthefile.Centralizedlicensefilescontainthestring licenseType=Serveraspartofeachlicensekeyblockinthefile,asshowninthe followingexamples. Example 81showsatypicalsinglehostlicensekey. Example 8-1. Single-Host License Key
INCREMENT PROD_ESX_FULL VMWARELM 2005.05 31-dec-2008 uncounted \ VENDOR_STRING="licenseType=Host;vmodl=esxFull;desc=ESX Server \ Enterprise;capacityType=cpuPackage;gp=14;exclude=BACKUP;count=8" \ HOSTID=ANY ISSUED=06-AUG-2007 \ NOTICE="FulfillmentId=777;Name=VMware Internal" TS_OK \ SIGN="095A 14A7 ..."
84
VMware, Inc.
NOTEInVirtualCenter 2.0,thedefaultlocationofthelicensefilewas C:\Documents and Settings\All Users\Application Data\VMware\ VMware License Server\vmware.lic.Thislocationnolongerexists. Youcanaddnewlicensefilestothelicensedirectory.SeeAddingNewLicense FilestoLicenseServersonpage 85. Singlehostlicensefilesareplacedatthefollowingdefaultlocationonthe machinerunningESX Server.
/etc/vmware/vmware.lic
RestarttheVMwareLicenseServerservice.
ThefollowingprocedureisforWindows2000Professional.Themenusandcommands forotherversionsofWindowscanvary.
VMware, Inc.
85
To restart the license server Windows Service 1 2 3 4 ChooseStart>Settings>ControlPanel. DoubleclickAdministrativeTools. DoubleclickServices. Scrolldown,rightclickVMwareLicenseServer,andchooseRestart.
Youcanchangethedefaultlocationofyourcentralizeddirectory,oryourlicensefile. To change the default location of the license directory 1 2 3 Onthecomputerthatrunsthelicenseserverapplication,chooseStart>Programs >VMware>VMwareLicenseServer>VMwareLicenseServerTools. ClicktheConfigServicestab. ClickBrowsenexttothePathtolicensefilefield,andchoosealicensefilefrom thelicensedirectory. Ifyouwantthelicenseservertousetheentirelicensedirectory,manuallyremove thenameofthefile,leavingonlythenameofthedirectory. 4 5 6 7 ClicktheStart/Stop/Rereadtab. ClickStop. ClickStart. ClickReReadLicenseFiletoloadthenewlicensefiles.
86
VMware, Inc.
VMware, Inc.
87
7 8
ClickInstalltobegintheinstallation. ClickFinishtocompletethelicenseserverinstallation.
Troubleshooting Licensing
Thissectionprovidesguidelinesfortroubleshootingyourlicensesetup.Ifyouarenot abletoresolveyourproblemswithlicensingbyusingtheinformationgiveninthis section,contactVMwareforsupportasfollows: IfyoudidnotreceivelicenseactivationcodesforyourVI3purchaseorhave difficultiesinusingyourlicenseactivationcodestoobtainlicensefiles,email vihotline@vmware.com. Ifyouhavelicensefilesandhavedifficultiesinconfiguringortroubleshooting licensedfeatures,fileasupportrequestathttp://www.vmware.com/support.
88
VMware, Inc.
To check that the license server Windows service is running 1 2 3 Onthemachineonwhichthelicenseserverisinstalled,chooseStart>Control Panel>AdministrativeTools>ServicestodisplaytheServicescontrolpanel. VerifythattheStatuscolumnfortheVMwareLicenseServerentryreadsStarted. IftheVMwareLicenseServerisnotstarted,startitbyrightclickingontheservice andchoosingStart.
To check that the license server is listening 1 2 3 Onthemachineonwhichthelicenseserverisinstalled,chooseStart>Command Prompt. Typenetstat -abatthecommandline. Verifythatthelmgrd.exeprocessislisteningonport27000andthatthe VMWARELM.exeprocessislisteningonport27010. Ifnot,thelicenseservermightnotbeinstalledormightnotbestarted.
VMware, Inc.
89
To check the license server status 1 Onthemachineonwhichthelicenseserverisinstalled,chooseStart>Programs> VMware>VMwareLicenseServer>VMwareLicenseServerToolstolaunchthe LMTOOLSutility. ClicktheServerStatustabtodisplaytheServerStatuspage. ClickPerformStatusInquiry. Licenseserverinformation,includingthelocationofthelicensefile,appearsatthe bottomofthepage.
2 3
90
VMware, Inc.
VMware, Inc.
91
92
VMware, Inc.
ThischapterdescribeshowtoprepareyourVirtualCenterdatabase,installVMware InfrastructureManagementsoftware,andconfigurecommunicationbetween components.YoucaninstallVMwareInfrastructureManagementsoftwareona physicalsystemoronavirtualmachinerunningonanESX Serverhost. Thischaptercontainsthefollowingtopics: PreparingtheVirtualCenter ServerDatabaseonpage 93 InstallingVMwareInfrastructureManagementSoftwareonpage 99 ConfiguringCommunicationBetweenVirtualCenterComponentsonpage 103 UninstallingVMwareInfrastructureComponentsonpage 105 InstallingVirtualCenteronaVirtualMachineonpage 106
VMware, Inc.
93
Createauser,suchasvpxAdmin,foraccessingthistablespacethroughODBC:
CREATE USER vpxAdmin IDENTIFIED BY vpxadmin DEFAULT TABLESPACE vpx;
94
VMware, Inc.
Eithergrantdbapermissiontotheuser,orgrantthefollowingpermissionsto theuser:
grant grant grant grant grant grant grant grant connect to <user> resource to <user> create view to <user> create any sequence to <user> # For VirtualCenter upgrade only create any table to <user> # For VirtualCenter upgrade only execute on dbms_job to <user> execute on dbms_lock to <user> unlimited tablespace to <user> # To ensure space limitation is not an issue
CreateanODBCconnectiontothedatabase.Thefollowingareexample settings:
Data Source Name: VMware VirtualCenter TNS Service Name: VPX User Id: vpxAdmin
Inthisexample,xxiseither 9Ior10g.
VMware, Inc.
95
UsetheNet8ConfigurationAssistanttoaddthefollowingentry:
VPX = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS=(PROTOCOL=TCP)(HOST=vpxd-Oracle)(PORT=1521)) ) (CONNECT_DATA = (SERVICE_NAME = VPX) ) ) HOST =
Inthisexample,HOSTisthemanagedhosttowhichtheclientneedstoconnect.
2 3 4 5
8 9
10 11
VMware, Inc.
97
Toidentifytheauthenticationtype: a b c OpenSQLServerEnterpriseManager. ClickthePropertiestabtoviewproperties. Checkthemode. ThemodeindicateseitherWindowsNTorSQLServerauthenticationtype. 12 TypeyourSQLServerloginnameandpassword. Askyourdatabaseadministratorforthisinformation. 13 14 15 16 ClickNext. SelectthedatabasecreatedforVirtualCenterfromtheChangethedefault databasetomenuandclickNext. ClickFinish. FromtheODBCMicrosoftSQLServerSetupmenu,chooseTestDataSource. Ifthetestdatasourceisacceptable,clickOK.Ifitisnotacceptable,clickBackand reconfigureanyincorrectitems. 17 18 ToclosetheODBCDataSourceAdministrator,clickClose. EnsurethattheSQLAgentisrunningonyourdatabaseserver. ThisappliestoSQLServer2000andSQLServer2005editions.
98
VMware, Inc.
VMware, Inc.
99
YoucandeployVirtualCenterbehindafirewall.However,makesurethereisno NetworkAddressTranslation(NAT)firewallbetweenVirtualCenterandthehosts itwillmanage. Theinstallerautomaticallyinstallsalicenseserverforyou,unlessyouenterapath toanexistinglicenseserver. Ifyouwanttouseanexistinglicenseserver,obtainthehostnameorIP address. Ifyouaregoingtoallowtheinstallertoinstallalicenseserver,youneeda validservedlicensefile. Becausethelicenseserverdoesnotsupportlicensefilesonanetworkshare, placeyourlicensefilesinadirectoryonasystemwhereyouareinstallingthe licenseserver.
Components Installed
TheVMwareInfrastructureManagementinstallerincludesthefollowingcomponents: VMwareVirtualCenterServerAWindowsservicetomanageESXServerhosts. VIClientAclientapplicationusedtoconnectdirectlytoanESXServeror indirectlytoanESXServerthroughaVirtualCenterServer. Microsoft.NETFrameworkSoftwareusedbytheVirtualCenterServer,Database Upgradewizard,andtheVIClient. MicrosoftSQLServer2005ExpressAfreeversionoftheMicrosoftSQLServer databaseforsmallerscaleapplications.Ifyouenterapathtoanexistingdatabase, theinstallerdoesnotinstallMicrosoftSQLServer2005Express. VMwareUpdateManager(optional)AVirtualCenterpluginthatprovides securitymonitoringandpatchingsupportforESXServerhostsandvirtual machines. VMwareConverterEnterpriseforVirtualCenterServer(optional)A VirtualCenterpluginthatenablesyoutoconvertyourphysicalmachinestovirtual machines. VMwarelicenseserverAWindowsserviceallowingallVMwareproductstobe licensedfromacentralpoolandmanagedfromoneconsole.Ifyouenterapathto anexistinglicenseserver,theinstallerdoesnotinstallalicenseserver.
100
VMware, Inc.
Installation Procedure
ThefollowingproceduredescribeshowtoinstallallVMwareInfrastructure managementcomponents. To install VMware Infrastructure Management 1 2 AsAdministratorontheWindowssystem,inserttheinstallationCD. WhentheVMwareInfrastructureManagementInstallerscreenappears,click Next. IftheVMwareInfrastructureManagementInstallerscreendoesnotappear, doubleclicktheautorun.exeicon. 3 4 5 6 ReadtheIntroductionpageandclickNext. SelectIacceptthetermsinthelicenseagreementandclickNext. TypeyourusernameandcompanynameandclickNext. SelectoneoftheinstallationtypesandclickNext. Thechoicesare: InstalltheVI Client. InstallVirtualCenter. Chooseacustominstallationtoinstallmultiplecomponents. 7 Selecttheoptioncorrespondingwiththedatabaseyouconfigured. Ifyouhavenotconfiguredasupporteddatabase,clickInstallMicrosoftSQL Server2005Express.Thisdatabaseissuitableforsmalldeploymentsofupto 5 hostsand50virtualmachines. Ifyouhaveconfiguredasupporteddatabase,clickUseanexistingdatabaseand enteryourdatabaseconnectioninformation: a Typethedatasourcename(DSN)associatedwithyourdatabase. ThismustbeasystemDSN. b IfyourdatabaseisalocalSQLServerdatabaseusingWindowsNT authentication,leavetheusernameandpasswordfieldsblank.Otherwise, typetheusernameandpasswordassociatedwiththedatasourcenameand clickNext. Ifyourconnectionfails,awarningappears.ClickOKandreenteryour databaseconnectioninformationuntilyoucancontinue.
VMware, Inc.
101
Selectoneofthefollowingoptions: TouseVirtualCenterinevaluationmode,selectIwanttoevaluate VirtualCenterServerandclickNext. Ifyouchoosethisoption,theenterpriseleveleditionofVirtualCenteris installedinevaluationmode.TheVMwareLicenseServerisalsoinstalledso thatyoucanswitchtolicensedmodeduringoraftertheevaluationperiod. TouseVirtualCenterinlicensedmodewithanexistinglicenseserver: i ii iii SelectUseanexistingLicenseServer. Enterthepathtoyourexistinglicenseserver. SelecttheVirtualCentereditionthatyoupurchasedandclickNext.
Ifyouchoosethisoption,theVMwareLicenseServerisinstalled. 9 Entertheportandproxyinformationthatyouwanttouseoracceptthedefault informationshownonscreenandclickNext.Thisstepappliesonlytocustom installations. ThedefaultportforHTTPSis443.IfyouconfigureVirtualCentertouseadifferent portforHTTPS,youmustusetheconfiguredportnumberwhenyouloginto VirtualCenterinthisformat:<ipaddress>:<portnumber> 10 EnterinformationaboutthesystemonwhichyouareinstallingVirtualCenterand clickNext. Enter: TheIPaddressordomainnameofthesystemonwhichyouareinstalling VirtualCenter. Theloginandpasswordthatyouusetologintothesystemonwhichyouare installingVirtualCenter. 11 ForVMwareUpdateManager,youcanusethesamedatabasethatyouusefor VirtualCenter,oryoucanuseanotherdatabase.SeeStep 7.
102
VMware, Inc.
12
13
14
AcceptthedefaultdestinationfoldersandclickNext. Ifyoudonotwanttoacceptthedefaultdestinationfolders: ForVMwareInfrastructure,clickChangetoselectanotherlocationandclick Next. Fordownloadingpatches,clickChangetoselectanotherlocationandclick Next. CAUTIONToinstalltheVMwareInfrastructurecomponentsonadriveotherthan theC:drive,verifythereisenoughspaceintheC:\WINDOWS\Installerfolderto installtheMicrosoftWindowsInstaller.msifile.Ifyoudonothaveenoughspace, becauseofaknownissuewithWindowsInstaller,yourVMwareInfrastructure installationmightfail.
15
16
ClickFinishtocompletetheVMwareInfrastructureinstallation.
VMware, Inc.
103
104
VMware, Inc.
To enable a VirtualCenter-managed host to receive data on the default port Openport902inthefirewalltoallowdatatransfertotheVirtualCentermanagedhost fromVirtualCenteroranotherVirtualCentermanagedhost.Foradditionalinformation onconfiguringtheports,seeyourfirewallsystemadministrator.
VMware, Inc.
105
3 4
ClickYestoconfirmthatyouwanttoremovetheprogram. ClickFinish.
106
VMware, Inc.
10
10
Softwareupdatesmightbepatchesforaddressingcriticalsecurityissuesorurgentbug fixes,ortheymightbegeneralupdatesormaintenancereleases.Theymightbelocated onthelocalfilesystemoronanNFS,FTP,orHTTPserver.Eachupdateconsistsofa descriptorfileandasetofpackages.Thedescriptorcontrolstheinstallationprocessand checksthatrequirementsaremet.Forexample,youmightberequiredtopoweroffall virtualmachinesrunningontheserveryouareabouttoupdate,oryoumightneedto reboottheserveraftertheupdate. Thischapterdiscussestwoutilitiesyoucanusetoapplysoftwareupdatestothe VI ClientandESX Server 3isoftware.TheVMwareInfrastructureUpdateisagraphical userinterface(GUI)application.Thevihostupdateutilityisaremotecommandline interface(CLI)tool.Theseutilitiesarediscussedinthefollowingsections: PerformingMaintenancewithInfrastructureUpdateonpage 107 PerformingMaintenanceWiththevihostupdateUtilityonpage 111 RollingBackanUpdateonpage 114
VMware, Inc.
107
TheInfrastructure Updateperiodicallychecksfornewupdatesthatareapplicableto ESX Server 3ihostsconnectedtotheVI Client.Ifnewupdatesarediscovered, Infrastructure Updatedownloadstheimageandthecompanionsoftwareinthe background,andcachesthedownloadedupdatesinalocalrepository. NOTESoftwareupgradesaredifferentfromupdates.Upgradesareformajorreleases ofthetypex.0andminorsoftwarereleasesofthetypex.y.Forexample,ESX Server 2.0 andESX Server 2.5. VMwareupdatesareformaintenancereleasesofthetypex.y.zandpatches.For example,ESX Server2.5.3andESX Server2.5.3Patch2.Updatesarediscussedinthis chapter. Seehttp://www.vmware.com/download.
108
VMware, Inc.
To schedule a different day and time for update checks 1 2 ChooseStart>Programs>VMware>Infrastructure Update. OntheUpdatestab,enteradifferentdayandtime.
Afterallupdatesareapplied,VMwareUpdaterestartsallaffectedservices.
VMware, Inc.
109
5 6 7
To add hosts to the managed hosts list 1 2 3 ChooseStart>Programs>VMware>VMwareInfrastructure Update. OntheHoststab,selectthehoststocheckforupdates. OntheUpdatestab,clickCheckNow.
VMware, Inc.
111
To update a host 1 Poweroffanyvirtualmachinesthatarerunningonthehosttoupdate. Whenyourunthevihostupdateutility,thesoftwareplacesthehostinto maintenancemode.Thehostcannotbeplacedintomaintenancemodeunlessyou firstpoweroffallvirtualmachinesthatarerunningonthehost. 2 Onahostotherthanthehostyouareupdating,powerontheRemoteCLIandlog in. Youdonotneedtotypethepasswordonthecommandline.Ifnopasswordis specified,thetoolpromptsyouforthepasswordwithoutechoingtheoutputtothe terminal.Thismeansthepasswordyoutypeisnotvisibleinthewindowasyou runthecommand. YoucancreateasecureconnectiontotheRemoteCLI,byusingtheRemoteCLIIP address.IfyouareusingtheVI Client,youcanrightclicktheRemoteCLIand selectOpenConsole.IftheRemoteCLIisinstalledonyourWindowsorLinux system,youcanusetheinstalledapplication,inwhichcaseyoudonotneedtolog in. 3 4 5 DownloadthefileandcopyittotheRemoteCLIfilesystem. Runthevihostupdateutility. Rebootthehostfortheupdatestotakeeffect.
Forcommandsyntaxexamples,seeExamples:thevihostupdateUtilityonpage 113.
112
VMware, Inc.
--m
--q
VMware, Inc.
113
114
VMware, Inc.
11
11
ESX Server 3imonitoringletsyouchecktheconditionofthefollowinghost components: CPUprocessors Fans Memory Storage Temperature To monitor the condition of a host 1 2 LogontotheVI Clientandselecttheserverfromtheinventorypanel. ClicktheConfigurationtabandclickHealthStatus.
Ifacomponentisfunctioningnormally,thestatusindicatorisgreen.Theindicator changestoyelloworredifasystemcomponentviolatesaperformancethresholdoris notfunctioningproperly.Generally,ayellowindicatorsignifiesdegradedperformance. Aredindicatorsignifiesthatacomponenthasstoppedoperatingorhasexceededthe highestthreshold. TheReadingcolumndisplaysthecurrentvaluesforthesensors.Forinstance,this columndisplaysrotationsperminute(RPM)forfansanddegreesCelsiusfor temperature. IfyouareusingVMwareDistributedResourceScheduler(DRS)andVMwareHigh Availability(HA),theseservicescantakeactionwhenhardwareeventsoccur.
VMware, Inc.
115
116
VMware, Inc.
VMware, Inc.
117
ASCSIadapter,FibreChanneladapter,orinternalRAIDcontroller: BasicSCSIcontrollersareAdaptecUltra160andUltra320,LSILogic FusionMPT,andmostNCR/SymbiosSCSIcontrollers. FibreChannel.SeetheStorage/SANCompatibilityGuide. RAIDadapterssupportedareHPSmartArray,DellPercRAID(Adaptec RAIDandLSIMegaRAID),andIBM(Adaptec)ServeRAIDcontrollers. ASCSIdisk,FibreChannelLUN,orRAIDLUNwithunpartitionedspace.This diskorRAIDisusedforthevirtualmachines. ForhardwareiSCSI,adiskattachedtoaniSCSIcontroller,suchastheQLogic qla405x. ForSATA,adiskconnectedthroughsupporteddualSASSATAcontrollersthatare usingSASdrivers. ESX Serversupportsthefollowingstoragesystems: ATAdiskdrivesStorageofvirtualmachinesiscurrentlynotsupportedonATA drivesorRAIDs.VirtualmachinesmustbestoredonVMFSvolumesconfigured onaSCSIorSATAdrive,aSCSIRAID,oraSAN. SerialATA(SATA)diskdrivesSharingVMFSdatastoresonSATAdisksacross multipleESX Serverhostsisnotsupported. SCSIdiskdrivesSCSIdiskdrivescanstorevirtualmachinesonVMFS partitions. Storageareanetworks(SANs)SANs,bothFibreChannelandiSCSI,are supportedforstoringvirtualmachinesonVMFSdatastores. NOTETheminimumsupportedLUNcapacityforVMFS3is1200MB.
118
VMware, Inc.
VMware, Inc.
119
120
VMware, Inc.
Index
Numerics
27000, port 79 27010, port 79
Consolidated Backup, licensing 53, 59 corrupted software, restoring 41 CPU processors, health 115
A
access, restricting 32 activation code, license 75 administrative password 32 applying patches 111 ATA disks 118 automatic updates 107
D
databases Oracle 94 preparing 93 SQL Server 96 deactivating ESX Server 3i 42 default storage behavior 29 DHCP 25 DHCP, direct console 26, 27 direct console 19, 37 alternatives 34 boot setting 23 configuring the keyboard 21 DHCP 26, 27 DNS 27 DNS suffixes 28 IP addressing 26, 28 management network 25 navigating 21 network adapters 25 network settings 25 NICs 25 password configuration 32 security banner 22 static addressing 26, 27, 28 testing management network 28 VLAN ID 25 DNS suffixes, direct console 28
B
backing up a configuration 38, 39 virtual machines 53, 59 banner, security 22 BIOS 23 boot setting 23 build numbers 114
C
CD-ROM, booting from virtual 24 centralized licensing configuring 76 description 56 clients, firewall 103 configuration backup and restore 38, 39, 40 configuration defaults, resetting 33 configuring the keyboard 21 configuring, ports 103 connectivity 35
VMware, Inc.
121
E
editions 59 ESX Server 3i backing up and restoring the configuration 38 deactivating 42 editions 59 restoring the firmware 41 update, rolling back 114 ESX Server hardware considerations 117 evaluation licenses 86
Oracle database 94 updates 109, 110 VI Client 34 VirtualCenter Server 34, 103 IP 25 IP addressing, direct console 26, 27, 28 iSCSI licensing 53
K
keyboard, localizing 21
L
LAC 52 license activation code 52, 75 license files installing 75 locations of 85 obtaining 75 license keys 56 license pool 56 license server availability 60 grace period 60 install 87 license types ESX Server 52 VirtualCenter Server 54 licenses, evaluation 86 licensing centralized 56 single-host 56 listening ports 103 local Oracle database 94 localizing, keyboard 21 lockdown mode 32
F
factory defaults, restoring 33 fan RPMs 115 file partitions, restoring 41 firewall 103 floppy, booting from virtual 24
G
grace period, license server 60 guest operating systems 49
H
HA, by edition 53 health monitoring 115 hosts firewall 103 hosts, updates 109
I
IDE disks 118 installing license server 87 on SANs 118
122
VMware, Inc.
Index
M
management agent, restarting 35 management network direct console 25 testing 28 manual updates 110 message, security 22 Microsoft Access database end of support life 47 monitoring, health 115 MSDE, preparing database 98
R
RCLI 38, 111 recovery CD 41 reimaging the USB flash 41 reinstalling VirtualCenter 105 remote access, restricting 32 management clients 34, 45 Oracle database 94 Remote CLI 38, 111 removable media, updates 110 removing VirtualCenter 105 resetting configuration defaults 33 restarting management agent 35 restoring a configuration 38, 40 ESX Server 3i firmware 41 factory defaults 33 restricting access 32 rolling back an ESX Server 3i update 114 root access, restricting 32 RPMs, fans 115
N
NAS, licensing 53 navigating, direct console 21 network settings, direct console 25 NICs, direct console 25 notifications for updates, disabling 110
O
ODBC databases 96 operating systems, guest 49 Oracle, preparing database 94
P
PAC 52 partitions 29 partner activation code 52 partner activation portal 52 password, administrative 32 patching 111 ports 27000 79 27010 79 configuring 103 firewall 103 license server 79 processor health 115
S
SATA disks 118 scheduling, updates 108 scratch storage 29 SCSI 118 SCSI disks 118 SDK 15 security banner 22 serial number 31, 80 single-host licensing configuring 80 description 56 SMP, licensing 53
VMware, Inc.
123
specifications ESX Server hardware considerations 117 performance recommendations 119 SQL Server, preparing database 96 static addressing about 25 direct console 26, 28 static DNS, direct console 27 storage 29 support information 31 support, guest operating system 49 system requirements license server 48 updates 108 VirtualCenter database 47 system swap 29
V
VCB 53, 59 VI Client connectivity 35 installing 34 vihostupdate 111 bundle option 113 examples 113 install option 113 metadata option 113 query option 113 scan option 113 vihost option 111 virtual appliance, RCLI 38 virtual machines adapters for 119 backing up 59 disk location and size 119 high availability 59 installing VirtualCenter on 106 migrating 44 powering on 60 RAM requirements 119 resource management 59 small deployments 47, 93 specifications 49 storage of 118 upgrading tools 44 virtual media 24 VirtualCenter connectivity 35 installing 34 VLAN ID, direct console 25 VMFS 29 VMotion, licensing 59
T
TCP/IP ports 27000 79 27010 79 temperature 115 testing management network direct console 28 troubleshooting 33, 35
U
uninstalling VirtualCenter 105 updates automatic 107 disabling notifications 110 installing 109, 110 manual 107, 110 removable media 110 scheduling 108 selecting hosts 109 system requirements 108
124
VMware, Inc.
Index
VMware Consolidated Backup 53, 59 DRS, licensing 59 HA, licensing 59 Infrastructure Update 107
VMware, Inc.
125
126
VMware, Inc.
LastUpdated:June12,2009 ThisdocumentprovidesupdatestotheESXServer3iversion3.5Embeddedand VirtualCenter2.5versionoftheESXServer3iEmbeddedSetupGuide.Updated descriptions,procedures,andgraphicsareorganizedbypagenumbersothatyoucan easilylocatetheareasoftheguidethathavechanges.Ifthechangespansmultiple sequentialpages,thisdocumentprovidesthestartingpagenumberonly. ThefollowingisalistofupdatestotheESXServer3iEmbeddedSetupGuide: UpdatesfortheTableofSupportedDatabaseFormatsonPage 47 UpdatesfortheToprepareaSQLServerdatabasetoworkwithVirtualCenter ProcedureonPage 96 UpdatesfortheConfiguringCommunicationBetweenVirtualCenterComponents SectiononPage 103
VMware, Inc.
Update1
Note:VMwaresupports10.2.0.3.0andlater versionsofOracleDatabase10gRelease2.
Updates for the To prepare a SQL Server database to work with VirtualCenter Procedure on Page 96
ThefollowingtextshouldappearinToprepareaSQLServerdatabasetoworkwith VirtualCenter: Makesurethatthedatabaseuserhasthefollowingpermissions: MicrosoftSQLServer2000Makesurethatthedatabaseuserhasthedb_owner fixeddatabaseroleontheVirtualCenterdatabaseandtheMSDBdatabase.The db_ownerroleontheMSDBdatabaseisrequiredforinstallationandupgradeonly. Youcanrevokethisroleaftertheinstallationorupgradeprocessiscompleted. Do notgranttheSystemAdministratorsserverroletothedatabaseuser.However, iftheSystemAdministratorsrolewaspreviouslygrantedwhilethedatabasewas usedwithVirtualCenterServer2.0.x,donotrevoketheSystemAdministrators role.Leaveitasis. MicrosoftSQLServer2005Makesurethatthedatabaseloginhaseitherthe sysadminserverroleorthedb_ownerfixeddatabaseroleontheVirtualCenter databaseandontheMSDBdatabase.Thedb_ownerroleontheMSDBdatabaseis requiredforinstallationandupgradeonly.Youcanrevokethisroleafterthe installationorupgradeprocessiscomplete.
Updates for the Configuring Communication Between VirtualCenter Components Section on Page 103
ThefollowingtextshouldappearintheConfiguringCommunicationBetween VirtualCenterComponentssection: Port443isrequiredforcommunicationfromVirtualCentertoESXServerhosts.
Update2
VMware, Inc.