@eneal --
That's good news.
Re: your latest question: A fix was added to snv_118 that allows
modifying the set of target groups even when the STMF service is up:
6788352 Cannot add target group members if STMF is enabled.
With that understood, are all the issues with target groups now
resolved? Or is there something more I should look at?
For those who find this conversation in the future...
I find it easy to confuse the iSCSI notion of "target portal group"
with the STMF notion of "target group".
The iSCSI "Target Portal Group" is basically a list of IP addresses that
determine which interfaces a given iSCSI target will listen on. The
"itadm create-tpg" command can be used to create a target portal group
as a list of ip-address:port specifiers. A specific iSCSI target is
bound to that target portal group with the "itadm modify-target -t"
command. Once that occurs, then an iSCSI listener will be created on
each IP address in that target portal group, listening for connections
to that iSCSI target. So this is the tool you use if you wish to
restrict your iSCSI target to be available only through one specific IP
address.
The STMF "host group" and "target group" notions are used for Logic Unit
Mapping (LUN Mapping), otherwise known as "COMSTAR Views". The set of
Logical Units that a particular SCSI initiator can see through a
particular I-T nexus is determined by the combined set of COMSTAR
Views. Each LU has an associated set of View Entries. Each view entry
specifies a target group and a host group and a LU number (LUN). The
idea is that any initiator that is a member of that specified host
group, when connecting through a target that is part of the specified
target group, will see the specified logical unit at the specified
LUN. This is the method you can use to restrict the set of LUs that a
given initiator can see, and assign the particular set of LU numbers
that will be used. It is a very general mechanism, so it can take a
bit of getting used to.
Peter C
[email protected] wrote:
Quoting Brent Jones <[email protected]>:
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Can confirm this appears to be a bug. I've tried making host groups
with a view for a lun added to that group.
What happens, the initiator can see a target, but no luns presented
underneath it.
--
Brent Jones
[email protected]
After some additional testing, instead of using the itadm to create
the host group, I used stfmadm to create at host group and target
portal group and that seemed to work.
-bash-3.2# stmfadm list-hg
Host Group: viGroup1
-bash-3.2# stmfadm list-hg -v
Host Group: viGroup1
Member: iqn.2007-01.com.virtualiron:01:0030483439ec
-bash-3.2#
The problem is that using target portal groups (ensuring a LUN is only
exposed to selected target), the command can only be issued with the
stmf service disabled??? What's that all about.
--------------------------------------------------------------------------------
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
