Applies To:Show Versions
BIG-IQ Centralized Management
- 7.0.0, 6.1.0, 6.0.1
Evaluating and Deploying Changes
How do I evaluate changes made to managed objects?
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.
Overview of evaluating changes made to managed objects
How do I deploy changes made to managed objects?
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.
Change managed object workflow
How does deployment to devices in a cluster work?
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.
Evaluate Access configuration changes
- To accept the default, proceed with the evaluation. The settings from the managing BIG-IQ overwrite the settings on the managed BIG-IP device.
- To override the default, re-discover the device and re-import the service. The settings from the managed BIG-IP device overwrite any changes that have been made using the BIG-IQ.
- Log in to the BIG-IQ system with your user name and password.
- Click Deployment.
Under EVALUATE & DEPLOY, select
The screen opens a list of Access evaluations and deployments that have been created on this device.
Under Evaluations, click Create.
The New Evaluation screen opens.
- In the Name field, type in a name for the evaluation task you are creating.
- In the Description field, type in a brief description for the evaluation task you are creating.
For the Source, select what you want to evaluate.
- To compare the object settings currently on the managed device with the object settings in the pending version, select Current Changes.
- To compare the object settings currently on the managed device with the object settings in a stored snapshot, select Existing Snapshot, then choose the snapshot you want to use.
- For Supporting Objects, select Include associated LTM Objects to deploy an Access configuration with associated LTM objects.
In the Target settings, from the
Group list, select the Access group that you want to
Devices in the group display in the Available field.
Move the devices that you want to evaluate to the
Note: If you are evaluating a device that is a member of a cluster set to initiate BIG-IP DSC sync at deployment, you can select either member of the HA pair.Note: If you are evaluating a device that is a member of a cluster set to ignore BIG-IP DSC sync, you should select both devices in the cluster.
- If you want to apply access policies on each BIG-IP device after deployment, select Automatically apply policies after deployment.
Review the evaluation to determine whether you are going to deploy it or
If there are critical errors, you cannot deploy these changes. Click
each error to see what it is, and then go back to where you made the
change to fix it.
After resolving any critical errors, you can come back and repeat the evaluation.
If there are verification warnings, you can still deploy your changes,
but you will probably want to resolve the warnings first. Click each
warning to see what it is, and then go back to where you made the change
to fix it.
After resolving any verification warnings, you can come back and repeat the evaluation.
If there are no critical errors or verification warnings, review the
changes by clicking the view link.
Each change is listed. You can review each one by clicking the name.Note: When you create an evaluation to deploy an ASM or AFM object that is referenced by a Local Traffic & Network object, it can trigger a verification error. This occurs for a few related object types that require manual intervention before you can deploy objects that reference them. To deploy these objects, you must deploy the related object and the object that references it using the Local Traffic & Network user interface. In some cases, before you deploy, you need to pin the related object to a pinning policy that establishes the relationship between a device and that object.
- If you get a verification error that requires a Local Traffic & Network deployment, use the partial deployment option to deploy the Local Traffic & Network object. After you complete the partial deployment, you can complete the deployment that triggered the error.
- If you get a verification error with a Pin Object button that requires a Local Traffic & Network deployment, click the button to associate the two objects, and then use the partial deployment option to deploy the Local Traffic & Network object. After you complete the partial deployment, you can complete the deployment that triggered the error.
- When you finish reviewing the differences, click Cancel.
- If there are critical errors, you cannot deploy these changes. Click each error to see what it is, and then go back to where you made the change to fix it.
- If the evaluation shows that you must evaluate and deploy Local Traffic configurations, do that before you deploy this evaluation.
To apply these just-evaluated object changes to the managed device, they must be deployed. Refer to Deploy configuration changes for instructions.
Deploy the Access configuration
Log in to the BIG-IQ system with your user name and password.
Important: You must log in as an Administrator, Access Manager, or Access Deployer user to perform this task.
- Click Deployment.
Under EVALUATE & DEPLOY, select
The screen displays a list of Access evaluations and deployments defined on this device.
Click the name of the evaluation that you want to deploy.
The View Evaluation screen opens.
Specify whether you want to deploy the changes immediately or schedule
deployment for later.
The process of deploying changes can take some time, especially if there are a large number of changes. During this time, you can click Cancel to stop the deployment process.Important: If you cancel a deployment, some of the changes might have already deployed. Cancel does not roll back these changes.
- To deploy this change
- Select Deploy Now.
- Click Deploy to confirm.
- To deploy this change
- Select the Schedule for later check box.
- Select the date and time.
- Click Schedule Deployment.
- To deploy this change immediately:
- If you chose to deploy immediately, the changes begin to deploy and the Status column updates as it proceeds.
- If you choose to delay deployment, the Status column displays the scheduled date and time.
Access deployment errors and warnings: causes and resolutions
|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.|