This tip is just for Scott. We had a conference meeting, Scott requested an update on my blog. I save the best for you!
We talked about collecting information from vCenter. What about ESX? the "vmware-vimdump" command will print out what vmkernel knows about the system it's running on, which is EVERYTHING!
Let's show some examples:
How do I know which path I'm using to connect to the storage?
How about I want to see the policy used?

What about the storage team ask me for the WWP?
Ok enough on storage, what about virtual switch?
You got the idea. Now you know too much!
We talked about collecting information from vCenter. What about ESX? the "vmware-vimdump" command will print out what vmkernel knows about the system it's running on, which is EVERYTHING!
Let's show some examples:
How do I know which path I'm using to connect to the storage?

How about I want to see the policy used?

What about the storage team ask me for the WWP?

Ok enough on storage, what about virtual switch?

You got the idea. Now you know too much!