A vSAN administrator is working with a network administrator to design a highly resilient all-flash vSAN cluster. Which design factor allows for a highly resilient vSAN network?
A true NIC teaming can only be achieved using LAG, which is only available on vDS. Not to mention NIOC. Therefore, vDS is the foundation for a good vSAN network design.
I would go for Option A
I would go for A
Resilence can be done only once we have vDS configured.
Additionaly for load balance we can use few options there Load Based Teaming, IP Hash and LAG .
LACP can be only implemented on switches that support this configuration
Based on this article
https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan-planning.doc/GUID-031F9637-EE29-4684-8644-7A93B9FD8D7B.html
vSAN uses the teaming and failover policy that is configured on the backing virtual switch for network redundancy only. vSAN does not use NIC teaming for load balancing.
https://blogs.vmware.com/virtualblocks/2017/01/18/designing-vsan-networks-using-multiple-interfaces/
I would go for A
Resilence can be done only once we have vDS configured.
Additionaly for load balance we can use few options there Load Based Teaming, IP Hash and LAG .
LACP can be only implemented on switches that support this configuration
https://blogs.vmware.com/virtualblocks/2017/01/18/designing-vsan-networks-using-multiple-interfaces/
The mean reason to use vDS is to enable Network I/O Control when you have physical NICs shared.
Link Aggregation Control Protocol (LACP) can be used for vSAN network redundancy.
vSAN supports both vSphere standard switches and vSphere distributed switches with either 1 Gigabit, 10 Gigabit, and 40 Gigabit Ethernet network uplinks. VMware recommends using distributed switches.
Uplink the virtual switch to a single layer 2 Ethernet broadcast domain that provides connectivity to all hosts in the cluster. For the best security and performance, isolate the vSAN network traffic to its own layer 2 network segment.
vSphere Distributed Switch has several benefits over standard switches:
• Simplifies management by abstracting networks.
• Reduces the amount of manual work and opportunity for mistakes.
• Allows the use of Network I/O Control.
• vSAN includes distributed switch licensing.
I would go with C answer as per Designin vSAN Network where we have the option of NIC Teaming for HA.
https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan-planning.doc/GUID-031F9637-EE29-4684-8644-7A93B9FD8D7B.html#:~:text=vSAN%20uses%20the%20teaming%20and,NIC%20teaming%20for%20load%20balancing.
https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan-planning.doc/GUID-7BDE36E1-2F06-4699-8D83-3694A0E638B5.html
vSAN does not use NIC teaming for load balancing.
- For hybrid configurations, dedicate at least 1-GbE physical network adapter. Place vSAN traffic on a dedicated or shared 10-GbE physical adapter for best networking performance.
- For all-flash configurations, use a dedicated or shared 10-GbE physical network adapter.
- Provision one additional physical NIC as a failover NIC.
- If you use a shared 10-GbE network adapter, place the vSAN traffic on a distributed switch and configure Network I/O Control to guarantee bandwidth to vSAN.
C - Dedicated
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
jasonv
Highly Voted 4 years, 9 months agoalsmk2
4 years, 8 months agoexam_survivor
Most Recent 3 years, 1 month agoLazylinux
3 years, 4 months agoLazylinux
3 years, 4 months agoHRC
3 years, 6 months agoVirtual_ITTech
3 years, 4 months agodiegof1
4 years, 4 months agosaxon
4 years, 7 months agosaxon
4 years, 7 months agodiegof1
4 years, 4 months agoLCOJ
4 years, 10 months agosettingsgear
3 years, 5 months agosettingsgear
3 years, 5 months ago