This post is more than 5 years old
1 Rookie
•
87 Posts
0
2471
Problem adding a DDMC storage provider
Hi
I'm using ViPR Controller vipr-2.3.0.1.846, and am trying to add a Data Domain Management Center (DDMC) as a storage provider. I select 'Storage Providers' -> 'Add', fill out the form, select 'Data Domain Management Center' as the 'Type', and click OK. I get the error message, "Failed to establish connection to the storage provider". I am able to connect via HTTPS to the DDMC, and log in using the same credentials that I provided to ViPR.
How can I diagnose this problem?
Thanks
tl
tlemons1
1 Rookie
1 Rookie
•
87 Posts
0
November 3rd, 2015 14:00
The answer to my problem was an incompatibility between ViPR V2.3 and the not-yet-released DDMC version I was using. Once I used a supported DDMC version, all was well.
Andrew291
92 Posts
0
October 23rd, 2015 06:00
Did you check the support matrix to validate you're using a supported firmware level on the data domain? You may want to try pinging the DD ip from the ViPR command line as well. Login as svcuser and your password or root login if you enabled it via the GUI settings. I don't think you need to fill out the element manager URL just the storage provider during discovery but I haven't done it in a while. You may want to try non SSL if that is an option as well. Please let me know how you make out.
tlemons1
1 Rookie
1 Rookie
•
87 Posts
0
October 26th, 2015 07:00
Thanks for the ideas. On the support matrix main page (https://elabnavigator.emc.com/eln/elnhome), I did find ViPR Software Defined Storage:
Data Domain as Filer
Data Domain is supported as described in the chart below.
Table 7 DataDomain support
OS Version(s)s 5.5.0.8, 5.5.1.3
Management Center 1.2.1
I'm testing ViPR 2.3.0.1 with DDMC 2.0; the DDRs are running 5.6 and 6.0.
I enabled 'root' ssh login in ViPR, logged in via ssh, and am able to to ping my DDMC system:
vipr1:~ # ping lfcp0154
ping: unknown host lfcp0154
vipr1:~ # ping lfcp0154.lss.emc.com
PING lfcp0154.lss.emc.com (10.241.160.154) 56(84) bytes of data.
64 bytes from lfcp0154.lss.emc.com (10.241.160.154): icmp_seq=1 ttl=64 time=0.306 ms
64 bytes from lfcp0154.lss.emc.com (10.241.160.154): icmp_seq=2 ttl=64 time=0.381 ms
64 bytes from lfcp0154.lss.emc.com (10.241.160.154): icmp_seq=3 ttl=64 time=0.272 ms
Since I'm using both DDMC and DDOS versions that are not formally supported, is this the likely problem? How can I confirm this?
Thanks!
tl
Andrew291
92 Posts
1
October 26th, 2015 13:00
I'm 99% that the fact that you're running an unsupported version is the reason it won't discover. Maybe you have another array that has a supported code version? You could also check the controllersvc.log file in ViPR under /opt/storageos/logs. It may show the version check but probably not since its not getting that far probably due to api incompatibility. Please let me know if you have other questions and mark the question as answered when you feel comfortable.
Andrew
tlemons1
1 Rookie
1 Rookie
•
87 Posts
0
October 26th, 2015 13:00
I see:
- in controllersvc.log:
2015-10-26 16:16:11,278 [pool-62-thread-1] ERROR DataDomainUtils.java (line 81) Storage Provider lfcp0154.lss.emc.com is not reachable
I did find my DDMC hostname (lfcp0154) mentioned in portalsvc.log. But staring at the XML gunk in that file for a while didn't locate anything useful to me.
I'll pursue another option to resolve this. Thanks very much for the counsel!
tl