vSphere Installation and Setup - Documentation - VMware

More documents

Recommendations

Info

vSphere Installation and Setup n ESXi supports a broad range of x64 multicore processors. For a complete list of supported processors, see the VMware compatibility guide at http://www.vmware.com/resources/compatibility. n ESXi requires a minimum of 2GB of physical RAM. Provide at least 8GB of RAM to take full advantage of ESXi features and run virtual machines in typical production environments. n To support 64-bit virtual machines, support for hardware virtualization (Intel VT-x or AMD RVI) must be enabled on x64 CPUs. n One or more Gigabit or 10Gb Ethernet controllers. For a list of supported network adapter models, see the VMware Compatibility Guide at http://www.vmware.com/resources/compatibility. n Any combination of one or more of the following controllers: n Basic SCSI controllers. Adaptec Ultra-160 or Ultra-320, LSI Logic Fusion-MPT, or most NCR/Symbios SCSI. n RAID controllers. Dell PERC (Adaptec RAID or LSI MegaRAID), HP Smart Array RAID, or IBM (Adaptec) ServeRAID controllers. n SCSI disk or a local, non-network, RAID LUN with unpartitioned space for the virtual machines. n For Serial ATA (SATA), a disk connected through supported SAS controllers or supported on-board SATA controllers. SATA disks will be considered remote, not local. These disks will not be used as a scratch partition by default because they are seen as remote. NOTE You cannot connect a SATA CD-ROM device to a virtual machine on an ESXi 5.1 host. To use the SATA CD-ROM device, you must use IDE emulation mode. Storage Systems ESXi 5.1 supports installing on and booting from the following storage systems: n SATA disk drives. SATA disk drives connected behind supported SAS controllers or supported on-board SATA controllers. Supported SAS controllers include: n LSI1068E (LSISAS3442E) n LSI1068 (SAS 5) n IBM ServeRAID 8K SAS controller n Smart Array P400/256 controller n Dell PERC 5.0.1 controller Supported on-board SATA include: n Intel ICH9 n NVIDIA MCP55 n ServerWorks HT1000 NOTE ESXi does not support using local, internal SATA drives on the host server to create VMFS datastores that are shared across multiple ESXi hosts. n Serial Attached SCSI (SAS) disk drives. Supported for installing ESXi 5.1 and for storing virtual machines on VMFS partitions. n Dedicated SAN disk on Fibre Channel or iSCSI n USB devices. Supported for installing ESXi 5.1. 28 VMware, Inc.
n Software Fibre Channel over Ethernet (FCoE). See “Installing and Booting ESXi with Software FCoE,” on page 25. ESXi Booting Requirements vSphere 5.1 supports booting ESXi hosts from the Unified Extensible Firmware Interface (UEFI). With UEFI you can boot systems from hard drives, CD-ROM drives, or USB media. Network booting or provisioning with VMware Auto Deploy requires the legacy BIOS firmware and is not available with UEFI. ESXi can boot from a disk larger than 2TB provided that the system firmware and the firmware on any addin card that you are using support it. See the vendor documentation. NOTE Changing the boot type from legacy BIOS to UEFI after you install ESXi 5.1 might cause the host to fail to boot. In this case, the host displays an error message similar to: Not a VMware boot bank. Changing the host boot type between legacy BIOS and UEFI is not supported after you install ESXi 5.1. Storage Requirements for ESXi 5.1 Installation Installing ESXi 5.1 requires a boot device that is a minimum of 1GB in size. When booting from a local disk or SAN/iSCSI LUN, a 5.2GB disk is required to allow for the creation of the VMFS volume and a 4GB scratch partition on the boot device. If a smaller disk or LUN is used, the installer will attempt to allocate a scratch region on a separate local disk. If a local disk cannot be found the scratch partition, /scratch, will be located on the ESXi host ramdisk, linked to /tmp/scratch. You can reconfigure /scratch to use a separate disk or LUN. For best performance and memory optimization, VMware recommends that you do not leave /scratch on the ESXi host ramdisk. To reconfigure /scratch, see “Set the Scratch Partition from the vSphere Client,” on page 179. Due to the I/O sensitivity of USB and SD devices the installer does not create a scratch partition on these devices. As such, there is no tangible benefit to using large USB/SD devices as ESXi uses only the first 1GB. When installing on USB or SD devices, the installer attempts to allocate a scratch region on an available local disk or datastore. If no local disk or datastore is found, /scratch is placed on the ramdisk. You should reconfigure /scratch to use a persistent datastore following the installation. In Auto Deploy installations, the installer attempts to allocate a scratch region on an available local disk or datastore. If no local disk or datastore is found /scratch is placed on ramdisk. You should reconfigure /scratch to use a persistent datastore following the installation. For environments that boot from a SAN or use Auto Deploy, it is not necessary to allocate a separate LUN for each ESXi host. You can co-locate the scratch regions for many ESXi hosts onto a single LUN. The number of hosts assigned to any single LUN should be weighed against the LUN size and the I/O behavior of the virtual machines. Recommendation for Enhanced ESXi Performance To enhance performance, install ESXi on a robust system with more RAM than the minimum required and with multiple physical disks. For ESXi system requirements, see “ESXi Hardware Requirements,” on page 27. Chapter 2 System Requirements VMware, Inc. 29
Page 1 and 2: vSphere Installation and Setup vSph
Page 3 and 4: Contents About vSphere Installation
Page 5 and 6: Configure Microsoft SQL Server Data
Page 7 and 8: About vSphere Installation and Setu
Page 9 and 10: Introduction to vSphere Installatio
Page 11 and 12: vSphere Web Client The vSphere Web
Page 13 and 14: Figure 1-1. Scripted Installation s
Page 15 and 16: n Boot from a remote location using
Page 17 and 18: Prerequisites n Linux machine n ESX
Page 19 and 20: You can also acquire a TFTP server
Page 21 and 22: } next-server xxx.xxx.xx.xx; filena
Page 23 and 24: 8 Save the PXE configuration file i
Page 25 and 26: 2 Modify the boot.cfg file with the
Page 27: System Requirements 2 Systems runni
Page 31 and 32: n For Intel Xeon-based systems, the
Page 33 and 34: Table 2-5. JVM Heap Settings for vC
Page 35 and 36: Processing requirements are listed
Page 37 and 38: Table 2-13. Recommended Minimum Siz
Page 39 and 40: Table 2-15. Ports Required for the
Page 41 and 42: Supported Remote Management Server
Page 43 and 44: Installing ESXi Interactively 3 Use
Page 45 and 46: What to do next Set up basic admini
Page 47 and 48: Installing, Upgrading, or Migrating
Page 49 and 50: Boot Options When you perform a scr
Page 51 and 52: Path to the Installation or Upgrade
Page 53 and 54: installorupgrade Either the install
Page 55 and 56: serialnum or vmserialnum (optional)
Page 57 and 58: --firstdisk= disk-type1, [disk-type
Page 59 and 60: install, installorupgrade, upgrade
Page 61 and 62: 2 When the ESXi installer window ap
Page 63 and 64: Installing ESXi Using vSphere Auto
Page 65 and 66: Figure 5-1. vSphere Auto Deploy Arc
Page 67 and 68: 4 Activate the rules in the working
Page 69 and 70: 3 Virtual machines are brought up o
Page 71 and 72: To successfully provision the hosts
Page 73 and 74: Table 5-2. Rule Engine PowerCLI Cmd
Page 75 and 76: n Secure your network as you would
Page 77 and 78: Install PowerCLI and Prerequisite S
Page 79 and 80:
Assigning license keys through the
Page 81 and 82:
6 Add the rule to the rule set. Add
Page 83 and 84:
Procedure 1 Run the Connect-VIServe
Page 85 and 86:
2 (Optional) If Auto Deploy applies
Page 87 and 88:
When you reboot hosts after complia
Page 89 and 90:
Table 5-3. Preparation for Stateles
Page 91 and 92:
2 You write a rule that provisions
Page 93 and 94:
6 In the System Image Cache Profile
Page 95 and 96:
Setting Up an Auto Deploy Reference
Page 97 and 98:
Configure ESXi Dump Collector with
Page 99 and 100:
3 For a new profile, click Create P
Page 101 and 102:
3 Customize your reference host by
Page 103 and 104:
n For hosts already provisioned wit
Page 105 and 106:
Prerequisites Set up your Auto Depl
Page 107 and 108:
Set Up the vCenter Server Appliance
Page 109 and 110:
Table 5-8. Host Profile Options tha
Page 111 and 112:
Table 5-10. Host Profile Options th
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
vSphere Auto Deploy Logging and Tro
Page 119 and 120:
Figure 5-5. Highly Available Auto D
Page 121 and 122:
Solution u Correct the IP address o
Page 123 and 124:
Solution 1 Reboot the host and foll
Page 125 and 126:
Recovering from Database Corruption
Page 127 and 128:
n Administrator rights to the targe
Page 129 and 130:
4 Confirm that PowerCLI is working.
Page 131 and 132:
d Click 066 Boot Server Host Name a
Page 133 and 134:
n Configure the Auto Deploy and TFT
Page 135 and 136:
The steps in this task instruct you
Page 137 and 138:
What to do next Boot the host and c
Page 139 and 140:
In this example, you create a host
Page 141 and 142:
3 (Optional) To display the rules i
Page 143 and 144:
Using vSphere ESXi Image Builder CL
Page 145 and 146:
See “SoftwarePackage Object Prope
Page 147 and 148:
n Performs VIB signature validation
Page 149 and 150:
Name Type Description MaintenanceMo
Page 151 and 152:
Name Type Description Name System.S
Page 153 and 154:
Image Builder Common Tasks The Imag
Page 155 and 156:
5 (Optional) Change the acceptance
Page 157 and 158:
Working with Acceptance Levels Host
Page 159 and 160:
Set the Image Profile Acceptance Le
Page 161 and 162:
Get-EsxSoftwarePackage -Vendor "V*"
Page 163 and 164:
4 Pipe the information about the ne
Page 165 and 166:
Setting Up ESXi 7 These topics prov
Page 167 and 168:
Create a Security Banner for the Di
Page 169 and 170:
6 Make sure that the VMkernel.Boot.
Page 171 and 172:
Procedure 1 Connect the media to th
Page 173 and 174:
Configuring Network Settings ESXi r
Page 175 and 176:
7 Select Use static IPv4 settings.
Page 177 and 178:
2 Press F11 to confirm. Restoring t
Page 179 and 180:
About the Scratch Partition For new
Page 181 and 182:
Configure Syslog on ESXi Hosts All
Page 183 and 184:
2 Click the Manage tab and click Se
Page 185 and 186:
3 Press F11 to confirm. The system
Page 187 and 188:
After You Install and Set Up ESXi 8
Page 189 and 190:
Access the ESXi License Key from th
Page 191 and 192:
Preparing vCenter Server Databases
Page 193 and 194:
2 Use the application to create a s
Page 195 and 196:
9 (Optional) Configure an IBM DB2 D
Page 197 and 198:
2 To configure the vSphere Client t
Page 199 and 200:
2 In the directory of the vCenter S
Page 201 and 202:
What to do next Optionally, you can
Page 203 and 204:
6 (Optional) Use a Script to Create
Page 205 and 206:
15 Revoke the VC_ADMIN_ROLE from th
Page 207 and 208:
if not exists (SELECT name FROM sys
Page 209 and 210:
l_purge_stat3_proc_mssql.sql l_stat
Page 211 and 212:
2 Click the System DSN tab and do o
Page 213 and 214:
5 Configure an Oracle Database Conn
Page 215 and 216:
(Optional) Use a Script to Create t
Page 217 and 218:
Configure an Oracle Database Connec
Page 219 and 220:
Enable Database Monitoring for a us
Page 221 and 222:
Before You Install vCenter Server 1
Page 223 and 224:
n Before the vCenter Server install
Page 225 and 226:
Alternatively, to customize the loc
Page 227 and 228:
For example, consider a corporation
Page 229 and 230:
Users can log in to vCenter Server
Page 231 and 232:
Login Behavior When You Install a C
Page 233 and 234:
The vCenter Server Appliance clock
Page 235 and 236:
JDBC URL Format for Single Sign-On
Page 237 and 238:
4 For the VirtualCenter.VimApiUrl k
Page 239 and 240:
Table 10-1. Information Required fo
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Installing vCenter Server 11 After
Page 247 and 248:
2 Extract the files from the zip ar
Page 249 and 250:
vCenter Single Sign-On is installed
Page 251 and 252:
What to do next After you install v
Page 253 and 254:
n Review “vCenter Single Sign-On
Page 255 and 256:
3 Install or Upgrade an Additional
Page 257 and 258:
11 If you are using the bundled Mic
Page 259 and 260:
Update the HTTPD Configuration with
Page 261 and 262:
4 Create a properties file for each
Page 263 and 264:
n See “Prerequisites for Installi
Page 265 and 266:
5 Select Multisite. 6 Enter the inf
Page 267 and 268:
n If you are upgrading the vSphere
Page 269 and 270:
6 Enter the fully qualified domain
Page 271 and 272:
3 Import the Single Sign-On data to
Page 273 and 274:
11 Select the size of your vCenter
Page 275 and 276:
n Verify that the database that vCe
Page 277 and 278:
Microsoft SQL Server and IBM DB2 ar
Page 279 and 280:
4 Add the MD5 hash to the vCenter S
Page 281 and 282:
VC_DB_INSTANCE=orcl VC_DB_USER=VCA-
Page 283 and 284:
After You Install vCenter Server 12
Page 285 and 286:
Procedure 1 Run the vSphere Client
Page 287 and 288:
7 Start the vSphere Web Client by d
Page 289 and 290:
Install the Update Manager Server T
Page 291 and 292:
For instructions on configuring ESX
Page 293 and 294:
Install or Upgrade vSphere Auto Dep
Page 295 and 296:
When you install the vSphere Authen
Page 297 and 298:
4 Verify that the DNS of the new ho
Page 299 and 300:
The following requirements apply to
Page 301 and 302:
The vCenter Server instance is now
Page 303 and 304:
The DNS name of the machine must ma
Page 305 and 306:
Table 12-3. vCenter Server Port and
Page 307 and 308:
Prerequisites n Consult your databa
Page 309 and 310:
8 Run the register-is.bat command t
Page 311 and 312:
Index Symbols %include command 51 %
Page 313 and 314:
direct console boot setting 170 con
Page 315 and 316:
ks.cfg 50 L LDAP 300 license key 18
Page 317 and 318:
Single Sign On, back up 295 Single
Page 319 and 320:
VLAN ID, direct console 173 VLANs,
show all

vSphere Installation and Setup - Documentation - VMware

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?