How to remove EMC DMX devices from a HP-UX 11.23 Server running Veritas Volume Manager (VxVM) 5.0 MP2 RP3 using DMP

Article:HOWTO53293  |  Created: 2011-06-05  |  Updated: 2014-01-02  |  Article URL http://www.symantec.com/docs/HOWTO53293
Article Type
How To




This document attempts to explain the essential steps required to unpresent (mask) EMC DMX storage devices controlled by DMP.

Due to numerous product enhancements surrounding the removal and provisioning of new devices to a running HP-UX server, it is essential that 5.0 MP2 RP3 for Veritas Volume Manager (VxVM) be installed.


How to confirm the current VRTSvxvm patch level on HP-UX

 

# swlist | grep -i VRTSvxvm
  PHCO_41469                            1.0            VRTS 5.0 MP2RP3 VRTSvxvm Command Patch
  PHKL_41470                            1.0            VRTS 5.0 MP2RP3 VRTSvxvm kernel Patch
  VRTSvxvm                              5.0            Veritas Volume Manager by Symantec


NOTE: Prior to installing 5.0 MP2 RP3, you may be prompted to install the following O/S patch
, PHCO_40214.

 

To obtain HP-UX O/S related patches, visit the HP IT Resource Center:

http://www11.itrc.hp.com/service/patch/mainPage.do

 

Example



The following EMC DMX SYMDEV "02F0" device will be unpresented (masked) from a HP-UX server using DMP as the multipathing solution.

# uname -a
HP-UX unknown B.11.23 U 9000/800 3101432742 unlimited-user license

 
The free EMC inq utility can be obtained using the following ftp link.

ftp://ftp.emc.com/pub/symm3000/inquiry/

 

The EMC inq utility presents an overview of the devices currently presented to the local server.

 
# /opt/inq.hpux1100 -f_emc
Inquiry utility, Version V7.3-1159 (Rev 1.0)      (SIL Version V7.2.1.0 (Edit Level 1159)
Copyright (C) by EMC Corporation, all rights reserved.
For help type inq -h.

.....................................

----------------------------------------------------------------------------------
DEVICE                  :VEND    :PROD            :REV   :SER NUM    :CAP(kb)
----------------------------------------------------------------------------------
/dev/rdsk/c6t0d0        :EMC     :SYMMETRIX       :5773  :2200010000 :        2880
/dev/rdsk/c6t2d0        :EMC     :SYMMETRIX       :5773  :22000f7000 :     2209920
/dev/rdsk/c6t2d1        :EMC     :SYMMETRIX       :5773  :22000f8000 :     2209920
/dev/rdsk/c6t2d2        :EMC     :SYMMETRIX       :5773  :22000f9000 :     2209920
/dev/rdsk/c8t0d0        :EMC     :SYMMETRIX       :5773  :2200010000 :        2880
/dev/rdsk/c8t14d7       :EMC     :SYMMETRIX       :5773  :22000f7000 :     2209920
/dev/rdsk/c10t1d7       :EMC     :SYMMETRIX       :5773  :22002f0000 :     2218560    <<<<<
/dev/vx/rdmp/EMC0_0     :EMC     :SYMMETRIX       :5773  :22002ef000 :     2218560
/dev/vx/rdmp/EMC0_1     :EMC     :SYMMETRIX       :5773  :22000f9000 :     2209920
/dev/vx/rdmp/EMC0_2     :EMC     :SYMMETRIX       :5773  :22000f8000 :     2209920
/dev/vx/rdmp/EMC0_3     :EMC     :SYMMETRIX       :5773  :22000f7000 :     2209920
/dev/vx/rdmp/EMC0_4     :EMC     :SYMMETRIX       :5773  :22002f0000 :     2218560  <<<<< device to be removed

 

In this instance the EMC Symmetrix ID(SID) is "000290300822" (SID 822 for short) connected to wwn "50060b000029e248"

 
It is advisable to refresh the HBA content using "symmask discover hba".


NOTE: To run the EMC SYMCLI commands directly on the server, the EMC "SYMCLI" package must be installed and licensed.


# swlist | grep -i symcli
  SYMCLI                        V7.0.0.0       EMC Data Storage Systems Private Limited
  SYMCLI                        V7.0.0.0       EMC Data Storage Systems Private Limited



How to establish the wwn details for the local server
 

# symmask discover hba

Symmetrix ID          : 000290300822
Device Masking Status : Success

  Identifier        Type   User-generated Name
  ----------------  -----  ---------------------------------
  50060b000029e248  Fibre  rdgrp3410-05/50060b000029e248


To list the "wwn" content visible to the server, type "symmask list hba".
 

# symmask list hba

Identifier        Type   Adapter           Physical Device Path      Dir:P
----------------  -----  ----------------  ------------------------  -----
50060b000029e248  Fibre  0-4-1-0-4-0       /dev/rdsk/c8t0d0          16C:0
                                           /dev/rdsk/c6t0d0          16C:1


How to confirm what wwn a given EMC SYMDEV is assigned to


In this instance, EMC SYMDEV "02F0" is assigned to wwn's "50060b000029e3d0" and "50060b000029e248".
The wwn for this local server is "
50060b000029e248".




# ./symmaskdb -sid 822 list assignment -dev 02F0

Symmetrix ID : 000290300822

Device  Identifier        Type   Dir:P
------  ----------------  -----  ----------------
02F0    50060b000029e3d0  FIBRE  FA-16C:0,FA-16C:1
        50060b000029e248  FIBRE  FA-16C:1

 

To confirm the Symmetrix ID is visible to the server, in this instance, type "symcfg -sid 822 list"


# ./symcfg -sid 822 list

Symmetrix ID: 000290300822

                                S Y M M E T R I X

                                       Mcode    Cache      Num Phys  Num Symm
    SymmID       Attachment  Model     Version  Size (MB)  Devices   Devices

    000290300822 Local       DMX4-6    5773        8192        11       900

 


Lun provisioning pre-checks


Prior to the removal of any storage.

 
1.] Ensure
the HP-UX device tree is clean prior to the removal of any new luns.
 

To display the devices currently discovered by the O/S, type:


# ioscan -fnC disk
Class     I  H/W Path        Driver     S/W State   H/W Type     Description
=============================================================================
disk      0  0/0/2/0.0.0.0   sdisk      CLAIMED     DEVICE       TEAC    DV-28E-N
                            /dev/dsk/c0t0d0   /dev/rdsk/c0t0d0
disk      1  0/1/1/0.0.0     sdisk      CLAIMED     DEVICE       HP 36.4GST336754LC
                            /dev/dsk/c2t0d0   /dev/rdsk/c2t0d0
disk      2  0/1/1/0.1.0     sdisk      CLAIMED     DEVICE       HP 36.4GST336754LC
                            /dev/dsk/c2t1d0   /dev/rdsk/c2t1d0
disk      3  0/4/1/0/4/0.1.11.0.0.0.0   sdisk      CLAIMED     DEVICE       HITACHI DF600F
                            /dev/dsk/c4t0d0   /dev/rdsk/c4t0d0
disk      4  0/4/1/0/4/0.1.11.0.0.0.1   sdisk      CLAIMED     DEVICE       HITACHI DF600F
                            /dev/dsk/c4t0d1   /dev/rdsk/c4t0d1
disk      5  0/4/1/0/4/0.1.11.0.0.0.2   sdisk      CLAIMED     DEVICE       HITACHI DF600F
                            /dev/dsk/c4t0d2   /dev/rdsk/c4t0d2
disk      6  0/4/1/0/4/0.1.11.0.0.0.3   sdisk      CLAIMED     DEVICE       HITACHI DF600F
                            /dev/dsk/c4t0d3   /dev/rdsk/c4t0d3
disk      7  0/4/1/0/4/0.1.11.0.0.0.4   sdisk      CLAIMED     DEVICE       HITACHI DF600F
                            /dev/dsk/c4t0d4   /dev/rdsk/c4t0d4
disk      8  0/4/1/0/4/0.1.11.0.0.0.5   sdisk      CLAIMED     DEVICE       HITACHI DF600F
                            /dev/dsk/c4t0d5   /dev/rdsk/c4t0d5
disk      9  0/4/1/0/4/0.1.11.0.0.0.6   sdisk      CLAIMED     DEVICE       HITACHI DF600F
                            /dev/dsk/c4t0d6   /dev/rdsk/c4t0d6
disk     10  0/4/1/0/4/0.1.11.0.0.0.7   sdisk      CLAIMED     DEVICE       HITACHI DF600F
                            /dev/dsk/c4t0d7   /dev/rdsk/c4t0d7
disk     11  0/4/1/0/4/0.1.11.0.0.1.0   sdisk      CLAIMED     DEVICE       HITACHI DF600F
                            /dev/dsk/c4t1d0   /dev/rdsk/c4t1d0
disk     12  0/4/1/0/4/0.1.11.0.0.1.1   sdisk      CLAIMED     DEVICE       HITACHI DF600F
                            /dev/dsk/c4t1d1   /dev/rdsk/c4t1d1
disk     14  0/4/1/0/4/0.34.7.0.0.0.0   sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX
                            /dev/dsk/c6t0d0   /dev/rdsk/c6t0d0
disk     15  0/4/1/0/4/0.34.7.0.0.2.0   sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX
                            /dev/dsk/c6t2d0   /dev/rdsk/c6t2d0
disk     16  0/4/1/0/4/0.34.7.0.0.2.1   sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX
                            /dev/dsk/c6t2d1   /dev/rdsk/c6t2d1
disk     17  0/4/1/0/4/0.34.7.0.0.2.2   sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX
                            /dev/dsk/c6t2d2   /dev/rdsk/c6t2d2
disk     19  0/4/1/0/4/0.34.7.0.1.1.6   sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX
disk     20  0/4/1/0/4/0.34.7.0.1.1.7   sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX
                            /dev/dsk/c10t1d7   /dev/rdsk/c10t1d7

disk     13  0/4/1/0/4/0.34.8.0.0.0.0   sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX
                            /dev/dsk/c8t0d0   /dev/rdsk/c8t0d0
disk     18  0/4/1/0/4/0.34.8.0.0.14.7  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX
                            /dev/dsk/c8t14d7   /dev/rdsk/c8t14d7



To report any stale device entries, type:
 

# ioscan -fnC disk | grep -i NO_HW


If devices are reported as "NO_HW", these entries must be deleted, and VxVM refreshed prior to the removal of any disks.


2.] To delete such stale entries, use the rmsf command:


Example


To delete the following "0/4/1/0/4/0.34.7.0.1.1.7" device entry:


# ioscan -fnC disk | grep -i NO_HW
disk     20  0/4/1/0/4/0.34.7.0.1.1.7   sdisk      NO_HW       DEVICE       EMC     SYMMETRIX

Type,

# rmsf -H  0/4/1/0/4/0.34.7.0.1.1.7 -k -v


Once done, confirm the entry has been deleted.

# ioscan -fnC disk | grep -i NO_HW
#
 

3.] Ensure VxVM is refreshed and the /etc/vx/disk.info file contents are updated prior to removing any storage.


# vxdisk scandisks


The VXVM CLI "vxddladm assign names" command was introduced with VxVM 5.0.1 on HP-UX 11.31 to refresh the contents of the /etc/vx/disk.info.
As this option does not exist with 5.0 MP2, the vxddladm persistence option can be toggled on and off to refresh the /etc/vx/disk.info file contents.


In this instance, the namingscheme is set to "ebn".


# vxddladm set namingscheme=ebn persistence=no

# vxddladm set namingscheme=ebn persistence=yes


4.]


To refresh the Physical Device Name details, run "symcfg discover"


How to view the EMC DMX devices associated with SID "822"


In this instance, using the Symmetrix ID "822" and the wwn of the server concerned (
50060b000029e248), type:



# ./symmaskdb -sid 822 list devs -wwn 50060b000029e248

Symmetrix ID        : 000290300822

Originator Port wwn : 50060b000029e248
User-generated Name : rdgrp3410-05/50060b000029e248

Sym Dev                                               LUN
Name    Dir:P  Physical Device Name     VBUS  TID  SYMM HOST  Attr  Cap(MB)
------  -----  -----------------------  ----  ---  ---- ----  ----  -------
00F0     1C:0  Not Visible                 0    0    19  N/A           2158
         1C:1  Not Visible                 0    0    db  N/A           2158
        16C:0  Not Visible                 0    0    db  N/A           2158
        16C:1  Not Visible                 0    0    19  N/A           2158
00F7     1C:0  Not Visible                 0    0    20  N/A           2158
         1C:1  Not Visible                 0    0    e7  N/A           2158
        16C:0  /dev/vx/rdmp/EMC0_3         0    0    e7    7           2158
        16C:1  /dev/vx/rdmp/EMC0_3         0    0    20    0           2158
00F8     1C:0  Not Visible                 0    0    21  N/A           2158
         1C:1  Not Visible                 0    0    e8  N/A           2158
        16C:0  Not Visible                 0    0    e8  N/A           2158
        16C:1  /dev/vx/rdmp/EMC0_2         0    0    21    0           2158
00F9     1C:0  Not Visible                 0    0    22  N/A           2158
         1C:1  Not Visible                 0    0    e9  N/A           2158
        16C:0  Not Visible                 0    0    e9  N/A           2158
        16C:1  /dev/vx/rdmp/EMC0_1         0    0    22    0           2158
02EF    16C:0  Not Visible                 0    0   12d  N/A           2167
        16C:1  /dev/vx/rdmp/EMC0_0         0    0   116    0           2167
02F0    16C:1  Not Visible                 0    0   117  N/A           2167        <<<< LUN to be removed, details have not been updated.


# ./symcfg -sid 822 discover

Attempting discovery of Symmetrix 000290300822

This operation may take up to a few minutes. Please be patient...


# ./symmaskdb -sid 822 list devs -wwn 50060b000029e248

Symmetrix ID        : 000290300822

Originator Port wwn : 50060b000029e248
User-generated Name : rdgrp3410-05/50060b000029e248

Sym Dev                                               LUN
Name    Dir:P  Physical Device Name     VBUS  TID  SYMM HOST  Attr  Cap(MB)
------  -----  -----------------------  ----  ---  ---- ----  ----  -------
00F0     1C:0  Not Visible                 0    0    19  N/A           2158
         1C:1  Not Visible                 0    0    db  N/A           2158
        16C:0  Not Visible                 0    0    db  N/A           2158
        16C:1  Not Visible                 0    0    19  N/A           2158
00F7     1C:0  Not Visible                 0    0    20  N/A           2158
         1C:1  Not Visible                 0    0    e7  N/A           2158
        16C:0  /dev/vx/rdmp/EMC0_3         0    0    e7    7           2158
        16C:1  /dev/vx/rdmp/EMC0_3         0    0    20    0           2158
00F8     1C:0  Not Visible                 0    0    21  N/A           2158
         1C:1  Not Visible                 0    0    e8  N/A           2158
        16C:0  Not Visible                 0    0    e8  N/A           2158
        16C:1  /dev/vx/rdmp/EMC0_2         0    0    21    0           2158
00F9     1C:0  Not Visible                 0    0    22  N/A           2158
         1C:1  Not Visible                 0    0    e9  N/A           2158
        16C:0  Not Visible                 0    0    e9  N/A           2158
        16C:1  /dev/vx/rdmp/EMC0_1         0    0    22    0           2158
02EF    16C:0  Not Visible                 0    0   12d  N/A           2167
        16C:1  /dev/vx/rdmp/EMC0_0         0    0   116    0           2167
02F0    16C:1  /dev/vx/rdmp/EMC0_4         0    0   117    0           2167



Lun removal steps:


Prior to the removal of the disk from the server.
 

1.] Ensure all corresponding filesystems are unmounted.


2.] Remove the disk from the required diskgroup, or deport if the diskgroup is to be migrated to an alternate host


# vxdg deport <diskgroup-name>


3.] Confirm using "vxdg list" that all required diskgroup(s) were deported


4.] Inform Volume Manager that the corresponding luns are to be removed, by running "vxdisk rm <disk-access-name>"


In this instance, EMC SYMDEV "02F0", Veritas Disk Access Name "EMC0_4"


# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
AMS_WMS0_0   auto:none       -            -            online invalid
AMS_WMS0_1   auto:none       -            -            online invalid
AMS_WMS0_2   auto:hpdisk     -            -            online
AMS_WMS0_3   auto:hpdisk     -            -            online
AMS_WMS0_4   auto:hpdisk     -            -            online
AMS_WMS0_5   auto:none       -            -            online invalid
AMS_WMS0_6   auto:cdsdisk    -            -            online
AMS_WMS0_7   auto:cdsdisk    -            -            online
AMS_WMS0_8   auto:cdsdisk    -            -            online
AMS_WMS0_9   auto:cdsdisk    -            -            online
Disk_0       auto:hpdisk     rootdisk01   rootdg       online
Disk_1       auto:hpdisk     -            -            online
EMC0_0       auto:none       -            -            online invalid
EMC0_1       auto:none       -            -            online invalid
EMC0_2       auto:none       -            -            online invalid
EMC0_3       auto:cdsdisk    -            -            online
EMC0_4       auto:none       -            -            online invalid  <<<< disk to be removed


# vxdisk rm EMC0_4


# vxdmpadm getsubpaths dmpnodename=EMC0_4

NAME         STATE[A]   PATH-TYPE[M] CTLR-NAME  ENCLR-TYPE   ENCLR-NAME    ATTRS
================================================================================
c10t1d7      ENABLED(A)   -          c10        EMC          EMC0             -


5.] Mask the LUN using the EMC SYMCLI interface.


# ./symmask -sid 822 -wwn 50060b000029e248 remove devs 02F0 -dir 16c -p 1


NOTE: In this instance, SYMDEV "02F0" has only a single path.

 

6.] Refresh and update the EMC Symmask Database



# ./symmask -sid 822 refresh -noprompt



Symmetrix FA/SE directors updated with contents of SymMask Database 000290300822


#  ./symcfg -sid 822 discover

Attempting discovery of Symmetrix 000290300822

This operation may take up to a few minutes. Please be patient...


7.]  Clean-up the HP device tree.


In this instance, hardware path "
0/4/1/0/4/0.34.7.0.1.1.7 " refers to removed lun " /dev/dsk/c10t1d7 ".


# ioscan -fnC disk | grep -i NO_HW
disk     20  0/4/1/0/4/0.34.7.0.1.1.7   sdisk      NO_HW       DEVICE       EMC     SYMMETRIX


To remove the stale device entry, type:


# rmsf -H  0/4/1/0/4/0.34.7.0.1.1.7 -k -v


Rescan the O/S device tree, to ensure the device entry does not reappear.


# ioscan -fnC disk | grep -i NO_HW



8.] Veritas DMP will still be aware of the removed LUN, until VxVM has been refreshed.


# vxdmpadm getsubpaths dmpnodename=EMC0_4

NAME         STATE[A]   PATH-TYPE[M] CTLR-NAME  ENCLR-TYPE   ENCLR-NAME    ATTRS
================================================================================
c10t1d7      ENABLED(A)   -          c10        EMC          EMC0             -


# vxdisk scandisks


# vxdmpadm getsubpaths dmpnodename=EMC0_4
VxVM vxdmpadm ERROR V-5-1-2268 EMC0_4 is not a valid dmp node name



# vxdisk list

DEVICE       TYPE            DISK         GROUP        STATUS
AMS_WMS0_0   auto:none       -            -            online invalid
AMS_WMS0_1   auto:none       -            -            online invalid
AMS_WMS0_2   auto:hpdisk     -            -            online
AMS_WMS0_3   auto:hpdisk     -            -            online
AMS_WMS0_4   auto:hpdisk     -            -            online
AMS_WMS0_5   auto:none       -            -            online invalid
AMS_WMS0_6   auto:cdsdisk    -            -            online
AMS_WMS0_7   auto:cdsdisk    -            -            online
AMS_WMS0_8   auto:cdsdisk    -            -            online
AMS_WMS0_9   auto:cdsdisk    -            -            online
Disk_0       auto:hpdisk     rootdisk01   rootdg       online
Disk_1       auto:hpdisk     -            -            online
EMC0_0       auto:none       -            -            online invalid
EMC0_1       auto:none       -            -            online invalid
EMC0_2       auto:none       -            -            online invalid
EMC0_3       auto:cdsdisk    -            -            online

 

NOTE: Veritas Disk Access (DA) Name "EMC0_4" is no longer presented to VxVM.


9.] Refresh the /etc/vx/disk.info file toggle the vxddladm persistence option, on and off.


# cat /etc/vx/disk.info
HP%2036.4G%5FST336754LC%5FDISKS%5F3KQ0HE47%20%20%20%20 c2t1d0 0x1000000 0x2 Disk_0 Disk DISKS
HP%2036.4G%5FST336754LC%5FDISKS%5F3KQ0G987%20%20%20%20 c2t0d0 0x1000010 0x2 Disk_1 Disk DISKS
HITACHI%5FDF600F%5F75050205%5F01EC c4t1d1 0x1000020 0x2 AMS_WMS0_0 AMS_WMS 75050205
HITACHI%5FDF600F%5F75050205%5F01EB c4t1d0 0x1000030 0x2 AMS_WMS0_1 AMS_WMS 75050205
HITACHI%5FDF600F%5F75050205%5F0139 c4t0d6 0x1000040 0x2 AMS_WMS0_2 AMS_WMS 75050205
HITACHI%5FDF600F%5F75050205%5F002C c4t0d4 0x1000050 0x2 AMS_WMS0_3 AMS_WMS 75050205
HITACHI%5FDF600F%5F75050205%5F0138 c4t0d5 0x1000060 0x2 AMS_WMS0_4 AMS_WMS 75050205
HITACHI%5FDF600F%5F75050205%5F01EA c4t0d7 0x1000070 0x2 AMS_WMS0_5 AMS_WMS 75050205
HITACHI%5FDF600F%5F75050205%5F002A c4t0d2 0x1000080 0x2 AMS_WMS0_6 AMS_WMS 75050205
HITACHI%5FDF600F%5F75050205%5F0029 c4t0d1 0x1000090 0x2 AMS_WMS0_7 AMS_WMS 75050205
HITACHI%5FDF600F%5F75050205%5F0028 c4t0d0 0x10000a0 0x2 AMS_WMS0_8 AMS_WMS 75050205
HITACHI%5FDF600F%5F75050205%5F002B c4t0d3 0x10000b0 0x2 AMS_WMS0_9 AMS_WMS 75050205
EMC%5FSYMMETRIX%5F300822%5F222EF000 c10t1d6 0x10000c0 0x2 EMC0_0 EMC 300822
EMC%5FSYMMETRIX%5F300822%5F220F9000 c6t2d2 0x10000d0 0x2 EMC0_1 EMC 300822
EMC%5FSYMMETRIX%5F300822%5F220F8000 c6t2d1 0x10000e0 0x2 EMC0_2 EMC 300822
EMC%5FSYMMETRIX%5F300822%5F220F7000 c6t2d0 0x10000f0 0x2 EMC0_3 EMC 300822
EMC%5FSYMMETRIX%5F300822%5F222F0000 c10t1d7 0xffffffff 0x2 EMC0_4 EMC 300822


NOTE: The "0xffffffff" device state implies the disk was marked for removal.


#  vxddladm set namingscheme=ebn persistence=no


#  more /etc/vx/disk.info

/etc/vx/disk.info: No such file or directory


#  vxddladm set namingscheme=ebn persistence=yes

# more /etc/vx/disk.info

HP%2036.4G%5FST336754LC%5FDISKS%5F3KQ0HE47%20%20%20%20 c2t1d0 0x1000000 0x2 Disk_0 Disk DISKS
HP%2036.4G%5FST336754LC%5FDISKS%5F3KQ0G987%20%20%20%20 c2t0d0 0x1000010 0x2 Disk_1 Disk DISKS
HITACHI%5FDF600F%5F75050205%5F01EC c4t1d1 0x1000020 0x2 AMS_WMS0_0 AMS_WMS 75050205
HITACHI%5FDF600F%5F75050205%5F01EB c4t1d0 0x1000030 0x2 AMS_WMS0_1 AMS_WMS 75050205
HITACHI%5FDF600F%5F75050205%5F0139 c4t0d6 0x1000040 0x2 AMS_WMS0_2 AMS_WMS 75050205
HITACHI%5FDF600F%5F75050205%5F002C c4t0d4 0x1000050 0x2 AMS_WMS0_3 AMS_WMS 75050205
HITACHI%5FDF600F%5F75050205%5F0138 c4t0d5 0x1000060 0x2 AMS_WMS0_4 AMS_WMS 75050205
HITACHI%5FDF600F%5F75050205%5F01EA c4t0d7 0x1000070 0x2 AMS_WMS0_5 AMS_WMS 75050205
HITACHI%5FDF600F%5F75050205%5F002A c4t0d2 0x1000080 0x2 AMS_WMS0_6 AMS_WMS 75050205
HITACHI%5FDF600F%5F75050205%5F0029 c4t0d1 0x1000090 0x2 AMS_WMS0_7 AMS_WMS 75050205
HITACHI%5FDF600F%5F75050205%5F0028 c4t0d0 0x10000a0 0x2 AMS_WMS0_8 AMS_WMS 75050205
HITACHI%5FDF600F%5F75050205%5F002B c4t0d3 0x10000b0 0x2 AMS_WMS0_9 AMS_WMS 75050205
EMC%5FSYMMETRIX%5F300822%5F222EF000 c10t1d6 0x10000c0 0x2 EMC0_0 EMC 300822
EMC%5FSYMMETRIX%5F300822%5F220F9000 c6t2d2 0x10000d0 0x2 EMC0_1 EMC 300822
EMC%5FSYMMETRIX%5F300822%5F220F8000 c6t2d1 0x10000e0 0x2 EMC0_2 EMC 300822
EMC%5FSYMMETRIX%5F300822%5F220F7000 c6t2d0 0x10000f0 0x2 EMC0_3 EMC 300822


# vxdisk -e list
DEVICE       TYPE      DISK         GROUP        STATUS       OS_NATIVE_NAME
AMS_WMS0_0   auto      -             -            online       c4t1d1
AMS_WMS0_1   auto      -             -            online       c4t1d0
AMS_WMS0_2   auto      -             -            online       c4t0d6
AMS_WMS0_3   auto      -             -            online       c4t0d4
AMS_WMS0_4   auto      -             -            online       c4t0d5
AMS_WMS0_5   auto      -             -            online       c4t0d7
AMS_WMS0_6   auto      -             -            online       c4t0d2
AMS_WMS0_7   auto      -             -            online       c4t0d1
AMS_WMS0_8   auto      -             -            online       c4t0d0
AMS_WMS0_9   auto      -             -            online       c4t0d3
Disk_0       auto      rootdisk01    rootdg       online       c2t1d0
Disk_1       auto      -             -            online       c2t0d0
EMC0_0       auto      -             -            online       c10t1d6
EMC0_1       auto      -             -            online       c6t2d2
EMC0_2       auto      -             -            online       c6t2d1
EMC0_3       auto      -             -            online       c6t2d0



Additional content



The "vxddladm get namingscheme" CLI command is available in 5.0.1 for HP 11.31.


# vxddladm get namingscheme
VxVM vxddladm ERROR V-5-1-2511 Unexpected error
VxVM vxddladm ERROR V-5-1-2585
        Incorrect Usage


        Usage: vxddladm [domain=<domainname>] [host=<hostname1,hostname2,...>] option <attribute=value..>
 option = [listexclude | listsupport | addjbod | rmjbod | excludearray
        listjbod | includearray | listversion | listforeign | rmforeign | addforeign | start eventsource | stop eventsource]
        enablescsi3 | disablescsi3 | modescsi3 | set

        For detailed help use vxddladm help




The EMC inq utility can be used to validate the revised view of the EMC related devices:


# /opt/inq.hpux1100 -sid -f_emc
Inquiry utility, Version V7.3-1159 (Rev 1.0)      (SIL Version V7.2.1.0 (Edit Level 1159)
Copyright (C) by EMC Corporation, all rights reserved.
For help type inq -h.

....................................

-------------------------------------------------------------------------------------------------
DEVICE                  :VEND    :PROD            :REV   :SER NUM    :CAP(kb)        :SYMM ID
-------------------------------------------------------------------------------------------------
/dev/rdsk/c6t0d0        :EMC     :SYMMETRIX       :5773  :2200010000 :        2880  :000290300822
/dev/rdsk/c6t2d0        :EMC     :SYMMETRIX       :5773  :22000f7000 :     2209920  :000290300822
/dev/rdsk/c6t2d1        :EMC     :SYMMETRIX       :5773  :22000f8000 :     2209920  :000290300822
/dev/rdsk/c6t2d2        :EMC     :SYMMETRIX       :5773  :22000f9000 :     2209920  :000290300822
/dev/rdsk/c8t0d0        :EMC     :SYMMETRIX       :5773  :2200010000 :        2880  :000290300822
/dev/rdsk/c8t14d7       :EMC     :SYMMETRIX       :5773  :22000f7000 :     2209920  :000290300822
/dev/vx/rdmp/EMC0_0     :EMC     :SYMMETRIX       :5773  :22002ef000 :     2218560  :000290300822
/dev/vx/rdmp/EMC0_1     :EMC     :SYMMETRIX       :5773  :22000f9000 :     2209920  :000290300822
/dev/vx/rdmp/EMC0_2     :EMC     :SYMMETRIX       :5773  :22000f8000 :     2209920  :000290300822
/dev/vx/rdmp/EMC0_3     :EMC     :SYMMETRIX       :5773  :22000f7000 :     2209920  :000290300822
#


NOTE: EMC0_4 (aka c10t1d7) is no longer visible to the O/S.



The number of "Symm" devices reported by "symcfg" should have also decreased.


# symcfg -sid 822 list

Symmetrix ID: 000290300822

                                S Y M M E T R I X

                                       Mcode    Cache      Num Phys  Num Symm
    SymmID       Attachment  Model     Version  Size (MB)  Devices   Devices

    000290300822 Local       DMX4-6    5773        8192        10       900         <<<< 11 devices were previously reported.


Process complete.





Article URL http://www.symantec.com/docs/HOWTO53293


Terms of use for this information are found in Legal Notices