Skip to main content

Removing NSX-T manager extension from vCenter



In NSX-T starting from ver 2.4 NSX-T appliance got decoupled from vCenter where now its not mandatory to run NSX-T on vCenter platform only. Now NSX-T can be managed through standalone ESXi host, KVM or through container platform.

As in version 2.4 there is still an option available to connect vCenter to NSX-T using Compute Manager.



Here in this blog we will learn how we can unregister and register NSX-T extenstion from vCenter in case of any sync or vCenter connectivity issue with NSX-T.

Lets get started..


1) Login to NSX-T UI

Go to -> System ->Compute Manager

Here, vCenter is showing in Down status where the status is showing as "Not Registered"






2) When we click on "Not Registered" option its states below error.



3) When try to click on Resolve option its states below.



At this stage if the Resolve option doesn't work then its require the remove the NSX-T extenstion from vCenter.

To remove the NSX-T extenstion from vCenter please use below steps.

  • Login to vCenter using "https://vCenterFQDN/mob
  • Click on "Content" under Properties

    • Click on ExtensionManger


    • Click on more... to expend extension to view nsx-extension.
    • Click on nsx extension "extensionList["com.vmware.nix.management.nsxt"]

    • validate the key String value.
    • Copy the highlighted value nsx manager and next step in invoke process.
    • Go back to Home page and again click content -> ExtensionManager.
    • Click on unregister Extension.
    • Paste the value which we copied in previous step to invoke.

    • Click on Invoke Method. 
     This process will remove the NSX-T extension from vCenter and now you can register the       Compute Manager (vCenter) again into NSX-T manager.


    Happy Sharing.... :)

    Labels:

    Comments

    Post a Comment

    Popular posts from this blog

    Changing the FQDN of the vCenter appliance (VCSA)

    This article states how to change the system name or the FQDN of the vCenter appliance 6.x You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out. Now the option left is from the command line of VCSA appliance. Below steps will make it possible to change the FQDN of the VCSA from the command line. Access the VCSA from console or from Putty session. Login with root permission Use above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_net Opt for option 3 (Hostname) Change the hostname to new name Reboot the VCSA appliance.   After reboot you will be successfully manage to change the FQDN of the VCSA . Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client. If you are using self-signed certificate, you can regenerate the certificate with the
    2 comments
    Read more

    Issue : Configure Management Network option is Grayed out into ESXi

    Last week I got into an issue of one of my client into Vsphere environment where one of its ESXi went done out of the network. Issue was IP address was showing 0.0.0.0 on main Esxi screen and when I tried to change the network configuration, its " Configure Management network option was greyed out.  I tried to gid into it and try to analyis its vmKernal and vmwarning logs. What I found is its VMkernal switch got removed due to unexpected reason. So to resolve the issue I tried to reconfigure its vswitch0 (vmk0) by going into Tech Mode of that Exi. Below are the steps which I followed to resolve the issue. 1) Login to ESXi 2) Press F2, Check if you " Configure Management network " is greyed out or not" if yes,    follow below 3) Press ALT+F1 to move the ESXi screen to tech mode   ( This is command line like dos) 4) login with root account 5) Run the following command into it esxcli network ip interface add --interface-name= vmk0
    2 comments
    Read more

    Collecting Logs from NSX-T Edge nodes using CLI

      This article explains how to extract the logs from NSX-T Edge nodes from CLI. Let's view the steps involved: 1) Login to NSX-T  Edge node using CLI from admin credentials. 2) Use of  " get support-bundle " for Log extraction. get support-bundle command will extract the complete logs from NSX-T manager/Edge nodes. nsx-manager-1> get support-bundle file support-bundle.tgz 3) Last step is to us e of " copy file support-bundle.tgz url " command. copy file will forward your collected logs from the NSX-T manager to the destination(URL) host from where you can download the logs. copy file support.bundle.tgz url scp://root@192.168.11.15/tmp Here, the URL specified is the ESXi host ( 192.168.11.15) under /tmp partition where logs will be copied and from there one can extract it for further log review. Happy Learning.  :)
    Post a Comment
    Read more