How do I move permanent licenses between NPAR's?

[Stephen Stephanian]

Haven't seen this answered here....

I've got a HP 9000 Superdome w/ 2 NPARS, one with 7 cells/56 cpus 48 of which are permanently licensed, and another w/ 3 cells/24 cpus and 16 permanent licenses.

Both NPARs are using VPARS (6 in npar 0, 2 in npar1) GWLM, and ICAP.

What I want to do is deactivate permanent licenses in NPAR 0 and turn them on in NPAR1; should be easy yet can't find the doc on how to do it.

FWIW, I do know I need to stop GWLM before I monkey w/ cpu counts. Any help?

[Steven E. Protter]

Shalom,

Assuming the OS version is the same, just migrate the .codewords file.

You are responsible on the honor system to not exceed your cpu total overall by using the same license on two systems simultaneously.

SEP

[Stephen Stephanian]

Thanks, Steve.....I'm sorry to say I'm not sure what that means, or where it is. And do I migrate or modify? We intend to stay in compliance; thought there might be a command to deactivate/activate across NPARs; and that I might have to do it for HPUX, VPAR, GWLM licenses, which are all cpu count based.

[Duncan Edmonstone · Accepted solution]

Steve,

Don't worry about SEP's comment, I think he's misunderstood what you are after and is talking about software licenses.

So yes you are on the right track with what you said...

Lets say you want to move 4 cores from nPar0 to nPar1 - Forgetting about vPars for the moment you would do the following:

1. Un-deploy the SRD in gWLM for this Superdome.

2. If the SRD is for the whole Superdome complex you may also need to look at altering the policies assigned to workloads within the SRD, otherwise gWLM may just "undo" what you changed manually to get back to policy compliance.

3. On nPar0 issue the command:

icapmodify -d 4 "move 4 cores to nPar1:Steve S"

4. On nPar 1 issue the command:

icapmodify -a 4 "move 4 cores from nPar0:Steve S"

5. Use the icapstatus command to make sure things have changed as you expected.

5. Re-deploy the SRD from within gWLM

vPars complicate things a bit, in that you may need to break up the icapmodify and run it in several different vPars (say deactivate 1 core in vPar0, 2 from vPar1, and 1 from vPar2 etc.) Also when you come to activate the cores in vPars in nPar1, you will hbave to check that it isn't going to exceed the max CPU allowed for that vPar (check with vparstatus) - if it does you will need to adjust with vparmodify - I don't remmember whether changing the max cpus value needs the vPar down to take effect...

HTH

Duncan

[Duncan Edmonstone]

Reading through your posts again I wonder if you _are_ concerened about software licenses as well?

First point I'd make is are you running the same HPUX software and operating environment in all partitions? If so, then everything you do is legal and above board - of course if you are turning off 4 cores in a partition running the Base or Foundation operating environment and then turning on 4 cores in a partition running the Data Centre or Mission Critical operating environment, then you have a commercial issue you need to address.

However you need to differentiate between commercial license terms and the technical implementation of those terms. Although what I described above is not allowed from a commercial license terms perspective, technically there's nothing to stop you doing it. Of course if HP then ask to conduct a SW license audit...

Does any of that make sense?

Duncan

[Stephen Stephanian]

Thanks, Duncan - that's just what I was looking for. And to your point on versioning, we're the same across the npars/vpars so no issues.