Citrix Systems 6.1.0 manual Upgrading a Single XenServer Host Using the xe CLI

Page 32

Important:

You will be unable to contact the pool master until the upgrade of the master is complete. Shutting down the pool master causes the other hosts in the pool to enter emergency mode. In general, a XenServer host enters emergency mode when it is a member of a pool whose master has disappeared from the network and cannot be contacted after a number of attempts. VMs continue to run on hosts in emergency mode, but control operations are not available.

4.Boot the pool master using the XenServer installation media and method of your choice (such as, installation CD or network). Follow the XenServer installation procedure (see Chapter 3, Installing XenServer and XenCenter) until the installer offers you the option to upgrade. Choose to upgrade.

Warning:

Be absolutely sure to select the upgrade option so as to avoid losing any existing data.

Warning:

If anything interrupts the upgrade of the pool master or if the upgrade fails for any reason, do not attempt to proceed with the upgrade. Reboot the pool master and restore to a working version of the master. For details on restoring a XenServer host, see the XenServer Administrator's Guide.

Once your pool master restarts, the other hosts in the pool will leave emergency mode and normal service is restored after a few minutes.

5.On the pool master, start or resume any shut down or suspended VMs. Migrate any VMs that you wish back to the pool master.

6.Select the next XenServer host in your upgrade path. Disable the host.

7.Ensure that no VMs are running on the host. Shut down, suspend or migrate VMs to other hosts in the pool.

8.Shut down the host.

9.Follow the upgrade procedure for the host, as described for the master in Step 4.

Note:

If the upgrade of a host that is not the master fails or is interrupted, you do not need to revert. Use the host-forgetcommand to forget the host. Re-install XenServer on the host, and then join it, as a new host, to the pool using the pool-joincommand.

10.On the host, start or resume any shutdown or suspended VMs. Migrate any VMs that you wish back to the host.

11.Repeat Steps 6 – 10 for the rest of the hosts in the pool.

12.Once each host in the pool has been upgraded, it is important to upgrade the XenServer Tools on all VMs. Please refer to the XenServer Virtual Machine User's Guide for details.

Note:

Running older versions of the XenServer Tools on newer XenServer installations is not supported, except during the upgrade process.

7.2. Upgrading a Single XenServer Host Using the xe CLI

7.2.1. Before You Upgrade a Single XenServer Host

Before upgrading a standalone XenServer host, you will be required to either shut down or suspend any VMs running on that host. It is important to eject and empty CD/DVD drives of any VMs that you plan to suspend. If you do not empty the CD/DVD drives, the suspended VMs may not be resumeable after upgrade.

27

Image 32
Contents Citrix XenServer 6.1.0 Installation Guide Trademarks Contents Using Scvmm and Scom with XenServer Boot From SAN Environments Benefits of Using XenServer Administering XenServerWelcome About This DocumentNew Features in XenServer XenServer EditionsXenServer Documentation Guest EnhancementsReferences XenServer Host System Requirements System RequirementsSystem Requirements XenCenter System Requirements Supported Guest Operating SystemsInstalling XenServer and XenCenter Installation Media and MethodsInstalling the XenServer Host To install or upgrade the XenServer hostPage Host Partition Format Installing XenCenterTo install XenCenter Connecting XenCenter to the XenServer Host To connect XenCenter to the XenServer hostInstallation and Deployment Scenarios High-level procedureXenServer Hosts with Local Storage Basic hardware requirementsPools of XenServer Hosts with Shared Storage XenServer Hosts with Shared NFS StorageConfiguring your iSCSI storage XenServer Hosts with Shared iSCSI StorageConfiguring an iSCSI IQN for each XenServer host Xe pool-param-set uuid=pooluuid default-SR=iscsisharedsruuid IntelliCache Deployment Enabling on Host InstallationXenServer and IntelliCache To enable local caching, enter the following commands Converting an Existing Host to Use Thin ProvisioningVM Boot Behavior Implementation Details and TroubleshootingXe sr-list params=local-cache-sr,uuid,name-label Integration Requirements for Scvmm Using Scvmm and Scom with XenServerHow to install the Integration Suite Supplemental Pack Integration Requirements for Scom Rolling Pool Upgrades Upgrading XenServerPage Before You Upgrade To upgrade a pool of XenServer hosts using the xe CLI Upgrading XenServer Hosts Using the xe CLIBefore you begin your rolling pool upgrade Upgrading a Single XenServer Host Using the xe CLI Before You Upgrade a Single XenServer HostTo upgrade a single XenServer host using the xe CLI Upgrading a Single XenServer Host Using the xe CLITo empty the CD/DVD drive of a VM using the xe CLI Page Upgrading LVM-based SRs using the xe CLI Upgrading LVM Storage from XenServer 5.0 or EarlierBefore you begin updating Applying Updates and Hotfixes to XenServerBefore You Apply an Update or Hotfix Updating Individual XenServer Hosts To update individual hosts using XenCenterTo update individual hosts using the xe CLI To update a pool of hosts using XenCenter Updating a Pool of XenServer HostsTo update a pool of XenServer hosts using the xe CLI To activate a free XenServer product Licensing XenServerActivating a Free XenServer Product Licensing XenServer Editions To license XenServer Advanced editions and higherAdditional Licensing Information To configure licensing for XenServer hosts using XenCenterTo configure licensing for XenServer hosts using the xe CLI Grace Period Appendix A. Troubleshooting To capture and save the log fileAppendix B. Boot From SAN Environments To configure your Tftp server Appendix C. PXE Boot InstallationsConfiguring your PXE Environment for XenServer Installation Creating an answer file for unattended PXE installation Preparing the destination systemElement Description Required? Element Description Required? Element Proto dhcp or static