hard mirage
Had to move cluster management ips/node/sp etc to a new vlan and ips, but not sure how to edit this in snapcenter. I can't find anything in the docs about needing to change the actual cluster information, it just refers to changing svm details.
What is the process for fixing a cluster which was already added to snapcenter, and now has new management ips.
polar owl
Is this for SnapCenter or SnapCenter for VMware?
polar owl
You are not using DNS FQDN's, you are using IP's?
hard mirage
I am using fqdns, but that also changed.
I could create a cname if that would resolve it all i suppose.
I do have a ticket open as well, but its just kind of sitting there currently. Feels like this shouldnt' be that uncommon, but I sure couldn't find much on it.
polar owl
You can use swagger to rename: https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/How_to_use_Swagger_to_edit_configuration_parameters_in_SCV
Use the '/4.1/storage-system performRename' method
nocturne orbit
Use the '/4.1/storage-system performRename' method
This can only be used to rename an SVM I think
ocean latch
I would pause your jobs first. Then remove and readd each svm back in using fqdn or add back in using cluster ip which will find the svm as well. Then upgrade to 6.0.1. As that's the now the stable version with all zapi rest-api bug fixes. You can remove your snap vmware plugins and reregister as well but make sure you got a vmware admin to remove any residue. Try one svm removal and add back in the and try a backup job associated with that svm first.
polar owl
This can only be used to rename an SVM I think
I only add SVM's in my environment, not the entire cluster, however I would run the getSvmAll method and see if the cluster SVM is defined. If it is in the list, it should be able to be renamed.
polar owl
Here is better documentation of the rename procedure. This will reassociate the backups in the database with the new name. https://docs.netapp.com/us-en/sc-plugin-vmware-vsphere/rename_storage.html
Take a look at the KB in step 2 of the above link. Bulleted issue #2 is: "SVM was originally added as part of a cluster not individually". Sounds like what you need.
It may be as easy as removing and readding the renamed cluster. If the SVM names didn't change, you may be good to go. If they did change too, you will need to run the rename procedure above. I would wait for input on my Tech Support case before proceeding.
hard mirage
They didn't change, I just couldn't find a doc to say exactly what to do. Removing/adding cluster certainly sounds like the easiest approach here.
hard mirage
Well dropped the old cluster and trying to re-add with new info gives me an error. Tried restarted scv services but same error.
"Failed to add/update storage system information: Failed to connect to storage system newclustername.whatever.com.\nThis instance has already started one or more requests. Properties can only be modified before sending the first request."
Well maybe its this, but that is a bit problematic as my subdomain has a hyphen in it.
Tried ip, and creating a cname with no luck. Went ahead and escalated my support case.
ocean latch
Obviously check firewall/routing table on cluster too. Net ping etc. Make sure svm have routing set correctly
hard mirage
I had the cluster added with certificates prior to having to rename/ip it. I was trying to use the same user/certs to add it back and that seems to be related to the issue. I created a new user and was able to add it back without issue. I haven't yet flipped it back to certs as I just wanted to test a new user and it worked with l/p.
polar owl
I had a similar issue, the certificate expired. I didn't want to use a new username and password so I deleted the associated client certificate on the svm, cluster svm in your case, and there was a process to regenerate the client cert. This was a while ago, so I can't quite remember exactly what I did.