topic Re: Problem in installing VPAR in Operating System - HP-UX

Problem in installing VPAR

Ali Imran Abbas — Mon, 17 Dec 2007 20:21:45 GMT

Dear Fellows,

I am having some problem in installing virtual partition. Let me describe my scenario here:

I am building a superdom server, I have installed hp-un first and then I created vp1 on that installation.
Next from the root prompt of the first vp, I created second vp vp2 and then started to boot from ignite. It is supposed to go to installation window but it showed the message vp1 booting and then came back to root prompt again.
I tried to telnet to GSP of the vp2 but its showing the following message:

[MON] vp2 loaded

and then it just stuck there.

I am trying to get the status of vp2 by doing vparstatus, its showing the following message:

Virtual Partition Name State Attributes Kernel Path Opts
============================== ===== ========== ========================= =====
vp1 Up Dyn,Auto /stand/vmunix
vp2 Boot Dyn,Auto /stand/vmunix

[Virtual Partition Resource Summary]
CPU Num Memory (MB)
CPU Bound/ IO # Ranges/
Virtual Partition Name Min/Max Unbound devs Total MB Total MB
============================== ================ ==== ====================
vp1 2/ 6 2 2 9 0/ 0 8192
vp2 2/ 6 2 2 7 0/ 0 8192

Can some body please direct me wat to do now? I wanna install hp-un and configure the second vp2.

An early reply would be highly appreciated.

Regards,

Ali

Re: Problem in installing VPAR

melvyn burnard — Mon, 17 Dec 2007 20:52:51 GMT

firstly, there IS no gsp for the 2nd vpar!
You use the gsp for the complex, and get to the relevant Npar console.
Once there, you toggle between the various Vpar consoles by using ctl-A.

When you created the vpars, what I/O did you add in to each vpar? Did you include the core I/O card into the first Vpar configuration?

Re: Problem in installing VPAR

Ali Imran Abbas — Mon, 17 Dec 2007 21:06:09 GMT

yea, i m doing telnet to the gsp of the complex and then selecting the particular npar. but when i m going to the console of the npar, its showing me the following message and its not toggling between screens.

[MON] vp2 loaded

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

I used the following commands to create vpars:

VP1:
vparcreate -p vp1 -a cpu::4 -a cpu:::2:6 -a mem::8192 -a io:0/0/11/0 -a io:0/0/
12/0 -a io:1/0/11/0 -a io:0/0/9/0/0.8.0:BOOT -a io:0/0/9/0/0.9.0:ALTBOOT

VP2:

vparcreate -p vp2 -a cpu::4 -a cpu:::2:6 -a mem::8192 -a io:1/0/14/0 -a io:1/0/
4/0 -a io:0/0/1/0/0.3.0:BOOT -a io:0/0/1/0/0.8.0:ALTBOOT

Re: Problem in installing VPAR

melvyn burnard — Mon, 17 Dec 2007 21:09:41 GMT

what is the path of the core I/O card in this Npar? it needs to be in vpar1, and I do not see it (unless I am mistaken)

Re: Problem in installing VPAR

Ali Imran Abbas — Mon, 17 Dec 2007 21:13:15 GMT

What do u mean by core I/O path?

Re: Problem in installing VPAR

melvyn burnard — Mon, 17 Dec 2007 21:16:08 GMT

the card that the Npar has as it's core I/O card, in slot 0 of the I/O bay , has the primary lan card for the Npar

Re: Problem in installing VPAR

Ali Imran Abbas — Mon, 17 Dec 2007 21:23:43 GMT

I am attaching the output of vparstatus -A:

usunx50:# vparstatus -A
[Unbound CPUs (path)]: 1.12
1.13
2.10
2.11
2.12
2.13
3.10
3.11
3.12
3.13
4.10
4.11
4.12
4.13
[Available CPUs]: 12

[Available I/O devices (path)]: 0.0.0
0.0.2
0.0.3
0.0.4
0.0.6
0.0.8
0.0.10
0.0.14
1.0.0
1.0.1
1.0.2
1.0.3
1.0.6
1.0.8
1.0.9
1.0.10
1.0.12

[Unbound memory (Base /Range)]: 0x0/64
(bytes) (MB) 0xc000000/15808
[Available memory (MB)]: 15872
Can u pls figure it out from this, I am sorry I am doing this for the first time

Re: Problem in installing VPAR

melvyn burnard — Mon, 17 Dec 2007 21:31:17 GMT

well it would help of you were to read the manuals at:
http://docs.hp.com/en/vse#Virtual%20Partitions

For example, take a look at page 56 of
http://docs.hp.com/en/T1335-90073/T1335-90073.pdf

0 cell
0/0 ioa System Bus Adapter (805)
0/0/0 ba Local PCI Bus Adapter (782)
0/0/0/0/0 tty PCI SimpleComm (103c1290)
0/0/0/0/1 tty PCI Serial (103c1048)

The vparstatus you have listed does not show what card is what, so I will hazard a guess and say it may be the card at 0/0/0 .
What would have been better is an ioscan output from the Npar (NOT the vpar).