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.... :)

    Comments

    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

    VM Creation Date & Time from Powercli

    Most of the times we have several requirement when we talk about IT environment like designing , deployment , compliance check or for Security auditing the environment. Somewhere during security auditing we require to provide several information to security team to get successful audit. One of them is the compliance of Virtual machine auditing of creation date and time. Here into this post we will explore how to get the creation date and time of virtual machine hosted into the vCenter or ESXi. To get the details we will use VMware Powercli to extract the details. By default there is no function added into Powercli to get such details, so here we will add a function of vm creation date. Below is the function which needed to be copy and paste into the Powercli. ======================================================================= function  Get-VMCreationTime  {     $vms  =  get-vm     $vmevts  = @()     $vmevt  =  new-object  PSObject     for

    Unable to poweron the VM. (Failed to lock the file)

    I have encountered may issues like where after some upgrade or migration we were unable to power on the VM. Figure 1 An error was received from the ESX host while powering on VM HSSVSQL01. Failed to start the virtual machine. Cannot open the disk '/vmfs/volumes/578d835c-18b2c97a-9b0d-0025b5f13920/SAMPLE1_cloud/000000.vmdk' or one of the snapshot disks it depends on. Failed to lock the file In above Figure:1, where while powering on the VM, its prompt for an error. Well, there are several reason for where the VM unable to poweron and you can find many article on this. Here in this article we will discuss to resolve this issue. Please use below step to resolve the disk lock issue  C hecked that VM is running on snapshot if its getting error " VM Consolidation required". Checked the snapshot manager if its showing any snapshot. If yes, try to delete the  snapshot. Verified the same from Esxi cl