I posted this on /r/linuxquestions and got no love. I am banging my head against a wall about this issue. Do any of you all have an idea?
This is a follow up to a question I posted on /r/vmware
So I have two CentOS boxes that are identical in almost every way. Both have 20TB carved up into three VG. When creating ISCSi's both boxes give Target1 the same information. This makes the ESXi environment read them as the same luns.
When I create a Target with a Target ID of 3, upon restart it resets back to Target 1.
[admin@xxxx] tgtadm --lld iscsi --mode target --op new --tid=3 --targetname ign.2016-02.XXXXXX:vm_storage [admin@xxxx] tgtadm --lld iscsi --mode target --op show Target 3: ign.2016-02.xxxxxxxx:vm_storage System information: Driver: iscsi State: ready I_T nexus information: LUN information: LUN: 0 Type: controller **SCSI ID: IET 00030000** SCSI SN: beaf30 Size: 0 MB, Block size: 1 Online: Yes Removable media: No Prevent removal: No Readonly: No Backing store type: null Backing store path: None Backing store flags: [admin@xxxx] service tgtd restart Stopping SCSI target daemon: [ OK ] Starting SCSI target daemon: [ OK ] [admin@xxxx] tgtadm --lld iscsi --mode target --op show Target 1: ign.2016-02.xxxxxxxx:vm_storage System information: Driver: iscsi State: ready I_T nexus information: LUN information: LUN: 0 Type: controller **SCSI ID: IET 00010000** SCSI SN: beaf10 Size: 0 MB, Block size: 1 Online: Yes Removable media: No Prevent removal: No Readonly: No Backing store type: null Backing store path: None Backing store flags: When I edit the /targets.conf file, manually setting the scsi_id only affects the LUNs and not the controller.
What am I missing, short of creating two isci targets that do not have any LUNs in it.
[link] [comments]