HPE Storage Users Group

A Storage Administrator Community




Post new topic Reply to topic  [ 5 posts ] 
Author Message
 Post subject: 8400 keep license after moving nodes
PostPosted: Wed Apr 19, 2023 8:33 am 

Joined: Wed Feb 15, 2023 6:45 am
Posts: 8
Hi all.

I have degraded 8400 array with failed node w/o support.
New nodes ordered but it will take time to deliver.
There's also a donor offline array which already used to get spare node earlier so now it has only one node.
This donor is fully licensed with All-Inclusive Multi-System SW.
I'd like to bring donor live a bit later after spares delivered.
How this can be done to keep licenses for donor array?
What if I replace donor node disk with the disk from faulty node and use donor node with old disk in active array.
Then once spare nodes delivered, and one spare node added with kept donor node disk to that donor array -- will it keep licenses?
Another way: Then once spare nodes delivered, I replace donor node in active array with a new spare, put back donor disk to donor node and place it back to donor array.
Will any of this work?

Thanks


Top
 Profile  
Reply with quote  
 Post subject: Re: 8400 keep license after moving nodes
PostPosted: Thu Apr 20, 2023 2:03 am 

Joined: Mon Sep 21, 2015 2:11 pm
Posts: 1570
Location: Europe
admkumar wrote:
Hi all.

I have degraded 8400 array with failed node w/o support.
New nodes ordered but it will take time to deliver.
There's also a donor offline array which already used to get spare node earlier so now it has only one node.
This donor is fully licensed with All-Inclusive Multi-System SW.
I'd like to bring donor live a bit later after spares delivered.
How this can be done to keep licenses for donor array?
What if I replace donor node disk with the disk from faulty node and use donor node with old disk in active array.
Then once spare nodes delivered, and one spare node added with kept donor node disk to that donor array -- will it keep licenses?
Another way: Then once spare nodes delivered, I replace donor node in active array with a new spare, put back donor disk to donor node and place it back to donor array.
Will any of this work?

Thanks


You can extract the license from an array using "showlicense -raw".

That license is tied to the system ID shown in "showsys -d".

The system ID is tied to the physical node.

So if you kill of the last node you have in your donor system, you might have issues getting it back up in a way that it will accept the license.

Once you move a node (or node disk) from one array to another, it needs to be rescued where the entire node disk is wiped.

_________________
The views and opinions expressed are my own and do not necessarily reflect those of my current or previous employers.


Top
 Profile  
Reply with quote  
 Post subject: Re: 8400 keep license after moving nodes
PostPosted: Fri Apr 21, 2023 4:25 am 

Joined: Wed Feb 15, 2023 6:45 am
Posts: 8
Hi MammaGutt,

Thanks, that worked perfect.
Saved "showlicense" and "showlicense -raw" outputs, hopefully that will help to restore licenses after bringing donor array live again :) Will update here later.

Can you guys also remind me which parameters must be updated to join donor node to degraded cluster? It's in production so there's no option for mistake.


Code:
Whack>help prom edit
This command is used to edit the manufacturing record information which
is stored in the PROM.
Whack>prom edit
Board Spin:       06
Size * 256 bytes: 04
Board Class:      920
Board Base:       200048
Board Rev:        B4
Assembly Vendor:  FXN
Assembly Year:    2019
Assembly Week:    07
Assembly Day:     17
Assembly Serial:  004**524
System Serial:    0
Node ID:          01 [updated 00 to 01]
Midplane Type:    1b
Node Type:        40
W19:              0002**96 [donor array ID]


SMI Whack>prom hp
HW Revision:         004*
Product ID:          HP_3PAR  8400
Assembly Serial Num: PFLK********EK
Assembly Part Num:   H6Y95-63001
Saleable Serial Num: CZ******D3 [donor array S/N]
Saleable Part Num:   H6Y96B
Spare Part Num:      792653-001


Should I update both W19 and Saleable Serial Num manually to match new array?

Thanks


/upd: I am a bit confused by this post https://www.3parug.com/viewtopic.php?p=12581#p12581 where Mr. cheese2 could join donor node to cluster with w19 kept as "0fffffff".


Top
 Profile  
Reply with quote  
 Post subject: Re: 8400 keep license after moving nodes
PostPosted: Mon Apr 24, 2023 2:24 am 

Joined: Wed Feb 15, 2023 6:45 am
Posts: 8
Hi All,

Any suggestion please?
Is it OK to change both W19 and Saleable Serial Num on donor node?
Is it sort of risky thing for running degraded cluster or worst thing is donor just will not be added to cluster?

Thanks


Top
 Profile  
Reply with quote  
 Post subject: Re: 8400 keep license after moving nodes
PostPosted: Mon Apr 24, 2023 4:30 am 

Joined: Wed Feb 15, 2023 6:45 am
Posts: 8
I have updated both w19 and Saleable Serial Num, ran prom checksum (returned PASS) and perfomed whack - reset.
During startup i enter whack again and see updated values in place but when running "prom checksum" again I get
Code:
Whack>prom checksum
    PROM checksum:                        PASS
Invalid Tornado CPU core count - 0 for node type - 0x40

*** Non-fatal error: Code 25, sub-code 0x5 (0).


Checkin cpuid I see 1428L


Code:
Whack>cpu id
    Found CPU ID string 'GenuineIntel'
      Intel(R) Xeon(R) CPU E5-1428L v2 @ 2.20GHz
      Family 6, Model 62, Stepping 4, Features bfebfbff:3
      Data TLB: 1GB Pages, 4 entries
      Data TLB: 4K Pages, 64 entries
      Inst TLB: 2M or 4M Pages, 8 entries
      Inst TLB: 4K Pages, 64 entries
      64-Byte Prefetching
      Shared TLB: 4K Pages, 512 entries
    CPUID[ 0] == 0000000d 756e6547 6c65746e 49656e69
    CPUID[ 1] == 000306e4 00200800 77bee3ff bfebfbff
    CPUID[ 2] == 76036301 00f0b2ff 00000000 00ca0000
    CPUID[ 3] == 00000000 00000000 00000000 00000000
    CPUID[ 4] == 00000000 00000000 00000000 00000000
    CPUID[ 5] == 00000040 00000040 00000003 00001120
    CPUID[ 6] == 00000077 00000002 00000009 00000000
    CPUID[ 7] == 00000000 00000000 00000000 00000000
    CPUID[ 8] == 00000000 00000000 00000000 00000000
    CPUID[ 9] == 00000000 00000000 00000000 00000000
    CPUID[10] == 07300403 00000000 00000000 00000603
    CPUID[11] == 00000000 00000000 00000094 00000000
    CPUID[12] == 00000000 00000000 00000000 00000000
    CPUID[13] == 00000000 00000000 00000000 00000000
      SKU Info: Max Frequency Ratio 22, Max Core Count 6
      CPU speed: 2200.00 MHz
      Bus speed:  100.00 MHz
      Bus to CPU ratio: 1/22
    MCG_CAP     00000000:01000c17
    Setting CR4 to 00000170



Is it safe to proceed further with InServ boot?


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 


Who is online

Users browsing this forum: Google [Bot] and 42 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group | DVGFX2 by: Matt