Esxi Ver 6.0 Interview Questions

ESXI ver 6.0:

Q Features & enhancements in vsphere6 ?

A 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

Q Latest feature in Vsphere Fault Tolerance in vsphere6

A 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!

Q vSphere 6.0 Fault Tolerance(Features) ?

A FT Features:

• 4vCPU Vms can be protected by FT
• VMs with up to 64Gb of RAM
• Up to 4 FT protected VMs per host
• Hot configured FT possibility
• Enhanced virtual disk format support
• VADP support (can backup FT protected VMs now. Previously not possible)

Q FT Storage?

A FT Storage– FT VMs will need to have a secondary storage! This is new as previously you could use the same storage (for primary and secondary VMs). It’s a hard requirement.

Q Storage in vsphere 6 ?

A Storage:

• Virtual Volumes (VVol)
• improved Storage IO Control

Q Vmotion Enhancements in 6.0 ?

A 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)

Q 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)

Q vSphere Web Client:

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

Q 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

Q 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

Q Comparison betweem Version 6 & version 5.x (HOSTS)?

A vSphere 6 Doubles the vSphere Maximums!

64 hosts per cluster (vSphere 5.x it was 32)

8000 Vms (previously 4000)

480 CPUs (vSphere 5.x it was 320 CPUs)

• 12 TB of RAM (vSphere 5.x it was 4 TB of RAM)
• 2048 VMs per host (vSphere 5.x it was 512 VMs).

Q Comparison betweem Version 6 & version 5.x (VM)?

A From VM perspective:

• Virtual hardware 11 (vmx-11)– newly released on vSphere 6
• 128vCPUs
• 4TB of RAM(NUMA aware)
• VDDM 1.1 GDI acceleration
• xHCI 1.0 controller compatible with OS X 10.8 + xHCI driver.

Q What is Long Distance Vmotion ?

A Long distance vMotion is to perform vMotion of Vms from one datacenter to another(to remote site or cloud datacenter) .

Requirements:Link with at least 100 ms RTT (previously 10 ms was necessary)

Network speed - 250 Mbps

Q Requirements of Long Distance Vmotion ?

A Requirements:

• vCenter 6 (both ends)
• Single SSO domain (same SSO domain to use the UI). With an API it’s possible to use different SSO domain.
• L2 connectivity for VM network
• vMotion Network
• 250 Mbps network bandwidth per vMotion operation

Q vMotion across vCenters:

• VM UUID is maintained across vCenter server instances
• Retain Alarms, Events, tak and history
• HA/DRS settings including Affinity/anti-affinity rules, isolation responses, automation level, star-up priority
• VM ressources (shares, reservations, limits)
• Maintain MAC address of Virtual NIC
• VM which leaves for another vCenter will keep its MAC address and this MAC address will not be reused in the source vCenter.

A datacenter was (until now) the highest point in the vCenter architecture…. But long distance vMotion can now get over it.

Q With vSphere 6.0 vMotion can be done between:

• vMotion across vCenters
• vMotion across virtual switches (VSS to VSS, VSS to VDS or VDS to VDS)
• vMotion across long distances and routed vMotion networks