2018-03-01 09:01 AM
First of all, thanks a lot for your time on reading this post!
I was working with VSC6.2, but we have recently upgrade ONTAP in our FAS8040 from 8.3.4 to 9.1, and after that, our VSC jobs kept working, but they werent capable of updating the snapmirror relationship against our secondary FAS8040.
So, let's move forward.
- I deployed a new VM with SnapCenter 4.0 in my main vCenter. My idea is that all VSCs from my four vCenters are controlled from there. And all backups jobs, policies, etc.
- I unninstalled VSC6.2 for my secondary vCenter.
- Afterwars I learned that VSC 7.X is no longer in charge of backups, but anyway i deployed one in one of my secondary vCenters, for test porpouses. I really like applying best practices for NFS / MPIO /adapters so easily .
- In SC 4.0 I added all SVMs from my two cabins, main and secondary.
- In SC.40 I added a new host for vsphere, choosed a win VM in my secondary vCenter, added win credentials (AD admin). After a while, all was deployed, incluiding SnapCenter Plugín for VMware vSphere.
- There I could see that my SVM where alredy deployed in "Storage Systems" tab, pulled from SnapCenter.
- There I could create a new policy, which I could see was pushed to the SC (settings - user access - policy). The strange thing is that in SC I couldnt see them on settings - policies...
My problem comes when I wan to create a Resource Group with a single datastore, using the newly created policy. I can choose it on the wizzard, but when I finish the task, I got errors:
- Resource Group creation failed : Unable to find host (X.X.X.X). This address if the IP from the server which i choosed to deploy the Plugin for vSphere.
- In "Monitor" tab in SC I can see the job listed as failed, with the same message.
- In "Monitor" tab, "Logs" subtab, I can see the following related messages:
About error 1 I found googling that NSM is the database installed during SC deployment. About error 2 I have double checked FW in all win machines (SC and Plugin VMs), and all firewalls in the middle (all traffic allowed). I suppose that vapps (vCenter and VSC) have all needed ports opened by default. About error 3 I found nothing.
I'm stucked at this point, and really appreciate any help.
2018-03-28 09:44 AM
After I went into settings in the vsphere snapcenter plugin, I confirmed the settigns I had before, the flash client will freeze up for about 5 min applying the settings but then it worked for me.
2018-04-10 02:30 PM - edited 2018-04-10 02:39 PM
We have a similar setup:
1. ONTAP 9.1 P8
2. We have multiple arrays i.e. 8020's, 8040's, AFF, etc.
3. VMware vCenter 6.0 Update 3(e)
4. Virtual Storage Console 6.2.1P1D2 (Plan in the works to upgrade to 7.0)
5. SnapCenter 4.0 (just recently installed to replace SMVI)
We are stuck with the following error logged in the newly installed SnapCenter in the logs:
ERROR SnapManagerWeb PID= TID= Failed to find host (X.X.X.X). Please check the host is up and running or check the firewall settings. No such host is known
When we attempt to create a resource group for one of our sites (remote, 8020), we get an error at one (1) of our 3 sites: "Some entities are not SnapCenter compatible." while the other sites (remote, 8040, AFF) work fine...
When reviewing the logs in SnapCenter, the following error is logged: "Failed to get the storage system for host resource"
2018-05-09 04:51 AM
The reasons when you can run into issue "Some entities are not SnapCenter compatible." are listed below:
Can you check if you are running into any of these?
The corrective actions are pretty obvious but nevertheless listing it here:
2018-05-09 08:25 AM - edited 2018-05-09 08:26 AM
We resolved our issue two (2) weeks ago; however, we scrapped Snap Center 4.0 out of our virtual infrastructure at this time.
Our issue was that we somehow missed adding two (2) backup SVM targets into Snap Center 4.0 interface. Once this was realized, we had no further issues in terms of the Resource Groups.
Now, for the reason we scrapped Snap Center 4.0...
NetApp VSC 6.2.1P1D2 is not compatible with Snap Center 4.0. As such, it is not recommended to run both in the same vCenter instance. When we contacted NetApp Support, we were told that we would need to upgrade to NetApp VSC 6.2.1P1D6 in order for things to work properly. So we followed the advice of support....
A week later, we started exhibiting problems with our VSC. It would disappear out of our vCenter environment completely. Although in the Windows Client the plug was showing as registered, the web client it was completely missing with only the Snap Center 4.0 plugin available. Our VSC SMVI snapshots however were unaffected but we were unable to manage our VSC.
After several interations with removing and re-registering the VSC plugin it would come back and the next day, it would disappear.
Further interaction with NetApp support turned out that not even P1D6 is supported to co-exist with Snap Center 4.0 in the same vCenter instance.
This basically put a halt on our migration road map to get off VSC 6.2.1 P1D6.
As a result we have to go back to the drawing board. We plan now to build a completely new vCenter environment with VSC 7.0 and SnapCenter 4.0 and perform a VSC 6.2.1 P1D6 migration to Snap Center 4.0.
VSC 7.0 is the only version supported to co-exist with Snap Center 4.0.
For us unfortunately, it was important to migrate from VSC 6.2.1 to Snap Center 4.0 due to the amount of SMVI snapshots we perform through VSC. VSC 7.0 no longer performs SMVI snapshots which is why we are moving or trying to move to Snap Center 4.0. Due to the incompatibility with 6.2.1 and Snap Center 4.0 we have hit a migration road bump.
Too bad NetApp can't make the migration from VSC to SnapCenter 4.0 seamless...
2018-05-09 08:51 AM
This is exactly were my problems started, as Im not being able to create snapshots with SC 4. Fortunately we tried first on a secondary vCenter enviorenment, so our production is still protected with an old VSC version + manual snapmirrors.
2018-05-09 08:59 AM
@COSNA2, that is not true (no seamless migration from VSC/SMVI to SnapCenter)!
NetApp has released a utility called 'NetApp Import Utility for SnapCenter & VSC' exactly for this purpose.
It can be accessed on the toolchest here: https://mysupport.netapp.com/tools/info/ECMLP2840096I.html?productID=62135&pcfContentID=ECMLP2840096
YouTube video on import utility: https://youtu.be/CEQmIEzNVfA
VMware community thread highlighting actual challenges and detailed step: http://community.netapp.com/t5/VMware-Solutions-Discussions/NetApp-Import-Utility-for-SnapCenter-and-Virtual-Storage-Console/m-p/137248#M9154
Feasibility for migration
Limitations of the tool
Hope this helps!
2018-05-09 08:59 AM
We are able to create Snapshots with Snap Center 4.0 just fine. We have tested it. It does the snapshot fine and mirrors/snapVaults to our backup targetss fine. Just that our VSC is un-manageable due to being incompatible. It disappears from vCenter without warning and generates log errors stating that there is a problem with the VSC plugin.
2018-05-09 09:04 AM
We are aware of this...
However, this process is recommended to do once you are ready to migrate from VSC to Snap Center 4.0 which we are not yet ready.
We were trying to evaluate Snap Center 4.0 along the sides of VSC before we jumped ship in the same vCenter. We were toldat first that this would be OK after recommending to upgrade to P1D6. Turns out it only made things worse for us.
Later, I found a posting in actual NetApp documentation that VSC 6.2.X is incompatible and not supported to co-exist with Snap Center 4.0.
When brought this forward and then moreconfusion started to arise from it all.
Eventually we simply yanked Snap Center 4.0 and restored our VSC to be able to actually manage it.
At this time, we are re-evaluating our options and it seems like we will be building a new vCenter with a migration plan for VSC to Snap Center 4.0.
That way, we can at least retain our existing VSC backups while we migrate to Snap Center 4.0 in the new vCenter.