Perhaps obfuscation is not the best word, but I'd like to get share my
thoughts on this. It's not an issue per-say, but I find myself doing a
lot of recursive lookups when trying to determine which iSCSI target
is associated with which lun. This is because I am using target portal
groups and host groups and target groups (stmfadm target groups).
Here is an example:
-bash-3.2# stmfadm list-target -v
Target: iqn.1986-03.com.sun:02:3c82f62d-cde6-e101-fdaf-f64bf10afd2c
Operational Status: Online
Provider Name : iscsit
Alias : -
Sessions : 2
Initiator: iqn.2007-01.com.virtualiron:01:0030483439ec
Alias: -
Logged in since: Sat Sep 5 18:25:01 2009
Initiator: iqn.2007-01.com.virtualiron:01:0030483439ec
Alias: -
Logged in since: Sat Sep 5 18:24:57 2009
Target: iqn.1986-03.com.sun:02:7f169cd7-0eb4-6861-d034-945326c9db5b
Operational Status: Online
Provider Name : iscsit
Alias : -
Sessions : 2
Initiator: iqn.2007-01.com.virtualiron:01:0030483439ec
Alias: -
Logged in since: Sat Sep 5 18:24:53 2009
Initiator: iqn.2007-01.com.virtualiron:01:0030483439ec
Alias: -
Logged in since: Sat Sep 5 18:24:49 2009
Ok - cool two targets. How do I determine what those two targets are for?
I have to start by looking at the logical units:
-bash-3.2# stmfadm list-lu -v
LU Name: 600144F0660B8D0000004AA295D70001
Operational Status: Online
Provider Name : sbd
Alias : /dev/zvol/rdsk/datapool/stores/vi/luns/lun2
View Entry Count : 1
Data File : /dev/zvol/rdsk/datapool/stores/vi/luns/lun2
Meta File : not set
Size : 107374182400
Block Size : 512
Management URL : not set
Vendor ID : SUN
Product ID : COMSTAR
Serial Num : not set
Write Protect : Disabled
Writeback Cache : Enabled
LU Name: 600144F0660B8D0000004AA295D90002
Operational Status: Online
Provider Name : sbd
Alias : /dev/zvol/rdsk/datapool/stores/vi/luns/lun1
View Entry Count : 1
Data File : /dev/zvol/rdsk/datapool/stores/vi/luns/lun1
Meta File : not set
Size : 107374182400
Block Size : 512
Management URL : not set
Vendor ID : SUN
Product ID : COMSTAR
Serial Num : not set
Write Protect : Disabled
Writeback Cache : Enabled
Ok - now I need to see what views are associated with those luns:
-bash-3.2# stmfadm list-view -l 600144F0660B8D0000004AA295D90002
View Entry: 0
Host group : viGroup1
Target group : datapool/stores/vi/luns/lun1
LUN : 1
Ok - now I need to see what hosts are in viGroup1 and what targets are
in datapool/stores/vi/luns/lun1.
-bash-3.2# stmfadm list-hg -v viGroup1
Host Group: viGroup1
Member: iqn.2007-01.com.virtualiron:01:0030483439ec
-bash-3.2# stmfadm list-tg -v datapool/stores/vi/luns/lun1
Target Group: datapool/stores/vi/luns/lun1
Member: iqn.1986-03.com.sun:02:3c82f62d-cde6-e101-fdaf-f64bf10afd2c
-bash-3.2#
Ok so I had to use four commands to determine what's really important
here; what backing store is associated with the target and who can see
it.
Now before anyone gets the wrong impression here, THIS IS NOT A
COMPLAINT. I'm not venting or anything of the like. I also recognize
that using chap for security could alleviate some of this. I'm simply
pointing out an observation. All of this can be of course automated
through scripts and if you have a GUI, none of this even matters. But
I wanted to share my observation just in case someone wanted to
enhance stmfadm to reduce what I am calling "obfuscation".
Thank you
--------------------------------------------------------------------------------
This email and any files transmitted with it are confidential and are
intended solely for the use of the individual or entity to whom they
are addressed. This communication may contain material protected by
the attorney-client privilege. If you are not the intended recipient,
be advised that any use, dissemination, forwarding, printing or
copying is strictly prohibited. If you have received this email in
error, please contact the sender and delete all copies.
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
