Veritas Volume Manager (VxVM) 5.0 MP4 (Linux) is not reporting EMC Symmetrix luns under the DMP "emc" enclosure when using PureDisk on SLES

Article: 100008172
Last Published: 2014-01-02
Ratings: 0 0
Product(s): InfoScale & Storage Foundation

Problem


Veritas Volume Manager (VxVM) is not reporting the EMC Symmetrix devices although detected by the O/S. The EMC luns are displayed with an index of "disk_#" by the VxVM CLI command "vxdisk list".

 
# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
disk_0       auto            -            -            error
disk_1       auto            -            -            error
disk_2       auto            -            -            error
disk_3       auto            -            -            error
disk_4       auto            -            -            error
disk_5       auto            -            -            error
disk_6       auto            -            -            error
disk_7       auto            -            -            error
disk_8       auto            -            -            error
disk_9       auto            -            -            error
eva4k6k0_0   auto:sliced     -            -            online
eva4k6k0_1   auto:sliced     -            -            online
eva4k6k0_2   auto:sliced     -            -            online
eva4k6k0_3   auto:sliced     -            -            online
eva4k6k0_4   auto:sliced     -            -            online
eva4k6k0_5   auto:sliced     sdj          PDDG2        online
eva4k6k0_6   auto:sliced     -            -            online
eva4k6k0_7   auto:sliced     -            -            online
eva4k6k0_8   auto:sliced     -            -            online
eva4k6k0_9   auto:sliced     -            -            online
sda          auto:none       -            -            online invalid
 

The EMC luns are seen by the OS as confirmed by the third party "lsscsi" utility.  However, they are claimed by the generic DMP "disk" enclosure.

Sample output

       # lsscsi |grep SYMM
                [0:0:1:0]    disk    EMC      SYMMETRIX        5874  /dev/sdq
                [0:0:1:1]    disk    EMC      SYMMETRIX        5874  /dev/sdr
                [0:0:1:2]    disk    EMC      SYMMETRIX        5874  /dev/sds
                [0:0:1:3]    disk    EMC      SYMMETRIX        5874  /dev/sdt
                [0:0:1:4]    disk    EMC      SYMMETRIX        5874  /dev/sdu
                [0:0:1:5]    disk    EMC      SYMMETRIX        5874  /dev/sdv
                [0:0:1:6]    disk    EMC      SYMMETRIX        5874  /dev/sdw
                [0:0:1:7]    disk    EMC      SYMMETRIX        5874  /dev/sdx
                [0:0:1:8]    disk    EMC      SYMMETRIX        5874  /dev/sdy
                [0:0:1:9]    disk    EMC      SYMMETRIX        5874  /dev/sdab
                [1:0:2:0]    disk    EMC      SYMMETRIX        5874  /dev/sdap
                [1:0:2:1]    disk    EMC      SYMMETRIX        5874  /dev/sdaq
                [1:0:2:2]    disk    EMC      SYMMETRIX        5874  /dev/sdar
                [1:0:2:3]    disk    EMC      SYMMETRIX        5874  /dev/sdas
                [1:0:2:4]    disk    EMC      SYMMETRIX        5874  /dev/sdat
                [1:0:2:5]    disk    EMC      SYMMETRIX        5874  /dev/sdau
                [1:0:2:6]    disk    EMC      SYMMETRIX        5874  /dev/sdav
                [1:0:2:7]    disk    EMC      SYMMETRIX        5874  /dev/sdaw
                [1:0:2:8]    disk    EMC      SYMMETRIX        5874  /dev/sdax
                [1:0:2:9]    disk    EMC      SYMMETRIX        5874  /dev/sday


# vxdmpadm  listenclosure all
ENCLR_NAME        ENCLR_TYPE     ENCLR_SNO      STATUS       ARRAY_TYPE LUN_COUNT
===================================================================================
disk              Disk           DISKS                CONNECTED    Disk 11
eva4k6k0          EVA4K6K        50001FE1500C03F0     CONNECTED    ALUA 10
 

The EMC ASL "libvxemc.so" is not listed with the CLI command "vxddladm listversion". As a result, the EMC Symmetrix related luns will not be claimed by the required ASL.


# vxddladm listversion output
LIB_NAME                        ASL_VERSION      Min. VXVM version  
===================================================================
libvx3par.so                    vm-5.0-rev-1            5.0
libvxCLARiiON.so                vm-5.0-rev-3            5.0
libvxhds9980.so                 vm-5.0-rev-1            5.0
libvxhdsalua.so                 vm-5.0-rev-2            5.0
libvxhdsusp.so                  vm-5.0-rev-2            5.0
libvxhpalua.so                  vm-5.0-rev-1            5.0
libvxhpmsa.so                   vm-5.0-rev-2            5.0
libvxibmds4k.so                 vm-5.0-rev-2            5.0
libvxibmds6k.so                 vm-5.0-rev-2            5.0
libvxibmds8k.so                 vm-5.0-rev-1            5.0
libvxpp.so                      vm-5.0-rev-1            5.0
libvxxp1281024.so               vm-5.0-rev-1            5.0
libvxxp12k.so                   vm-5.0-rev-2            5.0

# vxdmpadm  listctlr all
CTLR-NAME       ENCLR-TYPE      STATE      ENCLR-NAME
=====================================================
c0              Disk            ENABLED      disk
c1              Disk            ENABLED      disk
c2              Disk            ENABLED      disk
c1              EVA4K6K         ENABLED      eva4k6k0
c0              EVA4K6K         ENABLED      eva4k6k0

Error Message


Cause


What is an Array Support Library?
 

An ASL is a small library written either by VERITAS or by an array vendor that does the work of identifying an array and telling DMP how to use the devices that are present in the array.  By splitting the discovery and path fail over routines into a separate library we can add support for new arrays without changing the base VM package.


The ASL libraries are installed in /etc/vx/lib/discovery.d.

There is a corresponding ASL related key file installed in /etc/vx/aslkey.d.

NOTE: Without the applicable ASL related files, the specific disks will be claimed under the generic DMP enclosure category.


In this instance, the symbolic links for the "libvxemc.key" file do not exist in the directories /etc/vx/aslkey.d or /etc/vx/lib/discovery.d.

 

How to create the symbolic links for the corresponding "libvxemc.so.1" files


# cd /etc/vx/aslkey.d
# ln -s /etc/vx/aslkey.d/libvxemc.key.1 libvxemc.key

# cd /etc/vx/lib/discovery.d

# ln -s /etc/vx/lib/discovery.d/libvxemc.so.1 libvxemc.so


Please refer to Symantec Article: HOWTO77073 for further details in regards to:

How to recreate the missing symbolic links for a Veritas Array Support Library (ASL) not listed by vxddladm listversion
 

 

Solution


Steps


1.] cd /etc/vx/aslkey.d

2.] Confirm if the symbolic link is present for the required ASL key file.

3.] If the symbolic link is missing, recreate it as follows:

Sample syntax

# ln -s /etc/vx/aslkey.d/libvxemc.key.1 libvxemc.key

4.] cd /etc/vx/lib/discovery.d

5.] If the symbolic link is missing for the ASL library, recreate it as follows:

Sample syntax

# ln -s /etc/vx/lib/discovery.d/libvxemc.so.1 libvxemc.so

6.] Following the above changes to the aslkey.d and discovery.d directories, restart the Veritas Volume Manager "vxconfigd" daemon for the ASL updates to be detected.

# vxconfigd -k -x syslog



Example


Ensure the required symbolic links for the libvxemc ASL are in place:


# cd /etc/vx/aslkey.d

# ln -s /etc/vx/aslkey.d/libvxemc.key.1 libvxemc.key

# cd /etc/v/lib/discovery.d

# ln -s /etc/vx/lib/discovery.d/libvxemc.so.1 libvxemc.so

 


# vxdisk scandisks

# vxdisk list

DEVICE       TYPE            DISK         GROUP        STATUS
disk_0       auto            -            -            error
disk_1       auto            -            -            error
disk_2       auto            -            -            error
disk_3       auto            -            -            error
disk_4       auto            -            -            error
disk_5       auto            -            -            error
disk_6       auto            -            -            error
disk_7       auto            -            -            error
disk_8       auto            -            -            error
disk_9       auto            -            -            error
eva4k6k0_0   auto:sliced     -            -            online
eva4k6k0_1   auto:sliced     -            -            online
eva4k6k0_2   auto:sliced     -            -            online
eva4k6k0_3   auto:sliced     -            -            online
eva4k6k0_4   auto:sliced     -            -            online
eva4k6k0_5   auto:sliced     sdj          PDDG2        online
eva4k6k0_6   auto:sliced     -            -            online
eva4k6k0_7   auto:sliced     -            -            online
eva4k6k0_8   auto:sliced     -            -            online
eva4k6k0_9   auto:sliced     -            -            online
sda          auto:none       -            -            online invalid


Following the above changes to the aslkey.d and discovery.d directories, restart the Veritas Volume Manager "vxconfigd" daemon for the ASL updates to be detected.

 


# vxconfigd -k -x syslog


# vxdisk list

DEVICE       TYPE            DISK         GROUP        STATUS
emc0_0360    auto            -            -            error
emc0_0361    auto            -            -            error
emc0_0362    auto            -            -            error
emc0_0363    auto            -            -            error
emc0_0364    auto            -            -            error
emc0_0365    auto            -            -            error
emc0_0366    auto            -            -            error
emc0_0367    auto            -            -            error
emc0_0368    auto            -            -            error
emc0_0369    auto            -            -            error
eva4k6k0_0   auto:sliced     -            -            online
eva4k6k0_1   auto:sliced     -            -            online
eva4k6k0_2   auto:sliced     -            -            online
eva4k6k0_3   auto:sliced     -            -            online
eva4k6k0_4   auto:sliced     -            -            online
eva4k6k0_5   auto:sliced     sdj          PDDG2        online
eva4k6k0_6   auto:sliced     -            -            online
eva4k6k0_7   auto:sliced     -            -            online
eva4k6k0_8   auto:sliced     -            -            online
eva4k6k0_9   auto:sliced     -            -            online
sda          auto:none       -            -            online invalid


The missing ASL should now be listed by the CLI command "vxddladm listversion":
 

# vxddladm listversion
LIB_NAME                        ASL_VERSION      Min. VXVM version
===================================================================
libvx3par.so                    vm-5.0-rev-1            5.0
libvxCLARiiON.so                vm-5.0-rev-3            5.0
libvxemc.so                     vm-5.0-rev-3            5.0              <<< ASL now listed following the recreation of the required symbolic links
libvxhds9980.so                 vm-5.0-rev-1            5.0
libvxhdsalua.so                 vm-5.0-rev-2            5.0
libvxhdsusp.so                  vm-5.0-rev-2            5.0
libvxhpalua.so                  vm-5.0-rev-1            5.0
libvxhpmsa.so                   vm-5.0-rev-2            5.0
libvxibmds4k.so                 vm-5.0-rev-2            5.0
libvxibmds6k.so                 vm-5.0-rev-2            5.0
libvxibmds8k.so                 vm-5.0-rev-1            5.0
libvxpp.so                      vm-5.0-rev-1            5.0
libvxxp1281024.so               vm-5.0-rev-1            5.0
libvxxp12k.so                   vm-5.0-rev-2            5.0
 


 


Applies To

# rpm -qa | grep -i VRTSvxvm
VRTSvxvm-common-5.0.40.00-MP4_SLES10
VRTSvxvm-platform-5.0.40.00-MP4_SLES10

# /etc/SuSE-release
SUSE Linux Enterprise Server 10 (x86_64)
VERSION = 10
PATCHLEVEL = 2
 

Was this content helpful?