VMware Solutions Discussions
VMware Solutions Discussions
Hello,
did anybody try VSC 7.1 with vSphere 6.7 yet? I deployed the VSC appliance, it successfully registered to vCenter as shown in VSC maintenance screen and in vcenter/mob extensionManager, but its icon does not appear in vCenter nor is it displayed in the client plugins list in vCenter 6.7.
I already tried it using different browsers and rebooted the vCenter VCSA 6.7.
Solved! See The Solution
Hi,
VMware made some architectural changes in 6.7U2 that required additional changes/testing with the Unified Virtual Appliance (VSC/VP/SRA). We are targeting 6.7U2 support for the UVA with the 9.6 release this summer.
---Karl
6.7 and 6.7U1. But see my earlier note in this thread if you use NFSv3.
---Karl
VSC 7.2.1 is available for download: https://mysupport.netapp.com/NOW/download/software/vsc_win/7.2.1/
The virtual appliance for VSC, VASA Provider, and SRA provides the combined features of VSC, VASA Provider, and SRA in a single deployment. VSC features are enabled by default when you deploy the virtual appliance.
Depending on your requirements, you can enable VASA Provider or SRA by using the virtual appliance for VSC, VASA Provider, and SRA. The virtual appliance supports the following features:
Tried upgrading from 7.2 and although the system reports as successfully upgraded the appliance then fails to boot. There seems to be numerous errors but rolled back to 7.2 in the end.
Has anyone else managed to successfully perform this upgrade? Will log a support call next week if no one else has this issue.
Errors seem to be with some package removal requested in the upgrade script. Rolling back.
Upgrade failed for me also.
Do you have a screenshot of the errors? Also which version of vSphere is the appliance deployed on?
I have the exact same error. Tried upgrading vmtools before before upgrading to 7.2.1 but still had the same issue.
To confirm vmware tools did upgrade successfully without causing an issue.
any news on this topic?
Same exact issue here with the upgrade. Fails with the same issues as described previously here.
I do have 2 virtual centers and did a new install of 7.2.1 from OVF. That install went on without a hitch.
LB
For the upgrade issue, can you share the screenshot of the errors?
There are screenshots in an earlier post.
It would seem that mutiple people have the issue with the upgrade and screenshots have been provided. Can someone from NetApp acknowlegde this and that a fix will be released soon please?
Have you verified the VSC plugin after the upgrade. Especially in the About page on the VSC dashboard. It would show the 7.2.1 version.
Also, can you check if you are able to perform VSC operations if the about version shows as 7.2.1
After the upgrade fails the applicance fails to reboot. If you then manually restart the appliance it fails to boot at all and just hangs on startup. Obviously any tests of the plugin atre not posssible.
It looks like you are upgrading from 7.0P1.
The supported upgrade paths are from 7.1 and 7.2.
I'm upgrading from version 7.2 and I have the exact same issue. See below screenshot from the "About" tab on my exisiting installation.
It looks like 7.0P1, but it's only name of the guest i vsphere that is not updated. It's 7.2 for me also.
I am on VSC 7.2 and the upgrade failed in the same manner as Harkan
Hi,
I am sorry you are experiencing these problems. Engineering has been following this thread and is investigating. I just tried to upgrade my lab system and saw similar.
It's possible these are related to vCenter release. I have been working with Engineering to clarify the supported releases as listed in IMT. Has anyone had problems when upgrading using the vCenter releases that are currently listed in the IMT (6.5U2, 6.7 and 6.7U1)?
---Karl
netapp is able to recreate the issue when upgrading.. See below:
Thanks for your feedback
We were able to replicate the error reported. We submitted this report to our Engineering Department to investigate.
If version is necessary on your environment, two (2) scenarios are available as a workaround:
If scenarios 1 or 2 are not possible and the rollback to 7.2 works for you, our suggestion is to keep it as it is while our Engineering Dept. provides a fix. At the moment, no ETA has been provided (yet).
To follow-up on this, please refer this BURT ID: OMITTED
Given that this situation depends on a higher department and has been already escalated through the BURT provided above, is it safe for us to archive this case here at Technical Support?