Missing 3 of the paths for the newly connected storage

book

Article ID: 100043852

calendar_today

Updated On:

Description

Error Message

Paths missing in vxdisk list output for newly provisioned LUN's.  Only one path is visible.

Cause

SAN team missed to enable some settings from their end.

Resolution

From VERITAS Explorer logs.

<<<>>>

-bash-4.1$ cat vxdisk_list_emc0_0024
Device:    emc0_0024
devicetag: emc0_0024
type:      auto
hostid:    pedw-hd
disk:      name=vmx_u01_00 id=1533997096.639.pedw-hd
timeout:  30
pftostate: enabled
group:    name=pedwdg id=1352044298.413.pedw-hd5
info:      format=cdsdisk,privoffset=128
flags:    online ready private autoconfig autoimport imported thinrclm
pubpaths:  block=/dev/vx/dmp/emc0_0024 char=/dev/vx/rdmp/emc0_0024
guid:      {639a9262-9d71-11e8-9114-b499ba62c3b6}
udid:      EMC%5FSYMMETRIX%5F000197700557%5F5700024000
site:      -
version:  3.1
iosize:    min=512 (bytes) max=2048 (blocks)
public:    slice=0 offset=32896 len=52394184 disk_offset=0
private:  slice=0 offset=128 len=32768 disk_offset=0
update:    time=1533997457 seqno=0.5
ssb:      actual_seqno=0.0
headers:  0 120
configs:  count=1 len=24072
logs:      count=1 len=3648
Defined regions:
config  priv 000024-000119[000096]: copy=01 offset=000000 disabled
config  priv 000128-024103[023976]: copy=01 offset=000096 disabled
log      priv 024104-027751[003648]: copy=01 offset=000000 disabled
lockrgn  priv 027752-027823[000072]: part=00 offset=000000
Annotations:
tag      udid_asl=EMC%5FSYMMETRIX%5F000197700557%5F5700024000
Multipathing information:
numpaths:  1
c55t0d1        state=enabled       <<< It shows single path only

<<>>>>

-bash-4.1$ cat vxdisk_list_emc_clariion0_75
Device:    emc_clariion0_75
devicetag: emc_clariion0_75
type:      auto
flags:    error private autoconfig
pubpaths:  block=/dev/vx/dmp/emc_clariion0_75 char=/dev/vx/rdmp/emc_clariion0_75
guid:      -
udid:      DGC%5FVNX5700WDVR%5FAPM00113800272%5F6006016060202E00965FB6BDDE7DE211
site:      -
errno:    Disk read failure
Multipathing information:
numpaths:  8
c31t0d4        state=enabled  type=secondary
c39t0d4        state=enabled  type=secondary
c53t0d4        state=enabled  type=primary
c33t0d4        state=enabled  type=primary
c41t0d4        state=enabled  type=primary
c49t0d4        state=enabled  type=primary
c51t0d4        state=enabled  type=secondary
c47t0d4        state=enabled  type=secondary     <<< It shows all eight paths


<<< Checking the paths at OS level>>>

$less ioscan_m_dsf
/dev/rdisk/disk3037      /dev/rdsk/c33t0d4   <<>
                         /dev/rdsk/c31t0d4
                        /dev/rdsk/c41t0d4
                        /dev/rdsk/c39t0d4
                        /dev/rdsk/c49t0d4
                        /dev/rdsk/c47t0d4
                        /dev/rdsk/c53t0d4
                        /dev/rdsk/c51t0d4
                 
/dev/rdisk/disk3284      /dev/rdsk/c55t0d1    << OS device to path mapping, single path visible at OS level for VMAX disk emc0_0024>>

<<< Even the ioscan command shows single path for VMAX LUN emc0_0024 >>>

-bash-4.1$ grep 3284 ioscan_fN
lunpath    4594  37/0/2/2/0/0/0.0x50000973a008b404.0x1000000000000    eslpt          CLAIMED    LUN_PATH    LUN path for disk3284
disk      3284  64000/0xfa00/0x1c7                                    esdisk        CLAIMED    DEVICE      EMC    SYMMETRIX


<<>

-bash-4.1$ grep 3037 ioscan_fN
lunpath    1899  37/0/0/2/0/0/1.0x5006016247200e02.0x4004000000000000  eslpt          CLAIMED    LUN_PATH    LUN path for disk3037
lunpath    1837  37/0/0/2/0/0/1.0x5006016a47200e02.0x4004000000000000  eslpt          CLAIMED    LUN_PATH    LUN path for disk3037
lunpath    2979  37/0/2/2/0/0/1.0x5006016247200e02.0x4004000000000000  eslpt          CLAIMED    LUN_PATH    LUN path for disk3037
lunpath    2753  37/0/2/2/0/0/1.0x5006016a47200e02.0x4004000000000000  eslpt          CLAIMED    LUN_PATH    LUN path for disk3037
lunpath    3875  41/0/2/2/0/0/1.0x5006016647200e02.0x4004000000000000  eslpt          CLAIMED    LUN_PATH    LUN path for disk3037
lunpath    3673  41/0/2/2/0/0/1.0x5006016b47200e02.0x4004000000000000  eslpt          CLAIMED    LUN_PATH    LUN path for disk3037
lunpath    4356  42/0/0/0/0/0/1.0x5006016347200e02.0x4004000000000000  eslpt          CLAIMED    LUN_PATH    LUN path for disk3037
lunpath    4128  42/0/0/0/0/0/1.0x5006016b47200e02.0x4004000000000000  eslpt          CLAIMED    LUN_PATH    LUN path for disk3037
disk      3037  64000/0xfa00/0xe1                                    esdisk        CLAIMED    DEVICE      DGC    VNX5700WDVR


VERITAS Support advised customer to reach OS Vendor(If everything good from SAN end) to identify why the all the paths for VMAX LUN’s are not visible at OS level.  As VERITAS DMP depends on underlying SCSI layer to access devices.

Reference:

https://www.veritas.com/support/en_US/article.000024597

Customer replied that issue is from their Storage end (SAN) and his SAN team fixed it.

Issue/Introduction

We have connected VMAX storage and we only see only 1 path from the vxdmp.From storage side they can see 4 paths but not from the veritas DMP side.