Based on the output below give the target a few minutes before you attempt to have the Microsoft initiator log in.

You'll notice that the "Status" is currently "offline". Here's the ugly details of what's happening. I was kind of between a rock and a hard place for the initialization. The daemon needs to make sure all of the space for a LU is available. This requires that it write every block in the backing store if it's a regular file. If the daemon just writes the last block a hole-y file is created and while this is cool it presents problems (ask if you'd like more detail). So, there are two choices regarding initialization, either block the CLI from returning until complete or quickly return while the initialization is done in the background. I choose the latter. If an initiator attempts to connect to the target while the initialization occurs it fails to see the underlying LU. Once the LU completes the initialization it's notified of an inventory change such that it can discovery the devices again. I know this rediscovery works with Solaris as I tested it. I have not tested it with Microsoft so one of two possibilities exist. a) Microsoft doesn't handle this condition or b) the device hadn't completed initialization before you thought something was wrong. I wouldn't give odds one way or another.

So, wait until the device is "online" and then see if the Microsoft initiator doesn't connect.

Hope this helps.

On Apr 9, 2007, at 9:53 AM, Lan Tran wrote:

Hi, I'm new to Solaris OS.

I'm using MS initiator 2.3 to connect to a target on snv_61. Initiator can connect to target ok, but "Disk Management" on XP Pro does not see the target. I have no issue with a target created on FreeBSD-6.2 using same initator. Here is how I created the target on Solaris:
# mkdir -p /export/home/iscsi
# iscsitadm modify admin -d /export/home/iscsi
# iscsitadm create target -z 4g solaris
# iscsitadm list target -v solaris
Target: solaris
iSCSI Name: iqn.1986-03.com.sun:02:fec6603f-8b62-670f-cbe5- edd4794c142d.solaris
   Connections: 1
       Initiator:
           iSCSI Name: iqn.1991-05.com.microsoft:test.pc
           Alias: unknown
   ACL list:
   TPGT list:
   LUN information:
       LUN: 0
           GUID: 010000b0d0d1b3ae00002a00461a540e
           VID: SUN
           PID: SOLARIS
           Type: disk
           Size: 4.0G
           Status: offline

# svcs | grep isc
online         11:28:50 svc:/system/iscsitgt:default

Are there known issues with MS initiator 2.3? Has anyone gotten this combo to work?

Thanks,
LT
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

----
Rick McNeal

"If ignorance is bliss, this lesson would appear to be a deliberate attempt on your part to deprive me of happiness, the pursuit of which is my unalienable right according to the Declaration of Independence. I therefore assert my patriotic prerogative not to know this material. I'll be out on the playground." -- Calvin


_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

Reply via email to