nPartitions in SuperDome

[Alex Lavrov]

Hello all,
I have SuperDome with two nPartitions. I will be glad to know what can be done to one nPartition from other (with root, something like parmgr), is it dangerous and how can I overcome it. I want to create two separated servers that can not "hurt" one other.

Thank you.

[Ravi_8]

Hi,

npar's are independent of each other, Logically you can't hurt one n par from another. whereas you can dynamically allocate the CPU/RAM from one npar to another(parmodify).
shutiing down one npar wouldn't affect another npar.

http://www.docs.hp.com/hpux/onlinedocs/B2355-90762/B2355-90762.html

[CCIL]

n-Pars are logical partition but they , each n-Par can be treated as individual system. You can allocate resources to such as CPUs , memory , I/O slots . Each n-Par has its own cell board so it is very easy to mange the n-Pars than v-Pars . as ecah n-Pars is having there own cell boards.

[Alex Lavrov]

Thank you for your help,
as I can see, parmgr and parmodify,
can affect other nPars in SuperDome, so if I'll lock these commands (with SEOS for example), will my nPras be isolated?

I anyone has more ideas ...

[Dietmar Konermann]

Hi, Alex!

It's not an easy task to make a system secure against attacks from root (not to say impossible).

Locking the partition commands would be _some_ improvement, but of course not 100%, as longs as a kernel interface is still present that can be used by root. The next step would be removing the hd_fabric driver from the kernel... then at least a kernel build/reboot would be required (which could be done by root of course). :-)

Best regards...
Dietmar.