Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
appnote:iscsi_targets [2011/05/16 13:41] bootc |
appnote:iscsi_targets [2013/05/07 21:00] kes |
||
|---|---|---|---|
| Line 6: | Line 6: | ||
| * [[http://www.microsoft.com/Windowsserver2008/en/us/wss08.aspx|Windows Storage Server]] on Microsoft Windows | * [[http://www.microsoft.com/Windowsserver2008/en/us/wss08.aspx|Windows Storage Server]] on Microsoft Windows | ||
| * [[http://hub.opensolaris.org/bin/view/Project+comstar/WebHome|COMSTAR]] on Solaris and OpenSolaris (and related products such as Nexenta and OpenIndiana) | * [[http://hub.opensolaris.org/bin/view/Project+comstar/WebHome|COMSTAR]] on Solaris and OpenSolaris (and related products such as Nexenta and OpenIndiana) | ||
| + | * [[http://www.peach.ne.jp/archives/istgt/|ISTGT]] FreeBSD iSCSI target implementation for multipath failover cluster nodes | ||
| Many iSCSI target products are based upon one of these technologies, so your target may be supported even if it is not listed here. | Many iSCSI target products are based upon one of these technologies, so your target may be supported even if it is not listed here. | ||
| Line 16: | Line 17: | ||
| This target works fine, but by default sends NOP-In messages that iPXE can't handle. This should not cause any issues, but has been known to cause trouble with grub2. If you encounter this, try disabling the NOP pings by setting the ''nopin_timeout'' node attribute to 0: | This target works fine, but by default sends NOP-In messages that iPXE can't handle. This should not cause any issues, but has been known to cause trouble with grub2. If you encounter this, try disabling the NOP pings by setting the ''nopin_timeout'' node attribute to 0: | ||
| lio_node --setnodeattr <TARGET_IQN> <TPGT> <INITIATOR_IQN> nopin_timeout 0 | lio_node --setnodeattr <TARGET_IQN> <TPGT> <INITIATOR_IQN> nopin_timeout 0 | ||
| + | |||
| + | === Microsoft Target Software === | ||
| + | When setting up a iSCSI target using the Initiator software it must be explicitly pointed from target to client from the server side otherwise the iSCSI target will not be available or accessible from your network. This is done by: | ||
| + | iSCSITarget -> Expand iSCSI Targets -> Right click on iSCSI target -> Properties -> iSCSI Initiators tab -> Add | ||
| + | |||
| + | With that screen you can authorize a client by IQN, MAC Address, IP Address or DNS Name. | ||
