VMware prezentuje nowy system vSphere 5 i pakiet narzędzi do obsługiwania chmur

On page 5 it says VLAN trunking is qreuierd? Why is that?For example, if you have a dedicated vSwitch0 for kernel and console (and are using the same subnet) and use another, say vSwitch1 for example for guest traffic you would not NEED to use a trunk (at least not on the console / kernel vSwitch adapters).It also states In this example, the management network runs on vSwitch0 as active on vmnic0 and standby on vmnic2. The vMotion network runs on vSwitch0 as active on vmnic2 and standby on vmnic0. You have to specifically define this in your failover policy (it doesn't show this in the doc, it only briefly mentions setting up active/standby)? Also, on ESXi this would only work if you have separate IPs (possible, but not qreuierd ) for management and the kernel, so is this also the best practice on vSphere vs running everything on a single IP/network (I've seen in the past where best, best recommendations were to separate everything, like using 3 vSwitches, management, kernel, guests, is why I ask).Other than that, great document, always love best practices guides. *8)