If you have a black-screen on the vSphere console (no matter if using .NET client, Web-Client, Remote-Console, etc.) typically the following things help you out:
Having the correct port opened between your client and the ESXi host where the virtual machine is running on (TCP: 903)
Correct working DNS: Your client must be able to lookup the ESXi FQDN
For sure there are many more things… most of them are well documented nowadays… so check them out.
There might be another reason if you use Windows 10 or Windows 2012 R2 (Not sure how it is in the older versions) where the symptoms (a black screen) might be similiar, but the problem is not vSphere related (even though it seems to be).
As every year Eric Siebert started the collection for votes regarding the best blogs within the virtualization field.
Caused by the great blogging-landscape I don’t see any chance to come close to the top 100 area. But still I hope to gain one or the other vote within the new blogger category (vLenzker.net exists for around 6 months right now)
Sponsored? Nope ;-( (BYOW – Bring your own wallet)
I am impressed about the amount of people interested in such an event and Doodle has decided. We will have a Munich #vBeers meet-up on the 12th May 2016 – 06:00PM. If you are interested please don’t hesitate to sign-up here.
Over the years one of my favourite tool when troubleshooting network problems in the vSphere world was vmkping. It allows us to send an ICMP request based on a specified VMkernel port (perfect for troubleshooting vMotion/vXLAN problems).
With ESXCLI NETWORK DIAG PING a nice wrapper for the ping tool was implemented into the ESXCLI namespaces, so that we can use this command remote via vCLI oder even through the PowerCLI cmdlet.
Unfortunately in vSphere 6.0 the command doesn’t work anymore as it has been before (in case that you do NOT use the default networking stack). VXLAN, vMotion and Provisioning traffic can now be configured to use a seperate tcp/ip stack (dedicated routing/arp tables).
Once you use such a non-default-VMkernel port via ping or the according ESXCLI command you receive the following error:
Unknown interface ‘vmkX’: Invalid argument
To make it work again make sure to specify the networking stack.
VMworld 2015 is over and I still haven’t processed all the experiences, information, talks. Nevertheless I have processed all of the small videoclips I made during #VMworld with my iPhone.
Some people might know that I always like to create small videos (you find them on youtube as well) of the awesome trips,travels and journeys I am on. It is great to have a short summary of some experiences a few years later and therefore I did the same with the VMworld material I created during the last days.
I hope you enjoy it and hope to see a lot of the guys I met during this VMworld next year again (in Las Vegas & Barcelona).