I don't have the 3PAR powershell component loaded... but the normal non-powershell 3PAR cli command showvlun works to show LUN# for both hosts and host sets, I was not able to test it for volume sets, but I suspect it also works as intended.
Can you explain the problem you are trying to solve with this scipt? Its not clear to me, but I think it may be that my deployment uses a VV naming convention that includes the LUN# in the VV name, and we've planned it such that if a VV is to be exported to multiple hosts, it will be the same LUN# on all hosts.
_________________ Richard Siemers The views and opinions expressed are my own and do not necessarily reflect those of my employer.
|