Vmknic political grouping vs port group virtual wire vm political grouping

Similar Questions

• No port USB001 virtual in the drop-down list of printer ports

  I started this question in Twitter, but due to character limited in Twitter, I decided to bring the issue to this forum. How can I add a USB port to the list so that I can connect a USB printer. I tried to follow a suggestion by a Microsoft support engineer by selecting the Local port, but it led me to an assistant who would set up my printer as a network printer. my computer on a network, is not autonomous and the printer will not be on a network either. I searched the Internet for the parallel port of PC USB printer port converter but could not find the type that could be a solution. I would be grateful if someone could come up with a suggestion to help me. What point a hopeless case?

  Unfortunately, it's a very difficult situation to deal with.  The best way to install a virtual USB port is to use the printer installation software that comes with (or can be downloaded for) the printer.  What happened when you tried that?

  Sometimes, you can install another printer connected by USB (which will install the virtual USB port) and then move things more.  You - or have you ever had - any printer connected to the computer via USB?

  You sought a parallel to USB converter means that your computer has a physical parallel port but no physical USB port (or at least no functional and available USB port)?

  What is the brand and model of your printer?
  What version of Windows (XP Home, XP Pro, etc.) you have, including the service pack?

  I went through a long thread on this topic about a year ago.  The original poster has succeeded ultimately in the installation of the printer.

  You can take a look for a few suggestions--> http://answers.microsoft.com/en-us/windows/forum/windows_xp-hardware/how-can-i-manually-add-a-usb-printer-port/38424e6c-87f8-4b93-b197-c0d2f70368b8?msgId=e40296bd-71c9-40be-acdf-dfd7597808fe&page=1

• HP Envy X 2 cannot create com port error virtual 577

  Hi all

  Reinstalled Windows 8 32-bit HP ENVY X 2 and updated all drivers (again).

  Try to create the virtual com port with two different Xport and FransonGPSGate programs.

  These programs normally create a virtual Com Port that can be used by e.g. two different programs of maritime navigation at the same time.

  Xport responds: error code error Windows Xport pilot 577 from

  Franson GPSgate responds: unable to create virtual serial ports

  What is the solution for this problem?

  Thanks in advance for your answer!

  Learned a lot the last few weeks on Windows 8.

  I will guide you to acquire the same knowledge for Xport and fully operational Maxsea

  First read: http://www.pcworld.com/article/2027593/windows-8-put-its-hidden-security-features-to-work-.html

  You probably missed it but read what follows:

  "Included in the UEFI is a feature called Secure Boot, which avoids unauthorized operating systems and malicious software from running at startup."

  "Windows, you can type msinfo32 in the start menu search box or invites him to run it to find out the version of the BIOS.

  Within windows 8, I saw:

  -A start secure ACER (old machine): unsupported

  -To a HP Envy X 2 (new machine) Secure Boot: enabled.

  Secure boot disabled in Envy of HP X 2 and

  Xport and my older prog navigation are fully operational new.

  Good wind,

  -No.

• Consolidation and failover for the uplink on the Distributed switch port group

  Hello

  I have a problem with the implementation of a distributed switch, and I don't know I'm missing something!

  I have a few guests with 4 of each physical cards. On the host eash I configured 2 virtual switches (say A and B), with 2 physical network by vSwitch using etherchannel adapter. Everything works fine for etherchannel and route based on the hash of the IP for the latter.

  Recently, I decided to create two distributed switches and move the respective physical ports of virtual switches to this distributed switches. Once again, I want to configure etherchannel and route based on the hash of the IP. But when I open the settings for the uplink port group, aggregation and failover policies are grayed out and cannot be changed. Apparently they inherit configuration also but I don't know where!

  Chantal says:

  Once again, I want to configure etherchannel and route based on the hash of the IP. But when I open the settings for the uplink port group, aggregation and failover policies are grayed out and cannot be changed. Apparently they inherit configuration also but I don't know where!

  You must set the card NIC teaming policy on trade in reality and not on the uplink group more expected.

• Change the VM group vCenter watch NIC port is connected to the old and the new portgroup

  OK, I have built/upgraded to vSphere 5.

  Everything is fine, and now we migrate the virtual machine to the new VDS switches.

  I'm migrating each VM frm the old VSS to their port group concerned on the VDS.

  EVERYTHING is going very well unless I have a few VM, is that when I change VSS port 'The Virtual Machine Network' group the new service VDS 'Network of the Virtual Machine' vCenter shows the VM as being connected to vSwitches/Exchange.

  If you look at the network/host the virtual computer configuration is shown as attached to the VSS and VDS.

  If you use the CLI PowerShell the VM shows that connected to only the VDS, great she is successful, but how can I remove the old switch if he thinks that it is connected to a virtual computer?

  The VM keep in network connectivity.

  I also tried to change the portgroup interface CLI PS and it returns the same result in vSphere.

  Any thoughts?

  Was it virtual machines running snapshot in assets when they have been migrated from VSS for VDS?

  If so, both can be listed in the properties of the VM... In case you need to return the nod on those virtual machines, they will be then be reconnected to the old vs...

  / Rubeck

• USB 0001 virtual port for UsB not found

  When inatalling a Xerox Phaser 8560DN to my laptop HP Win 7 professinal it does not find the virtual USB 0001 port for UsB. I installed the printer even to other laptops and no prblem. When you come to select the port the virtual prot is tehre but not so much in this laptop and HP peole say it is not their problem. Any suggestions on what to do?

  Hello

  You don't see any other virtual ports except USB 0001?

  Follow these steps and check if that helps:

  1. go in Control Panel.
  2 Select all Control Panel items.
  3. open devices and printers.
  4. at the top of the window, select Add a printer.
  5. Select Add a local printer.
  6. If you want to choose a Printer Port, select use an existing port.
  7. in the drop-down list, select USB001 or USB0002 (virtual printer to USB Port).
  8. Select the next button.
  9. in the manufacturers section, select HP.
  10. in the printers section, search for your printer model and select it.

  Note: If your printer does not appear in the list of HP, select nearest LaserJet series model number.

  Click the Windows Update button. WU get the database driver for all HP printers.

  Note: the search may take a while.

  When the search is complete, go back to the HP section and your printer should now appear there. Select it and click the next button.

  Your printer appears in the printer name box, click Next again and the printer will be installed.

  Kind regards
  Amal-Microsoft Support.
  Visit our Microsoft answers feedback Forum and let us know what you think.

• NPIV Virtual Port and WWN VM

  Hi guys,.

  Looking at doc NPIV for VCAP-DCA. Little confusion of Virtual Port, NPIV and VM WWN.

  Some study guide talks on up to 4 virtual port by virtual computer. I understand the virtual port pair is WWN assigned to the virtual machine that can be used as vHBA to the FC fabric. In my lab 5.5, I can assign up to 16 pairs WWN on a virtual machine (8 HW).

  I can see the limit of 4 virtual port in the v4.1 document, but couldn't find it in v5 and v5.5. This limit removed from v5 and later?

  Thank you.

  VMware vSphere 4 - ESX and vCenter Server

  Each virtual machine can have up to 4 virtual ports. Active NPIV VMS are assigned exactly 4 WWN NPIV related, which is used to communicate with the physical host bus adapters through virtual ports. As a result, virtual machines can use up to 4 physical HBA to purposes are NPIV.

  Documentation Centre of vSphere 5.5

  In fact, it is given in the documentation of 5.5. You might have missed it. Here is the link for it

  Documentation Centre of vSphere 5.5

  You can have up to 16 WWN. "The documentation States" ""you can create 1 to 16 pairs WWN, which may be mapped to the first from 1 to 16 physical FC HBA on the host. "

• vShield Manager, virtual son VXLAN, uplink changes of VDS

  Need input on how to resolve this situation without rebuilding the entire cluster care...

  I have vSM for vCloud Director of VXLAN son/virtual networks. As a part of a host updates - migration of all 1 Gbit/s to 1 / 10 Gbps mixed - I was able to reorganize the network adapters on the host computers and add additional total ascending available on the DVS pass that VXLAN is "horse on.» As part of making these updates, I've renamed also uplinks, where mistakes and the discovery of the problem root.

  The errors were to appear when you try to instantiate a new network VXLAN. The vCloud error was pretty impenetrable (as usual), but trying to manually create a new network in vSM provides useful information: the error was a failure to set the mode of collection for the new port group, and it referred to one of the ancient names of uplink.

  After that I added rising additional "dummy" to the DVS and renamed them so that the old names have been included, the virtual wires could be built very well. However, by examining the exchange of news, it was clear that vShield were built using the original, pre-reconfiguration uplink names, ignoring all new uplink: the new rising have been defined as "unused" in the group properties and the 'active' were fake uplinks that had no physical associated cards!

  I restarted vSM, re-entered the credentials of vCenter to try to get it to re - sync with the configuration of the network, but nothing helped.

  I need a way to force vSM list again this DVS who uses VXLAN so that it will end up with the correct uplinks. So far, my Google-fu has failed me, so I hope someone on the Forum might have a clue. Heck, as far as I know, it is a defect that I just discovered...

  Assuming you are using "failover command" set up for your VXLAN, you can try to use the REST API to change the name of uplink in POSSIBLE Manager (almost similar to what you see in KB 2093324).

  Note : I recommend backup or snapshot Manager first! Just in case...

  Headers required such as:

  Accept: application/xml

  Content-Type: application/xml

  Basic authentication

  1 /

  Use GET on the following points for the VDS loan ':
  http:// /api/2.0/vdn/switches

  (of course replace the with the name or the IP address of your vShield/POSSIBLE Manager)

  You will get something like this (this is just a part of it, if you have several vDS):

  DVS-18

  VmwareDistributedVirtualSwitch

  DSwitch

  16

  VmwareDistributedVirtualSwitch

  Datacenter-2

  Data Center

  Cloud

  1600

  FAILOVER_ORDER

  Uplink 2

  Uplink 1

  fake

  2 /

  Modify the parts of that you need. For example:

  ...

  NewLink1

  NewLink2

  ...
  Leave the rest as what.

  3. /

  Then use to execute a 'PUT' to the URL below in the REST client containing the above (in step / 2) change of body (and once again: assuming you are using the failover command).
  http:// /api/2.0/vdn/switches/dvs-18

  Note: Replace "dvs-18" by the id between and to what you in the GET request (in bold and red).

  You should get a HTTP 200 code if everything is OK. See: vShield API Guide around page 154, but personally I think that the part "Edit Group Policy" is not correct.

  It won't change any existing in vCenter port group. You have to change them manually. This change is only for any other creation of sons v VXLAN.

  HTH

  Roland

  PS: I did my best to test and try the example above, but no warranty and no support provided. For support, please open a service request with VMware.

• Cisco 6500's inside the VSS Configuration. Port ID's channel

  Hello

  I have a pair of 6500's Setup with VSS and there is currently only one link between then. However, one end of the link is Po10 and the other end is on Po25.  If I move the Po10 Po25, things will break? It seems to work fine now. I am about to add a second link and I am concerned about the current configuration.  It makes more sense for me to have the two ends of the same binding on the same port channel ID.  I have seen documentation that States otherwise however.

  Interface Port-channel10

  No switchport

  no ip address

  pass the virtual link 1

  MLS qos trust cos

  no consistency mls qos channel

  !

  Interface Port-channel25

  No switchport

  no ip address

  pass the virtual link 2

  MLS qos trust cos

  no consistency mls qos channel

  DTC_6509s_VSS #sh run int Te1/5/4

  Building configuration...

  Current configuration: 116 bytes

  !

  interface TenGigabitEthernet1/5/4

  No switchport

  no ip address

  MLS qos trust cos

  channel-group 10 mode on

  end

  DTC_6509s_VSS #sh run int Te2/5/4

  Building configuration...

  Current configuration: 116 bytes

  !

  interface TenGigabitEthernet2/5/4

  No switchport

  no ip address

  MLS qos trust cos

  channel-group 25 mode on

  end

  DTC_6509s_VSS #.

  DTC_6509s_VSS #sh vslp lmp sum

  Example #1:

  Summary of the LMP

  Information about the link: configured: operational 1: 1

  Peer Peer Peer Peer timers running

  Interface Interface state flag MAC indicator switch (time remaining)

  --------------------------------------------------------------------------------

  4/5/TE1 VSFP VSFP operational 0026.0a26.84c0 2 Te2/5/4 T4 (24ms)

  T5 (s 59.95)

  DTC_6509s_VSS #sh switch port-channel virtual link

  Flags: - Low P - D bundled in port-channel

  I have - autonomous s - suspended

  H Eve (LACP only)

  R - Layer 3 S - Layer2

  U - N running - is not in service, no aggregation

  f cannot allocate an aggregator

  M not in use, no aggregation due to minimum links has not met

  m don't use, port do not associate due to not meeting minimum links

  u - unfit to tied selling

  d default port

  w waiting to be aggregated

  Protocol for the Port-Channel port group

  ------+-------------+-----------+-------------------

  10 Po10 (RU) - Te1/5/4 (P)

  25 Po25 (RU) - Te2/5/4 (P)

  Hello

  It doesn't make a difference if you do both sides with the same channel id or not. The ID of the port channel is a logical interface that does not impact on the etherchannel between them at all. So, you can leave one side Po10 and other like Po25 without problem. Just make sure you have at least one member of the Portchannel Active physical interfaces for not losing your connection to VSS.

  Kind regards

  Mohamed

• The network for ZFS supports "virtual storage device.

  Hello

  I'll put up a 5.1 ESXI machine to test the performance / proof of concept with a "storage device" in a virtual machine on a host computer.

  Right now I use a version of solaris (community edition of nexenta) to test.

  With success, I was able to set up the machine with through disk controllers and add a vswitch initial with a configured vmkernel port and a group of ports for virtual machines. -J' was able to set up comments solaris vm with two adapters e1000 in the vswitch, to be used for the management and the other configured with an address within the same private network that the port on the management... network vmkernel and things seem to work well.

  I wanted to test if there is no improvement in performance using the vmxnet3 adapter and have a completely 'virtual network' dedicated solely to the nfs traffic.

  So I created an additional vswitch without adapters attached to it, with an another vmkernel port and a second virtual machine portgroup and added a vmxnet3 adapter to my "vm storage" to go on this vswitch.

  Before I do, I was wondering if VMCI or anything else already going to do what I want (i.e. ESXi allow communicate with the computer in virtual storage on nfs with speeds above that the limitation of the e1000 adapter would provide by default)

  I say this because my initial test with iozone gave me numbers that seemed beyond 1 GB...

  So, to summarize, the e1000 would be made generally better than 1 Gbit of networking 'local' (in the same host); and (assuming that the handles of the tcp/ip stack of the guest OS UI VMXNET3 well - IE drivers, configuration, the efficiency of the OS.)  the VMXNET3 adapter would be even better.

  It can even better if the uplink to the physical network is faster.  The rate of 1GBit 'link' basically means nothing.

  If someone could point me to a 'best practice' guide or the discussion about setting up isolated networks 'private host' for best performance with NFS virtualized shared storage, I'd appreciate it. My plan is to implement three hosts, with the majority of local data stores to the same host, with little nfs traffic going to each box...

  Well, there's really only 1 way to set up a network of 'host-only', so I don't think you will find a guide BP.

  Also the terminology escapes me a bit, because 'virtual private network', 'private network' have other meanings in other contexts. Don't know what to call a network which has not set the physical network adapters and is localized to a single ESXi host...

  Most called it a network invited only.

• Report virtual distributed switch

  Hello

  I'm trying to write a script that will make my distributed virtual switches.  My Script is as follows:

  $reportcsv = @)
  Get-VdsDistributedPortgroup | Name - descending sort.
  {ForEach-Object
  $vdsportgroup = $_
  $vdsportgroupsec = $vdsportgroup | Get-VdsDVPortSecurityPolicy
  $Report = "" | Select-Object 'Port Group Name', 'number of Ports', 'Binding Port', 'Virtual Switch', 'VLAN Id', 'Type of VLAN", 'AllowPromiscuous',"Changes in MAC"," ' forged passes ""
  $Report. "' Name of the port group ' = $vdsportgroup. Name
  $Report. "" Number of Ports ' = $vdsportgroup. NumPorts
  $Report. "" The link port "= $vdsportgroup. PortBinding
  $Report. "" Virtual switch "= $vdsportgroup. VirtualSwitch
  $Report. "' VLAN Id ' = $vdsportgroup. VlanId
  $Report. "" Type of VLAN "= $vdsportgroup. VlanType
  $Report. "" AllowPromiscuous "= $vdsportgroupsec. AllowPromiscuous
  $Report. "' Change of MAC" = $vdsportgroupsec. MacChanges
  $Report. "" Forged passes ' = $vdsportgroupsec. AllowPromiscuous
  $reportcsv += $Report
  }

  The script works, however when I view the contents of $reportcsv values for AllowPromiscuous, MacChanges & ForgedTransmits presents itself as VMware.VimAutomation.VdsComponent.Types.V1.BoolPolicy.

  Does anyone have any suggestions?

  Thank you

  Frank

  These 3 properties are subject themselves, that's why the object type is displayed.

  You want the property of value of these items.

  BWT, no need to use the fling unsupported for vDS, all news are available via regular PowerCLI cmdlets.

  $reportcsv = @()
  Get-VirtualPortGroup -Distributed | Sort Name -Descending | ForEach-Object {
    $vdsportgroup = $_  $vdsportgroupsec = $vdsportgroup.ExtensionData.Config.DefaultPortConfig.SecurityPolicy  $Report = "" | Select-Object "Port Group Name","Number of Ports","Port Binding","Virtual Switch","VLAN Id","VLAN Type","AllowPromiscuous","MAC Changes","Forged Transmits"  $Report."Port Group Name" = $vdsportgroup.Name  $Report."Number of Ports" = $vdsportgroup.NumPorts  $Report."Port Binding" = $vdsportgroup.PortBinding  $Report."Virtual Switch" = $vdsportgroup.VirtualSwitch  $Report."VLAN Id" = $vdsportgroup.VlanId  $Report."VLAN Type" = $vdsportgroup.VlanType  $Report."AllowPromiscuous" = $vdsportgroupsec.AllowPromiscuous.Value  $Report."MAC Changes" = $vdsportgroupsec.MacChanges.Value  $Report."Forged Transmits" = $vdsportgroupsec.AllowPromiscuous.Value  $reportcsv += $Report}
  

• virtual network card to the physical network mapping and default loadbalancing

  What Virtual Machine virtual network card is map physical NIC.

  For example.

  lets assume Vswitch1 on host1 esx dedicated for the network of the virtual machine (port group) and it has 6 cards network linked to it (vmnic1, vmnic2, vmnic0, vmnic3)

  Load policy (default) Balancing - from the originating virtual port (it balances only outbound traffic through all the nic assigned to vswitch1 right?)

  ESXi host1 <-Vswitch1 (the VM network) <---(vmnic 0-vmnic 3)

  Lets assume that esxi hosting 6 virtual machines and each virtual machine has two network cards configured.  Through some documents, come out of that when the virtual machine is running, it gets connected to the ports of availabe on virtual swicth. say, I turn on the virtual machine in the order VM1, VM2... VM6.

  Vmname virtual adapter port on virtual switch1 Mapping of the physical network adapter                        

  VM1 eth0, eth1 1.2 which mappeed of the physical NIC to eth0, eth1?

  VM2            eth0,eth1                              3,4                                      ?

  VM3            eth0,eth1                              5,6                                      ?

  VM4            eth0,eth1                              7,8                                      ?

  VM5            eth0,eth1                              9,10                                    ?

  VM6            eth0,eth1                              11,12                                  ?

  Since we use load balancing based on the virtual port, can two virtual map of the same virtual machine are mapped to the two physical NETWORK card I want say eth0 VM1 is mapped to the (physical nic) VMNIC0, VM1 eth1 get connected VMNIC1 (physical nic).

  It would be great if you could explain how the virtual network adapters are mapped to the physical NIC Y at - it a command or a script to the list NIC(of all vms hosted on esxi) virtual NETWORK adapter mappings physical in detail.

  .

  sansaran wrote:

  Is there a way to know what virtual NIC to connect to which physical NIC

  With the virtual NETWORK adapter, you hear the virtual card inside the VM? If if and when you use several VMNIC like you, there is no visibility in vCenter (usually vSwitches, we see with Distributed vSwitches).

  However, you can use the command-line ESXTOP tool in the view 'n', for the connection between the virtual machines and the outgoing vmnic.

• Configuring the Network Ports

  Hi all

  In the inventory menu-> networking in my vSphere client 4 I see that someone has set up several 'networks '.

  How to understand which physical ports, they are assigned to, or understand how to route traffic.  I know if I have a DMZ network and a NETWORK card out of the demilitarized zone, how to make a virtual machine use this port?

  Thank you

  C

  Networking is via the use of virtual switches. The physical network are assigned to the virtual switch and the law as "uplink ports. There are three types of virtual switches:

  1. Internal only Virtual Switch - this provides networking remains completely inside you ESX host
  2. Virtual switch with the one uplink port - provides not only the networking between the ports conencted to the switch but provides also for the traffic to a physical network
  3. Virtual switch with 2 or more ports uplink - provides not only the networking between the ports conencted to the switch and provides for traffic to a physical network, but also allows for the grouping of NETWORK cards

  All the networks for your ESX host going thorugh virtual switch management traffic and the vm. There are two types of ports that are connected to the virtual switch:

  1. VMkernel Port - used for your ESXi including vmotion and iSCSI host management traffic. In an ESX host, it is also called the Service Console Port. This port wiill assign its own IP to uniique
  2. Group of ports in Virtual Machine - your virtual machines will connect to the virtual machine port group - it does not get an IP address as the IP {address iss asasociated with the virtual amchine

  When you look at your network in the client VI the right side will be the uplink ports - the physical posrts in your ESX host. The left side will be the or groups connected to the virtual switch ports

• VShield Configuration Manager 4.1 (and how to protect a virtual machine?)

  I have 2 ESXi hosts currently configured in vCenter 4.1.  Before vShield installation Manager, he had 3 vSwitches present on each server; a regular and two distributed.

  • vSwitch0 - connected to vmnic0 - has management and production of network 1 10.168.90.x

  • VLAN 10.1 - VMFN connected to vmnic1 on each host - connects to the private physical network 10.1.x.x

  • VLAN 10.2 - VMFN connected to vmnic2 on each host - connects to the private physical network 10.2.x.x

  After you install vShield Manager in a new virtual machine and then to deploy vShield Zones to each ESXi host, develops a new vSwitch

  vmservice-vswitch - again group of ports in Virtual Machine vmservice-vshield-pg - not connected to any physical cards

  VMS individual vShield-FW created for each host have connected network cards as below

  • Production network normal 1 - VM Network adapter (attached to vSwitch 0).

  • Production network normal 2 - VM Network adapter (attached to vSwitch 0).

  • Adapter 3 - vmservice-vshield-pg network

  I tried to connect my VMs to the network vmservice-vshield-pg in order

  to protect them and place them behiind the firewall.  However, who has

  seem to work, and my VM has lost network connectivity.

  How to protect a virtual machine that needs to connect to the normal production

  Network (on vSwitch0)?  Is there any configuration steps I'm missing?

  What happens if I want to connect a virtual machine or one of its network cards to one of the 10.1.xx

  or 10.2.x.x networks rather than the normal 10.168.90.x network?  What

  additional steps should I make?  The new 4.1 documentation is not

  helped at all, and it seems that the old vShield Zones 1.0 docs are not

  applies to all.

  There is no need to change the virtual computer is connected to the network.

  Just activate/install vShield zones on your hosts and add rules to the vSwitch or data center.

  The virtual machine will be becomes protected if no error is displayed.

• Advice on how best to configure the network adapters and virtual switch in ESX host

  I'm new to VMware and am its implementation.  I got my training a few weeks ago, and now I'm configing my hosts.  I have 3 guests, each have 2 network cards.  There is a virtual switch that ESX creates when it is installed (vSwtich0).  The books said that it is advisable to delete the VM network port of virtual machine that is assigned to the value group default virtual switch and put it on another virtual switch so that you keep your management network separated from the network of the vm for performance and security.  If I do this, all my virtual machines will have to go to 1 NIC b/c I only have 2 NICs per host.  I thought that I have just to keep all my groups of ports on the default vSwitch0 and add my second NETWORK adapter so that I can take advantage of the Association of NICs for redundancy and load balancing.  However, I'm not sure on the performance and the security risks.  Do you have any ideas or advice?  I could also create two virtual switches and put my virtual machines on one which would have a NETWORK card dedicated and put my service and Kernal VM console on another virtual switch with a dedicated network card.  However, in this scenario, I have no fault tolerance or load balancing.  We are a small shop and we have about 10-15 VMs on each host.  I don't have access to b/c distributed switching we paid only for the company (not more).  Thank you.

  Hi and welcome to the forums,

  With 10-15 VMs per box and I guess that I would seriously consider adding two extra cards for each host in the production machines. You could then do something like:

  vSwitch0 - vmnic0, vmnic2, vmnic3 - Console of Service, VM LAN network

  vSwitch1 - vmnic1 - VMkernel

  That would give you redundancy and performance to access your hosts (SC) and also for all your virtual machines. The VMkernel would get a NETWORK card dedicated for vMotion and could be on a separate network. He didn't need redundancy really as if the NIC sank the only issue is that you cannot vmotion virtual machines. In this case you would just move one of the NIC workgroup through to those switches manually.

  If you only have 2 network cards, then I would say having a vSwitch with two attached network adapters and VLAN the VMkernel may be off. I want absolutely to the redundancy of having two cards together.

  Hope this helps,

  Dan