VMware Cloud Community
vMarkusK1985
Expert
Expert
Jump to solution

Duplicate LUN Exports hidden in Client

Hello,

We had some HP 3Par LUNs exported twice to the same host with different LUNs IDs.

The duplicate LUNs are hidden in C# and WebClient. That means if I check the LUN in GUI, path count is 4. If I use “esxcli storage core path list -d naa.60002ac000000000000000bb0000998c | grep LUN:

Path count is 8:

#  esxcli storage core path list -d naa.60002ac000000000000000bb0000998c | grep LUN:

   LUN: 49

   LUN: 7

   LUN: 49

   LUN: 49

   LUN: 7

   LUN: 49

   LUN: 7

   LUN: 7

My question is why the ESXi handles this situation like that? And how can I identify that in Path state or something else…?

Kind Regards,

Markus

https://mycloudrevolution.com | https://twitter.com/vMarkus_K | https://github.com/vMarkusK
Reply
0 Kudos
1 Solution

Accepted Solutions
vMarkusK1985
Expert
Expert
Jump to solution

To identify the problem I have created a PowerCLI Script:

http://mycloudrevolution.com/2016/06/15/doppele-3par-lun-exporte-erkennen/

After the script has reported the problematic LUNs, I manually unmapped the duplicate VLUNs from 3Par side (In my Case the VLUN Templates from a direct export and not via a Host or VLUN Group).

https://mycloudrevolution.com | https://twitter.com/vMarkus_K | https://github.com/vMarkusK

View solution in original post

Reply
0 Kudos
3 Replies
RicArnold
Contributor
Contributor
Jump to solution

Hi

It is quite easy to get in a situation like you describe if you have a volume exported manually and in a host set.  This effectively leaves the same targets presented more than once with different LUN ID's. As long as you have multipathing setup you should be able to remove duplicate LUNs without down time.  You can see which VLUNs a  host has with showvlun, and remove them with removevlun.

I would suggest testing it on a test host first but in principle I can see no issue with removing the duplicate.

Richard

vMarkusK1985
Expert
Expert
Jump to solution

Hi,

Thanks for your Reply!

The Problem is already resolved from 3Par Side.

The question is more about the Identification and Handling on VMware Side.

Kind Regards,

Markus

https://mycloudrevolution.com | https://twitter.com/vMarkus_K | https://github.com/vMarkusK
Reply
0 Kudos
vMarkusK1985
Expert
Expert
Jump to solution

To identify the problem I have created a PowerCLI Script:

http://mycloudrevolution.com/2016/06/15/doppele-3par-lun-exporte-erkennen/

After the script has reported the problematic LUNs, I manually unmapped the duplicate VLUNs from 3Par side (In my Case the VLUN Templates from a direct export and not via a Host or VLUN Group).

https://mycloudrevolution.com | https://twitter.com/vMarkus_K | https://github.com/vMarkusK
Reply
0 Kudos