Installing VMWare ESX Server version 1.5 - Servers

Steps

VMware ESX Server version 1.5
Revision Level: 2.20
Updated: 16 Jan 2003

Supported Systems

8665 – IBM eServer xSeries 250
8685 – IBM eServer xSeries 255
8686 – IBM eServer xSeries 360
8681 – IBM eServer xSeries 370
8687 – IBM eServer xSeries 440

Follow the eServer xSeries VMware network operating system (NOS) installation instructions provided in this document in sequential order unless these instructions advise you differently. Windows and messages might differ from those in this document. Throughout this document, the term select is used to denote the use of arrow keys or the mouse to make a selection from a menu.

Sections within this document
This document contains the following sections:

1.0 Before installing VMware ESX Server
2.0 VMware ESX Server installation instructions
3.0 Advanced System Management Processor (Service processor)
4.0 Appendix
4.1 ServeRAID
4.2 Installing IBM ServeRAID - 4H device drivers
4.3 Setup of the FAStT500
4.4 Where to download device drivers and files
4.5 VMware and xSeries systems known issues

1.0 Before installing VMware ESX Server version 1.5

This document provides xSeries system users with the installation instructions for a basic VMware ESX Server installation process. Be sure to follow these instructions for installing VMware ESX Server precisely to ensure that you install it correctly. Determine if the system is equipped with an IBM ServeRAID card. If you have equipped your xSeries system with a ServeRAID card, please review section 4.0 Appendix before you proceed with the installation instructions in section 2.0.

NOTE: If you have a system that is equipped with a ServeRAID card, you must perform additional procedures in section 4.0 Appendix.

2.0 VMware ESX Server version 1.5 Installation instructions

Review this section to prepare for installing VMware ESX Server.

Storage
Before installing ESX Server, set up your disk hardware according to your needs. If you have a hardware RAID controller, set up your RAID sets. Make sure you know which disks and RAID sets will be used for the ESX Server software, the virtual machines, and any other data.

Install supplemental drivers
Occasionally, updated drivers for SCSI or RAID controllers are needed for installation on newer servers. If you have such a driver, have the disk ready during the installation.

Disk setup
There are three choices for partitioning the disk - Disk Druid, fdisk and autopartition.

• Autopartition
  Autopartition creates a default partition table and allows you to then manually edit that table with Disk Druid.
• Manually setting partition sizes
  You will create several partitions for the server installation. The instructions below will provide some guidance as to the recommended sizes:
  • The root partition (/) is used to store most of the files for the ESX Server software. The recommended size is 1.8GB.
  • The boot partition (/boot) stores the kernel files for the console operating system and the VMware kernel. The recommended size is 25MB.
  • The home partition (/home) is used to store the virtual machine configuration and log files. It is also the default location for suspended state files for the virtual machines. To reserve enough
    space for all of the virtual machines you plan to suspend to their configuration directories, you should allocate 10MB plus the memory size for each virtual machine.
    Note that suspended state files for virtual machines with more than 2GB of RAM must be suspended to a VMFS partition.
    
  • The swap partition is used by the console operating system and is normally 1 to 2 times the size of the memory allocated to the console operating system. The console operating system
    memory size can be determined as follows:
    • 1 - 4 virtual machines - 128MB
    • 5 - 8 virtual machines - 192MB
    • 9 - 16 virtual machines - 272MB
    • 17 - 32 virtual machines - 384MB
    • More than 32 virtual machines - 512MB

LILO boot loader
The installation process asks you where you would like to place LILO. Select MBR unless you have a system management partition you want to be able to boot.

Network configuration
This is the network configuration for the console operating system. While it is possible to use DHCP, using static IP address is recommended.

Time zone selection
Will the hardware clock be set to GMT? Select the appropriate time zone.

Accounts and passwords
Root account
The root account on the console operating system is used to administer the ESX Server computer. The password for this account is a critical part of ESX Server security and should be chosen with care. You should also record the password, as it cannot be recovered if it is lost.

User accounts
It is recommended that you create a non-root user for the purpose of creating and using virtual machines later. You may do this at the Add User screen. Often this user is generic.

System configuration
Once the server has rebooted, you should connect to the server using a Web browser to complete the installation. Log in as the root user then, click VMware ESX Server Setup Wizard.

Boot configuration
The configuration name appears on the boot loader screen during the initial stage of server startup. As there is normally only one configuration, the default value vmnix is recommended.

Console memory
The memory allocated exclusively to the console operating system varies based upon the number of concurrently running virtual machines. Use the following list to determine the correct amount:

• 1 - 4 virtual machines - 128MB
• 5 - 8 virtual machines - 192MB
• 9 - 16 virtual machines - 272MB
• 17 - 32 virtual machines - 384MB
• More than 32 virtual machines - 512MB

Kernel file
This name refers to the VMware kernel that is normally loaded during startup. You should accept the default kernel. Use it as the Default Boot Configuration. This choice allows you to select which configuration will be used to boot. As there is only one configuration during installation, you should select Yes.

Device allocation
ESX Server requires that devices be allocated between the console operating system and the virtual machines - and occasionally shared. List your disk controllers (SCSI/RAID/Fiber Channel), other SCSI devices and Ethernet adapters, then indicate whether each device should be assigned to the console operating system, assigned to the virtual machines, or shared. As a general rule, the first Ethernet adapter is assigned to the console operating system. Ensure that you reserve that adapter for the console operating system or you may lose network connectivity when you reboot. Note that network cards may not be shared. After allocating devices, click the link to reboot the computer.

Network configuration
Choose the network speed and duplex mode for the network cards assigned to the VMware kernel. The default is 100Mb/full. Read and accept the end user license agreement (EULA). You must enter the provided serial number before you can start virtual machines.

Host configuration
Start the VMware server at boot up. This is the recommended setting for normal running of ESX Server. You might change this if you need to start the VMware kernel manually for debug purposes.

Security configuration
ESX Server includes four security settings that may be changed while the server is running. From the following list, select the setting most appropriate for your environment :

• High security (SSL and SSH access only)
• Medium security (SSL,SSH and Telnet/FTP enabled)
• Low security (no encryption, Telnet/FTP enabled)
• Custom (check the following enabled services):
  • Management interface access encryption
  • Remote console encryption
  • SSH access to console operating system
  • Telnet allowed
  • FTP allowed

Editing Partitions and Creating VMFS
This section will describe how you are allowed to create new partitions using the available physical storage. Each physical disk/RAID will be shown in this section as a partitionable field; for example, if you have configured four disks as RAID 5 totaling 45GB, you can create one VMFS partition of the whole 45GB, or several smaller partitions (you cannot exceed four partitions per physical disk or configured RAID).

If you decide to create one large partition, you can then create several virtual machines on that partition (this is the recommend method when creating virtual machines). After creating the each partition, you need to format and name it. Virtual disks are created within VMFS partitions, so be sure to select VMFS as the partition type when creating partitions. You also need to create a 50MB VMware core dump partition for debugging purposes (this partition must be added manually even if you selected the auto partition method).

Swap File Configuration
By default the swap file is created the same size as the physical memory in the computer.

When you have completed this section, you have completed the installation and configuration of ESX Server. You are now ready to create virtual machines.

3.0 Advanced System Management Processor (Service Processor) driver

1. To install the Advanced System Management Processor (service processor) device driver, insert the Advanced System Management Processor driver diskette into the ESX Server’s diskette drive. For information on downloading the Advance System Management Processor driver, refer to section 4.4 Where to download device drivers and files.
2. To install the Linux driver on the ESX Server complete the following steps:
   1. On the console OS create the following symbolic link:
      ln -s /usr/src/2.4.9-vmnix2 /usr/src/linux
   2. Mount the floppy and install the following package:
      rpm -ivh /mnt/floppy/ibmasm/ibmasm-src-redhat-WRP112A.rpm
      Completing step 2 builds a new package.
   3. Install the newly built package as follows:
      rpm -ivh /usr/local/ibmasm/ibmasm-1.0-6.1.i386.rpm
      

4.0 Appendix

4.1 ServeRAID

The installation instructions for installing the ServeRAID controller card as the primary controller are listed below. The instructions vary depending on the type of ServeRAID you install.

NOTE: You should set configurations for the IBM ServeRAID card before you install VMware ESX Server.

4.2 Installing IBM ServeRAID - 4H device drivers

1. Insert the ServeRAID CD into the CD-ROM drive immediately after the system has started.
2. Shortly after you insert the ServeRAID CD, an IBM ServeRAID window appears, followed by a window that displays the current BIOS and firmware levels currently installed on your ServeRAID card. If they need to be updated, then click Update, if not, skip to step 4.
3. When the system has completed updating its files, you will be prompted to restart the system. Keep the ServeRAID CD in the CD-ROM drive and restart the system.
4. The system will start from the IBM ServeRAID CD again; however, this time, ServeRAID utilities will start and will be used to create and initialize the ServeRAID logical disks.

   NOTE: You must create and initialize the ServeRAID disks for a boot partition to be visible to VMware ESX Server. For instructions, click ServeRAID - IBM ServeRAID-4 Ultra 160 SCSI Controller user's reference version 4.80.

5. After you have created and initialized the ServeRAID disks, remove the ServeRAID CD and insert the VMware ESX Server Setup CD-ROM. Restart the system and continue with step 2 under section 2.0 Installation instructions. After completing the installation of VMware ESX Server, return and continue with step 6 (the next step of this section 4.2 Installing IBM ServeRAID - 4H device drivers) to update the ServeRAID- 4H driver.
6. The ServeRAID Driver on the IBM ServeRAID CD-ROM might not have a digital signature. To insure that a digitally signed driver is installed, refer to section 4.4 Where to download device drivers and files and download the latest digitally signed driver.
7. After you download the ServeRAID driver from the Web, update the ServeRAID driver on the system. Insert the diskette that contains the IBM ServeRAID driver into the diskette drive.

4.3 Setup of the FAStT500
It is recommended that installation and administration of the FAStT500 come from a Windows 2000 or Windows NT 4 system that is not running in a VM environment. There is currently a known issue with configuring the FAStT500 from a Linux box as it will overwrite LUN configurations and cause W2k and NT4 systems to lose access to their FAStT-based volumes. The following steps will configure the network interface on Controller A so that it can be administered from a W2k system. Instructions assume that the FAStT is already powered on.

Complete the following steps to setup the FAStT500:

1. Connect a NULL modem cable from Controller A’s serial port on the back of the FastT500 to an available laptop or desktop running W2k.
2. Open up HyperTerminal and configure to use that COM port with the following settings:
   1. 9600bps
3. 2. 8 data bits
   3. 1 stop bit
   4. Hardware flow control
4. Press Ctrl+Break a few times until you get the response “Esc for Shell Break to set baud rate”.
5. Press Ctrl+Break again until you get the prompt “Press Space to set baud rate”.
6. Press the Space bar until you get the response “Baud rate set at 9600”.
7. Press Ctrl+Break a few times until you get the response “Esc for Shell Break to set baud rate”.
8. Press Esc to get a login prompt.
9. Type infiniti as the password.
10. At the -> command prompt, type netCfgSet and press Enter.
11. Configure the following fields. Press Enter for fields not listed:
    1. RAIDMGR Server #1: Enter the IP address of the system you’ll be using to connect to the FastT500 and setup and initialize the volumes.
    2. My IP Address: Enter the IP address that you want to assign to the FastT500 controller itself.
    3. Subnet Mask: Enter the network mask (example: 255.255.255.0) for the FastT500.
    4. Gateway IP Address: Enter the gateway IP address if needed.
    5. Keep pressing Enter until you are back at the -> command prompt.
12. Type sysReboot and press Enter.
13. Install the FastT500 Client on the system with the IP address specified above and connect to the FastT500 over Ethernet.
14. Set up and initialize your arrays.

    NOTE: During installation of the VMware ESX Server software, do not connect the fiber cable to the Qlogic HBA. Doing so will cause the Qlogic to be enumerated first during setup, no matter which slot in which the Qlogic card is installed. Do not connect the fiber cable until after VMware ESX server is installed. After installation, when the fiber is reattached, VMware will re-enumerate the drives, and the fiber drives will show up first; the local SCSI drives will be second.

4.4 Where to download device drivers and files

• Click IBM Advanced System Management Device Driver for Red Hat Linux.
• Click IBM eServer xSeries 370 and IBM Netfinity 8500R - Advanced System Management Processor Firmware Update Diskette version 2.16 or later (DOS update package) for the xSeries 370 processor (service processor).
• Click IBM eServer xSeries 250 and Netfinity 7100, 7600 - Advanced System Management Processor Firmware Update Diskette version 1.25 or later (DOS update package) for the xSeries 250 processor (service processor).
• Click IBM eServer xSeries 255 - Integrated System Management Processor Update version 1.04 or later (DOS update package) for the xSeries 255 processor (service processor).
• Click ServeRAID - Version 5.11 for Linux to download the ServeRAID drivers.
• Click Servers - IBM 10/100 EtherLink Server Adapter by 3COM device drivers version 2.1c or later for Linux to download IBM 10/100 EtherLink Server Adapter by 3COM Device Drivers for Linux version 2.1c.
• Click Fibre Channel Solutions - IBM FAStT Host Adapter Device Driver version 5.38.6 for Red Hat Linux v7.1 and v7.2, SuSE Linux v7.3 and TurboLinux v7 to download IBM FAStT Host Adapter Device Driver for RedHat Linux v7.1 version 5.38.6.

4.5 VMware & xSeries systems known issues

8687 - eServer X440 system
The xSeries 440 system intermittently resets itself when configured with the combination of the ServeRAID 4Mx adapter and the Intel Dual Port 10/100 Ethernet Network Interface adapters. The current workaround to fix this issue is to disable the onboard Adaptec SCSI adapter.