The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes the verification and configuration best practices to complete before and after the upgrade of Cisco Secure Firewall Management Center (FMC) to Version 6.6.1+.
There are no specific requirements for this document.
The information in this document is based on these software and hardware versions:
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
Review the Firepower Release Notes for the Target Version and get familiar with:
Verify the current FMC Model and Software Version:
Subject to the current and target FMC software version, an interim upgrade might be required. In the Cisco Firepower Management Center Upgrade Guide, review the Upgrade Path: Firepower Management Centers section and plan the upgrade path.
In order to upload the upgrade package to the device, complete these steps:
Backup is an important disaster recovery step, which allows to restore configuration if an upgrade fails catastrophically.
Tip: We strongly recommend to back up to a secure remote location and verify transfer success. Remote Storage can be configured from the Backup Management page.
For more information, see:
For a successful FMC upgrade, NTP synchronization is required. In order to check NTP synchronization, complete these steps:
Note: Status: "Being Used" indicates that the appliance is synchronized with the NTP server.
For more information, see Firepower Management Center Configuration Guide, Version 7.0 - Time and Time Synchronization.
Dependent upon the FMC model and target version, ensure that there is enough of free disk space available, otherwise the upgrade fails. In order to check available FMC disk space, complete these steps:
Before the update or patch installation, it is required to deploy changes into the sensors. In order to ensure that all pending changes are deployed, complete these steps:
Caution: The Inspect Interruption column indicates traffic interruption
Readiness checks assess a Firepower appliance's preparedness for a software upgrade.
In order to perform the Software Readiness Checks, complete these steps:
For more information, see Cisco Firepower Management Center Upgrade Guide - Firepower Software Readiness Checks.
Immediately after every update or patch installation, it is required to deploy changes into the sensors. In order to ensure that all pending changes are deployed, complete these steps:
Caution: The Inspect Interruption column indicates traffic interruption
In order to verify the current Fingerprint (VDB) version, complete these steps:
In order to download the VDB updates directly from cisco.com, reachability from the FMC to cisco.com is required.
Note: If the FMC does not have Internet access, the VDB package can be download directly from software.cisco.com.
It is recommended to schedule tasks to perform automatic VDB package downloads and installations.
As a good practice, check for VDB updates daily and install them on the FMC during the weekends.
In order to check the VDB daily from www.cisco.com, complete these steps:
In order to install the latest VDB into the FMC, set the periodic task weekly:
For more information, see Firepower Management Center Configuration Guide, Version 7.0 - Update the Vulnerability Database (VDB)
In order to verify the current Snort Rule (SRU), Lightweight Security Package (LSP), and Geolocation versions, complete these steps:
To download the SRU and LSP directly from www.cisco.com, reachability from the FMC to www.cisco.com is required.
Note: If the FMC does not have Internet access, the SRU and LSP packages can be downloaded directly from software.cisco.com.
Intrusion rule updates are cumulative, and it is recommended to always import the latest update.
In order to turn on the weekly download and deployment of snort rule updates (SRU/LSP), complete these steps:
For more information, see Firepower Management Center Configuration Guide, Version 7.0 - Update Intrusion Rules.
In order to verify the current Geolocation version, complete these steps:
To download Geolocation Updates directly from www.cisco.com, reachability from the FMC to www.cisco.com is required.
Note: If the FMC does not have Internet access, the Geolocation Updates package can be downloaded directly from software.cisco.com.
In order to turn on the automatic Geolocation Updates, complete these steps:
For more information, see Firepower Management Center Configuration Guide, Version 7.0 - Update the Geolocation Database (GeoDB).
In order to ensure that threat data for URL filtering is current, the system must obtain data updates from the Cisco Collective Security Intelligence (CSI) cloud. To automate this process, follow these steps:
For more information, see Firepower Management Center Configuration Guide, Version 7.0 - Automating URL Filtering Updates Using a Scheduled Task.
As part of the disaster recovery plan, it is recommended to perform periodic backups.
For more information, see Firepower Management Center Configuration Guide, Version 7.0 - Chapter: Backup and Restore.
In order to register the Cisco Firewall Management Center with the Cisco Smart Software Manager, complete these steps:
For more information, see Firepower Management Center Configuration Guide, Version 7.0 - Register Smart Licenses.
Ensure HOME_NET variable contains only the inside networks/subnets in the organization. Improper variable set definition adversely impacts the firewall’s performance.
Other variables of interest are DNS_SERVERS OR HTTP_SERVERS.
For more information, see Firepower Management Center Configuration Guide, Version 7.0 - Variable Sets.
In order to take advantage of the different cloud services, navigate to System > Integration > Cloud Services.
Tip: For cache URL expiration, leave the default Never. If stricter web reclassification is needed this setting can be modified accordingly.
Note: This setting is no longer available in FMC 7.0+ and the port is always 443.
For FMC 6.6.x
For FMC 7.0+
The SecureX integration provides instant visibility into the threat landscape across your Cisco security products. In order to connect SecureX and enable the ribbon, follow these steps:
Note: This option is available for FMC version 7.0+.
Redirect URL: <FMC_URL>/securex/oauth/callback
Second Redirect URL: <FMC_URL>/securex/testcallback
2. From the FMC, navigate to System > SecureX.
3. Turn on the toggle in the upper right corner and confirm that the region shown matches with SecureX organization.
4. Copy the Client Id and Client Password and paste them into the FMC.
5. Choose test the configuration.
6. Log in to SecureX to authorize the API Client.
7. Save the changes and refresh the browser in order to see the ribbon displayed at the bottom.
8. Expand the Ribbon and choose Get SecureX. Enter the SecureX credentials if prompted.
9. The SecureX ribbon is now fully functional for your FMC user.
5YVPsGdzrkX8q8q0yYl-tDitezO6p_17MtH6NATx68fUZ5u9T3qOEQ
Note: If any other FMC user requires access to the ribbon, that user needs to log in to the ribbon with SecureX credentials.
5. In the main SecureX portal, navigate to Integration Modules > Firepower and add the Firepower integration module.
6. Create a new dashboard.
7. Add the Firepower related tiles.
In order to enable Secure Endpoint (AMP for Endpoints) integration with your Firepower deployment, follow these steps:
Note: The status Enabled means that the connection to the cloud is established.
By default, the Firepower Management Center can connect to the public Cisco Threat Grid cloud for file submission and report retrieval. It is not possible to delete this connection. Nevertheless, it is recommended to choose the closest to your deployment cloud:
For more information, see Firepower Management Center Configuration Guide, Version 7.0 - Enabling Access to Dynamic Analysis Results in the Public Cloud.
For on-premise Thread Grid appliance integration, see Firepower Management Center Configuration Guide, Version 7.0 - Dynamic Analysis On-Premises Appliance (Cisco Threat Grid) .
Revision | Publish Date | Comments |
---|---|---|
2.0 |
13-Oct-2021 |
Updated Engineer Titles. |
1.0 |
07-Oct-2021 |
Initial Release |