HERE is the best and most complete list of VMWare ports in use I've come across, hope this helps.
Edit - just spotted your second question - although your VMKernel
and VM traffic can be on the same port-group, and makes sense for some
configurations, I wouldn't do this for yours.
I would use;
two NICs for the 'internal' traffic, either one NIC to one internal
switch and another to a second switch or two NICs to the same switch -
both options cover you in case of NIC/cable/switch failure. Create a
new dual-port vswitch and matching port-group for this carrying
VMKernel traffic (SC/VMotion etc.)
the other two NICs for the 'DMZ' traffic, wired to either separate
or the same external switch/es/load-balancers, again for protection
and/or bandwidth improvements and again with a different dual-port
VM-facing vswitch and port-group.
This is very common practice and I think will serve you well, come
back to us if you have any further questions. Oh and ESX will open it's
own FW ports as you switch on certain services (NTP etc) so don't worry
about the servers, just any ACLs/FWs in the way ok.
from http://serverfault.com/questions/99167/service-console-networking
Starwind Software Developer
www.starwindsoftware.com
Kind Regards,
Anatoly Vilchinsky