Again distributed vSwitch in vCenter migration

Similar Questions

• Normal distributed vSwitch using and migration of vSwitch

  Hi people,

  As at the present time I intend to migrate my ESX and ESXi 4.1 in ESXi 5.1 update 1, I wonder if my expectations using DVS is correct.

  I have more than 40-50 VM hosts of joint enterprise & Enterprise Plus (soon to ESXi 5.1u1) managed with VCenter 4 x single Stand Standard 5.1 U1 so to simplify configuring vSwitches, can we establish the DVS?

  To join and implement the DVS, makes ESXi hosts each must have the same number on rising Teddy?

  How can I put all my vSwitches in DVS without causing any major downtime for the current production running VMS?

  With the help of DVS can make life easier restore network settings when a particular ESXi host is unable to start because of a hardware problem or does not upgrade?

  If anyone can help me with the question above that would be greatly appreciated.

  Thank you

  Well, we will try to address all here...

  1. you can only have DVS on ESX servers with Enterprise Plus licenses. Any other license does not support the DVS. Anyway, you can create a DVS where participate only the Enterprise hosts more under license.

  2. the DVS facilitates network management when you have many servers ESX os - if you need to create/modify a GROUP of ports, you don't have no need to go on each ESX Server on your cluster/DC, the configuration is "replicated".

  3. the guests didn't need to have the same number of uplink, but they * must * have the same number of uplink dedicated to the DVS, in order to avoid configuration problems (if you force a dvPortGroup use a spacific dvUplink and one of the hosts has no network cards on this dvUplink, communication fails when a virtual machine is on this defective ESX).

  4 Yf you have spare NICs on your system, you can attach them to the DVS and simply change the portgroup on each virtual machine configuration (there are assistants who can help you to do this on all the virtual machines at the same time for a given portgroup). After that, you can reacomodate the network cards on the DVSs.

  5 DVS are hell for troubleshooting if you get in the case that a problem happens with bonds rising and much more if the ESX management relates to the DVS.

  I hope this helps understand better DVS

• Distributed vSwitch without a vCenter?

  We look at the standard vSwitch migration to distributed vSwitch in the near future, but I need donkeys, possible headaches about that.

  Distributed VSwitch requires vCenter according to various documents.

  1. That means it must be that it is necessary for the configuration only or it will stop working IE. If the vCenter is inaccessible / crashed?

  2. If I would have to reinstall vCenter, what happends to the distributed vSwitches?

  3. If we would migrate ESX servers to a different vCenter, ESX configuration would work?

  When we went from ESX3.5 to ESX4.0, we simply disconnect the old vCenter2.5 ESX Server and connected to the new vCenter4 without any network related problems and could do without any interruption of service for running virtual machines.

  With Distributed vSwitch and vCenter requirement, it's not not clearly documents if we could make such an operation in the future.

  Does anyone have the answers to the questions? Anyone tried?

  A distributed vSwitch using "hidden or proxy" vswitches to perform tasks on the host itself.

  Thus, the vCenter is required only for the configuration, and a host will be

  continue to function if the connection is lost.

  That being said, the config is part of the vCenter, so you will have problems if you migrate or rebuild vCenter.  Here's a previous post that describes some problems and a workaround: http://communities.vmware.com/message/1400976#1400976

  -KjB

• vMotion VLAN\Distributed vSwitch Networking question

  I am facing a strange problem and was hoping someone might be able to enlighten. I have a vCenter cluster that contains 5 hosts. Four of the guests standard vSwitches and a host uses a distributed vSwitch. The four hosts who use standard vSwitches have a NETWORK card dedicated for vMotion network. The only host that uses the vSwitch distrubted has two NICS in a team. I followed the instructions listed here to set up the configuration (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 2007467)

  Three standard vSwitch hosts are able to ping to the active IP address for the host by using the distributed vSwitch while one of the hosts using a standard vSwitch is unable to ping the host by using the distributed vSwitch.

  If it was a problem with the distributed vSwitch or etherchannel configured on the Cisco switch for the collection of NETWORK adapters, I think that none of the other guests could ping the IP address, but they can. I also confirmed that the vMotion VLAN is configured on all Cisco switches and is to be shared between all hosts resources.

  I am at a loss to explain why a host is unable to communicate with the host distributed vSwitch on the VLAN of vMotion. Any help would be appreciated.

  Thank you.

  The problem I was experiencing was due to an incorrect configuration. After talking with a technician from VMWare, he explained to me that you should not use a configuration of etherchannel on the switch that connects to NICs hosts vMotion. The reason relates to the policy associated with the map NETWORK load balancing team.

  For etherchannel configuration work, politics of load balancing for the NIC team must be defined, 'route based on IP hash. You are not able to use this strategy to load with vMotion NIC team balancing. The policy load balancing for a correct vMotion NIC team would be 'road based on the original virtual port code '. This is because a NETWORK adapter is active while the other is standby.

  After removing the switch etherchannel configuration and redo my setup according to the above referenced article, guests may communicate on the network of vMotion of appropriately. I asked VMWare technology if there is no indication as to why the three hosts were working while we were not. He did not have an answer and is surprised that these other three hosts were working with the configuration I had initially.

• Not available to add to Distributed vSwitch to hosts/physical adapters

  It's probably something simple, I forgot, but have not been able to understand...

  Learning of vSphere 5.5 via Virtualization VM Workstation 9. Have many functional things already, to the point where I now both hosts ESXi, datastore iSCSI via standard vSwitches etc. No cluster, but everything works as expected.

  Currently distributed vSwitches research. I am trying to create one, but facing the question that I see not available to add to the hosts/physical adapters dvSwitch... Nothing appears in the list, nor does anything appear under "View Incompatible Hosts", so I can only continue when I choose "add hosts later." It is through vCenter Client and/or vCenter Web Client connected to the server vCenter.

  The two hosts of ESXi have 5 network cards. They have all been used in vSwitches for VMS, the iSCSI management..., so I decided to add an additional NETWORK card for each. I rebooted, ESXi, each of them guests show their new unused NIC under Configuration > network cards... This don't change nothing, always do not appear when you add hosts to the dvSwitch. I also tried to put in a standard vSwitch first on each ESXi host, with no difference. So I thought that maybe you can't see adapters hosts/physics to add to a dvSwitch after that that they have been added to a cluster, so I quickly created a cluster, added two ESXi hosts, no difference. I changed the version of the dvSwitch to 4, 5.5... I tried different settings to maximum number of physical cards by the host from 1 to 8... Nothing helps.

  I hope that I have reason to believe that you can add network individual cards of the hosts who also already have some network cards as used in standard vSwitches uplink adapters?

  Any comments appreciated,

  JH

  -

  Haha... It is even stupider than I thought.

  In order to tackle another question I got one a few days ago, I created a data center extra, with a very similar name. I moved all hosts of this new centre of data at any given time. But when I tried to create the distributed vSwitch, I accidentlly rightclicked the OLD Datacenter (empty). No host there to select a list empty... so of COURSE every time.

  Can someone slap me hard, please?

  JH

• Two vCenter - migration to vCenter Server 5

  Hello world.  I have a vCenter Server 4.1 to exsiting v4.1u1 hosts and production/DEV Essentials Enterprise production management.

  I want to build a new vCenter Server 5.  This new vCenter facility will also have the new databases and vcenter Update Manager, on a separate SQL Server.  I'm not worried about the loss of existing data as each of my existing hosts is also rebuilt to ESXi 5.

  My question is about licensing.  On the this server vCenter, all my license keys are exhausted.  If I build a new server vCenter, how can I add my existing ESX/ESXi servers to the new server vCenter without licenses available?  I realize that if I remove Let's said ESX01 since the existing vCenter server, these licenses go back in the pool on SERVER.  If I can't add ESX01 on the new vCenter server, I used this same license key?  In other words, have the same active key on two vCenter servers, which are not connected or even the same version?

  Clear as mud right?

  Thanks for your time.

  -Dave

  Using the same license key on both instances of vCenter server is actually the only way that you can migrate hosts on the new vCenter Server. I do not think that there is a problem of legal license if you disconnect a host of the "old" vCenter Server - releasing upward CPU licenses - and then assign the license to host again when you connect it to the new vCenter Server.

  In regards to your first sentence. Probably, you break the EULA if you manage Essentials through an instance other than the Server vCenter vCenter server for Essentials.

  André

• PowerCLI to change standard vSwitch network to Distributed vSwitch

  I'm working on a deployment script to build my VMs from a template. After its construction, I need to switch from the network to a dvSwitch. I need help to understand the correct syntex.

  It did not work:

  $vmname = test2008_11

  $vlan = XXX_XX_57_x

  Get - vm $vmname | Get-NetworkAdapter | Together-NetworkAdapter - StartConnected $true - DistributedSwitch dvSwitch1 - NetworkName $vlan - confirm: $false

  Here's the info of powerCLI

  PowerCLI > Get-VirtualSwitch-name dvSwitch1

  Name NumPorts Num Ports Mtu Key Notes
  Available
  ----            --------   ---------- ---   ---                            -----
  dvSwitch1 2474 1500 FC 12 50 f2 a5 b5-64 1 c b2...

  
  PowerCLI C:\Users\bxg4211\Documents\PowerCli\Deploy > Get-VirtualSwitch-name dvSwitch1 | Get-VirtualPortGroup

  Name key VLanId PortBinding NumPorts
  ----                      ---                            ------ ----------- --------
  XXX_XX_61_x dvportgroup-12662 128 static
  XXX_XX_50_x dvportgroup-12676 128 static
  XXX_XX_44_x dvportgroup-12675 Street 128 static
  dvSwitch1-DVUplinks-12654 dvportgroup-12655 static 42
  XXX_XX_00_x dvportgroup-12664 128 static
  XXX_XX_40_x dvportgroup-12674 128 static
  XXX_XX_60_x dvportgroup-12680 128 static
  XXX_XX_01_x dvportgroup-12665 128 static
  XXX_XX_14_x dvportgroup-12673 128 static
  XXX_XX_02_x dvportgroup-12666 128 static
  XXX_XX_13_x dvportgroup-12672 128 static
  XXX_XX_03_x dvportgroup-12667 128 static
  XXX_XX_12_x dvportgroup-12671 128 static
  XXX_XX_56_x dvportgroup-12679 128 static
  XXX_XX_04_x dvportgroup-12668 128 static
  XXX_XX_11_x dvportgroup-12670 128 static
  XXX_XX_57_x dvportgroup-12678 128 static
  dvSwitch1 all dvportgroup-12661 128 static
  XXX_XX_10_x dvportgroup-12669 128 static
  XXX_XX_54_x dvportgroup-12677 128 static

  The Ps and the names have been changed to protect the innocent.

  On the portgroup, the script finds all available ports.

  Then, it checks all virtual machines that already have a connection to this portgroup and removes this Portkey to the list.

  I keep the portkeys in a hash table, because that makes it easy to remove entries.

  $nicTypes = "VirtualE1000","VirtualE1000e","VirtualPCNet32","VirtualVmxnet","VirtualVmxnet2","VirtualVmxnet3" $ports = @{}$pgName = "MyPG"
  
  # Get all the portkeys on the portgroup $pg = Get-VirtualPortGroup -Distributed -Name $pgName $pg.ExtensionData.PortKeys | %{$ports.Add($_,$pg.Name)}
  
  # Remove the portkeys in use Get-View $pg.ExtensionData.Vm | %{    $nic = $_.Config.Hardware.Device |       where {$nicTypes -contains $_.GetType().Name -and $_.Backing.GetType().Name -match "Distributed"}    $nic | %{$ports.Remove($_.Backing.Port.PortKey)}}
  
  # Assign the first free portkey $key = ($ports.Keys | Sort-Object)[0]
  

• vCenter Migration and vDistributed switch problem

  Hi all

  I spend vcenter box intel AMD box. So this means that I won't be able to vmotion right?

  In this sense, I installed a new server vcenter on AMD box and added ESX servers one by one on the new vcenter server except those relating to the vDistributed switch.

  .

  I had problems with vDistributed switch cause if I try to remove a server from the cluster HA, vcenter gives an error because it has connection with the vDistributed switch.

  Please let me know how could remove the old vcenter servers and add new server vcenter.

  Thank you!

  Maybe the article will be useful

  http://KB.VMware.com/kb/1029498

• Distributed VSwitches with vShield Zones

  Hello

  It has been a week since I tried to play with vShield with vNDS.

  Although I followed word by word the administration guide, my protected virtual machines are not able to communicate with the rest of the network.

  What seems strange to me, is that in an environment normal vswitch, the u0 is always linked originally vswitch, linked to a physical interface.

  But if you see the vNDS procedure, u0 and p0 are connected to the VMFN cloned without related physical adapter... so maybe I'm missing something or there is something odd here

  If someone managed to fully configure vShield with vNDS and if so, could you help me please :)?

  Thank you very much

  I think that this could be a problem with the documentation is not not clear in the summary at the bottom the page 32 of Executive Guide. Specifically the step #2 that does sound like the protected and non protected port groups must be created on the same vDS. Steps 1-4 (page 32-34) are only a summary of what to do and lists only very generalized steps.

  The procedure detailed first on page 33:

  -Create the second vDS (the protected) Page 33

  -Creating the dvPort protected group in the vDS second/protected the Page 33

  -Create the unprotected dvPort group in the vDS existing or unprotected. He is the one with the physical card. Page 34

  Ultimately, the insertion is very similar as with the legacy vSwitch. Two virtual switches filled by the vShield, where the protected outside/no switch (physical NIC) uplink and the switch Interior/protected does not.

• Vcenter migration to another machine

  I have a virtual centre running with version 5.1 and build a new virtual center with 5.5 U1a. I would like to move all objects including alarms, permissions, inventory, schedule tasks, and DRS rules. Well let me know how can I achieve this.

  Thank you

  Hi Vinod,

  To do this use the instant inventory.

  Download: InventorySnapshot & #8211; VMware Labs

  Documentation: is a future Virtualization: how to use the instant inventory for vSphere

  All the best,

  Remember to mark this reply 'proper' or 'useful', if you found it useful.

  Anjani Kumar

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

  VMware, Windows

  Consulant

  Email ID: [email protected]

  Website: http://www.Vmwareminds.com

• iSCSI multipath on a distributed vSwitch?

  I read that there are problems with this and I'm pretty positive, I read that it is still not supported in one of the documents ESX4u1 (although for the life of me I can't find this text of presentation this morning).  Is this even a question?  And if so, can someone explain why exactly this is not working?

  I'm documenting a config proposed for deployment using cards dual 10GbE and I do research using iSCSI multipath and dvSwitches.  Which raises another question, on a channel 10GbE same multipathing necessary?

  
  
  -Justin

  If you are talking about the use of links in the port, then you must use conventional switches for this purpose.  It is in the notes version of vSphere

  vExpert

  VMware communities moderator

  -KjB

• Recovery of accidentally deleted vCenter

  We run 5.5 on our hosts and vCenter. and the vCenter VM has been deleted by accident one of the hosts. So, we currently have our guests running in a cluster, with VDS and no way to manage it properly. The VCDB was on a different virtual machine which is still OK, but I need to do it all in place and working again.

  In terms of recovery, what would people recommend? Delete the DB and rebuild it from scratch (I have no real need for historical data)? Or can I reinstall VC and that it points to the current VCDB? Also, I'm better off migration at this point out of VDS hosts for a standard switching? I think I'll have questions, add hosts to an another VC if they carry a VDS created on another VC?

  Hi, if you have vCenter DB intact, so you can install a new vCenter and point to the existing database.  If you do not have a backup of the files system of the former vcenter, so you will have problems with the ssl certificate.  It would be helpful for you http://www.virtualclouds.info/restoring-vcenter-server/

  Regarding the VDS, once you have vCenter and launched, you can resynchronize hosts.  I would not retreat standard switches, here's a good read Distributed vSwitches and vCenter fails, that & #039; s the deal?

• VCenter downwards and no backups

  Hello, I could be walking in an environment where the Vcenter server is down and there may be no backups. Ive been told there are problems with the certificates and the database.  Now, I don't know the details right now, but it's wondering what I have to do if I need to put in place a new Vcenter server and there is no backup of database and certificates are bad?

  I don't know some info.  There are about 6 hosts running ESXi 5.1.  There are on the run from 30 VM.  There is a HA cluster and Vmotion is configured.  not sure whether the DRS.

  If I were to set up a new server Vcenter with new SS and the new database.  Can I just add the ESXi hosts on the new Vcenter server without being troubled for the virtual machine?

  IM basically worried configs Switch network, storage configs and lose this info.  Some virtual machines may need to connect to one network rather than another.  This information would get lost and my VM would lose network connectivity if I just added the new Vcenter Server?  Or ESXi hosts with all this info it would be fine and come?

  I don't like on Performance data or the user, or permissions, roles which can all be setup again.

  Reset the HA cluster should not be a big problem as im assuming that the Cluster info would no more even if the hosts have this info?

  I hope it made sense

  Thank you

  Hello

  You must be totally fine with a few re-estabilishing a new vCenter from scratch and connecting hosts ESXi back once again and then just by creating a cluster and placing it there as well as the good configuration for DTS/DRS/VCA, etc.. This will not affect running Virtual Machines somehow - but just to be safe, I recommend to do this out of hours

  The only thing you will lose is:

  • Resource pools
  • Annotations of VM
  • Custom folder organization

  The rest is retained within the hypervisor itself - if the virtual machines have been on standard vSwitch, you're good. If they were on distributed vSwitch, you want to export the configuration of a current ESXi host, then apply together via Exim vCenter again. Some useful links about that: VMware KB: export/import/restore Distributed Switch configs using vSphere client Web and: Distributed vSwitches and vCenter fails, that & #039; s the deal?

• migration from 4.1 to 5.1 hosts/guests of Nexus 1000V to VDS using CLI power

  Is there scripts out there that will migrate to a host and guests on this respective host of a virtual center of ESXi 4.1 with Nexus 1000v switch, for a new virtual Center 5.1 with a VDS of VMWare ESXi.

  I don't want to upgrade the host 5.1, or guests. only move them from 4.1 to 5.1 Virtual Center and upgrade at a later date

  Maybe can the Gabe migration distributed vSwitch in vCenter new post help?

• vDS and vCenter

  Hello

  Is it true that if vCenter falls down for more than 24 hours we will lose all switches connections vDS?

  Kind regards

  Have you checked this blog?

  http://www.yellow-bricks.com/2012/02/08/distributed-vSwitches-and-vCenter-outage-whats-the-deal/