{"id":38437,"date":"2019-07-04T14:30:52","date_gmt":"2019-07-04T12:30:52","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=38437"},"modified":"2023-07-16T11:30:30","modified_gmt":"2023-07-16T09:30:30","slug":"vcsa-connected-to-dvswitch-is-unaccessible-after-restore","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/vcsa-connected-to-dvswitch-is-unaccessible-after-restore\/","title":{"rendered":"vCSA connected to dvSwitch is unaccessible after restore"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-38994 size-full\" title=\"vcsa-distributed-switch-unaccessible-after-restore-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/07\/vcsa-distributed-switch-unaccessible-after-restore-01.jpg\" alt=\"vcsa-distributed-switch-unaccessible-after-restore-01\" width=\"602\" height=\"202\" \/><\/p>\n<p>The procedure to <a href=\"https:\/\/nolabnoparty.com\/en\/recover-failed-vcenter-ha\/\">restore a failed vCSA<\/a> connected to Distributed vSwitch (dvSwitch) could be tricky if the infrastructure uses dvSwitches with no <strong>ephemeral port group<\/strong> available.<\/p>\n<p>In an environment running Distributed vSwitches, the <strong>vCSA binding to the dvSwitch virtual port<\/strong> can behave weirdly with the result of losing the connection with the virtual machine.<!--more--><\/p>\n<p>This article has been written for\u00a0<a href=\"https:\/\/www.starwindsoftware.com\/blog\/\" target=\"_blank\" rel=\"noopener noreferrer\">StarWind blog<\/a>\u00a0and can be found in\u00a0<a href=\"https:\/\/www.starwindsoftware.com\/blog\/vcsa-connected-to-dvswitch-is-unaccessible-after-restore\" target=\"_blank\" rel=\"noopener noreferrer\">this page<\/a>. It covers the full procedure to properly restore the vCenter attached to a dvSwitch configuring a <strong>port group as Ephemeral<\/strong>.<\/p>\n<p>&nbsp;<\/p>\n<h2>Restoring the vCSA connected to dvSwitch<\/h2>\n<p>In case of a vCSA failure, the first action normally performed by administrators is the <strong>restore of the VM<\/strong>\u00a0from the backup.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-38996 size-full\" title=\"vcsa-distributed-switch-unaccessible-after-restore-02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/07\/vcsa-distributed-switch-unaccessible-after-restore-02.jpg\" alt=\"vcsa-distributed-switch-unaccessible-after-restore-02\" width=\"589\" height=\"450\" \/><\/p>\n<p>Anyhow, even if the restore completes successfully\u00a0the <strong>ping to the vCSA is not responding<\/strong> and the <strong>VM is unaccessible <\/strong>from the network.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-38998 size-large\" title=\"vcsa-distributed-switch-unaccessible-after-restore-03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/07\/vcsa-distributed-switch-unaccessible-after-restore-03-600x215.jpg\" alt=\"vcsa-distributed-switch-unaccessible-after-restore-03\" width=\"600\" height=\"215\" \/><\/p>\n<p>If you don't have an <em>ephemeral<\/em> port group available, you can't create a new one since you <strong>can't have a dvSwitch without a vCenter Server<\/strong>. Also <strong>changing a mapped port group<\/strong> is not allowed without a vCenter and you will get an error if you try to do this action. How can you properly restore a vCSA in case of need then?<\/p>\n<p>If the vCSA is attached to a dvSwitch to access the network and <strong>all vmnics are assigned<\/strong> to the dvSwitch, the only possible solution to recover the vCSA functionality is the <strong>creation of a temporary virtual switch<\/strong> (vSwitch) using a vmnic detached from the dvSwitch.<\/p>\n<p>When the procedure has been completed, you are <strong>able to ping and access<\/strong> the vCSA once again.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39000 size-large\" title=\"vcsa-distributed-switch-unaccessible-after-restore-04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/07\/vcsa-distributed-switch-unaccessible-after-restore-04-600x238.jpg\" alt=\"vcsa-distributed-switch-unaccessible-after-restore-04\" width=\"600\" height=\"238\" \/><\/p>\n<p>Read the\u00a0<a href=\"https:\/\/www.starwindsoftware.com\/blog\/vcsa-connected-to-dvswitch-is-unaccessible-after-restore\" target=\"_blank\" rel=\"noopener noreferrer\">full article<\/a>\u00a0on StarWind blog.<\/p>\n<p><img decoding=\"async\" title=\"signature\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" alt=\"signature\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The procedure to restore a failed vCSA connected to Distributed vSwitch (dvSwitch) could be tricky if the infrastructure uses dvSwitches with no ephemeral port group available. In an environment running Distributed vSwitches, the vCSA binding to the dvSwitch virtual port can behave weirdly with the result of losing the connection with the virtual machine.<\/p>\n","protected":false},"author":3,"featured_media":38994,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[903,2701],"tags":[2004,2005,936,2006],"class_list":["post-38437","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-vsphere-en","tag-distributed-switch","tag-ephemeral","tag-restore-en","tag-vcsa-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/38437","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=38437"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/38437\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/38994"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=38437"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=38437"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=38437"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}