Table of Contents

• Table of Contents
• Overview
• Create an original restore point.
• Remove old plugins from vCenter
• Unregister the plugin for com.vmware.vShieldManager
• Updating NSX Manager against the vCenter.
• Confirm registration

Overview

After upgrading our NSX to 6.4.4 and newer we had a problem where the H5 plugin was not showing inside the vCenter via the HTML5 client. It was showing properly inside the FLEX flash based client but since FLASH is now completely gone this proved to be a serious problem. Even after upgrading to NSX 6.4.10 it was still not displaying properly. In order to resolve this we following this recently published article from VMware https://kb.vmware.com/s/article/67357

Create an original restore point.

1. Create a clone of the Cloud Director VM.
2. Create a snapshot of the Cloud Director VM.

Remove old plugins from vCenter

1. Ensure that all sessions are logged out from the html5 and flash based clients.
2. SSH into the vCenter itself and gain shell access.
3. We will want to stop the html5 and flash based services.

   service-control --stop vsphere-client
   service-control --stop vsphere-ui
   

4. Create backups for the plugs (in case we accidentally remove the wrong item) for “vsphere-client” and “vsphere-ui” in the backup folder “vsphere-client-serenity”

   mkdir /ect/temp/vsphere-client-serenity
   mkdir /etc/temp/vsphere-ui-serenity
   cp /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/ /ect/temp/vsphere-client-serenity
   cp /etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/ /etc/temp/vsphere-ui-serenity
   

5. Delete all plugins from “vsphere-client-serenity”. While we’re specifically looking for “com.vmware.vShieldManager” and “com.vmware.nsx.ui.h5” we can remove them all and there should be no negative impact.

   rm -rf /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/*
   rm -rf /etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity/*
   

Unregister the plugin for com.vmware.vShieldManager

1. Navigate to the mob for our vCenter by opening a web browser and going to https://vCenter-URL-or-IP/mob
2. Log into the interface using the administrator@vsphere.local credentials.
3. Click on Content and then ExtensionManager.

   NOTE: As an alternative once you’re logged into the mob you can go directly to https://vCenter-URL-or-IP/mob/?moid=ExtensionManager)

4. Expand the list by clicking on (more…).
5. You should see “com.vmware.vShieldManager” is listed but it is missing “com.vmware.nsx.ui.h5”.
6. Click “UnregisterExtension” at the bottom of the page and enter the name “com.vmware.vShieldManager”.
7. Click Invoke Method which should return VOID, this is confirmation it was successful.

   NOTE: If you see that “com.vmware.nsx.ui.h5” was still listed then you can perform the same action on it and invoke method to remove it.

8. Back in the SSH session start up the vsphere-client and vsphere-ui services.

   service-control --start vsphere-client
   service-control --start vsphere-ui
   

Updating NSX Manager against the vCenter.

1. Login to NSX Manager VAMI with standard admin username/password.
2. Click on “Manage vCenter Registration”
3. On the “Lookup Service URL” section
   1. Save the URL and SSO administrator information, ensure you have the password for this account, if not then do not proceed.
   2. Click on Unconfigure.
   3. Edit your lookup information and enter the information:
      • Lookup Service Host can be either URL or IP.
      • The Port the service is running on, default is 443.
      • The SSO Admin service account, ex: administrator@vsphere.local
      • The password to the account provided
      • Click OK
4. On the “vCenter Server” section
   1. Click on Edit
   2. Provide the vCenter Server URL or IP address
   3. Provide the vCenter service account, ex: administrator@vsphere.local
   4. Provide the password to the account provided.
   5. Click OK

Confirm registration

1. Log out of all active sessions to the vCenter Server.
2. Clear the browser cache.
3. Navigate to the mob for our vCenter by opening a web browser and going to https://vCenter-URL-or-IP/mob
4. Log into the interface using the administrator@vsphere.local credentials.
5. Click on Content and then ExtensionManager.

   NOTE: As an alternative once you’re logged into the mob you can go directly to https://vCenter-URL-or-IP/mob/?moid=ExtensionManager)

6. Confirm you have “com.vmware.vShieldManager” and “com.vmware.nsx.ui.h5” listed.
7. Log into the html5 client and confirm Networking and Security is now showing properly.

NOTE: while performing the last two sections you can also watch the log files to ensure everything registers correctly by running on the vCenter ‘tail -f /var/log/vmware/vsphere-client/logs/vsphere_client_virgo.log’ and on the NSX manager ‘tail -f /home/secureall/secureall/logs/vsm.log’