Troubleshooting Licensing

This section cites problems you may encounter with VCS licensing. It provides instructions on how to validate license keys and lists the error messages associated with licensing.

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 system
   
     License Key              = XXXX-XXXX-XXXX-XXXX-XXXX-XXXX
     Product Name              = VERITAS Cluster Server
     License Type              = PERMANENT
     OEM ID              = 4095
   
     Features :=
     Platform              = HP-UX
     Version              = 4.1
     Tier              = Unused
     Reserved              = 0
   
     Mode              = VCS
      Global Cluster Option = Enabled
3. 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.

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

Licensing Error Messages

This section lists the error messages associated with licensing. These messages are logged to the file /var/VRTSvcs/log/engine_A.log.

  [Licensing] Insufficient memory to perform operation

The system does not have adequate resources to perform licensing operations.

  [Licensing] No valid VCS license keys were found

No valid VCS keys were found on the system.

  [Licensing] Unable to find a valid base VCS license key

No valid base VCS key was found on the system.

  [Licensing] License key can not be used on this OS platform

This message indicates that the license key was meant for a different platform. For example, a license key meant for Windows is used on a Solaris platform.

  [Licensing] VCS evaluation period has expired

The VCS base demo key has expired

  [Licensing] License key can not be used on this system

Indicates that you have installed a key that was meant for a different system (i.e. node-locked keys)

  [Licensing] Unable to initialize the licensing framework

This is a VCS internal message. Call VERITAS Technical Support.

  [Licensing] QuickStart is not supported in this release

VCS QuickStart is not supported in this version of VCS .

  [Licensing] Your evaluation period for the %s feature has expired. This feature will not be enabled the next time VCS starts

The evaluation period for the specified VCS feature has expired.