Skip to main content

vSphere Distributed Switch Part 9 – Migrate Virtual Machine network from Standard Switch to Distributed Switch without downtime

Migrating the virtual Machine network from standard switch to distributed switch is one of interesting task in dvswitch administration. This is one of the task that VMware admin should be aware about. This post i am going to explain the step by step procedure to migrate your virtual machines from the standard switch to distributed switch.
In this post, I am going to migrate few of the virtual machines from the portgroup (VM_PROD_VLAN17) on my standard switch ( vSwitch0) to dvportgroup (DVPG_VM_PROD_VLAN17) on my distributed switch (DSwitch-Production)
Prerequisites for the Migration without downtime
1. Ensure that your ESXi host has been added to dvswitch before initiating this migration. (My ESXi host called 192.168.0.125″ is already added to dvswitch)
2.Ensure that you have network connectivity of your distributed switch uplink is having same or relevant VLANs trunked as same as your standard switch uplink. Compare the configuration of your destination dvswitch uplink with your existing uplink of standard switch and also ensure that they are configured identically on the physical switch also. (My dvswitch uplink vmnic1 and vmnic 3 is having same network connectivity as my standard switch uplink vmnic0)

Procedure

Login to your vCenter Server using vSphere Web client. Select your Distributed switch and click on Actions. Select Add and Manage Hosts option
Select Manage Host Networking option and click on Next
Select the Hosts from the list and click on Next.
Select the checkbox Migrate Virtual machine networking task and click on Next. This task allows you to migrate VM network adapters by assigning them to distributed port groups on the distributed switch.
Select the Virtual machines or network adapters from the below list to migrate to the distributed switch and click on Assign Port Group
Select the  destination dvportgroup from the list for the virtual machines to migrate to and click on Ok.  I have selected DVPG_VM_PROD_VLAN17
Review the Destination Port Group information of the virtual machines and click on Next.
Review your settings selected and click on Finish.
Once the Migration is Completed, My 2 VM’s (Prod-WebServer and Prod-Fileserver) is moved to my dvport group (DVPG_VM_PROD_VLAN17)
The above procedure is more suitable to perform migration of group of virtual machines networking. If you have one or few VM network need to migrated to dvswitch then, you can manually edit the virtual machine settings and Assign the portgroup from list in Network adapter settings to migrate it to dvswitch.
I hope this is informative for you. Thanks for Reading!!!. Be Social and share it in social media if you feel worth sharing it.

Comments

Popular posts from this blog

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
  Issue with Aria Automation Custom form Multi Value Picker and Data Grid https://knowledge.broadcom.com/external/article?articleNumber=345960 Products VMware Aria Suite Issue/Introduction Symptoms: Getting  error " Expected Type String but was Object ", w hen trying to use Complex Types in MultiValue Picker on the Aria for Automation Custom Form. Environment VMware vRealize Automation 8.x Cause This issue has been identified where the problem appears when a single column Multi Value Picker or Data Grid is used. Resolution This is a known issue. There is a workaround.  Workaround: As a workaround, try adding one empty column in the Multivalue picker without filling the options. So we can add one more column without filling the value which will be hidden(there is a button in the designer page that will hide the column). This way the end user will receive the same view.  
  "Cloud zone insights not available yet, please check after some time" message on Aria Automation https://knowledge.broadcom.com/external/article?articleNumber=314894 Products VMware Aria Suite Issue/Introduction Symptoms: The certificate for Aria operations has been replaced since it was initially added to Aria Automation as an integration. When accessing the Insights pane under  Cloud Assembly  ->  Infrastructure  ->  Cloud Zone  ->  Insights  the following message is displayed:   "Cloud zone insights not available yet, please check after some time." The  /var/log/services-logs/prelude/hcmp-service-app/file-logs/hcmp-service-app.log  file contains ssl errors similar to:   2022-08-25T20:06:43.989Z ERROR hcmp-service [host='hcmp-service-app-xxxxxxx-xxxx' thread='Thread-56' user='' org='<org_id>' trace='<trace_id>' parent='<parent_id>' span='<span_id>'] c.v.a.h.a.common.AlertEnu...