For When You Can't Have The Real Thing
[ start | index | login ]
start > Windows > iSCSI creation

iSCSI creation

Created by dave. Last edited by dave, 9 years and 91 days ago. Viewed 3,821 times. #2
[diff] [history] [edit] [rdf]
labels
attachments

Creating an iSCSI connection between a NetApp filer and a Win2k3 Server

Provisions:

This worked for me with a Windows Server 2K3 Standard/64 install against a NetApp 2020 running OnTap 7.2.1.1.

I am not using authentication at this point, so the lun is not password-protected in this setup. This may not be what you want.

Procedure:

Get the iSCSI initiator from Microsoft. It is a free download. Google is your friend. Installing it is straight forward, and for me did not require a reboot.

Bring up the iSCSI initiator control, which Microsoft has dropped on your desktop.

Make note of the Node Name, we are going to need it when creating the target on the NetApp. It will be a string like iqn.1991-05.com.microsoft:sqlsvr-fo.xdroop.com

The NetApp bit. We are creating a 1GB iSCSI lun on a 1.1GB volume, inside aggregate myAggr. Note that filers seem to be happiest when 5% to 10% of the volume is free, even if it's going to contain an iSCSI lun. (These numbers are small because this is a test; the largest I've committed is a 250GB LUN into a 265GB volume.)

myFiler> vol create myWindows_test myAggr 1100m
myFiler> snap reserve myWindows_test 0
myFiler> vol options myWindows_test nosnap on
myFiler> vol options myWindows_test nosnapdir on
myFiler> lun create -s 1000m -t $TYPE /vol/myWindows_test/lun0
myFiler> igroup create -i -t $TYPE myWindows $InitiatorName
myFiler> lun map /vol/myWindows_test/lun0 myWindows 0

Note:

  • lun create: $TYPE must be one of: solaris, windows, hpux, aix, linux, netware, vmware or windows_gpt.
  • lun create: $InitiatorName is the string above (ie something like iqn.1991-05.com.microsoft:sqlsvr-fo.xdroop.com)
  • igroup create: $TYPE must be one of: solaris, windows, hpux, aix, linux netware, or vmware.
If you are adding a new LUN to a server which already has one, you don't have to create a new iGroup, you can use the existing one:

filer> lun show -m
[...]
/vol/sqldata0/sqldatalun0           iXXX-SQLSVR             0     iSCSI
/vol/sqllogs0/sqllogslun0           iXXX-SQLSVR             1     iSCSI
/vol/sqlsharepoint/lun0             iXXX-SQLSVR             6     iSCSI
filer> lun map /vol/sqlsharepoint/lun1 iXXX-SQLSVR 7
filer> lun show -m
/vol/sqldata0/sqldatalun0           iXXX-SQLSVR             0     iSCSI
/vol/sqllogs0/sqllogslun0           iXXX-SQLSVR             1     iSCSI
/vol/sqlsharepoint/lun0             iXXX-SQLSVR             6     iSCSI
/vol/sqlsharepoint/lun1             iXXX-SQLSVR             7     iSCSI

Go back to the Windows server.

  • In the iSCSI control, click on the Discovery tab and add your filer to the Target Portals list.
  • On the Targets tab, click on Refresh, and your filer should show up as a potential target. Click on Log On to connect. Click the Automatically restore this connection when the system boots option box.
  • On the Bound Volumes/Devices tab, click Bind All. Your target should show up as a scsi string.
Now you can bring up the Computer Management control panel, and manage your disk through Disk Management. You will have to initialize, partition, and then format the lun as if it was a real disk.
no comments | post comment
This is a collection of techical information, much of it learned the hard way. Consider it a lab book or a /info directory. I doubt much of it will be of use to anyone else.

Useful:


snipsnap.org | Copyright 2000-2002 Matthias L. Jugel and Stephan J. Schmidt