Standalone Firepower Management Center Model Migration Workflow

Use the following workflow to migrate your Firepower Management Center from the source model to the target model.

Table 1. Standalone Firepower Management Center Model Migration Workflow

1

Create a backup file in the source Firepower Management Center.

Back up the Firepower Management Center

Note 

In addition to Back Up Configuration, you must also select Backup Events and Backup Threat Intelligence Director. If Threat Intelligence Director is not enabled, the option to select TID backup does not appear.

2

Set up the target FMC.

Prepare for Migration

3

Copy the generated backup file to the target FMC.

Upload a Backup File

4

Disconnect the target FMC from the network.

Physically disconnect (unplug) the target FMC device from the network.

5

Execute the migration script in the target FMC.

Firepower Management Center Model Migration Script

6

Unregister your source Firepower Management Center from the Cisco Smart Software Manager.

Deregister a Firepower Management Center from the Cisco Smart Software Manager

7

Disconnect the source FMC from the network.

Physically disconnect (unplug) the source FMC device from the network.

8

Connect the target FMC to the network. Note that it may take a few minutes for the managed devices to establish a heartbeat with the target FMC.

See the Getting Started Guide for your Firepower Management Center model.

9

Enable smart licensing in the target FMC.

License Requirements for Firepower Management Center

10

Verify that a heartbeat is established for all devices managed by target FMC.

After a successful migration, the target Firepower Management Center has the IP address that the source model had before migration. Log in to the target FMC and verify that all configurations are restored and that basic FMC operations such as policy editing, deployment, and scheduled jobs work as expected.

High Availability Firepower Management Center Model Migration Workflow

Use the following workflow to migrate your Firepower Management Center High Availability setup from the source models to the target models.

Table 2. High Availability Firepower Management Center Model Migration Workflow

1

Create a backup file in each of the source Firepower Management Centers.

Back up the Firepower Management Center

Note 

In addition to Back Up Configuration, you must also select Backup Events and Backup Threat Intelligence Director. If Threat Intelligence Director is not enabled, the option to select TID backup does not appear.

2

Set up the target Firepower Management Centers.

Prepare for Migration

3

Copy the generated backup files to the target Firepower Management Centers.

Upload a Backup File

4

Disconnect target Firepower Management Centers from the nework.

Physically disconnect (unplug) the target FMC devices from the network.

5

Execute the migration script in the target FMCs.

Firepower Management Center Model Migration Script

6

Verify that the data migrated successfully to the target FMCs.

After a successful migration, the target Firepower Management Center has the IP address that the source model had before migration. Log in to the target FMC and verify that all configurations are restored and that basic FMC operations such as policy editing, deployment, and scheduled jobs work as expected.

7

Unregister your source Firepower Management Centers from the Cisco Smart Software Manager.

Deregister a Firepower Management Center from the Cisco Smart Software Manager

8

Disconnect source Firepower Management Centers from the network.

Physically disconnect (unplug) the source FMC devices from the network.

9

Connect the target Firepower Management Centers to the network. Note that it may take a few minutes for the managed devices to establish a heartbeat with the target FMCs.

See the Getting Started Guide for your Firepower Management Center models.

10

Validate connectivity between the target FMCs.

Viewing Firepower Management Center High Availability Status

11

Pause FMC HA synchronization from Active Firepower Management Center and wait for the operation to complete.

Pausing Communication Between Paired Firepower Management Centers

12

Resume FMC HA synchronization from Active Firepower Management Center and wait for the operation to complete.

Restarting Communication Between Paired Firepower Management Centers

13

Verify that the FMC HA configuration is healthy, and alerts are cleared.

Viewing Firepower Management Center High Availability Status

14

Register smart licensing in the target primary Active FMC.

License Requirements for Firepower Management Center

15

Verify that heartbeat is established for all devices managed by the target Firepower Management Centers.

After a successful migration, the target Firepower Management Centers have the IP address that the source model had before migration. Log in to the target FMC and verify that all configurations are restored and that basic FMC operations such as policy editing, deployment, and scheduled jobs work as expected.

Prepare for Migration

Before you begin, perform the following steps to prepare your target Firepower Management Center model for migration:

Firepower Management Center Model Migration Script

Use the following procedure to migrate your Firepower Management Center configurations from the source model to the target model. Note that this procedure is one step in the Firepower Management Center model migration. See Standalone Firepower Management Center Model Migration Workflow for the full model migration workflow.

Procedure


Step 1

Log into the target Firepower Management Center CLI in expert mode.

Step 2

Execute the migration command:

sf-migration.pl backup_file_path

Example:

[root@firepower:/var/sf/backup#
[root@firepower:/var/sf/backup# /var/sf/bin/sf-migration.pl /var/sf/backup/100LocalBackup-2019examp.tar

Once the migration process is complete, the system reboots.


What to do next

Return to Standalone Firepower Management Center Model Migration Workflow or High Availability Firepower Management Center Model Migration Workflow and complete all remaining steps.