nPar and vPar

[MárcioAFM]

Hello,

It is possible to create nPar's and vPar's in smh interface?

Thanks,

Márcio

[Torsten.]

Yes and no.

The partition manager (nparmgr) is integrated in smh, the vpar manager is standalone and only available in 11.11.

Anyway, IMHO it is better to configure vpars from the commandline. the vpar manager only works in a already running vpar env.

[MárcioAFM]

Thank you.

Is the first time i'm gone do nPar and Vpar, so i don't know where to start the work.

Best Regards

Márcio

[Torsten.]

Is this a question or statement?

;-)

[MárcioAFM]

:)

Well is kind of question :)

Márcio

[Torsten.]

Any specific question?

In general, these documents will help you:


nPartition Administrator's Guide
http://docs.hp.com/en/5991-1247B/index.html

HP-UX Virtual Partitions Administrator's Guide (includes A.03.05 and A.04.05)
http://docs.hp.com/en/T1335-90083/index.html

[MárcioAFM]

Hello again,

The configuration i need to do is:

One server rp8640 with two vPar working in one npar with tow cell's

vPar1 - 7 CPU's, 24G of ram,
vPar2 - 3 CPU's, 8G Ram

Another server rp8640 with 3 vPar's wornking in one nPar with two cell's

vPar1 - 5 CPU, 18G Ram
vpar2 - 3 CPU, 8G Ram
vpar3 - 2 CPU, 6G Ram



Then i need to add i think two disks for each vPar (one for SO and another for mirror) and one Lan Card


Someone can give me some ideas?

Thanks

Márcio

[pa8700]

go to any of thr Vpar
#vparstatus -A

it will give the free resources available inthe npar which can be assigned to any of the vpar by vparmodify command.

For IO addition you need your target vpar in shutdown state.

is it ok

[MárcioAFM]

Hello,

It's possible to first do the vPar's and then install the OS point to the disk i have configured the vPar? Or i have first to install OS's in two disks and only after configure the vPar with the disk's that i have install de OS (HP-UX)?

Regards,


Márcio

[Pupil_1 · Accepted solution]

do you have an existing vpar or you want to create a set to vpars on this 8640?

If new vpars, then
install OS in nPar mode.
from OS, do your vparcreate with cpu, mem and IO.
vparstatus (to verify ur vpar create)
mkboot -a "boot /stand/vpmon -a" /dev/rdsk/cxtxdx
vparenv -m vpars
reboot
vpar should boot now and from this vpar, create ur other vpars.

The io paths in the vparcreate can be got the o/p of ioscan -fnC ba in npar mode.

Hope that helps.

[Pupil_1]

the OS in npar mode will become the 1st vpar and does not need an install again.

For the new vpars ur create, you will have to install the OS from CD/DVD if u have IO assigned or from Ignite.

Cheers.

[MárcioAFM]

Hello,

Well, i don't have vPar's. only a nPar that will have two vPars. My plan is:

1. I have a first HPUX installed and i will create a vPar with it.

2. I will create the othe vPar with two disks and io devices (Tape, DVD, LAN and HBA's).

3. Then vparenv -m vpars
4. Reboot
5. Now i should be in vPars mode

After this i realy don't no how two install the OS in the other vPar already created.

Regards

Márcio

[Pupil_1]

from the vparboot man page on 11.23.


-I ignite_kernel (PA-RISC platforms only) Specifies a path to a
cold-install kernel such as
/opt/ignite/boot/WINSTALL. This form of the
command is used to cold-install an instance of
HP-UX on a virtual partition. Most often, this is
done on a newly-created virtual partition, one
that has a completely unwritten disk. However, it
can be used to cold-install HP-UX over an existing
instance.

ignite_kernel can reside either on the local
virtual partition (the one on which vparboot is
run) or on any other networked system or virtual
partition accessible from that partition. The
syntax for ignite_kernel is:

[Server name or IP addr,]cold-install_kernel

If cold-install_kernel begins with a slash, "/",
you are specifying an absolute path and vparboot
looks for it at that location. With Ignite-UX
revisions prior to C.6.0, if cold-install_kernel
does not begin with "/", the default path
/opt/ignite/boot/ is prepended to cold-
install_kernel.

With Ignite-UX revision C.6.0 or later, there is
no cold-install_kernel at the default path
/opt/ignite/boot. Hence it is required to specify
an absolute path, such as
/opt/ignite/boot/Rel_B.11.11/WINSTALL.

Hewlett-Packard Company - 3 - HP-UX 11i Version 2: Sep 2004

vparboot(1M) vparboot(1M)

If the Server name or IP address, is not
specified, vparboot loads the cold-install kernel
from the file space of the local virtual
partition. Otherwise the command loads it from
the file space of the specified server. The comma
is a required part of the server name syntax.


I don't have a rp node to confirm the syntax.

Do you have an Ignite server? if not, then you might have to move the IO for DVD around in between the vpars.

Cheers.

[MárcioAFM]

Hello,

Nothing better then read the User Guide.


Thanks for the help.

Regards,

Márcio

[Torsten.]

"Nothing better then read the User Guide."

This is what I suggested in the beginning.

;-)

Have fun!

[MárcioAFM]

Hello,


Yes indeed, thanks again!

Márcio