![\"vmware-vsphere-6-7-update-3-released-01\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-6-7-update-3-released-01.jpg\" "\\"vmware-vsphere-6-7-update-3-released-01\\"")
<\/p>\n<\/p>\n
VMware released the new vSphere 6.7<\/a> Update 3 introducing some enhancements and bug fixes to improve overall performance.<\/p>\n The most interesting feature implemented in vSphere 6.7 Update 3 is the ability to change the vCenter Server hostname<\/strong> after the deployment.<\/p>\n <\/p>\n The new release comes with the following new features:<\/p>\n <\/p>\n Update 3 provides the support for up to four<\/strong> NVIDIA GRID virtual GPUs (vGPU) per virtual machine allowing more workloads on vSphere with intensive graphics and compute<\/strong> requirements improving VM performance.<\/p>\n <\/p>\n The 2nd Generation of AMD EPYC processors are now supported.<\/p>\n <\/p>\n Until now after the deployment of the vCSA, the change of the FQDN or the hostname<\/strong> (aka Primary Network ID or PNID) of the vCenter Server was no supported. Also during the migration from vCenter Windows-based to vCSA or the vCSA upgrade, the old FQDN is preserved<\/strong>.<\/p>\n vSphere 6.7 Update 3 provides the capability to rename<\/strong> the vCenter Server\u2019s FQDN with a dedicated wizard (picture from VMware).<\/p>\n To rename the vCSA's FQDN you need the SSO Domain Administrator<\/strong> credentials, such as administrator@vsphere.local<\/em>.<\/p>\n As stated by VMware, once the vCSA has been renamed, there are some additional steps to perform<\/strong> in order to avoid services disruption:<\/p>\n <\/p>\n If the vCSA is configured with a dynamic IP assigned by a DHCP server<\/strong>, when the vCSA IP changes the DNS record needs to be modified accordingly to ensure the hostname is correctly resolved.<\/p>\n The new Update 3 comes with Dynamic DNS (DDNS) support in order to dynamically update a DNS<\/strong> server with the new IP address.<\/p>\n <\/p>\n New enhancements have been introduced to VMXNET3<\/strong>. As reported in the VMware documentation, with Update 3 is now possible to use Guest encapsulation offload and UDP, and ESP RSS support to the Enhanced Networking Stack (ENS).<\/p>\n Checksum calculations are offloaded from encapsulated packets to the virtual device emulation and you can run RSS on UDP and ESP packets on demand. The feature requires a corresponding VMXNET3 v4 driver<\/strong>.<\/p>\n <\/p>\n The new release introduces significant performance enhancements<\/strong> to VMware vSAN. Check out this VMware post<\/a> for more details.<\/p>\n Additional info related to Update 3 can be found in the Release Notes<\/strong>: vCSA 6.7 U3<\/a>, ESXi 6.7 U3<\/a> and vSAN 6.7 U3<\/a>.<\/p>\n VMware released the new vSphere 6.7 Update 3 introducing some enhancements and bug fixes to improve overall performance. The most interesting feature implemented in vSphere 6.7 Update 3 is the ability to change the vCenter Server hostname after the deployment.<\/p>\n","protected":false},"author":3,"featured_media":40273,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[903,2701],"tags":[2046,2045,2047,2006],"class_list":["post-40270","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-vsphere-en","tag-nvidia","tag-pnid","tag-update-3-en","tag-vcsa-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/40270","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=40270"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/40270\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/40273"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=40270"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=40270"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=40270"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}What's new in vSphere 6.7 Update 3<\/h2>\n
Support for multiple NVIDIA vGPUs<\/h4>\n
![\"vmware-vsphere-6-7-update-3-released-02\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-6-7-update-3-released-02.jpg\" "\\"vmware-vsphere-6-7-update-3-released-02\\"")
<\/p>\nAMD EPYC Generation 2 support<\/h4>\n
Ability to change vCenter Server PNID<\/h4>\n
![\"vmware-vsphere-6-7-update-3-released-03\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-6-7-update-3-released-03-600x311.jpg\" "\\"vmware-vsphere-6-7-update-3-released-03\\"")
<\/p>\n\n
Dynamic DNS support<\/h4>\n
Driver enhancements<\/h4>\n
vSAN 6.7 Update 3<\/h4>\n
![\"vmware-vsphere-6-7-update-3-released-04\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-6-7-update-3-released-04-600x457.jpg\" "\\"vmware-vsphere-6-7-update-3-released-04\\"")
<\/p>\n![\"signature\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" "\\"signature\\"")
<\/p>\n","protected":false},"excerpt":{"rendered":"