I am new to the SAN environment, and most especially to the iSCSI way of doing things. I have the iSCSI protocol enabled on my filer, and I have the Microsoft iSCSI initiator downloaded and installed on my PC. From the filer, I have created a couple LUNs on my filer, I have created igroups, mapped the LUNs to the igroups, set the create_ucode option to on, and started the iSCSI service. On the Windows system, I have added the target portal, logged on, and I can see an active session. I think I have all the basics under control. What I can't seem to figure out is how the LUNs now show up as being somehow connected to my Windows computer. I'm sure I've missed something, but I can't figure out what. I've tried reading the "ONTAP SysAdmin Block Access Management Guide" and working through the examples step by step, still to no avail. Some details:
Host (initiator): Windows 2000 ONTAP version 6.4.3 toaster> iscsi show adapter Adapter: iswta Slot: N/A Description: NetApp Software Implementation Status: Online Target Portal Groups: portal group 1: inet 192.168.1.3 port 3260
toaster> igroup show windows-igroup0 (iSCSI) (ostype: windows): iqn.1992-08.com.netapp:sn.123456789
toaster> lun show -v /vol/vol0/iscsi/lun0 10.0g (10742215680) (r/w, online, mapped) Comment: "iSCSI test lun0" Serial#: HPlwFYo6bJoZ Share: none Space Reservation: enabled Multiprotocol Type: windows Maps: windows-igroup0=0 /vol/vol0/iscsi/lun1 10.0g (10742215680) (r/w, online, mapped) Comment: "iSCSI test lun1" Serial#: HPlwFYo6bQDV Share: none Space Reservation: enabled Multiprotocol Type: windows Maps: windows-igroup0=1
toaster> iswt interface show Interface e0 enabled
toaster> iscsi nodename iSCSI target nodename: iqn.1992-08.com.netapp:sn.123456789
Any help would be greatly appreciated.
Thanks,
Geoff Hardin geoff.hardin@dalsemi.com
Thanks to everyone who responded so quickly.
Turns out I had two problems: 1) I had the wrong nodename in the node in the igroup (I had the filer's nodename, not the Windows system's nodename), and 2) I'm a UNIX system admin so I didn't know how to "mount" the drives to the Windows system.
Special thanks to Antonio Jose Rodrigues Neto and Michael Smith (both from NetApp) for their input and quick responses.
Thanks again,
Geoff
Geoff Hardin wrote:
I am new to the SAN environment, and most especially to the iSCSI way of doing things. I have the iSCSI protocol enabled on my filer, and I have the Microsoft iSCSI initiator downloaded and installed on my PC. From the filer, I have created a couple LUNs on my filer, I have created igroups, mapped the LUNs to the igroups, set the create_ucode option to on, and started the iSCSI service. On the Windows system, I have added the target portal, logged on, and I can see an active session. I think I have all the basics under control. What I can't seem to figure out is how the LUNs now show up as being somehow connected to my Windows computer. I'm sure I've missed something, but I can't figure out what. I've tried reading the "ONTAP SysAdmin Block Access Management Guide" and working through the examples step by step, still to no avail. Some details:
Host (initiator): Windows 2000 ONTAP version 6.4.3 toaster> iscsi show adapter Adapter: iswta Slot: N/A Description: NetApp Software Implementation Status: Online Target Portal Groups: portal group 1: inet 192.168.1.3 port 3260
toaster> igroup show windows-igroup0 (iSCSI) (ostype: windows): iqn.1992-08.com.netapp:sn.123456789
toaster> lun show -v /vol/vol0/iscsi/lun0 10.0g (10742215680) (r/w, online, mapped) Comment: "iSCSI test lun0" Serial#: HPlwFYo6bJoZ Share: none Space Reservation: enabled Multiprotocol Type: windows Maps: windows-igroup0=0 /vol/vol0/iscsi/lun1 10.0g (10742215680) (r/w, online, mapped) Comment: "iSCSI test lun1" Serial#: HPlwFYo6bQDV Share: none Space Reservation: enabled Multiprotocol Type: windows Maps: windows-igroup0=1
toaster> iswt interface show Interface e0 enabled
toaster> iscsi nodename iSCSI target nodename: iqn.1992-08.com.netapp:sn.123456789
Any help would be greatly appreciated.
Thanks,
Geoff Hardin geoff.hardin@dalsemi.com
-
Geoff Hardin