Forum Discussion

Michael_Brown_1's avatar
Michael_Brown_1
Icon for Nimbostratus rankNimbostratus
Sep 04, 2004

ITCMCommonIPPortDefinition.Address string or long ?

Hi,

 

I've just loaded the SDK and am playing around with the C samples and the sample from the video demo. I keep getting the error that the ITCMCommonIPPortDefinition.Address is actually expecting a long value rather than a string. This seems to be what is defined in the ITCMCommon definitions that I have.

 

If it really is supposed to be a long, how do I represent the IP address correctly ???

 

Thanks, Mike.

6 Replies

  • Hi Joe,

     

    Thanks for getting back with me. I'm coding in C (VS.NET 2003). I'm getting the SOAP fault at runtime: "cannot implicitly convert String to Long". This is the code snippet:

     

     

    node_defs[0].address = txtAddress.Text.Trim();

     

     

    I am using BigIP 4.5.10 and iControl SDK 4.6.2.

     

     

    It looks, from the thread you referred me to, like there is a bug in the 4.6.2 SDK. Is the bug in the SDK only ? Or do I need to get my iControl interfaces on the BigIP box updated (not too likely in the short term). Also, will SDK 9.0 work with the BigIP 4.5.10 interfaces ? (it sounds like 9.0 fixed the long/string issue) If not, will a 'fixed' version of 4.6.2 be posted on downloads ? I only see 9.0 right now.

     

     

    Thanks for all your help !

     

    Mike.
  • Wow, that's 2 posts for the IPAddress today. Check out my history of the IPAddress at this .

     

     

    With that being said, can you provide some more specifics and possibly some code as to the problem you are having.

     

     

       

    1. BIG-IP Version

       

    2. iControl SDK Version

       

    3. Language

       

    4. Which sample, or a snippet of the offending code

       

    5. Is the error a compile time issue or is a SOAPFault returned from the server.

       

     

     

    Thanks, and I'll be waiting to hear from you...

     

     

    -Joe
  • Thanks again Joe !

     

    I actually found the 'offending line' in the SDK WSDL files and fixed it. Then I redirected my Web Reference to the local WSDL rather than the server WSDL and was able to get past the bug.

     

    I'd be very interested in the fixed SDK though. It would be something that we should have on our 4.5.10 servers if we continue to pursue iControl based solutions.

     

    See you ! Mike.
  • This is a problem with the WSDL documents in the SDK. It does effect the product in the fact that we host the WSDL documents on the server as well so if you are getting your references directly from the BIG-IP, you'll need to wait for the fix in an upcoming release (or copy the WSDL docs in the updated SDK).

     

     

    I've uploaded a corrected version to DevCentral but we are having technical difficulties getting it displayed in the downloads section. I'll send you a private message as to a direct link until we get the downloads page working.
  • My pleasure. I sent you a personal message on devcentral with the location of the updated SDK. Keep us informed in what you are up to.

     

     

    -Joe
  • I just realized I didn't answer your question about the 9.0 SDK. The 9.0 interfaces are not backward compatible to 4.x. We do provide a subset of the 4.x methods on our 9.0 platform for migration efforts but we recommend using the new interfaces only when accessing a 9.x device and using the 4.6.2 SDK for all 4.x platforms.

     

     

    -Joe