Move a CPU between nPars

[Jayaprakash Subramanian]

Hello All,

I have an rx8620 complex with 2nPars and each nPar has 3 vPars each. The complex has 16 CPU cores in total.
Here the configuration of the CPU's -
==============================
nPar0 CPU's | nPar1 CPU's
==============================
vPar1 - 2 | vPar4 - 2
vPar2 - 2 | vPar5 - 2
vPar3 - 2 | vPar6 - 2
Inactive Core - 2 | Inactive Core - 2
===============================

The inactive cores are activated on-demand by using the TiCAP license.

The requirement here is i have to increase 1 CPUs for all the vPars in nPar0 and there are only 2 inactive cores available on nPar0.

Is it possible to move a CPU from nPar1 (2 inactive cores available) to nPar0 without using GiCAP?

Please advise.

Thanks,
Jayaprakash S

[SoorajCleris]

Hi Jayaprakash,

I am sorry to say it is not possible. Moving the CPUs across Npar.

Npar behave like electrically isolated system from other Npars.

Only thing you can do is reconfiguration of Npar.

Regarsd,
Sooraj U

[SoorajCleris]

Small clarification.

Howmany cell boards do you have?
Howmany CPU sockets are poulated?
Howmany cellboards allocated for each Npar?

Regards,
Sooraj

[Duncan Edmonstone · Accepted solution]

You have to think about what is physically possible here...

If you have 16 cores in total, presumably you have 2 cell boards, one for each nPar.

The granularity level of an nPar is at the cell board level, so that means each nPar here has at most 8 cores.

To make all the vPars in nPar0 have 3 cores would require 4 x 3 = 12 cores. You don't have that in the nPar.

You could of course look at combining the 2 seperate nPars into 1 big nPar with 6 vPars - although that would require you to blow away and re-cerate all the vPar definitions for one of the current nPars, but that would at least give you the flexibility to do what you are asking for. However I'd imagine there's some good reason why these vPars are in seperate nPars, and judging byt your question here, you may not have the experience/confidence to do such a major change

>> without using GiCAP

why do you think GiCAP would help you here? GiCAP is used between complexes, not within complexes.

HTH

Duncan

[Jayaprakash Subramanian]

Hi Duncan,

Thanks for the info and we'll consider repartitioning of the vPar.

--JP

[Jayaprakash Subramanian]

Hi Sooraj,

Thanks for your valuable response.

We have 4 Cell Boards totally and each nPars has 2 Cellboards assigned.

--JP

[SoorajCleris]

Hi again :)

So from the details, I can understand that you have populated all the cellboards ( 4).

How many CPUs are there in each cell board?

I believe it should be 2 each . you have two options here.

1. Combine both Npar to a single one and assingn the CPUs accordingly.

2. Install more new CPUs as you have free sockets. (consult HP)

I would prefer 1st option for urgent resourse and 2nd for long term ..

:)


* iCAP is only usefull when you have enough physical CPUs..

Regards,
Sooraj

[Vivek_Pendse]

Hi,

The core licenses are stored in the Complex profile. If, you have 6 license cpus activated in npar1 & npar2, then you can deactivate one cpus in one of the npar & activate the in-active cpus in other npar. This will work; because when you will de-activate one cpu the profile updates as one free cpu license. And same can be used in other npar to activate the inactive cpu.

Regards,
Vivek

[SoorajCleris]

Hi Vivek ,

There are only two Inactive cores in Npar0 . and he wants 3 CPU cores atleast .

How will activate the core if there is no Physcal CPU available ??

:)

Regards,
SOoraj

[Vivek_Pendse]

Oops, i din't check that.

There is one more option to merge these 2 npars in single npar & then can be used.
as this is rx86xx, so h/w is much stable in it's profile.

[Jayaprakash Subramanian]

Hi Sooraj and Vivek,

Thanks for your valuable suggestions. Each cell board has 4 CPU's and I consider the repartitioning of the server by moving the low usage vPars to an nPar and the rest of the vPars to the another nPar.

This will utilize the idle CPU cores from the nPar1 in this case.

So the partitioning would be done as 2 vPars in nPar0 and 4 vPars in nPar1 and assign the iCAP CPU's for the machines.

Thanks,
Jayaprakash S.

[Torsten.]

Consider this: If you move some vPars from one nPar to another, the I/O will stay in the original nPAr. Maybe creating one large nPar would be the better solution.

[Vivek_Pendse]

yes, right, to swap the vpar go for ignite backup/restore. but again you need to take care of storage luns; means to update the wwn on storage side & zoning if u r using soft, also vgmaps, etc..

Regards,
Vivek