Difference between revisions of "Installation (ESX)"

Jump to navigation Jump to search
1,069 bytes added ,  08:47, 28 October 2010
(→‎High Availability: Added "Error Hints")
Line 133: Line 133:


= Configuration Considerations =
= Configuration Considerations =
== Hardware ==
=== HP ASR ===
Should be disabled.
VMware don’t recommend that we use the HP ASR feature (designed to restart a server in the case of an OS hang), they’ve come across occasions when an ESX under load will suddenly restart due to ASR time-outs.  See [http://kb.vmware.com/kb/1010842 VM KB 1010842 - HP Automatic Server Recovery in a VMware ESX Environment] for further info.
=== CPU Power / Performance ===
If in doubt put server BIOS settings to maximum performance - this ensures that ESX can get the most out of the hardware, allowing the BIOS to balance or use low power modes may impact VM performance.
If using ESX4.1 or higher then set the BIOS to allow OS control of CPU performance (if the setting is available), this allows the CPU Performance to be controlled dynamically by ESX (and configurable through the VI Client)
See [http://kb.vmware.com/kb/1018206 VM KB 1018206 - Poor virtual machine application performance may be caused by processor power management settings] for further info
== Networking ==
== Networking ==
=== Beacon Probing ===
=== Beacon Probing ===
Should only be used when there are 3 or more physical NIC's assigned to the vSwitch, uplinked to the network switch.  This is to enable the ESX to be able to properly determine the state of the network during a faulty condition.  If there's only two uplinks and the beacon gets lost between the two NIC's, then the ESX can't know which uplink is faulty, just that there is a fault.   
Should only be used when there are 3 or more physical NIC's assigned to the vSwitch, uplinked to the network switch.   
 
This is to enable the ESX to be able to properly determine the state of the network during a faulty condition.  If there's only two uplinks and the beacon gets lost between the two NIC's, then the ESX can't know which uplink is faulty, just that there is a fault.   


See http://kb.vmware.com/kb/1005577 for further info.
See [http://kb.vmware.com/kb/1005577 VM KB 1005577 - What is beacon probing?] for further info.


== Storage ==
== Storage ==
=== ESX Installation Sizing ===
=== ESX Installation Sizing ===
See [http://kb.vmware.com/kb/1026500 VM KB 1026500 Recommended disk or LUN sizes for VMware ESX/ESXi installations]
See [http://kb.vmware.com/kb/1026500 VM KB 1026500 - Recommended disk or LUN sizes for VMware ESX/ESXi installations]


=== SCSI Resets ===
=== SCSI Resets ===

Navigation menu