Validating license keys

The installvcs script handles most license key validations. However, if you install a VCS key outside of installvcs (using vxlicinst, for example), you can validate the key using the procedure described below.

  1. The vxlicinst command handles some of the basic validations:

    node lock: Ensures that you are installing a node-locked key on the correct system

    demo hard end date: Ensures that you are not installing an expired demo key

  2. Run the vxlicrep command to make sure a VCS key is installed on the system. The output of the command resembles:

Veritas License Manager vxlicrep utility version 3.02.003

Copyright (C) Veritas Software Corp 2002. All Rights reserved.

Creating a report on all Veritas products installed on this



Product Name = Veritas Cluster Server

License Type = PERMANENT

OEM ID = 4095

Features :=

Platform = AIX

Version = 5.0

Tier = Unused

Reserved = 0

Mode = VCS

Global Cluster Option = Enabled

  1. Look for the following in the command output:

    Make sure the Product Name lists the name of your purchased component, for example, Veritas Cluster Server. If the command output does not return the product name, you do not have a VCS key installed.

    If the output shows the License Type for a VCS key as DEMO, ensure that the Demo End Date does not display a past date.

    Make sure the Mode attribute displays the correct value.

    If you have purchased a license key for the Global Cluster Option, make sure its status is Enabled.

  2. Start VCS. If HAD rejects a license key, see the licensing error message at the end of the engine_A log file.