Monitor instances with the 4.2 BigIP

OK, here goes.

 

 

I have a simple web application, built with LAMP, which contains the 'configuration' of

 

the various F5 BigIPs we have on our network. This is not the configuration from the F5

 

appliance perspective, it's the configuration that describes how we want the devices

 

to work for our environment. We don't even use 50% of the devices flexibility; we

 

do however do some interesting stuff with rules and pools. Given that complexity, we

 

want to be able to configure and deploy the devices from a central location, reliably

 

and identically (as much as you can within the network config off course).

 

 

The application than takes the specified configuration, which contains mostly IP addresses,

 

pools, rules and monitor definitions and turns it into a large bigpipe command file (i.e.

 

shell script). I can then take that command file to a BigIP device, which has only the basic

 

'config' script run on it and finish the configuration.

 

 

This is off course inconvenient and the iControl API allows me to do most (all?) of this

 

from my application, without having to transfer a bigpipe command file. So, my first

 

step is to start building a new piece, which will undo everything I did to the device

 

with the command file (reverse order), using iControl. Once that's done, I can recreate

 

the command file functionality as well.

 

 

So, my first step was to undo all monitor instances, which I'm first trying to find. That's

 

where most of my initial questions came from. Baby steps! :-)

 

 

So, one thing I still haven't figured out is how to remove the piece described below,

 

the 'Basic Associations' for the 'Standard' services (as it shows on the GUI)? The rest

 

of what I built I have now figured out how to undo with iControl. Rebuilding using

 

iControl is next.

 

 

Hope that is clear....