Where did vpmon boot from?

[Robert Cook_6]

Is there a way to determin what disk vpmon booted from while I'm up in vpar's mode? The command parstatus returns boot disk info for the vpar not the npar.

Thanks,

Bob

[Don Morris_1 · Accepted solution]

vparstatus -m

[whiteknight]

vparstatus -m
Console path: 0.0.4.0.643.0.0.0.0.0
Monitor Boot disk path: 0.0.2.1.6.0.0.0.0.0
Monitor Boot filename: /stand/vpmon
Database filename: /stand/vpdb

ioscan -fnc disk
disk 2 0/0/2/1.6.0 sdisk CLAIMED DEVICE SEAGATE ST318436LC
/dev/dsk/c2t6d0 /dev/rdsk/c2t6d0

#lifcp /dev/rdsk/c2t6d0:AUTO -
hpux /stand/vpmon -a

WK

[Robert Cook_6]

Thanks. The problem is that the disk vparstatus -m identifies is not owned by any vpar. Can I truely trust that this is the disk vpmon was loaded from? That would not be good for sync of vpdb. I have 2 itanium superdomes each with a 4 cell npar with vpars. Both return the same disk 0.0.1.1.0.4.0.0.0 as the monitor boot path.

Thanks,

Bob

[Torsten.]

I have never seen this kind of config, but it should not be a problem.

The active vpmon is working like an own small OS maintaining the vpdb (master) file.

The running vPars will synchronize their own copies of vpdb with the vpmon's master DB on every action and within a period of time.

How this works is written in the manual section "vPars Partition Database", see

http://docs.hp.com/en/T1335-90073/T1335-90073.pdf

page 32 - vPars Monitor and Database