VSS migration to virtual Distributed Switch configuration

Hi all

I am trying to wrap my brain around that and just run into a few problems actually make things work. Please bear with me, I will try and describe the environment that I have and what I'm trying to building with like jargin little I can.

My current vmware environment consists of 3 hosts vsphere 4.x and about 6 different subnets. My primary host vSphere is home to the largest part of the virtual machine and manages 5 different subnets connected to each of 5 virtual switches separated with 1 assigned to each NETWORK adapter. Also, there is a switch of kernel VM with a connection to my NetApp iSCSI. The other vSphere hosts are simple enough, the two are connected to subnet 1 with a virtual switch for it and a switch of kernel VM with a connection to the NetApp iSCSI.

Each subnet in my lab is managed/break through the VLANS on Cisco devices, so I saw that it had to assign any settings VLAN since the power of VMware.

If you refer to the VMWare vNetwork Distributed Switch: Migration and vmware Configuration guide, I am trying to migrate a seup similar to this:

vmware_multiple_vds.JPG

However, I'm running issues when you try to get the int hosts a vDS configuration. I could create a vDS for my root subnet, add one of my hosts vSPhere and migrate the virtual machine to the new port group in this vDS. The Service console as well as the VMKernel remain virtual switches on the host and I can't understand how these migrate to a vDS host without lose the connection.

I'm asssuming based on the number of subnets that I manage between hosts, I'll finish with about a 5-switch vritualDistributed for subnets, each with at least 1 card a vSphere host physical NETWORK link up to the appropriate subnet. In addition to this, I'm assumining I'll need to create a vDS for the Service console and VMKernel (iSCIS) traffic. The Service Console are on the same subnet, some VM most residence on that subnet, separate VSS was created on the hosts to manage separate traffic.

Any help anyone can provide on how to create vDS for SC/vmk traffic and get the associated host migrated to which would be very useful. As I said I was able to create 1 vDS and add a host computer via 1 uplink NIC with the virtual machine, but nothing beyond that seems bad connection.

Feel you please free to ask for additional details, I know it's a lot and maybe a bit confusing. Thank you.

-Bryan

Hello

If I'm correct, when the host is added the vDS and the creation of the vDS Service Console, I have to select an unused NIC and migrate the SC existing to the new group of port... or should I add a second SC for the VSS by using a NETWORK card available and who migrate to the new vDS?

Yes, select an unused physical nic so that you have a physical nic connected to the VSS and the other to connect to the uplink of vDS group and migrate the SC. existing if you have several hosts, vMotion all VM and test to see if the migration without distruption, also works to keep details of the ILO ready incase you need to connect to the console of the server.

This is a very good book white http://www.vmware.com/files/pdf/vsphere-vnetwork-ds-migration-configuration-wp.pdf that provides detailed information about the migration.

All the best.

Kind regards
Arun

If you have found this or other useful information, please consider awarding points to 'Correct' or 'useful '. Regards, Arun VCP3/4, HPCP, HP UX CSA http://kb.vmware.com/

Tags: VMware

Similar Questions

  • Virtual Switch Standard virtual Distributed Switch migration / a physical Uplinku

    Hello community,

    My ESXI 4.1 hostmachines are configured with virtual standard switches as follows:

    -1 xGbit public - network VMKERNEL management

    -2 x Gbit/active - VMotion + pi (VMKERNEL)

    -2 x Gbit/active - storage NAS (VMKERNEL)

    -2 x Gbit/active - VM LAN

    I want to migrate to a distributed virtual switch, but Ami don't know if it's possible. The problem is I onlyy a uplink public and I can't add the physical NIC as the standard switch and distributed virtual switch. IAM looking for a way to migrate the portgroup & physical uplink NIC in one step. Someone knows how to do this without adding a second NIC uplink? Please keep in mind that my vCenter is a virtual machine on this machine.

    Thanks in advance,

    Stephan

    Another person asked a similar question in which I looked at How to migrate from a vSwitch to the switch distributed - see if that answers your question.

  • migration of the distributed switch standard, how much should be created?

    I'm migrating my VMs from standard to distributed switches.  Are there practices for distributed switches how you create?  Vmotion traffic must be on a separate dvswitch?  My plan was to a dvswitch for vMotion and the other for my VMs and mgmt of ESXi servers.  OR would they all simply in the same switch?

    Thanks in advance.

    Do not forget that each vDS need your own uplinks (physical network interfaces)... If you have enough rising, you can create several vDS, but with a small number of uplink, a better approach is to create just a single vDS and a group of ports for each type of traffic (vMotion, mgmt, VM)... and you can specify the uplink for each port group to use by using the configuration of aggregation and failover.

  • VMware vNetwork Distributed Switch Configuration

    Hello

    Please suggest... As I intend to configure VMware vNetwork Distributed Switch, I have question if my vCenter comes down to will my vm to communicate with the external network or not?

    Thank you

    Hello

    very good question, yes even your virtual machines can communicate with external networks because ESX/ESXi contain hidden vSwitch,

    For more information the article below

    http://www.google.co.in/#sclient=psy&hl=en&source=hp&q=How+VMware+vNetwork+Distributed+Switch+work+if+vCenter+fail+site%3A+blog.srinfotec.com&pbx=1&oq=How+VMware+vNetwork+Distributed+Switch+work+if+vCenter+fail+site:+blog.srinfotec.com&aq=f&aqi=&aql=&gs_sm=s&gs_upl=1070l6889l2l9388l13l13l0l0l0l2l440l2757l0.8.4.0.1l13l0&bav=on.2,or.r_gc.r_pw.&fp=b2a44f43975a6a66&biw=1366&bih=647

    or

    http://blog.srinfotec.com/?p=326

    concerning

    Kardous

  • Virtual distributed switches

    I'm trying to implement virtual switches distributed in vCenter. I created the distributed switch, then port groups. When I RT. Click the distributed switch > add a host, there is no available host. I have 3 hosts in a cluster, but I don't see one any of them. Any ideas how to add? We have a license from the company. Enterprise Plus it takes to add hosts? I think that would not allow you to add the distributed switch, if that were the case.

    Thank you

    Scott

    According to this document , you must use more Ent license for dvSwitch.

    I have a question, how have your host NIC and how many of them already used in VSS (Standard vSwitch)?

    -= If you have found this note/response useful, please consider awarding points to 'Correct' or 'Useful', thank you! =-

    MCTS, VCP

  • Switch Standard virtual and virtual distributed switch

    How to migrate the virtual machine to switch vNetwork Standard to a vNetwork Distributed Switch, where can I get more information? How to set up?

    Thank you

    I think that's what you're looking for

    It's pretty easy actually, I have not you, but once I had to manually migrate the 120VMs to one portgroup to another, now, it is quite easy to use GUI version 4.

    Migration of virtual machines between vSwitch or exchanges of vDS or dvPortgroups

    http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1010612

  • virtual distributed switch issues

    We're going from the standard virtual switches to virtual switches distributed in the coming months.

    We will use the Cisc00 1000v. The supervisor module runs on hardware, Cisco 1010.

    My questions are.

    1. is it better to keep management on virtual if possible standard switch connections?

    2. our Virtual Center servers are virtual machines should I move them to physics?

    This is why I generally prefer vDS with LBT, NIOC & SIOC; with this configuration you could use two connections rising 10GbE and be perfectly fine.

    Just use the standard pool and put the secondary 4th uplink for all networks.

    See you soon,.

    Paul

  • 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}
    
  • Need help distributed switch

    My lab at home is built entirely in ESXi 5. In other words: a physical host with two VirtualHost ESXi ESXi 5 remaining with at. My data store is a race off the coast of SAN virtualized FreeNas.

    The question that I meet is when I create a Virtual Switch distributed and the establishment is looking for a physical network card. Is there a way to get around this? I could create a vDS to a virtual NETWORK adapter? If so, how?

    Your help wil greatly appreciated.

    The wizard could cause the interruption very you speak if she were to offer this option ;-)

    In avoiding or minimizing disturbance is a challenge of the migration of the distributed switch standard, in a lab like this is less of a concern, of course, imagine if it were a production environment! If you were to follow an approach to the real world, you would look to have all your switches using grouping of NETWORK cards in a first time, the process would be:

    0 migrate virtual machines on a host

    1. remove 1 NETWORK card in the standard switch NIC team

    2. create the distributed switch and add the host by using the NETWORK card removed in step 1 as the first uplink

    3 migrate or create the ports for the distributed switch group

    4. remove the remaining standard switch NETWORK card and add it to the distributed switch

    5. proceed to the next host

    I would complement the management process of network cards on a per host basis, of course, you just create a single switch distributed in total.

    Who is?

  • vSphere update your distributed switch 5.1 to 5.5

    Hi after that the upgrade to vsphere vsphere 5.5 5.1 and using vsphere distribution swtich to VDS needs to upgrade to 5.5 see a screenshot in attachment.

    The VDS 5.5 upgrade will cause failures or packet drops?

    The upgrade of virtual distributed switch won't cause any downtime. It is a non-distrayant operation, you should not see any package drop.

    -A

  • Migrating from a distributed virtual switch pass

    I have a cluster that is approved for business-more.  I would like the host to a distributed switch.  The configuration of the virtual switch is as follows:

    4 NICs connected to a host, the NIC are part of an EtherChannel.  The network adapters are teamed up with ip route based on the hash of the IP.  All network adapters are connected to the same vSwitch with port groups created for access to the different VLANS

    I did the following to try to migrate to the new distributed switch: I broke the EtherChannel and removed three network adapters on the virtual switch and assigns them to the distributed switch.  At the same time grouping NETWORK adapters on the virtual channel switch based on the originating virtual, we changed the port ID.  I then migrated the service console more for the new switch successfully distributed.  I have created groups of ports on the virtual switch.

    The question is when I re - create the EtherChannel falls hosts on the network.  I have noted the following: "see attachment".

    Anyone using EtherChannel with distributed switches?

    Any help would be appreciated...

    How to configure etherchannel on your Cisco switch? You may not use LACP or PAgP. You must use "channel-group mode on.

  • Full migration to a distributed virtual switch

    Hi all

    When an ESX Server is first installed, it uses a switch vNetwork standard for COS as vswif0.

    When this server is added to the server Vcenter, the Vcenter contacted with ESX vswif0 via the standard switch.

    What is the process to move the vswif0 vDS? Is this possible via CLI?

    A new vswif to create in the vDS with a new uplink, remove the ESX the Vcenter and add it with the new ip vswif and then delete the old vswif of the standard switch.

    Is there a better way to do it?

    Kind regards

    Sharath

    It's better if you could refer to vSS to vDS migration TSB practice.

    In the doc mentioned about 2 x posible to migrate:

    1. the host migrate with some distruption to virtual machines

    2. the host migrate without distruption to virtual machines

    So, I prefer option 1, because you only have a physical nic involved.

    This option includes two steps:

    A. migrating from virtual port (console service etc.) first--so you can always manage ESX

    B. Migrate machine virtual network (Distruption on the network of the virtual computer until step B)

    Host migration with a few disruptions to virtual machines

    The process as outlined in step 3 of the chart includes two substeps:

    A. migration vmnic and virtual ports (VMkernel and Service Consoles) ports can be migrated in one step of

    vCenter Server.

    B. migration of VM networking where virtual machines are migrated from vSS Port port vDS DV groups groups.

    If all vmnic is migrated in step A, then all the virtual machines will lose network connectivity until step b. step B can follow quickly after (that's the step A

    up to the speed of the operator), but active sessions will probably drop. However, VMs may stay lit.

    vcbMC - 1.0.6 Beta

    Lite vcbMC - 1.0.7

    http://www.no-x.org

  • Switch std to distributed switch migration.

    I have 2 Dell T710 with 6 NIC cards.

    I configured on the 4 standard vSwitches.  Each standard vSwitch is connected to a physical network adapter card.

    I have a vSwitch for manage management, one for vMotion for iSCSI and one for traffic from the virtual machine.

    The reason I set up is to put the vMotion, iSCSI on a different NETWORK card and so another port on the physical port in order to get the maximum flow.

    Now, when I tried to configure a switch to vDistributed.  I was reading this document from vmware (http://www.vmware.com/files/pdf/vsphere-vnetwork-ds-migration-configuration-wp.pdf) and there seems to be all the VLAN based.  In the vDistributed switch, I create the port group, and then associate the group the dvUplink ports and the dvUplink will map to the physical NETWORK adapter on the host.

    I don't seem to find an option to specify the Group of ports on the dvPortGroup if East of vMotion, management and/or iSCSI traffic.

    I'm missing something.

    Can someone tell me some good practices of switch vDistributed?

    Thanks for the information and have a good year.

    Anthony.

    ATC wrote:

    I don't seem to find an option to specify the Group of ports on the dvPortGroup if East of vMotion, management and/or iSCSI traffic.

    I'm missing something.

    You will need to go to the host tab configuration, management network, distributed switch - then "virtual cards" - the Vmkernel ports for the distributed switches.

  • VNetwork Distributed Switch virtual cards

    Trying to get my head around e-cards in the distributed switch.

    In standard switch, I understand the hierarchy like this:

    vSwitch (upper level)

    groups (including the kernel) port (2nd level)

    physical cards (identical to "vmnic..") (join vSwitch)

    I do not understand the hierarchy for the distributed switches.  The use of the term virtual card throws me a loop for.  I consult the virtual map of term as something that you "attach" to something (vswitch etc...), not something you add.  For example, when I go in manage e-cards and select migrate existing adapters, I give you the choice of console and vmotion.  I find the console and vmotion as groups of ports and not e-cards.  Any help to understand this would be appreciated.

    Thank you

    From page 36 of the Guide de Configuration ESX (http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_esx_server_config.pdf):

    Virtual network cards manage services network host on a vNetwork Distributed Switch.

    You can configure the console service and VMkernel virtual cards for an ESX host by a partner

    vNetwork Distributed Switch or by creating new virtual maps or the migration of existing virtual cards.

    When you migrate a virtual network adapter, you should migrate the service or VMkernel console since a standard vSwitch to a group of ports in the vNetwork Distributed Switch.

    -

  • Distributed switch migration

    Hello

    We would like to migrate from standard switches to a distributed switch. Currently, we use different VLAN.

    Could someone help me on how to implement this migration, favorably without any downtime?

    Thank you

    Steven

    You can also have a look at this useful document: http://vmware.com/files/pdf/vsphere-vnetwork-ds-migration-configuration-wp.pdf

    and if the info is useful, don't forget to serve point accordingly (useful/correct)

    concerning

    Jose Ruelas B

    http://aservir.WordPress.com

Maybe you are looking for