Onboard a Clustered Secure Firewall Threat Defense Device

Onboard a threat defense device that has already been clustered with the following procedure:

Before you begin

The following devices support clustering:

  • Secure Firewall 3100 devices

  • Firepower 4100 devices

  • Firepower 9300 devices

  • Threat Defense Virtual device (AWS, Azure, VMware, KVM, GCP)

Note the following limitations for clustered devices:

  • Devices must be running at least version 6.4.

  • Devices must be managed by a physical or virtual Secure Firewall Management Center.

  • Firepower 4100 and Firepower 9300 devices must be clustered through the device's chassis manager.

  • Secure Firewall 3100 devices, KVM, and VMware environments must be clustered through the Secure Firewall Management Center UI.

  • Azure, AWS, and GCP environment clusters must be created through their own environment and onboarded to Secure Firewall Management Center.

Procedure

Step 1

Log in to Security Cloud Control.

Step 2

In the left pane, click Security Devices.

Step 3

Click the blue plus button to Onboard a device.

Step 4

Click FTD.

Step 5

Under Management Mode, be sure FTD is selected.

By selecting FTD, you are retaining Secure Firewall Management Center as the managing platform. If you select FDM, this switches the manager from Secure Firewall Management Center to a local manager such as the Firewall Device Manager or cloud-delivered Firewall Management Center. Note that Switching managers resets all existing policy configurations except for interface configurations and you must re-configure policies after you onboard the device.

Step 6

On the Onboard FTD Device screen, click Use CLI Registration Key.

Step 7

Enter the device name in the Device Name field. This could be the hostname of the device or any other name you choose.

Step 8

In the Policy Assignment step, use the drop-down menu to select an access control policy to deploy once the device is onboarded. If you have no policies configured, select the Default Access Control Policy.

Step 9

Specify whether the device you are onboarding is a physical or virtual device. If you are onboarding a virtual device, you must select the device's performance tier from the drop-down menu.

Step 10

Select the essentials licenses you want applied to the device. Click Next.

Step 11

Security Cloud Control generates a command with the registration key. Paste the entire registration key as is into the device's CLI.

Step 12

The device starts to onboard. As an optional step, you can add labels to your device to help sort and filter the Security Devices page. Enter a label and select the blue plus button. .

What to do next

Once the device is sychronized, Security Cloud Control automatically detects that the device is clustered. From here, select the device you just onboarded from the Security Devices page and select any of the options listed under the Management pane located to the right. We strongly recommend the following actions:

  • If you did not already, create a custom access control policy to customize the security for your environment. See FDM-Managed Access Control Policy for more information.

  • Enable Cisco Security Analytics and Logging (SAL) to view events in the Security Cloud Control dashboard or register the device to an Secure Firewall Management Center for security analytics.