Migrating FS-VMW-10-SW-K9 to SF-FMC-VMW-10-K9 without Classic License

[brettp]

Hello, I am sorry for posting this as it's similar to existing posts, but there seems to be massive confusion across the board with migrating the "perpetual" FS-VMW-10-SW-K9 license to the SF-FMC-VMW-10-K9. Most documentation notes that this pertains to  classic licenses -- but I have always used SmartLicensing (our Firepower setup has never used Classic Licenses.) I have talked to two resellers and two Cisco techs who tell me I have to purchase and apply the new license. So... I purchased the new license, but I have conversely seen the PID swap can be handled like an RMA by the backend Cisco team. I currently have a case open with Cisco for migrating this license but even the tech isn't sure how it works. He's working on figuring it out but I figured I would ask here... Does anyone have any clue how to apply the new license, assuming I even had to purchase it, since FS-VMW-10-SW-K9 will seen be reaching Last Day of Support? Has anyone done this? Thanks!

[Sheraz.Salim · Accepted solution]

Migrating licenses in Cisco's Firepower ecosystem, especially when transitioning from older licenses like FS-VMW-10-SW-K9 to newer ones like SF-FMC-VMW-10-K9, can indeed be confusing, even for Cisco support teams. Here's a breakdown of what you need to know and how to proceed:

-Understanding the License Migration: FS-VMW-10-SW-K9: This is a perpetual license for Firepower Threat Defense (FTD) virtual instances, which is being phased out.

SF-FMC-VMW-10-K9: This is the newer license intended to replace the older one, and it is tied to Smart Licensing.

Since you've already been using Smart Licensing, the migration process should theoretically be straightforward, but Cisco's documentation and support can sometimes be unclear.

-Do You Need to Purchase the New License?

If you have a valid FS-VMW-10-SW-K9 perpetual license, Cisco typically allows a PID (Product ID) swap to the new license without requiring a new purchase. This is handled as a backend process by Cisco's licensing team.

However, if you've already purchased the SF-FMC-VMW-10-K9 license, you can proceed with applying it, but you may want to confirm with Cisco whether the PID swap is still possible to avoid unnecessary costs.

- Steps to Migrate the License

Here’s how you can proceed:
Option 1: PID Swap (If Applicable)

Contact Cisco TAC (in you case your TAC Engineer) or your Cisco account team and request a PID swap for your FS-VMW-10-SW-K9 license to the new SF-FMC-VMW-10-K9.

Provide them with your existing license details (e.g., PAK or Smart Account information).

Cisco will process the swap on their backend, and the new license will appear in your Smart Account.

Option 2: Apply the New License (If Purchased)

If you’ve already purchased the SF-FMC-VMW-10-K9 license, follow these steps:

Log in to your Cisco Smart Account.

Locate the new license in your inventory.

- Escalating the Case

If the Cisco tech you’re working with is unsure how to proceed. Request escalation to a licensing specialist or a senior engineer. Provide all relevant details, including your existing license information, Smart Account details, and the new license (if purchased). Ask for a clear explanation of whether the PID swap is still an option or if you must use the newly purchased license.

[ahollifield]

Is this an AI copy/paste?

[brettp]

Thank you for the information! Regarding option 2... if it's a perpetual license, how does the new license "take over," considering the old one never expires? I see them both in SmartLicensing but the PID of FMC in SmartLicensing still shows FS-VMW-10-SW-K9.

[Marvin Rhoads]

There's no change to the license really. It's more of a support SKU that is used for Smartnet support entitlement.

If you have the "new" license PID already appearing in your Smart account you should be able to deregister FMC and delete the old license instance. When you re-register, it should pick up the new instance since FMC itself doesn't really know whether you purchased the old SKUI or the new SKU.

Can you share a sanitized screen shot of your Smart Account license inventory showing both items?

[brettp]

Here are two screenshots. The one shows the new license being added 1/14/25 along with the old one. The other image shows the FMC (in SmartLicensing, not on the actual FMC appliance) showing that only the old PID is being used. Thanks!

[Marvin Rhoads]

I would try to unregister and then reregister the FMC to Smart Licensing and confirm if it picks up the correct association.

If that fails, perhaps you could move the old license to a different Virtual Account to prevent it from being used. Then try to reregister the FMC using a token from the correct virtual account.

[brettp]

Thank you for the suggestion. That was exactly what I was going to try before opening a case with Cisco. Ultimately, TAC told me it should automatically renew after it expires, which I questioned twice… being as though its a permanent license that doesn’t expire. I will give the de-registering / re-registering thing a try soon and hope for the best.

[brettp]

Ultimately, contacted Cisco licensing and they indeed simply update it "on the back end." I was told by 4 people I need the new license, including two TAC techs and two Cisco Resellers. So, to anyone out there, beware, you don't need the new license. Contact Cisco Licensing and have them change it manually.

[Massimo Baschieri]

The new license is mandatory in order to maintain maintenance, old license maintenance cannot be renewed after april 30