2015-05-04 08:20 AM
Are there any know issues with Symmetrix acquisition with 7.0.2? We had successful acquisition with 7.0.1, then when we upgraded to 7.0.2 we started seeing this error:
"Failed to execute external utility: Failed to execute Sym CLI symcfg, because The remote client/server handshake failed. Please consult symapi and storsvd log files"
So, consulted the logs, and maybe I just don't know what I'm looking for - is there a particular error message that I should see in these logs related to this issue?
I have the 7.0.2 patches file from Ostiguy, but not sure if the patch contained for the Symmetrix is relevant, or if there is something else going on. Nothing has changed. Same server, same netcnfg file. Now, we also had 7.0.2 running on a test server in our lab environment with zero issues - acquiring happily with no errors. I just upgraded to 7.1.0 in our test environment, and still happily acquiring.
The OCI server apparently still has permissions to access the SE server, although I'm having the storage team review and ensure that this is the case and that nothing funny has happened since it seems like if it was failing in one place, it should be failing in all places. We still have 6.4.3 running in production, and we've had no issues there. All acquiring successfully.
Anyone else come across this?
2015-05-04 08:42 AM
2015-05-04 08:49 AM
Thanks for the quick reply! I'll run this past the team and see if they can review the SE server against the OCI server. As far as the obvious, the only change I made was installing 7.0.2, but maybe there was something else going on on the SE server and it turned into a perfect storm to create an issue. I'm not aware that I created any new certificates, but maybe on the SE server? I'll take a look.
2015-05-04 10:34 AM
I strongly doubt this was OCI related - this is really a SE <-> SE issue.
Since SE 7.0, mutual SSL/TLS negotiation occurs, so if either side dislikes the other side's certificate, your handshake message results
2015-05-04 11:02 AM
So, to clarify, it could be that whatever certificates are running on the OCI server might not be compatible with the certs on the SE server? Vice versa?
We went through something like this once before, where we updated the certs on the OCI server and the SE server, and it did not go well. We ended up rolling back because it caused the data sources to fail in our Lab and Production environment. It is just strange that it is only happening in one place after the 7.0.2 install, when we have OCI (in one version or another) running on three different servers. Which makes me think and agree that it's probably not an OCI issue alone.