Upgrading the virtual network to use NSX is not a heavy or large task. It can be, depending on what you are doing, but the basics are fairly straightforward. These basics are not the wholesale replacement of your existing virtual network. They are not the inclusion of new forms or routing in your virtual environment. The are the addition of NSX on top of what you already have. Once you have NSX in place, then you can dream, plan, and adopt those better ways of managing and creating virtual networks. Continue reading vSphere Upgrade Saga: NSX in 8 Easy Steps
Once I upgraded to vSphere 6.5A, I was no longer able to upload OVF or OVA files through vCenter using either of the web clients. It complains in both cases that I am not running vCenter 6.5. This is a known bug. For more information, see KB 2148007. However, there is a solution: use ovftool.
This was a painful upgrade, but I had lots of help from various sources. The main element is to ensure you follow the vSphere Update Sequence. Update everything in that specific order: do not differentiate. This is important, as some things will not upgrade if they are out of order. This part of my vSphere Upgrade Saga upgrade was far from smooth.
VMware has the HTML5 vSphere/vCenter Client constantly under development. Yet, would you use it? Would I? The client is woefully incomplete for the entire VMware product suite but seems to have the basics done well. Here are a few tips for keeping this client up to date, as well as what seems to be missing for day-to-day use.
At the moment, I am waiting for several updates on VMware products to allow an upgrade to vSphere 6.5. Specifically, I am waiting on an upgrade of NSX and VIN that are supported by vSphere 6.5. The other tools I use should be fine with 6.5, but without those, I cannot upgrade. The vSphere Upgrade Saga continues with the following updates.
I run multiple iSCSI servers, ranging from HPE StoreVirtual (must trusted) and Synology Server (tertiary server) to my own CentOS 7 base iSCSI server (least trusted). All run over 10GB links. In general, iSCSI usually works quite well. But for some reason, my CentOS 7 iSCSI server would cause the management agents to fail and vSphere to disconnect from vCenter. This would go on until the iSCSI server was shut down. I use those 10TBs of storage for testing data protection tools and for emergencies. This is a bad thing for the continued support of generic iSCSI. This is also a vSphere Upgrade Saga entry.