Is there a way to find out the wwn of unexported virtualvome?

Not today, you need to have it part of a storage view, you can create an empty one if you dont want it exposed to a host.

HI cattaf,

You'll be happy to know that this is being fixed for a future release.  It's been a frequent ask.

It will appear as an additional property of a virtual-volume.

Gary

Hi Gary, do you know what version this will come out in??  We use local mirrors at our DR facility and come to find it to be a challenge to locate the UID for the mirror device.  Will this version that you are speaking of allow for me to locate the UID for the mirror device prior to the detach?

Hi aaronmatson,

This is fixed in the upcoming 5.4 release of GeoSynchrony.

If I understand your scenario correct, you create a mirror, detach it, and then create a new virtual-volume on top of it?  And you're interested in knowing what the VPD83T3 string (aka. NAA string) of the volume will be?

If this is true, then yes, with 5.4 when you create the virtual-volume but don't export it (yet), you will be able to see what the assigned VPD83T3 string will be before it's exported.

You will see a new field of the virtual-volume, like this:

VPlexcli:/clusters/cluster-1/virtual-volumes/dd_vol_1> ll

Name Value

-------------------------- ----------------------------------------

block-count 1310720

block-size 4K

cache-mode synchronous

capacity 5G

consistency-group -

expandable true

expandable-capacity 0B

expansion-method storage-volume

expansion-status -

health-indications []

health-state ok

locality distributed

operational-status ok

recoverpoint-protection-at []

recoverpoint-usage -

scsi-release-delay 0

service-status running

storage-tier -

supporting-device dd_sample1

system-id dd_vol_1

volume-type virtual-volume

vpd-id VPD83T3:6000144000000010f02886e1aa9e6b15

Gary

Thanks garyo.  I have recently learned that for the people running 5.3 a very easy way to automate this process after added to the storage view using expect scripts.  I will post for the ones that may be interested in using this.  We have a lot of V-Vols to recover during our DR tests and this will save us hours of time.  You can pipe this out to a file name and save it off to send to the necessary support group.  This will export all V-Vol information UID, Host LUN ID, Name and size.  I saved this as a .sh file and called it (single view).

service@ :~> singleview | awk 'NR > 12' > .txt

#!/usr/bin/expect -f

# the cmd variable can be set to a command that you would like to execute automatically

set cmd [lrange $argv 0 0 ]

set timeout -1

# now connect to vplexcli

spawn vplexcli

#look for the vplexcli login prompt

expect -re "Name:"

#send vplexcli login name

send "service\r"

# look for the passsword prompt

expect -re "Password:"

# send password

send "Mi@Dim7T\r"

#look for the VPlexcli prompt`

expect -re "VPlexcli:/> "

# send The command

send "ll -f /clusters/cluster-1/exports/storage-views/$cmd\r"

#look for the VPlexcli prompt`

expect -re "VPlexcli:/> "

# uncomment the following to interact with the vplexcli`

#interact

I hope that this can help the ones of you that struggle to get this information when tim is of the essence and you use local mirrors. 

Nice script.  Thanks.

You could probably accomplish the same via RESTful API as well.

Gary