To change the object settings on a managed device, there are four tasks to perform.
This figure illustrates the workflow you perform to manage the objects on BIG-IP® devices. Evaluating the changes you have made is the third step in this process.
Deploying changes applies the revisions that you have made on the BIG-IQ® Centralized Management system to the managed BIG-IP® devices.
This figure illustrates the workflow you perform to manage the objects on BIG-IP devices. Deploying the settings is the last step in this process.
When you created a cluster in BIG-IQ® inventory, you chose a deployment option for the devices in that cluster.
If you chose to initiate BIG-IP® DSC® sync, and the Sync-Failover group on the BIG-IP system is configured for manual sync, after deployment to either device in the HA pair, Access kicks off manual sync to the other device. If manual sync succeeds, the deployment is successful. Otherwise, the deployment status shows an error.
If you chose to initiate BIG-IP DSC sync and the Sync-Failover group on the BIG-IP system is configured for automatic sync, after deploying to either device in the HA pair, automatic sync propagates the configuration to the other device. If automatic sync succeeds, the deployment is successful. Otherwise, the deployment status shows an error.
If you chose to ignore BIG-IP DSC sync, you must deploy the configuration from BIG-IQ to both devices in the cluster.
To apply these just-evaluated object changes to the managed device, they must be deployed. Refer to Deploy configuration changes for instructions.
|Access profile type mismatch||The deployment process imports an access profile from a device to the other devices in the Access group. If an access profile of the same name exists on a device, the access profile types must match. If it does not, a critical error occurs and deployment fails.||On the BIG-IP device, delete the access profile. Then, redeploy on the BIG-IQ system.|
|Sandbox object outside of the /Common partition||If partitions exist on the device in addition to the /Common partition, they contain sandbox objects by default. When the deployment process tries to create the sandbox objects, if the same partitions do not exist on the device, a critical error occurs and deployment fails.||On each BIG-IP device, create the same partitions. Then, redeploy on the BIG-IQ system.|
|Pools, pool members, self IPs, route domains||Access objects refer to pools, pool members, self IP addresses, and route domains, all of which are managed in ADC. If any of these objects is not present on the device, evaluation provides a warning that LTM must be deployed before Access can be deployed. If the warning is ignored, Access deployment fails.||Deploy LTM. Then re-discover LTM before trying to deploy Access.|