Tagged in: VMware vSphere

repost: VMware ESXi Release and Build Number History as of Dec 15 2017

Repost: VMware ESXi Release and Build Number History as of Dec 15 2017

The following listings are a comprehensive collection of the flagship hypervisor product by VMware. All bold versions are downloadable releases. All patches have been named by their release names. Please note that the ESXi hypervisor is available since version 3.5.

 

So I am still learning and when i went to download esxi i was unable to download version 6.5  and it would only allow me to download version 6, being a newbie and assuming there were no major differences beween version 6 and 6.5, I did so.

But now with hindsight i understand that was not the case and i am reposting this excellent article on VMwares build history to help you avoid falling in the same trap

VMware ESXi Release and Build Number History

So what’s the difference?

the main difference apears to be with vSphere, having moved from a client app system to a HTML5 interface,  now  seeing as its a complete interface change it would be better to learn that.  But have no fear all is not lost, i now have the perfect opertunity to look into upgrade paths and learn about that!

Anyway keep tuned for the next insallment

Tchau for now.

Phil

 

 

Installing a server on our hypervisor with vSphere 6.0

Installing a server on our hypervisor with vSphere

So, where are we?

We have a virtual server with exsi hypervisor running on as a base for a virtual lab,  now as a (out of touch) windows domain admin i think installing windows server to refresh myself is a good a place as any to start. Since the last time i administered a domain was when server 2008 R2 was new and starting to get adopted, i figure ill grab myself a evaluation copy of windows server 2016 and see whats new. So I’ve grabbed an ISO of that and im ready to get started.

So here i am, a vSphere front screen,  now Inventory, Administration and Recent Tasks, seam like reassuring fields to have connecting to a hypervisor, especially when you can see power events in t the tasks pane.  looks like i’m good to go.

Now as a noob, I must confess it isn’t entirely obvious where to go to start creating virtual machines, but hey,  i figure inventory is the most likely of the options presented to me.

so opening inventory i find:

 

After that brief moment of confusion, everything is much clearer now another MMC-like window with a nice explanation of what a virtual machine is and a nice “create new virtual machine link”

that’s more like it, now i’m happy again, so lets do that and create a Virtual machine  for windows server 2016.

Up comes another great Wizzard,  prompts you for each configuration option.  Now this is so quick and easy i am basically going to accept defaults at every stage where possible, after all a vanilla 2016 install must be one of the most common tasks performed and i want to see how it does.

Just calling it testvm for now

again default storage location.

I changed from the default, to server 2016 (64bit).

Default nework configuration looks good to me.

again I accept the defaults, reducing the disk to 10Gb assuming i can always grow it if necessary

Click finish, and in a blink of an eye, its done and all i have to show for it is a new item under inventory;- testvm

looks like it worked, lets see if we can get windows installing on it

nice to not the create virtual machine task is registered in recent tasks, lets click on testvm and see what we can do,

first thing i notice is we get a toolbar with play pause and stop buttons,  hitting the play button.

does very little. apart from putting a play icon over the virtual machine, and adding a power on virtual machine event in the task log.

ok makes sense, its for virtual servers, which are usually headless and remote, and from past playing with virtual machines at cambridge i know i need to connect to the console of the virtual machine. lucky for me in the new toolbar one of the icons has a hover over tooltip that says “launch the virtual machine console”, so i hit it:

and i’m greeted by a failed pxe boot screen,  again makes sense i haven’t given it an install media and the VM is network booting by default. very useful for remote installs..

so we need to give the virtual machine a install media, i have an iso and as i’m too lazy to burn it i will try and mount it, so closing down the console and shutting down the vm, lest see if we can mount the iso to install from.  Right clicking on the testvm i have an option to edit settings..

now under CD/DVD drive Device type we have client device with a message telling us to power on the device then click on the connect cd/dvd button in the toolbar.

sounds sensible, lets try that..

on the 3rd reboot i worked out to press F2 to enter the bios of the VM in order to give me enough time to mount the ISO to boot from it.

now im not going to talk you through installing windows, i’m sure you are capable of that,   and in my next post i will mention any hurdles i had.

off to install windows, hope you enjoyed it.

Tchau for now

Phil

My vSphere 6.5 Upgrade Checklist – painful : Repost

I ran across this post when reviewing VMware vSphere 6.5 upgrade best practices via google.

I like to read about others and what they experience while upgrading prior to running through a upgrade myself.

 

by Michael White

https://notesfrommwhite.net/2017/01/29/my-vsphere-6-5-upgrade-checklist-painful/

 

“Yes, this has taken me a while to get too. And it took me a while to do as well. Now that I work at Veeam, and while I have used Veeam products for many years, now I need to work my lab like a Veeam customer. vSphere 6.5 is a big deal for me, and it has a lot of new stuff in it that I am looking forward to so I have been waiting anxiously for Update 1 for Veeam that supports 6.5. It is here now but there is still one more tool of mine that is not 6.5 capable but I am tired of waiting for it. It is the VMware Infrastructure Navigator (VIN) and I find it most useful. BTW, I do this article, and then with it as a plan I do the upgrade. After that I update the article with anything I learned and then finally I publish. I will keep in this article the problems I had in case it helps someone.”

I thought it was worth the time to read.

Roger L

 

Opvizor Inside the Dashboard.

This is my first post on a series of posts about opvizor. http://www.opvizor.com/ Opvizor is a predictive analysis and issue prevention tool.

In my previous post, Getting Opvizor Working by Michael White worth a read. Michael outlines the install process. I will continue , assuming you have setup the product.

 

Once we login to the webpage at https://opvizor.com/login/  we see a dashboard. Where to start?  That is a lot of information.

In the top left you have the environmental overview. This includes your issues per cluster, host, VM, datastore, and network. As you can see I have induced lots of issues into my lab.

vmware vsphere opvizor home

Let’s dig into each.

 

Overall Status

vmware vsphere opvizor overall Statistics

Overall Statistics

vmware vsphere opvizor overall Statistics

Statistics by Upload

vmware vsphere opvizor Statistics by Upload

Issues by  by Upload

vmware vsphere opvizor Issues by  by Upload

Top 5 Largest Datastores

vmware vsphere opvizor Top 5 Largest Datastores

Top 5 Entities by Issue Rate

vmware vsphere opvizor Top 5 Entities by Issue Rate

Top 5 VMs by Snapshot Usage

vmware vsphere opvizor top 5 snapshots

 

Yikes, that seems a little large doesn’t it?

 

Top 5 BMs by Memory Usage

vmware vsphere opvizor Top 5 BMs by Memory Usage

These are fairly self explanatory. But we can dig into each to get more information from this screen.

 

If we click the small table icon  vmware vsphere opvizor expand icon next to Top 5 Larges Datastores

 

vmware vsphere opvizor Top 5 Largest Datastores expand

 

Here we can see more information on the Datastores in my lab.

 

This is our first look into Opvizor, of the series.

 

 

Roger Lund