Note: vSphere 6.7 Update 2 was recently announced and is generally available as an update and download.
The announcement of vSphere 6.7 Update 2 informed us of many new features like DRS-MM (DRS in Maintenance Mode), CPU scheduler options for vulnerabilities like L1TF, as well as new vSphere ROBO licensing, and updates to vSphere Platinum. While this release does include the usual bug fixes, it also focuses on improvements in several key areas. In this post, we’ll go over these key improvements and their importance as they pertain to vCenter Server. Let’s find out what’s new in vCenter Server 6.7 Update 2.
vCenter Server Architecture
Recently, VMware announced it would deprecate the external Platform Services Controller deployment model and in the next major vSphere release (not an update release), external deployments would not be an available option. To build on this change of deployment types as well as help alert customers, vCenter Server 6.7 Update 2 now includes warnings informing the vSphere Administrator of the deprecated deployment for the External Platform Services Controller.
Warnings are visible in the vCenter Server Appliance installer UI or CLI. Please see KB 60229 for more details.
The Converge Tool was introduced in vSphere 6.7 Update 1 as the method to move from an external PSC deployment to an embedded PSC via the vCenter Server CLI. Today with vCenter Server 6.7 Update 2, convergence functionality is now available within the vSphere Client. Included is a Table View or Topology View of all vCenter Servers and PSCs. Easily identify replication partners or log in to the vCenter Server Appliance Management Interface (VAMI) interface directly. Table View is the starting point for converging an external PSC to embedded, with a simplistic overview of all vCenter Server nodes.
Simply select the vCenter Server that is registered to an external PSC, then choose Converge To Embedded to begin consolidating. At a high level, convergence begins, the required RPMs for PSC services are installed on the vCenter Server, and replication agreements are configured. The external PSC can then be decommissioned after all vCenter Servers in the SSO domain have been completed. Select the PSC to decommission and click Decommission PSC to unregister the external node from its vCenter Server. The decommission process also powers off the PSC.
NOTE: Be sure to repoint any other VMware or 3rd party software from the external PSC to the new embedded PSC node prior to decommissioning the external PSC.
File-Based Backup and Restore
vCenter Server 6.7 Update 2 includes new protocol support for backing up and restoring a vCenter Server Appliance. Introducing Network File System (NFS) & Samba (SMB) as the newest supported protocols for the built-in File-Based Backup and Restore. The addition of NFS and SMB now brings the protocol choices up to 7 total (HTTP, HTTPS, FTP, FTPS, SCP, NFS, and SMB) when configuring a vCenter Server for File-Based Backup or Restore. Currently supported versions of these new protocols are, NFSv3 and SMB2.
Backing up vCenter Server is an important task that tends to fall within Day 2 operations. The vCenter Server Appliance supports both Image-Level as well as File-Based backups. Many customers today leverage image-level backups just like they do for other virtual machines (VM) within vSphere. Leveraging the built-in File-Based backup is the best way to back up your vCenter Server. When an Image-Level backup is used in conjunction with a File-Based backup, you now have peace of mind that if an issue arises with a backup, your vCenter Server data can be recovered. Utilizing both methods will act as your insurance policy for backups.
NOTE: These features are only available for the vCenter Server Appliance.
Another improvement to File-Based Backup is the introduction of Event Notifications for backup & restore. vSphere 6.7 Update 2 now contains Alarms such as Backup Job Status, as well as Success and Failure events. Now easily identify success or failures of File-Based backups in vCenter Server.
File-Based backup alarms are of course customizable to fit needs. In this example we see from Alarm Definitions window, we can search for the alarm, edit and customize as needed. Options for email notifications or SNMP traps can also be configured here.
When vSphere 6.7 became generally available in April of 2018, it included a powerful new feature, vSphere Health. vSphere Health works to identify and resolve potential issues within a customer’s environment. Telemetry data is collected analyzed from the vSphere environment and used to guide the vSphere Administrator through remediation.
Discover more about vSphere Health: Understanding vSphere Health & Tech Field Day 18
New to vSphere Health in this update release is Categories and Alarms. Alarms are generated when a new issue is detected in vSphere. vSphere Health alarms can be set to Acknowledge or Reset to Green much like other vCenter Server alarms.
Health checks are now grouped into one of four health Categories; Online Availability, Compute, Network, and Storage. This new grouping feature not only allows for a simple, organized view of all vSphere Health checks but also aligns with the goal of improving the overall organization of vSphere Health as more health checks are introduced.
The addition of storing Virtual Machine Template (VMTX) files in Content Library was introduced in vSphere 6.7 Update 1. This enables deploying a virtual machine from native VM templates alongside OVF/OVA templates within Content Library.
vCenter Server 6.7 Update 2 continues to add new functionally when utilizing Content Library. Syncing of native VM templates between Content Libraries is now available when vCenter Server is configured for Enhanced Linked Mode. Published libraries can now become subscriber aware allowing newly published items to replicate to other subscribed Content Libraries.
A Publish option is available when viewing the VMTX template or from the Subscriptions tab of the local library. Publishing from the local library will sync the VM template to the selected Subscriber Libraries.
One of the biggest use cases for Content Library is the ability to distribute VM content across vCenter Servers in order to avoid recreating VM template configurations from scratch. Content Library Sync addresses this concern allowing the distribution of VMTX templates between vCenter Servers.
Let’s not forget the vSphere Client. In what started out as a VMware Fling, the vSphere Client has become our default client when using vSphere. vSphere 6.7 Update 2 brings a few additional enhancements to this HTML5 based client.
New to the vSphere Client is Developer Center with Code Capture and API Explorer. While this popular feature started out in the vSphere HTML5 Web Client Fling, it is now available in vSphere 6.7 Update 2. Code Capture allows you to record your actions in the vSphere Client delivering simple, usable code output. Senior Technical Marketing Architect, Kyle Ruddy says it all in a recent post; “If you’ve ever wanted to see how tasks performed in the UI would look as code, this is it.”
Learn more about Code Capture: Introducing Code Capture
Once enabled, Code Capture can easily be activated via the “record” button in the vSphere Client.
Next is API Explorer. If you are familiar with using APIs in vSphere you probably remember API Explorer located here; https://<vCenterServer-FQDN>/apiexplorer since the vSphere 6.5 release. This update brings API Explorer into the vSphere Client which removes the extra steps authenticating prior to interacting with the REST APIs. Quickly search certain services and methods available in the vSphere REST API by specific words. For example, searching the term “back” filters APIs to show relevant results.
An Execute button now appears the bottom of each method’s section allowing quick access to perform the action via the REST API. Fair warning that this is a LIVE CHANGE, pop warnings are also shown when trying these actions.
vSphere Update Manager (VUM) adds enhancements also to the vSphere Client. Now perform Attach, Check Compliance, and Remediate actions all from one screen. Remediation workflow updates include attaching and remediating multiple baselines, disconnecting removable devices, and enabling Quick Boot. Viewing the details of an ESXi Image within vSphere Update Manager has also evolved. Easily discover the Name, Version, Vendor, Acceptance Level, etc. for all packages included in the selected image.
The Client Plug-Ins page has been given an update as well in vSphere 6.7 Update 2. In previous vSphere versions, troubleshooting client plug-in issues meant sifting through logs to find out what went wrong. Now easily view the Deployment state of a plug-in right from the vSphere Client. vSphere Plug-Ins that have failed to deploy to the vSphere Client or are incompatible will be shown on the Client Plug-Ins screen. Access this interface by selecting Administration from the Menu, then select Client Plug-Ins under Solutions.
The vSphere Task Console will now also show the status of each plug-in as it registers with vCenter Server. If a plug-in download or deployment failure occurs, more details can be found by selecting the task and reviewing the error stack. The Task Console is found from the vSphere Client Menu under Tasks.
In closing, we see that vSphere 6.7 Update 2 is bringing plenty of new enhancements for vCenter Server. Stay tuned for future posts and walkthroughs that go into more detail for new vCenter Server6.7 Update 2 features. If you have any questions please post in the comments section below!