Changing or displaying npar boot paths from a vpar

[SCC (Kavanagh) Support]

Hi,

On an rx8640 with one npar I have two vpars each running HPUX 11.23.

I would like to check and alter the npar HAA and ALT boot paths.

In the past I have booted the npar back to npar mode and changed the boot paths however is it possible to do this while still in the npar, vpar mode and from a vpar?

On the 1st vpar if I run the parstatus -V -p 0 command I get:
parstatus -V -p0
[Partition]
Partition Number : 0
Partition Name : npar0
Status : Active
IP Address :
Primary Boot Path : 0/0/0/2/0.6.0
Alternate Boot Path : 0/0/0/3/0.6.0
HA Alternate Boot Path :

On the second vpar I get:
parstatus -V -p 0
[Partition]
Partition Number : 0
Partition Name : npar0
Status : Active
IP Address :
Primary Boot Path : 1/0/0/2/0.6.0
Alternate Boot Path : 1/0/0/3/0.6.0
HA Alternate Boot Path :

The above seem to be the vpar boot paths not the npar boot paths.

Regards

David

[Torsten.]

According to the docs you use parmodify to set the boot path of the nPar, so I would assume you get them with parstatus. What version is running?

Does vparstatus show the same? Likely.

However, try

# vparstatus -m

[SCC (Kavanagh) Support]

Hi Torsten,

The vpar version is 4.06.

vparstatus -m gives

root@rx8640n1:/usr/sbin> vparstatus -m
Console path: No path as console is virtual
Monitor boot disk path: 1.0.0.2.0.6.0
Monitor boot filename: /stand/vpmon
Database filename: /stand/vpdb
Memory ranges used: 0x0/349814784 monitor
0x14d9c000/925696 firmware
0x14e7e000/1425408 monitor
0x14fda000/50487296 firmware
0x18000000/134213632 monitor
0x3fffe000/8192 firmware
0x703fc000000/67108864 firmware
0x783fc000000/67108864 firmware

and from the 2nd vpar for completeness
root@rx8640n0:/> vparstatus -m
Console path: No path as console is virtual
Monitor boot disk path: 1.0.0.2.0.6.0
Monitor boot filename: /stand/vpmon
Database filename: /stand/vpdb
Memory ranges used: 0x0/349814784 monitor
0x14d9c000/925696 firmware
0x14e7e000/1425408 monitor
0x14fda000/50487296 firmware
0x18000000/134213632 monitor
0x3fffe000/8192 firmware
0x703fc000000/67108864 firmware
0x783fc000000/67108864 firmware


Followed by vparstatus -v


root@rx8640n1:/usr/sbin> vparstatus -v
[Virtual Partition Details]
Name: barlows_vpar1
State: Up
OS Version: B.11.23
Attributes: Dynamic,Autoboot,Autosearch
Kernel Path: /stand/vmunix
Boot Opts: -lq

[CPU Details]
Min/Max: 2/8
User assigned [Path]:
Boot processor [Path]: 0.120
Monitor assigned [Path]: 0.121

Non-cell-specific:
User assigned [Count]: 0
Monitor assigned [Count]: 2
Cell-specific [Count]: Cell ID/Count


[IO Details]
0.0.0
0.0.6
0.0.2
0.0.1
0.0.0.2.0.6.0 BOOT
0.0.0.3.0.6.0.0.0.0.0,ALTBOOT

[Memory Details]
ILM, user-assigned [Base /Range]:
(bytes) (MB)
ILM, monitor-assigned [Base /Range]: 0x380000000/10240
(bytes) (MB)
ILM Total (MB): 10240

ILM Granularity (MB): 1024

CLM, user-assigned [CellID Base /Range]:
(bytes) (MB)
CLM, monitor-assigned [CellID Base /Range]:
(bytes) (MB)
CLM (CellID MB):

CLM Granularity (MB): 128

[Virtual Partition Details]
Name: barlows_vpar2
State: Up
OS Version: B.11.23
Attributes: Dynamic,Autoboot,Autosearch
Kernel Path: /stand/vmunix
Boot Opts: -lq

[CPU Details]
Min/Max: 2/8
User assigned [Path]:
Boot processor [Path]: 0.122
Monitor assigned [Path]: 0.123

Non-cell-specific:
User assigned [Count]: 0
Monitor assigned [Count]: 2
Cell-specific [Count]: Cell ID/Count


[IO Details]
1.0.0
1.0.6
1.0.4
1.0.2
1.0.1
1.0.0.3.0.6.0 ALTBOOT
1.0.0.2.0.6.0,BOOT

[Memory Details]
ILM, user-assigned [Base /Range]:
(bytes) (MB)
ILM, monitor-assigned [Base /Range]: 0x100000000/10240
(bytes) (MB)
ILM Total (MB): 10240

ILM Granularity (MB): 1024

CLM, user-assigned [CellID Base /Range]:
(bytes) (MB)
CLM, monitor-assigned [CellID Base /Range]:
(bytes) (MB)
CLM (CellID MB):

CLM Granularity (MB): 128

[Torsten.]

Not sure if it helps, but check for patch PHCO_34963.

[SCC (Kavanagh) Support]

Hi Torsten,

PHCO_34963 is installed.

Been looking further and just found this statement in the vpars admin guide

"To modify stable storage, you must either:

- go into standalone/nPars mode and use setboot or parmodify

- within the vPars environment on PA-RISC nPartitionable servers, use parmodify
(parmodify is not supported from within the vPars environment on Integrity servers

- go to the BCH for PA-RISC or EFI Shell for Integrity systems"

So it looks like I will have to set the npar back to npar mode and set the boot paths to vpmon at that level as I did in the past.

[Torsten.]

>> parmodify is not supported from within the vPars environment on Integrity servers

I missed this. But normally there is no need (I never had any) to change this.

I normally set the vpmon path to the first disk of the first vpar, the next path to the next vPar and the third to any of the remaining (most of the times the mirror of the first vpar).

[SCC (Kavanagh) Support]

I do the same re paths.

Just a bind having to close the vpars down and go to npar mode to set the paths.

Thanks for you assistance.

David