On Mon, 2013-10-07 at 23:20 +0200, Thomas Glanzmann wrote: > Hello Nab, > > > > /backstores/fileio create shared-01.v101.campusvl.de /iscsi1/shared-01.v101.campusvl.de size=80G buffered=true > > > /iscsi create iqn.2013-03.de.campusvl.v101.storage:shared-01.v101.campusvl.de > > > /iscsi/iqn.2013-03.de.campusvl.v101.storage:shared-01.v101.campusvl.de/tpgt1/portals create 10.101.99.4 > > > /iscsi/iqn.2013-03.de.campusvl.v101.storage:shared-01.v101.campusvl.de/tpgt1/portals create 10.101.99.5 > > > /iscsi/iqn.2013-03.de.campusvl.v101.storage:shared-01.v101.campusvl.de/tpgt1/luns create /backstores/fileio/shared-01.v101.campusvl.de lun=10 > > > /iscsi/iqn.2013-03.de.campusvl.v101.storage:shared-01.v101.campusvl.de/tpgt1/ set attribute authentication=0 demo_mode_write_protect=0 generate_node_acls=1 cache_dynamic_acls=1 > > > > /backstores/fileio create shared-01.v102.campusvl.de /iscsi1/shared-01.v102.campusvl.de size=80G buffered=true > > > /iscsi create iqn.2013-03.de.campusvl.v102.storage:shared-01.v102.campusvl.de > > > /iscsi/iqn.2013-03.de.campusvl.v102.storage:shared-01.v102.campusvl.de/ create 2 > > > /iscsi/iqn.2013-03.de.campusvl.v102.storage:shared-01.v102.campusvl.de/tpgt2/portals create 10.102.99.4 > > > /iscsi/iqn.2013-03.de.campusvl.v102.storage:shared-01.v102.campusvl.de/tpgt2/portals create 10.102.99.5 > > > /iscsi/iqn.2013-03.de.campusvl.v102.storage:shared-01.v102.campusvl.de/tpgt2/luns create /backstores/fileio/shared-01.v102.campusvl.de lun=10 > > > /iscsi/iqn.2013-03.de.campusvl.v102.storage:shared-01.v102.campusvl.de/tpgt2/ set attribute authentication=0 demo_mode_write_protect=0 generate_node_acls=1 cache_dynamic_acls=1 > > > /iscsi/iqn.2013-03.de.campusvl.v102.storage:shared-01.v102.campusvl.de/ delete 1 > > > So what I was thinking for the above is to configure a vlan device (say > > eth0.5), and assign it a specific IP address. From there the vlan > > device's IP address can be assigned as a network portal to individual > > TargetName+TargetPortalGroupTag endpoints. > > I thought I have done that. Haven't I? > > VLAN 101: > TargetPortalGroupTag 1 > Portal: 10.101.99.4 > Portal: 10.101.99.5 > > VLAN 102: > TargetPortalGroupTag 2 > Portal: 10.102.99.4 > Portal: 10.102.99.5 > > When I discover on 10.101.99.4 I still see the demo_mode LUNs from > 'TargetPortalGroupTag 2'. Mmmm, strange. I'm guessing this has something to do with using the same TargetName and multiple TargetPortalGroupTags. The one limitation of doing this is that the Initiator does not explicitly select which TargetPortalGroupTag it wants to connect with during Login, and has to rely upon network portal addresses for this. Can you confirm what logging into 10.101.99.4 returns for key TargetPortalGroupTag in the first login response payload..? So separate from the above, I'd recommend using different TargetNames w/ TPGT=1 across the different VLANs, and managing endpoints by TargetNames instead of TargetPortalGroupTags. This should work the way you expect with different VLANs. > > > > iSCSI (Text Response) > > > Opcode: Text Response (0x24) > > > Flags: 0x80 > > > 1... .... = F: Final PDU in sequence > > > .0.. .... = C: Text is complete > > > TotalAHSLength: 0x00 > > > DataSegmentLength: 0x000002be > > > LUN: 0000000000000000 > > > InitiatorTaskTag: 0x00000001 > > > TargetTransferTag: 0xffffffff > > > StatSN: 0xa33a9e16 > > > ExpCmdSN: 0x00000002 > > > MaxCmdSN: 0x00000002 > > > Key/Value Pairs > > > KeyValue: TargetName=iqn.2013-03.de.campusvl.v102.storage:shared-01.v102.campusvl.de > > > KeyValue: TargetAddress=10.102.99.5:3260,2 > > > KeyValue: TargetAddress=10.102.99.4:3260,2 > > > KeyValue: TargetName=iqn.2013-03.de.campusvl.v101.storage:shared-01.v101.campusvl.de > > > KeyValue: TargetAddress=10.101.99.4:3260,1 > > > KeyValue: TargetAddress=10.101.99.5:3260,1 > > > Padding: 0000 > > > I'm a bit confused here. What is the discovery output that is expected > > here? > > I don't want to see > TargetName=iqn.2013-03.de.campusvl.v102.storage:shared-01.v102.campusvl.de > Please confirm that iqn.2013-03.de.campusvl.v102.storage:shared-01.v102.campusvl.de is configured with generate_node_acls=0, and that no active sessions from the initiator has created a NodeACL with se_node_acl->dynamic_node_acl --nab -- 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
