Client can't see LUN from openSuSE iSCSI

**jcdick1** · 10-Aug-2020, 05:32

I have a 2TB logical drive on openSuSE I am trying to export as a LUN with iSCSI LIO. I've created a partition on it with a "Linux" device type, but not formatted it or given it a mount point. In the YaST iSCSI LIO server config, I point the LUN configuration to the device partition - /dev/sdc1 - and the LIO config does not seem to have an issue with this. However, after completing the configuration and exiting the tool in YaST, the client can only see the target IQN. It cannot see any LUNs beneath that. I am not sure where to look for further information beyond the client's message of "No LUNs were found on <hostname/IP>."

Any help is appreciated.

**jcdick1** · 10-Aug-2020, 20:50

Using targetcli, I do show the device accepted as a LUN:

Code:

/> ls
o- / ..................................................................... [...]
  o- backstores .......................................................... [...]
  | o- block .............................................. [Storage Objects: 1]
  | | o- dev-sdc1 .................... [/dev/sdc1 (1.8TiB) write-thru activated]
  | |   o- alua ............................................... [ALUA Groups: 1]
  | |     o- default_tg_pt_gp ................... [ALUA state: Active/optimized]
  | o- fileio ............................................. [Storage Objects: 0]
  | o- pscsi .............................................. [Storage Objects: 0]
  | o- ramdisk ............................................ [Storage Objects: 0]
  | o- rbd ................................................ [Storage Objects: 0]
  o- iscsi ........................................................ [Targets: 1]
  | o- iqn.2020-08.net.domain.host:881adfdfb3fc7299efcf ..... [TPGs: 1]
  |   o- tpg1 .............................................. [gen-acls, no-auth]
  |     o- acls ...................................................... [ACLs: 0]
  |     o- luns ...................................................... [LUNs: 1]
  |     | o- lun0 .............. [block/dev-sdc1 (/dev/sdc1) (default_tg_pt_gp)]
  |     o- portals ................................................ [Portals: 1]
  |       o- 192.168.1.10:3260 ............................................ [OK]
  o- loopback ..................................................... [Targets: 0]
  o- srpt ......................................................... [Targets: 0]
  o- vhost ........................................................ [Targets: 0]
  o- xen-pvscsi ................................................... [Targets: 0]

**tsu2** · 10-Aug-2020, 23:51

I haven't looked implemented iSCSI recently, but I do know over the past couple years there have been substantial changes.
I didn't have problems before...

By default only the iSCSI client is installed.
From your post, I assume you installed the YaST iSCSI LIO Server module, and made changes there.
Are you saying that after setting up using the Server module, the LUNs don't show in the YaST iSCSI initiator module?

TSU

**jcdick1** · 11-Aug-2020, 08:42

Originally Posted by tsu2

I haven't looked implemented iSCSI recently, but I do know over the past couple years there have been substantial changes.
I didn't have problems before...

By default only the iSCSI client is installed.
From your post, I assume you installed the YaST iSCSI LIO Server module, and made changes there.
Are you saying that after setting up using the Server module, the LUNs don't show in the YaST iSCSI initiator module?

TSU

Obviously I'm not trying to mount the device on the same host as the iSCSI server, but I have used both the YaST module and the targetcli tool to configure the device as an iSCSI LUN attached to the configured IQN, and none of the iSCSI clients on my network can see that LUN. After configuration of the target IQN and LUN, the service is restarted to export that LUN. The hosts almost immediately discover the IQN when they scan the host IP, but they never see the LUN behind that.