Cisco UCS Manager Flex-based Plugin for VMware vSphere Web Client (End of Support)

[ericwill]

End of Support Notice: Support for the Flex-based Plugin for VMware vSphere has been discontinued.  The HTML based Plugin is recommended as a replacement.

Previous Release Information:

Cisco UCS Manager Plugin is an extension for the vSphere Web Client. It enables virtualization administrators to view, manage and monitor various aspects of Cisco UCS physical infrastructure. The result is a single pane of glass for Virtual Center users to get both physical and virtual infrastructure information for a given hypervisor.

New Features in UCS Manager Plugin 2.0(3):

• Defect fixes

Supported vSphere Web Client Releases:

• vSphere Web Client 5.5
• vSphere Web Client 6.0
• vSphere Web Client 6.5

Refer to release notes and user guide for more details.

[xvandyk01]

Hi . Publish and tested both ways https and http. Still nothing is visible

[vaibjain]

https://techzone.cisco.com/t5/B-Series/Troubleshooting-the-UCS-plugin-for-vCenter/ta-p/178146

Problem:

Following installation, the UCS plugin for vCenter icon does not appear under the administration section of the Web Client as expected.  Though you may see the plugin registered from the java VI Client "Plugin Extension" wizard, it doesn't appear in the Web Client.

Background:

The plugin registration (installation) process only registers the "details" of the plugin including the URL where it's located.  vCenter doesn’t download the plugin at this stage. It just registers the details of the plugin. When the call to vCenter returns without an error, we show the success message to the user.

Its only when user tries to login to the vsphere web client, the web client fetches the plugin details from vCenter and tries to download the plugin directly from the URL.  This is the point where there may be a problem with the web client accessing the plugin URL, and fail to load & display within the web client.

Solution:

1. Windows Vcenter Only: Validate that Windows Firewall Settings on Vcenter Server to allow Vsphere Web-Client - http(s) Port is "allowed" .  To check Windows Firewall settings click: Control Panel\All Control Panel Items\Windows Firewall\Allowed Programs and validate a checkbox is checked for WebClient Http/HTTPs port.
2. Make sure that there aren’t trailing whitespaces when adding the line “allowHttp=true” in the file "webclient.properties" as per the registration procedure.  Remember to restart the web client service after you make changes.
3. Use FQDN instead of hostname in the URL used while registering the plugin.  Common issues arise if the domain suffix of the web client host is different than that domain suffix of the target HTTP server hosting the plugin.  Using the FQDN avoids this problem.  If prevsiously register, unregister and start over with the FQDN. 
4. View the web client logs for clues.

If this does not solve the problem, we can troubleshoot the problem over webex.

[vaibjain]

https://techzone.cisco.com/t5/B-Series/Troubleshooting-the-UCS-plugin-for-vCenter/ta-p/178146

Problem:

Following installation, the UCS plugin for vCenter icon does not appear under the administration section of the Web Client as expected.  Though you may see the plugin registered from the java VI Client "Plugin Extension" wizard, it doesn't appear in the Web Client.

Background:

The plugin registration (installation) process only registers the "details" of the plugin including the URL where it's located.  vCenter doesn’t download the plugin at this stage. It just registers the details of the plugin. When the call to vCenter returns without an error, we show the success message to the user.

Its only when user tries to login to the vsphere web client, the web client fetches the plugin details from vCenter and tries to download the plugin directly from the URL.  This is the point where there may be a problem with the web client accessing the plugin URL, and fail to load & display within the web client.

Solution:

1. Windows Vcenter Only: Validate that Windows Firewall Settings on Vcenter Server to allow Vsphere Web-Client - http(s) Port is "allowed" .  To check Windows Firewall settings click: Control Panel\All Control Panel Items\Windows Firewall\Allowed Programs and validate a checkbox is checked for WebClient Http/HTTPs port.
2. Make sure that there aren’t trailing whitespaces when adding the line “allowHttp=true” in the file "webclient.properties" as per the registration procedure.  Remember to restart the web client service after you make changes.
3. Use FQDN instead of hostname in the URL used while registering the plugin.  Common issues arise if the domain suffix of the web client host is different than that domain suffix of the target HTTP server hosting the plugin.  Using the FQDN avoids this problem.  If prevsiously register, unregister and start over with the FQDN.
4. View the web client logs for clues.

If this does not solve the problem, we can troubleshoot the problem over webex.

[imagineps]

Thanks so much for including these troubleshooting steps after viewing the log on our Web Client server I was able to find that it was downloading the plugin but couldn't because our proxy wasn't allowing virtual center out.

https://communities.cisco.com/servlet/JiveServlet/download/36989-10-61965/ucs-vcplugin-0.9.4.zip to directory C:\ProgramData\VMware\vSphere Web Client\vc-packages\vsphere-client-serenity\com.cisco.ucs.vcplugin-0.9.4, check if the server process has Write Permission on this machine. java.net.SocketException: Connection reset

  at java.net.SocketInputStream.read(Unknown Source)

I then created a com.cisco.ucs.vcplugin-0.9.4 folder in the specified location and extracted the zip in it and all was well.

[dalefebv]

I am also looking for this information.  If anyone knows what privileges are required to allow access to the KVM button, that would be appreciated.

[reswaran]

We are looking into it. Will get back to you soon.

[vaibjain]

Ideally for KVM launch user, you can associate user with a role which has "ls-ext-access" (Service Profile Ext Access) privilege.  But there seems to be a bug in the plugin, the button only gets enabled for following privileges : admin, Server maintenance, Server policy, Server equipment.

You can have any these privileges to get this working on this version. We will fix this issue in the upcoming version of plugin.

Vaibhav

[vaibjain]

Hi Dzmitryj Jakavuk,

Are you still facing this problem? I cant access the screenshot.

Regards,

Vaibhav 

[vaibjain]

Hi Rus,

Do you see any entry for "com.cisco.ucs.vcplugin" in mob under ExtensionManager. You can launch MOB by typing following url on your browser:

https://<vcenter ip>/mob/?moid=ExtensionManager

If you see any entry for "com.cisco.ucs.vcplugin", which means the plugin is registered and registration tool is not giving correct error message, let us know we will fix it in next release. In this case to further troubleshoot you can check web client logs.

-Vaibhav

[NordnetSA]

Hi Vaibhav,

I have the same issue when I try to connect to vCenter even after removing the extension through the extension manager.

Is there a way to force the registration?

I am using vCenter 5.5 U1 and I have no problem to connect with both clients.

Regards.

[simon.wright321]

I am seeing the same problem with vCenter 5.5 update 1b. I am using the VCSA. The both clients are working for me as is the NetApp VSC 5.0, UCS director.

[reswaran]

We identified the issue. Its due to an API change in PowerCLI 5.5 R2. We are working on fixing our registration tool. In the mean time, you can downgrade your PowerCLI from 5.5 R2 to 5.5 and then register the plugin.

More details about the API change at PowerCLI 5.5 Release 2 - change to API - VMware... | VMware Communities

[reswaran]

We identified the issue. Its due to an API change in PowerCLI 5.5 R2. We are working on fixing our registration tool. In the meantime, you can downgrade your PowerCLI from 5.5 R2 to 5.5 and then register the plugin.

More details about the API change at  https://communities.vmware.com/thread/478700

[reswaran]

We identified the issue. Its due to an API change in PowerCLI 5.5 R2. We are working on fixing our registration tool. In the meantime, you can downgrade your PowerCLI from 5.5 R2 to 5.5 and then register the plugin.

More details about the API change at  https://communities.vmware.com/thread/478700

[reswaran]

The issue is fixed and the updated registration tool 0.9.6 is available above for download.