iSCSI target problem

  • Follow


Hi all,

I was sick with iSCSI target and initiator on Solaris 10 x86 (same machine).

Steps:
1. svcadm enable svc:/system/iscsitgt:default
2. svcadm enable svc:/network/iscsi_initiator:default
(target side)
3. iscsitadm create target --type raw --backing-store /dev/dsk/c1t1d0p0 c1t1d0p0
4. iscsitadm list target -v
[iqn.1986-03.com.sun:02:784d74bd-cd5c-c03e-8c59-85ea587752e9.c1t1d0p0]

(initiator side)
5. iscsiadm list initiator-node
[iqn.1986-03.com.sun:01:e000000078eb.47fa31de]
6. iscsiadm modify initiator-node -H solaris -N iqn.1986-03.com.sun:01:e000000078eb.47fa31de
7. iscsiadm modify initiator-node -a CHAP
8. iscsiadm modify initiator-node -C

(target side)
9. iscsitadm create initiator -n iqn.1986-03.com.sun:02:784d74bd-cd5c-c03e-8c59-85ea587752e9.c1t1d0p0 iqn.1986-03.com.sun:01:e000000078eb.47fa31de
10. iscsitadm modify initiator -H solaris iqn.1986-03.com.sun:01:e000000078eb.47fa31de
11. iscsitadm modify initiator -C iqn.1986-03.com.sun:01:e000000078eb.47fa31de

(initiator side)
12. iscsiadm add discovery-address 192.168.138.129
13. iscsiadm modify discovery --sendtargets enable

Now step 13 gets the following error:
=============================================
iscsi: [ID 409607 kern.warning] WARNING: iscsi connection(4) login failed - failed to receive login response - timeout
iscsi: [ID 114404 kern.notice] NOTICE: iscsi discovery failure - SendTargets (192.168.138.129)
=============================================

Anyone can resolve sendtargets problem?  I have no problem
to make CentOS iSCSI target and Solaris iSCSI initiator.

Thank you very much.

--
Johnson Chow

0
Reply Mr 4/7/2008 3:23:45 PM

Mr. Chow Wing Siu schrieb:
> Hi all,
> 
> I was sick with iSCSI target and initiator on Solaris 10 x86 (same machine).
> 
> Steps:
> 1. svcadm enable svc:/system/iscsitgt:default
> 2. svcadm enable svc:/network/iscsi_initiator:default
> (target side)
> 3. iscsitadm create target --type raw --backing-store /dev/dsk/c1t1d0p0 c1t1d0p0
> 4. iscsitadm list target -v
> [iqn.1986-03.com.sun:02:784d74bd-cd5c-c03e-8c59-85ea587752e9.c1t1d0p0]
> 
> (initiator side)
> 5. iscsiadm list initiator-node
> [iqn.1986-03.com.sun:01:e000000078eb.47fa31de]
> 6. iscsiadm modify initiator-node -H solaris -N iqn.1986-03.com.sun:01:e000000078eb.47fa31de
> 7. iscsiadm modify initiator-node -a CHAP
> 8. iscsiadm modify initiator-node -C
> 
> (target side)
> 9. iscsitadm create initiator -n iqn.1986-03.com.sun:02:784d74bd-cd5c-c03e-8c59-85ea587752e9.c1t1d0p0 iqn.1986-03.com.sun:01:e000000078eb.47fa31de
> 10. iscsitadm modify initiator -H solaris iqn.1986-03.com.sun:01:e000000078eb.47fa31de
> 11. iscsitadm modify initiator -C iqn.1986-03.com.sun:01:e000000078eb.47fa31de
> 
> (initiator side)
> 12. iscsiadm add discovery-address 192.168.138.129
> 13. iscsiadm modify discovery --sendtargets enable
> 
> Now step 13 gets the following error:
> =============================================
> iscsi: [ID 409607 kern.warning] WARNING: iscsi connection(4) login failed - failed to receive login response - timeout
> iscsi: [ID 114404 kern.notice] NOTICE: iscsi discovery failure - SendTargets (192.168.138.129)
> =============================================
> 


I think you miss to allow the initiator to access the target with
"iscsitadm modify target --acl" on target side.

Wolfgang
0
Reply Wolfgang 4/7/2008 9:59:09 PM


Wolfgang <wtrappe@AT.web.de> wrote:
> I think you miss to allow the initiator to access the target with
> "iscsitadm modify target --acl" on target side.
> Wolfgang
-----------------------------

I add your provided command line.  I get the same error message.

--
Johnson Chow
0
Reply Mr 4/8/2008 12:39:51 AM

Mr. Chow Wing Siu schrieb:
> Wolfgang <wtrappe@AT.web.de> wrote:
>> I think you miss to allow the initiator to access the target with
>> "iscsitadm modify target --acl" on target side.
>> Wolfgang
> -----------------------------
> 
> I add your provided command line.  I get the same error message.
> 
> --
> Johnson Chow

I have only created a target by sharescsi a zfs volume, which i can use 
without acl and without problems. Maybe you can make a zfs target and 
compare the target parameters with yours.

Wolfgang
0
Reply Wolfgang 4/9/2008 9:01:54 PM

3 Replies
294 Views

(page loaded in 0.082 seconds)

Similiar Articles:






7/29/2012 8:56:03 AM


Reply: