Understand Rebranding Device Outputs to Cisco Secure Firewall

Introduction

This document describes insight into Rebranding Device Outputs to Cisco Secure Firewall.

Prerequisites

Background Information

• Displayed device names now match other branding materials
• This creates a stronger brand and a more straightforward user experience
• No functional impact to any platforms; only the text has changed. 
• Older FTD hardware platforms (FPR1010/11XX, FPR41XX, FPR93XX) still use Firepower branding
• Some system defaults and component names can still use firepower

Requirements

Cisco recommends that you have knowledge of these topics:

• Cisco Next Gen Firewall(NGFW) portfolio

Components Used

The information in this document is based on these software and hardware versions:

• Firepower Management Center(FMC) version 7.6.0
• Firepower Device Manager(FDM) version 7.6.0
• All Virtual Firepower Threat Defense(FTD) version 7.6.0
• Cisco Secure Firewall 31XX,42XX

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.

Feature Description

How it works:

• Full model names and short model names for CSF31XX, CSF42XX, Firewall Threat Defense (FTD) Virtual, and all Firewall Management Center (FMC) platforms contain Cisco Secure Firewall branding.
• The CSF31XX FDM software is now SFDM, Secure Firewall Device Manager.
• There are no functional components to this feature.
• There are no configuration options for this feature.

Upgrading:

• When upgrading to Secure Firewall 7.6, all relevant CLIs and GUIs updated to reflect current branding.
• No issues during upgrade for registered devices
  • If Firewall Threat Defense (FTD) is upgraded, Firewall Management Center (FMC) update its GUI with current branding.
  • If Firewall Management Center (FMC) is upgraded, all registered devices restore connectivity after upgrade as expected.

Configure

Firewall Management Center Examples

Summary Status:

• Management Center model name has Cisco branding prepended.

Configuration Information:

• Management Center model name has Cisco branding prepended.

CLI Output:

• Full model name is shown with Cisco Secure Firewall branding.

Device Management:

• Managed devices show shortened model names.
• Both Firepower (FPR1140 here)  and Secure Firewall Devices (here, 3130, 4215, and FTD on VMware) can appear together.

Firepower Devices Example

Summary status:

• Full model name is shown in device system info

• FP 11XX is shown as Firepower

System Details for Secure Firewall Device:

• Full model name is shown in device system info.
• CSF31XX is shown as Cisco Secure Firewall.

Chassis Manager for 3100 / 4200 in Multi-Instance Mode:

• Full model name is shown in device system info.
• CSF42XX chassis is shown as Cisco Secure Firewall.

Firewall Threat Defense Configuration Defaults:

• System hostname default is still firepower,

• We kept firepower, because this does not directly reference the running platform.

• This can be easily changed by the user.

Do you want to configure IPv4? (y/n) [y]:

Do you want to configure IPv6? (y/n) [y]: n

Configure IPv4 via DHCP or manually? (dhcp/manual) [manual]:

Enter an IPv4 address for the management interface [192.168.0.190]: 192.168.0.231

Enter an IPv4 netmask for the management interface [255.255.255.0]:

Enter the IPv4 default gateway for the management interface [data-interfaces]: 192.168.0.254

Enter a fully qualified hostname for this system [firepower]:

Enter a comma-separated list of DNS servers or 'none' [x.x.x.x]:

Enter a comma-separated list of search domains or 'none' []:

If your networking information has changed, you need to reconnect.

Firewall Device Manager Examples

Summary Status:

• Main device page shows full model name with Secure Firewall branding.

Firewall Threat Defense CLI Output:

• Full model name is shown with Secure Firewall naming.
• This is also shown on SSH logins.
• Other CLI output, such as show version, uses Secure Firewall instead of Firepower.

Manage the device locally? (yes/no) [yes]:

Configuring firewall mode to routed.

Update policy deployment information

    - add device configuration

Successfully performed firstboot initial configuration steps for Secure Firewall Device Manager for Secure Firewall Threat Defense.

> show version

-------------------[ firepower ]--------------------

Model                     : Cisco Secure Firewall 3130 Threat Defense (80) Version 7.6.0 (Build 13)

UUID                      : 123ab4d5-e6aa-11bb-ccc7-f888d99f000d

VDB version               : 377

----------------------------------------------------

Firewall Device Manager System Monitor:

• System monitoring dashboard also uses correct model name.