VMware

VMware ESX Server 2.0

Features | Documentation | Knowledge Base | Discussion Forums

previous Prev   Contents   Last   Next next

 Upgrading from ESX Server 1.5.x or ESX Server 2.0 Beta to ESX Server 2.0

Upgrading from ESX Server 1.5.x or ESX Server 2.0 Beta to ESX Server 2.0

To upgrade from ESX Server 1.5.x or a beta version of ESX Server 2.0 to ESX Server 2.0, use the installation CD-ROM.

Caution: Upgrading directly from ESX Server 1.0 or 1.1 to ESX Server 2.0 is not supported.

  1. Insert the installation CD into the server's CD-ROM drive.
  2. Boot the computer. The system begins booting from the CD-ROM. If it does not boot, change the BIOS setting to allow the system to boot from CD-ROM.
  3. At the first installer screen, choose Upgrade.
  4. You are asked if you have a driver disk provided by VMware for a device that is not handled by drivers in this release of ESX Server.

    If you do not have a driver disk, choose No and continue with the installation.

    If you have a driver disk from VMware, put the driver disk into the floppy drive and choose Yes.

  5. If you do not have enough swap space for the new service console, the installer asks you where to place a new swap partition. Accept the default location unless you have a specific reason for using a different one.
  6. The installer upgrades your ESX Server installation.
  7. When the upgrade completes and displays the final screen, reboot. The machine keeps the device allocations that you previously set up.
  8. After the server reboots, the System Configuration Wizard launches. For information on configuring the server, see Using the System Configuration Wizard to Configure Your Server. As you step through the wizard, ensure that the wizard's settings are appropriate. Note the following:
    • On the Licensing and Serial Numbers screen, enter your ESX Server 2.0 license and, if you have one, your VMware Virtual SMP for ESX Server license.
    • On the Startup Profiles screen, adjust the amount of memory allocated to the service console. If your ESX Server 1.5.2 installation had 128MB allocated to the service console, this amount must be upgraded to 192MB, which is sufficient for managing up to eight virtual machines. Change the number to 272MB for managing up to 16 virtual machines, 384MB for 32 virtual machines or 512MB for more than 32 virtual machines. For background, see Sizing Memory on the Server and Updating the Startup Profile.

      Also, check device allocation for the SCSI controller. If there is only one SCSI adapter the you need to make sure it is shared between the virtual machines and the service console. For the SCSI controller, in the Dedicated To list, select Virtual Machines, then check Shared with console operating system.

  9. If you want, you can improve virtual machine performance by upgrading the VMFS volume from VMFS-1 to VMFS-2. See Configuring Storage: Disk Partitions and File Systems.
Verifying Your Device Driver Mappings

Verifying Your Device Driver Mappings

During the upgrade, the ESX Server installer renames the /etc/vmware/vmware-device.map.local file to /etc/vmware/vmware-device.map.local.orig. After the upgrade, compare the vmware-device.map.local.orig file with the newly created vmware-device.map.local file and make any necessary changes, as the locations of some drivers have changed in ESX Server 2.0. With the addition of new drivers in ESX Server 2.0, further customization of vmware-device.map.local may not be necessary.

Upgrading Default Speed/Duplex Setting for NICs for a Previous ESX Server Release

Upgrading Default Speed/Duplex Setting for NICs for a Previous ESX Server Release

The default speed/duplex setting for ESX Server NICs has changed from "100/1000/full" in ESX Server 1.5.x to "autonegotiate" in ESX Server 2.0.1. If you are upgrading from ESX Server 1.5.x, then you may need to alter your switch's setting to "autonegotiate", for ports connected to the ESX Server machine, or you may force the NICs to full duplex in the NIC configuration page. (Log into the VMware Management Interface as the root user, click the Options tab, click Network Connections, then click Physical Adapters.)

Note: It is important that both the switch port and the NIC are either both set to autonegotiate, or both forced to the same speed/duplex setting

Upgrading SNMP from a Previous ESX Server Release

Upgrading SNMP from a Previous ESX Server Release

If you are upgrading from an ESX Server 1.5.x release, then SNMP, and possibly other system management agents, will not work properly. Save and copy onto another machine all SNMP files that were used to set up read/write community names, trapsinks, and trapcommunity names.

Complete the following steps.

  1. Save and copy onto another machine the following files:
    • ESX Server 1.5 and 1.5.1:
    1. /usr/share/snmp/snmpd.conf — Save this file, but remove the last section that starts with "# VMware ESX Server SNMP modules -- Edit this section at your own risk". We'll call this file Alpha.
    2. (Optional) /etc/snmp/snmpd.conf — If you have this file, and made changes to it or if you have installed third-party system management software on ESX Server, then save this file. We'll call this file Beta.
      • ESX Server 1.5.2:
    3. /etc/vmware/vmware-snmpd.conf — Save this file, but remove the last section that starts with "# VMware ESX Server SNMP modules -- Edit this section at your own risk". We'll call this file Alpha.
    4. (Optional)/etc/snmp/snmpd.conf — If you have this file, and made changes to it or if you have installed third-party system management software on ESX Server, then save this file. We'll call this file Beta.
  2. If you've created only an Alpha file, then rename it to MAIN. If you've created Alpha and Beta, then merge your customizations into a single file, called MAIN. Be sure to eliminate any duplicate configuration items in the MAIN file.
  3. Follow the instructions in Upgrading from a Previous Version of ESX Server.
  4. If you are upgrading from ESX Server 1.5 or 1.5.1, then install the ucd-snmp-4.2.3-1.i386.rpm and ucd-snmp-utils-4.2.3-1.i386.rpm files from the ESX Server CD. Log in as the root user and type rpm -Uhv <snmp_file> for each of these files. If you are upgrading from ESX Server 1.5.2, then you do not do this step.
  5. Complete one of the following, depending on whether you are only using VMware ESX Server SNMP or if you are using VMware ESX Server SNMP with third-party system management agents:
    • Only using VMware ESX Server SNMP
    1. Take the MAIN file you created and rename it on ESX Server as /etc/snmp/snmpd.conf.
    2. Use the VMware Management Interface to configure the vmware-snmpd agent and restart SNMP services. See Configuring the ESX Server Agent through the VMware Management Interface.
      • Using VMware ESX Server SNMP with third-party system management agents
    3. Upgrade or reinstall your third-party system management agents. Refer to your management application documentation.
    4. Take the MAIN file you created and rename it on ESX Server as /etc/snmp/snmpd.conf.
    5. Use the VMware Management Interface to configure the vmware-snmpd agent and restart SNMP services. See Configuring the ESX Server Agent through the VMware Management Interface.
    6. Restart the third-party system management agents according to the vendor's procedures.
Upgrading a Previous ESX Server Release with an existing vmware- device.map.local File

Upgrading a Previous ESX Server Release with an existing vmware- device.map.local File

During the ESX Server upgrade, the ESX Server installer renames the /etc/vmware/vmware-device.map.local file to /etc/vmware/vmware-device.map.local.orig. After the upgrade, compare the vmware-device.map.local.orig file with the newly created vmware-device.map.local file and make any necessary changes, as the locations of some drivers have changed in ESX Server 2.0. With the addition of new drivers in ESX Server 2.0, customization of vmware-device.map.local may not be necessary.

previous Prev   Contents   Last   Next next