4. Firepower Threat Defense 6 2: FlexConfig (Netflow)

Описание: The FlexConfig feature allows you use the Firepower Management Center to deploy ASA CLI template-based functionality to Firepower Threat Defense devices. This feature allows you to enable some of the most valuable ASA functions that are not currently available on Firepower Threat Defense devices. This functionality is structured as templates and objects that are stitched together in a policy. The default templates are officially supported by Cisco TAC Support.


Note: when deploying in a production environment consideration should be made around the deployment and type options - see below from the guide. In the video this was a lab network highlighting the usage.
https://www.cisco.com/c/en/us/td/docs...


Deployment—Select one of the following:

-Once—Commands in the object are deployed once. Use this option when you know (from testing) that the configuration commands will not be negated by commands generated for managed features upon each deployment. Also, this option is appropriate when you are clearing the configuration for a feature without intending to reconfigure it.

-Everytime—Commands in the object are deployed each time you deploy the device configuration. Test to determine if you need to first clear commands for a feature configuration before re-issuing commands on subsequent deployments. Use an Everytime deployment when it is likely, or a tested reality, that the configuration commands in the object will be removed by the deployment of managed features.

Type—Select one of the following:

-Append—(The default.) Commands in the object are put at the end of the configurations generated from the Firepower Management Center policies. You must use Append if you use policy object variables, which point to objects generated from managed objects. If commands generated for other policies overlap with those specified in the object, you should select this option so your commands are not overwritten. This is the safest option.

-Prepend—Commands in the object are put at the beginning of the configurations generated from the Firepower Management Center policies. You would typically use prepend for commands that clear or negate a configuration.