2,187
edits
m (Added "Banners") |
m (→Build Numbers: Added v5.1 build) |
||
(83 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{ | == Build Notes == | ||
* '''[[ESX3 Installation]]''' - Example, based on an old ESX v3 build guide | |||
* '''[[ESX4i Installation]]''' - Example, bit brief in places | |||
* [http://www.jam-software.com/heavyload/download.shtml HeavyLoad] - Load tester (stick it in a test VM, memory test doesn't really work as ESX page sharing kicks in) | |||
== Build Numbers == | |||
ESX build numbers, note that installing subsequent patches, on top of one of the major releases below will increase the build number. | |||
{|class="vwikitable" | |||
|- | |||
! ESX version !! ESX !! ESXi | |||
|- | |||
| 3.5 Update 1 || 82663 || 82664 | |||
|- | |||
| 3.5 Update 2 || 110268 || 110271 | |||
|- | |||
| 3.5 Update 3 || 123630 || 123629 | |||
|- | |||
| 3.5 Update 4 ||colspan="2"| 153875 | |||
|- | |||
| 3.5 Update 5 ||colspan="2"| 207095 | |||
|- | |||
| 4.0 ||colspan="2"| 164009 | |||
|- | |||
| 4.0 Update 1 ||colspan="2"| 208167 | |||
|- | |||
| 4.0 Update 2 ||colspan="2"| 261974 | |||
|- | |||
| 4.0 Update 3 ||colspan="2"| 398348 | |||
|- | |||
| 4.0 Update 4 ||colspan="2"| 504850 | |||
|- | |||
| 4.1 ||colspan="2"| 260247 | |||
|- | |||
| 4.1 Update 1 ||colspan="2"| 348481 | |||
|- | |||
| 4.1 Update 2 ||colspan="2"| 502767 | |||
|- | |||
| 4.1 Update 3 ||colspan="2"| 800380 | |||
|- | |||
| 5.0 ||colspan="2"| 469512 | |||
|- | |||
| 5.0 Update 1 ||colspan="2"| 623860 | |||
|- | |||
| 5.1 ||colspan="2"| 799733 | |||
|} | |||
== USB Image == | |||
If you're installing ESXi 4 then you don't need to do this, the installer will detect the USB stick and install to it. | |||
'''Required software etc...''' | |||
* '''''WinImage''''' - http://www.winimage.com/download.htm | |||
* '''''DD''''' - http://www.chrysocome.net/dd | |||
* '''''ESXi install ISO''''' | |||
* '''''Disk Cloner''''', eg G4U - http://www.feyrer.de/g4u/ | |||
** Ideally use a cloner that ignores the actual disk contents and does a block by block copy, anything that tries to interpret the disk image may not copy it faithfully | |||
* You must be able to connect '''two''' image files remotely to your server, a disk cloner ''CD'' ISO, and the image ''USB'' ISO (hint: use the floppy drive). | |||
'''Creating the USB image file''' | |||
# Open up the ISO with WinImage | |||
# Extract the <code> INSTALL.TGZ </code> from the ISO | |||
# Uncompress <code> INSTALL.TGZ </code> and locate <code> .\INSTALL\usr\lib\vmware\installer\VMware-VMvisor-big-3.5.0_Update_4-153875.i386.dd.bz2 </code> | |||
# Uncompress <code> VMware-VMvisor-big-3.5.0_Update_4-153875.i386.dd.bz2 </code> so that you have <code> VMware-VMvisor-big-3.5.0_Update_4-153875.i386.dd </code> | |||
# Create ISO image from DD image by using DD | |||
#* <code> dd bs=1M if=VMware-VMvisor-big-3.5.0_Update_4-153875.i386.dd of=esx3.5ihp-usbimage.iso </code> | |||
'''Deploying the USB image file''' | |||
# Attach your disk cloner image to your server and boot | |||
# Once the the server is booting to the CD ISO, attach the USB ISO | |||
# List the avaialble disks | |||
#* <code> list </code> | |||
# Identify the image disk (which is 750MB) and the USB disk (which will be whatever size your USB key is) | |||
# Copy the image to the USB key | |||
#* <code> copydisk sd1 sd0 </code> | |||
# Disconnect all images, reboot server, cross fingers | |||
#* <code> reboot </code> | |||
== VMware CLI == | |||
Especially if using ESX'''i''', you'll need to install the VMware CLI on any machine you want to access the ESX command line from. Be aware that [http://www.activestate.com/activeperl/ ActivePerl] gets installed as well, so proceed with caution if you've already got Perl installed on the machine. | |||
== Security Hardening == | == Security Hardening == | ||
=== Service Console === | === Service Console === | ||
Applicable to ESX only (not ESXi, as ESXi doesn't have a service console) | |||
==== Disk Partitions ==== | ==== Disk Partitions ==== | ||
Suggesting partition sizing for Service Console on local disk to prevent Root partition being filled with user data | Suggesting partition sizing for Service Console on local disk to prevent Root partition being filled with user data | ||
Line 86: | Line 163: | ||
Prepend your banner to the <code>/etc/issue</code> file | Prepend your banner to the <code>/etc/issue</code> file | ||
= | === ESX === | ||
== | ==== Network Settings ==== | ||
{|class="vwikitable" | |||
{| | |||
|- | |- | ||
! Setting !! Default !! Preferred !! Explanantion | |||
|- | |- | ||
| | | '''Promiscuous Mode''' || Reject || Reject | ||
|| Principally used in situations where you need to perform a network traffic (snif) capture. Data from all ports propagates to all ports (VM Port group becomes a hub rather than a switch) | |||
|- | |- | ||
| | | '''MAC address changes''' || Accept || Reject | ||
|| There are situations where allowing MAC Address Changes to Accept is required. For example; legacy applications, clustered environments, and licensing. Legacy applications may require a specific MAC addresses to be used for the application. Microsoft Clusters utilize an artificial MAC address for all servers in the cluster | |||
|- | |- | ||
| | | '''Forged Transmits''' || Accept || Reject | ||
|| The setting affects traffic transmitted from a virtual machine. If this option is set to reject, the virtual switch compares the source MAC address being transmitted by the operating system with the effective MAC address for its virtual network adapter to see if they are the same. If the MAC addresses are different, the virtual switch drops the frame. The guest operating system will not detect that its virtual network adapter cannot send packets using the different MAC address. To protect against MAC address impersonation, all virtual switches should have forged transmissions set to reject | |||
|} | |} | ||
[[Category: | [[Category:ESX]] |