This post is more than 5 years old
4 Posts
0
3952
March 25th, 2009 17:00
XAM 1.0 C-Clip Reads
I am converting a custom Centera API application to use XAM 1.0. In testing our prototype, reading and writing new data works fine. However, reads of existng C-Clips sometimes fail and the failures seem to be tied to what version of CenteraStar we are reading from. Is it simply impossible to read existing clips from pre-4.0.1 Centeras using XAM? If so, I will have to re-think this project.
Rick
No Events found!
gstuartemc
2 Intern
•
417 Posts
0
March 26th, 2009 03:00
You are correct - as the XAM SDK has a dependency on CentraStar 4.0.1 then the cluster must be upgraded to that revision in order for the data to be retrievable using XAM.
However, if your environment has old clusters that cannot be upgraded (and you do not wish to perform a data migration to newer levels of Cenetera nodes), it is possible to have code that uses both the Centera SDK API calls and the XAM SDK ones. For this situation, you would require the matching FPLibrary files for the base SDK libraries that form part of the Centera VIM deliverables. These can be supplied on request.
RickS1
4 Posts
0
March 26th, 2009 05:00
Thank you for the prompt response. I guess if I want to stick with XAM I'll have to take a two-pronged approach:
- attempt to connect using XAMLibrary.connect()
- if that fails, try to connect using the API
Assuming the XAM connection succeeds, do I need to check the Centera code level after connection? Or if it succeeds does that mean I am in the clear? Are there XAM properties that allow me to check the firmware level?
Rick
gstuartemc
2 Intern
•
417 Posts
1
March 26th, 2009 05:00
A more foolproof method would be to attach using the Centera SDK, call FPPool_GetPoolInfo and thencheck the CentraStar level contained in the version field of the FPPoolInfo structure.
If you attempt to connect using XAMConnect then it will fail if the CentraStar version is too low - if it succeeds then you know the level is high enough and you don't need to pull it back!
However, you an pull it back using the com.emc.centera.poolinfo.version field on the XSystem connection object.
gstuartemc
2 Intern
•
417 Posts
0
March 26th, 2009 06:00
Send an email to CenteraIntegrationConsulting@EMC.com outlining your requirements (reason for wanting it and the XAM SDK version you are using).
RickS1
4 Posts
0
March 26th, 2009 06:00
Great, thanks for the advice. One last question: how do I go about getting the XAM-compatible SDK library?
Rick
RickS1
4 Posts
0
April 9th, 2009 12:00
Thank you for your help, Graham. I've been able to get my test code working bi-modally using both XAM and the API together using the supplied libraries.
One point I wanted to add to this thread, for others' future reference: When I started working with the XAM-compatible SDK library, occasionally I would see a JVM crash and a message about "call to terminate after receiving instance of FPUnsupportedException". After debugging for a bit and some more help from Graham (offline), this appears to have been caused by a mismatch between the FPLibrary.jar from SDK 3.2 which I was trying to use with the new native libraries. Upgrading to a new jar appears to have fixed that issue.
I appreciate the time and effort Graham put in to help me work through this problem.
Sincerely,
Rick