What’s new in vSphere 6 (Features and Enhancements)

-
VMware vSphere 6 introduces many new features and enhancements.
This article provides an overview of the new features and capabilites + links to other websites/blogs where you can read more about the individual topics.

vSphere 6 ESXi and VM enhancements:

  • Cluster now supports up to 64 nodes and 8.000 VMs
  • VMs now support up to 128 vCPUs and 4 TB vRAM
  • Hosts now support up to:
    480 pCPUs
    12 TB RAM
    datastores with 64 TB
    1000 VMs
  • added guest OS support for FreeBSD10.0 and Asianux 4 SP3
  • expanded support for the latest x86 chip sets

Storage:

  • Virtual Volumes (VVol)
  • improved Storage IO Control

vSphere Fault Tolerance:

  • FT support for up to 4 vCPUs and 64 GB RAM
  • new, more scalable technology: fast check-pointing to keep primary and secondary in sync
  • continuous availability – zero downtime, zero data loss for infrastructure failures
  • FT now supports Snapshots (Backup)
  • Storage Fault Tolerance:
    primary and secondary VM has its own .vmx & .vmdk files
    primary and secondary VM can be placed on different datastores!

Troubleshooting with ESXTOP

vMotion Enhancements:

  • vMotion across vCenter Servers
  • vMotion across vSwitches
  • Long-distance vMotion – now support of local, metro and cross-continental distances (up to 100+ms RTTs)

vCenter Server Appliance:

  • the configuration maximums of the vCenter Server Appliance will be extended:
    The embedded DB now supports up to 1.000 Hosts and 10.000 powered on VMs (vSphere 5.5: 100 hosts/3000 VMs)

vSphere Web Client:

  • long awaited performance improvements are implemented
  • but nevertheless a Virtual Infrastructure Client 6.0 (C#) will be still available
Links:

Improved vSphere Replication:

  • Recover Point Objectives (RPOs) will remain at 15 minutes (was at 5 min in early builds – maybe it will be higher in later releases)
  • support for up to 2000 VM replications per vCenter

VMware Virtual SAN (VSAN 6.0)

  • new On-Disk Format
  • Performance Snapshots – vsanSparse
  • usability improvements
  • supports Failure Domains (note: failure domains are NOT metro/streched clusters)
  • new disk serviceability feature
Links:

Comments

Post a Comment

Popular posts from this blog

Designing and Configuring an Enterprise Cloud Solution

-
Image
We have already discussed the architecture of a vRealize Automation environment in previous post. Many topics, including the physical, conceptual and logical design have been covered. These design documents helped us to set up a vRealize Automation environment. However, in order to proceed with the configuration of vRealize Automation, we again need to shift our focus towards the design aspects of implementing a vRealize Automation platform. This chapter will help you to understand these fundamental design concepts. In the following, we will focus on the different components as well as on security aspects. For the most part, this chapter deals with describing the building blocks within a vRealize Automation environment. Afterwards, it will end up with discussing a couple of further design aspects. This chapter will only focus on design issues. The implementation itself will be described in the following chapters. 6.1 vRealize Automation Layers Traditionally, one of the key requ...
Read more

"Host IPMI system event log status" alarm in vCenter Server

-
To resolve this issue, ensure that the NTP settings are correct on the ESXi host, clear the IPMI System Event log file, and reset the sensors.   To clear the IPMI System Event log file and reset the sensors: Open vCenter Server using the vSphere Client. In the vCenter Server Inventory, select the ESXi/ESX host. Click the  Hardware Status  tab. Click  System Event log  under View. Click  Reset Event   Log . The red alert is removed from the System Event log. Click  Reset Sensors  to reset the host sensors. Starting with ESXi 5.1 U2, 5,5 P01 and later, you can use the  localcli  command line to clear the IPMI SEL logs. To clear the IPMI SEL logs in ESXi 5.1 and later: Connect to the ESXi host through SSH.  Run this command: localcli hardware ipmi sel clear If you find an incorrect date and if you are unable to reset the logs: In ESX - Restart the management agents and  sfcbd...
Read more

Virtual machines appear as invalid or orphaned in vCenter Server

-
Symptoms Virtual Machines show as invalid or orphaned in vCenter Server Virtual Machines show as invalid or orphaned after a VMware High Availability (VMware HA) host failure occurs Virtual Machines show as invalid or orphaned after an ESX host comes out of maintenance mode Virtual Machines show as invalid or orphaned after a failed DRS migration Virtual Machines show as invalid or orphaned after a storage failure Virtual Machines show as invalid or orphaned after the connection is lost between the vCenter Server and the host where the virtual machine resides You see one or more of these errors when trying to start a virtual machine: Could not power VM, no swap file, failed to power on VM. VMControl error -11: No such virtual machine. A general system error occurred. The system returned on error. Communication with the virtual machine may have been interrupted In   C:\ProgramData\VMware\VMware VirtualCenter\Logs\vpxd.log   file, you see entries similar to: [11...
Read more