Hello All
While we are on this topic I would like to share my experience regarding
exporting VxDMP devices to guest domains. Below are the details of the
setup and the issue I faced. Appreciate if you all can throw some light of
the probable problem of the setup. So far SUN have not come up with any
solution to the problem.
The workaround to the problem ofcourse is -- (a) not to used VxDMP in the
control/service domain (b) export the native disks on both the fiber paths
individually to the guest domain (c) use VxDMP on the guest host. However
the below setup should be supported as stated by Veritas and in LDOM 1.0.3
Setup details:
Sun T5240 hardware, Solaris 10, kernel patch level 137111-04, LDOM 1.0.3
Storage used for Guest LDOM's: SAN. The control and service domain is
connected to SAN storage disks with 2 fiber channel paths.
Software used: Veritas volume manager with DMP 4.1 in the Control domain ;
Veritas Volume Manager 4.1 in the guest domains
The SAN luns are exported to the Guest LDOM's by exporting the whole DMP
devices for ex. /dev/vx/dmp/<device name>. They are accessible by the guest
domains without issues in normal situations.
Problem:
Whenever we powercycle the T5240 server, the guest domains configured in
LDOM using the SAN disks gets stuck while booting. the SAN disks which
were exported before to the guest domain is not accessbile by the guest
domain anymore. Once I remove the disks and add them back in the LDOM
config, it works fine.
Regards
Sidh
Alexandre Chartre
<Alexandre.Chartr
e at Sun.COM> To
Sent by: Rushi Srinivas
ldoms-discuss-bou <rushi.srinivas at gmail.com>
nces at opensolaris. cc
org ldoms-discuss at opensolaris.org
Subject
Re: [ldoms-discuss] SVM metaset and
02/21/2009 04:01 SCSI commands on vdisk backends
AM
Rushi Srinivas wrote:
> Hi Alex,
>
> Thanks for confirming that SCSI inquiries are supported from both
> guest LDom and control Domain on the same physical SCSI disk.
>
> However, your statement,
> "When using VxDMP, you should use the disk as managed by VxDMP
> (i.e. /dev/vx/dmp/dsk/...) and not the physical disk itself
(/dev/dsk/...)".
>
> But this statement contradicts (if I understood correctly) the following
> statement mentioned in Veritas 5.0 MP3 document, which says,
>
> "The virtual disk client (VDC) driver controls all virtual disks in the
> Guest LDom and not the SCSI driver. Therefore, it is not possible to
construct
> a SCSI packet and send the packet down through DMP." [ section DMP SCSI
Bypass,
> page 22 under Veritas Storage Foundation features restrictions]
That's an old statement because LDoms use to exclusively opens devices
exported
as virtual disks, and this was preventing other applications to use that
device.
This is no longer the case and you can use /dev/vx/dmp even if it is
exported
as a vdisk.
> Does this mean that with DMP in guest domain SCSI inquiry should be
invoked
> on on /dev/dsk/... and not on /dev/vx/dmp/... device?
Actually this does not really no matter as you eventually access the same
disk
(but /dev/vx/dmp/ manages multipathing).
alex.
_______________________________________________
ldoms-discuss mailing list
ldoms-discuss at opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
Generally, this communication is for informational purposes only
and it is not intended as an offer or solicitation for the purchase
or sale of any financial instrument or as an official confirmation
of any transaction. In the event you are receiving the offering
materials attached below related to your interest in hedge funds or
private equity, this communication may be intended as an offer or
solicitation for the purchase or sale of such fund(s). All market
prices, data and other information are not warranted as to
completeness or accuracy and are subject to change without notice.
Any comments or statements made herein do not necessarily reflect
those of JPMorgan Chase & Co., its subsidiaries and affiliates.
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.
