dingding
Enthusiast
Enthusiast

dependency of distributed vswitch on vcenter server

since config of distributed switch is stored in vcenter server, what will happen if center server is down? is all the VMs using distributed vswitch unaccessible? i know in ESX 3.5, virtualcenter down does not affect the VM's accessibility.

---- Idleness is not doing nothing. Idleness is being free to do anything.
0 Kudos
2 Replies
krowczynski
Virtuoso
Virtuoso

Some info:

receive the same question around dvSwitches almost every week; should I only use dvSwitches or go for a hybrid model? The whitepaper that has been released a couple of months ago clearly states that a hybrid model is a supported configuration but would I recommend it? Or would a pure vDS model make more senses?

Let me first start with the most obvious answer: it depends. Let's break it down and create two categories:

  1. Hosts with two NIC ports

  2. Hosts with more than two NIC ports

Now most of you would probably say who the hell would only have two NIC ports? Think 10Gbe in blade environments for instance. With only two physical NIC ports available you would not have many options. You would have exactly two options(if not using Flex-10 of course):

  1. Pure vDS

  2. Pure vSwitch

Indeed, no hybrid option as you would still want to have full redundancy which means you will need at least 2 physical ports for any virtual switch. Now what would I recommend when there are only two physical NIC ports available; I guess it depends on the customer. There are multiple pros and cons for both models but I will pick the most obvious and relevant two for now:

  1. PRO vDS: Operational benefits. Updating port groups, consistency and increased flexibility with vDS.

  2. CON vDS: If vCenter fails there's no way to manage your vDS

There it is; probably the most important argument on why or why not to run your Service Console on a vDS. If vCenter fails there's no way to manage your vDS. For me personally this is the main reason why I would most like not recommend running your Service Console/VMkernel portgroups on a dvSwitch. In other words: Hybrid is the way to go...

MCP, VCP

MCP, VCP3 , VCP4
vmroyale
Immortal
Immortal

Hello.

Check out: http://www.yellow-bricks.com/2009/09/24/dvswitch/

Good Luck!

Brian Atkinson | vExpert | VMTN Moderator | Author of "VCP5-DCV VMware Certified Professional-Data Center Virtualization on vSphere 5.5 Study Guide: VCP-550" | @vmroyale | http://vmroyale.com
0 Kudos