[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:Welcome to the Digital UNIX Conference
Moderator:SMURF::DENHAM
Created:Thu Mar 16 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:10068
Total number of notes:35879

9699.0. "OSF-BASE PAK doesn't license this processor" by MUNICH::CUZUM () Fri May 02 1997 05:05

Hi, folks,

now I have a licensing problem:

Customer has 2 CPUs and 2 OSF-BASE licenses. He often
finds error messages like this in syslog.dated:

/var/adm/syslog.dated/25-Apr-10:15/kern.log:Apr 25 15:32:07 smu10
vmunix: OSF-BASE PAK doesn't license this processor
/var/adm/syslog.dated/27-Apr-10:25/kern.log:Apr 28 07:27:46 smu10
vmunix: OSF-BASE PAK doesn't license this processor
/var/adm/syslog.dated/28-Apr-10:25/kern.log:Apr 29 09:51:52 smu10
vmunix: OSF-BASE PAK doesn't license this processor

A "lmf list" shows both OSF-BASE licenses as active. The one shows
"active" and the other "active, multiple". The system works, so it gets
enough units from OSF-BASE. So, what's the real problem? Can anyone
explain this?


Regards,

Corina
T.RTitleUserPersonal
Name		DateLines
9699.1more infomationMUNICH::CUZUMTue May 06 1997 08:2252
    More information on this problem:
    
    Here the output of:
    # lmf full for OSF-BASE
    
    Product Name: OSF-BASE
                   Producer: DEC
                     Issuer: DEC
       Authorization Number: ATP-IL-1997FEB17-3037
            Number of units: 0
                    Version:
       Product Release Date:
       Key Termination Date: 1-JUN-1997
    Availability Table Code:
        Activity Table Code: CONSTANT=100
                Key Options:
              Product Token:
                Hardware-Id:
             License status: active
          Cancellation Date:
      Revision Number: 0
                    Comment:
          Cache Total Units: 100
            Activity Charge: 100
               Usable Units: 0
    
               Product Name: OSF-BASE
                   Producer: DEC
                     Issuer: DEC
       Authorization Number: ALS-IL-1996APR02-720
            Number of units: 100
                    Version:
       Product Release Date:
       Key Termination Date:
    Availability Table Code: A
        Activity Table Code:
     Key Options: ALPHA
              Product Token:
                Hardware-Id:
             License status: active, multiple
          Cancellation Date:
            Revision Number: 0
                    Comment:
    
    Can you tell me if this is ok? Does he need the secind
    OSF-BASE-License?
    
    The computer is an AlphaServer 2100A 5/250.
    
    Waining for a reply,
    
    Corina
9699.2Mixing apple keys & orange keysSMURF::PUSHEETue May 06 1997 14:2525
The two paks listed in .1 are inconsistent.  

The first key (Units:0, Activity table: Constant=100) is essentially
a key that will work on any system but it has  a key termination
date indicating that it will no longer be valid on 1-Jun-1997.
This does not appear to be a normal customer license key.  For
an AlphaServer 2100 the standard license key should have
no expiration date and Units:400 and Activity Table: A.

The second key (Units:100, Availability table: A) appears to
be a standard SMP extension key used for adding 1 CPU to the
AlphaServer 2100 system.  This key is designed to be combined
with the standard base license (400 units), not with the
temporary skeleton key (0 units).  Combination with the
temporary key is probably what gave the observed symptoms.

Removing (see the lmf issue command) the second key from the license 
database should let the temporary key work until it expires.  The customer
needs to get the temporary key replaced with a permanent key.
When they have that key, they should load it along with the
100 unit key.  It appears that the customer either lost or never had 
a license for the original AlphaServer 2100 uniprocessor (QL-MT4AG-6E).