Depending on the configuration that was implemented prior to shutting down cluster, there may be globally visible objects such as distributed consistency groups, distributed devices and globally visible local devices which require communications between both clusters to break down in a graceful manner. This is no longer an option.
The next best option may be to do a system reset. Prior to configuring it, do the ndu pre-config upgrade.
Thanks Mike and appreciate the response! Just to close the loop on this, we ended up doing a meta-volume cleanup and system-reset as this was the only workaround. We were then able to apply the upgrade and configure as a local cluster. Additionally, we had to cleanup some residual entries for cluster-2 with EMC Support's help based on https://support.emc.com/kb/84969.
MikeCram
15 Posts
0
December 16th, 2015 08:00
My best answer here is to open an SR.
Depending on the configuration that was implemented prior to shutting down cluster, there may be globally visible objects such as distributed consistency groups, distributed devices and globally visible local devices which require communications between both clusters to break down in a graceful manner. This is no longer an option.
The next best option may be to do a system reset. Prior to configuring it, do the ndu pre-config upgrade.
cconnolly1
2 Posts
0
December 16th, 2015 18:00
Thanks Mike and appreciate the response! Just to close the loop on this, we ended up doing a meta-volume cleanup and system-reset as this was the only workaround. We were then able to apply the upgrade and configure as a local cluster. Additionally, we had to cleanup some residual entries for cluster-2 with EMC Support's help based on https://support.emc.com/kb/84969.
MikeCram
15 Posts
0
December 17th, 2015 10:00
Thank you for the update and I'm happy you were able to resolve this!