Commit Migration Changes Manually to Cloud-delivered Firewall Management Center

We recommend committing migration changes manually if you are convinced with your changes and not waiting for Cisco Defense Orchestrator to auto-commit changes. The window shows the number of days remaining to revert to the management center as your device manager or change your actions and commit the migration changes to Cloud-delivered Firewall Management Center. During the evaluation period, you have an opportunity to change specified actions for selected threat defense devices before committing the changes.

When a device is associated with a site-to-site VPN topology, Cisco Defense Orchestrator automatically selects its peer devices that belong to the same or different topologies for all specified commit actions.

Once the changes are committed, you can't revoke the actions specified in the window.

Note

The commit manager changes actions are disabled in the following conditions:

  • The 14-day evaluation period has passed.

  • The threat defense devices have been revered or deleted, in which case, no further actions can be taken.

Procedure


Step 1

On the migration jobs page, click the under the Actions column of a completed job.

Step 2

Click Commit Migration Changes. This link is available only when the job is completed successfully.

Step 3

If you want to change the actions specified for a device, select the device, and in the Actions list, select an action:

  • Retain on OnPrem FMC for Analytics: After committing the changes, analytics management for selected threat defense devices is retained on the management center.
  • Delete Threat Defense from OnPrem FMC: After committing the changes, the selected devices are removed from the management center and are available for Cisco Defense Orchestrator to handle the analytics. You must configure the threat defense to send events to Cisco Defense Orchestrator for managing analytics. Once the threat defense devices are deleted from the management center, they cannot be revoked.
  • Revert Manager to OnPrem FMC: After committing the changes, the device management is returned to the management center from Cisco Defense Orchestrator.
    Note
    • After committing this action, you can't change the management of the device to Cisco Defense Orchestrator again.

      Workaround: You must remove the device from the management center and onboard it. Then, you can change the management of the device in Cisco Defense Orchestrator.

    • After committing this action, the device does not show an "Out-of-Date" status in the management center.

      Workaround: On the on premises management center, deploy the changes to the device.

Step 4

Click Commit executes your specified actions immediately without further confirmation.

Step 5

On the migration jobs screen, you can expand the job to check the progress of the actions specified.