#topvblog 2016: Place your vote and see my recommendations

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)

Screen Shot 2016-05-04 at 09.56.55

Here you can give your vote. Thanks VMturbo and Eric Siebert to sponsor and execute this event once again.

I am listed with two blogs this year: vLenzker (Fabian Lenz) & 

Read more

UPDATE: #vBeers in Munich: 12th May 2016 – 06:00PM – Augustiner Keller


WHEN12th May 2016 – 06:00PM

WHERE? Augustiner Keller (Arnulfstr. 52, 80335 München)

Sponsored? Nope ;-( (BYOW – Bring your own wallet)

Screen Shot 2016-05-06 at 10.14.24

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.

Read more

How to do the ESXi VMkernel PING: Unknown interface: Invalid argument

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

Invalid Argument

To make it work again make sure to specify the networking stack.

esxcli network diag ping -I vmk2 –netstack=vmotion -H

VMkping suc

Take care since the stack parameter requires a case-sensitive input?

esxcli network diag ping -I vmk2 –netstack=vMotion -H

leads to

Got no data from process:
/bin/ping ++netstack=vMotion -S vMotion -I vmk2 -X

so better use the correct value out of the following command return:

esxcli network ip netstack list



vxlan / vmotion or skip the entry for defaultTcpipStack

If you don’t like the ESXCLI method, just use the -S parameter in the good old vmkping



#VMworld 2015 Barcelona in 187 seconds: A video for the memories

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.

VMworld header

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

Direct link