because I had problems with VSC Windows Installation discovering the Storage on my VCSA 6.5, I downloaded and installed VSC 7.0 (virtual appliance) yesterday.
Installation worked pretty well, but if I click on the Virtual Storage Console Icon in VCenter Web Client, VSC hangs with message "Loading Storage System Details" - without no other error/warning message.
I read that VSC 7.0 does not support linked mode, the system will then also be stuck at the same loading message, but along with an error message that states that linked configuration is not supported.
I have no linked mode configured, but I do use VCenter HA. Could that be the problem or do you have another idea?
Restarting VCenter and/or VSC did not solve the problem.
Solved! See The Solution
The VSC 7.0P1 release came out today. I installed it on my vCenter 6.5 setup this afternoon and seems like everything that wasn't working is now working again. I just thought I'd let everyone know.
i'm pleased to report you all that here the problems have been resolved as well.
VSC plugin is very fast, way faster than 6.
Everything is reporting the way it supposed to be and Host settings can be applied without errors: everything in green.
Thanks NetApp for resolving the issues.
My customer is having the exact same issue.
They are only able to see the LIFs, no Hosts, NAS, SAN ot SVMs are listed.
Even though the ESXi hosts have several NFS mounts connected, VSC is detecting no storage.
Please let me know when the fix is released.
Personally, I have those issues with VSC 7 on VCSA 6.5 and up:
Hope ther will be a quick update to fix those problems
VSC 7 was not working on VCSA 6.5 U1. I did an inplace upgrade from VSC 6.2.1P1D2
The plugin in VCSA showed version 7. After exactly 1 week VCSA was showing VSC 6.2.1P1D2
I did not uninstall the 7 plugin or a downgrade. it simply switched to 6.2.1P1D2 and eveything was showing ok.
The VM instance of VSC 7 was not showing any error. Very weard.
For the time being all versions and plugins have been removed, vasa provider removed and we'll wait for an update.
In place upgrade is not supported for VSC 6.2.x to VSC 7.0. You have to perform migration which involves uninstalling existing VSC 6.2.x and installing VSC 7.0.
Please refer and perform steps mentioned in 'Migrating existing VSC installation to the 7.0 version of the virtual appliance for VSC, VASA Provider, and SRA' section of Deployment and Setup Guide.
Thank you for your reply. we are aware of this. We removed the whole VSC plugin and started from scratch. Still no working solution for VCSA 6.5 and VSC 7.
We're still on VCSA 6 with VSC 6.2 on production.
In test environment we can run VCSA 6.5 U1 with VSC 6.2P1D2.
VSC 6.2 or 7 will not function.
We see the following issues with VCS 7 on VCSA 6.5 and up:
Unable to apply VSC host settings. All ESXi servers report HBA settings unable to be applied: java null error.
VASA 7 provider reports to vsphere client that it can find all SVM but no datastores found.
VSC 7 in vpshere plugin show only the cluster and lifs.
NAS, SAN, SVM, VOL and Aggrs are not shown.
This same behaviour was seen in VSC 6.2.1 with VASA provider 6.2
There was a fix produced and a patch made: VSC 6.2.1 P1D2 (we've used VSC-6.2.1P1D2-win64.exe)
And indeed all these problems were solved:
VSC host settings were successfully applied, VASA 6.2 provider reports all datastores, svm, vol and aggrs
VSC 6.2.1 P1D2 reports all clusters, svm, lifs, NAS, SAN, VOL and aggrs.
So what ever fix was done in 6.2.1P1D2 solved these problems and needs to be applied to VSC 7 since it was confirmed in this topic it was not included.