{"id":535,"date":"2021-04-26T12:58:30","date_gmt":"2021-04-26T12:58:30","guid":{"rendered":"https:\/\/robinplomp.com\/?p=535"},"modified":"2022-01-12T14:03:45","modified_gmt":"2022-01-12T14:03:45","slug":"fixing-an-interrupted-nsx-t-manager-upgrade","status":"publish","type":"post","link":"https:\/\/robinplomp.com\/?p=535","title":{"rendered":"Fixing an interrupted NSX-T Manager upgrade"},"content":{"rendered":"<p><a href=\"https:\/\/robinplomp.com\/wp-content\/uploads\/2021\/04\/nsxt.png\"><img loading=\"lazy\" decoding=\"async\" title=\"nsxt\" style=\"float: left; display: inline; background-image: none;\" alt=\"nsxt\" src=\"https:\/\/robinplomp.com\/wp-content\/uploads\/2021\/04\/nsxt_thumb.png\" width=\"244\" height=\"94\" border=\"0\" align=\"left\"><\/a>The process for upgrading the NSX-T managers in an environment is a automated process that works through three managers and finishes the moment all the NSX-T managers are upgraded to the new desired version. Recently I was upgrading a NSX-T datacenter environment from version 3.1.0.0.017107177 to version 3.1.1.0.0.17483065 in my lab environment. The <a href=\"https:\/\/robinplomp.com\/?p=500\" target=\"_blank\" rel=\"noopener noreferrer\">Edge nodes<\/a> and Transport Nodes had already been upgraded successfully. While we where in the middle of upgrading the the NSX-T manager upgrade got interrupted and the NSX-T managers rebooted when the upgrade was not yet finished.<br \/>\n<!--more--><br \/>\nAfter all the nodes where back up again I was not able to logon to the Management environment, the designated Virtual IP (VIP) appeared to be down.&nbsp; When I connected to the first NSX-T Manager machine I was presented with a message indicated that the upgrade had not fully completed. When I executed the following command at the prompt <strong><em>Get upgrade progress-status<\/em><\/strong> I was presented with the following output:<\/p>\n<p><a href=\"https:\/\/robinplomp.com\/wp-content\/uploads\/2021\/04\/2021-03-27-13_46_50-SSDC-Man-PEC-TeamViewer.png\"><img loading=\"lazy\" decoding=\"async\" title=\"2021-03-27 13_46_50-SSDC-Man-PEC - TeamViewer\" style=\"margin-right: auto; margin-left: auto; float: none; display: block; background-image: none;\" alt=\"2021-03-27 13_46_50-SSDC-Man-PEC - TeamViewer\" src=\"https:\/\/robinplomp.com\/wp-content\/uploads\/2021\/04\/2021-03-27-13_46_50-SSDC-Man-PEC-TeamViewer_thumb.png\" width=\"719\" height=\"394\" border=\"0\"><\/a><\/p>\n<p>The output shows that all the upgrade steps where completed successfully. When I connected to the second NSX-T manager machine I got the same output.<\/p>\n<p>I then connected to the third NSX-T Manager, this one was not completed and caused the other NSX-T managers to remain in the upgrading status and the Management VIP to remain unavailable.<\/p>\n<p><a href=\"https:\/\/robinplomp.com\/wp-content\/uploads\/2021\/04\/2021-03-27-13_45_22-SSDC-Man-PEC-TeamViewer.png\"><img loading=\"lazy\" decoding=\"async\" title=\"2021-03-27 13_45_22-SSDC-Man-PEC - TeamViewer\" style=\"margin-right: auto; margin-left: auto; float: none; display: block; background-image: none;\" alt=\"2021-03-27 13_45_22-SSDC-Man-PEC - TeamViewer\" src=\"https:\/\/robinplomp.com\/wp-content\/uploads\/2021\/04\/2021-03-27-13_45_22-SSDC-Man-PEC-TeamViewer_thumb.png\" width=\"958\" height=\"461\" border=\"0\"><\/a><\/p>\n<p>I first executed the command to see the available upgrade packages on the NSX-T Manager machine.<strong><em>&nbsp; get upgrade-bundle playbooks <\/em><\/strong>To resume the NSX-T Manager upgrade I executed the following command:<strong><em>&nbsp; resume upgrade-bundle VMware-NSX-appliance-3.1.1.0.0.17483186 playbook <\/em><\/strong><\/p>\n<p>The upgrade process resumed and completed successfully in a manner of minutes, after which the environment became functional again and Management VIP became accessible again.<\/p>\n<p><a href=\"https:\/\/robinplomp.com\/wp-content\/uploads\/2021\/04\/image-11.png\"><img loading=\"lazy\" decoding=\"async\" title=\"image\" style=\"margin-right: auto; margin-left: auto; float: none; display: block; background-image: none;\" alt=\"image\" src=\"https:\/\/robinplomp.com\/wp-content\/uploads\/2021\/04\/image_thumb-10.png\" width=\"1032\" height=\"489\" border=\"0\"><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The process for upgrading the NSX-T managers in an environment is a automated process that works through three managers and finishes the moment all the NSX-T managers are upgraded to the new desired version. Recently I was upgrading a NSX-T datacenter environment from version 3.1.0.0.017107177 to version 3.1.1.0.0.17483065 in my lab environment. The Edge nodes &hellip; <a href=\"https:\/\/robinplomp.com\/?p=535\" class=\"more-link\">Lees verder <span class=\"screen-reader-text\">Fixing an interrupted NSX-T Manager upgrade<\/span> <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[39,38,22],"tags":[],"class_list":["post-535","post","type-post","status-publish","format-standard","hentry","category-nsx-t","category-vexpert","category-vmware"],"_links":{"self":[{"href":"https:\/\/robinplomp.com\/index.php?rest_route=\/wp\/v2\/posts\/535","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/robinplomp.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/robinplomp.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/robinplomp.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/robinplomp.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=535"}],"version-history":[{"count":2,"href":"https:\/\/robinplomp.com\/index.php?rest_route=\/wp\/v2\/posts\/535\/revisions"}],"predecessor-version":[{"id":715,"href":"https:\/\/robinplomp.com\/index.php?rest_route=\/wp\/v2\/posts\/535\/revisions\/715"}],"wp:attachment":[{"href":"https:\/\/robinplomp.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=535"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/robinplomp.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=535"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/robinplomp.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=535"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}