vSphere 6.7的新增功能？我應該升級嗎？

https://www.altaro.com/vmware/new-in-vsphere-6-7/

Ryan Birk?2018年5月3日

29

自從我們有了新的vSphere版本以來，已經有一段時間了，但是等待已經結束– vSphere 6.7已經正式發布！我一直在參與6.7 beta版，因此能夠公開談論該版本終于很高興。我想發表一篇文章，概述此版本中已更新或新增的一些新功能。因此，讓我們開始吧！

升級版

讓我們先談談您可以升級和不能升級的內容。新版本僅支持從vSphere 6.0或6.5的升級和遷移。如果您的環境運行的是5.5版，則升級到6.7需要額外的步驟。您將必須至少遷移到6.0版，然后再遷移到6.7版。如果您具有運行6.0或6.5的vCenter Server管理ESXi主機5.5的混合環境，則必須在升級vCenter Server之前將主機至少升級到版本6.0。VMware已經為此花了很多時間和警告，很多人看到了它的到來，但是現在它是正式的，盡快脫離5.5！

當前支持的版本6.7遷移路徑：

• vSphere 6.0至6.7
• vSphere 6.5至6.7
• *?不支持?vSphere 5.5至6.7?*。

vSphere 6.7配置最大值

VMware再次更新了一些最大值。大多數常用的CPU和內存內容保持不變，但下面列出了其他更改。容錯VM進行了另一次升級，現在可以升級到8個vCPU，這很好。

?

HTML 5 Web客戶端

對我來說，這是我在6.7中最喜歡的更新。我經常被問到他們何時要殺死基于Flash的客戶端，而隨著去年宣布棄用基于Flash的客戶端，答案很快就會得到答案。HTML 5客戶端現在已完成95％的功能。在過去的幾個月中，他們確實為客戶做了大量工作，并為之努力。他們在這里所做的工作給我留下了深刻的印象，這對vCenter團隊來說真是太好了！Platform Services Controller功能現在也已成為vSphere Client的一部分。現在，它位于“管理”菜單下，“ PSC”選項位于兩個選項卡之間。證書管理有其自己的標簽，所有其他管理均在配置標簽下。

更新的vSphere Client版本中的一些較新的工作流程包括：

• vSphere Update Manager
• 內容庫
• 虛擬SAN
• 儲存政策
• 主機配置文件
• vDS拓撲圖
• 發牌

請注意，并非所有上述工作流程都已100％完成，但是VMware每次更新都在不斷更新工作流程。這只是時間問題。

vCenter Appliance備份計劃

6.5中內置了內置備份工具，但是要能夠輕松自動備份設備是一個挑戰。如下所示，您現在可以設置基本的備份計劃，以備份設備配置以供以后還原。您還可以設置要保留的備份數量。我仍然建議您使用Altaro之類的第三方備份工具來備份vCenter Linux Appliance，因為您永遠無法擁有足夠的備份！

CLI工具

它已經回來了！vCenter 6.7的一項新功能是能夠將vCenter Server重新指向駐留在完全不同的vSphere SSO域中的另一個Platform Services Controller節點??。對于域合并，此功能非常龐大，如果需要，可以使用cmss-util工具進行域拆分。

該功能在vSphere 5.5中可供vSphere管理員使用，并且已成為該產品版本6.0和6.5的痛點，因為它限制了基于業務需求或IT資源的整合而無需構建新vCenter Server的情況下進行合并或拆分的能力。組織。

新的CMSSO-UTIL CLI實用程序允許跨SSO域重新指向vCenter設備。

更新的vSphere Appliance管理界面

VAMI界面已得到改進，新增了功能和選項卡，主要用于監視和故障排除：

• 在“??監視”??選項卡中，現在可以查看vCSA的所有磁盤分區，可用空間和利用率。更好地了解CPU，內存，網絡和數據庫利用率。
• 現在，服務??狀態，啟動類型和運行狀況在VAMI中可見。如果需要，可以直接從VAMI啟動，停止和重新啟動服務。
• ?現在支持的Syslog轉發為三個。以前僅支持一次轉發。
• 更新了?“??更新”??部分，在選擇補丁和更新時提供了更大的靈活性，并提供了?從VAMI?登臺或登臺和安裝補丁或更新的選項??。現已更多信息??什么??是包括?每個補丁或者升級程序以及類型，嚴重程度，以及是否需要重新啟動。

ESXi單次重啟

VMware在此6.7版本的vSphere中簡化了升級過程。從6.5升級到6.7將是第一個看到這種好處的人。VMware消除了主要版本升級通常需要的兩次重新引導之一，因此您的升級將更快，過程更流暢，誰會抱怨呢？

ESXi快速啟動

這是一個很好的功能，至少在我的家庭實驗室中，我還沒有機會使用很多功能。對于初學者來說，您的硬件必須支持此功能，但是其想法是無需通過物理硬件重新啟動過程即可重新啟動虛擬機管理程序。目前僅支持有限數量的服務器，但將來數量會增加，因此我們至少期待更多。此功能不僅適用于重新引導，還適用于升級。系統將創建第二個ESXi內存映像，并且在重新引導主機時，它不會執行完全重新引導，而是切換到最新的。這是一個非常酷的新功能！

?

?

03 May 2018 by?Ryan Birk

29

It’s been awhile since we’ve had a new vSphere release to get excited about but the wait is over – vSphere 6.7 has been officially released! I have been participating in the 6.7 beta so it’s finally nice to be able to talk about the release publicly. I wanted to put together a post that outlines some of the new features that are updated or new in this release. So let’s get to it!

Upgrades

2019微信新增三大功能、Let’s talk first about what you can and can’t upgrade from.?The new version supports upgrades and migrations from vSphere 6.0 or 6.5 only. If your environment is running version 5.5, the upgrade to 6.7 needs an additional step. You will have to migrate at least to version 6.0 then to 6.7. If you have a mixed environment with vCenter Server running 6.0 or 6.5 managing ESXi hosts 5.5, you have to upgrade the hosts to at least version 6.0 before upgrading the vCenter Server. VMware has given plenty of time and warnings about this and many saw it coming, but now it’s official, get off of 5.5 as soon as possible!

Currently supported migration paths to version 6.7:

• vSphere 6.0 to 6.7
• vSphere 6.5 to 6.7
• vSphere 5.5 to 6.7 is?*not supported*.

vSphere 6.7 Configuration Maximums

VMware has once again updated some maximums. Most of the usual CPU and memory stuff stayed the same, but other changes are listed below. Fault Tolerant VMs get another upgrade and can be now bumped to 8 vCPUs, which is nice.

?

The HTML 5 Web Client

For me, this is hands down my favorite update in 6.7. I am constantly asked when they’re going to kill the Flash-based client and the answer is very soon with the announced deprecation of the Flash-based client last year. The HTML 5 client is now 95% feature complete. They’ve really polished the client and worked hard on it over the last several months. I’m very impressed with the work they’ve done here, so nice work to the vCenter team! The Platform Services Controller functionality is now part of the vSphere Client as well. It now located under the Administration menu, the PSC options are divided between two tabs. Certificate management has its own tab and all other management is under the configuration tab.

Some of the newer workflows in the updated vSphere Client release include:

• vSphere Update Manager
• Content Library
• vSAN
• Storage Policies
• Host Profiles
• vDS Topology Diagram
• Licensing

新增了nfc功能？Note that not all of the above workflows are 100% finished but VMware has been constantly updating the workflows with each update. It’s only a matter of time.

vCenter Appliance Backup Schedule

Built-in backup tools were built into 6.5, but easily being able to backup the appliance automatically was a challenge. As you can see below, you can now set up a basic backup schedule to backup your appliance configuration for a later restore. You can also set the number of backups to retain. I’d still recommend backing up your vCenter Linux Appliance with a third party backup tool like Altaro, just because you can never have enough backups!

CLI Tools

It has returned! A new feature with vCenter 6.7 is the ability to re-point a vCenter Server to another Platform Services Controller node, that resides in an?entirely different vSphere SSO domain. This functionality is insanely huge for domain consolidation, and also domain splitting if needed with the cmss-util tool.

This functionality was available to vSphere administrators in vSphere 5.5 and has been a pain point of versions 6.0 and 6.5 of the product as it constrained the ability to consolidate or split without building new vCenter Servers, based on business requirements or consolidation of IT resources within an organization.

微信功能升級了？New CMSSO-UTIL CLI utility allows repointing vCenter appliance across SSO domains.

Updated vSphere Appliance Management Interface

The VAMI interface has been improved with new features and tabs mainly focused on monitoring and troubleshooting:

• In the?Monitoring?tab, there is now the possibility to see all the disk partitions for the vCSA, space available and utilization.?Better visibility to CPU, memory, network, and database utilization.
• Services?status, startup type, and health are now visible in the VAMI. Services can be started, stopped, and restarted directly from the VAMI if needed.
• Syslog?forwards supported are now three. Previously only one forwarding was supported.
• The?Update?section has been improved providing a more flexibility in selecting patches and updates providing the option to?stage or stage and install?a patch or update from the VAMI. Are now available more information?about what?is included?for each patch or update as well as type, severity, and if a reboot is required.

ESXi Single Reboot

VMware has streamlined the upgrade process in this 6.7 release of vSphere. Upgrades from 6.5 to 6.7 will be the first to see this benefit. VMware has eliminated one of the two reboots that were normally required for major version upgrades, so your upgrades are going to be faster and a smoother process, and who could complain there?!

ESXi Quick Boot

This is a neat feature that I have not had the opportunity to use much of yet, at least in my home lab. For starters, your hardware has to support this feature, but the idea is that?the hypervisor can be restarted without going through the physical hardware reboot process. There is currently only a limited number of servers that are supported but the number will be increased in the future, so we get to look forward to more of this at least. This feature works not only for reboots but also for upgrades. The system creates a second ESXi memory image and when the host is rebooted it doesn’t perform a full reboot but it switches over to the latest instead. This is a pretty cool new feature!