Mar 14

Enhanced LACP Support in vSphere Distributed Switches

Principal Engineer Ravi Soundararajan explains the concepts behind the Enhanced LACP support in vSphere Distributed Switch 5.5.

Rating: 5/5


May 15

What’s New in VMware vSphere™ 5.0 Networking

Introduction

With the release of VMware vSphere™ 5.0 (“vSphere”), VMware brings a number of powerful new features and enhancements to the networking capabilities of the vSphere platform. These new network capabilities enable customers to run business-critical applications with confidence and provide the flexibility to enable customers to respond to business needs more rapidly. All the networking capabilities discussed in this document are available only with the VMware vSphere Distributed Switch (Distributed Switch).

There are two broad types of networking capabilities that are new or enhanced in the VMware vSphere 5.0
release. The first type improves the network administrator’s ability to monitor and troubleshoot virtual
infrastructure traffic by introducing features such as:

  • NetFlow
  • Port mirror

The second type focuses on enhancements to the network I/O control (NIOC) capability first released in
vSphere 4.1. These NIOC enhancements target the management of I/O resources in consolidated I/O
environments with 10GB network interface cards. The enhancements to NIOC enable customers to provide
end-to-end quality of service (QoS) through allocating I/O shares for user-defined traffic types as well as tagging packets for prioritization by external network infrastructure. The following are the key NIOC
enhancements:

  • User-defned resource pool
  • vSphere replication trafc type
  • IEEE 802.1p tagging

The following sections will provide higher-level details on new and enhanced networking capabilities in vSphere 5.0.

Network Monitoring and Troubleshooting

In a vSphere 5.0 environment, virtual network switches provide connectivity for virtual machines running on VMware® ESXi™ hosts to communicate with each other as well as connectivity to the external physical
infrastructure. Network administrators want more visibility into this traffic that is flowing in the virtual infrastructure. This visibility will help them monitor and troubleshoot network issues. VMware vSphere 5.0 introduces two new features in the Distributed Switch that provide the required monitoring and troubleshooting capability to the virtual infrastructure.

NetFlow

NetFlow is a networking protocol that collects IP traffic information as records and sends them to a collector such as CA NetQoS for traffic flow analysis. VMware vSphere 5.0 supports NetFlow v5, which is the most common version supported by network devices. NetFlow capability in the vSphere 5.0 platform provides visibility into virtual infrastructure traffic that includes:

  • Intrahost virtual machine traffic (virtual machine–to–virtual machine traffic on the same host)
  • Interhost virtual machine traffic (virtual machine–to–virtual machine traffic on different hosts)
  • Virtual machine–physical infrastructure traffic

Figure 1 shows a Distributed Switch configured to send NetFlow records to a collector that is connected to an external network switch. The blue dotted line with arrow indicates the NetFlow session that is established to send flow records for the collector to analyze.

NetFlow Traffic

Figure 1. NetFlow Traffic

Usage

NetFlow capability on a Distributed Switch along with a NetFlow collector tool helps monitor application flows and measures flow performance over time. It also helps in capacity planning and ensuring that I/O resources are utilized properly by different applications, based on their needs.

IT administrators who want to monitor the performance of application flows running in the virtualized
environment can enable flow monitoring on a Distributed Switch.

Configuration

NetFlow on Distributed Switches can be enabled at the port group level, at an individual port level or at the uplink level. When configuring NetFlow at the port level, administrators should select the NetFlow override tab, which will make sure that flows are monitored even if the port group–level NetFlow is disabled.

Port Mirror

Port mirroring is the capability on a network switch to send a copy of network packets seen on a switch port to a network monitoring device connected to another switch port. Port mirroring is also referred to as Switch Port Analyzer (SPAN) on Cisco switches. In VMware vSphere 5.0, a Distributed Switch provides a similar port mirroring capability to that available on a physical network switch. After a port mirror session is configured with a destination—a virtual machine, a vmknic or an uplink port—the Distributed Switch copies packets to the destination. Port mirroring provides visibility into:

  • Intrahost virtual machine traffic (virtual machine–to–virtual machine traffic on the same host)
  • Interhost virtual machine traffic (virtual machine–to–virtual machine traffic on different hosts)

Figure 2 shows different types of traffic flows that can be monitored when a virtual machine on a host acts as a destination or monitoring device. All traffic shown by the orange dotted line with arrow is mirrored traffic that is sent to the destination virtual machine.

NetFlow Traffic

Figure 2. Port Mirror Traffic Flows When Destination Where Packets Are Mirrored Is a Virtual Machine

Usage

The port mirroring capability on a Distributed Switch is a valuable tool that helps network administrators in debugging network issues in a virtual infrastructure. The granular control over monitoring ingress, egress or all trafc of a port helps administrators fne-tune what trafc is sent for analysis.

Configuration

Port mirror configuration can be done at the Distributed Switch level, where a network administrator can create a port mirror session by identifying the traffic source that needs monitoring and the traffic destination where the traffic will be mirrored. The traffic source can be any port with ingress, egress or all traffic selected. The traffic destination can be any virtual machine, vmknic or uplink port.

Download

Download a full What’s New in VMware vSphere™ 5.0 Networking Technical White Paper.

Rating: 5/5


May 11

End of General Support for vSphere 5.0 and vSphere 5.1 (KB: 2145103)

Purpose

This article provides information on the End of Support Life for vSphere 5.0 and vSphere 5.1, which includes vSphere Hypervisor ESXi 5.0 and 5.1 and vCenter Server 5.0 and 5.1 respectively.

Resolution

The End of General Support for vSphere 5.0 and vSphere 5.1 is August 24, 2016. To maintain your full level of support and subscription, you will need to upgrade to a supported version of vSphere. For more information on the benefits of upgrading and how to upgrade, visit the VMware vSphere Upgrade Center.

If you would like assistance in moving to a newer version of vSphere, VMware’s vSphere Upgrade Service is available. This service delivers a comprehensive guide to upgrading your virtual infrastructure. It includes recommendations for planning and testing the upgrade, the actual upgrade itself, validation guidance and rollback procedures. For more information contact your Technical Account Manager or visit VMware Professional Services.

In the event you are unable to upgrade before the End of General Support (EOGS) and are active on Support and Subscription, you have the option to purchase extended support in one year increments for up to two years beyond the EOGS date. The price of Extended Support is $300,000 per product per year. Visit VMware Extended Support for more information.

Technical Guidance is available until August 24, 2018 primarily through the self-help portal. During the Technical Guidance phase, VMware does not offer new hardware support, server/client/guest OS updates, new security patches or bug fixes unless otherwise noted. For more information, visit VMware Lifecycle Support Phases.

Related Education

http://www.vmware.com/support.html
http://www.vmware360.com/files/pdf/products/vsphere/Product-Lifecycle-Matrix.pdf
http://www.vmware.com/consulting/
http://www.vmware360.com/files/pdf/products/vsphere/extended_support.pdf

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Download

Download a full VMware Technical Support Welcome Guide.

Rating: 5/5


May 06

Upgrading to vCenter Server 5.1 best practices (2021193)

Purpose

This article provides information about upgrading to vCenter Server 5.1

Notes:

  • This article assumes that you have read the vSphere Upgrade Guide. This guide contains definitive information. If there is a discrepancy between the guide and this article, assume that the guide is correct.
  • Because each environment is different, many upgrade decisions require knowledge and understanding beyond the scope of this article. For more detailed information about your installation, see the vSphere Upgrade Guide.
  • Review the VMware vSphere 5.1 Release Notes for known issues or special installation notes.

Resolution

Rating: 5/5

vCenter Single Sign-On
vSphere 5.1 introduces the vCenter Single Sign On service as part of the vCenter Server management infrastructure. This change affects vCenter Server installation, upgrading, and operation.

Authentication by vCenter Single Sign On makes the VMware cloud infrastructure platform more secure by allowing the vSphere software components to communicate with each other through a secure token exchange mechanism, instead of requiring each component to authenticate a user separately with a directory service like Active Directory.

When you upgrade to vCenter Server 5.1, the upgrade process installs vCenter Single Sign On first, then upgrades vCenter Server.

For more information on the affects of vCenter Single Sign on vCenter Server installation and upgrades, see: Comparing behaviour of vCenter Single Sign On with earlier versions of vCenter Server (2032135).
For information about configuring vCenter Single Sign On, see the vSphere Security Guide.

Hardware Requirements for vCenter Server, vCenter Single Sign On, and Inventory Service

The vCenter Server system can be a physical machine or virtual machine with access to a supported database. The vCenter Server system (vCenter Server, vCenter Single Sign On, and Inventory Service) must meet the following hardware requirements.

Note these points before upgrading:

  • VMware supports in-place upgrades on 64-bit systems from vCenter Server 4.x and vCenter Server 5.0.x to vCenter Server 5.1.

  • vCenter Server 5.1 does not support directly migrating an existing vCenter Server to a new machine during an upgrade to 5.1.
    You can migrate an existing vCenter Server to a new machine during an upgrade to version 5.0, then perform an in-place upgrade from version 5.0 to version 5.1. See Upgrading to vCenter Server on a Different Machine in the vSphere Upgrade Guide.

  • vCenter Server 5.1 can manage ESX/ESXi 4.x and ESXi 5.0.x hosts in the same cluster with ESXi 5.1 hosts. vCenter Server 5.1 cannot manage ESX 2.x or 3.x hosts.

  • vSphere 5.1 introduces the vCenter Single Sign On service as part of the vCenter Server management infrastructure. For more information, see Comparing behaviour of vCenter Single Sign On with earlier versions of vCenter Server (2032135)

  • When you upgrade to vCenter Server 5.1, the upgrade process installs vCenter Single Sign On first, then upgrades vCenter Server. You must install or update these components in this order: vCenter Single Sign On, Inventory Service, and vCenter Server.

  • Create a vCenter Single Sign On database, unless you plan to install the bundled database. For further information, see Methods of Upgrading to vCenter Server 5.1 (2021188).
  • In upgrades to vCenter Server versions earlier than vCenter Server 5.1, both the local operating system users and Active Directory users that are registered with vCenter Server before the upgrade continue to work with the upgraded vCenter Server. This behavior changes in vCenter Server 5.1

    Note: In vCenter Server 5.1, if vCenter Single Sign On is running on a virtual machine or physical machine that is in the same domain as Active Directory, Single Sign On will automatically discover the existing Active Directory domain and join it automatically during the Single Sign On installation process. If Single Sign On is not running on a virtual machine or physical machine that is in the same domain as Active Directory, you must use the vSphere Web Client to log in to vCenter Server and add the Active Directory domain to Single Sign On. For further information, see Comparing behaviour of vCenter Single Sign On with earlier versions of vCenter Server (2032135).

vCenter Single Sign On, Inventory Service and vCenter Server hardware requirements

vCenter Single Sign On, Inventory Service and vCenter Server can be installed on the same host machine (as with vCenter Server Simple Install) or on different machines.
 
Minimum Hardware Requirements for vCenter Single Sign On, Running on a Separate Host Machine from vCenter Server lists the hardware requirements for vCenter Single Sign On, assuming that Single Sign On runs on a different host machine from vCenter Server. If vCenter Server and vCenter Single Sign On are installed on the same host machine, the Single Sign On memory and disk storage requirements are in addition to the requirements for vCenter Server. See Minimum Hardware Requirements for vCenter Server.

Minimum Hardware Requirements for vCenter Single Sign On, Running on a Separate Host Machine from vCenter Server

vCenter Single Sign On Hardware Requirement
Processor Intel or AMD x64 processor with two or more logical cores, each with a speed of 2GHz
Memory 3GB.

Memory requirements might be higher if the vCenter Single Sign On database runs on the same host machine. If vCenter Single Sign On runs on the same host machine as vCenter Server, see Minimum Hardware Requirements for vCenter Server.

Disk Storage 2GB. Disk requirements might be higher if the vCenter Single Sign On database runs on the same host machine.
Network Speed 1Gbps

Minimum Hardware Requirements for vCenter Inventory Service, Running on a Separate Host Machine from vCenter Server

Hardware Requirement
Processor Intel or AMD x64 processor with two or more logical cores, each with a speed of 2GHz.
Memory 3GB. If vCenter Inventory Service runs on the same host machine as vCenter Server, see Minimum Hardware Requirements for vCenter Server.
Disk Storage At least 60GB for medium- to large-sized inventories (more than 100 hosts or 1000 virtual machines).

If vCenter Inventory Service runs on the same host machine as vCenter Server, see Minimum Hardware Requirements for vCenter Server.

Network Speed 1Gbps

Minimum Hardware Requirements for vCenter Server

Hardware Requirement
CPU Two 64-bit CPUs or one 64-bit dual-core processor.
Processor 2.0GHz or faster Intel 64 or AMD 64 processor. The Itanium (IA64) processor is not supported. Processor requirements might be higher if the database runs on the same machine.
Memory The amount of memory needed depends on your vCenter Server configuration.

  • If vCenter Server is installed on a different host machine than vCenter Single Sign On and vCenter Inventory Service, 4GB of RAM are required.
  • If vCenter Server, vCenter Single Sign On and vCenter Inventory Service are installed on the same host machine (as with vCenter Simple Install), 10GB of RAM are required.
Memory requirements might be higher if the vCenter Server database or vCenter Single Sign On database runs on the same machine as vCenter Server.

vCenter Server includes several Java services: VMware VirtualCenter Management Webservices (tc Server), Inventory Service, and Profile-Driven Storage Service.

 
When you install vCenter Server, you select the size of your vCenter Server inventory to allocate memory for these services. The inventory size determines the maximum JVM heap settings for the services. You can adjust this setting after installation if the number of hosts in your environment changes. See the recommendations in JVM Heap Settings for vCenter Server.
Disk Storage The amount of disk storage needed depends on your vCenter Server configuration.

  • If vCenter Server is installed on a different host machine than vCenter Single Sign On and vCenter Inventory Service, 4GB of RAM are required.
  • If vCenter Server, vCenter Single Sign On and vCenter Inventory Service are installed on the same host machine (as with vCenter Simple Install), at least 40-60GB of free disk space are required after installation, depending on the size of your inventory. 100GB are recommended, to allow for future growth of your inventory.

Disk storage requirements might be higher if the vCenter Server database or vCenter Single Sign On database runs on the same machine as vCenter Server.

In vCenter Server 5.x, the default size for vCenter Server logs is 450MB larger than in vCenter Server 4.x. Make sure the disk space allotted to the log folder is sufficient for this increase.

Microsoft SQL Server 2008 R2 Express disk Up to 2GB free disk space to decompress the installation archive. Approximately 1.5GB of these files are deleted after the installation is complete.
Network Speed 1Gbps

JVM Heap Settings for vCenter Server

vCenter Server Inventory VMware VirtualCenter Management Webservices Inventory Service Profile-Driven Storage Service
Small inventory (1-100 hosts or 1-1000 virtual machines) 1GB 3GB 512MB
Medium inventory (100-400 hosts or 1000-4000 virtual machines) 2GB 6GB 1GB
Large inventory (More than 400 hosts or 4000 virtual machines) 3GB 12GB 2GB

vCenter Server operating system requirements

vCenter Server 5.1 requires a 64-bit operating system and cannot be installed on a 32-bit operating system. When performing an install you must ensure that your operating system is 64-bit capable. For a list of supported operating systems, see the VMware Compatibility Guide.

VMware recommends that vCenter Server be installed on a system that is dedicated to managing your virtual infrastructure environment. 3rd party and other applications on the same system may utilize the same shared system resources, impacting performance and support.

Pre-upgrade software requirements

vCenter Server requires Microsoft .NET 3.5 SP1 Framework. If it is not installed on your system, the vCenter Server installer installs it for you.

Note: The Microsoft .NET 3.5 SP1 installation might require Internet connectivity to download and update files during the installation procedure.

If you plan to use the Microsoft SQL Server 2008 R2 Express database that is bundled with vCenter Server, Microsoft Windows Installer version 4.5 (MSI 4.5) must be installed on your system. You can download MSI 4.5 from the Microsoft Web site. You can also install MSI 4.5 directly from the vCenter Server 5.1 CD/DVD-ROM.

Network prerequisites

Verify that DNS reverse lookup returns a fully qualified domain name when queried with the IP address of the vCenter Server. When you upgrade vCenter Server, the installation of the web server component that supports the vSphere Client fails if the installer cannot look up the fully qualified domain name of the vCenter Server from its IP address. Reverse lookup is implemented using PTR records. To create a PTR record, see the documentation for your vCenter Server host operating system.

If you use DHCP instead of a manually assigned (static) IP address for vCenter Server, make sure that the vCenter Server computer name is updated in the domain name service (DNS). Test this is by pinging the computer name. For example, if the computer name is host-1.company.com, run this command in the Windows command prompt:

ping host-1.company.com

If you can ping the computer name, the name is updated in DNS.

Ensure that the ESXi host management interface has a valid DNS resolution from the vCenter Server and all vSphere Clients. Ensure that the vCenter Server has a valid DNS resolution from all ESXi hosts and all vSphere Clients.

For the vCenter Single Sign On installer to automatically discover Active Directory identity sources, verify that these conditions are met:

  • The Active Directory identity source must be able to authenticate the user who is logged in to perform the Single Sign On installation.

  • The DNS of the Single Sign On Server host machine must contain both lookup and reverse lookup entries for the domain controller of the Active Directory. For example, pinging mydomain.com should return the domain controller IP address for mydomain. Similarly, the ping -a command for that IP address should return the domain controller hostname. Avoid trying to correct name resolution issues by editing the hosts file. Instead, make sure that the DNS server is correctly set up.

  • The system clock of the Single Sign On Server host machine must be synchronized with the clock of the domain controller.

 

Ensuring that your database is ready to be installed/upgraded

Make sure your database requirements and patch levels are compliant. For more information, see VMware Product Interoperability Matrixes and vCenter Server Database Configuration Notes in the vSphere 5.1 Documentation Center for the most up to date list of database versions supported with vCenter Server. See also Supported Database Upgrades in the vSphere 5.1 Documentation Center.

If you are performing an upgrade, configuration and per-requirements may have already have been done with a previous installation of vCenter Server. Contact your DBA if you are unsure if these procedures have been completed.

vCenter Server databases require a UTF code set.

The vCenter Server system must have a 64-bit DSN. This requirement applies to all supported databases. You also need to ensure that you have created a full backup of your database before proceeding with the vCenter Upgrade.

Notes:

  • Microsoft SQL Server 2008 R2 Express is intended for use with small deployments of up to 5 hosts or 50 virtual machines.
  • IBM DB2 database is only supported for vCenter Server. There is no support for IBM DB2 with Update Manager or with any plug-in that requires a database.
If your database is located on the same machine on which vCenter Server will be installed, and you have recently changed the name of this machine to comply with the name-length requirement, make sure the vCenter Server DSN is configured to communicate with the new name of the machine.

Changing the vCenter Server computer name impacts database communication if the database server is on the same computer with vCenter Server. If you changed the machine name, you can verify that communication remains intact. The name change has no effect on communication with remote databases. You can skip this procedure if your database is remote.

Note: The name-length limitation applies to the vCenter Server system. The data source name (DSN) and remote database systems can have names with more than 15 characters.

Check with your database administrator or the database vendor to make sure all components of the database are working after you rename the server.


When configuring vCenter Server to communicate with a database, make sure that:
  • The database server is running

  • The vCenter Server computer name is updated in the domain name service (DNS). To test the connection, ping the computer name. For example, if the computer name is host-1.company.com, run this command in a Windows command prompt:

    ping host-1.company.com

    If you can ping the computer name, the name is updated in DNS.

Note: For further recommendations on preparing your vCenter Server Database, see Preparing for the Upgrade to vCenter Server in the vSphere Upgrade Guide.

Bundled Microsoft SQL Server 2008 R2 SP1 Express Database Package

The bundled Microsoft SQL Server 2008 R2 Express database package is installed and configured when you select the bundled database during vCenter Server installation or upgrade.

To install the bundled Microsoft SQL Server 2008 R2 Express database, Microsoft Windows Installer version 4.5 (MSI 4.5) is required on your system. You can download MSI 4.5 from the Microsoft Web site. You can also install MSI 4.5 directly from the vCenter Server autorun.exe installer.

Pre-upgrade considerations and recommendations

Before upgrading, consider these points:

  • Prepare for the vCenter Server installation by recording the values that the vCenter Server system requires. For further information, see Required Information for Installing or Upgrading vCenter Single Sign On, Inventory Service, and vCenter Server in the vSphere Upgrade Guide.

  • If you do not intend to use evaluation mode, make sure that you have valid license keys for all purchased functionality. License keys from vSphere versions prior to version 5.0 are not supported in vCenter Server 5.x. If you do not have the license key, you can install in evaluation mode and use the vSphere Client or vSphere Web Client to enter the license key later.

  • Close all instances of the VMware Infrastructure Client, the vSphere Client, and the vSphere Web Client.

  • Before you install or upgrade any vSphere product, synchronize the clocks of all machines on the vSphere network. See Synchronizing Clocks on the vSphere Network in the vSphere Upgrade Guide.

  • In-place upgrade to vCenter Server 5.1 is not supported on Microsoft Windows XP.

  • Ensure that your vCenter Server 5.1 is capable of running on a 64-bit operating system.

  • Ensure that you have made a backup of your vCenter Server database.

  • If the vCenter Server upgrade fails, no automatic rollback occurs to the previous vCenter Server version.

  • The data migration tool is not supported for vCenter Server 5.1. You cannot directly migrate an existing vCenter Server to a new machine during an upgrade to version 5.1. You can migrate an existing vCenter Server to a new machine during an upgrade to version 5.0, and then perform an in-place upgrade from version 5.0 to version 5.1.

  •  Ensure that NetBios over TCP/IP is enabled in TCP/IP v4 settings on the Windows server.

  • Ensure that all domains that are to be added as Identity sources are added to the DNS suffix list of the NIC. 

Additional Information

 

May 06

Methods of upgrading to vCenter Server 5.1 (2021188)

Purpose

This article provides high-level information about the methods of upgrading to vCenter Server 5.1. 
 

Note:

Resolution

Before upgrading to vCenter Server 5.1, vSphere 5.1 requires you to install vCenter Single Sign On and install or upgrade the Inventory Service. You can install vCenter Single Sign On and upgrade the Inventory Service and vCenter Server all on a single host machine using the vCenter Server Simple Install option. This option is appropriate for small deployments.

Alternatively, you can install vCenter Single Sign On, upgrade the Inventory Service, and upgrade vCenter Server separately to customize the location and configuration of the components. See the Installing components separately

 
For more information vCenter Single Sign On, see:

Prerequisites

Before upgrading, you need to create a vCenter Single Sign On database, unless you plan to install the bundled database. For information about vCenter Single Sign On supported database versions, see the VMware Product Interoperability Matrix.

If you are using an existing database for vCenter Single Sign On:

  • You have the option of specifying a database user (RSA_USER) and database administrator (RSA_DBA) to use for Single Sign On database installation and setup. See Required vCenter Single Sign On Database Users in the vSphere Upgrade Guide.
    • If you choose this option, create these users before you run the installer. See Required vCenter Single Sign On Database Users in the vSphere Upgrade Guide for a list of required permissions.
    • If you do not choose this option, the installer creates these users for you using the credentials of a database administrator you specify during the installation process. Verify that the database user you specify has the required permissions. See Permissions Required by vCenter Single Sign On for Database Administrators in the vSphere Upgrade Guide.
  • Ensure that the tablespaces are named RSA_DATA and RSA_INDEX. Any other table space names cause the vCenter Single Sign On installation to fail.
  • Ensure that table space is created for the database. Run the script:

    rsaIMSLite<DBName>SetupTablespaces.sql

    Note: The script is included in the vCenter Server installer download package (vCenter Server Installation directory\Single Sign On\DBScripts\SSOServer\Schema\your_existing_database ). You can run this script prior to the installation, or during the installation of Single Sign On, when you are prompted by the installer. You can leave the installer to run the script, and resume the installer after you run the script.

  • If you do not choose this option, the installer creates these users for you using the credentials of a database administrator you specify during the installation process. Verify that the database user you specify has the required permissions. See Permissions Required by vCenter Single Sign On for Database Administrators in the vSphere Upgrade Guide.

Note: For information on vCenter Single Sign On, vCenter Inventory Service, and vCenter Server install prerequisites, hardware and software requirements, see Upgrading to vCenter Server 5.1 best practices (2021193)

Installing components on one host using Simple Install

To install vCenter Single Sign On and upgrade the Inventory Service and vCenter Server all on a single host machine using the vCenter Server Simple Install option:

  1. Install vCenter Single Sign On as Part of a vCenter Server Simple Install. Create the only node in a basic vCenter Single Sign On installation, or the first node in a high availability or multisite installation.
  2. Install or Upgrade Inventory Service as Part of vCenter Server Simple Install.

    Note: The Inventory Service stores vCenter Server application and inventory data, enabling you to search and access inventory objects across linked vCenter Servers.

    You can install vCenter Single Sign On, vCenter Inventory Service, and vCenter Server together on a single host machine using the vCenter Server Simple Install option. This option is appropriate for small deployments.

  3. Upgrade to vCenter Server 5.1 as Part of a Simple Install.

    Notes:

    • You can upgrade vCenter Server as part of a Simple Install after installing vCenter Single Sign On, and upgrading the Inventory Service. Alternatively, you can install vCenter Single Sign On, upgrade Inventory Service, and upgrade vCenter Server separately to customize the location and configuration of the components. See Install vCenter Single Sign On, Upgrade Inventory Service, and Upgrade vCenter Server Separately. See the below section for further details.
    • You can use Simple Install to upgrade vCenter Server if you have a version 4.x or 5.0.x vCenter Server installation that is supported for upgrade. See vCenter Server Upgrade Summary. In this case, the Simple Install option installs Single Sign-On, upgrades Inventory Service, and upgrades vCenter Server.
    • If you are upgrading a version 5.1 vCenter Server installation to version 5.1.x, you cannot use Simple Install. Upgrade the Single Sign-On, Inventory Service, and vCenter Server components separately. See Separately Install vCenter Single Sign On, Upgrade Inventory Service, and Upgrade vCenter Server.
    • If an earlier version of vCenter Server is on your machine, the vCenter Server installer detects and upgrades it. If the upgrade fails, no automatic rollback occurs to the previous vCenter Server version.

For more information on the Single Sign On install and vCenter Server upgrade option, see the vSphere Upgrade Guide.

Installing components separately

To install vCenter Single Sign On, install/upgrade the Inventory Service, and upgrade vCenter Server separately to customize the location and configuration of the components:

  1. Install vCenter Single Sign On as a New Installation. Create the only node in a basic vCenter Single Sign On installation, or the first node in a high availability or multisite installation.

    Or

    Install an Additional Node for an Existing vCenter Single Sign On Installation. Create an additional vCenter Single Sign On node for an existing high availability or multisite vCenter Single Sign On installation.

  2. Install or upgrade vCenter Inventory Service in a Separate Installation.

    Note: The Inventory Service stores vCenter Server application and inventory data, enabling you to search and access inventory objects across linked vCenter Servers.

  3. Upgrade vCenter Server in a Separate Upgrade.

Note: For more information about the Single Sign On install and vCenter Server upgrade option, see the vSphere Upgrade Guide.

Updating vCenter Server and its Components

VMware provides updates for vCenter Server 5.1 software.

vCenter Server components  can include updates to vCenter Server, Inventory Service, vCenter Single Sign On, and Profile-Driven Storage Service.

vCenter Server 5.1 updates s are available from www.vmware.com. The service pack update process updates files and registry settings required by vCenter Server and restarts Windows services that are stopped during the update.

For more information, see the Updating vCenter Server with  Components section in the vSphere Upgrade Guide.

See Also