VMware vSphere 6.7 Update 3 is GA as of August 20, 2019.
The most interesting new feature is the possibility to change the Primary Network Identifier (PNID) of vCenter Server Appliance
With vCenter Server 6.7 Update 3, you can change the Primary Network Identifier (PNID) of your vCenter Server Appliance. You can change the vCenter Server Appliance FQDN or hostname, and also modify the IP address configuration of the virtual machine Management Network (NIC 0).
I wrote about PNIC last year here on this blog post What is vCenter PNID?
It is a great improvement that you can change vCenter FQDN, however, the process has some
For further operational details on how to change vCenter Server's FQDN/PNID read the blog post - Changing your vCenter Server’s FQDN.
There are a few more new features and enhancements
For further information read ESXi Release Notes here, vCenter Release Notes here and VMware Update Manager here.
I also recommend reading the blog post Announcing vSphere 6.7 Update 3 available at https://blogs.vmware.com/vsphere/2019/08/announcing-vsphere-6-7-update-3.html
The most interesting new feature is the possibility to change the Primary Network Identifier (PNID) of vCenter Server Appliance
With vCenter Server 6.7 Update 3, you can change the Primary Network Identifier (PNID) of your vCenter Server Appliance. You can change the vCenter Server Appliance FQDN or hostname, and also modify the IP address configuration of the virtual machine Management Network (NIC 0).
I wrote about PNIC last year here on this blog post What is vCenter PNID?
It is a great improvement that you can change vCenter FQDN, however, the process has some
For further operational details on how to change vCenter Server's FQDN/PNID read the blog post - Changing your vCenter Server’s FQDN.
There are a few more new features and enhancements
- vCenter Server 6.7 Update 3 supports a dynamic relationship between the IP address settings of a vCenter Server Appliance and a DNS server by using the Dynamic Domain Name Service (DDNS). The DDNS client in the appliance automatically sends secure updates to DDNS servers on scheduled intervals.
- With vCenter Server 6.7 Update 3, you can publish your .vmtx templates directly from a published library to multiple subscribers in a single action instead of performing a synchronization from each subscribed library individually. The published and subscribed libraries must be in the same linked vCenter Server system, regardless if on-premises, on cloud, or hybrid. Work with other templates in content libraries does not change.
- With vCenter Server 6.7 Update 3, if the overall health status of a vSAN cluster is Red, APIs to configure or extend HCI clusters throw InvalidState exception to prevent further configuration or extension. This fix aims to resolve situations when mixed versions of ESXi host in a HCI cluster might cause vSAN network partition.
- ixgben driver enhancements
- VMXNET3 enhancements
- NVIDIA virtual GPU (vGPU) enhancements
- bnxtnet driver enhancements
- QuickBoot support enhancements
- Configurable shutdown time for the sfcbd service
For further information read ESXi Release Notes here, vCenter Release Notes here and VMware Update Manager here.
I also recommend reading the blog post Announcing vSphere 6.7 Update 3 available at https://blogs.vmware.com/vsphere/2019/08/announcing-vsphere-6-7-update-3.html
No comments:
Post a Comment