Rehost Licenses from a Failed Product
There may be cases when your Cisco product which is reserving licenses is not accessible, i.e. due to a system failure. You have the option to rehost (or copy) the existing reserved licenses to a replacement product instance.
Procedure
In the Smart Software Manager, click the Inventory tab and click the Product Instances tab. Locate the product instance in the table and in the Actions column, from the Actions drop-down list, choose Rehost Licenses from a Failed Product.
| Step 1 |
In the Request Code window, enter the Reservation Request Code in the field provided. (You will need to first generate a Reservation Request Code from the replacement product. To learn how to generate this code, see the configuration guide for the licensed product.) (Optional) In the Notes field, you may enter a reason for rehosting the reserved licenses on a replacement product, i.e., include details of the replacement product for future reference. Click Next. |
|
System Check |
The system checks to see how many product instances are being reserved in the Smart Account/Virtual Account. The system will only allow up to a certain number of product instances reserving licenses to be rehosted based on a threshold calculation (see Insufficient License Threshold Calculation below). If the rehost will result in insufficient licenses, the threshold calculation is invoked. If there are no replacement licenses available in your inventory, you will receive the following warning message and you will not be able to continue with the rehost: “Previous Product Return Pending: The licenses on this product cannot be moved to another product because there are no replacement licenses available in your inventory, and too many other failed products are still pending removal. The licenses will be returned to your inventory when the failed product is returned. If you need assistance, please open a support case.” If replacement licenses are available, proceed to Step 2. |
| Step 2 |
Review and confirm the licenses that will be copied as reserved licenses in the replacement product, then click Generate Authorization Code. |
| Step 3 |
In the Authorization Code window, you can choose to download the Reservation Authorization Code as a file or copy it to the clipboard. Instructions for next steps are provided within this window as follows:
Click Close. |
Once the rehost is complete, you can see in Smart Software Manager under the Inventory and Product Instances tabs that the failed product and replacement product are reserving the same license(s). In the Alerts column, the failed product shows Pending Removal. Remove a failed product by contacting support. To clear the alert from the Alerts column, click the Actions drop-down menu for the failed product and choose Reset Alert to clear the alert.
Insufficient License Threshold Calculation
If rehosting a product instance reserving licenses results in insufficient licenses, the threshold calculation is invoked. The threshold is calculated at 10% of the total number of product instances reserving licenses in the Virtual Account. For example:
|
# Product Instances Reserving Licenses in the Virtual Account | # Product Instances that can be rehosted in the Virtual Account |
|---|---|
| 1-10 |
1 |
|
11-20 |
2 |
|
21-30 |
3 |
Note | Cisco Product Instances use Certification Identification that is valid for a period of one year from the date of issue. Product Instances automatically contact Cisco for this identifier when the product is used. If a product does not contact Cisco for more than 30 days, a Minor Alert is issued indicating that there may be an Internet connectivity issue. Another Minor Alert is issued if the Product Instance does not contact Cisco within 60 days of the validation date. A Major Alert is issued if the Product Instance has not contacted Cisco for 90 days. After one year, the Product Instance is assumed to be no longer valid and it is automatically removed from the portal. |