How to deactivate and remove an EMC MirrorView SnapView snapshot from a Solaris server using EMC PowerPath

book

Article ID: 100037724

calendar_today

Updated On:

Description

Description

This document attempts to explain how to deactivate and remove an EMC MirrorView SnapView snapshot from a Solaris server.

The following EMC CLARiiON devices are presented to a Solaris server using EMC PowerPath as the multipathing solution

 

Volume Manager device listing

 
In this instance, the EMC MirrorView SnapView snapshot devices controlled by EMC PowerPath are emcpower6s2, emcpower7s2 and emcpower8s2.
 

# vxdisk -e -o alldgs list
DEVICE       TYPE           DISK        GROUP        STATUS               OS_NATIVE_NAME   ATTR
disk_0       auto:sliced    c2t0d0       rootdg      online               c2t0d0s2         -
disk_1       auto:sliced    c2t0d0-s0    rootdg2     online               c2t1d0s2         -
emcpower0s2  auto           -            -           error                emcpower0c       -
emcpower1s2  auto           -            -           error                emcpower1c       -
emcpower2s2  auto           -            -           error                emcpower2c       -
emcpower3s2  auto           -            -           error                emcpower3c       -
emcpower4s2  auto           -            -           error                emcpower4c       -
emcpower5s2  auto           -            -           error                emcpower5c       -
emcpower6s2  auto:cdsdisk   emc_clariion0_500  asyncDG1_fd online               emcpower6c       -  <<<< EMC MirrorView SnapView snapshot "lun600_fd_snapshot"
emcpower7s2  auto:cdsdisk   emc_clariion0_502  asyncDG3_fd online               emcpower7c       -  <<<< EMC MirrorView SnapView snapshot "lun602_fd_snapshot"
emcpower8s2  auto:cdsdisk   emc_clariion0_501  asyncDG2_fd online               emcpower8c       -  <<<< EMC MirrorView SnapView snapshot "lun601_fd_snapshot"

 

The above EMC MirrorView devices are associated with the EMC CLARiiON StorageGroup "vcssx065_066".

 

How to view the EMC CLARiiON devices associated with StorageGroup "vcssx065_066"


Figure 1.0



Sample output

 

Note: The IP address for the EMC CLARiiON in this instance is "10.209.64.29"

 

# /opt/Navisphere/bin/naviseccli -h 10.209.64.29 storagegroup -list -gname vcssx065_066 -host

Storage Group Name:    vcssx065_066
Storage Group UID:     24:1D:66:4B:F2:12:DE:11:91:E0:00:60:16:1E:66:AC
HBA/SP Pairs:

  HBA UID                                          SP Name     SPPort
  -------                                          -------     ------
  20:00:00:E0:8B:14:0C:04:21:00:00:E0:8B:14:0C:04   SP A         4
Host name:             vcssx066
  20:00:00:E0:8B:14:0C:04:21:00:00:E0:8B:14:0C:04   SP B         4
Host name:             vcssx066

HLU/ALU Pairs:

  HLU Number     ALU Number
  ----------     ----------
    1               601
    2               602
    3               604
    4               603
    5               605
    6               600

HLU/SLU Pairs:

 HLU No.  SNAP SHOT UID                                     SNAP SHOT NAME
 ------  -----------------------------------------------    --------------
 0       60:06:01:60:3A:31:1F:00:00:58:24:D8:AF:DD:DF:11      lun600_fd_snapshot
 7       60:06:01:60:3A:31:1F:00:6C:6B:2C:E7:AF:DD:DF:11      lun602_fd_snapshot
 8       60:06:01:60:3A:31:1F:00:8A:0C:E1:F5:AF:DD:DF:11      lun601_fd_snapshot

Shareable:             YES
 

Note: The EMC MirrorView SnapView snapshot devices are shown in blod text.

 

Stop eventsource


Due to interoperability issues with EMC PowerPath and the Volume Manager/DMP stack, Veritas recommend that the "eventsource" (vxesd) be disabled prior to the presenting of new devices and the removal of devices.

5.1 SP1 will contain a "vxesd" product enhancement allowing EMC PowerPath and Volume Manager/DMP to safely interact, without the current interoperability issues.

 

# ps -ef | grep vxesd
    root   775     1   0 12:22:24 ?           0:00 /sbin/vxesd
    root 11898 10965   0 12:48:30 pts/1       0:00 grep vxesd

 

How to stop the "vxesd" daemon


# vxddladm stop eventsource

# pgrep vxesd


Steps to unpresent the EMC MirrorView SnapView (cloned) devices

 

Sample output

 

1.]  Ensure all corresponding filesystems are unmounted.

 

2.] Deport the cloned diskgroup images, in this instance "asyncDG1_fd", "asyncDG2_fd" and "asyncDG3_fd"
 

# vxdg deport asyncDG1_fd asyncDG2_fd asyncDG3_fd

 

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

 

4.] Inform Volume Manager that the corresponding luns are to be removed, by running "vxdisk rm "
 

Note: In this instance, the disk access names are " emcpower6s2", " emcpower7s2" and "emcpower8s2"

 

# vxdisk rm emcpower6s2 emcpower7s2 emcpower8s2

 

5.] Display the EMC CLARiiON devices associated with EMC PowerPath, record the CLARiiON lun count.
 

# powermt display class=clariion
CLARiiON logical device count=9
==============================================================================
----- Host Bus Adapters ---------  ------ I/O Paths -----  ------ Stats ------
###  HW Path                       Summary   Total   Dead  IO/Sec Q-IOs Errors
==============================================================================
3072 pci@1e,600000/fibre-channel@3/fp@0,0  optimal       9      0       -     0      0

 

Veritas DMP should report the same LUN count for the EMC CLARiiON luns controlled by EMC PowerPath.

 

# vxdmpadm listenclosure all
ENCLR_NAME        ENCLR_TYPE     ENCLR_SNO      STATUS       ARRAY_TYPE     LUN_COUNT
===================================================================================
disk              Disk           DISKS                CONNECTED    Disk        2
pp_emc_clariion0  PP_EMC_CLARiiON CK200080501031       CONNECTED    A/A         9



Check the UDID values match for the EMC CLARiiON luns
 

Sample output
 

# /opt/Navisphere/bin/naviseccli -h 10.209.64.29 storagegroup -list -gname vcssx065_066 -host | grep snapshot
 0       60:06:01:60:3A:31:1F:00:00:58:24:D8:AF:DD:DF:11      lun600_fd_snapshot
 7       60:06:01:60:3A:31:1F:00:6C:6B:2C:E7:AF:DD:DF:11      lun602_fd_snapshot
 8       60:06:01:60:3A:31:1F:00:8A:0C:E1:F5:AF:DD:DF:11      lun601_fd_snapshot

# powermt display dev=emcpower6c | grep ^Logical
Logical device ID=600601603A311F00005824D8AFDDDF11     <<<<<   lun600_fd_snapshot

# powermt display dev=emcpower7c | grep ^Logical
Logical device ID=600601603A311F006C6B2CE7AFDDDF11     <<<<<   lun602_fd_snapshot

# powermt display dev=emcpower8c | grep ^Logical
Logical device ID=600601603A311F008A0CE1F5AFDDDF11     <<<<<   lun601_fd_snapshot
 

6.] Remove the EMC PowerPath pseudo references.

 

Note: The EMC CLI  "powermt remove dev" command is currently unable to remove multiple EMC PowerPath devices in a single operation.

It is essential that each EMC PowerPath pseudo device be closed individually to ensure that the EMC device is closed correctly.

 

# powermt remove dev=emcpower6c
# powermt remove dev=emcpower7c
# powermt remove dev=emcpower8c

 

Note: The EMC CLARiiON lun count should decrease following the "powermt remove dev=" commands.


# powermt display class=clariion
CLARiiON logical device count=6
==============================================================================
----- Host Bus Adapters ---------  ------ I/O Paths -----  ------ Stats ------
###  HW Path                       Summary   Total   Dead  IO/Sec Q-IOs Errors
==============================================================================
3072 pci@1e,600000/fibre-channel@3/fp@0,0  optimal       6      0       -     0      0

 

In this instance, the EMC CLARiiON lun count has reduced from the previous valu of "9" to "6" as required.

 

 

7.] Update the EMC PowerPath configuration database

 

Note: In this instance, all "3" removed EMC PowerPath pseudo devices must be deleted.
 

Sample output


# powercf -q

Could not validate the entry:
---------------------------------------
emcpower6: user ID = 15000000030
---------------------------------------

removing emcpower6

Could not validate the entry:
---------------------------------------
emcpower7: user ID = 15000000038
---------------------------------------

removing emcpower7

Could not validate the entry:
---------------------------------------
emcpower8: user ID = 15000000040
---------------------------------------

removing emcpower8

 

 

How to deactivate and remove the EMC MirrorView SnapView snapshot with the name of "lun600_fd_snapshot"

 

Sample syntax

 

1.] Deactivate snapshot "lun600_fd_snapshot"


# /opt/Navisphere/bin/naviseccli -h 10.209.64.29 snapview -deactivatesnapshot -snapshotname lun600_fd_snapshot -o


2.] Remove snapshot "lun600_fd_snapshot" from EMC CLARiiON Storage group "vcssx065_066"

# /opt/Navisphere/bin/naviseccli -h 10.209.64.29 storagegroup -removesnapshot -gname vcssx065_066 -snapshotname lun600_fd_snapshot -o


3.] Remove the snapshot name "lun600_fd_snapshot"

# /opt/Navisphere/bin/naviseccli -h 10.209.64.29 snapview -rmsnapshot -snapshotname lun600_fd_snapshot -o

 

 

Additional examples:

 

How to deactivate and remove the EMC MirrorView SnapView snapshot with the name of "lun601_fd_snapshot"

 

Sample syntax



1.] Deactivate and remove snapshot "lun602_fd_snapshot"


# /opt/Navisphere/bin/naviseccli -h 10.209.64.29 snapview -deactivatesnapshot -snapshotname lun602_fd_snapshot -o

# /opt/Navisphere/bin/naviseccli -h 10.209.64.29 storagegroup -removesnapshot -gname vcssx065_066 -snapshotname lun602_fd_snapshot -o

# /opt/Navisphere/bin/naviseccli -h 10.209.64.29 snapview -rmsnapshot -snapshotname lun602_fd_snapshot -o



2.] Deactivate and remove snapshot "lun601_fd_snapshot"

# /opt/Navisphere/bin/naviseccli -h 10.209.64.29 snapview -deactivatesnapshot -snapshotname lun601_fd_snapshot -o

# /opt/Navisphere/bin/naviseccli -h 10.209.64.29 storagegroup -removesnapshot -gname vcssx065_066 -snapshotname lun601_fd_snapshot -o

# /opt/Navisphere/bin/naviseccli -h 10.209.64.29 snapview -rmsnapshot -snapshotname lun601_fd_snapshot -o

 

Once the EMC MirrorView SnapView snapshot's have been deactivated and removed, the related session needs to be stopped.

 

How to stop EMC MirrorView SnapView session with a name of "VCS_fd_session"

 

Sample syntax



# /opt/Navisphere/bin/naviseccli -h 10.209.64.29 snapview -stopsession VCS_fd_session -o

 

 

Revised view of the EMC CLARiiON devices associated with StorageGroup "vcssx065_066"


Figure 2.0

# /opt/Navisphere/bin/naviseccli -h 10.209.64.29 storagegroup -list -gname vcssx065_066 -host

Storage Group Name:    vcssx065_066
Storage Group UID:     24:1D:66:4B:F2:12:DE:11:91:E0:00:60:16:1E:66:AC
HBA/SP Pairs:

  HBA UID                                          SP Name     SPPort
  -------                                          -------     ------
  20:00:00:E0:8B:14:0C:04:21:00:00:E0:8B:14:0C:04   SP A         4
Host name:             vcssx066
  20:00:00:E0:8B:14:0C:04:21:00:00:E0:8B:14:0C:04   SP B         4
Host name:             vcssx066

HLU/ALU Pairs:

  HLU Number     ALU Number
  ----------     ----------
    1               601
    2               602
    3               604
    4               603
    5               605
    6               600
Shareable:             YES


Note: The EMC CLARiiON MirrorView SnapView snapshot devices have now been removed following the above lun removal steps.

 

 

Clean-up Solaris

# cfgadm -alo show_FCP_dev
Ap_Id                          Type         Receptacle   Occupant     Condition
c1                             fc-fabric    connected    configured   unknown
c1::5006016041e02d28,0         disk         connected    configured   unknown
c1::5006016841e0a366,0         disk         connected    configured   unknown   <<<< cfgadm fails to report usable state as the HLU is "0"
c1::5006016841e0a366,1         disk         connected    configured   unknown
c1::5006016841e0a366,2         disk         connected    configured   unknown
c1::5006016841e0a366,3         disk         connected    configured   unknown
c1::5006016841e0a366,4         disk         connected    configured   unknown
c1::5006016841e0a366,5         disk         connected    configured   unknown
c1::5006016841e0a366,6         disk         connected    configured   unknown
c1::5006016841e0a366,7         disk         connected    configured   unusable
c1::5006016841e0a366,8         disk         connected    configured   unusable

c1::50060e8005650921           unavailable  connected    unconfigured failed


Using cfgadm, remove the access paths marked as "unusable" which have an access point of "c1::5006016841e0a366".


# cfgadm -o unusable_FCP_dev -c unconfigure c1::5006016841e0a366

 

As shown below, the "unusable" access paths have been deleted which were associated with access point "c1::5006016841e0a366".


# cfgadm -alo show_FCP_dev
Ap_Id                          Type         Receptacle   Occupant     Condition
c1                             fc-fabric    connected    configured   unknown
c1::5006016041e02d28,0         disk         connected    configured   unknown
c1::5006016841e0a366,0         disk         connected    configured   unknown
c1::5006016841e0a366,1         disk         connected    configured   unknown
c1::5006016841e0a366,2         disk         connected    configured   unknown
c1::5006016841e0a366,3         disk         connected    configured   unknown
c1::5006016841e0a366,4         disk         connected    configured   unknown
c1::5006016841e0a366,5         disk         connected    configured   unknown
c1::5006016841e0a366,6         disk         connected    configured   unknown
c1::50060e8005650921           unavailable  connected    unconfigured failed



Access path "c1::5006016841e0a366,0" will still be reported as the special EMC CLARiiON "LUNZ" device will now appear in place of the removed CLARiiON data disk on device "0" (HLU 0).

 

# ./inq.sol64
Inquiry utility, Version V7.3-1059 (Rev 2.0)      (SIL Version V7.1.2.0 (Edit Level 1059)
Copyright (C) by EMC Corporation, all rights reserved.
For help type inq -h.

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

--------------------------------------------------------------------------------------------
DEVICE                            :VEND    :PROD            :REV   :SER NUM    :CAP(kb)
--------------------------------------------------------------------------------------------
/dev/rdsk/c1t5006016041E02D28d0s2 :DGC     :LUNZ            :0326  :00000000   :      FAILED
/dev/rdsk/c1t5006016841E0A366d0s2 :DGC     :LUNZ            :0326  :00000000   :      FAILED     <<<<  LUNZ
/dev/rdsk/c1t5006016841E0A366d1s2 :DGC     :RAID 5          :0326  :590000BD   :     1048576
/dev/rdsk/c1t5006016841E0A366d2s2 :DGC     :RAID 5          :0326  :5A0000BD   :     1048576
/dev/rdsk/c1t5006016841E0A366d3s2 :DGC     :RAID 5          :0326  :5C0000BE   :     1048576
/dev/rdsk/c1t5006016841E0A366d4s2 :DGC     :RAID 5          :0326  :5B0000BE   :     1048576
/dev/rdsk/c1t5006016841E0A366d5s2 :DGC     :RAID 5          :0326  :5D0000BF   :     1048576
/dev/rdsk/c1t5006016841E0A366d6s2 :DGC     :RAID 5          :0326  :580000BD   :     1048576
/dev/rdsk/c2t0d0s2                :FUJITSU :MAT3073N SUN72G :0602  :050008b01A :    71687369
/dev/rdsk/c2t1d0s2                :FUJITSU :MAT3073N SUN72G :0602  :050024b07L :    71687369
/dev/rdsk/emcpower0c              :DGC     :RAID 5          :0326  :5D0000BF   :     1048576
/dev/rdsk/emcpower1c              :DGC     :RAID 5          :0326  :5B0000BE   :     1048576
/dev/rdsk/emcpower2c              :DGC     :RAID 5          :0326  :5C0000BE   :     1048576
/dev/rdsk/emcpower3c              :DGC     :RAID 5          :0326  :5A0000BD   :     1048576
/dev/rdsk/emcpower4c              :DGC     :RAID 5          :0326  :590000BD   :     1048576
/dev/rdsk/emcpower5c              :DGC     :RAID 5          :0326  :580000BD   :     1048576
/dev/vx/rdmp/disk_0s2             :FUJITSU :MAT3073N SUN72G :0602  :050008b01A :    71687369
/dev/vx/rdmp/disk_1s2             :FUJITSU :MAT3073N SUN72G :0602  :050024b07L :    71687369
/dev/vx/rdmp/emcpower0s2          :DGC     :RAID 5          :0326  :5D0000BF   :     1048576
/dev/vx/rdmp/emcpower1s2          :DGC     :RAID 5          :0326  :5B0000BE   :     1048576
/dev/vx/rdmp/emcpower2s2          :DGC     :RAID 5          :0326  :5C0000BE   :     1048576
/dev/vx/rdmp/emcpower3s2          :DGC     :RAID 5          :0326  :5A0000BD   :     1048576
/dev/vx/rdmp/emcpower4s2          :DGC     :RAID 5          :0326  :590000BD   :     1048576
/dev/vx/rdmp/emcpower5s2          :DGC     :RAID 5          :0326  :580000BD   :     1048576



Important : Ensure the stale O/S device entries are deleted by running "devfsadm -Cvc disk". It is essential that such entries are removed.

 

# devfsadm -Cvc disk
devfsadm[5155]: verbose: removing file: /dev/dsk/c1t5006016841E0A366d7s0
devfsadm[5155]: verbose: removing file: /dev/dsk/c1t5006016841E0A366d7s1
devfsadm[5155]: verbose: removing file: /dev/dsk/c1t5006016841E0A366d7s2
devfsadm[5155]: verbose: removing file: /dev/dsk/c1t5006016841E0A366d7s3
devfsadm[5155]: verbose: removing file: /dev/dsk/c1t5006016841E0A366d7s4
devfsadm[5155]: verbose: removing file: /dev/dsk/c1t5006016841E0A366d7s5
devfsadm[5155]: verbose: removing file: /dev/dsk/c1t5006016841E0A366d7s6
devfsadm[5155]: verbose: removing file: /dev/dsk/c1t5006016841E0A366d7s7
devfsadm[5155]: verbose: removing file: /dev/dsk/c1t5006016841E0A366d8s0
devfsadm[5155]: verbose: removing file: /dev/dsk/c1t5006016841E0A366d8s1
devfsadm[5155]: verbose: removing file: /dev/dsk/c1t5006016841E0A366d8s2
devfsadm[5155]: verbose: removing file: /dev/dsk/c1t5006016841E0A366d8s3
devfsadm[5155]: verbose: removing file: /dev/dsk/c1t5006016841E0A366d8s4
devfsadm[5155]: verbose: removing file: /dev/dsk/c1t5006016841E0A366d8s5
devfsadm[5155]: verbose: removing file: /dev/dsk/c1t5006016841E0A366d8s6
devfsadm[5155]: verbose: removing file: /dev/dsk/c1t5006016841E0A366d8s7
devfsadm[5155]: verbose: removing file: /dev/rdsk/c1t5006016841E0A366d7s0
devfsadm[5155]: verbose: removing file: /dev/rdsk/c1t5006016841E0A366d7s1
devfsadm[5155]: verbose: removing file: /dev/rdsk/c1t5006016841E0A366d7s2
devfsadm[5155]: verbose: removing file: /dev/rdsk/c1t5006016841E0A366d7s3
devfsadm[5155]: verbose: removing file: /dev/rdsk/c1t5006016841E0A366d7s4
devfsadm[5155]: verbose: removing file: /dev/rdsk/c1t5006016841E0A366d7s5
devfsadm[5155]: verbose: removing file: /dev/rdsk/c1t5006016841E0A366d7s6
devfsadm[5155]: verbose: removing file: /dev/rdsk/c1t5006016841E0A366d7s7
devfsadm[5155]: verbose: removing file: /dev/rdsk/c1t5006016841E0A366d8s0
devfsadm[5155]: verbose: removing file: /dev/rdsk/c1t5006016841E0A366d8s1
devfsadm[5155]: verbose: removing file: /dev/rdsk/c1t5006016841E0A366d8s2
devfsadm[5155]: verbose: removing file: /dev/rdsk/c1t5006016841E0A366d8s3
devfsadm[5155]: verbose: removing file: /dev/rdsk/c1t5006016841E0A366d8s4
devfsadm[5155]: verbose: removing file: /dev/rdsk/c1t5006016841E0A366d8s5
devfsadm[5155]: verbose: removing file: /dev/rdsk/c1t5006016841E0A366d8s6
devfsadm[5155]: verbose: removing file: /dev/rdsk/c1t5006016841E0A366d8s7

 

Refresh EMC PowerPath

 

# yes | powermt restore dev=all

# /etc/powermt check dev=all class=clariion force

# /etc/powercf -q

# /etc/powermt config

# /etc/powermt save
 

Note: Initially when the EMC MirrorView SnapView CLARiiON luns were presented the LUN count was "9", following the removal exercise it has now been reduced to "6" as required.

 

# powermt display
Symmetrix logical device count=0
CLARiiON logical device count=6   <<<<< was "9"
Hitachi logical device count=0
Invista logical device count=0
HP xp logical device count=0
Ess logical device count=0
HP HSx logical device count=0
==============================================================================
----- Host Bus Adapters ---------  ------ I/O Paths -----  ------ Stats ------
###  HW Path                       Summary   Total   Dead  IO/Sec Q-IOs Errors
==============================================================================
3072 pci@1e,600000/fibre-channel@3/fp@0,0  optimal       6      0       -     0      0

 

Update VxVM and DMP configuration details since the LUN removal
 

Ensure VxVM removes the disk access names records for the recently removed luns by running "vxdisk scandisks", followed by "vxdisk -eo alldgs list".

 

# vxdisk scandisks


# vxdisk -eo alldgs list

DEVICE       TYPE           DISK        GROUP        STATUS               OS_NATIVE_NAME   ATTR
disk_0       auto:sliced    c2t0d0       rootdg      online               c2t0d0s2         -
disk_1       auto:sliced    c2t0d0-s0    rootdg2     online               c2t1d0s2         -
emcpower0s2  auto           -            -           error                emcpower0c       -
emcpower1s2  auto           -            -           error                emcpower1c       -
emcpower2s2  auto           -            -           error                emcpower2c       -
emcpower3s2  auto           -            -           error                emcpower3c       -
emcpower4s2  auto           -            -           error                emcpower4c       -
emcpower5s2  auto           -            -           error                emcpower5c       -

 

As shown above, the previously configured EMC PowerPath luns, emcpower6s2, emcpower7s2 and emcpower8s2 are no longer listed by VxVM CLI command "vxdisk -eo alldgs list".

 

If the /etc/vx/disk.info file exists, it will contain the removed disk entries with a "0xfffffff" state.

 

# more /etc/vx/disk.info
DGC%5FRAID%205%5FCK200080501031%5F600601603A311F008A0CE1F5AFDDDF11 emcpower8 0xffffffff 0x4 emcpower8 PP_EMC_CLARiiON CK200080501031
DGC%5FRAID%205%5FCK200080501031%5F600601600F311F000C005487D2AADF11 emcpower3 0x5280030 0x4 emcpower3 PP_EMC_CLARiiON CK200080501031
DGC%5FRAID%205%5FCK200080501031%5F600601600F311F00709F849ED2AADF11 emcpower0 0x5280018 0x4 emcpower0 PP_EMC_CLARiiON CK200080501031
FUJITSU%5FMAT3073N%20SUN72G%5FDISKS%5F000508B01ARL%20%20%20%20AAN0P5201ARL c2t0d0 0x5280000 0x2 disk_0 Disk DISKS
DGC%5FRAID%205%5FCK200080501031%5F600601603A311F00005824D8AFDDDF11 emcpower6 0xffffffff 0x4 emcpower6 PP_EMC_CLARiiON CK200080501031
DGC%5FRAID%205%5FCK200080501031%5F600601600F311F002DFA267CD2AADF11 emcpower4 0x5280028 0x4 emcpower4 PP_EMC_CLARiiON CK200080501031
DGC%5FRAID%205%5FCK200080501031%5F600601600F311F002CFA267CD2AADF11 emcpower5 0x5280010 0x4 emcpower5 PP_EMC_CLARiiON CK200080501031
FUJITSU%5FMAT3073N%20SUN72G%5FDISKS%5F000524B07L70%20%20%20%20AAN0P5607L70 c2t1d0 0x5280050 0x2 disk_1 Disk DISKS
DGC%5FRAID%205%5FCK200080501031%5F600601603A311F006C6B2CE7AFDDDF11 emcpower7 0xffffffff 0x4 emcpower7 PP_EMC_CLARiiON CK200080501031
DGC%5FRAID%205%5FCK200080501031%5F600601600F311F006439258ED2AADF11 emcpower1 0x5280020 0x4 emcpower1 PP_EMC_CLARiiON CK200080501031
DGC%5FRAID%205%5FCK200080501031%5F600601600F311F00283D7F94D2AADF11 emcpower2 0x5280008 0x4 emcpower2 PP_EMC_CLARiiON CK200080501031

 

To refresh the /etc/vx/disk.info contents, type "vxddladm assign names".

 

# vxddladm assign names

 

Note: The "vxddladm assign names" command was introduced in 5.0 MP3 onwards.


# more /etc/vx/disk.info

FUJITSU%5FMAT3073N%20SUN72G%5FDISKS%5F000508B01ARL%20%20%20%20AAN0P5201ARL c2t0d0 0x5280000 0x2 disk_0 Disk DISKS
DGC%5FRAID%205%5FCK200080501031%5F600601600F311F000C005487D2AADF11 emcpower3 0x5280030 0x4 emcpower3 PP_EMC_CLARiiON CK200080501031
DGC%5FRAID%205%5FCK200080501031%5F600601600F311F002DFA267CD2AADF11 emcpower4 0x5280028 0x4 emcpower4 PP_EMC_CLARiiON CK200080501031
DGC%5FRAID%205%5FCK200080501031%5F600601600F311F006439258ED2AADF11 emcpower1 0x5280020 0x4 emcpower1 PP_EMC_CLARiiON CK200080501031
DGC%5FRAID%205%5FCK200080501031%5F600601600F311F00709F849ED2AADF11 emcpower0 0x5280018 0x4 emcpower0 PP_EMC_CLARiiON CK200080501031
DGC%5FRAID%205%5FCK200080501031%5F600601600F311F002CFA267CD2AADF11 emcpower5 0x5280010 0x4 emcpower5 PP_EMC_CLARiiON CK200080501031
FUJITSU%5FMAT3073N%20SUN72G%5FDISKS%5F000524B07L70%20%20%20%20AAN0P5607L70 c2t1d0 0x5280050 0x2 disk_1 Disk DISKS
DGC%5FRAID%205%5FCK200080501031%5F600601600F311F00283D7F94D2AADF11 emcpower2 0x5280008 0x4 emcpower2 PP_EMC_CLARiiON CK200080501031

 

# vxdmpadm listenclosure all
ENCLR_NAME        ENCLR_TYPE     ENCLR_SNO      STATUS       ARRAY_TYPE     LUN_COUNT
===================================================================================
disk              Disk           DISKS                CONNECTED    Disk        2
pp_emc_clariion0  PP_EMC_CLARiiON CK200080501031       CONNECTED    A/A         6

 

Note: DMP reflects the reduction in the EMC CLARiiON LUN count to "6" from previous value of "9".

 

Issue/Introduction

How to deactivate and remove an EMC MirrorView SnapView snapshot from a Solaris server using EMC PowerPath