jemimus
2 Bronze

Registered VSI to both vCenters, do not get the EMC VSI option in webclient

Jump to solution

Hi,

I have installed the OVF and seemingly successfully installed the plugin.

SNAG-0161.jpg

However, when I look in the vCenter webclient, I do not see the EMC VSI option.
We have 2 vCenters in Linked mode, and I have 'installed' the plugin to both.

However, it should be noted, that in both cases, the vCenter itself, and the webclient portion (along with the inventory service), are not on the same Windows server.

SNAG-0162.jpg

I have cleared my browser cache a few times already and logged out and back in several times.

The version of both vCenters is 5.5.0, build 2183111
The version of VSI is 6.5.1.15

In the classic client, you can see the plugin is actually installed:

SNAG-0163.jpg

Anyone have any suggestions?

Labels (1)
1 Solution

Accepted Solutions
jemimus
2 Bronze

Re: Registered VSI to both vCenters, do not get the EMC VSI option in webclient

Jump to solution

I have heard back from an informal EMC contact:

I’m sorry to report Robert that the code is the culprit here, not simply a matter of supportability.

I suppose we will have to wait for a future version...

View solution in original post

2 Replies
jemimus
2 Bronze

Re: Registered VSI to both vCenters, do not get the EMC VSI option in webclient

Jump to solution

According to EMC support, Linked mode is not supported. They are recommending we turn this off.

That is quite frustrating to hear. We rely on Linked Mode quite heavily to ease our vSphere administration. Its quite disappointing that VSI, even after all these years, is limited in this way.

I am trying to get out of EMC support if this particular problem is actually indeed caused by Linked-Mode directly, or their statement is just a matter of formality.

0 Kudos
jemimus
2 Bronze

Re: Registered VSI to both vCenters, do not get the EMC VSI option in webclient

Jump to solution

I have heard back from an informal EMC contact:

I’m sorry to report Robert that the code is the culprit here, not simply a matter of supportability.

I suppose we will have to wait for a future version...

View solution in original post