Iscsiadm initiator reported error 24 iscsi login failed due to authorization failure

I am trying to set up a iSCSI target:

[root@localhost /]# targetcli
targetcli shell version 2.1.fb37
Copyright 2011-2013 by Datera, Inc and others.
For help on commands, type 'help'.

/> cd backstores/fileio 
/backstores/fileio> create disk01 /iscsi_disks/disk01.img 5G
Created fileio disk01 with size 5368709120
/backstores/fileio> cd /iscsi 
/iscsi> create iqn.2015-06.world.server:storage.target01
Created target iqn.2015-06.world.server:storage.target01.
Created TPG 1.
Global pref auto_add_default_portal=true
Created default portal listening on all IPs (0.0.0.0), port 3260.
/iscsi> cd iqn.2015-06.world.server:storage.target01/tpg1/luns
/iscsi/iqn.20...t01/tpg1/luns> create /backstores/fileio/disk01 
Created LUN 0.
/iscsi/iqn.20...t01/tpg1/luns> cd ../acls 
/iscsi/iqn.20...t01/tpg1/acls> create iqn.2015-06.world.server:www.server.world
Created Node ACL for iqn.2015-06.world.server:www.server.world
Created mapped LUN 0.
/iscsi/iqn.20...t01/tpg1/acls> cd iqn.2015-06.world.server:www.server.world/
/iscsi/iqn.20....server.world> set auth userid=foo
Parameter userid is now 'foo'.
/iscsi/iqn.20....server.world> set auth password=bar
Parameter password is now 'bar'.
/iscsi/iqn.20....server.world> exit
Global pref auto_save_on_exit=true
Last 10 configs saved in /etc/target/backup.
Configuration saved to /etc/target/saveconfig.json
[root@localhost /]# service iscsid restart
Redirecting to /bin/systemctl restart iscsid.service
[root@localhost /]# service iscsi restart
Redirecting to /bin/systemctl restart iscsi.service

Here’s the structure (open image in a new window to see it full size):

Discovery seems to work fine:

[root@linuxbox ~]# iscsiadm -m discovery -t sendtargets -p 10.0.0.60
10.0.0.60:3260,1 iqn.2015-06.world.server:storage.target01

However, when I try to connect, I get this authorization failure message:

[root@linuxbox ~]# iscsiadm -m node --targetname "iqn.2015-06.world.server:storage.target01" --portal "10.0.0.60:3260" --login 
Logging in to [iface: default, target: iqn.2015-06.world.server:storage.target01, portal: 10.0.0.60,3260] (multiple)
iscsiadm: Could not login to [iface: default, target: iqn.2015-06.world.server:storage.target01, portal: 10.0.0.60,3260].
iscsiadm: initiator reported error (24 - iSCSI login failed due to authorization failure)
iscsiadm: Could not log into all portals

Ben.T. George

Sr. Technical Engineer

• Linux
• Ubuntu: iscsiadm: initiator reported error (24.

Feb.07

Ubuntu: iscsiadm: initiator reported error (24 – iSCSI login failed due to authorization failure)

i was trying to export one iscsi share from centOS server and my client is Ubuntu server.

well i know this will work on CentOS/Redhat without any changes and i was under impression that , on ubuntu also will get same behavior.

On CentOS, below are the commands to create Iscsi target

Server

Install and enable services:
yum -y install target*
systemctl start target && systemctl enable target
# targetcli /backstores/block create name=ubuntu-iscsi dev=/dev/cl_centos/lv_scsi
# targetcli /iscsi create iqn.2017-02.com.example.kw:centos
# targetcli /iscsi/iqn.2017-02.com.example.kw:centos/tpg1/acls create iqn.2017-02.com.example.kw:ubuntu-archive
# targetcli /iscsi/iqn.2017-02.com.example.kw:centos/tpg1/luns create /backstores/block/ubuntu-iscsi
# targetcli /iscsi/iqn.2017-02.com.example.kw:centos/tpg1/portals delete 0.0.0.0 3260
# targetcli /iscsi/iqn.2017-02.com.example.kw:centos/tpg1/portals create 192.168.1.66 3260
# targetcli saveconfig

Allow TCP port if firewalld is enabled.

# firewall-cmd –permanent –add-port=3260/tcp

All set from from target(server) side.

Client

On client side install iscsi packages

# apt-get -y install open-iscsi

edit /etc/iscsi/iscsid.conf and change like below

# To request that the iscsi initd scripts startup a session set to “automatic”.
# node.startup = automatic
node.startup = automatic

and i manually edited /etc/iscsi/initiatorname.iscsi , added iqn number taken from server.Which is

# service iscsid restart

Do the discovery

# iscsiadm -m discovery –type sendtargets –portal 192.168.1.66

And finally Login to target

# iscsiadm -m node –targetname iqn.2017-02.com.example.kw:centos –portal 192.168.1.66 –login

After this , the newly added disk will be displayed under fdisk. Below is the syslog

Источник

login iqn.2003-01.com.redhat.iscsi-gw:ceph-igw failed
I don’t understand gwcli set chap under client name.

1. does iscsiadm need to specify the name of the client when it login to target?
   2.if the client name have some rules，such astarget-name:client-name？

Login result:
iscsiadm -m node -T iqn.2003-01.com.redhat.iscsi-gw:ceph-igw -l
Logging in to [iface: default, target: iqn.2003-01.com.redhat.iscsi-gw:ceph-igw, portal: 172.16.121.131,3260] (multiple)
Logging in to [iface: default, target: iqn.2003-01.com.redhat.iscsi-gw:ceph-igw, portal: 172.16.121.130,3260] (multiple)
iscsiadm: Could not login to [iface: default, target: iqn.2003-01.com.redhat.iscsi-gw:ceph-igw, portal: 172.16.121.131,3260].
iscsiadm: initiator reported error (24 — iSCSI login failed due to authorization failure)
iscsiadm: Could not login to [iface: default, target: iqn.2003-01.com.redhat.iscsi-gw:ceph-igw, portal: 172.16.121.130,3260].
iscsiadm: initiator reported error (24 — iSCSI login failed due to authorization failure)
iscsiadm: Could not log into all portals

Prepare for login:
vi /etc/iscsi/iscsid.conf
node.session.auth.authmethod = CHAP
node.session.auth.username = consumer
node.session.auth.password = 012345678912

/> ls
o- / . [. ]
o- clusters . [Clusters: 1]
| o- c1 . [HEALTH_WARN]
| o- pools . [Pools: 1]
| | o- rbd . [(x3), Commit: 384M/6G (6%), Used: 3K]
| o- topology . [OSDs: 1,MONs: 1]
o- disks . [384M, Disks: 3]
| o- rbd.disk_1 . [disk_1 (128M)]
| o- rbd.disk_2 . [disk_2 (128M)]
| o- rbd.disk_3 . [disk_3 (128M)]
o- iscsi-target . [Targets: 1]
o- iqn.2003-01.com.redhat.iscsi-gw:ceph-igw . [Gateways: 2]
o- gateways . [Up: 2/2, Portals: 2]
| o- node0 . [172.16.121.130 (UP)]
| o- node1 . [172.16.121.131 (UP)]
o- host-groups . [Groups : 0]
o- hosts . [Hosts: 3]
o- iqn.1994-05.com.redhat:rh7-client . [Auth: None, Disks: 0(0b)]
o- iqn.1994-05.com.redhat:xx . [Auth: CHAP, Disks: 1(128M)]
| o- lun 0 . [rbd.disk_1(128M), Owner: node1]
o- iqn.2003-01.com.redhat.iscsi-gw:nike [Auth: CHAP, Disks: 1(128M)]
o- lun 0 . [rbd.disk_2(128M), Owner: node0]

• (_get_rbd_config) config object contains ‘ <
  «clients»: <
  «iqn.1994-05.com.redhat:rh7-client»:<
  «auth»: <
  «chap»: «»
  >,
  «created»: «2017/08/28 06:08:53»,
  «group_name»: «»,
  «luns»: <>,
  «updated»: «2017/08/28 06:08:53»
  >,
  «iqn.1994-05.com.redhat:xx»:<
  «auth»: <
  «chap»: «consumer/012345678912»
  >,
  «created»: «2017/08/29 03:05:00»,
  «group_name»: «»,
  «luns»: <
  «rbd.disk_1»: <
  «lun_id»: 0
  >
  >,
  «updated»: «2017/08/29 06:20:45»
  >,
  «iqn.2003-01.com.redhat.iscsi-gw:nike»:<
  «auth»: <
  «chap»: «consumer/012345678912»
  >,
  «created»: «2017/08/29 07:07:28»,
  «group_name»: «»,
  «luns»: <
  «rbd.disk_2»: <
  «lun_id»: 0
  >
  >,
  «updated»: «2017/08/29 07:11:57»
  >
  >,
  «created»: «2017/08/28 03:26:42»,
  «disks»: <
  «rbd.disk_1»: <
  «created»: «2017/08/29 02:41:52»,
  «image»: «disk_1»,
  «owner»: «node1»,
  «pool»: «rbd»,
  «pool_id»: 1,
  «updated»: «2017/08/29 02:41:52»,
  «wwn»: «95c0d3a9-96cf-4158-9341-88020e2cc8d7»
  >,
  «rbd.disk_2»: <
  «created»: «2017/08/29 03:02:49»,
  «image»: «disk_2»,
  «owner»: «node0»,
  «pool»: «rbd»,
  «pool_id»: 1,
  «updated»: «2017/08/29 03:02:49»,
  «wwn»: «8383bdfa-1e94-4a94-ae59-c33a0dd7a737»
  >,
  «rbd.disk_3»: <
  «created»: «2017/08/29 03:03:51»,
  «image»: «disk_3»,
  «owner»: «node1»,
  «pool»: «rbd»,
  «pool_id»: 1,
  «updated»: «2017/08/29 03:03:51»,
  «wwn»: «d80cc287-4b16-408b-932a-b5ede4e5bc96»
  >
  >,
  «epoch»: 20,
  «gateways»: <
  «created»: «2017/08/28 03:31:58»,
  «ip_list»: [
  «172.16.121.131»,
  «172.16.121.130»
  ],
  «iqn»: «iqn.2003-01.com.redhat.iscsi-gw:ceph-igw»,
  «node0»: <
  «active_luns»: 1,
  «created»: «2017/08/28 04:00:44»,
  «gateway_ip_list»: [
  «172.16.121.131»,
  «172.16.121.130»
  ],
  «inactive_portal_ips»: [
  «172.16.121.131»
  ],
  «iqn»: «iqn.2003-01.com.redhat.iscsi-gw:ceph-igw»,
  «portal_ip_address»: «172.16.121.130»,
  «tpgs»: 2,
  «updated»: «2017/08/29 03:02:49»
  >,
  «node1»: <
  «active_luns»: 2,
  «created»: «2017/08/28 03:33:26»,
  «gateway_ip_list»: [
  «172.16.121.131»,
  «172.16.121.130»
  ],
  «inactive_portal_ips»: [
  «172.16.121.130»
  ],
  «iqn»: «iqn.2003-01.com.redhat.iscsi-gw:ceph-igw»,
  «portal_ip_address»: «172.16.121.131»,
  «tpgs»: 2,
  «updated»: «2017/08/29 03:03:51»
  >
  >,
  «groups»: <>,
  «updated»: «2017/08/29 07:11:57»,
  «version»: 3
  >’

The text was updated successfully, but these errors were encountered:

Источник

iSCSI Setup with FlashArray

This blog post covers the steps required to connect FlashArray volumes over iSCSI on RHEL variant Linux systems (RHEL, Oracle Linux, CentOS).

Required package on RHEL for iSCSI
iscsi-initiator-utils

Multipathing package
device-mapper-multipath

High level process with iSCSI

1. Setup iSCSI at the initiator
2. Setup Host at the FlashArray level
3. Discover the iSCSI targets
4. Login to the iSCSI targets
5. Create volumes, attach to the hosts, scan them and create the filesystems

1. To set up iSCSI at the host level, install the package iscsi-initiator-utils and start the iscsi service. Make sure to include the multipathing package as well.

] # systemctl enable iscsid Created symlink from /etc/systemd/system/multi-user.target.wants/iscsid.service to /usr/lib/systemd/system/iscsid.service.

] # systemctl start iscsid

] # systemctl status iscsid ● iscsid.service — Open-iSCSI

2. Setup the host at the FlashArray level by first getting the initiator’s IQN which can be found at /etc/iscsi/initiatorname.iscsi

]# cat /etc/iscsi/initiatorname.iscsi
InitiatorName=iqn.1988-12.com.oracle:abd254f8bba0

Go the Pure FlashArray, click Storage on the left frame and select the Hosts tab. Click the + sign on the right side to create a new host. Provide the IQN name you got from the initiator.

Configure IQN for a host in FlashArray

3. On the host, discover the iSCSI targets

$ iscsiadm -m discovery -t st -p

] # iscsiadm -m discovery -t st -p 192.168.228.24

4. Create a volume on Pure FlashArray and attach to the host. Without a volume/lun attached to the host, trying to login to the target will result in following errors.

iscsiadm -m node –targetname iqn.2010-06.com.purestorage:flasharray.7b87f11aad2d06c8 -p 192.168.154.254 -l

5. Using the IQN information of the target, login to iSCSI target using iscsiadm command.

iscsiadm -m node –targetname -p –login

] # iscsiadm -m node —targetname iqn.2010-06.com.purestorage:flasharray.6fb3576b8af88fd5 -p 192.168.228.24 —login

Login on all the iSCSI ports on the target. As of now, we have connected only to the first iSCSI target IP and hence Purity GUI shows Uneven paths. Run the above login command across all available iscsi paths .

To login automatically on the host startup, run the following command to update the config at the host level. Do it on all the available iSCSI target IP addresses.

iscsiadm -m node -T -p –op update -n node.startup -v automatic

] # iscsiadm -m node —targetname iqn.2010-06.com.purestorage:flasharray.6fb3576b8af88fd5 -p 192.168.228.27 —op update -n node.startup -v automatic

] # iscsiadm -m node —targetname iqn.2010-06.com.purestorage:flasharray.6fb3576b8af88fd5 -p 192.168.228.26 —op update -n node.startup -v automatic

] # iscsiadm -m node —targetname iqn.2010-06.com.purestorage:flasharray.6fb3576b8af88fd5 -p 192.168.228.25 —op update -n node.startup -v automatic

] # iscsiadm -m node —targetname iqn.2010-06.com.purestorage:flasharray.6fb3576b8af88fd5 -p 192.168.228.24 —op update -n node.startup -v automatic

You can verify if the iSCSI setup is successful by checking at the FlashArray GUI. Click Health on the left frame and go to the Connections tab. Look for the Paths against the host you just added. If it shows “Unused Port” and if you don’t see any entries against the host initiator it means the host has not logged into the target.

Clicking on the “Unused Port” shows the connection map of the host ports.

After discovering and logging into the target from all the initiators, we can see that the Paths shows Redundant across all of them.

5. Create the volumes on Pure Flasharray and attach to the host.

Источник

Seneca-CD Research Project

To see a working iSCSI model in action, I’m going to have to have a remote server set up as an iSCSI Initiator Node. Though we do have a second machine, we decided that I should work in a virtual environment instead. So, I’m going to create a Virtual Machine by following the instructions on this post, and they’re going to be my remote servers for this experiment.

My main resources for these next few steps are:

Step 1: Set-up a Virtual Machine and Install “iscsi-initiator-utils”

Funny thing, I’ve set up my virtual machine, but my host can’t interact with it! No pings, no ssh, nothing. Some research later, I discovered that it was because I didn’t properly connect the VM to my host network adapter. An excellent tutorial on the subject can be found here (thanks to Haydn Solomon).

Now for some reason my virtual machine can’t communicate with its host machine. *sigh*

For now, I’m going to try to use my localhost as both a Target and an Initiator.

Installing the utilities to manage an iSCSI initiator is pretty easy with YUM:

Although, as it turns out, my machine already has these preloaded.

Step 2: Setting the Initiator Authentication

Similarly to tgt-admin, there is a tool called iscsiadm which allows us to do general administration for open-iscsi Initiator Nodes.

I’ll edit the open-iscsi daemon configuration file to contain the necessary target authentication details (as root):

First, enable CHAP authentication by uncommenting the line:

Then, add the CHAP Initiator and Target authentication details created on the Target node:

It is worth noting that the discovery of a Target itself by an Initiator node can be authenticated through CHAP in a similar way, in the same config file.

Step 3: Discovering the Target(s)

Now we get to play with iscsiadm:

1. -m discovery is setting the operation mode to search for Targets
2. -t sendtargets is telling the Targets to return their names
3. -p 10.0.0.21 is explicitly defining which IP or host to scan for Target nodes.

And now I’m receiving an error message:

To save time, I specified localhost instead of an IP address and here’s what happened:

Good! Now to make sure the iSCSI daemon is set to start on boot:

I’ll check to make sure the target node is still registering with:

So far so good! Target acquired.

Step 4: Login to the Target, and Check Partitions

All that’s left is to log in to the Target node. If this is successful, I should be able to see the iSCSI partition I created for the Target Node as one of my local drives.

Logging in is simple after editing the .conf file:

or SHOULD be, except I’m getting this error:

After spending some time with the settings, I’ve discovered that Target Authentication (the credentials the Initiator provides to get access to the Target) is working properly, but Initiator Authentication (the credentials the Target provides to the Initiator) is causing some problems.

Rather than waste too much time here, I’m going to disable Initiator (also known as outgoing ) authentication by removing the outgoinguser details from /etc/tgt/targets.conf thusly:

And then disable outgoing authentication in /etc/iscsi/iscsid.conf:

Now, I must rediscover the Target Node, and then try to log in:

This time, it seems to have worked properly.

To confirm, I’ll logout of the session, check my partitions, then log in and redo the check:

It works!! Line 29 shows a new partition that only exists when the iSCSI session is active!

Conclusion

This was tough. There are some serious unknowns here, mainly because of the different tools involved. For next steps, it would be best to delve into the documentation of these tools and the projects associated with them so that I can create a substantial test conditions. In the meantime however, it is working!

Источник

login iqn.2003-01.com.redhat.iscsi-gw:ceph-igw failed
I don’t understand gwcli set chap under client name.

1. does iscsiadm need to specify the name of the client when it login to target?
   2.if the client name have some rules，such astarget-name:client-name？

Login result:
iscsiadm -m node -T iqn.2003-01.com.redhat.iscsi-gw:ceph-igw -l
Logging in to [iface: default, target: iqn.2003-01.com.redhat.iscsi-gw:ceph-igw, portal: 172.16.121.131,3260] (multiple)
Logging in to [iface: default, target: iqn.2003-01.com.redhat.iscsi-gw:ceph-igw, portal: 172.16.121.130,3260] (multiple)
iscsiadm: Could not login to [iface: default, target: iqn.2003-01.com.redhat.iscsi-gw:ceph-igw, portal: 172.16.121.131,3260].
iscsiadm: initiator reported error (24 — iSCSI login failed due to authorization failure)
iscsiadm: Could not login to [iface: default, target: iqn.2003-01.com.redhat.iscsi-gw:ceph-igw, portal: 172.16.121.130,3260].
iscsiadm: initiator reported error (24 — iSCSI login failed due to authorization failure)
iscsiadm: Could not log into all portals

Prepare for login:
vi /etc/iscsi/iscsid.conf
node.session.auth.authmethod = CHAP
node.session.auth.username = consumer
node.session.auth.password = 012345678912

restart iscsid

/> ls
o- / …………………………………………………….. […]
o- clusters ……………………………………… [Clusters: 1]
| o- c1 …………………………………………. [HEALTH_WARN]
| o- pools ……………………………………….. [Pools: 1]
| | o- rbd ………………. [(x3), Commit: 384M/6G (6%), Used: 3K]
| o- topology ………………………………. [OSDs: 1,MONs: 1]
o- disks ……………………………………… [384M, Disks: 3]
| o- rbd.disk_1 ………………………………… [disk_1 (128M)]
| o- rbd.disk_2 ………………………………… [disk_2 (128M)]
| o- rbd.disk_3 ………………………………… [disk_3 (128M)]
o- iscsi-target …………………………………… [Targets: 1]
o- iqn.2003-01.com.redhat.iscsi-gw:ceph-igw ……….. [Gateways: 2]
o- gateways …………………………… [Up: 2/2, Portals: 2]
| o- node0 ……………………………. [172.16.121.130 (UP)]
| o- node1 ……………………………. [172.16.121.131 (UP)]
o- host-groups ………………………………… [Groups : 0]
o- hosts ……………………………………….. [Hosts: 3]
o- iqn.1994-05.com.redhat:rh7-client . [Auth: None, Disks: 0(0b)]
o- iqn.1994-05.com.redhat:xx ……. [Auth: CHAP, Disks: 1(128M)]
| o- lun 0 ………………… [rbd.disk_1(128M), Owner: node1]
o- iqn.2003-01.com.redhat.iscsi-gw:nike [Auth: CHAP, Disks: 1(128M)]
o- lun 0 ………………… [rbd.disk_2(128M), Owner: node0]

rbd-target-api.log:

• (_get_rbd_config) config object contains ‘{
  «clients»: {
  «iqn.1994-05.com.redhat:rh7-client»: {
  «auth»: {
  «chap»: «»
  },
  «created»: «2017/08/28 06:08:53»,
  «group_name»: «»,
  «luns»: {},
  «updated»: «2017/08/28 06:08:53»
  },
  «iqn.1994-05.com.redhat:xx»: {
  «auth»: {
  «chap»: «consumer/012345678912»
  },
  «created»: «2017/08/29 03:05:00»,
  «group_name»: «»,
  «luns»: {
  «rbd.disk_1»: {
  «lun_id»: 0
  }
  },
  «updated»: «2017/08/29 06:20:45»
  },
  «iqn.2003-01.com.redhat.iscsi-gw:nike»: {
  «auth»: {
  «chap»: «consumer/012345678912»
  },
  «created»: «2017/08/29 07:07:28»,
  «group_name»: «»,
  «luns»: {
  «rbd.disk_2»: {
  «lun_id»: 0
  }
  },
  «updated»: «2017/08/29 07:11:57»
  }
  },
  «created»: «2017/08/28 03:26:42»,
  «disks»: {
  «rbd.disk_1»: {
  «created»: «2017/08/29 02:41:52»,
  «image»: «disk_1»,
  «owner»: «node1»,
  «pool»: «rbd»,
  «pool_id»: 1,
  «updated»: «2017/08/29 02:41:52»,
  «wwn»: «95c0d3a9-96cf-4158-9341-88020e2cc8d7»
  },
  «rbd.disk_2»: {
  «created»: «2017/08/29 03:02:49»,
  «image»: «disk_2»,
  «owner»: «node0»,
  «pool»: «rbd»,
  «pool_id»: 1,
  «updated»: «2017/08/29 03:02:49»,
  «wwn»: «8383bdfa-1e94-4a94-ae59-c33a0dd7a737»
  },
  «rbd.disk_3»: {
  «created»: «2017/08/29 03:03:51»,
  «image»: «disk_3»,
  «owner»: «node1»,
  «pool»: «rbd»,
  «pool_id»: 1,
  «updated»: «2017/08/29 03:03:51»,
  «wwn»: «d80cc287-4b16-408b-932a-b5ede4e5bc96»
  }
  },
  «epoch»: 20,
  «gateways»: {
  «created»: «2017/08/28 03:31:58»,
  «ip_list»: [
  «172.16.121.131»,
  «172.16.121.130»
  ],
  «iqn»: «iqn.2003-01.com.redhat.iscsi-gw:ceph-igw»,
  «node0»: {
  «active_luns»: 1,
  «created»: «2017/08/28 04:00:44»,
  «gateway_ip_list»: [
  «172.16.121.131»,
  «172.16.121.130»
  ],
  «inactive_portal_ips»: [
  «172.16.121.131»
  ],
  «iqn»: «iqn.2003-01.com.redhat.iscsi-gw:ceph-igw»,
  «portal_ip_address»: «172.16.121.130»,
  «tpgs»: 2,
  «updated»: «2017/08/29 03:02:49»
  },
  «node1»: {
  «active_luns»: 2,
  «created»: «2017/08/28 03:33:26»,
  «gateway_ip_list»: [
  «172.16.121.131»,
  «172.16.121.130»
  ],
  «inactive_portal_ips»: [
  «172.16.121.130»
  ],
  «iqn»: «iqn.2003-01.com.redhat.iscsi-gw:ceph-igw»,
  «portal_ip_address»: «172.16.121.131»,
  «tpgs»: 2,
  «updated»: «2017/08/29 03:03:51»
  }
  },
  «groups»: {},
  «updated»: «2017/08/29 07:11:57»,
  «version»: 3
  }’

I am attempting to setup an iSCSI target, with one block LUN which is a zfs zvol on a CentOS 7 machine. I’ve only ever used iscsitarget and the /etc/iet/ietd.conf file on ubuntu systems.

I have this (from targetcli):

/iscsi> ls
o- iscsi .............................................................................................................. [Targets: 1]
  o- iqn.2019-09.com.nas:main ............................................................................................ [TPGs: 1]
    o- tpg1 ................................................................................................. [no-gen-acls, no-auth]
      o- acls ............................................................................................................ [ACLs: 1]
      | o- iqn.2019-09.com.nas:main:client ........................................................................ [Mapped LUNs: 1]
      |   o- mapped_lun0 .................................................................................. [lun0 block/block1 (rw)]
      o- luns ............................................................................................................ [LUNs: 1]
      | o- lun0 ....................................................................... [block/block1 (/dev/zd0) (default_tg_pt_gp)]
      o- portals ...................................................................................................... [Portals: 1]
        o- 0.0.0.0:3260 ....................................................................................................... [OK]
/iscsi> 

And I ran this:

/iscsi/iqn.20...nas:main/tpg1> set attribute authentication=0
Parameter authentication is now '0'.
/iscsi/iqn.20...nas:main/tpg1> 

However, a Windows client refuses to connect, and from an Ubuntu machine I receive this authorization error:

iscsiadm -m node --targetname "iqn.2019-09.com.nas:main" --portal "192.168.0.146" --login
Logging in to [iface: default, target: iqn.2019-09.com.nas:main, portal: 192.168.0.146,3260] (multiple)
iscsiadm: Could not login to [iface: default, target: iqn.2019-09.com.nas:main, portal: 192.168.0.146,3260].
iscsiadm: initiator reported error (24 - iSCSI login failed due to authorization failure)
iscsiadm: Could not log into all portals

I was not looking to use any CHAP authentication, but I guess if I have to I can. targetcli is entirely new to me, not sure what is missing and from looking around that set attribute command from within tpg1 should have done the trick.

From https://www.systutorials.com/docs/linux/man/8-targetcli/

No Authentication Authentication is disabled by clearing the TPG
«authentication» attribute: set attribute authentication=0. Although
initiator names are trivially forgeable, generate_node_acls still
works here to either ignore user-defined ACLs and allow all, or check
that an ACL exists for the connecting initiator

Perhaps I named this incorrectly? As under «acls» I have iqn.2019-09.com.nas:main:client but a discovery from clients only returns iqn.2019-09.com.nas:main

This is the guide I used to setup:

RHEL7: Configure a system as either an iSCSI target or initiator that persistently mounts an iSCSI target.

Hi,
I am sharing storage between 2 machines, follow the steps and stuck in the last of sharing storage. I am using Oracle Linux 7.9 on both machines (storage and node) and sharing storage using targetcli on it, all the things run smoothly. I discovered the storage from node but when trying to login, it shows an this error.
Please Guide
root@racnode1 iscsi]# iscsiadm -m discovery -t sendtargets -p 192.168.1.15
192.168.1.15:3260,1 iqn.2003-01.org.linux-iscsi.storage.x8664:sn.cf46131fa4fe

Error:
————
[root@racnode1 iscsi]# iscsiadm -m node -T iqn.2003-01.org.linux-iscsi.storage.x8664:sn.cf46131fa4fe 192.168.1.15 -l
Logging in to [iface: default, target: iqn.2003-01.org.linux-iscsi.storage.x8664:sn.cf46131fa4fe, portal: 192.168.1.15,3260] (multiple)
iscsiadm: Could not login to [iface: default, target: iqn.2003-01.org.linux-iscsi.storage.x8664:sn.cf46131fa4fe, portal: 192.168.1.15,3260].
iscsiadm: initiator reported error (24 — iSCSI login failed due to authorization failure)
iscsiadm: Could not log into all portals
==============================================================
Other info:
========
ssh configured, firewall stopped, pining successfully

Node iqn:
—————
[root@racnode1 iscsi]# cat /etc/iscsi/initiatorname.iscsi
InitiatorName=iqn.2017-02.tn.wadhahdaouehi.node:racnode1

Storage iqn:
———————
[root@storage ~]# cat /etc/iscsi/initiatorname.iscsi
InitiatorName=iqn.2003-01.org.linux-iscsi.storage.x8664:sn.cf46131fa4fe

Storage:
———————
[root@storage ~]# targetcli
targetcli shell version 2.1.53
Copyright 2011-2013 by Datera, Inc and others.
For help on commands, type ‘help’.
/> ls
o- / …………………………………………………………………………………………………………. […]
o- backstores ……………………………………………………………………………………………….. […]
| o- block …………………………………………………………………………………….. [Storage Objects: 1]
| | o- newlun_sdb …………………………………