WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud
  • Tanzu
    • Application Modernization
    • Tanzu services
    • Tanzu Community Edition
    • Tanzu Kubernetes Grid
    • vSphere with Tanzu
  • Home Lab
  • Nested Virtualization
  • Apple
You are here: Home / NSX / Quick Tip - NSX-T 2.1 upgrade gotcha, use NSX Manager IP Address vs Hostname

Quick Tip - NSX-T 2.1 upgrade gotcha, use NSX Manager IP Address vs Hostname

01.02.2018 by William Lam // 1 Comment

NSX-T 2.1 was released right before the holiday break and one of the biggest enhancement is support for VMware's upcoming Pivotal Container Service (PKS) which you can read more about here. Right before I took some much needed time off with the family, I had attempted an upgrade of my existing NSX-T 2.0 environment and ran into an issue which turned out to be a known issue but apparently it is no where listed on the NSX-T 2.1 release notes.

I figure I would share the simple workaround as it drove me a bit insane trying to figure out what was going on. After successfully uploading the NSX-T 2.1 upgrade bundle and then starting the upgrade, which starts off by updating the Upgrade Coordinator component and shortly after, I am shown the following error message:

This page is only available on the NSX Manager where Upgrade Coordinator is running. To enable the service, run the command "set service install-upgrade enabled" on the NSX Manager. If the install-upgrade service is already enabled, try disabling it using "clear service install-upgrade enabled" and then enable it again.

Although the error seems to suggest the Upgrade Coordinator service may not be running (it was), even after performing the recommended operations, the error message continue to persists as seen in the screenshot below.


After reaching out to Engineering as I was out of ideas on how to further troubleshoot the issue, it turns out this was actually a known upgrade issue going from 2.0 to 2.1. Instead of connecting to the NSX-T Manager using its Hostname (FQDN), I needed to use the IP Address instead for the upgrade. Once I logged back in using the IP Address, I was no longer seeing the error message and could proceed with my NSX-T upgrade as shown in the screenshot below.

More from my site

  • NSX Alarms in vCenter Server using vSphere Events in vSphere 8
  • Integrated NSX-T deployment in vSphere 7.0 Update 3 fails with timeout
  • Retrieving network statistics on VMware Cloud on AWS using NSX-T Policy API
  • Configure NSX-T Edge to run on AMD Ryzen CPU
  • NSX-T Edge OVF property to automatically join NSX-T Management Plane

Categories // NSX Tags // NSX-T, upgrade coordinator

Comments

  1. Biswajit Mukherji says

    03/08/2021 at 3:31 am

    We have observed the issue in 2.4.2 as well. Thanks for your tip !

    Reply

Thanks for the comment!Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Author

William Lam is a Senior Staff Solution Architect working in the VMware Cloud team within the Cloud Infrastructure Business Group (CIBG) at VMware. He focuses on Cloud Native, Automation, Integration and Operation for the VMware Cloud based Software Defined Datacenters (SDDC) across Private, Hybrid and Public Cloud

Connect

  • Email
  • GitHub
  • LinkedIn
  • RSS
  • Twitter
  • Vimeo

Recent

  • Easily disable vSphere Cluster Services (vCLS) using UI/API in vSphere 8.0 Update 2 09/21/2023
  • ESXi on Lenovo ThinkStation P3 Tiny 09/20/2023
  • How to setup custom vSphere Content Library on a Synology? 09/19/2023
  • ESXi on SolidRun V3000 09/18/2023
  • Synology NFS VAAI Plug-in support for vSphere 8.0 09/14/2023

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2023

 

Loading Comments...