cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

DMP devices displayed at the format

Hi all,

just to understand the way DMP manages devices. We want to use DMP devices inside zpools. So I enabled the dmp_native_support and disabled the MPxIO. Everything seems to work the right way. However in the format (solaris 10) I see dmp devices with strange names:

 

      13. c0d11018 <HP-OPEN-V-SUN-6007 cyl 27304 alt 2 hd 15 sec 512>  100GB-00
          /virtual-devices@100/channel-devices@200/disk@2b0a
      14. c0d11035 <HP-OPEN-V-SUN-6007 cyl 4094 alt 2 hd 15 sec 512>  2GB-03
          /virtual-devices@100/channel-devices@200/disk@2b1b
      15. c0d11111 <HP-OPEN-V-SUN-6007 cyl 271 alt 2 hd 15 sec 512>  1GB-02
          /virtual-devices@100/channel-devices@200/disk@2b67
      16. c0d12111 <HP-OPEN-V-SUN-6007 cyl 27304 alt 2 hd 15 sec 512>  100G-loc
          /virtual-devices@100/channel-devices@200/disk@2f4f
      17. hp_xp24k0_022bs6 <HP-OPEN-V*2-SUN-6007 cyl 10921 alt 2 hd 15 sec 512>  40GB
          /dev/vx/rdmp/hp_xp24k0_022bs6
      18. hp_xp24k0_022ds0 <HP-OPEN-V-SUN-6007 cyl 5459 alt 2 hd 15 sec 512>  20GB
          /dev/vx/rdmp/hp_xp24k0_022ds0
      19. hp_xp24k0_0128s5 <HP-OPEN-V-SUN-6007 cyl 27304 alt 2 hd 15 sec 512>  100G-loc
          /dev/vx/rdmp/hp_xp24k0_0128s5
      20. hp_xp24k0_0231s4 <HP-OPEN-V-SUN-6007 cyl 4094 alt 2 hd 15 sec 512>  2GB-03
          /dev/vx/rdmp/hp_xp24k0_0231s4
      21. hp_xp24k0_0531s4 <HP-OPEN-V-SUN-6007 cyl 27304 alt 2 hd 15 sec 512>  100GB-01
          /dev/vx/rdmp/hp_xp24k0_0531s4
      22. hp_xp24k0_0635s4 <HP-OPEN-V-SUN-6007 cyl 544 alt 2 hd 15 sec 512>  2GB-00
          /dev/vx/rdmp/hp_xp24k0_0635s4
      23. hp_xp24k0_0636s7 <HP-OPEN-V-SUN-6007 cyl 544 alt 2 hd 15 sec 512>  2GB-01
          /dev/vx/rdmp/hp_xp24k0_0636s7
      24. hp_xp24k0_0637s0 <HP-OPEN-V-SUN-6007 cyl 544 alt 2 hd 15 sec 512>  2GB-02
          /dev/vx/rdmp/hp_xp24k0_0637s0
 
Names end with the slice number, that is different for each disk. Moreover the partition is not present on the disk. For instance:
 
prtvtoc /dev/vx/rdmp/hp_xp24k0_0636s7 | grep -v ^*
       0      2    00      23040   4154880   4177919
       2      5    01          0   4177920   4177919
 
I tried with a riconfigurative boot but nothing changed. 
The question is: how does DMP assign name to disks? is there any way to correct the format output?
Many thanks, regards
Mauro Vicini
1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

I am wondering here as

I am wondering here as solaris device layer is below DMP, so might be that DMP has nothing to do here..

how are disks visible in "vxdisk list" command ?

also, what version you are using for vxvm ?

 

I had a look at 5.1RP1 readme file for DMP & this is what I see is one of known issues:

Using DMP with zpools on a simple disk
On Solaris, when a zpool is created on a whole (simple) disk (device name not
containing any slice), ZFS changes the label on the disk from SMI to EFI label. The
DMP device shows in the error state until you update the DMP data structures.

To update the DMP data structures with this change, run the vxdisk scandisks
command.

 

Link here:

ftp://ftp.veritas.com/pub/support/patchcentral/Solaris/5.1/vm/vm-sol_x64-5.1RP1_DMP_Native_Support_GA-patches.tar.gz_doc/dmp_readme_51rp1_sol.pdf

more stuff to check in the document:

Device naming limitations
In order to useDMPfor OS native device support, the device naming scheme must
be enclosure-based naming (EBN) and the persistence attribute must be on.
The naming scheme cannot be changed after the feature is enabled.

has this been tried ?
 

 

Disk access name limitations
The following limitations apply to disk access names:
■ You cannot change the DMP name of a device when native device support is
enabled. If you must change the DMP name, you must disable the feature,
update the name and again enable the feature.
■ You also cannot change the name for an enclosure which has at least oneDMP
device that is using native device support, because that would require theDMP
device name to change.
■ Whennative multipathing is enabled, you cannot assign device names manually
using the vxddladm assign names command.

Gaurav

View solution in original post

2 Replies
Highlighted
Accepted Solution!

I am wondering here as

I am wondering here as solaris device layer is below DMP, so might be that DMP has nothing to do here..

how are disks visible in "vxdisk list" command ?

also, what version you are using for vxvm ?

 

I had a look at 5.1RP1 readme file for DMP & this is what I see is one of known issues:

Using DMP with zpools on a simple disk
On Solaris, when a zpool is created on a whole (simple) disk (device name not
containing any slice), ZFS changes the label on the disk from SMI to EFI label. The
DMP device shows in the error state until you update the DMP data structures.

To update the DMP data structures with this change, run the vxdisk scandisks
command.

 

Link here:

ftp://ftp.veritas.com/pub/support/patchcentral/Solaris/5.1/vm/vm-sol_x64-5.1RP1_DMP_Native_Support_GA-patches.tar.gz_doc/dmp_readme_51rp1_sol.pdf

more stuff to check in the document:

Device naming limitations
In order to useDMPfor OS native device support, the device naming scheme must
be enclosure-based naming (EBN) and the persistence attribute must be on.
The naming scheme cannot be changed after the feature is enabled.

has this been tried ?
 

 

Disk access name limitations
The following limitations apply to disk access names:
■ You cannot change the DMP name of a device when native device support is
enabled. If you must change the DMP name, you must disable the feature,
update the name and again enable the feature.
■ You also cannot change the name for an enclosure which has at least oneDMP
device that is using native device support, because that would require theDMP
device name to change.
■ Whennative multipathing is enabled, you cannot assign device names manually
using the vxddladm assign names command.

Gaurav

View solution in original post

Highlighted

Hi Gaurav, thanks for your

Hi Gaurav,

thanks for your answer.

 

root@VASPOCET3-PBC2L2D1 # vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
hp_xp24k0_00ef auto:cdsdisk    -            -            online
hp_xp24k0_00f0 auto:cdsdisk    -            -            online
hp_xp24k0_00f1 auto:cdsdisk    -            -            online
hp_xp24k0_022b auto:none       -            -            online invalid
hp_xp24k0_022d auto:none       -            -            online invalid
hp_xp24k0_0128 auto:ZFS        -            -            ZFS
hp_xp24k0_0231 auto:none       -            -            online invalid
hp_xp24k0_0530 auto:cdsdisk    -            -            online shared
hp_xp24k0_0531 auto:none       -            -            online invalid
hp_xp24k0_0635 auto:none       -            -            online invalid
hp_xp24k0_0636 auto:none       -            -            online invalid
hp_xp24k0_0637 auto:none       -            -            online invalid
root@VASPOCET3-PBC2L2D1 # pkginfo -l VRTSvxvm 
   PKGINST:  VRTSvxvm
      NAME:  Binaries for VERITAS Volume Manager by Symantec
  CATEGORY:  system
      ARCH:  sparc
   VERSION:  5.1,REV=10.06.2009.22.05
   BASEDIR:  /
    VENDOR:  Symantec Corporation
      DESC:  Virtual Disk Subsystem
    PSTAMP:  5.1.100.000-5.1SP1-2010-10-10
  INSTDATE:  Feb 17 2012 17:08
   HOTLINE:  http://support.veritas.com/phonesup/phonesup_ddProduct_.htm
     EMAIL:  support@veritas.com
    STATUS:  completely installed
     FILES:      950 installed pathnames
                  34 shared pathnames
                 115 directories
                 425 executables
              417695 blocks used (approx)
root@VASPOCET3-PBC2L2D1 # vxddladm get namingscheme
NAMING_SCHEME       PERSISTENCE    LOWERCASE      USE_AVID       
============================================================
Enclosure Based     Yes            Yes            Yes            
 
Customer use ASM, don't know if this is related.
Thanks