{"id":2369,"date":"2021-02-07T11:59:28","date_gmt":"2021-02-07T11:59:28","guid":{"rendered":"http:\/\/vpxd.dc5.cz\/?p=2369"},"modified":"2022-01-21T16:55:24","modified_gmt":"2022-01-21T16:55:24","slug":"nsx-t-upgrade-from-3-1-0-0-0-17107157-to-3-1-1-0-0-17483185","status":"publish","type":"post","link":"https:\/\/vpxd.dc5.cz\/index.php\/2021\/02\/07\/nsx-t-upgrade-from-3-1-0-0-0-17107157-to-3-1-1-0-0-17483185\/","title":{"rendered":"NSX-T upgrade to 3.1.1 with few issues."},"content":{"rendered":"\n

\r\n\t\t\t\t<\/span> Post Views:<\/span> 2,480<\/span>\r\n\t\t\t<\/div><\/code><\/p>\n\n\n\n

I updated NSX-T in my lab environment (more about the homelab here<\/a>) from version 3.1.0 to 3.1.1 { more precisely from 3.1.0.0.0.17107157 to 3.1.1.0.0.17483185 }. And during the update I went through few issues, which I was able to solve \ud83d\ude42 Learning curve go up ..<\/p>\n\n\n\n

<\/p>\n\n\n\n

Before you start, read release notes: https:\/\/docs.vmware.com\/en\/VMware-NSX-T-Data-Center\/3.1\/rn\/VMware-NSX-T-Data-Center-311-Release-Notes.html<\/a><\/p>\n\n\n\n

The first step should be to check NSX-T backups and alarms. I did the first, but not the second. So it had consequences.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n\n\n\n\n

Backups were looking good. So I download the upgrade MOB file from vmware.com pages to my computer.<\/p>\n\n\n\n

Then I navigate to my NSX-T manager \u2192 System \u2192 Upgrade and click “Upgrade NSX”<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

“Prepare for Upgrade”.<\/h1>\n\n\n\n

First choose the upload method. In my case “Upload Local MUB file”. Click “Browse” and pick up the previously downloaded MUB file and click “Upload”<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

It took some time to upload 7,5GB MUB file.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Run pre-checks<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Confirm it.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

As I stated before I didn’t check the alarms. So during pre-check, it shows me all the issues I have.<\/p>\n\n\n\n

Issue with edges:
<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Issue with ESXi hosts
<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

I had 2 main issues:<\/p>\n\n\n\n

  1. Two of my ESXi hosts had not enough space in “tmp” directory. NSX-T update needs at least 180MB free space in “tmp”.  To solve this issue I used this KB 2001550<\/a>.<\/li>
  2. ESXi host pst-esx3 was powered off and it was only one ESXi host in one of my clusters. So if there are some running VM’s on it, it will never enter maintenance mode. And maintenance mod is needed to update the ESXi host. The resolution was simple. Turn on the host and put it into maintenance mode manually.<\/li><\/ol>\n\n\n\n

    Once all the issues were solved, I ran pre-checks again, and all statuses become green. <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    Now I can start with upgrading by pressing “Upgrade” button.
    <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    “Check” EULA  and continue.
    <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    Once again confirm an upgrade “Yes, continue”.
    <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n
    \"\"<\/figure>\n\n\n\n

    Edges<\/h1>\n\n\n\n

    I choose a parallel upgrade order plan for my edges. “START”<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    Edges upgrade in progress…
    <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    Upgrade of edges finished successfully. Now I can run post checks.
    <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    All post checks are green “No Edge(s) with issues”.
    <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    Hosts<\/h1>\n\n\n\n

    Clicked on “Next” and continue with the Hosts upgrade. This time a choose “serial” upgrade plan order across groups and hit “Start”
    <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    It take a while to upgrade all hosts.<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    Once all hosts were upgraded I ran “Post Checks” to verify that the upgraded components are functioning smoothly.
    <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    In my case, there was one post-check error. “Post checks are complete. Found 1 Host(s) with issues”
    <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n


    <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    Because in one host group I have only one host in a cluster. Yes, it is the pst-esx3. I must exit the host from the maintenance mode manually.<\/p>\n\n\n\n

    Second post-check ..
    <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    .. finished without any issue.
    <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    NSX Manager<\/h1>\n\n\n\n

    The last object to upgrade is NSX Manager. Hit “Start”.
    <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    Confirm your intentions.
    <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    watch progress. Once the NSX manager is updated, it restarts itself.
    <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    After reboot, login back to NSX Manager, confirm “Customer Experience Improvement Program” and click “SAVE”.
    <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    Go back to System\u2192 Upgrade \u2192 NSX Manager and see the final result.  All should be green\/successful. Hit “DONE”.
    <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    This is how it should look after the upgrade to version 3.1.1 build 17483185
    <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    My upgrade history
    <\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    <\/p>\n\n\n\n

    Good luck with your upgrade.<\/p>\n","protected":false},"excerpt":{"rendered":"

    I updated NSX-T in my lab environment (more about the homelab here) from version 3.1.0 to 3.1.1 { more precisely from 3.1.0.0.0.17107157 to 3.1.1.0.0.17483185 }. And during the update I went through few issues, which I was able to solve \ud83d\ude42 Learning curve go up .. Before you start, read release notes: https:\/\/docs.vmware.com\/en\/VMware-NSX-T-Data-Center\/3.1\/rn\/VMware-NSX-T-Data-Center-311-Release-Notes.html The first … Continue reading “NSX-T upgrade to 3.1.1 with few issues.”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[23,5,8],"tags":[],"class_list":["post-2369","post","type-post","status-publish","format-standard","hentry","category-blog","category-nsx","category-vmware"],"_links":{"self":[{"href":"https:\/\/vpxd.dc5.cz\/index.php\/wp-json\/wp\/v2\/posts\/2369","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vpxd.dc5.cz\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vpxd.dc5.cz\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vpxd.dc5.cz\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vpxd.dc5.cz\/index.php\/wp-json\/wp\/v2\/comments?post=2369"}],"version-history":[{"count":26,"href":"https:\/\/vpxd.dc5.cz\/index.php\/wp-json\/wp\/v2\/posts\/2369\/revisions"}],"predecessor-version":[{"id":2648,"href":"https:\/\/vpxd.dc5.cz\/index.php\/wp-json\/wp\/v2\/posts\/2369\/revisions\/2648"}],"wp:attachment":[{"href":"https:\/\/vpxd.dc5.cz\/index.php\/wp-json\/wp\/v2\/media?parent=2369"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vpxd.dc5.cz\/index.php\/wp-json\/wp\/v2\/categories?post=2369"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vpxd.dc5.cz\/index.php\/wp-json\/wp\/v2\/tags?post=2369"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}