topic Hi Luis,That is correct, once in Network Security

Sourcefire - How to transfer an existing license for an RMA

mereyes — Fri, 13 Jun 2014 16:19:19 GMT

To transfer an existing license for an RMA:

Step 1: Login to the License Registration Portal

Step 2: From the Manage menu select “Devices”

Step 3: Select “Filters” and enter the license key of the DC in “Devive/Product Instance ID” and click apply

Step 4: Select the Device checkbox, and click on the option for the menu

Step 5: Select RMA from the menu, on the screen enter the “License Key” of the destination DC. Click Next

Step 6: Agree to terms and click on Transfer to complete the RMA

Thanks,

Merv Reyes

License Program Manager

It works, Thanks for the

dhvenkat — Fri, 13 Jun 2014 17:54:55 GMT

It works, Thanks for the steps

Hi Merv, The License

jiida — Tue, 10 Feb 2015 01:11:35 GMT

Hi Merv,

The License registration Portal interface has been updated, therefore the process has been changed.

Could you please update the process posted here?

Thanks,

Jun

Hi All,The license portal is

dhvenkat — Fri, 13 Feb 2015 20:52:48 GMT

Hi All,

The license portal is updated the steps to perform RMA is modified, please check on the document attached for detailed steps.

Thanks,

I won't be physically sending

shadowplay101 — Wed, 01 Jul 2015 17:39:53 GMT

I won't be physically sending the defective device to Cisco so I won't have an RMA#, so will these steps still work to transfer a license from a failed device to a replacement device?

Thanks

Hi Luis,It will work, RMA# is

dhvenkat — Wed, 01 Jul 2015 17:42:56 GMT

Hi Luis,

It will work, RMA# is not a mandatory field.

Please try it.

Thanks,

V.Dhanasekaran

Thanks for the straight

shadowplay101 — Wed, 01 Jul 2015 17:53:49 GMT

Thanks for the straight answer!

One more question. I want to try this myself before I add these steps to a document for my field techs.

I have 2 working WLCs, if I try this, will the WLC reported as 'defective' will be tagged as so in Cisco's database and no longer be able to receive support for it?

I see how some people might be able to take advantage of this in order to use the same license on multiple devices.

Thanks again.

Hi Luis,That is correct, once

dhvenkat — Wed, 01 Jul 2015 18:35:08 GMT

Hi Luis,

That is correct, once you transfer the license to new device all license support for old device will no more exist.

So you cannot take advantage of using same license on multiple devices.

Thanks,

V.Dhanasekaran

Hi All,The license portal is

dhvenkat — Wed, 01 Jul 2015 18:41:51 GMT

Hi,

jackson.ku — Tue, 16 Aug 2016 03:07:00 GMT

Hi,

As I know the license key is depend on DC. If we replace the sensor and use the same DC, how can we get the new license key to transfer the license?

Best Regards,

Jackson

Hi,

jackson.ku — Tue, 16 Aug 2016 03:07:35 GMT

Hi,

As I know the license key is depend on DC. If we replace the sensor and use the same DC, how can we get the new license key to transfer the license?

Best Regards,

Jackson

Hi Jackson,

Pujita Patni — Tue, 16 Aug 2016 16:17:52 GMT

Hi Jackson,

If you are using the same DC and just replace the sensor, you will not need to re-host the License. The License is dependent on the License Key of the DC. So if you do not change the DC, you will not need to re-host the License for your sensors.

Thanks,

Pujita Patni

Rate if it helps !

Re: Hi Jackson,

joselfra — Tue, 24 Mar 2020 03:02:17 GMT

Hi Pujita/Jackson,

If my customer has 2 IPS with their Serial numbers and The FirePOWER 7115 Control License SKU & PAK (Perpetual) which were installed on a current FMC, right now, this FMC will be deprecated, and the newest one has no the licenses, my question is:

1. Do the new FMC need internet connection to process the "Re-Host" process and generate the new licenses to the new FMC?

2. The steps described on the document you shared in this post, can be performed by the customer or do they need to open a TAC case to request this?

regards!

Luis

Firepower Licensing

Marvin Rhoads — Tue, 24 Mar 2020 03:21:21 GMT

@joselfra This discussion thread is 4 years old. I suggest starting a new discussion.