First I have to say that the two methods described in my first post still work in ESXi 5.0 Shell.
Thanks to the new changes made by VMware in ESXi 5.0 we can now use esxcli to get the same result.
There is a big advantage on using esxcli over the other methods. In ESX(i) 4.x and ESXi 5.0 with the old procedure you had to be logged into the host but with esxcli it can be performed remotely using vSphere CLI.
But there is more, thanks to Get-EsxCli cmdlet the same operation can be done using PowerCLI, here it is how.
First we need to setup the esxcli instance.
And now we issue the command using the name of the module as the argument, please pay attention to the syntax.
As you should have imagined this procedure can be used to get info about any VMkernel module in the host, not just the network interface one.