[Info-vax] HP Integrity rx2800 i4 (2.53GHz/32.0MB) :: PAKs won't load

David Turner dturner at islandco.com
Mon Feb 15 16:18:35 EST 2016


EFI> cpuconfig threads off
EFI> reset




On 2/15/2016 3:56 PM, kennethnospam.randell at gmail.com wrote:
> On Monday, February 15, 2016 at 3:27:10 PM UTC-5, VAXman- wrote:
>> Hi,
>>
>> I'm working with a customer who has 2 HP Integrity rx2800 i4 (2.53GHz/32.0MB)
>> (from $ SHOW CPU output).  Each has a separate system disk because they will
>> be clustered at disparate sites.  The PAKs on one of the nodes load but they
>> do not load on the other.  I've checked that each node has different/unique
>> PAKs by authorization numbers.  Listed below:
>>
>>                   NODE_1                         NODE_2
>>
>>   Issuer:         VSI                           VSI
>>   Authorization:  1R-VSI-20150903-00005         1R-VSI-20150903-00007
>>   Product Name:   OPENVMS-I64-BOE               OPENVMS-I64-BOE
>>   Producer:       VSI                           VSI
>>   Units:          8                             8
>>
>>   Issuer:         VSI                           VSI
>>   Authorization:  1R-VSI-20150903-00006         1R-VSI-20150903-00008
>>   Product Name:   OPENVMS-I64-BOE               OPENVMS-I64-BOE
>>   Producer:       VSI                           VSI
>>   Units:          8                             8
>>
>>   Issuer:         VSI                           VSI
>>   Authorization:  1R-VSI-20160121-00007         1R-VSI-20160121-00009
>>   Product Name:   VMSCLUSTER                    VMSCLUSTER
>>   Producer:       VSI                           VSI
>>   Units:          8                             8
>>
>>   Issuer:         VSI                           VSI
>>   Authorization:  1R-VSI-20160121-00008         1R-VSI-20160121-00010
>>   Product Name:   VMSCLUSTER                    VMSCLUSTER
>>   Producer:       VSI                           VSI
>>   Units:          8                             8
>>
>>   Issuer:         VSI                           VSI
>>   Authorization:  1R-VSI-20160121-00011         1R-VSI-20160121-00013
>>   Product Name:   VOLSHAD                       VOLSHAD
>>   Producer:       VSI                           VSI
>>   Units:          8                             8
>>
>>   Issuer:         VSI                           VSI
>>   Authorization:  1R-VSI-20160121-00012         1R-VSI-20160121-00014
>>   Product Name:   VOLSHAD                       VOLSHAD
>>   Producer:       VSI                           VSI
>>   Units:          8                             8
>>
>>
>> On NODE_2, a $ LICENSE LOAD returns:
>>
>> %LICENSE-W-NOLOAD, license was not loaded for OPENVMS-I64-BOE
>> -LICENSE-F-EXCEEDED, attempted usage exceeds active license limits
>> %LICENSE-W-NOLOAD, license was not loaded for VMSCLUSTER
>> -LICENSE-F-EXCEEDED, attempted usage exceeds active license limits
>> %LICENSE-W-NOLOAD, license was not loaded for VOLSHAD
>> -LICENSE-F-EXCEEDED, attempted usage exceeds active license limits
>>
>> WTF?
>> --
>> VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG
>>
>> I speak to machines with the voice of humanity.
>
> Does Node 2 have hyperthreads turned on?  If so, this will double the expected license requirements.  Most IA64 systems I have seen have this turned on by default.
>




More information about the Info-vax mailing list