Yep, we already connect to the vnx fine. At home now till Monday so can't check with tool. The vmax guy says he sees us connect ok then some ssl issue disconnects us. Thanks
If you changed the port that SMI-S is listening on there is a procedure for creating a new SSL certificate. I've seen that cause these errors. Have a great weekend.
To clarify, we haven't changed anything, our server running EMC-SI 3.9 is monitoring VNX's on port 443 and VMAX on 5989. Existing VNX is fine, adding the VMAX is having the issues.
To clarify, we haven't changed anything, our server running EMC-SI 3.9 is monitoring VNX's on port 443 and VMAX on 5989. Existing VNX is fine, adding the VMAX is
Do we still need to create a new certificate? Can you point me at the doc to recreate please?
To figure out where your issue is try using a browser to connect to https://yoursmis:5989. You should get the above response. If not your SMI-S ECOM service is not running or you have a port conflict. If you can connect to the server with a browser then the issue is with ESI.
Hi Sean, the testsmiprovider.exe comes built into Solutions Enabler 8.x and above and is added when you select the SMI-S Provider during the Solutions Enabler installation.
seandefraine
9 Posts
4053
0
Posted February 26th, 2016 09:00
Yep, we already connect to the vnx fine. At home now till Monday so can't check with tool. The vmax guy says he sees us connect ok then some ssl issue disconnects us. Thanks