Technical Tip: Control Manager license file prevents license upgrade - Internal

[cmaheu]

Description

Unable to apply new license to an appliance that was previously managed by a Control Manager (NCM).

Installed new license, however, after restarting management services, the license information is not updated in the Dashboard.

If using the Administration UI (System > Settings > System Management > License Management).  The existing key detail and new key detail displayed in the license verification pop-up window is correct. 

If using CLI,  results of the following command look correct:
dumpkey /bsc/campusMgr/.licenseKey

Scope
Version: 8.x

Solution

1.  Login to the appliance CLI as root.

2.  Check to see if /bsc/campusMgr/.licenseKeyNCM exists and review entitlements.  Type
dumpkey /bsc/campusMgr/.licenseKeyNCM

If this file exists, it will most likely reflect the current entitlements.

3.  Verify the new license entitlements are reflected in the .licenseKey file.  Type
dumpkey /bsc/campusMgr/.licenseKey

Entitlements in .licenseKeyNCM will take precedence over .licenseKey.  When a POD is removed from the Control Manager, /bsc/campusMgr/.licenseKeyNCM should be removed.  This did not always occur in older code. 

Refer to the Appendix of the Deployment Guide for information regarding license distribution in multiple appliance deployments, and License Key file locations.

4.  Delete the Control Manager license file.  Type

rm /bsc/campusMgr/.licenseKeyNCM

Note:  If High Availability system, remove the file from the Secondary Server as well (if the file exists).

5.  Restart management services (on the Primary Server) to apply changes.  Type

shutdownNAC

<wait 30 seconds>

startupNAC

6.  Verify the new entitlements are reflected in the Dashboard or type

dumpkey

Note:  If High Availability system, copy license to Secondary Server by re-applying High Availability configuration.  See License Upgrade Guide in the Document Library for details.