HP BladeSystem – EFUSE

HP BladeSystem – EFUSE

The term e-Fuse, e-fuse, Efuse or EFUSE is used when a Blade system has to be reset virtually (without physically reseating the server).

An e-fuse reset causes the server blade to lose power momentarily as the e-fuse is tripped and reset.
Details
CAUTION: Use this command with caution. This will result in any activity on the server operating system being lost.
To perform an e-fuse reset:

  1. Telnet to OA IP Address
  2. Login to Onboard Administrator with Administrator privileges using the OA CLI.
  3. Enter the command RESET SERVER X where [X = bay number].
  4. Confirm that the user wants to reset the server blade.
This will reset/restart the Blade Server in that particular bay.

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=120&prodSeriesId=3188465&prodTypeId=329290&objectID=c03101166

Don’t be Scared 🙂

Command Prompt - MetaFrame Presentation Server Client_2014-02-20_14-40-24

Installing Intel NIC Drivers on VMware ESXi for System x3650 M3

Installing Intel NIC Drivers on VMware ESXi for System x3650 M3

 

This procedure describes, how to setup base Networking configuration for ESXi 4.1 on IBM System X 3650 M3 Servers:

 This is a high level overview and reference only. This is not a step-by-step guide. You will need to have 3rd experience in VMWare to use this guide. This should be used with ESXi build guides and Detailed design.

Installing Intel NIC Drivers on VMware ESXi for System x3650 M3:-

Known Issue:-

 After installing VMware ESXi 4X on IBM System X 3650 M3 Servers, ESXi does not see Intel Quad-Port or Dual-Port NIC – Intel Ethernet Dual-Port or Quad-Port Server Adapter: – http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=migr-5089106 (Intel Ethernet Dual Port Server Adapter I340-T2 for IBM System x (49Y4230)  See below screenshot:

  • Download the IBM customised ESXi (.iso)

http://www14.software.ibm.com/webapp/download/preconfig.jsp?id=2011-12-14+09%3A23%3A53.641127R&S_TACT=104CBW&S_CMP=

  • Download the appropriate driver (.iso) from VMware.com only (unless otherwise indicated):-

http://downloads.vmware.com/d/info/datacenter_downloads/vmware_vsphere_hypervisor_esxi/4_0#drivers_tools

http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5085368

  • Download the latest ESX update: – http://www.vmware.com/patchmgr/download.portal
  • Use existing ESXi Base Build Guides and install ESXi.
  • Enable Local Tech support mode in ESXi and use ALT-F1 and ALT-F2 to Enter and Exit local console:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1017910

  • Insert NIC Driver CD or Mount NIC Driver ISO via Remote RSA/IMM (iLo/DRAC)
  • Issue the following command to ensure CD-ROM is detected:

[sourcecode]

–       ls –lash /dev/cdrom

–       esxcfg-mpath -l

–       esxcfg-mpath -b | grep "CD-ROM"

–       (You should see an mpx.vmhbaXX:C0:T0:L0-type filename (note the vmhba#) & a vml.-type filename)

[/sourcecode]

  • If CD-ROM is detected, issue the following commands to load the iso9960 module and mount the CD-ROM:

[sourcecode]

–       vmkload_mod iso9660

–       vim-cmd hostsvc/maintenance_mode_enter

–       vsish -e set /vmkModules/iso9660/mount mpx.vmhba<b>33</b>:C0:T0:L0

–       vim-cmd hostsvc/maintenance_mode_exit

–       vim-cmd hostsvc/hostsummary|grep -i maintenance

–       (Note: the number in RED may differ but is taken from the /dev/cdrom directory listing from the previous command.)

[/sourcecode]

  • The CD-ROM should be mounted and available here:

[sourcecode]-       ls –lash /vmfs/volumes/CDROM[/sourcecode]

  • Change to the offline bundle (.zip file) directory

[sourcecode]-       cd /vmfs/volumes/CDROM/OFFLINE_ (or something similar)[/sourcecode]

  • Place the host into Maintenance Mode:

[sourcecode]-       vim-cmd hostsvc/maintenance_mode_enter[/sourcecode]

  • Execute bundle/update:

[sourcecode]-       esxupdate –bundle NameOfBundle.zip update[/sourcecode]

  • Issue the following command to unmount the CD-ROM:

[sourcecode]-       vsish -e set /vmkModules/iso9660/umount mpx.vmhba33:C0:T0:L0[/sourcecode]

  • Issue the following command to fix incompatibility with ESXi 4.1 and IBM x3650 M3

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1030265

http://www.sysadmintutorials.com/vmware-esx-and-esxi-4-1-incompatibility-with-ibm-x3650-m3-server/

[sourcecode]

–       esxcfg-advcfg -k TRUE iovDisableIR

–       esxcfg-info –c

[/sourcecode]

  • Reboot the ESXi Server
  • Verify the NICs are visible to ESXi and document the wiring information to the switch ports:

[sourcecode]

–       cat /etc/vmware/esx.conf | grep “net”

–       esxcfg-nics –l

–       ethtool –i vmnic0

–       esxcfg-vswitch –l

–       ethtool –p vmnic0 10 (Start Blinking NIC LEDs for 10 seconds)

–       vm-support

–       Check /bootbank/oem/oem.tx

–       esxcli network nic up/down –n vmnicX

[/sourcecode]

  • Configure IP addresses for the Management NIC and select the correct NICs:
  • LACP Configuration notes:

As the switch ports will already be configured to LACP or Etherchannel with Load Balancing configurations. Example: IP Hash.

It is not possible to configure all required details for LACP via the command line or ESXi console GUI.

You will need to configure a management IP address on the Management NIC first and then connect to this IP via vSphere Client GUI to complete LACP and Etherchannel settings.

You can also configure an IP address on one of the NICs configured for LACP and VLAN. (Don’t select all LACP NICs, only a single NIC)

Then connect to this IP via vSphere Client GUI to complete the Networking configuration as per Build and Detailed Design.

  • Document the Physical Port wiring:

IBM DSA on VMware ESXi

[sourcecode]
Open Port 5989
ibm_utl_dsa_dsyt85t-3.40_portable_windows_x86-64.exe -vmwesxi user:[email protected] -v -c -d c:\temp\dsa
-f -v -f –ffdc
[/sourcecode]

  • VMware Portabl command:

[sourcecode]
transfer the file via CP / ssh or WinSCP  or USB to /tmp
cp /mnt/key/ibm_utl_dsa_212p_rhel3_i386.bin /tmp
chmod +x ibm_utl_dsa_212p_rhel3_i386.bin
./ibm_utl_dsa_212p_rhel3_i386.bin
/var/log/IBM_SUPPORT
[/sourcecode]

VMWare vDR Backup HTML Report

VMWare vDR Backup HTML Report

SCRIPT:

[source language=”bash”]
#!/bin/bash
#Parse file
err=$(strings -e l /var/vmware/datarecovery/operations_log.utx | grep -i -B2 "error" | awk -F"$" ‘{print substr($2,5,21) " " substr($2, 27, 100) " " $3 " " substr($6,17,20)}’ | grep c)
succ=$(strings -e l /var/vmware/datarecovery/operations_log.utx | grep -i -B1 "success" | awk -F"$" ‘{print substr($2,5,21) " " substr($2, 26, 100) " " substr($3,5,100)}’ | grep c)
#Test String – strings -e l /var/vmware/datarecovery/operations_log.utx | grep -i -B1 "success" | awk -F"$" ‘{print substr($2,5,21) " " substr($2, 26, 100) " " substr($3,5,100)}’ | grep c

#Mail Server Variables
domain=
host=$HOSTNAME
smtphost=yourmailhost
[email protected]

# Compare new list of all errors to old list of all errors
#if ! diff /root/olderror.out /root/newerror.out
#then
#err=$(diff olderror.out newerror.out | grep -c ">")
#mv /root/newerror.out /root/olderror.out -f

#Send Report to Mail Server
(
sleep 1
echo "HELO $host.$domain"
sleep 1
echo "mail from:[email protected]$domain"
sleep 1
echo "rcpt to:$mailto"
sleep 1
echo "data"
sleep 1
echo "subject:VDR-Report – $host $(date +"%Y-%m-%d %H:%M") Jobs OK: $succ, FAILED: $err"
sleep 1
echo "from:VMWare Data Recovery on "$host
sleep 1
echo "$host $(date +"%Y-%m-%d %H:%M") Jobs OK:$succ, FAILED:$err "
sleep 1
echo "##### Successful Jobs ($succ) #####"
sleep 1
strings -e l /var/vmware/datarecovery/operations_log.utx | grep -i -B1 "success" | awk -F"$" ‘{print substr($2,5,21) " " substr($2, 26, 100) " " substr($3,5,100)}’ | grep c
sleep 1
echo "##### Failed Jobs ($err) #####"
sleep 1
echo "VDR Errors: "$err
sleep 1
echo "."
sleep 1
echo "QUIT"
) | telnet smtphost 25

[/source]


 

TESTED AND WORKING:

 

[source language=”bash”]

#!/bin/bash

#Mail Server Variables
domain=
host=$HOSTNAME
smtphost=
mailto=

#Send Report to Mail Server
(
sleep 1
echo "HELO $host.$domain"
sleep 1
echo "mail from:[email protected]$domain"
sleep 1
echo "rcpt to:"$mailto
sleep 1
echo "data"
sleep 1
echo "subject:VDR-Report – $host.$domain $(date +"%Y-%m-%d %H:%M")"
sleep 1
echo "from:VMWare Data Recovery Report on "$host
#sleep 1
#echo "$host $(date +"%Y-%m-%d %H:%M") Jobs OK:$succ, FAILED:$err "
sleep 1
echo "##### Failed Jobs #####"
sleep 1
succ=$(strings -e l /var/vmware/datarecovery/operations_log.utx | grep -i -B1 "success" | awk -F"$" ‘{print substr($2,5,21) " " substr($2, 26, 100) " " substr($3,5,100)}’)
sleep 1
echo "."
sleep 1
echo "QUIT"
) | telnet $smtphost 25

[/source]

 

CRON JOB: To run every Monday at 8 AM

[source]
chmod +x vDRreport.sh

crontab -e
00 8 * * 1 /root/vDRreport.sh
[/source]

References:

Install/Renew SSL cert on ESXi

Install/Renew SSL cert on ESXi

To extract the private and public keys from the pfx you can use openssl and the following commands:

Step 1. openssl pkcs12 -in xxxx.pfx -out rui.crt -nokeys -clcerts

Step 2. openssl pkcs12 -in xxxx.pfx -nocerts -out privatekey.pem

Step 3. openssl rsa -in privatekey.pem -out rui.key

Install vCenter CLI

Install using default configuration on the vCenter server.

NB: The source files are loacated on the media kit.

Disable Lockdown Mode

a) Select Host 1 from the vCenter console and click the “Configuration” tab.
b) In the “Software” menu on the configuration sheet select “Security Profile”.
c) Click “Edit” to change the Lockdown mode
d) Untick “Enable Lockdown Mode”

Verify the private and public key match.

a) Openssl x509 –noout –modulus –in rui.crt | openssl md5
b) Openssl rsa –noout –modulus –in rui.key | openssl md5

The md5 hashes returned from each of the above commands should match.

Install New Certificates

a) Copy the private and public key files for the new certificates to c:\SSLcert on the vCenter server.

a. Public Key = rui.crt
b. Private Key = rui.key

b) Open the vSphere CLI command prompt and enter the following command.

vifs.pl –server <hostx> –put c:\SSLcert\rui.key /host/ssl_key
vifs.pl –server <hostx> –put c:\SSLcert\rui.crt /host/ssl_cert

c) Reboot the ESXi host
d) Repeat the above steps for each ESXi host in the cluster.

Insall/Renew SSL cert vCenter Server

Insall/Renew SSL cert vCenter Server

Backup the contents of : C:\Users\All Users\VMWare\VMWare VirtualCenter\SSL

Stop the following services:

• VMware VirtualCenter Management Webservices
• VMWare VirtualCenter Server

To extract the private and public keys from the pfx you can use openssl and the following commands:

Step 1. openssl pkcs12 -in xxxx.pfx -out rui.crt -nokeys -clcerts

Step 2. openssl pkcs12 -in xxxx.pfx -nocerts -out privatekey.pem

Step 3. openssl rsa -in privatekey.pem -out rui.key

openssl pkcs12 -export -in rui.crt -inkey rui.key -name rui -passout pass:testpassword -out rui.pfx

NB: the rui.pfx key should have the testpassword set as per article

You will now have the 3 files required to replace the self signed certificate in vcenter.

Copy the SSL private key, public key and pfx files that have been issued by Certificate Authority to:

• Private Key = rui.key
• Public Key = rui.crt
• PFX = rui.pfx

C:\Users\All Users\VMWare\VMWare VirtualCenter\SSL

1. Open the command prompt.
2. Change to the directory where vCenter Server is installed. The default location is
C:\Program Files\VMware\Infrastructure\VirtualCenter Server.
3. Run this command to reset the database password:
vpxd.exe -p
4. When prompted, enter the new password.

Note: This command rehashes the passwords for the database users from the ODBC connection.

Start the following services:

• VMware VirtualCenter Management Webservices
• VMWare VirtualCenter Server

NB: If the services do not restart then there is either a missing file or the public and private key do not match.

Restore the backed up public and private key files to rollback.

Test the certificate by opening a browser to the following address:
http://<FQDN of vSphere vCenter Server>

Reference: http://kb.vmware.com/selfservice/microsites/search.do?
language=en_US&cmd=displayKC&externalId=1003070

Note: After changing the SSL certificate, all hosts managed by vCenter Server must be re-authenticated.

To do so, use the VI Client to disconnect and then reconnect the hosts

Check if the following articles applies to your environment – vCenter Server Service Status plug-in cannot be enabled (1013472) – http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1013472

Usefull VMware PowerCLI Commands and others commands

[source]ForEach ($VM in Get-VM ){($VM.Extensiondata.Guest.Disk | Select @{N="Name";E={$VM.Name}},DiskPath, @{N="Capacity(MB)";E={[math]::Round($_.Capacity/ 1MB)}}, @{N="Free Space(MB)";E={[math]::Round($_.FreeSpace / 1MB)}}, @{N="Free Space %";E={[math]::Round(((100* ($_.FreeSpace))/ ($_.Capacity)),0)}})}[/source]

  • VMware Support Bundle

[source]

vm-support -w /vmfs/volumes/datastore1/

Usage: /sbin/vm-support [-a] [-n] [-s] [-S] [-d duration_in_seconds] [-i interval] [-k] [-x] [-X wid] [-q] [-w] [-l] [-Z wid] [-r] [-R statedumper options] [-v] [-h]
-a causes all cores to be tar’ed up – even those from previous
runnings of this script
-n causes no cores to be tar’ed up
-s take performance snapshots in addition to other data
-S take only performance snapshots
-d <s> set performance snapshot duration to <s> seconds [default 300]
-i <s> sleep <s> seconds between snapshots [default autodetect]
-k gather files stats/ of each VM (vm’s stats, vmware-stats*.log files)
-x lists wids for running VMs
-X <wid> grab debug info for a hung VM
-q runs in quiet mode
-w <dir> sets the working directory used for the output files
-l print list of files being collected
-Z <wid> suspends a VM and grabs debug info
-r causes all vmfs3 volumes’ volume headers to be tar’ed up
-R <statedumper options> invokes statedumper utility with given options
-v prints out vm-support version
-h prints this usage statement

[/source]

  • Export Advanced Settings

[source]Get-VMHostAdvancedConfiguration -vmhost (get-vmhost) | findstr "NFS"[/source]

  • Connect to vSphere Server

[source]Connect-VIServer [vSphere Hostname][/source]

  • Remove all Snapshots

[source]Get-VM | Get-Snapshot | fl | remove-Snapshot[/source]

  • Execution Signing

[source]powershell Set-Executionpolicy unrestricted[/source]

 

[source]powershell Set-Executionpolicy restricted[/source]

  • Deploy VMware Tools

[source]
Get-Cluster "Productie" | Get-VM | Update-Tools –NoReboot
Get-Cluster "Productie" | Get-Folder "Beheer servers" | Get-VM | Update-Tools –NoReboot
Get-Cluster "Productie" | Get-VM "BHR-SVR11" | Update-Tools –NoReboot
Get-View -ViewType VirtualMachine | select Name, @{ Name=”ToolsVersion”;Expression={$_.config.tools.toolsVersion}}
[/source]

  • Show Physica NIC details

[source]
esxcfg-nics -l
/etc/vmware/esx.conf
[/source]

  • Sometimes you need exactly the correct version of tools from ESXi, maybe to package it via SCCM.. Here is the location of the ISO.

[sourcecode]

/vmimages/tools-isoimages

[/sourcecode]

vmware_tools

VCDX5 and VCP510 Exam notes

Target acquired – VCDX 5 – I have selected this certification path as my next goal and will keep all my research on this post..

vSphere Documents

VMware Online Labs

VCP510

  • 85 Questions
  • 300 Pass Score (scaled scores)
  • 90 Minutes
  • 1 min aprox per Question

Exam

Notes:

Reference Sites:

vSphere Videos

IBM and Vmware

Cisco UCS Reference architecture

 HP and VMware Networking

Posters 

Vmware Diagnostics

TODO:

  1. Watch Trainsingals training on Train
  2. Read the Official VCP Training Book
  3. Study Exam Questions
  4. Setup Lab
    1. vSphere Appliance
    2. ESXi 5 .1
    3. Storage Appliance
        • [sourcecode]gunzip -c vsim-DOT812-7m.tgz  | tar xopf[/sourcecode]

  1. Install VIX API – http://www.vmware.com/support/developer/vix-api/vix112_reference/
  2. Change Password Complexity – http://www.novell.com/support/kb/doc.php?id=7008156
  3. ESX opensources
  4. BusyBox (minimal console of ESXi)
  5. Read all the material
  6. Command Cheat Sheet
  7. Read Blogs on Exam
  8. Make notes on possible Exam Questions
  9. Practice GUI and take screenshots

Scripts

VMware vSphere vs Citrix XenServer Cost Calculator

Download VMware vSphere vs Citrix XenServer Cost Calculator here :- VMware vs XenServer Cost Analysis – v1

Objectives of the Calculator

The calculator is a tool to assist getting in front of IT Decision makers to educate, visualize and discuss VMware vs XenServer cost comparison and identify business requirements, matching features to editions and simplifying the complexity of various licensing options.
How to Use the Calculator
To compare VMware vs XenServer Costs, simply complete the items in the green section and take note of the comments.

  • Number of Host Servers
  • Number CPUs per host

The VMware vs XenServer Calculator has tabs that contain the following for easy reference:

  • XenServer Editions and Features List
  • VMware Editions and Features List
  • Citrix XenServer Support Options

Clearly explain the highlighted points and difference between products and support agreements..

Someone is targeting my blog/this post with SPAM, please ignore any rude photos at the bottom of this blog.. WordPress.com is trying to fix it atm

How to Configure Scripted ESX Installations


Using Floppy Disk and CD-ROM

Build the Kickstart Config File

  • Browse to an existing ESX server at http://esxservername
  • Click Log in to the Scripted Installer at right
  • Click Yes in the Security Alert message window
  • Log in with User name “root” and this server’s root account password
  • Select Installation Type Initial Installation
  • Select Installation Method CD-ROM
  • Leave Remote Server URL empty
  • Select Network Method Static IP
  • Select Yes for Create a default network for VMs
  • Verify the VLAN value is 0
  • Set Time Zone appropriately
  • Select Yes for Reboot after Installation
  • Enter a password without any space characters for the Root Password
  • Click Next
  • Enter required values for Hostname, IP address, Netmask, Gateway and Nameserver and click Next
  • Accept the Licence Agreement and click Next
  • In the Partition Configuration table, change the “/” partition size to 10000, the “swap” partition size to 1500 and the /var/log partition size to 4000
  • Verify that the Licensing Mode is set to Use License Server
  • Click Next
  • Set the License server name to mpxsydvc1.mpxnsw.ad.multiplex.biz and the Port to 2700
  • Set the ESX Server License Type to Standard
  • Click Next

 

  • Click Download Kickstart File
  • Click Save and save the Kickstart File KS.cfg to floppy disk

Note:  Never, ever, ever edit or even open a Kickstart config file in Notepad. Only ever use Wordpad. Now, read the previous sentence again. If you choose to ignore this, then don’t bother reading the rest of this document as none of it will work!

  • Close the browser.

Run a Scripted Installation

  • At the server which is to have VMware ESX installed, boot the server from an ESX installation CD-ROM
  • At the ESX Server 3 installation method selection screen, type:

esx ks=floppy method=cdrom and press Enter

  • Allow the installation to proceed through to completion
  • The CD-ROM will be ejected – remove the disk
  • The server will reboot into VMware ESX Server


Using PXE and RIS

Build the Kickstart Config File

  • Browse to an existing ESX server at http://esxservername
  • Click Log in to the Scripted Installer at right
  • Click Yes in the Security Alert message window
  • Log in with User name “root” and this server’s root account password
  • Select Installation Type Initial Installation
  • Select Installation Method Remote
  • Edit  the Remote Server URL to ftp://ftpserverFQDN/

e.g. ftp://mpxbnebck1.mpxqld.ad.multiplex.biz/

  • Select Network Method DHCP
  • Select Yes for Create a default network for VMs
  • Verify the VLAN value is 0
  • Set Time Zone appropriately
  • Select Yes for Reboot after Installation
  • Enter a password without any space characters for the Root Password
  • Click Next
  • Enter required values for Hostname, IP address, Netmask, Gateway and Nameserver and click Next
  • Accept the Licence Agreement and click Next
  • In the Partition Configuration table, change the “/” partition size to 10000, the “swap” partition size to 1500 and the /var/log partition size to 4000
  • Verify that the Licensing Mode is set to Use License Server
  • Click Next
  • Set the License server name to mpxsydvc1.mpxnsw.ad.multiplex.biz and the Port to 2700
  • Set the ESX Server License Type to Standard
  • Click Next
  • Click Download Kickstart File
  • Click Save
  • Save the Kickstart File KS.cfg to a temporary location and close the browser.

Note:  Never, ever, ever edit or even open a Kickstart config file in Notepad. Only ever use Wordpad. Now, read the previous sentence again. If you choose to ignore this, then don’t bother reading the rest of this document as none of it will work!


Configure RIS

  • At an available Windows Server 2003 server, install and configure Microsoft RIS
  • In the RIS folder structure, create the following folders:
    • RISdrive:\RISfolder\Setup\English\Images\PXELinux
    • RISdrive:\RISfolder\Setup\English\Images\PXELinux\i386
    • RISdrive:\RISfolder\Setup\English\Images\PXELinux\i386\templates
    • RISdrive:\RISfolder\Setup\English\Images\PXELinux\i386\templates\pxelinux.cfg
  • Copy the following files from the \isolinux folder on the ESX CD-ROM to the RISdrive:\RISfolder\Setup\English\Images\PXELinux\i386\templates folder:
    • boot.msg
    • initrd.img
    • splash.lss
    • vmlinuz
  • Download syslinux from http:www.kernel.org/pub/linux/utils/boot/syslinux and copy the following files to the RISdrive:\RISfolder\Setup\English\Images\PXELinux\i386\templates folder:
    • pxelinux.0
  • In the RISdrive:\RISfolder\Setup\English\Images\PXELinux\i386\templates folder, create a file pxelinux.sif with the following content:

[OSChooser]

Description = “VMware ESX Server 3.0.1”

Help = “This option runs a Linux installer to install VMware ESX Server 3.0.1.”

LaunchFile = “Setup\English\Images\PXELinux\i386\templates\pxelinux.0″

ImageType = Flat

Version=”1.01”

  • In the RISdrive:\RISfolder\Setup\English\Images\PXELinux\i386\templates\pxelinux.cfg folder, create a file default (no extension) with the following content:

DEFAULT esx

prompt 0

timeout 1000

label esx

kernel vmlinuz

append ksdevice=eth0 initrd=initrd.img ks=ftp://IP_address_of_FTP_server/vmwareesx301/ks.cfg

 

 

Configure FTP Server

  • At an available FTP server, create the folder VMWareESX301
  • Copy the entire contents of an ESX Server Installation CD-ROM into this folder
  • Copy the KS.cfg file created above and stored in a temporary location into this folder

 

Run a Scripted Installation

  • At the server which is to have VMware ESX installed, boot the server and select PXE Installation (F12)
  • Select the ESX Server 3.01 installation option
  • Continue through the RIS process and allow the ESX installation to proceed through to completion
  • The server will reboot into VMware ESX Server