VMware VSphere 5.5 Update 2

VMware vSphere 5.5 Update 2

VMware VSphere 5.5 Update 2 was released in September 2014 for some time now, and the new version adds new features that fix many bugs in previous releases and run more stably. Now upgrade the virtualization system to the latest version of St.

One, the current version

At present, the St virtualization system uses a version of 5.5.0, there are some problems, such as: ESXi host may experience a longer I/O latency, vCenter Server may display the status of the power information as unknown, when the uplink instability, ESXi host may be faulted, and display purple screen and so on.

Second, VMware vSphere 5.5 Update 2 new features (i) VCenter Server database support

VCenter Server now supports the following external databases :
Oracle 12c

Microsoft SQL Server Service Pack 1

Microsoft SQL Server 2014

(ii) VCloud Hybrid Service:

The VCloud Hybrid Service (VCHS) introduces a new container, the Hybrid Cloud service, on the VSphere Web Client home page. The Hybrid Cloud Service container contains the Vchs installer and the new VCloud Connector Setup program.

(iii) Customer Experience Improvement Program:

The Vsphere Customer Experience Improvement Program was introduced to collect vsphere configuration data and transfer it to VMware for analysis on a weekly basis to help VMware understand usage and improve the product.

Iii. issues addressed by VMware VSphere 5.5 Update 2 (a) The issues addressed in the server configuration are:

1. You cannot connect to an NTP server when you configure multiple NTP servers through the VSphere Web Client

2. The host profile answer file may not be applied when the ESXi host is rebooted

3. The VMware vCenter Server Performance Chart incorrectly displays the Throughput.usage.average value

4. The Ethtool reported Emulex 10Gb Ethernet (10GbE) 554FLR-SFP Adapter cable type may be incorrect.

5. Client operation customizations may fail if the virtual machine is migrated due to DRS

6. Installing ESXi on an ISCSI remote LUN may fail

7. The virtual machine may experience slow I/O response issues

8. Unable to create a VMFS-5 data store larger than TB on the storage device

(ii) memory

Resolves an issue that could fail when performing multiple concurrent network file copy operations between two data stores.

(iii) issues addressed in the area of upgrading and installation are:

1. After upgrading from VCenter Server 4.x to 5.x, VSphere Web Client, hardware status, health status, and storage views do not function properly.

2. A command-line upgrade from VCenter Server 5.1 to 5.5 adds unnecessary steps to the [Past day statistics rollup] job.

(iv) The issues addressed by VCenter Server, vsphere client, and vsphere Web client are:

1. The VMware vCenter Server Service (vpxd.exe) may fail with a reboot and Win32 exception occurs.

2. When virtual Flash is enabled on the ESXi server, the VCenter Server service shuts down.

3. Unable to launch HTML console from VSphere Web Client.

4. Unable to change physical compatibility mode to virtual compatibility mode in VSphere Web Client

5. The option to force mounted data storage is not uninstalled via VSphere Web Client.

6. Attempts to unregister multiple virtual machines simultaneously in the vApp failed with a "managed object not found" exception.

7. You cannot set a higher value for the peak bandwidth and average bandwidth for traffic adjustment in the host configuration file.

8. VCenter Server Appliance has set the hostname error after deployment.

9. If disk space on the database server is exhausted, VCenter server may stop running.

10. If VMware Workstation is installed, a delay occurs when the virtual machine console is turned on.

11. If the VCenter single sign-on (SSO) password set for [email protected] contains an exclamation point (!), attempting to reregister the VSphere Web client with the Client-repoint.bat command may Failed.

12. When editing VSwitch settings, the VSphere Web Client displays incorrect vmnic groups and failover sequences.

13. When you copy/paste a Vmware Remote console URL from one browser to another, the next-generation client console is not loaded.

14. You cannot log in to VSphere Client using [email protected] During a domain connection outage.

15. The VCenter Server service may fail because SQL query execution fails.

16. Attempts to log on to VCenter Server 5.5 using VSphere Web Client failed with the following error: Internal error #1009 (an internal error had occurred-error #100 9).

17. You cannot use VSphere client to edit settings for a virtual machine with hardware version 10.

18, VCenter Server upload files too long

(v) Virtual machine management

Resolves an issue in which a message may be displayed indicating that the virtual machine may have been moved or copied when the template is converted to virtual machines.

(vi) The issues addressed by the VMotion and Storage vMotion are:

1. If a memory reservation is set on the virtual machine, attempting to migrate the virtual machine back to the original host via vMotion may fail.

2. Orphaned virtual machine disks are created when a vSphere Storage vMotion task is performed during a virtual machine backup

Iv. downtime during vcenter server Upgrade (i) The estimated downtime for vcenter server is as follows:

1. The upgrade requires VCenter Server to stop working for 40-50 minutes, depending on the size of the database. During this time, the database schema upgrade takes approximately 10-15 minutes. This is not expected to include upgraded host reconnection.

2. The VMware distributed Resource Scheduler will not work during the upgrade process. VMware HA can work during the upgrade process.

3. The Esx/esxi host managed by VCenter Server does not require downtime, and virtual machines running on the host do not need to be down-time.

V. Precautions (i) before upgrading vcenter server, back up the vcenter server database and the View Composer database. (ii) Before upgrading VCenter server, use the Vdmexport.exe utility to back up the view LDAP database from the View connection server instance. Vi. Upgrading vcenter Server5.5 Update2 (i) Upgrading vcenter single sign-on

1. If you upgrade vcenter single sign-on and vcenter Server, vcenter single sign-on will recognize the existing local operating system users. In addition, users [email protected] can log in to Vcenter single sign-on and vcenter Server as an administrator user.

2. VCenter single sign-on is the most common deployment mode that can meet the requirements of most VSphere 5.5 users. Typically, this deployment pattern maintains the same schema as the previous VCenter Server environment.

3, in most cases, you can use vcenter simple installation in basic mode to deploy Vcenter Server with vcenter single sign-on.

(ii) Upgrading Vcenter Server:

Verify the upgrade path from the current version of VCenter Server to the target version.

(iii) Upgrading vsphere Web Client:

Verify that vsphere Web client supports upgrading to the version of Vcenter Server Update 2.

(iv) Upgrading ESX and ESXi hosts:

Verify that the ESXi host supports upgrading to the version of Vcenter Server Update 2.

(v) Upgrading virtual machines and VMware Tools:

Upgrade virtual machine hardware, VMware Tools, and virtual appliances directly with update Manager, or you can patch and update third-party software that is running on virtual machines and virtual appliances.

VMware VSphere 5.5 Update 2