Monthly Archives: August 2017

VMware Cloud on AWS Availability with Veeam

It’s been exactly a year since VMware announced their partnership with AWS and it’s no surprise that at this year’s VMworld the solution is front and center and will feature heavily at Monday’s keynote. Earlier today Veeam was announced as an officially supported backup, recovery and replication platform for VMware Cloud on AWS. This is an exciting announcement for existing customers of Veeam who currently use vSphere and are interesting in consuming VMware Cloud on AWS.

In terms of what Veeam has been able to achieve, there is little noticeable difference in the process to configure and run backup or replication jobs from within Veeam Backup & Replication. The VMware Cloud on AWS resources are treated as just another cluster so most actions and features of the core platform work as if the cloud based cluster was local or otherwise.

Below you can see a screen shot of an VMC vCenter from the AWS based HTML5 Web Client. What you can see if the minimum spec for a VMC customer which includes four hosts with 36 cores and 512GB of RAM, plus vSAN and NSX.

In terms of Veeam making this work, there were a few limitations that VMware have placed on the solution which means that our NFS based features such as Instant VM Recovery, Virtual Labs or Surebackups won’t work at this stage. HotAdd mode is the only supported backup transport mode (which isn’t a bad thing as it’s my preferred transport mode) which talks to a new VDDK library that is part of the VMC platform.

With that the following features work out of the box:

  • Backup with In Guest Processing
  • Restores to original or new locations
  • Backup Copy Jobs
  • Replication
  • Cloud Connect Backup
  • Windows File Level Recovery
  • Veeam Explorers

With the above there are a lot of options for VMC customers to stick to the 3-2-1 rule of backups…remembering that just because the compute resources are in AWS, doesn’t mean that they are highly valuable from a workload and application availability standpoint. Customers can also take advantage of the fact that VMC is just another cluster from their on-premises deployments and use Veeam Backup & Replication to replicate VMs into the VMC vCenter to which end it could be used as a DR site.

For more information and the offical blog post from Veeam co-CEO Peter McKay click here.

Veeam Vault #8: VMworld 2017 Edition…Still Best Of!

I’m sitting in the airport lounge waiting to board the first leg of my 26 hour journey to Las Vegas for VMworld 2017 and I thought it was no better time to write the next edition of my Veeam Vault series. This will be my fifth VMworld as as I wrote earlier in the week…I don’t take this event for granted! This year will be a little different for me in that I am there representing Veeam and I am lucky enough to be presenting a couple of sessions while participating in other Veeam related meetings and activities.

Veeam has had a strong presence at VMworld’s past and this year is no exception. In fact from what I understand it’s our biggest VMworld to date and as you walk around Mandalay Bay you will feel Veeam’s presence. Veeam in it’s early years won the Best of Show in 2010 and Best of Technology in 2011 and has a proud history of a strong showing at every VMworld we have been a part of. And while we have challengers nipping at our feet trying to outdo us we remain focus on delivering great technology while being able to be the top contributer to the community and still able to put on the best events at the show.

Veeam Sessions @VMworld:

Officially we have two breakout sessions this year, with Danny Allan and Rick Vanover presenting a Deep Dive on v10 and Michael Cade and myself presenting a session on advanced VMware and Veeam features and integrations. There are also a couple of vBrownBag Tech Talks where Veeam features including talks from Michael Cade, myself and some of our great Veeam Vanguard’s.

The sessions can be viewed and selected from the VMworld Content Catalog here and we also have a number of Sponsor Booth sessions with our ecosystem partners…so keep an eye out for those.

Veeam @VMworld Solutions Exchange:

This year we will have two huge booths on the floor, with a Main Booth Area doing demo’s prize, giveaways, having an Experts Bar and acting as sponsor of the opening night hall crawl. We also have a coffee bar and lounge space called the vBar. This will be a chill out area serving good coffee and offering seats for people to come and relax during the event.

Veeam Community Support @VMworld:

As Eric Siebert wrote last week… Veeam gets the community and has been a strong supporter historically of VMworld community based events. This year again, we have come to the party are have gone all-in in terms of being front and center in supporting community events. Special mention goes to Rick Vanover who leads the charge in making sure Veeam is doing what it can to help make these events possible:

  • #vGolf
  • Opening Acts
  • VMunderground
  • vBrownBag
  • Spousetivities
  • vExpert Breakfast
  • vDestination Giveaway

Party with Veeam @ VMworld:

Finally, it wouldn’t be VMworld without attending Veeam’s seriously legendary party. This year we are looking to top last years event at Light nightclub by taking over the hottest club in Vegas… Hakkasan Nightclub! I know how hard it is to plan evening activities at VMworld and there is no doubt that there are a lot of decent competing parties on the Tuesday night…however whatever you do, you need to make sure that you at least stop by the MGM and party in green. RSVP here.

Final Word:

Again, this year’s VMworld is going to be huge and Veeam will be right there front and center of the awesomeness. Please stop by our sessions, visit our stand and attend our community sponsored events and feel free to chase me down for a chat…I’m always keen to meet other members of this great community. Oh, and don’t forget to get to the party!

VMworld 2017: vCloud Air Network Again Out in Force

Last year saw a resurgence in vCloud related sessions at VMworld and the trend has continued this year at the 2017 event. Looking through the sessions at Partner Exchange and VMworld proper the refocus on the vCloud Air Network that was announced at VMworld 2015 has gathered steam. This together with the subsequent release of vCloud Director SP 8.20 and the pending release of the next version of vCD, things are looking good for service providers that have built their platforms on VMware technologies.

If you are attending Partner Exchange there are a number of sessions that should be on your list for the Sunday. The sessions seem to be down on last year but that’s due to vCloud Air no longer being a going concern. I’ve listed down my top picks below added links to them for easy searchability in the VMworld Session Catalog. I’ve added a session on AWS and a session on vSAN as service providers should understand how both technologies fit into their strategy.

  • PAR4360BU – Cloud Service Provider Platform: Evolution and Future
  • PAR4358BU – How to Build a Hybrid Cloud Using NSX and vCloud Director-A Service Provider Perspective
  • PAR4383BU – Delivering Hybrid Cloud Architectures for Your Customers with VMware Cloud on AWS
  • PAR4382BU – Embracing VMware Cloud on AWS – How Can You Deliver Value to Your Customers
  • PAR4367BU – What’s New in vSAN 6.6 – A Deep Dive 

Looking through the breakout sessions there are 20 sessions directly relating to vCloud Director which is an excellent result. The rest that i’ve listed below tie in a mix of disaster recovery, hybrid cloud and NSX related networking sessions.

  • LHC1661BU—Getting Started with vCloud Air Network (Technical Tips and Tricks)
  • LHC1716BU—On-Ramp to the Cloud: Migration Tools and Strategies
  • LHC1753BU—Case Study: How VMware NSX Is Empowering a Service Provider to Help Customers Achieve and Maintain Industry Compliance
  • LHC1809BU—Use NSX to Deploy a Secure Virtual Network Bridging Multiple Locations for a True Hybrid Cloud
  • LHC1951BU—Automated Cloud Recovery for When You are Nuked from Orbit
  • LHC2424BU—200 to 40,000 VMs in 24 Months: Building Highly Scalable SDDC on Hybrid Cloud: Real-World Example
  • LHC2573BU—Achieving Hybrid Cloud Data Agility Securely with VMware NSX
  • LHC1739GU—Disaster Recovery to the Cloud: What Has Changed in the Past Year?
  • LHC3179GU—Choosing the Ideal Cloud Provider Partner
  • LHC3180GU—Effective DR Strategies
  • LHC1566PU—Ask the vCloud Air Network Cloud Experts
  • LHC3139SU— Achieving Success in a Multi-Cloud World
  • LHC2626BU—Build VMware Powered Hybrid Clouds: See How vCloud Director and NSX work together to build true Hybrid Clouds

There are also a number of vCloud Air Network partners on the exhibit floor.

  • CenturyLink
  • OVH
  • Faction
  • phoenixNAP
  • Fujitsu
  • Rackspace
  • IBM
  • SkyTap
  • iland
  • SwissCom
  • Navisite
  • Virtustream

Apart from what I have listed above there will also be a lot of vCAN talent hovering around the conference so make sure you make an effort to connect, network and share vCAN experiences. The vCloud Air Network is a symbiotic ecosystem and if the vCAN grows stronger…the ecosystem grows stronger.

#LongLivevCD

References:

https://blogs.vmware.com/vcloud/2017/08/have-you-signed-up-your-vmworld-cloud-provider-sessions.html

https://blogs.vmware.com/vcloud/2017/08/vcloud-air-network-partners-can-accelerate-your-success-in-the-cloud.html

VMworld 2017: Don’t Take it for Granted!

This time next week VMworld 2017 will be kicking off with the Sunday evening Welcome Reception among other sponsor and community events and for me, it will mark my fifth VMworld since 2012 having only missed the 2013 event. It’s become an annual pilgrimage to the west coast of the US so much so that my wife locks in the dates at the beginning of every year. It just so happens that Father’s Day in Australia is the Sunday after VMworld and it’s also around the time of my wedding anniversary…so if anything, VMworld reminds to take time out from the event and pick up that year’s anniversary gift.

Having been lucky enough to attend five out of the last six VMworld’s it has almost become automatic that I am at the event, and it could be easy for me to take VMworld for granted. I am very mindful of the fact that while the event is starting to loose a little bit of it’s perceived shine in certain circles it’s still the #1 Information Technology Industry Ecosystem event of the year and with that it’s still the must attend event for IT professionals, customers, partners and vendors alike.

I am also mindful of the fact that even after attending so many VMworld’s to not waste the opportunity that presents it’s self as an attendee. If I think back to my first VMworld in 2012, I still remember being somewhat timid and reluctant to participate in not much more than the sessions and official parties however the one thing I did do was observe how others where using the event to their advantage. While there is brilliant technology to be uncovered and lots of learning to be done, those that have been do VMworld before come to understand that networking is a primary benefit of attending and the networking should be milked for all it’s worth!

Someone told me while at VMworld 2014 that “you never know who is interviewing you”. This is very true and should be something that first timers and regulars understand and use to their advantage as a mechanism for potential career advancement…there is no better event to rub shoulders with industry peers, community leaders a tech rockstars. With that you should always be aware of your surroundings and not to waste any opportunity the may present it’s self. I’m not saying that you will get a new role just by attending and seeking out conversation..but what I am saying is to constantly be on your game!

Even for those, like me that have been lucky enough to attend multiple VMworld’s it’s easy to fly in and just go with the flow. Easy to not appreciate what it means to be there and easy to turn it into a week long drinking event. So my closing message is for everyone attending VMworld this year, be it your 10th or you 1st is to make sure you maximize everything that VMworld has to offer. Take advantage of the opportunity to not only get exposure to new technologies and products but also to network and realize the value that being at such an event offers. You never know when this VMworld could be your last…

Don’t take it for granted!

Runecast: Overview and Service Provider Use Case

A few months ago I was lucky enough to spend time with a couple of the founders of Runecast, Stanimir Markov and Ched Smokovic and got to know a little more about their real time analytics platform for VMware based infrastructure. Soon after that I downloaded and deployed it in my lab and have been running it for a few months. In that time I’ve come to understand and appreciate the value that it adds to the operations and management of any vSphere platform.

Having been part of, and led teams that operated and managed large vSphere based cloud platforms one of the challenges of managing any platform of size is how to stay on top of issues operationally…not only when and as they happen, but also before then happen. Proactive monitoring and alerting that pinpoints issues before they happen is invaluable and up to this point I haven’t found a product that focuses in as specifically as Runecast does to help solve that challenge.

In the past I have researched and used more than a few tools on the market and probably the closest comparison that I can make with Runecast is what CloudPhysics tried to do with their Knowledge Base Adviser feature. For those that have used CloudPhysics in the past Runecast will feel somewhat similar in theory, however Runecast have taken what CloudPhsyics had done and taken it to the next level.

By using a number of resources within VMware’s knowledgebase Runecast is been able to deliver a platform that looks at best practices, log information and security hardening guides to monitor your vSphere infrastructure which in turn brings to your attention through a simple yet intuitive interface to issues that may exist.

Runecast for Service Providers:

Proactive analysis is the name of the game and it’s one of the holy grail’s for any operations team. Prevention of an issue before it occurs is what Runecast sets out to achieve and for service providers that are running critical line of business applications for their clients (which is all service providers) the ability to prevent service disruption is huge.

Apart from the obvious benefits around proactive analytics, one of the best features for service providers is the security hardening feature. Lots of service providers these days are being governed by specific regulations and compliance and security has become front and center of any platform owner. With the security hardening feature it points out specifically what passes and what fails as per the official VMware hardening guide.

I can also see how the specific inventory feature for vCenter objects can be developed in the future to allow service providers to expose certain information via the Runecast APIs to their tenants. I’d love to see some integration with vCloud Director, NSX and vSAN among other VMware platforms…there is serious potential here.

The API endpoints that are being exposed version to version means that service providers can take the information presented and manipulate it their hearts content. It providers a powerful way for service providers to take full advantage of the data that’s being collect and analyised.

Final Thoughts:

This is, for the most a targeted analytics system that focuses on getting you the relevant information quickly and without fuss and allows you to ascertain issues and work towards their resolution. I’m looking forward to seeing what the guys come up with over the next twelve to eighteen months as they further enhance the capabilities.

For your free 14 day Trial register here and if you are heading to VMworld this year make sure to visit them at Booth #832

Disclaimer: Runecast are sponsors of Virtualization is Life!

NSX Bytes: NSX-v 6.3.3 Released – Upgrade Notes and Enhancements

Last week VMware released NSX-v 6.3.3 (Build 6276725) and with it comes a new operating system for the NSX Controllers. Once upgraded the new controllers will be powered by Photon OS which is more and more making it’s way into VMware’s appliances. There are a few other new bits in this release but more importantly a number of Resolved Issues. For those running homelabs with one NSX Controller there are some important upgrade notes to be made aware of before kicking off…i’ll go into those below.

Compatibility:

Before moving to the upgrade there are some important notes around interoperability and supported ESXi versions as is explained in this VMwareKB. The minimum supported version of ESXi running with NSX-v 6.3.3 is as shown below:

  • NSX-v 6.3.3 installed in a vSphere 5.5 environment requires a minimum version of ESXi 5.5 GA
  • NSX-v 6.3.3 installed in a vSphere 6.0 environment requires a minimum version of ESXi 6.0 Update 2
  • NSX-v 6.3.3 installed in a vSphere 6.5 environment requires a minimum version of ESXi 6.5a
If NSX 6.3.3 is installed on an earlier version of 5.5/6.0 ESXi, the netcpa service will fail to start preventing communication between ESXi hosts and the NSX Controllers.
In terms of upgrading from previous versions of NSX-v you can see that the upgrade path does have some stoppers. Below is the interoperability matrix that included vCloud Director 8.20 which, at the moment is not supported with NSX-v 6.3.3…I expect that to change over the next couple of weeks.
Upgrading to NSX-v 6.3.3:

 

As mentioned there are things to look out for during and after the upgrade from previous builds of NSX-v. There are detailed upgrade notes in the release notes so as always, make sure to read those as well, but below is a brief walk through of the upgrade process I conducted in one of my NestedESXi labs.
Once the NSX Manager has been upgraded you should have the following in your Summary tab:
Once the NSX Manager has been upgraded you should restart the vCenter Web Client to ensure any lingering parts of the previous version are removed. Login to the Web Client and click through to Networking & Security -> Installation and then the Management Tab where you will see Upgrade Available.
IMPORTANT NOTE: The upgrade notes state that you need to have a minimum of three NSX Controllers which I’d say is linked to the fact that the underlying OS of the Controllers has been shifted to Photon OS. This is likely to impact anyone running NSX in a NestedESXi or homelab as generally, only one was deployed to preserve resources. Once you click on upgrade you will get a special upgrade warning before committing to the upgrade as shown below:
  • The NSX Controller cluster must contain three controller nodes to upgrade to NSX 6.3.3. If it has fewer than three controllers, you must add controllers before starting the upgrade
  • When you upgrade to NSX-v 6.3.3, instead of an in-place software upgrade, the existing controllers are deleted one at a time, and new Photon OS based controllers are deployed using the same IP addresses

There is also a slight increase to the size of the storage for the controllers from 20GB to 28GB. Once upgraded the NSX Controllers will be at version 6.3.6235594.

The last major step is to upgrade the Host components from the Host Preparation tab. On vSphere 6.0 and above once you have upgraded to NSX 6.3.x, all future NSX VIB changes do not trigger a reboot…only maintenance mode is required to complete the VIB change. In NSX 6.3.3 there is a change to the NSX VIB names on ESXi 6.0 and later where the esx-vxlan and esx-vsip VIBs have been merged and replaced with esx-nsxv as shown below.

VIB names on ESXi 5.5 remain the same.

References:

https://docs.vmware.com/en/VMware-NSX-for-vSphere/6.3/rn/releasenotes_nsx_vsphere_633.html

https://kb.vmware.com/kb/2151267

 

Top vBlog 2017: Notable Representation and Thanks

It feels like this year moving along at ludicrous speed so it’s no surprise that the Top vBlog for 2017 has been run and won. This year Eric Siebert changed things up by introducing new voting mechanisms to try and deliver a more palatable outcome for all who where involved…I think it worked well and delivered interesting results for all those active bloggers listed on the vLaunchpad.

Eric introduced a point system based on Google Page Speed and the number of posts in 2016 to help level the playing field and make it less of a perceived popularity contest. Introducing tangible metrics to make up a portion of the total ranking points was an interesting move and seemed to work well. If nothing else it made people (myself included) more aware around the dark art of web page speed optimization…and this has meant a better browsing experience for those visiting Top vBlog sites.

The Results:

As expected, with Duncan Epping bowing out of the race William Lam deservedly took out the #1 spot with Vladan Seget, Cormac Hogan, Chris Wahl and Scott Lowe rounding out the top 5. There was lots of movement in the top 25 and I managed to sneak into the top 20 at #19 which is extremely humbling.

Creating content for this community is a pleasure and has become somewhat of a personal obsession so it’s nice to get some recognition and I’m happy that what I’m able to produce is (for the most) found useful by people in the community. I’m a passionate guy in most things that I am involved in so it’s no surprise that I feel so strongly in being able to contribute to this great vCommunity…especially when it comes to my strong passion around Hosting, Cloud, Backup and DR.

Aussie Representation:

As with previous years I like to highlight the Aussie and Kiwi (ANZ) representation in the Top vBlog and this year is no different. We have a great blogging scene here in the VMware community and that is reflected with the quality of the bloggers listed below. Special mention to Matt Allford who debuted at #190 …watch out for him to climb up the list over the next few years!

Blog Rank Prev +/- Total Points Total Votes Voting Points #1 Votes # 2016 posts Post Pts PS % PS Pts
Virtualization is Life! (Anthony Spiteri) 19 44 25 1420 165 1042 15 123 246 66% 132
Long White Virtual Clouds (Michael Webster) 20 13 -7 1374 201 1228 7 17 34 56% 112
CloudXC (Josh Odgers) 29 17 -12 1166 144 930 7 53 106 65% 130
Penguinpunk.net (Dan Frith) 106 78 -28 545 48 317 4 46 92 68% 136
Virtual 10 (Manny Sidhu) 115 82 -33 520 44 268 0 32 64 94% 188
Proudest Monkey (Grant Orchard) 127 93 -34 501 53 341 0 11 22 69% 138
Demitasse (Alastair Cooke) 140 168 28 467 42 261 0 33 66 70% 140
Pragmatic IO (Brett Sinclair) 174 153 -21 418 29 222 6 12 24 86% 172
Virtual Tassie (Matt Allford) 190 NEW NEW 392 29 170 1 23 46 88% 176
ukotic.net (Mark Ukotic) 201 179 -22 369 24 159 6 14 28 91% 182
Virtual Notions (Derek Hennessy) 266 298 32 253 21 121 0 25 50 41% 82
Veeam Representation:

My follow colleagues at Veeam made it into the list and all below made the top 50!

Blog Rank Prev +/- Total Points Total Votes Voting Points #1 Votes # 2016 posts Post Pts PS % PS Pts
Virtualization is Life! (Anthony Spiteri) 19 44 25 1420 165 1042 15 123 246 66% 132
Notes from MWhite (Michael White) 31 38 7 1080 108 642 2 132 264 87% 174
Virtual To The Core (Luca Dell’Oca) 38 41 3 927 111 695 2 36 72 80% 160
vZilla (Michael Cade) 44 120 76 871 109 645 9 27 54 86% 172
Tim’s Tech Thoughts (Tim Smith) 48 100 52 837 92 583 5 32 64 95% 190
The Results Show:

Again a massive thank you to Eric for putting together the voting and organising the whole thing. It’s a huge undertaking and we should all be in gratitude to Eric for making it all happen.

The whole list and category winners can been viewed here.

 

Updated: VMworld 2017 – #vGolf Las Vegas

To say that #vGolf is back bigger and better than the inaugural #vGolf held last year at VMworld 2016 is an understatement! This year’s event has been very popular and has gotten a great response.

I’d like to give special mention and thank you to the sponsors of this years event:

Special mention going to Expedient and  who has organized special branded #vGolf balls for the day. We are still looking for another couple of sponsors which will mean that we will be able to accomodate more players as we reached the initial maximum capacity four weeks ago and have had a number of enquiries into getting people on a waiting list. Can I ask that those who wish to put on a wait list please fill out the form below and from there we are working to try and extend the numbers that can play on the day.

vSphere 6.5 Update 1 – What’s in it for Service Providers

Late last week VMware released vSphere 6.5 Update 1 which included updated builds of both vCenter and ESXi and as per usual I will go through some of the key features and fixes that are included in the latest versions of vCenter and ESXi. When looking through the release notes I generally keep an eye out for improvements that relate back to Service Providers who use vSphere as the foundation of their Managed or Infrastructure as a Service offerings. This update also contains an update to vSAN which is now at 6.6.1 so I’ll spend some time looking at what’s been added there.

 

New Features and Enhancements:

Without question this is a significant patch release for vCenter and ESXi and the length of the release notes is testament to that point. In terms of new features there isn’t anything groundbreaking but there are a few nice additions like being able to run the VCSA GUI and CLI installers on Windows 2012 and 2012 R2 as well as 2016 and macOS Sierra and Ubuntu 17.04 OS is supported for Guest OS Customization. vCenter now supports Microsoft SQL Server 2014 SP2 2016 and SP1 as well as some increased configuration maximums supporting Linked Mode with 15 vCenter Instances, 5000 ESXi hosts and 50,000 powered on virtual machines.

Ability to Upgrade or Migrate from vCenter 6.0 Update 3:

This release addresses the previous limitation in the upgrade and migration path for those running vSphere 6.0 U3 in going to vSphere 6.5. I know this will make a lot of providers happy as I know a lot that had to go to 6.0 Update 3 to address existing bug in the platform but where not yet ready or able to go to 6.5 at the time.

HTML5 Client Update:

The HTML5 Web Client has gotten it’s own update that brings it up to speed with the 3.15 Fligng version however it’s still partially functional which remains somewhat frustrating…The online documentation for supported functionality has been updated to vSphere 6.5U1 and is available here.

The list below is of the main updates in this release.

  • DRS/HA VM overrides
  • SDRS rules
  • Content Library – further actions
  • Roles and Global Permissions
  • Download multiple files as zip
  • Distributed Switch – further actions
  • Fault Tolerance
  • SPBM
  • VM Hardware – further items
  • Apply Customize Guest OS during Clone
  • VM Migration – further actions (compute+storage, Cross VC, batch)
vSAN Features:

For service providers, vSAN 6.6 was another major release that sured up vSANs status as a serious storage platform for service provider platforms.

vSAN 6.6.1 introduces three key new features:

  • VMware vSphere Update Manager (VUM) integration
  • Performance Diagnostics in vSAN Cloud Analytics
  • Storage Device Serviceability enhancement

The ability to upgrade with VUM is a nice touch and continues to improve on the usability and manageability of vSAN. For a full look at what’s new in this release for vSAN 6.6.1 head to this blog post.

Resolved Issues:

There are a bunch of resolved issues in this release and I’ve gone through the rather extensive list to pull out the biggest fixes that relate to my experience in service provider operations and have also extended this to include fixes that relate to backup operations. The majority of what I pick out related to storage, networking hosts and VM operations…the core of any platform, but even more important in the service provider world. The ones in red are specific fixes that relate to issues that iv’e come across…good to see them addressed!

vCenter:
  • First-boot failure occurs when upgrading from vSphere 5.5 or 6.0 to vSphere 6.5 on Windows If an older version of the OpеnSSL DLLs are installed, upgrading to vSphere 6.5 fails to run because the older DLL versions are loaded
  • Affinity rules configured on vCenter Server 5.5 can cause crashes after upgrading to vCenter Server 6.5 Migrating a VM with affinity rules configured while on vCenter Server 5.5 to a cluster that has affinity rules configured on vCenter Server 6.0 or 6.5 can cause vCenter Server to crash.
  • VM Snapshot Size (GB) alarm is not triggered after the VM is powered on. VM Snapshot Size (GB) alarm is reset if the virtual machine is shut down. Alarm fails to trigger after the VM is powered on. This issue occurs in alarms based on VM Snapshot (GB) and Vm Total Size on Disk because their status is altered when the power state of the VM is changed. This issue occurs because disk usage of a VM is the same regardless of the VM power state.
  • When you add ports to a vSphere Distributed Switch you get an error Because of a race condition, when you add ports to a vSphere Distributed Switch you get the error message: Cannot create a new port because number of ports exceeds 2147483647, maximum number of ports allowed on vDS.
  • A runtime exception “Unable to retrieve data about the distributed switch” might occur while upgrading vSphere Distributed Switch (vDS) from 5.0 to 6.5 version When you try to upgrade an existing distributed switch after the vCenter upgrade is completed, the runtime exception Unable to retrieve data about the distributed switch might occur in the wizard and the distributed switch cannot be upgraded. The exception is a result of unexpected value NULL for a LACP property of the distributed switch, instead of TRUE or FALSE, as LACP is not supported for the current version of vSphere Distributed Switch.
  • Host configuration might not be available after vCenter Server restarts After a vCenter Server restart, the host configuration might not be available if vCenter Server cannot communicate with the host. After connectivity is restored, the configuration becomes available.
  • OVF tool fails to upload OVF or OVA files larger than 10 GB If you use OVF tool fails to upload OVF or OVA files larger than 10 GB, the upload might fail.

ESXi:

  • Virtual machine crashes on ESXi 6.5 when multiple users log on to Windows Terminal Server VM Windows 2012 terminal server running VMware tools 10.1.0 on ESXi 6.5 stops responding when many users are logged in.vmware.log will show similar messages to2017-03-02T02:03:24.921Z| vmx| I125: GuestRpc: Too many RPCI vsocket channels opened.
    2017-03-02T02:03:24.921Z| vmx| E105: PANIC: ASSERT bora/lib/asyncsocket/asyncsocket.c:5217
    2017-03-02T02:03:28.920Z| vmx| W115: A core file is available in "/vmfs/volumes/515c94fa-d9ff4c34-ecd3-001b210c52a3/h8-
    ubuntu12.04x64/vmx-debug-zdump.001"
    2017-03-02T02:03:28.921Z| mks| W115: Panic in progress... ungrabbing 
  • An ESXi host might fail with purple diagnostic screen when collecting performance snapshots
    An ESXi host might fail with purple diagnostic screen when collecting performance snapshots with vm-support due to calls for memory access after the data structure has already been freed.An error message similar to the following is displayed:
  • Full duplex configured on physical switch may cause duplex mismatch issue with igb native Linux driver supporting only auto-negotiate mode for nic speed/duplex setting
    If you are using the igb native driver on an ESXi host, it always works in auto-negotiate speed and duplex mode. No matter what configuration you set up on this end of the connection, it is not applied on the ESXi side. The auto-negotiate support causes a duplex mismatch issue if a physical switch is set manually to a full-duplex mode.
  • An ESXi host might fail with a purple screen and a Spin count exceeded (refCount) – possible deadlock with PCPU error An ESXi host might fail with a purple screen and a Spin count exceeded (refCount) - possible deadlock with PCPU error, when you reboot the ESXi host under the following conditions:
    • You use the vSphere Network Appliance (DVFilter) in an NSX environment
    • You migrate a virtual machine with vMotion under DVFilter control
  • A Virtual Machine (VM) with e1000/e1000e vNIC might have network connectivity issues For a VM with e1000/e1000e vNIC, when the e1000/e1000e driver tells the e1000/e1000e vmkernel emulation to skip a descriptor (the transmit descriptor address and length are 0), a loss of network connectivity might occur.
  • An ESXi host might stop responding when you migrate a virtual machine with Storage vMotion between ESXi 6.0 and ESXi 6.5 hosts The vmxnet3 device tries to access the memory of the guest OS while the guest memory preallocation is in progress during the migration of virtual machine with Storage vMotion. This results in an invalid memory access and the ESXi 6.5 host failure.
  • Modification of IOPS limit of virtual disks with enabled Changed Block Tracking (CBT) fails with errors in the log files To define the storage I/O scheduling policy for a virtual machine, you can configure the I/O throughput for each virtual machine disk by modifying the IOPS limit. When you edit the IOPS limit and CBT is enabled for the virtual machine, the operation fails with an error The scheduling parameter change failed. Due to this problem, the scheduling policies of the virtual machine cannot be altered. The error message appears in the vSphere Recent Tasks pane.You can see the following errors in the /var/log/vmkernel.log file:2016-11-30T21:01:56.788Z cpu0:136101)VSCSI: 273: handle 8194(vscsi0:0):Input values: res=0 limit=-2 bw=-1 Shares=1000
    2016-11-30T21:01:56.788Z cpu0:136101)ScsiSched: 2760: Invalid Bandwidth Cap Configuration
    2016-11-30T21:01:56.788Z cpu0:136101)WARNING: VSCSI: 337: handle 8194(vscsi0:0):Failed to invert policy
  • When you hot-add an existing or new virtual disk to a CBT (Changed Block Tracking) enabled virtual machine (VM) residing on VVOL datastore, the guest operation system might stop responding When you hot-add an existing or new virtual disk to a CBT enabled VM residing on VVOL datastore, the guest operation system might stop responding until the hot-add process completes. The VM unresponsiveness depends on the size of the virtual disk being added. The VM automatically recovers once hot-add completes.
  • When you use vSphere Storage vMotion, the UUID of a virtual disk might change When you use vSphere Storage vMotion on vSphere Virtual Volumes storage, the UUID of a virtual disk might change. The UUID identifies the virtual disk and a changed UUID makes the virtual disk appear as a new and different disk. The UUID is also visible to the guest OS and might cause drives to be misidentified.
  • An ESXi host might become unresponsive if the VMFS-6 volume has no space for the journal When opening a VMFS-6 volume, it allocates a journal block. Upon successful allocation, a background thread is started. If there is no space on the volume for the journal, it is opened in read-only mode and no background thread is initiated. Any intent to close the volume, results in attempts to wake up a nonexistent thread. This results in the ESXi host failure.
  • SSD congestion might cause multiple virtual machines to become unresponsiv Depending on the workload and the number of virtual machines, diskgroups on the host might go into permanent device loss (PDL) state. This causes the diskgroups to not admit further IOs, rendering them unusable until manual intervention is performed.
  • Unable to collect vm-support bundle from an ESXi 6.5 host Unable to collect vm-support bundle from an ESXi 6.5 host because when generating logs in ESXi 6.5 by using the vSphere Web Client, the select specific logs to export text box is blank. The options: network, storage, fault tolerance, hardware etc. are blank as well. This issue occurs because the rhttpproxy port for /cgi-bin has a value different from 8303.This issue is resolved in this release.
  • vSphere Storage vMotion might fail with an error message if it takes more than 5 minutes The destination virtual machine of the vSphere Storage vMotion is incorrectly stopped by a periodic configuration validation for the virtual machine. vSphere Storage vMotion that takes more than 5 minutes fails with the The source detected that the destination failed to resume message.
    The VMkernel log from the ESXi host contains the message D: Migration cleanup initiated, the VMX has exited unexpectedly. Check the VMX log for more details.

vSAN:

  • Hosts in a vSAN cluster have high congestion which leads to host disconnects When vSAN components with invalid metadata are encountered while an ESXi host is booting, a leak of reference counts to SSD blocks can occur. If these components are removed by policy change, disk decommission, or other method, the leaked reference counts cause the next I/O to the SSD block to get stuck. The log files can build up, which causes high congestion and host disconnects.
  • vSAN cluster becomes partitioned after the member hosts and vCenter Server reboot If the hosts in a unicast vSAN cluster and the vCenter Server are rebooted at the same time, the cluster might become partitioned. The vCenter Server does not properly handle unstable vpxd property updates during a simultaneous reboot of hosts and vCenter Server.
  • Large File System overhead reported by the vSAN capacity monitor When deduplication and compression are enabled on a vSAN cluster, the Used Capacity Breakdown (Monitor > vSAN > Capacity) incorrectly displays the percentage of storage capacity used for file system overhead. This number does not reflect the actual capacity being used for file system activities. The display needs to correctly reflect the File System overhead for a vSAN cluster with deduplication and compression enabled.

It’s also worth reading through the Known Issues section as there is a fair bit to be aware of in Update 1 and that remain from the GA.

Happy upgrading!

References:

https://docs.vmware.com/en/VMware-vSphere/6.5/rn/vsphere-esxi-651-release-notes.html

https://docs.vmware.com/en/VMware-vSphere/6.5/rn/vsphere-vcenter-server-651-release-notes.html

https://blogs.vmware.com/vsphere/2017/07/second-vsphere-client-html5-update-in-vsphere-6-5u1.html

https://blogs.vmware.com/virtualblocks/2017/07/27/introducing-hci-powered-by-vsan-6-6-1/