Manuals+

Backup and Restore

About Backup and Restore

The ability to recover from a disaster is an essential part of any system maintenance plan. As part of your disaster recovery plan, Cisco recommends performing periodic backups to a secure remote location.

On-Demand Backups: You can perform on-demand backups for the FMC and 7000/8000 series devices from the FMC. You can also use the local web interface on a 7000/8000 series device. Local backup management on 7000/8000 series devices is slightly different and has fewer options than backup management on the FMC, but in general works the same way. The FMC can back up these devices remotely.

For more information, see Backing Up FMCs or Managed Devices.

Scheduled Backups: You can use the scheduler on an FMC or 7000/8000 series device to automate backups. Remote device backups cannot be scheduled from the FMC.

For more information, see Scheduled Backups.

Storing Backup Files: You can store backups locally. However, Cisco recommends backing up FMCs and managed devices to a secure remote location by mounting an NFS, SMB, or SSHFS network volume as remote storage. After this, all subsequent backups are copied to that volume, but you can still use the FMC to manage them.

Restoring the FMC and Managed Devices

You restore the FMC and 7000/8000 series devices from the local Backup Management page. You cannot use the FMC to restore a device.

For more information, see Restoring FMCs and Managed Devices.

What Is Backed Up?

FMC backups can include:

  • Configurations: All configurations set on the FMC web interface are included, except for remote storage and audit log server certificate settings. In a multidomain deployment, configurations must be backed up; events or TID data cannot be backed up alone.
  • Events: Event backups include all events in the FMC database. FMC event backups do not include intrusion event review status. Restored intrusion events do not appear on Reviewed Events pages.
  • Threat Intelligence Director (TID) data: For more information, see About Backing Up and Restoring TID Data.

7000/8000 series device backups are always configuration-only.

What Is Restored?

Restoring configurations overwrites all backed-up configurations, with few exceptions. On the FMC, restoring events and TID data overwrites all existing events and TID data, with the exception of intrusion events. Ensure you understand and plan accordingly:

  • You cannot restore what is not backed up: FMC configuration backups do not include remote storage and audit log server certificate settings, requiring reconfiguration after restore. FMC event backups do not include intrusion event review status, meaning restored intrusion events do not appear on Reviewed Events pages.
  • Restoring to a configured FMC (instead of factory-fresh or reimaged) merges intrusion events and file lists: The FMC event restore process adds intrusion events to the database rather than overwriting them. To avoid duplicates, delete existing intrusion events before restoring. The FMC configuration restore process merges existing file lists with backup file lists, rather than overwriting them. To replace file lists, delete existing ones before restoring.

Requirements for Backup and Restore

Backup and restore operations have the following requirements.

Model Requirements: Backup

You can back up:

  • FMCs
  • 7000/8000 series devices

Backup is not supported for:

  • Firepower Threat Defense
  • NGIPSv
  • ASA FirePOWER

If you need to replace a device where backup and restore is not supported, you must manually recreate device-specific configurations. However, backing up the FMC does back up policies and other configurations deployed to managed devices, as well as events transmitted from those devices.

Model Requirements: Restore

A replacement appliance must be the same model as the one being replaced. Replacement managed devices should have the same number of network modules and the same type and number of physical interfaces.

Version Requirements

As the first step in any backup, note the patch level. To restore a backup, the old and new appliances must be running the same Firepower version, including patches. For FMC backups, you must also have the same VDB. The SRU is not required to match.

License Requirements

Address licensing or orphan entitlements concerns as described in the best practices and procedures. If you notice licensing conflicts, contact Cisco TAC.

Domain Requirements

To:

  • Back up or restore the FMC: Global only.
  • Back up a device from the FMC: Global only.
  • Restore a device: None. Restore devices locally.

In a multidomain deployment, you cannot back up only events/TID data; configurations must also be backed up.

Guidelines and Limitations for Backup and Restore

Backup and restore operations have the following guidelines and limitations.

Backup and Restore is for Disaster Recovery/RMA

Backup and restore is primarily intended for RMA (Return Material Authorization) scenarios. Before beginning the restore process of a faulty or failed physical appliance, contact Cisco TAC for replacement hardware.

Backup and Restore is not Configuration Import/Export

A backup file contains information that uniquely identifies an appliance and cannot be shared. Do not use the backup and restore process to copy configurations between appliances or devices, or to save configurations while testing new ones. Instead, use the import/export feature.

Restore is Individual and Local

You restore to FMCs and managed devices individually and locally. This means:

  • You cannot batch-restore to high availability (HA) FMCs or devices. The restore procedures in this guide explain how to restore in an HA environment.
  • You cannot use the FMC to restore a device. For the FMC and 7000/8000 series devices, you can use the local web interface to restore.
  • You cannot use an FMC user account to log into and restore one of its managed devices. FMCs and devices maintain their own user accounts.

Best Practices for Backup and Restore

Backup and restore operations follow these best practices.

When to Back Up

Cisco recommends backing up during a maintenance window or other time of low use. While the system collects backup data, there may be a temporary pause in data correlation (FMC only), and you may be prevented from changing configurations related to the backup. If event data is included, event-related features such as eStreamer are not available.

You should back up in the following situations:

  • Regular scheduled backups: As part of your disaster recovery plan, perform periodic backups. To automate this process, see Scheduled Backups.
  • Before upgrade or reimage: If an upgrade fails catastrophically, you may have to reimage and restore. Reimaging returns most settings to factory defaults, including the system password. A recent backup allows for a quicker return to normal operations.
  • After upgrade: Back up after upgrading to have a snapshot of your freshly upgraded deployment. It is recommended to back up the FMC after upgrading its managed devices, so the new FMC backup file reflects the upgraded devices.

Maintaining Backup File Security

Backups are stored as unencrypted archive (.tar) files. Private keys in PKI objects, which represent public key certificates and paired private keys required for your deployment, are decrypted before backup and re-encrypted with a randomly generated key upon restore.

Caution: Cisco recommends backing up FMCs and devices to a secure remote location and verifying transfer success. Backups left locally may be deleted manually or by the upgrade process, which purges locally stored backups. Because backup files are unencrypted, do not allow unauthorized access. If backup files are modified, the restore process will fail. Anyone with the Admin/Maint role can access the Backup Management page and move or delete files from remote storage.

In the FMC's system configuration, you can mount an NFS, SMB, or SSHFS network volume as remote storage. All subsequent backups will be copied to this volume, and you can still use the FMC to manage them. For more information, see Remote Storage Management and Manage Backups and Remote Storage.

Note that only the FMC mounts the network volume; managed device backup files are routed through the FMC. Ensure sufficient bandwidth for large data transfers between the FMC and its devices. For more information, see Guidelines for Downloading Data from the Firepower Management Center to Managed Devices (Troubleshooting TechNote).

Backup and Restore in FMC High Availability Deployments

In an FMC high availability deployment, backing up one FMC does not back up the other. Regularly back up both peers. Do not restore one HA peer with the backup file from the other, as a backup file uniquely identifies an appliance and cannot be shared.

Note that you can replace an HA FMC without a successful backup. For more information on replacing HA FMCs, see Replacing FMCs in a High Availability Pair.

Before Backup

Before you back up, you should:

  • Update the VDB and SRU on the FMC: Always use the latest vulnerability database (VDB) and intrusion rules (SRU). Check the Cisco Support & Download site for newer versions before backing up an FMC. This is crucial for the VDB, as VDB versions must match for restoration. Since you cannot downgrade the VDB, avoid a situation where your replacement FMC has a newer VDB than the backed-up FMC.
  • Check Disk Space: Before beginning a backup, ensure sufficient disk space on the appliance or remote storage server. The available space is displayed on the Backup Management page. Backups can fail due to insufficient space. Regularly prune backup files or allocate more disk space to the remote storage location, especially for scheduled backups.

Before Restore

Before restoring, you should:

  • Revert licensing changes: Revert any licensing changes made since the backup. Otherwise, you may encounter license conflicts or orphan entitlements after restore. Do not unregister from Cisco Smart Software Manager (CSSM); if you do, you must unregister and re-register after restoring. After the restore completes, reconfigure licensing. Contact Cisco TAC if you notice licensing conflicts or orphan entitlements.
  • Disconnect faulty appliances: Disconnect the management interface and, for devices, the data interfaces. Note that restoring an FMC or 7000/8000 series device does not change the management IP address; this must be set manually on the replacement. Ensure the old appliance is disconnected from the network before proceeding.
  • Do not unregister managed devices: Whether restoring an FMC or a managed device, do not unregister devices from the FMC, even if an appliance is physically disconnected. Unregistering requires redoing device configurations, such as security zone to interface mappings. After restoring, the FMC and devices should communicate normally.
  • Reimage: In an RMA scenario, the replacement appliance arrives with factory defaults. If the replacement appliance is already configured, reimaging is recommended. Reimaging returns most settings to factory defaults, including the system password. Reimaging is only possible to major versions, so patching may be required afterward. If you do not reimage, remember that FMC intrusion events and file lists are merged rather than overwritten.

After Restore

After restoring, you should:

  • Reconfigure anything that was not restored: This includes reconfiguring licensing, remote storage, and audit log server certificate settings.
  • Update the VDB and SRU on the FMC: Always use the latest vulnerability database (VDB) and intrusion rules (SRU).
  • Deploy: After restoring an FMC, deploy to all managed devices. After restoring a device, deploy to that device. If devices are not marked as out of date, force deploy from the Device Management page: Redeploy Existing Configurations to a Device.

Backing Up FMCs or Managed Devices

You can perform on-demand or scheduled backups for supported appliances. A backup profile is not required to back up 7000/8000 series devices from the FMC. However, FMC backups and local backups on 7000/8000 series devices require backup profiles. The on-demand backup process allows you to create a new backup profile.

For more information, see:

Back up the FMC

Use this procedure to perform an on-demand FMC backup. To back up a 7000/8000 series device from its local web interface, see Back up a 7000/8000 Series Device Locally.

Before you begin

You must read and understand the requirements, guidelines, limitations, and best practices to avoid missteps and security concerns. Careful planning and preparation are key.

Procedure

  1. Select System > Tools > Backup/Restore. The Backup Management page lists all locally and remotely stored backups and available disk space. Backups can fail if there is not enough space.
  2. Choose whether to use an existing backup profile or start fresh. FMC backups require a backup profile.
    • Click Backup Profiles to use an existing profile. Next to the desired profile, click the edit icon. You can then click Start Backup or edit the profile.
    • Click Firepower Management Backup to start fresh and create a new profile. Enter a Name for the backup profile.
  3. Choose what to back up:
    • Back Up Configuration
    • Back Up Events
    • Back Up Threat Intelligence Director
    In a multidomain deployment, configurations must be backed up; events or TID data cannot be backed up alone. For details, see About Backup and Restore.
  4. Note the Storage Location for FMC backup files (local storage in /var/sf/backup/ or a remote network volume). For more information, see Manage Backups and Remote Storage.
  5. (Optional) Enable Copy when complete to copy completed FMC backups to a remote server. Provide hostname/IP, path, username, and password. For SSH public key authentication, copy the SSH Public Key to the user's authorized_keys file on the remote server. This is useful for storing backups locally and SCPing them to a remote location. If SSH remote storage is configured, do not use Copy when complete for the same directory.
  6. (Optional) Enable Email and enter an email address to be notified when the backup completes. Configure the FMC to connect to a mail server for notifications: Configuring a Mail Relay Host and Notification Address.
  7. Click Start Backup to initiate the on-demand backup. If not using an existing profile, the system creates and uses one. You can click Save or Save As New to save the profile for later use or scheduled backups.
  8. Monitor progress in the Message Center. During backup, there may be a temporary pause in data correlation, and configuration changes might be restricted. If remote storage or Copy when complete is enabled, temporary files may be written to the remote server and cleaned up afterward.

Back up a Device from the FMC

Use this procedure to perform an on-demand backup of a 7000/8000 series device from the FMC. Backup and restore are not supported for Firepower Threat Defense at this time.

Before you begin

You must read and understand the requirements, guidelines, limitations, and best practices to avoid missteps and security concerns. Careful planning and preparation are key.

Procedure

  1. Select System > Tools > Backup/Restore, then click Managed Device Backup.
  2. Select one or more Managed Devices.
  3. Note the Storage Location for device backup files (local storage in /var/sf/remote-backup/ or a remote network volume). For more information, see Manage Backups and Remote Storage.
  4. If remote storage is not configured, choose whether to Retrieve to Management Center:
    • Enabled: Saves the backup to the FMC in /var/sf/remote-backup/.
    • Disabled (default): Saves the backup to the device in /var/sf/backup.
    If remote backup storage is configured, backup files are saved remotely, and this option has no effect.
  5. Click Start Backup to start the on-demand backup.
  6. Monitor progress in the Message Center.

What to do next: If you configured remote storage or enabled Copy when complete, verify transfer success of the backup file.

Back up a 7000/8000 Series Device Locally

Use this procedure to perform a local, on-demand backup for a 7000/8000 series device. Device backups are always configuration-only.

Note that local backup management on 7000/8000 series devices is slightly different and has fewer options than on the FMC, but generally works the same way. Unless you have a specific need (like scheduling backups), Cisco recommends using the FMC to back up these devices remotely.

Before you begin

You must read and understand the requirements, guidelines, limitations, and best practices to avoid missteps and security concerns. Careful planning and preparation are key.

Procedure

  1. On the device's local web interface, select System > Tools > Backup/Restore. The Backup Management page lists all locally stored backups and available disk space. Backups can fail if there is not enough space.
  2. Choose whether to use an existing backup profile or start fresh. 7000/8000 series local backups require a backup profile. If you do not select an existing profile during an on-demand backup, the system automatically creates and uses one. You can then use this profile for scheduled backups.
    • Click Backup Profiles to use an existing profile. Next to the profile, click the edit icon. You can then click Start Backup or edit the profile.
    • Click Device Backup to start fresh and create a new profile. Enter a Name for the backup profile.
  3. (Optional) Enable Copy when complete to copy completed backups to a remote server. This is the only option for remote storage for 7000/8000 series local backups. Provide hostname/IP, path, username, and password. For SSH public key authentication, copy the SSH Public Key to the user's authorized_keys file on the remote server.
  4. (Optional) Enable Email and enter an email address to be notified when the backup completes. Configure the device to connect to a mail server for notifications: Configuring a Mail Relay Host and Notification Address.
  5. Click Start Backup to start the on-demand backup. If not using an existing profile, the system automatically creates and uses one. You can click Save or Save As New to save the profile for later use or scheduled backups.
  6. Monitor progress in the Message Center.

Create a Backup Profile

A backup profile is a saved set of preferences, defining what to back up, where to store it, and so on. FMC backups and 7000/8000 series local backups require backup profiles. Backup profiles are not required to back up a device from the FMC. When performing an on-demand FMC or 7000/8000 series local backup without selecting an existing profile, the system automatically creates and uses one, which can then be used for scheduled backups. Note that 7000/8000 series device backups cannot be scheduled from the FMC.

The following procedure explains how to create a backup profile without performing an on-demand backup.

Procedure

  1. Select System > Tools > Backup/Restore, then click Backup Profiles.
  2. Click Create Profile and enter a Name.
  3. (FMC only) Choose what to back up. 7000/8000 series backups are always configuration-only.
    • Back Up Configuration
    • Back Up Events
    • Back Up Threat Intelligence Director
    In a multidomain deployment, configurations must be backed up; events or TID data cannot be backed up alone. For details, see About Backup and Restore.
  4. Note the Storage Location for backup files. For FMC backup profiles, this is local storage (/var/sf/backup/) or a remote network volume. For 7000/8000 local backup profiles, this is always /var/sf/backup/. For more information, see Manage Backups and Remote Storage.
  5. (Optional) Enable Copy when complete to copy completed FMC backups to a remote server. Provide hostname/IP, path, username, and password. For SSH public key authentication, copy the SSH Public Key to the user's authorized_keys file on the remote server.
  6. (Optional) Enable Email and enter an email address to be notified when the backup completes. Configure the FMC to connect to a mail server for notifications: Configuring a Mail Relay Host and Notification Address.
  7. Click Save.

What to do next: If you enabled Copy when complete, verify transfer success of the backup file.

Restoring FMCs and Managed Devices

For the FMC and 7000/8000 series devices, you use the local web interface to restore from backup. You cannot use the FMC to restore a device.

The following sections explain how to restore FMCs and managed devices.

Restore an FMC from Backup

When you restore an FMC backup, you can choose to restore any or all of the components included in the backup file (events, configurations, TID data).

Note: Restoring configurations overwrites all configurations, with few exceptions, and reboots the FMC. Restoring events and TID data overwrites all existing events and TID data, with the exception of intrusion events. Ensure you are ready.

Use this procedure to restore an FMC from backup. For more information on backup and restore in an FMC HA deployment, see Replacing FMCs in a High Availability Pair. To restore a 7000/8000 series device, see Restore a 7000/8000 Series Device from Backup.

Before you begin

You must read and understand the requirements, guidelines, limitations, and best practices to avoid missteps and security concerns. Careful planning and preparation are key.

Procedure

  1. Log into the FMC you want to restore.
  2. Select System > Tools > Backup/Restore. The Backup Management page lists all locally and remotely stored backup files. You can click a backup file to view its contents. If the backup file is not listed and you have it saved locally, click Upload Backup; see Manage Backups and Remote Storage.
  3. Select the backup file you want to restore and click Restore.
  4. Select from the available components to restore, then click Restore again to begin.
  5. Monitor progress in the Message Center. If you are restoring configurations, you can log back in after the FMC reboots.

What to do next:

  • If necessary, reconfigure any licensing settings that were reverted before the restore. Contact Cisco TAC if you notice licensing conflicts or orphan entitlements.
  • If necessary, reconfigure remote storage and audit log server certificate settings, as these are not included in backups.
  • (Optional) Update the SRU and VDB. If the SRU or VDB on the Cisco Support & Download site is newer than the currently running version, install the newer version.
  • Deploy configuration changes; see Deploy Configuration Changes.

Restore a 7000/8000 Series Device from Backup

This procedure explains how to use the 7000/8000 series local web interface to restore from backup. Restoring overwrites all configurations, with few exceptions, and reboots the device.

Before you begin

You must read and understand the requirements, guidelines, limitations, and best practices to avoid missteps and security concerns. Careful planning and preparation are key.

Procedure

  1. Log into the device you want to restore.
  2. Select System > Tools > Backup/Restore. The Backup Management page lists all locally stored backup files. You can click a backup file to view its contents. If the backup file is not listed and you have it saved locally, click Upload Backup; see Manage Backups and Remote Storage.
  3. Select the backup file you want to restore and click Restore.
  4. Make sure Replace Configuration Data is enabled, then click Restore again to begin. Device backups are always configuration-only.
  5. Monitor progress in the Message Center until the device reboots.

What to do next: Deploy configuration changes; see Deploy Configuration Changes.

Manage Backups and Remote Storage

Backups are stored as unencrypted archive (.tar) files. The file name includes identifying information such as the backup profile or scheduled task name, the backed-up appliance's display name or IP address, and the appliance's role (e.g., HA pair member).

Cisco recommends backing up appliances to a secure remote location and verifying transfer success. Backups left on an appliance may be deleted manually or by the upgrade process, which purges locally stored backups. For more information on options, see Backup Storage Locations.

Caution: Because backup files are unencrypted, do not allow unauthorized access. If backup files are modified, the restore process will fail. Anyone with the Admin/Maint role can access the Backup Management page and move or delete files from remote storage.

The following procedure describes how to manage backup files.

Procedure

  1. Select System > Tools > Backup/Restore. The Backup Management page lists available backups and available disk space. Backups can fail if there is not enough space.
  2. Do one of the following:
    • Enable or disable remote storage for backups: Click Enable Remote Storage for Backups. This option appears after configuring remote storage and toggles the setting in System > Configuration > Remote Storage Device. Tip: Quickly access remote storage configuration by clicking Remote Storage at the upper right of the Backup Management page.
    • Move a file between the FMC and the remote storage location: Click Move. You can move files back and forth; this action deletes the file from the current location. When moving a backup file from remote storage to the FMC, its storage location depends on the backup type:
      • FMC backups: /var/sf/backup
      • Device backups: /var/sf/remote-backup
    • View the contents of the backup: Click the backup file.
    • Delete a backup file: Choose a backup file and click Delete. You can delete both locally and remotely stored backup files.
    • Upload a backup file from your computer: Click Upload Backup, choose a backup file, and click Upload Backup again.
    • Download a backup to your computer: Choose a backup file and click Download. Unlike moving, this does not delete the backup from the FMC.

Backup Storage Locations

The following tables describe backup storage options for FMCs and managed devices.

Table 1: Remote Storage and Backup File Management

ToDo This
Enable or disable remote storage for backups without having to edit the FMC system configuration.Click Enable Remote Storage for Backups. This option appears only after you configure remote storage. Toggling it here also toggles it in the system configuration (System > Configuration > Remote Storage Device). Tip: To quickly access your remote storage configuration, click Remote Storage at the upper right of the Backup Management page.
Move a file between the FMC and the remote storage location.Click Move. You can move a file back and forth as many times as you want. This will delete—not copy—the file from the current location. When you move a backup file from remote storage to the FMC, where it is stored on the FMC depends on the kind of backup:
  • FMC backups: /var/sf/backup
  • Device backups: /var/sf/remote-backup
View the contents of the backup.Click the backup file.
Delete a backup file.Choose a backup file and click Delete. You can delete both locally and remotely stored backup files.
Upload a backup file from your computer.Click Upload Backup, choose a backup file, and click Upload Backup again.
Download a backup to your computer.Choose a backup file and click Download. Unlike moving a backup file, this does not delete the backup from the FMC.

Table 2: Backup Storage Locations

LocationDetails
Remote, by mounting a network volume (NFS, SMB, SSHFS).In the FMC's system configuration, you can mount an NFS, SMB, or SSHFS network volume as remote storage for FMC and device backups; see Remote Storage Management. After you do this, all subsequent FMC backups and FMC-initiated device backups are copied to that volume, but you can still use the FMC to manage them (restore, download, upload, delete, move). Note that only the FMC mounts the network volume. Managed device backup files are routed through the FMC. Make sure you have the bandwidth to perform a large data transfer between the FMC and its devices. For more information, see Guidelines for Downloading Data from the Firepower Management Center to Managed Devices (Troubleshooting TechNote).
Remote, by copying (SCP).For the FMC and for 7000/8000 series local backups, you can use a Copy when complete option to securely copy (SCP) completed backups to a remote server. Compared with remote storage by mounting a network volume, Copy when complete cannot copy to NFS or SMB volumes. You cannot provide CLI options or set a disk space threshold, and it does not affect remote storage of reports. You also cannot manage backup files after they are copied out. This option is useful if you want to store backups locally and SCP them to a remote location. It is also your only option for remote storage for 7000/8000 series local backups. Note: If you configure SSHFS remote storage in the FMC system configuration, do not copy backup files to the same directory using Copy when complete.
Local, on the FMC.If you do not configure remote storage by mounting a network volume, you can save backup files on the FMC:
  • FMC backups are saved to /var/sf/backup.
  • Device backups are saved to /var/sf/remote-backup on the FMC if you enable the Retrieve to Management Center option when you perform the backup.
Note that you cannot save 7000/8000 series local backups to the FMC.
Local, on the device internal flash memory.Device backup files are saved to /var/sf/backup on the device if you:
  • Do not configure remote storage by mounting a network volume.
  • Do not enable Retrieve to Management Center.

PDF preview unavailable. Download the PDF instead.

backup and restore DITA Open Toolkit XEP 4.9 build 20070312; modified using iText 2.1.7 by 1T3XT

Related Documents

Preview Cisco Prime Infrastructure 2.1 Administrator Guide: Chapter 4 - Backing Up and Restoring
This chapter details the procedures for backing up and restoring Cisco Prime Infrastructure 2.1, including automatic backups, remote repositories (NFS, SFTP, FTP), command-line operations, and migration strategies.
Preview Cisco Firepower 1100 Getting Started Guide
A comprehensive guide to setting up and deploying Cisco Firepower 1100 devices, covering operating system choices (ASA and FTD), manager options (FDM, CDO, FMC), and the end-to-end deployment process using Low-Touch Provisioning (LTP) with Cisco Defense Orchestrator (CDO).
Preview Cisco Hotfixes: A Guide to Downloading, Installing, and Verifying
This document provides essential information on Cisco hotfixes, detailing how to download, install, and verify them for Cisco Secure Firewall Threat Defense and Firepower products. It covers management center and device manager deployments, troubleshooting common issues, and accessing Cisco support resources.
Preview Cisco Firepower: Introduction to Network Discovery and Identity
A comprehensive guide to network discovery, host and application data, user identity management, and NetFlow data within the Cisco Firepower System, detailing its features for network visibility, security, and control.
Preview Reset Admin Password for Cisco Firepower System
Comprehensive guide on how to reset the admin password for various Cisco Firepower system components, including Firepower Threat Defense (FTD), ASA FirePOWER Services modules, Firepower Management Centers (FMC), and NGIPSv devices. Covers procedures for lost passwords, CLI and web interface access, and different device models.
Preview Cisco Firepower Management Center 1000, 2500, and 4500 Getting Started Guide
This guide provides comprehensive instructions for installing, setting up, and configuring Cisco Firepower Management Center (FMC) appliances, including models 1000, 2500, and 4500. It covers physical interfaces, LED status, command-line and web interface access, network deployment considerations, and initial configuration steps for various software versions.
Preview Cisco Firepower 4100/9300 FXOS CLI Configuration Guide, 2.8(1)
This guide provides comprehensive instructions for configuring the Cisco Firepower 4100/9300 series using the Command Line Interface (CLI) with FXOS version 2.8(1). It covers essential topics such as initial setup, CLI overview, license management, user management, image management, security certifications, system administration, platform settings, interface management, logical devices, security modules, configuration import/export, and troubleshooting.
Preview Cisco Catalyst Center Administrator Guide, Release 3.1.3
Comprehensive guide for administering Cisco Catalyst Center, covering system settings, user management, licensing, backup and restore, disaster recovery, and cluster integration. Optimized for network visibility and performance.