Thank you for the reply!! Still some more; Since you wand to use different VLANs, configure the ports on the Cisco switch as "Trunk" (802.1q) ports, and allow the appropriate VLANs. Done. So...
See more...
Thank you for the reply!! Still some more; Since you wand to use different VLANs, configure the ports on the Cisco switch as "Trunk" (802.1q) ports, and allow the appropriate VLANs. Done. So no Cisco "Port Group" which is different then the VMware port group. You may then create different port groups on the vSwitch, and configure them with the required VLAN-ID. Perfect, I was worried I couldn't do this, and it was one of my problems. Please note that a port group for the physical switch port's native/default VLAN must not have the VLAN-ID set! Can you be specific, I am not sure what you are talking about here. Under port groups, I have 3; Servers153, Management Network 154, and VM Network 254. all are explicitly defined on vSwitch0. On the physical Cisco switch, it is a trunk, and assigning a vlan to the trunk makes no sense. With the default settings on the vSwitch, the traffic will be balanced in Round-Robin manner, and fail over to the other vmnic in case of an uplink failure. Perfect TY. In order to allow VMs in different VLANs to communicate with each other you'll need to have routing in place. This can be either a physical, or a virtual router. ESXi itself doesn't provide such an option. Perfect TY!
