Unsolved
This post is more than 5 years old
1 Rookie
•
73 Posts
0
2025
July 2nd, 2014 04:00
SMI-S
I am trying to discover my EMC VMAX from my IBM TPC application.
I have installed the SMI-S provider and when I type dv within the TestSMIProvider.exe I can see my VMAX listed.
However from the TPC application when I add the system including the host ip, port, username, password etc I am getting an error message saying The SSL information is not valid.
Any ideas on how to troubleshoot these SSL issues. I have looked at the release notes.
No Events found!


Steve0_2012
1 Rookie
•
73 Posts
0
July 2nd, 2014 04:00
admin/#1Password as per TestSMIProvider.exe
M_Salem
213 Posts
1
July 2nd, 2014 04:00
When you run the testsmiprovider.exe, is should prompt you whether you want to use no_ssl (default) or ssl?
Can you please type ssl and update us if it is working?
Hope that helps
Mohammed Salem
M_Salem
213 Posts
0
July 2nd, 2014 04:00
Hello Steve,
Welcome to EMC Community
What is the username and password you are using?
Hope that helps
Mohammed Salem
Steve0_2012
1 Rookie
•
73 Posts
0
July 2nd, 2014 06:00
I have tried ssl also. It chnages the port but I still cannot log in. A different error message this time saying the USER ID and Password may not be correct. Please check host and ports also.
M_Salem
213 Posts
1
July 2nd, 2014 12:00
Can you please share ECOM logs?
Dream93
72 Posts
1
July 2nd, 2014 20:00
I am probably missing something - if testsmisprovider is working properly with the provider and giving results for the queries, isn't the problem is probably with TPC (the app you are using)?
Few suggestions:
1. Since SMI-S/ECOM is nothing but HTTP Server, can you observe the packets that TPC app sending to server? please try with HTTP (not https), as its probably easy to see the packets that TPC is sending.
And yes, i never used TPC so cannot give you actual answer - but this is generally what i do when i trouble shoot any issues while interacting with provider (in fact, if TPC uses CIM-XML protocol underneath you can actually compare the relative packets used by testsmisprovider with TPC side by side).
2. btw, is TPC app remote to the provider? if yes, can you try running from the machine where SMI-S is, just to avoid network out of the picture?
3. And also since ur TPC app is giving error related to 'SSL', see by disabling auth in provider and see if functionality works (if the provider is in windows machine, you can disable the auth by "C:\Program Files\EMC\ECIM\ECOM\conf\Security_settings.xml" by following setting:
And yes, do restart the service after the setting change...
Regards.
Steve0_2012
1 Rookie
•
73 Posts
0
July 3rd, 2014 00:00
I got it to work late yesterday by pointing TPC at the VMAX ip. I had being pointing it to the server where SMI-S was installed. Also I change the namespace from root/emc (which is set in the testsmiprovider.exe) to Interop.
Thanks for the support.