Enhancement Requested for Shared Storage Pools (SSPs)

Customer asked for an "automated way" to avoid having to manually map all of the shared storage pools (SSPs) created on production system (in Mississippi) to disaster recovery/HA system (in Arizona). Would like script or other utility provided with LUIDs.

From expert blogger: we don't have a simple automated report or command line output that details
For every LU in the SSP -> which LPAR name and machine is it connected to (the VIOS SSP only knows the vadapter/vhost and client id, NOT the LPAR=VM name)
Or the reverse
For every LPAR (Virtual Machine) by name -> which LUs it has online

The customer is correct in this.
My nmap given away script (modified) can get us partly there.

Technical stuff below describing how close we can get using regular commands.

From my investigation and help from colleague, Gareth Coates - we can in two commands get all the data and manually match LU to VM name

1) VIOS in the SSP and as root users (oem_setup_env)
clcmd /usr/ios/cli/ioscli lsmap -all -field clientid SVSA backing Physloc -fmt : 2>/dev/null
This gives us lists of the mapped LU for every VIOS in the SSP
KEY: GREEN=client LPAR Id and RED=SSP LU name (diskname) and BLUE machine MTM+Serial number and the BROWN the LPAR=VM name
. . .
-------------------------------
NODE emeraldvios1.aixncc.uk.ibm.com
-------------------------------
0x00000007:vhost0:U8286.42A.100EC7V-V2-C3:vm178boot.b7f6f81dbe9897d68395fbfca8bf0684
0x00000063:vhost1:U8286.42A.100EC7V-V2-C4:
0x0000000a:vhost2:U8286.42A.100EC7V-V2-C5:
0x00000008:vhost3:U8286.42A.100EC7V-V2-C6:volume-vm177-3bce00b6-00000015-boot-0-846d927d-12cc.74a9e888e9f1b3599ebf2e44fbe19d56
. . .

2) To look up the client IDs on the HMC and find the LPAR=VM name
lssyscfg -r sys -F name | while read M; do lssyscfg -r sys -m $M -F name,type_model,serial_num; lssyscfg -r lpar -m $M -F name,lpar_id; echo; done

. . .
P8-S824-emerald,8286-42A,100EC7V
vm51,14
download-repo,13
w3-blue,12
vm50,11
vm20,10
vm179-dcfb17c5-00000016,9
vm177-3bce00b6-00000015,8 <-
vm178,7 <-
vm173-05ec5972-0000000e,6
vm26,5
vm25,4
emeraldvios2,3
emeraldvios1,2
emeraldbackup-76665db5-00000009,1
. . .

So for example VIOS SSP LU vm178boot is the disk for Virtual Machine vm178

It is very disappointing to note the VIOS Client VM ID is in hexadecimal (see 0x0000000a:vhost2:U8286.42A.100EC7V-V2-C5:) and decimal on the HMC (which add extra complexity).

Some one on HMC dev or SSP dev teams could create this script or utility.
All clients would benefit from this information as it increases SSP usability.