How To
Summary
Revision level: 3.2 Updated: 14 January 2003 Supported system: IBM eServer xSeries 440 (Type 8687) Follow the eServer xSeries VMware network operating system (NOS) installation instructions provided in this document in sequential order.
Steps
Revision level: 3.2
Updated: 14 January 2003
Supported system: IBM eServer xSeries 440 (Type 8687)
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.
This document contains the following:
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 Installing a ServeRAID controller
4.2 Installing IBM ServeRAID- 4H device drivers
4.3 Setup of the FAStT500
4.4 Pre-ESX install checklist for a 16-way x440 system
4.5 VMware and 440 xSeries server known issues
This document provides xSeries server users with the installation instructions for a basic VMware ESX Server installation. Be sure to follow these instructions for installing VMware ESX Server precisely to ensure that you install it correctly. Determine if the server is equipped with an IBM ServeRAID card. If your xSeries server has a ServeRAID adapter, review 4.0 Appendix" before you proceed with the installation instructions in section "2.0. VMware ESX Server version 1.5.2 installation instructions".
Note: If your server has a ServeRAID card installed, you must perform additional procedures described in 4.0 Appendix".
Note: If you have a 16-way x440, when you start the server from the VMware ESX Server CD for the first time, at the Boot: prompt, type esx APIC and press Enter.
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. See the ServeRAID or FAStT documentation for information about how to setup any necessary RAID array or SAN.
Install supplemental device drivers
Occasionally, updated device drivers for SCSI or RAID controllers are needed for installation on newer servers. If you have such a device driver, have the disk ready during the installation.
Note: These device drivers are VMware specific. Standard Linux or Unix device drivers do not work.
This section contains preparatory information about installing VMware ESX Server.
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 server and the VMware kernel. The recommended size is 25MB.
-
The swap partition is used by the console-operating server and is normally 1 to 2 times the size of the memory allocated to the console-operating server. The console operating server memory size can be determined as follows:
- 1 to 4 virtual machines - 128MB
- 5 to 8 virtual machines - 192MB
- 9 to 16 virtual machines - 272MB
- 17 to 32 virtual machines - 384MB
- 32 or more virtual machines - 512MB
LILO boot loader
The installation process asks you where you would like to place LILO. Choose MBR unless you have a server management partition you want to be able to boot.
Network configuration
This is the network configuration for the console-operating server. While it is possible to use DHCP, using static IP address is recommended.
Time zone selection
Select the appropriate time zone.
Accounts and passwords
Root account
The root account on the console-operating server 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.
Note:
If you have a 16-way x440, at the end of text mode setup, do not restart the server. On a second server, open up a web browser and go to http://x.xx.xx.xx/pcidivy, where x.xx.xx.xx is the FQDN or IP address of the VMware server you are installing, and setup your devices. Ensure that all devices that will be either dedicated or shared with the console OS, reside on the primary/master node. Console access to resources, such as network cards, HBAs, and disk controllers that are physically located on the secondary/slave mode is not supported. Restart the server after finishing device allocation to continue VMware ESX Server installation.
System configuration
Once the server has restarted, 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 displays on the boot loader screen during the initial stage of server startup. As there is normally only one configuration, the default of vmnix is recommended.
Console memory
The memory allocated exclusively to the console-operating server varies based on the number of concurrently running virtual machines. Use the following list to determine the correct amount of console memory:
- 1 to 4 virtual machines - 128MB
- 5 to 8 virtual machines - 192MB
- 9 to 16 virtual machines - 272MB
- 17 to 32 virtual machines - 384MB
- 32 or more 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 start the server. 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 server 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 server, assigned to the virtual machines or shared. As a general rule, the first Ethernet adapter is assigned to the console operating server. Ensure that you reserve that adapter for the console operating server or you may lose network connectivity when you reboot. A network card can be shared with the console operating server if needed. This will impact the performance. For more information and instructions, see the Networking chapter on page 222, Allowing the Console Operating System to Use the Virtual Machines Devices, in the VMware v1.5.2 manual.
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 when you start the server. 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. Select the choice most appropriate for your environment. Select from the following:
- 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 allow the user to create new partitions using the available physical storage. Each physical disk/RAID will show in this section, as a partitionable field, for example if you had configured four disks as RAID 5 totaling 45 GB, you can create one VMFS partition of the whole 45 GB, or several smaller partitions (you can not exceed four partitions per physical disk or configured RAID). If you select to create one large partition, you can then create several virtual machines on that partition (this is the recommended method when creating virtual machines). After creating the partition(s) you will 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). Each RAID volume can have up to 4 partitions. If you need more partitions, create an extended partition on the RAID volume. This will house any other partitions you wish to make.
Swap File Configuration
By default the swap file is created the same size as the physical memory in the computer. This completes the installation and configuration of ESX Server. You are now ready to create virtual machines.
Complete the following steps to install the Advanced System Management Processor (service processor) device driver:
- Insert the Advanced System Management Processor driver diskette into the ESX Servers diskette drive.
-
To install the Linux driver on the ESX Server complete the following steps:
- On the console OS create the following symbolic link:
ln -s /usr/src/2.4.9-vmnix2 /usr/src/linux - Mount the floppy and install the following package:
rpm -ivh /mnt/floppy/ibmasm/ibmasm-src-redhat-WRP112A.rpm - After the new package is created in step b, install the new package:
rpm -ivh /usr/local/ibmasm/ibmasm-1.0-6.1.i386.rpm
- On the console OS create the following symbolic link:
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.
Note: VMware supports the ServeRAID-3H, 4L, 4Lx, 4Mx as well as the 4H.
Complete the following steps to install IBM ServeRAID:
- Insert the ServeRAID CD into the CD-ROM drive immediately after the server has started.
- Shortly after you insert the ServeRAID CD, an IBM ServeRAID window displays 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.
- When the server has completed updating its files, you will be prompted to restart the server. Keep the ServeRAID CD in the CD-ROM drive and restart the server.
- The server 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, go to ServeRAID - (4H, 4M, 4Mx, 4L, 4Lx) User's Reference v4.80
- After you have created and initialized the ServeRAID disks, remove the ServeRAID CD and insert the VMware ESX Server Setup CD. Restart the server and continue with step 2 under section 2.0 Installation instructions.
It is recommended that installation and administration of the FAStT500 come from a Microsoft Windows 2000 or Windows NT 4 server that is not running in a VM (Virtual Machine) mode. There is currently a known issue with configuring the FAStT500 from a Linux box as it will overwrite LUN configurations and cause Windows 2000 and Windows NT 4 servers 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 Windows 2000 server. These instructions assume that the FAStT500 is already powered on.
Complete the following steps to setup the FAStT500:
- Connect a NULL modem cable from Controller As serial port on the back of the FastT500 to an available laptop or desktop running Windows 2000.
-
Open up HyperTerminal and configure to use that COM port with the following settings:
- 9600bps
- 8 data bits
- 1 stop bit
- Hardware flow control
- Press Ctrl+Break a few times until you get the prompt Esc for Shell Break to set baud rate.
- Press Ctrl+Break again until you get the prompt Press Space to set baud rate.
- Press the space bar until you get the message Baud rate set at 9600.
- Press Ctrl+Break a few times until you get the prompt Esc for Shell Break to set baud rate.
- Press Esc to get a login prompt.
- Type infiniti as the password.
- At the -> command prompt, type netCfgSet and press Enter.
-
Configure the following fields. Press Enter for fields not listed:
- RAIDMGR Server #1: Enter the IP address of the server youll be using to connect to the FastT500 and setup/initialize the volumes.
- My IP Address: Enter the IP address that you want to assign to the FastT500 controller itself.
- Subnet Mask: Enter the network mask (example: 255.255.255.0) for the FastT500.
- Gateway IP Address: Enter in the gateway IP address if needed.
- Keep pressing Enter until you are back at the -> command prompt.
- Type sysReboot and press Enter.
- Install the FastT500 Client on the server with the IP address specified above and connect to the FastT500 over Ethernet.
- Setup 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 the Qlogic card is installed in. Do not connect the fiber cable until AFTER VMware ESX server is installed. After installation, when the fiber is re-attached, VMware will re-enumerate the drives, and the fiber drives will show up first, and the local SCSI drives will be second.
Before installing VMware ESX server on a 16-way system, complete the following steps:
- Use a recommended BIOS, Systems Management firmware, and Hot firmware.
- If a ServeRAID 4 or 3 series of RAID controller is to be used, ensure that it is running firmware level 4.84.
- Ensure that there are no more than seven PCI devices installed across both nodes.
- Follow the instructions that came with your server for information about how to correctly cable up and create a partition descriptor that will allow the two chassis to merge.
8687 - eServer xSeries 440 system
- The x440 server intermittently resets itself when configured with the combination of ServeRAID 4Mx adapter and Intel Dual Port 10/100 Ethernet Network Interface adapters. The current workaround to fix this issue is to disable the onboard Adaptec SCSI adapter.
- If you are installing on a x440 server with greater than 9 CPUs, processor affinity is not supported in this time.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
27 January 2019
UID
ibm1MIGR-45915