Forum Discussion
Jayaram_S_96796
Nimbostratus
Jul 27, 2006Can we connect once BIG-IP device and pull all the object details
Hi
We are using v4.5 and v9.1 version of BIG-IP and we are using appropriate API to connect to these BIG-IPs. Our application pulls data from from each object such as
1. VIP
2. Pool
3. Node
4. SNAT
5. Proxy etc.
We used WSDL generate classes for the API and calling the appropriate class files and authenticating and pulling the data from BIG-IP.
Do we have any means by which we can connect once to BIG-IP devices and pull all the object details in one shot?
we are currently doing something like this for pulling Pool details and similarly for other objects
oPoolConfig = new LocalLBPool();
oPoolConfig.Credentials = creds;
oPoolConfig.Url = urlBigIP;
oPoolConfig.PreAuthenticate = true;
So whats happening with this code is, we are authenticating and connecting to BIG-IP each time for pulling each object details.
Appreciate your response asap
Thanks
Jayaram
- I'm not quite sure I get your question. If you are asking whether you can, with one method call, return the configuration for all objects on the system, the answer is no. In v9.0 we made all our methods bulk-enabled, meaning, you can pull each attribute of all like-objects (ie. enabled states for all pools) in a single method call. In v4.5, all methods are singular meaning you'll have to pull down each object's attributes individually.
- ccarls_127183
Nimbostratus
Perhaps a more detailed review of the code is needed here. I think what v-jaysiv is trying to say is that based on the way they have coded their data population they are authenticating to the BigIP with each method call. Correct? - Ok, that makes a bit more sense. If you create a single instance of a interface variable and reuse it with the PreAuthenticate flag set, then it should use the same HTTP connection (and the same WWW-Authenticate header). But, saying that, I remember there being an issue with a version of apache we were using back on 4.x where KeepAlive connections with POST requests was broken so we disabled the KeepAlives to avoid this issue. I'm not sure if that carried over to our new platforms or not but you can find out by searching for "KeepAlive" in the /config/httpd/conf/httpd.conf file. If you find a value of "Off" for that configuration variable then Keep-Alives have been turned off.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects