1 person found this helpful
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.
Thanks for your Reply!
The Problem is already resolved from 3Par Side.
The question is more about the Identification and Handling on VMware Side.
To identify the problem I have created a PowerCLI Script:
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).