vPar confusion

[David Harwood]

Hi,
I'm reasonably new at nPar and vPar admin so apologies if the following sounds dumb...

I have created an nPar on a Superdome and assigned 5 Cell Boards, each cell board giving 8 processors and 32Gb. I then created 7 vPars assigning the required CPU and memory.
When I rebooted the nPar into vPar mode, I found that parstatus shows three of my cells (the ones without i/o attached) had changed from "float" to "base" and the output of vparstatus showed I'd lost some memory assignments.
Can somebody suggest where I've gone wrong? Selected outputs are below...

In nPar mode:
[Cell]
CPU Memory Use
OK/ (GB) Core On
Hardware Actual Deconf/ OK/ Cell Next Par
Location Usage Max Deconf Connected To Capable Boot Num
========== ============ ======= ========= =================== ======= ==== ===
cab0,cell0 Active Core 8/0/8 32.0/0.0 cab0,bay0,chassis1 yes yes 0
cab0,cell1 Active Float 8/0/8 32.0/0.0 - no yes 0
cab0,cell2 Active Base 8/0/8 32.0/0.0 cab0,bay1,chassis3 yes yes 0
cab0,cell3 Active Float 8/0/8 32.0/0.0 - no yes 0
cab0,cell4 Active Float 8/0/8 32.0/0.0 - no yes 0


Virtual Partition Name Min/Max CPUs IO ILM CLM
============================== ======= ==== ==== ========== ==========
cebor01 8/ 8 8 4 1024 1024
cebor02 8/ 8 8 4 1024 1024
cebor03 4/ 4 4 3 1024 1024
cebor04 4/ 4 4 3 1024 1024
cebap01 6/ 6 6 3 1024 1024
cebap02 6/ 6 6 3 1024 1024
cebap03 4/ 4 4 3 1024 1024

Memory (MB)
ILM CLM
# User # User
Virtual Partition Name Ranges/MB Total MB Ranges/MB Total MB
============================== ====================== ======================
cebor01 0/ 0 24576 0/ 0 0
cebor02 0/ 0 24576 0/ 0 0
cebor03 0/ 0 8192 0/ 0 0
cebor04 0/ 0 8192 0/ 0 0
cebap01 0/ 0 9216 0/ 0 0
cebap02 0/ 0 9216 0/ 0 0
cebap03 0/ 0 16384 0/ 0 0


After reboot into vPar mode:

[Cell]
CPU Memory Use
OK/ (GB) Core On
Hardware Actual Deconf/ OK/ Cell Next Par
Location Usage Max Deconf Connected To Capable Boot Num
========== ============ ======= ========= =================== ======= ==== ===
cab0,cell0 Active Core 8/0/8 32.0/0.0 cab0,bay0,chassis1 yes yes 0
cab0,cell1 Active Base* 8/0/8 32.0/0.0 - no yes 0
cab0,cell2 Active Base 8/0/8 32.0/0.0 cab0,bay1,chassis3 yes yes 0
cab0,cell3 Active Base* 8/0/8 32.0/0.0 - no yes 0
cab0,cell4 Active Base* 8/0/8 32.0/0.0 - no yes 0


[Virtual Partition Resource Summary]
CPU Num Num Memory Granularity
Virtual Partition Name Min/Max CPUs IO ILM CLM
============================== ======= ==== ==== ========== ==========
cebor01 8/ 8 8 4 1024 1024
cebor02 8/ 8 8 4 1024 1024
cebor03 4/ 4 4 3 1024 1024
cebor04 4/ 4 4 3 1024 1024
cebap01 6/ 6 6 3 1024 1024
cebap02 6/ 6 6 3 1024 1024
cebap03 4/ 4 4 3 1024 1024

Memory (MB)
ILM CLM
# User # User
Virtual Partition Name Ranges/MB Total MB Ranges/MB Total MB
============================== ====================== ======================
cebor01 0/ 0 24576 0/ 0 0
cebor02 0/ 0 24576 0/ 0 0
cebor03 0/ 0 8192 0/ 0 0
cebor04 0/ 0 7551 0/ 0 0
cebap01 0/ 0 0 0/ 0 0
cebap02 0/ 0 0 0/ 0 0
cebap03 0/ 0 0 0/ 0 0

[Don Morris_1 · Accepted solution]

vPars doesn't support Dynamic nPartitions underneath it. Hence you can't OLD the Cells while in vPar mode - hence they are reported as Base, I expect. (is that * beside "Base" a footnote in the output somewhere, perhaps?)

Note that the nPar can consider cells all Base and the vPar environment can consider some or all of the resources as Float for the vPars themselves.

[David Harwood]

Thanks for the reply, the penny travelled some way before it finally dropped but that makes perfect sense now.

[David Harwood]

I am, indeed, an idiot.