path of vpmon not clear.

[samay_hcl]

Hello,
i am confused about virtual monitor path.

i am working a pertition which have two vpars
i can find that
Monitor boot disk path: 6.0.1.1.0.0.0.0.0.0.0
but lvlnboot output shows:
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t0d0 (4/0/1/1/0.0.0) -- Boot Disk
/dev/dsk/c4t0d0 (6/0/0/1/0.0.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c2t0d0
/dev/dsk/c4t0d0
Root: lvol3 on: /dev/dsk/c2t0d0
/dev/dsk/c4t0d0
Swap: lvol2 on: /dev/dsk/c2t0d0
/dev/dsk/c4t0d0
Dump: lvol2 on: /dev/dsk/c2t0d0, 0

My doubt is :
1.Which disk is being used by MON
2.How can i see this path?
As right now ioscan shows

disk 5 6/0/1/1/0.0.0 sdisk NO_HW DEVICE
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0

could you please more clear on this?

[Torsten.]

As you can see

Monitor boot disk path: 6.0.1.1.0.0.0.0.0.0.0

Once started, the monitor resides in memory.

But while the system was up, the SCSI controller went away:

ext_bus 2 6/0/1/1/0 mpt NO_HW INTERFACE SCSI Ultra320 A6961-60011
/dev/mpt2



There is something wrong with your hardware (failed).

[samay_hcl]

Hi Experts,



I think i am not able to make you guys clearer about the question. So, posting it again.



I am one Npar having two vpars, everything is working fine. Here are some outputs.



root@thopold:/root_home> vparstatus -m

Console path: 4.8.1

Monitor boot disk path: 6.0.1.1.0.0.0.0.0.0.0

Monitor boot filename: /stand/vpmon

Database filename: /stand/vpdb



root@thopold:/tmp/test99> lvlnboot -v

Boot Definitions for Volume Group /dev/vg00:

Physical Volumes belonging in Root Volume Group:

/dev/dsk/c2t0d0 (4/0/1/1/0.0.0) -- Boot Disk

/dev/dsk/c4t0d0 (6/0/0/1/0.0.0) -- Boot Disk

Boot: lvol1 on: /dev/dsk/c2t0d0

/dev/dsk/c4t0d0

Root: lvol3 on: /dev/dsk/c2t0d0

/dev/dsk/c4t0d0

Swap: lvol2 on: /dev/dsk/c2t0d0

/dev/dsk/c4t0d0

Dump: lvol2 on: /dev/dsk/c2t0d0, 0







Now, my confusion is



1) my vparstatus command is showing monitor disk path as 6.0.1.1.0.0.0.0.0.0.0, whereas lvlnboot and setboot command showing my primary boot path as 4/0/1/1/0.0.0. Now, the thing is if my server booted from 4/0/1/1/0.0.0, then it should have taken monitor path from the same disk. Why it is showing them monitor path from 6.0.1.1.0.0.0.0.0.0.0.



2) i attached its ioscan, where i sacnned on H/w path 6/0/1/1/0, but it shows me No_HW for all devices and also i am not able to find 6.0.1.1.0.0.0.0.0.0.0 h/w path in that ioscan. i tried ioscan on this h/w path, but it did not show anything. please explain this weird thing for me.



Thanks

[Torsten. · Accepted solution]

You can even boot the vpmon from a completely different disk, it is not always the same disk as one of the vPars boot disk.

Think about what the system does - boot the vpmon, then boot the vPars according to the configuration.



But the NO_HW entries are a problem. Check this!

[Jupinder Bedi]

When you assign a disk as a monitor boot disk path it will not show you in the OS . The active vpmon is working like a small OS maintaining the vpdb file and once you will assign the disk in vpdb it will not show you in the OS but it will remain in your OS and works fine.

[Torsten.]

Please post an

# ioscan -fn

and

# olrad -q

now.

[samay_hcl]

Hello Torstone,

I have attached the ioscan and olard -q output.

Thanks!

[samay_hcl]

Hi Torstene,

ioscan -fn otput also sent.

Thanks!

[Torsten.]

Everything is back now

ext_bus 4 6/0/0/1/0 mpt CLAIMED INTERFACE SCSI Ultra320 A6961-60011
/dev/mpt4
target 7 6/0/0/1/0.0 tgt CLAIMED DEVICE
disk 10 6/0/0/1/0.0.0 sdisk CLAIMED DEVICE HP 146 GST3146855LC
/dev/dsk/c4t0d0 /dev/rdsk/c4t0d0
target 8 6/0/0/1/0.2 tgt CLAIMED DEVICE
disk 11 6/0/0/1/0.2.0 sdisk CLAIMED DEVICE HP 146 GST3146855LC
/dev/dsk/c4t2d0 /dev/rdsk/c4t2d0
target 10 6/0/0/1/0.4 tgt CLAIMED DEVICE
disk 12 6/0/0/1/0.4.0 sdisk CLAIMED DEVICE HP 146 GST3146855LC
/dev/dsk/c4t4d0 /dev/rdsk/c4t4d0
target 11 6/0/0/1/0.6 tgt CLAIMED DEVICE
disk 13 6/0/0/1/0.6.0 sdisk CLAIMED DEVICE HP 146 GST3146855LC
/dev/dsk/c4t6d0 /dev/rdsk/c4t6d0




Any related messages in syslog and root's mailbox?

[Torsten.]

Mixed up this 6/0/0 and 6/0/1.

Please post a

# vparstatus -v