4 Replies Latest reply on Jan 31, 2018 11:32 PM by tanurkov

    Unable to register NSX 6.4 with VCenter(400 Bad Request)

    mdevarajan Lurker
    VMware Employees

      Hello Team,

      As part of testbed bringup we spin up nsx and register with VC.

      Registration works fine with NSX 6.3. But the same code doesnt work with NSX 6.4

      I did go through 6.4 API guide and Release notes, dont see any changes mentioned for registration.


      Can you please shed some light on why registration fails with NSX 6.4 alone.



      Nsx 6.4:

      send: 'PUT /api/2.0/services/vcconfig HTTP/1.1\r\nHost:\r\nAccept-Encoding: identity\r\nContent-Length: 278\r\nContent-Type: application/xml\r\nAuthorization: Basic YWRtaW46ZGVmYXVsdA==\r\n\r\n'

      send: u'<vcInfo><userName>administrator@vsphere.local</userName><password>replaced</password><ipAddress></ipAddress><certificateThumbprint>79:D0:96:08:18:15:70:C2:50:AE:56:CC:6A:33:4A:4B:53:28:96:04</certificateThumbprint><assignRoleToUser>true</assignRoleToUser></vcInfo>'

      reply: 'HTTP/1.1 400 Bad Request\r\n'


      NSX 6.3:


      send: 'PUT /api/2.0/services/vcconfig HTTP/1.1\r\nHost:\r\nAccept-Encoding: identity\r\nContent-Length: 277\r\nContent-Type: application/xml\r\nAuthorization: Basic YWRtaW46ZGVmYXVsdA==\r\n\r\n'

      send: u'<vcInfo><userName>administrator@vsphere.local</userName><password>replaced</password><ipAddress></ipAddress><certificateThumbprint>17:A0:CB:AB:1D:DD:1D:EC:A1:83:E2:A6:0D:7B:D1:B2:8E:3D:B4:51</certificateThumbprint><assignRoleToUser>true</assignRoleToUser></vcInfo>'

      reply: 'HTTP/1.1 200 OK\r\n'

        • 1. Re: Unable to register NSX 6.4 with VCenter(400 Bad Request)
          lhoffer Hot Shot
          vExpertVMware Employees

          What version is your vCenter server?  6.4 removed support for anything less than 6.0u2 per the VMware Product Interoperability Matrices where previous versions (including 6.3) supported down to 5.5.

          • 2. Re: Unable to register NSX 6.4 with VCenter(400 Bad Request)
            mdevarajan Lurker
            VMware Employees

            We are using VC version

            • 3. Re: Unable to register NSX 6.4 with VCenter(400 Bad Request)
              canero Hot Shot

              NSX Manager <--> vCenter registration, Is  the vCenter that the NSX Managers 6.3 and 6.4 are registering to the same vCenter VM? Since at one time there can be only one NSX Manager registered to and the NSX Managers are seperate, how is the deRegistration of 6.3 done before registering 6.4? Points may be:

              • DNS --> both forward and reverse should be resolved on both NSX Managers and vCenter
              • NTP --> Time should be synchronized

              Also what error is seen if instead of through API request, GUI registration is through NSX Manager Web is configured?


              If for 6.3  there are Controllers, hosts are  prepared and configurations done on NSX manager there could be additional steps needed for Unregistering NSX Manager from the vCenter through Invoke method:




              Safely Remove an NSX Installation

              A complete uninstall of NSX removes host VIBs, the NSX Manager, controllers, all VXLAN configuration, logical switches, logical routers, NSX firewall, Guest Introspection, and the vCenter NSX plug in. Make sure to follow the steps for all hosts in the cluster. VMware recommends that you uninstall the network virtualization components from a cluster before removing the NSX plug-in from vCenter Server.


              6. For the vCenter on which you want to remove the NSX Manager plug-in, log in to the managed object browser at https://your_vc_server/mob.

              7. Click Content.For example:


              8.Click ExtensionManager.


              9.Click UnregisterExtension


              10. Enter the string com.vmware.vShieldManager and click on Invoke Method.


              11. If you are running the vSphere 6 vCenter Appliance, launch the console and enable the BASH shell under Troubleshooting Mode Options.



              Another way to enable the BASH shell is to log in as root and run the shell.set --enabled true command.

              12. Delete the vSphere Web Client directories for NSX and then restart the Web Client service.The vSphere Web Client directories for NSX are called com.vmware.vShieldManager.** and are located as follows:

              • vCenter Server 5.x
                • Windows 2003 – %ALLUSERSPROFILE%\Application Data\VMware\vSphere Web Client\vc-packages\vsphere-client-serenity\
                • Windows 2008/2012 – %ALLUSERSPROFILE%\VMware\vSphere Web Client\vc-packages\vsphere-client-serenity\
                • VMware vCenter Server Appliance – /var/lib/vmware/vsphere-client/vc-packages/vsphere-client-serenity/
              • vCenter Server 6.0.x
                • Windows 2008/2012 – C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\vsphere-client-serenity\
                • VMware vCenter Server Appliance – /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/

              For vCenter Server Appliance, run the service vsphere-client restart command in the appliance shell.For Windows-based vCenter, run services.msc, right-click vSphere Web Client, and click Start.




              The NSX Manager plug-in is removed from vCenter. To confirm, log out of vCenter and log back in.

              The NSX Manager plug-in Networking & Security icon no longer appears on the Home screen in the vCenter Web Client.


              Go to Administration > Client Plug-Ins and verify that the list of plug-ins does not include NSX User Interface plugin.


              • 4. Re: Unable to register NSX 6.4 with VCenter(400 Bad Request)
                tanurkov Enthusiast


                check virgo logs on vcenter "find  . iname ""virgo". and search for vShield.

                Playing with extensions is last thing that need to be done , first verify what is going on , before delete extensions .