Hi,
Always consider redundancy. The following VLAN tags are examples only and should match your network design. Also if you want to incorporate vMotion in the future when you have two hosts, simply add another vmkernel port group to vSwitch1 and make each uplink/vmnic on vSwitch0 active for one traffic type and passive for the other and vice versa. This way you still have redundancy and seperation except in the event of a vmnic uplink failure when the traffic types will mix as the standby uplink will become active (hope this makes sense)!
Simple Design
3 x vSwitch
vSwitch0 - Management- (VLAN100) - vmnic0 & vmnic1
vSwitch1 - VM Data - (VLAN200) - vmnic2 & vmnic3
vSwitch2 - Storage - (VLAN300) - vmnic4 & vmnic5
When you use the word SAN, I assume these are IP based, not fibre channel!
Always follow the basic rules,
- Use Network cards in pairs for redundancy should vmnic uplink connections fail.
- Always seperate different traffic types, logically using VLAN's is good, but physical seperation is better especially when you consider how high bandwidth usage traffic streams such as storage could negatively effect the other traffic such as production virtual machine traffic. So yes definately keep storage traffic seperate from data and management traffic.
- Each vSwitch can carry multiple traffic types, via additional port groups, however each vSwitch only has so many physical uplinks/vmnics. If you have multiple traffic types on a vSwitch via multiple port groups then unless you configure one uplink for one traffic type and another for another traffic type via Active, Standby then you will mix the traffic across the uplinks and contention could result in performance degradation.
As for your VLAN's this will depend upon your network infrastructure
Hope this helps.
Regards