ARM Technical Support Knowledge Articles

Updating an ADS License Server to license RVDS features

Applies to: ARM Developer Suite (ADS), RealView Development Suite (RVDS), Tool Licensing (License Management)


If you upgrade from ADS to RVDS then following receipt of RVDS upgrade, you must apply to ARM for a new RVDS license file.

Following receipt of an RVDS license file there are now two possibilities:

1 - The License Server details have changed from the previous installation.

If this is the case then you should proceed as for a new license server installation. NOTE: Existing clients wishing to use this new License Server must also be updated to locate the new server.

The simplest scheme is to create or update the existing licensing environment variable ARMLMD_LICENSE_FILE using the port@servername scheme, for example, 8224@My_Licence_Server.

2 - The License Server details are unchanged from the previous installation.

In this case the License Server software must be updated to license the new RVDS components and the license file must be updated. If this is not done then the new license file will fail, typically with the error message "Invalid license key(inconsistent authentication code)".

Upgrading the License Server

The License Server license file "license.dat", must either be replaced by the new version supplied by ARM, or combined with the existing license file. If the license file is combined with the new license file, then the license server will support the previous tools in addition to the new RVDS components. The FAQ entry: How do I merge my license files?  discusses how to combine license files.

For the License Server to grant RVDS licenses, the License Server daemons must be updated to the version 9.0 builds or later, this means that lmgrd and armlmd daemons on the license server must be replaced by new versions from the RVDS CD. We also recommend that lmutil is also updated.

New versions of the FLEXnet/FLEXlm components for the supported license server platforms are supplied on the RVDS installation CD, for example, at the following location: Utilities\FLEXlm\\1

The version of a FLEXlm component can be identified in two ways ( in the examples below the version number associated with armlmd is examined).

>lmutil lmver armlmd
lmutil - Copyright (c) 1989-2006 Macrovision Europe Ltd. and/or Macrovision Corporation. All Rights Reserved.
FLEXnet Licensing v10.8.5.0 build 31891 i86_n3 (lmgr.lib), Copyright (c) 1988-2006 Macrovision Europe Ltd. and/or Macrovision Corporation. All Rights Reserved

>armlmd -vsn
16:30:23 (armlmd) FLEXnet Licensing version v10.8.5.0 build 31891 i86_n3
16:30:23 (armlmd) Vendor daemons must be run by the license server manager (lmgrd)

The License Server software must be upgraded along with the new Server License file. Either remove the existing License Server software and perform a new installation, or incrementally replace the old components.

NOTE: The existing license server process must of course be stopped when these changes are made and then restarted.

Article last edited on: 2010-07-28 16:31:09

Rate this article

Disagree? Move your mouse over the bar and click

Did you find this article helpful? Yes No

How can we improve this article?

Link to this article
Copyright © 2011 ARM Limited. All rights reserved. External (Open), Non-Confidential