Skip to main content

vSphere Distributed Switch Part 8 – Migrate VMkernel Network from Standard Switch to Distributed Switch without downtime

This post is in my mind from the long time because lot of people asked me procedures about migrating your existing VMkernel or Service console network from the standard switch to your distributed switch. So I decided to place this migration  setps as part of this distributed switch series of posts. This post will help you to understand detailed step by step procedure to migrate your VMkernel network from standard switch to distributed switch. This step applies to your Service console network too.
In this post, I am going to migrate my VMkernel network (vmk0: 192.168.0.125) of my ESXi host from the standard switch called vSwitch0 to my distributed switch called DSwitch-Production.
In the below screenshot, You can see my the vmkernel network vmk0 is in the vSwitch0 of my ESXi host.
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)
3.It is best practice to have access to remote console of your ESX/ESXi host, when migrating the vmkernel or service console network. This will help to troubleshoot your host if any issues happened.
4.Ensure that the dvportGroups is going to be used for vmkernel or service console is configured to match with the existing port group configuration (VLAN,NIC Teaming) on the standard switch.

Procedure

Login to your vCenter server using vSphere web client and click on your distributed switch (DSwitch-Production). Click on Actions tab and Select Add and Manage Hosts from the options.
Select Manage Host Networking from the task and click on Next
Select your ESX/ESXi host form the list to manage its networking on this distributed switch and click on Next.
Select Manage VMkernel adapters. This option allows you to add or migrate VMkernel network adapters to dvswitch, assign them to dvportgroup, configure VMkernel adapter settings or remove the existing ones.  Click on Next.
Under On Other Switches Section, Select the VMkernel Network (vmk0) on vSwitch0, which is on the port group “Management Network” on the standard switch (vSwitch0) of my ESXi host. Select the VMkernel adapter from the below list and click on Assign Port Group
Select the destination dvportGroup (DVPG-Management Network) in dvswitch (DSwitch-Production)  where you want to migrate your existing VMkernel port group from your standard switch. Click on Ok.
Now Review the Migration options like Source Port group and Destination Port Group. As part of this Migration, ESXi host VMkernel Adapter vmk0 is going to migrate from the port group (Management network) on the Standard switch  vSwitch0 to dvportgroup (DVPG-Management Network) on the distributed switch (DSwitch-Production).  Click on Next to continue.
Analyze the impact of this migration or configuration. There is No impact since we have uplink assigned at the dvswitch. Click on Next.
Review the Selections and click on Finish to complete the migration
After the migration completed Successfully,  You can see the VMkernel adapter (192.168.0.125) is in the distributed switch (DSwitch-Production) and in dvportgroup called DVPG-Management network.
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...