Unsolved
This post is more than 5 years old
11 Posts
0
3089
April 21st, 2010 13:00
Issues connecting to Centera Cluster
Hello all,
I've recently started attempts for my company to integrate with EMC (Centera) and as such downloaded the EMC SDK and have begun learning some XAM. My issue is that the test code tidbits I have written are useless without being able to connect me to a test system. I came across the Centera online clusters here and have been attempting to connect to them with limited success. Code example of a simple Win32 application (in Visual C++ 6) below:
void main(int argc, char** argv)
{
xam_int vStatus;
xset_handle vXSystem;
xam_string vXRI = “snia-xam://centera_vim!128.221.200.60?C:\\emc\\xam\\xamconnect.pea”;
vStatus = XAMLibrary_Connect(vXRI,&vXSystem);
printf("Connect status: %i\n", vStatus);
...
}
I'm observing vStatus always being set to 0x3f3, aka. 1011, aka. the connection isn't being made. I'm pretty sure the xam_string is sound, since I tried a string of nonsense and the error code changed to 1008, invalid string format. I also tried removing the VIM namespace and let it default to whatever VIM it could, but the result was the same. Does anyone have any ideas what I could be doing wrong here? I've tried everything the online docs on the clusters recommended - the pea is where it is being assumed to be in the xam_string, the pea should match up to the cluster IP according to the page linked above and I have port 3218 open for TCP/UDP both ways. The only thing I can think of is the pea is the problem and I should be generating my own, but I haven't the faintest idea how I go about doing that. Any thoughts on this, or any other possible solutions?
Regards,
Jamie
mckeown_paul
409 Posts
0
April 21st, 2010 13:00
Jamie
Try emea1 with the armtesting,pea file I've used that recently. If its still a problem post and when I get into tomorrow I'll check them all out
khanz1
2 Intern
•
136 Posts
0
April 21st, 2010 14:00
Hi Jamie,
I recommend that you test the connectivity by using the PEA file with JCenteraVerify and check if you get any errors. I just tested the xamconnect.pea file with the 128.221.200.60 Centera and verified that the PEA file works. By trying first with JCenteraVerify you can isolate the problem (i.e. whether it is on the network side or is it in the code).
Thanks,
Zeeshan
jamie_mct
11 Posts
0
April 22nd, 2010 04:00
Hi Zeeshan and Paul,
I was pleasantly surprised how quick I got a reply, thanks!
@Paul: I tried emea1armtesting with all available IPs for emea1 (128.221.200.56, .58 and .59) but still saw 1011 returned. However..
@Zeezhan: Using JCenteraVerify I tried both emea1armtesting.pea against 128.221.200.56 and xamconnect.pea against 128.221.200.60 and got a successful log file back each time (see attached).
I suppose this confirms that I've opened up 3218 properly in both directions,something I was indecisive about earlier since the D-Link interface was a little ambiguous. It's a weight off my mind and I'm now scrutinising the code and my local install. I said my code above was just a snippet but in truth it contains pretty much all of my simple program bar the includes:
#include "xam.h"
#include "xam_toolkit.h"
#include "stdio.h"
All I can do now is glare at my code until I spot a runtime error, or go back and re-evaluate how I installed the SDK. Installation, for me, consisted of unzipping the lib32 folders (both XAM and VIM) and the XAM includes, then adding these directories to the include and library files respectively in my VC++ 6 directories. Could there be some additional step in my installation I haven't thought of? Again, my gratitude going forward to anyone who looks in on this discussion : )
Regards,
Jamie
2 Attachments
VerifyLog_128.221.200.60_xamconnect.txt
VerifyLog_128.221.200.56_emea1armtesting.txt