FMC Virtual HA and Managed Device Licensing Requirements

Issue

A user running an FMC virtual platform in VMWare managing 4 Firepower Threat Defense (FTD) virtual sensors encountered confusion regarding licensing requirements for FMCv High Availability (HA) deployment.

The user owned 12 Firepower MCv Device licenses and needed clarification on whether additional licenses were required to enable FMCv HA or if existing MCv licenses could be reused for the FMC HA pairing. Specifically, the user questioned whether they could use their available 8 remaining MCv licenses to deploy the second FMCv node for FMC HA configuration.

Environment

• Cisco Secure Firewall Firepower version 7.6.2

• Standalone FMCv managing 4 FTD virtual sensors

• Available Firepower MCv Device licenses in the Smart Account

Resolution

The licensing requirements for FMCv HA were clarified through detailed analysis and user validation session.

FMCv HA Licensing Requirements

Each FMCv node in an HA pair requires its own FMCv device license of the same tier (that is, FMCv10, FMCv25, and more). The licensing behavior adheres to these principles:

• Each FMCv in the HA requires its own identical FMCv license tier.

• FMCv licenses cannot be mixed across tiers within an HA pair.

• A single FMCv license cannot be shared between two FMC HA nodes.

• Each managed device under an FMCv consumes a Firepower MCv device license.

License Calculation for HA Deployment

For FMCv HA deployment, the user requires double the amount of Firepower MCv Device licenses compared to standalone deployment:

• Standalone FMCv managing 4 FTDs: 4 Firepower MCv device licenses

• FMCv HA managing 4 FTDs: 8 Firepower MCv device licenses

User License Validation

Through Smart Licensing inventory review and Webex validation session, the user license validates:

• Confirmed ownership of 12 Firepower MCv Device licenses.

• Verified current consumption of 4 licenses for existing FTD management.

• Validated 8 remaining licenses available for HA deployment.

• Confirmed sufficient license capacity to proceed with FMCv HA.

The user was able to proceed with FMCv HA deployment using the existing available licenses without requiring additional license purchases.

Cause

The issue was caused by a misunderstanding of FMCv licensing behavior in HA deployments. The user initially believed that existing MCv licenses could be shared or reused between HA nodes, when in fact each FMCv node in an HA pair requires its own dedicated FMCv device license of the same tier. This is expected product licensing design and not a software defect, as documented in Cisco Secure Firewall licensing requirements: "For FMC Virtual High Availability, each FMC must be licensed with the same model and capacity."

Related Content

• Cisco Secure Firewall Licensing FAQ

• Cisco Technical Support & Downloads

Revision History

Revision	Publish Date	Comments
1.0	12-May-2026	Initial Release