vSphere 5.1 U1 מה תוקן #1 – vCenter

עברתי על Resolved Issues של vSphere 5.1 U1 ולהלן כמה מתוכם שנתקלתי בהם וחיכיתי לפתרון או שנראים לי רלוונטיים. בגלל שיש לא מעט דברים, חילקתי את הרשימה לכמה פוסטים. בפוסט הראשון אתמקד ב-vCenter:

Unable to add ESXi 5.1 hosts to existing vSphere Distributed Switch versions 4.0, 4.1, and 5.0 in vCenter Server 5.1 with compatibility issue
When you upgrade from vCenter Server 4.0, 4.1, or 5.0 to vCenter Server 5.1, adding ESXi 5.1 hosts to the existing vSphere Distributed Switch (vDS) versions 4.0, 4.1, and 5.0 might fail. However, if you create new vDS switch versions 4.0, 4.1, 5.0 or 5.1 after upgrading to vCenter Server 5.1, you will be able to add ESXi 5.1 hosts.

This issue is resolved in this release.

Note:

  • This fix resolves the issue when you upgrade from vCenter Server 4.0, 4.1 and 5.0 to vCenter Server 5.1 Update 1. This fix will not solve the issue if you have already upgraded from vCenter Server 4.0, 4.1 or 5.0 to vCenter Server 5.1 GA or 5.1 Patches and then upgraded to vCenter Server 5.1 Update 1. In which case, you can contact VMware Technical Support for the workaround.
  • This fix resolves the issue for VMware vSphere Distributed Switch (vDS) switches only.

Host profile compliance check displays that ESX/ESXi hosts are compliant even when their physical NIC configuration does not match the policy in attached host profile
If the policy for the physical NIC configuration in host profile is set to Fixed physical NIC configuration, and the ESX/ESXi host's physical NIC is auto negotiating at the same speed as that specified in this policy, then host profile compliance check reports the host as compliant instead of non-compliant.

This issue is resolved in this release.

Single Sign On (SSO)  upgrade from vCenter Server 5.1 0a to vCenter Server 5.1 0b does not replace the sspiservice.exe and  rsautil.cmd files
After you upgrade SSO from vCenter Server 5.1 0a to vCenter Server 5.1 0b, the sspiservice.exe and rsautil.cmd files are not replaced. When you run the rsautil -v command, the resulting version number is of  vCenter Server 5.1 0a.

This issue is resolved in this release.

Unable to edit the settings of a virtual machine that is a member of a datastore cluster
In vCenter Server, you cannot edit the settings of a virtual machine that is a member of a datastore cluster by using a user account that does not have the permission to configure a datastore cluster in vCenter Server but has full permissions at the virtual machine level. The following error message is displayed:
Permission to perform this operation was denied.
You do not hold privilege "Datastore cluster > Configure a datastore cluster on Datastore cluster Cluster Name"

This issue is resolved in this release.

vCenter Server incorrectly reports hosts are connected to the HA Master in vSphere HA Cluster Status when the hosts are not part of the HA host list
During host failures or reboots, virtual machines might not failover because the host it resides on is not part of the HA host list. Even vSphere HA Cluster Status show the host is connected to the HA Master.

This issue is resolved in this release. vSphere HA Cluster Status now reports accurate information about host connection state. Also, HA Host Status alarm is enhanced to alert users when a host loses it's Management Traffic enabled network interface. Note that the HA Host Status alarm update only applies to fresh vCenter installation. For upgrade scenarios, users have to update the HA Host Status alarm manually by adding Host has no port groups enabled for vSphere HA event to the list of triggers and assign Alert as the status.

Unable to see CPU, memory, disk metrics on the cluster view in the performance chart
The CPU, memory, disk, and network metrics are absent from the cluster view under the performance option of the Advanced tab in vSphere Client.

This issue is resolved in this release.

vSphere Web Client incorrectly displays WWNN and WWPN values for Fibre Channel storage adapters
When you use the vSphere Web Client to review Fibre Channel adapter characteristics, the Properties tab might display incorrect values for node World Wide Name (WWNN) and port World Wide Name (WWPN). The last two digits of the WWNN and WWPN might be missing.

This issue is resolved in this release.

vCenter Server 5.1 service fails to start after you restart the server
The vCenter Server service fails to start if the Single Sign On service cannot connect to the database. This occurs when the Single Sign On service starts before the database service.

This issue is resolved in this release.

vCenter Server 5.1 virtual machines might display a red warning icon in the inventory
In vCenter Server 5.1, some virtual machines might display a red warning icon in the inventory. However, the Alarms tab for the virtual machine does not indicate that any alarm was triggered. This icon might appear for powered on and powered off virtual machine

This issue is resolved in this release.

Performance history for past year might contain only 30 days of information in vSphere 5.1
When you attempt to view the vSphere performance history for past year in the past year view tab, you can see only one month of performance history.

This issue is resolved in this release

Message related to HA initiated failover of virtual machine remains in Summary tab of cluster
After failover action is completed, the vSphere HA initiated a virtual machine failover action in cluster xx in datacenter xx message remains in the Summary tab of the cluster.

This issue is resolved in this release.

vSphere 5.1 Web Client advanced performance charts are slow to display
In the vCenter 5.1 web client, the advanced performance charts takes several minutes to load.

This issue is resolved in this release.

vCenter Server Service status displays a warning message related to performance statistics rollup
vCenter Server service status might display the following warning message related to performance statistics rollup:
Performance Statistics rollup from Past xxx to Past xxx is not occurring in the database

This issue occurs if the statistics collection for one or more interval duration is disabled in vCenter Server settings. In this case, the warning is triggered when the rollup status checks jobs run for the disabled interval duration, but do not report a valid result.

This issue is resolved in this release.

Virtual Machine snapshot size (GB) and VM Total Size on Disk (GB) alarms are triggered incorrectly
In vCenter Server 5.1 you can configure the vCenter Server to send alarms when virtual machine size on disk exceeds a limit or when virtual machine snapshot size exceeds a limit. These alarms are falsely triggered when the virtual machine size or snapshot size are within the set limits. The alarm for virtual machine snapshot size might even be triggered when no snapshot exists.

This issue is resolved in this release

Cloning a virtual machine through vSphere Client or vSphere Web Client causes the resulting virtual machine to have its disk pointing back to the source virtual machines disk
In vCenter Server, when you clone a virtual machine through vSphere Client or vSphere Web Client, you have the option to edit the hardware of the destination virtual machine. If you choose to edit a disk and adjust its size, the disk of the resulting virtual machine points back to the source virtual machine disk. This results in the destination virtual machine using the source virtual machine disk.

This issue is resolved in this release.

vSphere Client stops responding when virtual machines are hidden from view
After you select the option to hide virtual machines from view in vCenter Server 5.1, the vSphere client stops responding in the following situations:

  • When you perform a search using the search box at the top right, and click a link in the search box.
  • After selecting a host in the Hosts and Clusters view, when you select the Virtual Machines tab and double-click on any virtual machine in the list.
  • When you select the Virtual Machines tab in the VM and Templates view and double-click any virtual machine in the list.

This issue is resolved in this release.

Virtual machines incorrectly shown as being managed by VMware vCenter Site Recovery Manager
After a failover from production site (A) to recovery (B), the virtual machines at the new production site (B) might shown as being managed by VMware vCenter Site Recovery Manager in the Summary tab.

This issue is resolved in this release.

Virtual machines are unable to connect to the network after reverting to a snapshot
In vCenter Server, when a snapshot is reverted and virtual machine is powered on, Connect At Power On is selected on the network adapter but Connected is deselected. If you select the Connected check box an error similar to the following is displayed:

Invalid Configuration for device 0.

This issue is resolved in this release.

Unable to vMotion virtual machines between hosts if virtual machine is connected to a vDS without any uplinks
In vCenter Server, you might not be able to to vMotion virtual machines between hosts if virtual machine is connected to a host with no uplinks on the vDS and the destination host also doesn't have ay uplinks on that same vDS. This issue occurs because vCenter Server disallows the vMotion operation, so that virtual machines do not lose network connectivity when the destination host does not have any uplinks.

This issue is resolved in this release. If a virtual machine is already on a host that doesn't have uplinks, vCenter Server allows vMotion.

vSphere 5 Storage vMotion is unable to rename virtual machine files on completing migration
In vCenter Server , when you rename a virtual machine in the vSphere Client, the VMDK disks are not renamed following a successful Storage vMotion task. When you perform a Storage vMotion task for the virtual machine to have its folder and associated files renamed to match the new name, the virtual machine folder name changes, but the virtual machine file names do not change.

This issue is resolved in this release. To enable this renaming feature, you need to configure the advanced settings in vCenter Server and set the value of the provisioning.relocate.enableRename parameter to true.

User is unable to unmount or remove a datastore in a High Availability cluster
When you attempt to unmount a datastore from an HA cluster which is being used for datastore heartbeat or data persistence operation, failure to quiesce the I/O fails with the following error message:

Failed to quiesce file activity on datastore by HA

This issue is resolved in this release.

מיכאל.

כתיבת תגובה

האימייל לא יוצג באתר. שדות החובה מסומנים *

*