Saludos amigos, este mes está siendo movido respecto a Releases, Patch, etc. En esta entrada os quiero dejar lo más destacable a mi parecer de esta Release B de vSphere 6.0.
Normalemente se deja la Release x.0 estable con Updates como esta misma, c, d, f, etc. Para dar el salto final a x.1, supongo que para el VMworld de Barcelona veremos vSphere 6.1 con todos los cambios que hoy os presento más alguna funcionalidad adicional.
- Release notes de vCenter Server 6.0.0b disponibles aquí. Build Number: 2800571
- Descargar vCenter Server 6.0.0b aquí
Bugs corregidos destacados a nivel ESXi
- ESXi host might become unusable with no connectivity until reboot
When an ESXi host has three or more vmknics, if you reset network settings from DCUI or apply a Host Profile where the vmknics are on a DVS, including the management vmknic, a Hostctl exception might occur. This might cause the host to become unusable with no connectivity until it is rebooted. - ESXi host might lose network connectivity after enabling port mirroring sessions
An ESXi host or a virtual machine might lose network connectivity after you enable port mirroring sessions on the vSphere Distributed Switch.
- NTP package updated
The NTP package is updated to address a stability issue. - Windows 8 and Windows 2012 Server virtual machine reboot on an ESXi host might fail
Attempts to reboot Windows 8 and Windows 2012 Server virtual machine on an ESXi host might fail. For more information, see Knowledge Base article 2092807. - Attempts to create more than 16 TB of VMFS5 datastore on storage device fail
An ESXi host might fail when you attempt to expand a VMFS5 datastore beyond 16TB. - Overall ESXi utilization might decrease when you set the CPU limit of a single processor virtual machine
When you set the CPU limit of a single processor virtual machine, the overall ESXi utilization might decrease due to a defect in the ESXi scheduler. This happens when the ESXi scheduler is making incorrect CPU load balancing estimations, and considers virtual machines as running. For more details, see Knowledge Base article 2096897. -
Persistently mounted VMFS snapshot might not get mounted
Persistently mounted VMFS snapshot volumes might not get mounted after you reboot the ESXi host. Log messages similar to following are written to the syslog file:
localcli: Storage Info: Unable to Mount VMFS volume with UUID nnnnnnnn-nnnnnnnn-nnnn-nnnnnnnnnnnn.
Sysinfo error on operation returned status : Bad parameter count. Please see the VMkernel log for detailed error information
localcli: StorageInfo: Unable to restore one or more conflict-resolved VMFS volumes -
ESXi host might not receive SNMP v3 traps with third-party management tool
An ESXi host might not receive SNMP v3 traps when you are using a third-party management tool to collect SNMP data. Entries similar to the following are written to /var/snmp/syslog.log file:
snmpd: snmpd: snmp_main: rx packet size=151 from: 172.20.58.220:59313
snmpd: snmpd: SrParseV3SnmpMessage: authSnmpEngineBoots(0) same as 0, authSnmpEngineTime(2772) within 0 +- 150 not in time window
....
For further information, see Knowledge Base article 2108901. - Attempts to boot an ESXi 6.0 host from an iSCSI SAN might fail
Attempts to boot an ESXi 6.0 host from an iSCSI SAN might fail. This happens when the ESXi host is unable to detect the iSCSI Boot Firmware Table (iBFT), causing boot to fail. This issue might occur with any iSCSI adapter, including Emulex and QLogic. - Slow NFS storage performance in virtual machines running on VSA provisioned NFS storage
Slow NFS storage performance is observed on virtual machines running on VSA provisioned NFS storage. Delayed acknowledgements from the ESXi host for the NFS Read responses might cause this performance issue. - Virtual hardware versions prior to version 11 incorrectly claim support for Page Attribute Table
The virtual hardware versions prior to version 11 incorrectly claim support for Page Attribute Table (PAT) in CPUID[1].EDX[PAT].
This issue is resolved in this release by extending support for the IA32_PAT MSR to all versions of virtual hardware.
Note: This support is limited to recording the guest’s PAT in the IA32_PAT MSR. The guest’s PAT does not actually influence the memory types used by the virtual machine. - Quiesced snapshot might fail during snapshot initialization
Quiesced snapshot might fail due to a race condition during snapshot initialization. An error message similar to the following is displayed on the Tasks and Events tab of the vCenter Server:
An error occurred while saving the snapshot
You might also see the following information in the guest event log:
System Event Log
Source: Microsoft-Windows-DistributedCOM
Event ID: 10010
Level: Error
Description:
The server {nnnnnnnn-nnnn-nnnn-nnnn-nnnnnnnnnnnn} did not register with DCOM within the required timeout.
Bugs corregidos destacados a nivel vCenter
- vCenter Server fails to display the node count within the environment for a user
Users from domains other than the system tenant’s system domain are not considered a Configuration User and cannot utilize the privileges afforded by the SystemConfiguration.Administrators group. On the System Configuration page, you might not be able to see any of the nodes present or any of the services on an embedded vCenter Server Windows. - The Network Time Protocol (NTP) package is updated
The NTP package is updated to address a stability issue. - vApp creation fails when storage DRS is enabled
When you use vCloud Director 5.5.3 with vSphere 6.0, any operation that clone a vApp, including add to my cloud, instantiate a vApp template, copy, relocate, or import a vApp might fail when the target virtual data center includes a storage DRS-enabled storage cluster that does not support source virtual machine’s storage profile.This failure logs an error message similar to the following:Could not find datastore to create VM ...
Cannot use datastore [vcId=nnnn, moref=datastore-nn] since it does not support storage policy SDRS_SP - Attempt to delete vSphere Distributed Switches fail
Attempting to delete vSphere Distributed Switches (VDS) fail when VPX_DVPORT_MEMBERSHIP and VPX_DVPORT tables have conflicting port entries and the proxy host of the port does not exist in the inventory of vCenter Server. - vSphere Web Client displays vApp and VM templates as Unknown when you delete their content in a subscribed library
If you are using subscribed library with enabled option to download library content only when needed, when you delete the content of a VM template, the vSphere Web Client displays the VM template as Unknown, and the item becomes unusable. Same behavior occurs for vApp templates in the subscribed library. - SNMP alerts display IP as 0.0.0.0 instead of the vCenter Server IP address after upgrading to vCenter Server 5.5 Update 2d
When you use SNMP receiver to receive SNMP trap messages, the information from vCenter Server appears to originate from an incorrect IP address 0.0.0.0. This issue occurs after upgrading the vCenter Server to version 5.5 Update 2d.
Espero que os guste esta entrada y os sirva, y si tenéis un entorno vSphere 6.0 os recomiendo esta actualización.
- Release notes de vCenter Server 6.0.0b disponibles aquí. Build Number: 2800571
- Descargar vCenter Server 6.0.0b aquí
Un saludo
Leave a Reply