Matching back-end array LUN ID to VPLEX UIDS

//Matching back-end array LUN ID to VPLEX UIDS

As you already noticed when working with VPLEX is that VPLEX masks the back-end array LUN ID and present to the client with different internal VPLEX UIDS.

The reason for that is because VPLEX technically virtualize the back-end array(s). So with VPLEX you are not attached to a specific array, and VPLEX have the ability to change your underneath storage array/location without affecting client presented LUN(s).

Another issue that you will notice is that VPLEX can take several back-end array LUNs and present them as one device to a server, this is why you will only deal with VPLEX UIDS instead of back-end array LUN ID.

 

The following procedure will demonstrate how to match the back-end array LUN ID to VPLEX UIDS (assuming that you have used the a full LUN from the back-end array and presented it using VPLEX as a device to the server).

Array LUN# VPLEX VPD ID – WWN Server – WWN
36B9 xxxxxxxxxxxxxxxxxxxxxxxxxxc23ead Disk9 : xxxxxxxxxxxxxxxxxxxxxxxxxxc23ead

VPLEX Side:

GUI
VPLEX_LUN_WWN01

CLI command:

command: ls -t /clusters/cluster-1/exports/storage-views/
note: this command will print the full list of initiators, ports, and virtual volumes

example
VPlexcli:/> ls -t /clusters/cluster-1/exports/storage-views/demoluster_clu

/clusters/cluster-1/exports/storage-views/democluster_clu:
Name                                      Value
—————————– ———————————————————————————
initiators                               [democluster_A, democluster_B] operational-status               ok
caw-enabled                          true
name                                      democluster_clu
write-same-16-enabled      true
ports               [P00000000123412F1-A0-FC00, P00000000123412F1-A0-FC01, P00000000123412F1-A0-FC02,
.                       P00000000123412F1-A0-FC03, P00000000123412F1-B0-FC00, P00000000123412F1-B0-FC01,
.                       P00000000123412F1-B0-FC02, P00000000123412F1-B0-FC03]

port-name-enabled-status[P00000000123412F1-A0-FC00,true,ok, P00000000123412F1-A0-FC01,true,ok,
P00000000123412F1-A0-FC02,true,ok, P00000000123412F1-A0-FC03,true,ok,
P00000000123412F1-B0-FC00,true,ok, P00000000123412F1-B0-FC01,true,ok,
P00000000123412F1-B0-FC02,true,ok, P00000000123412F1-B0-FC03,true,ok]

controller-tag           –

virtual-volumes[(0,vol_democluster_36C3_45D1,VPD83T3: 60001110000000111111f69795c23d18,113G),
(1,vol_democluster_36BE_45CC,VPD83T3:60001110000000111111f69795c23d17,113G),
(2,vol_democluster_36BB_45C9,VPD83T3:60001110000000111111f69795c23d16,34G),
(3,vol_democluster_36BA_45C8,VPD83T3:60001110000000111111f69795c23d15,11.3G),
(4,vol_democlustera_device1_36B8,VPD83T3:60001110000000111111f69795c23eac,3.1G),
(5,vol_democlusterb_device1_36B9,VPD83T3:60001110000000111111f69795c23ead,3.1G),
(6,vol_democluster_36B6_45C4,VPD83T3:60001110000000111111f69795c23d14,6.2G),
(7,vol_democluster_36B4_45C2,VPD83T3:60001110000000111111f69795c23d13,6.2G),
(8,vol_democluster_36B2_45C0,VPD83T3:60001110000000111111f69795c23d0f,516M),
(9,vol_democluster_36B0_45BE,VPD83T3:60001110000000111111f69795c23d10,1.01G)]

PowerPath Windows Side:

GUI
VPLEX_LUN_WWN02

CLI Command:

command: powermt display dev=all
note: we will only print two drives as the list is long

example
C:\Windows\system32>powermt display dev=all
Pseudo name=harddisk1
VPLEX ID=FNM00123123123
Logical device ID=60001110000000111111F69795C23D18
state=alive; policy=ADaptive; queued-IOs=0
==============================================================================
————— Host —————   – Stor – — I/O Path —   — Stats —
### HW Path               I/O Paths   Interf. Mode     State   Q-IOs Errors
==============================================================================
5 port5\path0\tgt3\lun0 c5t3d0     06       active   alive     0     0
5 port5\path0\tgt2\lun0 c5t2d0     04       active   alive     0     0
5 port5\path0\tgt1\lun0 c5t1d0     00       active   alive     0     0
5 port5\path0\tgt0\lun0 c5t0d0     02       active   alive     0     0
3 port3\path0\tgt3\lun0 c3t3d0     01       active   alive     0     0
3 port3\path0\tgt2\lun0 c3t2d0     03       active   alive     0     0
3 port3\path0\tgt1\lun0 c3t1d0     05      active   alive     0     0
3 port3\path0\tgt0\lun0 c3t0d0     07       active   alive     0     0

Pseudo name=harddisk9
VPLEX ID=FNM00123123123
Logical device ID=60001110000000111111F69795C23EAD
state=alive; policy=ADaptive; queued-IOs=0
==============================================================================
————— Host —————   – Stor – — I/O Path —   — Stats —
### HW Path               I/O Paths   Interf. Mode     State   Q-IOs Errors
==============================================================================
5 port5\path0\tgt3\lun5 c5t3d5     06       active   alive     0     0
5 port5\path0\tgt2\lun5 c5t2d5     04       active   alive     0     0
5 port5\path0\tgt1\lun5 c5t1d5     00       active   alive     0     0
5 port5\path0\tgt0\lun5 c5t0d5     02       active   alive     0     0
3 port3\path0\tgt3\lun5 c3t3d5     01       active   alive     0     0
3 port3\path0\tgt2\lun5 c3t2d5     03       active   alive     0     0
3 port3\path0\tgt1\lun5 c3t1d5     05       active   alive     0     0
3 port3\path0\tgt0\lun5 c3t0d5     07       active   alive     0     0

2017-05-19T00:20:16+00:00 December 5th, 2014|VPLEX|0 Comments

Leave A Comment

About me

I have more than 15 years hands-on experience in the IT field. The majority of my work is in networking, operating systems and applications and storage. I carry industry certifications in Redhat, Microsoft, EMC, VMWare, VCE and ITIL.

I find it hard to find procedures or documents on how to implement specific technology and this is how the decision to create a place to share my knowledge and ideas for anyone interested in the same subject.

If you have the same vision and you are interested to publish on this website please contact me and I will create an account for you.

Certifications:
RHCSA

Certifications:
MCSE Security
MCSA Massaging

Certifications:
EMCIE- Isilon
EMCTA- Isilon
EMCIE- VNX

Certifications:
VCP-DCV

Certifications:
VCE-CIA

Certifications:
TITL

This site is targeting Solution Architects, Implementation Engineers and Systems Administrators. It is not targeting sales or intending to promote any specific technology or vendor.

The focus is on hands-on work, technical documentations and architecting solutions.

The site reflects my knowledge and opinions, I do recommend that you test what you learn in the lab environment before implementing it in production.

If you have a doubt call technical support, I do not assume any liability for any errors or omissions in those articles, I also make no representations as to the accuracy or completeness of any information on this site or found by following any link on this site

Content published here is tested in my own lab and is not reviewed or approved by any vendor.

If you have any issues with your system I highly recommend you contact the technical support of the vendor.

Disclaimer

Knowledge Ascent (KA) makes information available on its web site to enhance public knowledge and promote a better understanding of the IT environment. KA attempts to provide accurate, complete, and timely information. KA, however, cannot guarantee the quality, content, accuracy, or completeness of the information, text, graphics, links, and other items contained on its web pages because the material comes from a variety of sources, collected and maintained for different purposes. KA also retains the right to change any content on its web site without prior notice.

Information provided on the KA web site should not be used as a substitute for IT or other professional advice. KA assumes no liability for any damages or loss of any kind that might arise from the use of, misuse of, or the inability to use the KA web site and/or the materials contained on the web site. KA also assumes no liability for improper or incorrect use of materials or information contained on its web site. All materials that appear on the KA web site are distributed and transmitted "as is," without warranties of any kind, either express or implied, and subject to the terms and conditions stated in this disclaimer.

Contact Me
FAQ