RSS

VMWare vSwitch design

30 May

3 questions on vSwitch design:

1-How much vSwitch should I have? single or multiple?

2-Which type of vSwitch should be used? vSS or vDS?

3-should each FCOE port running mix of FC and network flow?

my environment is:

2 piece of 2 10Gb ports FOCE CAN cards per Server

Cisco 5K switches connect to same network VLAN.

EMC vnx5700 with FCOE interface

VMWare version is 5.0.1

I will use vDirector for whole operation.

What I am planning:

1- use as less as possible vSwitch. I am planning to use 1 vSwitch.

reason:

1a-in my environment, all ESXi servers will connect to the same network VLAN, single and multiple vSwitches is same function level on both performance, security.

1b-vSwitch count is not important. but Port Group is more important and could provide the same level of performance, security.

1c-multiple vSwitch is same as single vSwitch function from ESXi software level, all the vSwitch is logically split by ESXi but they are the same from physical level.

2- use only one type. I am planning to use vDS only.

reason:

2a-in my environment, all ESXi servers will connect to the same network VLAN, for vDS or vSS it looks like the same.

2b-it looks like vDirector need all ESXi servers have same vDS vSwitch.

3-  not or do the split the FC and network flow.

reason:

3a- each ESXi server will have 4 SPF ports on two CAN cards to provide enough redundancy on both card level and port level.

3b- 2 ports on the same CAN card will connect to the same Cisco 5K switch.   This will provide port level redundancy when split FC and network flow.

3c- 2 CAN cards will connect to different Cisco 5K switch. This will provide card level redundancy.This will provide port level redundancy when not split FC and network flow.

3d- if I choose to split the FC and network flow on each port as there are two cards with 4 ports, the redundancy level is still on both port and card level with a 99.9999% no-failure rate

3e- if I choose to not split the FC and network flow on each port but use 1 port as network another as FC connection on the same card, the redundancy level is still on both port and card level with a 99.99% no-failure rate. but will make the whole operation more easier.

3f- so the split the FC and network flow decision should based on the cards and the ports on the server. if you have only one CAN card with 2 ports on the server, you will need to split the FC and network flow and get only port level redundancy. if you have 2 CAN cards with total 4 ports on the server, either split or not should be fine to the whole design.

 

What others saying

1. 思科 live 2009 session brkct-2868. 他说到,无需使用多vSwitch来分离数据流量。Link: http://files.netcore.be/Cisco%20Networkers%202009%20-%20All%20Sessions/Breakouts/BRKDCT/BRKDCT-2868/BRKDCT-2868.pdf

a. clip_image001

2. Vmware 高级系统工程师写的文档。没有必要使用多个vswitch 来分离数据流量和sc,vmkernel 的流量。 Link: http://wenku.baidu.com/view/b3a59c8483d049649b6658b0.html

a. clip_image002

b. clip_image003

3. 一个思科专家design的设计,也只用到了单vswitch, 同时该设计也是基于CNA卡的。 Link:http://bradhedlund.com/2009/07/05/cisco-ucs-vmware-vswitch-design-cisco-10ge-virtual-adapter/

a. clip_image005

4. 有一个人说vSwitch 的配置应该要周全的考虑。他列举了一些不好的design会导致的问题:http://etherealmind.com/vmware-vswitch-does-not-scale-design/

a. 简单说就是同一群集的主机应该都绑定在相同的物理交换机上

5. 有一个人说vswitch的数量并不重要,重要的是分好port group. http://kensvirtualreality.wordpress.com/2009/04/17/the-great-vswitch-debate-part-5/

a. clip_image007

b. 要考虑安全,性能,可管理性

c. clip_image009

d. clip_image011

e. clip_image013

6. 10Gbe对vswitch的影响http://vstorage.wordpress.com/2010/05/09/10gige-changing-vmware-vswitch-best-practices/

a. clip_image014

7. 一个人对vswitch功能的仔细研究:http://bradhedlund.com/2010/02/10/vswitch-illusion-dmz-virtualization/

a. clip_image016

8. 思科的人对vswitch的说明:http://faz1.com/blog/2009/08/20/two-vswitches-are-better-than-1-right/

a. clip_image018

9. 思科和vmware一起出的白皮书http://www.vmware.com/files/pdf/techpaper/WP-VMW-Nexus1000v-vSphere4-Deployment.pdf

a. clip_image020

10. Vmware自己的文章:http://blogs.vmware.com/networking/2010/05/vsphere-loves-10gige.html

a. clip_image022

11. Vmware自己的白皮书http://www.vmware.com/files/pdf/techpaper/vsphere-distributed-switch-best-practices.pdf

a. clip_image024

b. clip_image026

12. Vmware networking best practice: http://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.storage.doc_50%2FGUID-6B49866F-7005-4099-84AC-4FB2A1A91F64.html

a. clip_image028

13. VMWARE fcoe支持数量为4,http://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.storage.doc_50%2FGUID-6B49866F-7005-4099-84AC-4FB2A1A91F64.html

a. clip_image030

Advertisements
 
1 Comment

Posted by on May 30, 2012 in VMWare

 

One response to “VMWare vSwitch design

  1. SEO Done for you

    June 13, 2012 at 09:47

    Hi, i believe that i saw you visited my web site thus i got here to return the desire?.I’m trying to find things to improve my web site!I suppose its ok to make use of some of your concepts!!

     

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: