You can use BIG-IQ® ADC to centrally manage resources located on BIG-IP® devices in your local network, in a public cloud like Amazon EC2, or in combination.
The first step to managing device resources is the discovery process. After discovery, you can make revisions, and then deploy the configuration changes to the managed devices for easy asset management. You can make these device configuration modifications without having to log in to each device individually.
You must have Read permissions to view the configuration settings imported from managed devices.
Before you can monitor or manage settings for configuration objects on a device, you must be managing that device.
The default behavior for the BIG-IQ® device in its role as manager is to exercise authority over the devices it manages. The settings of the managing BIG-IQ device prevail. That is, if there are differences between the current objects and settings on the managed BIG-IP® device, and the objects and settings that the managing BIG-IQ device has for that BIG-IP device, the BIG-IQ device uses the settings it already has.
In situations in which you do not want this to occur, you can overwrite the objects and settings that the BIG-IQ device recognizes for the managed device with the current objects and settings on the managed device. When you do this, settings on the BIG-IQ device (including undeployed configuration revisions) are replaced with the settings from the managed device.
Before you make changes to a local traffic object on a managed device, there are two tasks to perform to ensure that you get the expected result.
The format for an IPv4 address is I<a>.I<b>.I<c>.I<d>:I<port>. For example, 172.16.254.1:443.
The format for an IPv6 address is I<a>:I<b>:I<c>:I<d>:I<e>:I<f>:I<g>:I<h>.I<port>.For example, 2001:db8:85a3:8d3:1319:8a2e:370:7348.443. If the port is well-known to be associated with a specific port number, you can specify it by name. Using the previous example, 2001:db8:85a3:8d3:1319:8a2e:370:7348.443 becomes 2001:db8:85a3:8d3:1319:8a2e:370:7348.https.
You can use the BIG-IQ® ADC interface to add a node to a managed device.
Nodes are the basis for creating a load balancing pool. For any server that you want to be part of a load balancing pool, you must first create a node, that is, designate that server as a node. After designating the server as node, you can add the node to a pool as a pool member. You can also associate a health monitor with the node, to report the status of that server.
Using BIG-IQ® ADC to manage the devices in your network means that you can deploy configuration changes without having to log in to each individual BIG-IP® device. You can review deployment changes before you make them, and then either make the changes, or revert them.
When you deploy changes to a managed device, before the BIG-IQ device applies the configuration changes, it first does a fresh import from the managed device to ensure there are no conflicts. If there are conflicts, the default behavior is to discard any changes made on the managed device before deploying the configuration changes. You can work around this by overwriting undeployed changes. Overwriting undeployed changes performs a fresh import from the managed BIG-IP device and uses those objects and settings to overwrite any revisions performed on the managing BIG-IQ device.
You must create a deployment job and submit that job before changes to configuration objects you have made are applied to the managed device.
When you deploy a configuration job, details display in the Deployment panel's Pending list while the deployment is being processed. These details display until the job either fails or succeeds.