On Thu, 2016-02-11 at 19:41 -0800, Schlacta, Christ wrote: > On Thu, Feb 11, 2016 at 6:57 PM, Schlacta, Christ <aarcane@xxxxxxxxxxx> wrote: > > On Thu, Feb 11, 2016 at 3:58 PM, Nicholas A. Bellinger > > <nab@xxxxxxxxxxxxxxx> wrote: > >> On Thu, 2016-02-11 at 09:44 -0800, Schlacta, Christ wrote: > >>> I apologize, as last night I accidentally replied off-list to this > >>> thread due to a mis-configured list. I've recreated the messages > >>> below, updated the time, and corrected a typo. > >>> > >>> > >>> On Thu, Feb 11, 2016 at 12:00 AM, Nicholas A. Bellinger > >>> <nab@xxxxxxxxxxxxxxx> wrote: > >>> > On Wed, 2016-02-10 at 18:36 -0800, Schlacta, Christ wrote: <SNIP> > >>> >> /qla2xxx/21:0...9d:12:dd/acls> ls / > >>> >> o- / .............................................. [...] > >>> >> o- backstores ................................... [...] > >>> >> | o- fileio ....................... [3 Storage Objects] > >>> >> | | o- izanami01 . [256.0G, /vdisk02/izanami01, in use] > >>> >> | | o- test01 ....... [256.0G, /vdisk02/test01, in use] > >>> >> | | o- test02 ....... [256.0G, /vdisk02/test02, in use] > >>> >> | o- iblock ........................ [0 Storage Object] > >>> >> | o- pscsi ......................... [0 Storage Object] > >>> >> | o- rd_mcp ........................ [0 Storage Object] > >>> >> o- iscsi .................................. [0 Targets] > >>> >> o- loopback ............................... [0 Targets] > >>> >> o- qla2xxx ................................. [1 Target] > >>> >> | o- 21:00:00:1b:32:9d:12:dd ................ [enabled] > >>> >> | o- acls ................................... [1 ACL] > >>> >> | | o- 20:00:00:1b:32:9d:77:da ...... [3 Mapped LUNs] > >>> >> | | o- mapped_lun0 .................... [lun0 (rw)] > >>> >> | | o- mapped_lun1 .................... [lun1 (rw)] > >>> >> | | o- mapped_lun2 .................... [lun2 (rw)] > >>> >> | o- luns .................................. [3 LUNs] > >>> >> | o- lun0 . [fileio/izanami01 (/vdisk02/izanami01)] > >>> >> | o- lun1 ....... [fileio/test01 (/vdisk02/test01)] > >>> >> | o- lun2 ....... [fileio/test02 (/vdisk02/test02)] > >>> >> o- vhost .................................. [0 Targets] > >>> > > >>> > Looks fine as an NodeACL + MappedLUN for 20:00:00:1b:32:9d:77:da > >>> > > >>> > Please confirm your FC WWPN initiator port (non-NPIV) value > > Also, insofar as I can verify, the FC WWPN initiator port (non-NPIV) > value is as follows: > > Hostname: > localhost > HBA Model: > QLE2462 > Node Name: > 20-00-00-1B-32-9D-77-DA > Port Name: > 21-00-00-1B-32-9D-77-DA > HBA Port: > 1 > Port ID: > 00-00-02 > The targetcli /qla2xxx/$WWPN endpoint and configfs group in /sys/kernel/config/target/qla2xxx/$WWPN/ both expect 21: prefixed non-NPIV World Wide Port Name, and not 20: prefixed Node Name as per your original setup above. > >>> > > >>> > >>> I'm not at the initiator now, but I'll check later. > >> > >> In recent versions of tcm_qla2xxx, there is a configfs attribute to list > >> which 'demo-mode' sessions are active: > >> > >> cat /sys/kernel/config/target/qla2xxx/$WWPN/tpgt_1/dynamic_sessions > >> > >> This will show which $INITIATOR_WWPN ports have logged in, vs. what's > >> currently configured in /qla2xxx/$WWPN/acls/$INITIATOR_WWPN/ for > >> explicit NodeACLs. > > > > I'm on 3.16.0-4 on debian wheezy, so I'm guessing this isn't a new > > enough version. Is there a DKMS package I can install newer modules > > with? That kinda defeats the purpose of switching to lio though > > > >> > >>> In the mean time, > >>> can I somehow disable acls, as there is only the two endpoints on the > >>> physical loop, and that's enough access control for testing purposes? > >>> (No switch) > >> > >> Yes, in targetcli under each /qla2xxx/$WWPN/ context, do: > >> > >> /> cd /qla2xxx/21:00:00:24:ff:48:97:7e/ > >> /qla2xxx/21:0...4:ff:48:97:7e> set attribute generate_node_acls=1 > >> cache_dynamic_acls=1 demo_mode_write_protect=1 > >> Parameter generate_node_acls is now '1'. > >> Parameter cache_dynamic_acls is now '1'. > >> Parameter demo_mode_write_protect is now '1'. > > > > Those are the default values already set. Are you sure some of them > > shouldn't be 0s? Yes, the tcm_qla2xxx defaults of 1 allows all FC hosts to login to all FC ports. Historically, some FC initiator HBAs go nuts if they are unable to complete session login. Keep in mind that if your /qla2xxx/$WWPN/ endpoint has already been enabled before the LUNs where added, and NodeACLs + MappedLUNs where added, your port will see a Virtual LUN=0. The following targetcli global controls this: targetcli /> get global auto_enable_tpgt auto_enable_tpgt=true > I can't find documentation on them anywhere. > > http://www.spinics.net/lists/target-devel/msg07844.html -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
