| 1 | <?xml version="1.0" encoding="UTF-8"?>
|
|---|
| 2 | <!DOCTYPE topic
|
|---|
| 3 | PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
|---|
| 4 | <topic xml:lang="en-us" id="storage-iscsi">
|
|---|
| 5 | <title>iSCSI Servers</title>
|
|---|
| 6 |
|
|---|
| 7 | <body>
|
|---|
| 8 | <p>
|
|---|
| 9 | iSCSI stands for <i>Internet SCSI</i> and is a
|
|---|
| 10 | standard that supports use of the SCSI protocol over Internet
|
|---|
| 11 | (TCP/IP) connections. Especially with the advent of Gigabit
|
|---|
| 12 | Ethernet, it has become affordable to attach iSCSI storage servers
|
|---|
| 13 | simply as remote hard disks to a computer network. In iSCSI
|
|---|
| 14 | terminology, the server providing storage resources is called an
|
|---|
| 15 | <i>iSCSI target</i>, while the client connecting to
|
|---|
| 16 | the server and accessing its resources is called an
|
|---|
| 17 | <i>iSCSI initiator</i>.
|
|---|
| 18 | </p>
|
|---|
| 19 | <p>
|
|---|
| 20 | <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can transparently present iSCSI remote storage to a
|
|---|
| 21 | virtual machine as a virtual hard disk. The guest OS will not see
|
|---|
| 22 | any difference between a virtual disk image (VDI file) and an
|
|---|
| 23 | iSCSI target. To achieve this, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has an integrated
|
|---|
| 24 | iSCSI initiator.
|
|---|
| 25 | </p>
|
|---|
| 26 | <p> <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s iSCSI support has been developed according to the iSCSI
|
|---|
| 27 | standard and should work with all standard-conforming iSCSI targets. To use an iSCSI target
|
|---|
| 28 | with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, you must use the command line. See <xref
|
|---|
| 29 | href="vboxmanage-storageattach.dita"/>. </p>
|
|---|
| 30 | </body>
|
|---|
| 31 |
|
|---|
| 32 | </topic>
|
|---|
