How to remove EMC DMX devices from a Solaris server using EMC PowerPath

book

Article ID: 100037803

calendar_today

Updated On:

Description

Description

 

This document attempts to explain the essential steps required to unpresent existing EMC storage devices controlled by EMC PowerPath.


The following EMC DMX SYMDEV "00E9" device will be unpresented (masked) from a Solaris server (ie serverA) using EMC PowerPath as the multipathing solution.
In this instance the EMC Symmetrix ID(SID) is "000290300822" (SID 822 for short) connected to wwn "200000017301bbeb"


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 "SYMsymcli" package must be installed and licensed.
# symmask discover hba

Symmetrix ID          : 000290300822
Device Masking Status : Success

  Identifier        Type   User-generated Name
  ----------------  -----  ---------------------------------
  200000017301bbeb  Fibre  serverA/200000017301bbeb

Symmetrix ID          : 000290301414
Device Masking Status : Success

  Identifier        Type   User-generated Name
  ----------------  -----  ---------------------------------
  200000017301bbeb  Fibre  serverA/200000017301bbeb



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


Identifier        Type   Adapter           Physical Device Path      Dir:P
----------------  -----  ----------------  ------------------------  -----
200000017301bbeb  Fibre  @1e,600000/SUNW*  c1t5006048C5368E580d0s2*  01C:0
                                           c1t5006048C5368E5A0d0s2*  01C:1
                                           c1t5006048C5368E58Fd0s2*  16C:0
                                           c1t5006048C5368E5AFd0s2*  16C:1
                                           c1t5006048C53697980d0s2*  01C:0


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         7       713




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


To refresh the Physical Device Name details, run "symcfg discover"
# symcfg -sid 822 discover

Attempting discovery of Symmetrix 000290300822

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



In this instance, using the Symmetrix ID "822" and the wwn of the server concerned ( 200000017301BBEB), type:
# symmaskdb -sid 822 list devs -wwn 200000017301bbeb

Symmetrix ID        : 000290300822

Originator Port wwn : 200000017301bbeb
User-generated Name : serverA/200000017301bbeb

Sym Dev                                               LUN
Name    Dir:P  Physical Device Name     VBUS  TID  SYMM HOST  Attr  Cap(MB)
------  -----  -----------------------  ----  ---  ---- ----  ----  -------
00E9     1C:0  rdmp/emcpower1s2            0    0    12    0           2158




The LUN Symm reference can be converted from HEX to decimal to work out what the Solaris target would be, using:
In this instance "0x12" (HEX) translates to a decimal value of "18"

# printf "%#d\n"  0x12
18

Note: At this time a single device is presented via SID "822" to the Solaris server.
This can be confirmed by running vxdmpadm CLI command "vxdmpadm listenclosure all"
# vxdmpadm listenclosure all
ENCLR_NAME        ENCLR_TYPE     ENCLR_SNO      STATUS       ARRAY_TYPE     LUN_COUNT
=======================================================================================
disk              Disk           DISKS                CONNECTED    Disk        1
pp_emc0           PP_EMC         000290301414         CONNECTED    A/A         1
pp_emc1           PP_EMC         000290300822         CONNECTED    A/A         1     <<<< Concerned with this enclosure





EMC inq.sol64 utility

The free "inq.sol64" utility from EMC can be used to extract disk/HBA related content.
# inq.sol64 -mapinfo
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.


---------------------------------------------------
HBA name:           JNI Corporation-FCX-6562-L-0
host WWN:           100000017301BBEB
vendor name:        JNI Corporation
model:              FCX-6562-L
firmware version:   4 ENG-2423
driver version:     SunFC JNI FCA v20041215-1.44
serial number:      113643
vendor code:        0x173
HBA type:           Fibre Channel
port count:         1

port number:                 1
    port WWN:                     200000017301BBEB
    Port OS name:                 /dev/cfg/c1
    port type:                    NPORT
    port speed:                   UNKNOWN
    supported speed:              2GBIT
    port state:                   ONLINE
    port FCID:                    0x10100
    port supported COS:           0x00000008
    port supported FC4 types:     0x0000000000000000000000000000000000000000000000000000000000000000
    port active FC4 types:        0x0000012000000000000000000000000000000000000000000000000000000000
    max frame size:               2112


--------------------------------------------------------------------------------------------------------------------------------------------------------
RAW                                             ARRAY
DEVICE NAME         :VENDOR   :PROD     :REV   :SERIAL #     :CAP        :BUS  :TGT  :LUN  :HBA PORT WWN      :TARGET PORT WWN   :PARENT DEVICE
--------------------------------------------------------------------------------------------------------------------------------------------------------
/dev/rdsk/c1t500601603021C60Ed0s2:DGC     :LUNZ      :0226 :CK200053300424  : FAILED   :1    :17357:0    :200000017301bbeb  :500601603021c60e :N/A

/dev/rdsk/c1t500601613021C60Ed0s2:DGC     :LUNZ      :0226 :CK200053300424  : FAILED   :1    :27357:0    :200000017301bbeb  :500601613021c60e :N/A

/dev/rdsk/c1t500601683021C60Ed0s2:DGC     :LUNZ      :0226 :CK200053300424  : FAILED   :1    :31821:0    :200000017301bbeb  :500601683021c60e :N/A

/dev/rdsk/c1t500601693021C60Ed0s2:DGC     :LUNZ      :0226 :CK200053300424  : FAILED   :1    :41821:0    :200000017301bbeb  :500601693021c60e :N/A

/dev/rdsk/c1t5006048C5368E5AFd0s2:EMC     :SYMMETRIX :5773 :000290300822    :    2880  :1    :0    :0    :200000017301bbeb  :5006048c5368e5af :N/A

/dev/rdsk/c1t5006048C5368E5A0d0s2:EMC     :SYMMETRIX :5773 :000290300822    :    2880  :1    :0    :0    :200000017301bbeb  :5006048c5368e5a0 :N/A

/dev/rdsk/c1t5006048C5368E58Fd0s2:EMC     :SYMMETRIX :5773 :000290300822    :    2880  :1    :0    :0    :200000017301bbeb  :5006048c5368e58f :N/A

/dev/rdsk/c1t5006048C5368E580d0s2:EMC     :SYMMETRIX :5773 :000290300822    :    2880  :1    :0    :0    :200000017301bbeb  :5006048c5368e580 :N/A

/dev/rdsk/c1t5006048C5368E580d18s2:EMC     :SYMMETRIX :5773 :000290300822    : 2209920  :1    :0    :18   :200000017301bbeb  :5006048c5368e580 :/dev/rdsk/emcpower1c
/dev/rdsk/c1t5006048C53697980d0s2:EMC     :SYMMETRIX :5773 :000290301414    :    2880  :1    :0    :0    :200000017301bbeb  :5006048c53697980 :N/A

/dev/rdsk/c1t5006048C53697980d215s2:EMC     :SYMMETRIX :5773 :000290301414    :77760000  :1    :0    :215  :200000017301bbeb  :5006048c53697980 :/dev/rdsk/emcpower0c
/dev/rdsk/c2t0d0s2  :SEAGATE :ST373307L :0707 :N/A             :71687369  :2    :0    :0    :N/A               :N/A              :/dev/vx/rdmp/disk_0s2
/dev/rdsk/c2t1d0s2  :SEAGATE :ST373307L :0707 :N/A             :71687369  :2    :1    :0    :N/A               :N/A              :/dev/vx/rdmp/disk_0s2
/dev/rdsk/c2t2d0s2  :SEAGATE :ST373307L :0707 :N/A             :71687369  :2    :2    :0    :N/A               :N/A              :/dev/vx/rdmp/disk_0s2
/dev/rdsk/emcpower0c:EMC     :SYMMETRIX :5773 :000290301414    :77760000  :0    :0    :0    :N/A               :N/A              :/dev/vx/rdmp/emcpower0s2
/dev/rdsk/emcpower1c:EMC     :SYMMETRIX :5773 :000290300822    : 2209920  :0    :0    :0    :N/A               :N/A              :/dev/vx/rdmp/emcpower1s2
/dev/vx/rdmp/disk_0s2:SEAGATE :ST373307L :0707 :N/A             :71687369  :0    :0    :0    :N/A               :N/A              :N/A
/dev/vx/rdmp/emcpower0s2:EMC     :SYMMETRIX :5773 :000290301414    :77760000  :0    :0    :0    :N/A               :N/A              :N/A
/dev/vx/rdmp/emcpower1s2:EMC     :SYMMETRIX :5773 :000290300822    : 2209920  :0    :0    :0    :N/A               :N/A              :N/A



Various views:


Display EMC Symmetrix devices with additional WWN content:

# ./inq.sol64 -no_dots -sym_wwn
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.



----------------------------------------------------------------------------------------------
Symmetrix Device                     Symm Serial #  Device #  WWN
----------------------------------------------------------------------------------------------
/dev/rdsk/c1t5006048C5368E5AFd0s2    000290300822   00010     60060480000290300822533030303130
/dev/rdsk/c1t5006048C5368E5A0d0s2    000290300822   00010     60060480000290300822533030303130
/dev/rdsk/c1t5006048C5368E58Fd0s2    000290300822   00010     60060480000290300822533030303130
/dev/rdsk/c1t5006048C5368E580d0s2    000290300822   00010     60060480000290300822533030303130
/dev/rdsk/c1t5006048C5368E580d18s2   000290300822   000E9     60060480000290300822533030304539
/dev/rdsk/c1t5006048C53697980d0s2    000290301414   00010     60060480000290301414533030303130
/dev/rdsk/c1t5006048C53697980d215s2  000290301414   000C6     60060480000290301414533030304336
/dev/rdsk/emcpower0c                 000290301414   000C6     60060480000290301414533030304336
/dev/rdsk/emcpower1c                 000290300822   000E9     60060480000290300822533030304539
/dev/vx/rdmp/emcpower0s2             000290301414   000C6     60060480000290301414533030304336
/dev/vx/rdmp/emcpower1s2             000290300822   000E9     60060480000290300822533030304539




Display only EMC devices



# ./inq.sol64 -no_dots  -f_emc
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/c1t5006048C5368E5AFd0s2   :EMC     :SYMMETRIX       :5773  :2200010000 :        2880
/dev/rdsk/c1t5006048C5368E5A0d0s2   :EMC     :SYMMETRIX       :5773  :2200010000 :        2880
/dev/rdsk/c1t5006048C5368E58Fd0s2   :EMC     :SYMMETRIX       :5773  :2200010000 :        2880
/dev/rdsk/c1t5006048C5368E580d0s2   :EMC     :SYMMETRIX       :5773  :2200010000 :        2880
/dev/rdsk/c1t5006048C5368E580d18s2  :EMC     :SYMMETRIX       :5773  :22000e9000 :     2209920
/dev/rdsk/c1t5006048C53697980d0s2   :EMC     :SYMMETRIX       :5773  :1400010330 :        2880
/dev/rdsk/c1t5006048C53697980d215s2 :EMC     :SYMMETRIX       :5773  :14000c6330 :    77760000
/dev/rdsk/emcpower0c                :EMC     :SYMMETRIX       :5773  :14000c6330 :    77760000
/dev/rdsk/emcpower1c                :EMC     :SYMMETRIX       :5773  :22000e9000 :     2209920
/dev/vx/rdmp/emcpower0s2            :EMC     :SYMMETRIX       :5773  :14000c6330 :    77760000
/dev/vx/rdmp/emcpower1s2            :EMC     :SYMMETRIX       :5773  :22000e9000 :     2209920






Lun removal steps:


Prior to the removal of the disk from the server.
 

1.] Ensure all corresponding filesystems are unmounted.

2.] Deport related Volume Manager diskgroups related to the EMC CLARiiON storage to be removed.
# vxdg deport

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 "
# vxdisk -eo alldgs list
DEVICE       TYPE           DISK        GROUP        STATUS               OS_NATIVE_NAME   ATTR
disk_0       auto:none      -            -           online invalid       c2t1d0s2         -
emcpower0s2  auto:cdsdisk   -            -           online               emcpower0c       -
emcpower1s2  auto:cdsdisk   -            -           online               emcpower1c       -   <<< LUN to be removed from the server.



In this instance, EMC SYMDEV "00E9" relates to Veritas Disk Access Name "emcpower1s2", as confirmed by running:
# powermt display dev=emcpower1c
Pseudo name=emcpower1a
Symmetrix ID=000290300822
Logical device ID=00E9
state=alive; policy=SymmOpt; priority=0; queued-IOs=0
==============================================================================
---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---
###  HW Path                I/O Paths    Interf.   Mode    State  Q-IOs Errors
==============================================================================
3073 pci@1e,600000/SUNW,jfca@2/fp@0,0 c1t5006048C5368E580d18s0 FA  1cA   active  alive      0      0


# vxdisk rm emcpower1s2




5.] Mark the LUN for removal within the EMC PowerPath database.
Note: The EMC Symmetrix(DMX) LUN count is currently "2".
#  /etc/powermt display class=symm
Symmetrix logical device count=2
==============================================================================
----- Host Bus Adapters ---------  ------ I/O Paths -----  ------ Stats ------
###  HW Path                       Summary   Total   Dead  IO/Sec Q-IOs Errors
==============================================================================
3073 pci@1e,600000/SUNW,jfca@2/fp@0,0  optimal       2      0       -     0      0



Note: It is critical that the EMC Pseudo names are specified separately, otherwise, the EMC "powercf -q" command will fail to delete the removed disk entries from the EMC PowerPath configuration.
 

# powermt remove dev=emcpower1c


Refresh the EMC PowerPath configuration.
# powercf -q
Could not validate the entry:
---------------------------------------
emcpower1: user ID = 12500000008
---------------------------------------

removing emcpower1

 


6.] Mask the LUN using the EMC SYMCLI interface
# symmaskdb -sid 822 list devs -wwn 200000017301bbeb
Symmetrix ID        : 000290300822

Originator Port wwn : 200000017301bbeb
User-generated Name : serverA/200000017301bbeb

Sym Dev                                               LUN
Name    Dir:P  Physical Device Name     VBUS  TID  SYMM HOST  Attr  Cap(MB)
------  -----  -----------------------  ----  ---  ---- ----  ----  -------
00E9     1C:0  rdmp/emc0_00e9s2            0    0    12    0           2158



The LUN Symm reference can be converted from HEX to decimal to work out what the Solaris target would be, using:

In this instance "0x12" (HEX) translates to a decimal value of "18"
# printf "%#d\n"  0x12
18


The decimal value of "18" refers to the Solaris target, ie c#t#d18s2



EMC LUN Removal syntax:


# /opt/emc/SYMCLI/V6.5.1/bin/symmask -sid 822 -wwn 200000017301bbeb remove devs 00e9 -dir 1c -p 0

Note: In this instance, SYMDEV "00E9" has only a single path.

# symmaskdb -sid 822 list devs -wwn 200000017301bbeb

Symmetrix ID        : 000290300822

Originator Port wwn : 200000017301bbeb
User-generated Name : serverA/200000017301bbeb

  No Devices were found for that WWN






Refresh and update the Symmask Database and discovery the recently provisioned storage



# symmask -sid 822 refresh -noprompt

Symmetrix FA 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.] Refresh the Solaris leadville stack with the Storage activity events.
# cfgadm -alo show_FCP_dev
Ap_Id                          Type         Receptacle   Occupant     Condition
c1                             fc-fabric    connected    configured   unknown
c1::200000017301bbdf           unknown      connected    unconfigured unknown
c1::210000e08b8129fa           unknown      connected    unconfigured unknown
c1::500601603021c60e,0         disk         connected    configured   unknown
c1::500601613021c60e,0         disk         connected    configured   unknown
c1::500601683021c60e,0         disk         connected    configured   unknown
c1::500601693021c60e,0         disk         connected    configured   unknown
c1::5006048c5368e580,0         disk         connected    configured   unknown
c1::5006048c5368e580,18        disk         connected    configured   unusable   <<<<<< access point/path to be removed
c1::5006048c5368e58f,0         disk         connected    configured   unknown
c1::5006048c5368e5a0,0         disk         connected    configured   unknown
c1::5006048c5368e5af,0         disk         connected    configured   unknown
c1::5006048c53697980,0         disk         connected    configured   unknown
c1::5006048c53697980,215       disk         connected    configured   unknown




Note: In this instance, the disk to be removed only had a single path to the LUN.


# accesspaths=`cfgadm -alo show_FCP_dev | grep "unusable" | awk -F"," '{ print $1}' | sort |uniq | tr -s "\n" " "`

# echo $accesspaths
c1::5006048c5368e580



# /usr/sbin/cfgadm -o unusable_FCP_dev -c unconfigure $accesspaths

or



# cfgadm -o unusable_FCP_dev -c unconfigure c1::5006048c5368e580


Critical: If either state is reported, correct the "cfgadm" output prior to presenting the new devices

# cfgadm -alo show_FCP_dev | egrep 'failing|unusable'


Revised output:


# cfgadm -alo show_FCP_dev
Ap_Id                          Type         Receptacle   Occupant     Condition
c1                             fc-fabric    connected    configured   unknown
c1::200000017301bbdf           unknown      connected    unconfigured unknown
c1::210000e08b8129fa           unknown      connected    unconfigured unknown
c1::500601603021c60e,0         disk         connected    configured   unknown
c1::500601613021c60e,0         disk         connected    configured   unknown
c1::500601683021c60e,0         disk         connected    configured   unknown
c1::500601693021c60e,0         disk         connected    configured   unknown
c1::5006048c5368e580,0         disk         connected    configured   unknown
c1::5006048c5368e58f,0         disk         connected    configured   unknown
c1::5006048c5368e5a0,0         disk         connected    configured   unknown
c1::5006048c5368e5af,0         disk         connected    configured   unknown
c1::5006048c53697980,0         disk         connected    configured   unknown
c1::5006048c53697980,215       disk         connected    configured   unknown



8.] Clean-up the Solaris device tree:

# /usr/sbin/devfsadm -Cvc disk


9.] Refresh the EMC PowerPath database

# powercf -q
# powermt config
# powermt save


# powermt display
Symmetrix logical device count=1
CLARiiON logical device count=0
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
==============================================================================
3073 pci@1e,600000/SUNW,jfca@2/fp@0,0  optimal       1      0       -     0      0



Note: The EMC PowerPath lun count has been reduced to "1" from "2".




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


If not running VxVM 5.1 SP1 upwards, the /etc/vx/array.info file contents can be refreshed as follows:
 

# rm /etc/vx/array.info


Note: If Veritas Cluster Server (VCS) or other clustering software is configured, ensure ServiceGroup are Frozen to prevent monitoring timeouts.

 



# vxconfigd -k
V-5-1-12104 vxvm:vxconfigd: Warning: File /etc/vx/array.info does not exist.
This file will be generated when switching to ENABLED mode.

V-5-1-12104 vxvm:vxconfigd: Warning: File /etc/vx/array.info does not exist.
This file will be generated when switching to ENABLED mode.

V-5-1-12104 vxvm:vxconfigd: Warning: File /etc/vx/array.info does not exist.
This file will be generated when switching to ENABLED mode.

V-5-1-11887 vxvm:vxconfigd: NOTICE: Generating /etc/vx/array.info



# more /etc/vx/array.info
DISKS
disk
0
Disk
000290301414
pp_emc0
0
PP_EMC




Process complete.
 

 


# vxdisk scandisks


# vxdisk -eo alldgs list
DEVICE       TYPE           DISK        GROUP        STATUS               OS_NATIVE_NAME   ATTR
disk_0       auto:none      -            -           online invalid       c2t1d0s2         -
emcpower0s2  auto:cdsdisk   -            -           online               emcpower0c       -



Note: Veritas disk access name "emcpower1s2" is no longer presented by VxVM.


"Data Corruption Protection Activated (DCPA)"

 
Veritas introduced a new feature in 5.0 MP3 onwards called "Data Corruption Prevention Activity" (DCPA) feature which basically puts a bubble around each DMP device.

The Data Corruption Prevention Activity (DCPA) feature will assist with safeguarding your data.


The data corruption protection feature actually works to prevent corruption and is a proactive message, rather than a warning about specific corruption !


Using the bubble protector technology surrounding all the existing DMP nodenames, the product prevents other paths merging with it from another physical device. This dramatically helps to reduce the chances of data corruption, when the customer fails to perform the correct and essential steps surrounding the complex lun removal and storage provisioning process.

Prior to 5.0 MP3 it is very difficult to conclude if a step during the lun removal process failed or was accidentally missed.

 

Critical: If you encounter the following messages, please contact Veritas Support before preceeding.

 

VxVM vxdisk ERROR V-5-1-14519 Data Corruption Protection Activated - User Corrective Action Needed
VxVM vxdisk INFO V-5-1-14521 To recover, first ensure that the OS device tree is up to date (requires OS specific commands).


 

Note: The DCPA feature was released in 5.0 MP3 onwards on all the UNIX flavors apart from HP-UX (where it was rebranded as 5.0.1).



How to refresh the /etc/vx/disk.info file contents
 

Note: The value of "0xffffffff" states that the device has been marked for removal.


# more /etc/vx/disk.info
SEAGATE%5FST373307LSUN72G%5FDISKS%5F30353033423959314D320000 c2t1d0 0x4800000 0x2 disk_0 Disk DISKS
EMC%5FSYMMETRIX%5F000290301414%5F140C6330 emcpower0 0x4800008 0x4 emcpower0 PP_EMC 000290301414
EMC%5FSYMMETRIX%5F000290300822%5F60060480000290300822533030304539 emcpower1 0xffffffff 0x4 emcpower1 PP_EMC 000290300822



Note: As no "0xffffffff" entries are reported, the /etc/vx/disk.info file has been updated as required.


# vxddladm assign names


# more /etc/vx/disk.info

SEAGATE%5FST373307LSUN72G%5FDISKS%5F30353033423959314D320000 c2t1d0 0x4800000 0x2 disk_0 Disk DISKS
EMC%5FSYMMETRIX%5F000290301414%5F140C6330 emcpower0 0x4800008 0x4 emcpower0 PP_EMC 000290301414



# vxdmpadm listenclosure all
ENCLR_NAME        ENCLR_TYPE     ENCLR_SNO      STATUS       ARRAY_TYPE     LUN_COUNT
=======================================================================================
disk              Disk           DISKS                CONNECTED    Disk        1
pp_emc0           PP_EMC         000290301414         CONNECTED    A/A         1




How to refresh the /etc/vx/array.info file contents


As the enclosure will no longer be presented to the server, it is recommended to refresh the /etc/vx/array.info file contents.


# more /etc/vx/array.info
DISKS
disk
0
Disk
CK200053300424
emc_clariion0
0
EMC_CLARiiON
000290300822
emc0
0
EMC
000290301414
pp_emc0
0
PP_EMC
000290300822
pp_emc1
0
PP_EMC

 

Note: VxVM 5.1 SP1 introduces a new command option with "vxddladm" to refresh both the /etc/vx/array.info and /etc/vx/disk.info files ( vxddladm -c assign names ). Removing  the need to recycle vxconfigd.


# vxddladm -c assign names


Revised /etc/vx/array.info file details


# more /etc/vx/array.info

DISKS
disk
0
Disk
000290301414
pp_emc0
0
PP_EMC

 

Stop eventsource daemon


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 contains 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

 

Issue/Introduction

How to remove EMC DMX devices from a Solaris server using EMC PowerPath