I have 10 NICs on each ESX server.
Current setup with standard license:
vSwitch0 - 2 NICs
VM Network - VLAN22
Service Console
vSwitch1 - 2 NICs
VM Network - VLAN28
vSwitch2 - 2 NICs
VM Network - VLAN20
vSwitch3 - 2 NICs
VM Network - VLAN16
vSwitch4 - 2 NICs
VM Network - VLAN 22
We are going to upgrade our license to Enterprise and add shared storage. So now I need vmkernel for VMotion, vmkernel for FT and vmkernel for iSCSI.
I have 5 different VLANs for VM groups... No trunk ports on switches but each port has its own VLAN configured.
What would be the bets approach?
I was thinking to configure it this way:
vSwitch0 - 2 NICs
Service Console
vSwitch1 - 2 NICs
VM Network - VLAN22
VM Network - VLAN28
VM Network - VLAN20
VM Network - VLAN16
VM Network - VLAN 22
vSwitch2 - 2 NICs
vmkernel - iSCSI storage
vSwitch3 - 2 NICs
vmkernel - VMotion
vSwitch4 - 2 NICs
vmkernel FT
My concern is vSwitch1. since we don't have a trunk ports that ESX are connected to will it be a security issue?
Thoughts?
How I would probably configure it:
vSwitch0 - 2 NICs - Trunk ports
Service Console - VLANxx (NIC1 active, NIC 2 standby)
vmkernel - VMotion - VLANyy (NIC1 standby, NIC2 active)
vSwitch1 - 2 NICs - Trunk Port
VM Network - VLAN22
VM Network - VLAN28
VM Network - VLAN20
VM Network - VLAN16
VM Network - VLAN 22 (why do you need this twice?)
vSwitch2 - 4 NICs (dependig on the storage provider's best practice)
vmkernel - iSCSI storage
vSwitch3 - 2 NICs
vmkernel FT
It's up to you how you configure vSwitch2 and 3 (trunk or not).
André
My concern is vSwitch1. since we don't have a trunk ports that ESX are connected to will it be a security issue?
I don't think this will be a security issue at all, since you most likely don't even get a network connection without configuring trunk ports!
You can set the VLAN on either the port group or the physical switch post. Not on both of them (except I'm missing something).
André
Andre, yes you are right i would have to configure trunk on my switch to support multiple VLANs.
If understood you correctly:
vSwitch0 - 2 NICs
Service Console
vSwitch1 - 2 NICs - Trunk Port
VM Network - VLAN22
VM Network - VLAN28
VM Network - VLAN20
VM Network - VLAN16
VM Network - VLAN 22
vSwitch2 - 4 NICs
vmkernel - iSCSI storage
vSwitch3 - 2 NICs
vmkernel - VMotion
vmkernel FT
Do I need to configure different VLAN on vSwitch0, 2 and 3? if yes, would I need to trunk those ports as well?
How I would probably configure it:
vSwitch0 - 2 NICs - Trunk ports
Service Console - VLANxx (NIC1 active, NIC 2 standby)
vmkernel - VMotion - VLANyy (NIC1 standby, NIC2 active)
vSwitch1 - 2 NICs - Trunk Port
VM Network - VLAN22
VM Network - VLAN28
VM Network - VLAN20
VM Network - VLAN16
VM Network - VLAN 22 (why do you need this twice?)
vSwitch2 - 4 NICs (dependig on the storage provider's best practice)
vmkernel - iSCSI storage
vSwitch3 - 2 NICs
vmkernel FT
It's up to you how you configure vSwitch2 and 3 (trunk or not).
André
VLAN22 was a typo... should be 27
Is there white paper on VMware recommendations for trunk ports and this kind of setups?
Yes, see e.g. http://www.vmware.com/files/pdf/virtual_networking_concepts.pdf and http://kb.vmware.com/kb/1004074
André
Pcerda, i am on 4.0 and planning to upgrade to 4.1
That paper applies to vSphere 4.x