Multiple Connections per Session
The Linux SCSI Target Wiki
(Difference between revisions)
m (→See also) |
m |
||
| (31 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| - | '''Multiple | + | '''Multiple (iSCSI) connections per (iSCSI) session''' ('''MC/S''') means creating multiple communication paths in a single session (''[[I_T Nexus]]''), i.e. across [http://en.wikipedia.org/wiki/TCP TCP], [http://en.wikipedia.org/wiki/SCTP SCTP], [[ISCSI Extensions for RDMA|iSER]], and/or RCaP transport connections. |
| - | + | Architectural session command ordering is preserved across those communication paths. Session-wide architectural command ordering (defined by the <code>CmdSN</code>) is preserved per RFC 3720. This is to ensure in-order delivery of tasks from an SCSI Initiator port to an SCSI target port as defined by the SCSI Architecture Model, in which iSCSI provides the SCSI transport. | |
| - | + | ||
| - | + | ||
== Linux Compatibility == | == Linux Compatibility == | ||
| Line 12: | Line 10: | ||
== Standards compliance == | == Standards compliance == | ||
| - | The requirements as defined by RFC 3720 for non-[[ERL]] dependent MC/S support are not limited to the following: | + | The requirements as defined by RFC 3720 for non-[[Error Recovery Level|ERL]] dependent MC/S support are not limited to the following: |
* Add additional connections on the fly with active+inactive IO (non-leading login) | * Add additional connections on the fly with active+inactive IO (non-leading login) | ||
| Line 21: | Line 19: | ||
== See also == | == See also == | ||
| - | * [[ | + | * {{Target}} |
| - | + | * [[SCSI]]: [[Persistent Reservations]] (PRs), [[Asymmetric Logical Unit Assignment]] (ALUA), [[Error Recovery Level]] (ERL) | |
| + | * Fabric modules: [[FCoE]], [[Fibre Channel]], [[iSCSI]], [[iSER]], [[SRP]] and [[vHost]] | ||
| + | * Management: [[targetcli]] | ||
| + | * [[Kernel-based Virtual Machine|KVM]] (with some MC/S performance data) | ||
== External links == | == External links == | ||
| - | {{RFC|3720|Internet Small Computer Systems Interface (iSCSI)}} | + | * {{RFC|3720|Internet Small Computer Systems Interface (iSCSI)}} |
[[Category:iSCSI]] | [[Category:iSCSI]] | ||
Latest revision as of 17:24, 29 September 2013
Multiple (iSCSI) connections per (iSCSI) session (MC/S) means creating multiple communication paths in a single session (I_T Nexus), i.e. across TCP, SCTP, iSER, and/or RCaP transport connections.
Architectural session command ordering is preserved across those communication paths. Session-wide architectural command ordering (defined by the CmdSN) is preserved per RFC 3720. This is to ensure in-order delivery of tasks from an SCSI Initiator port to an SCSI target port as defined by the SCSI Architecture Model, in which iSCSI provides the SCSI transport.
Contents |
Linux Compatibility
- Core-iSCSI: supported, stable
- Open-iSCSI: not supported
Standards compliance
The requirements as defined by RFC 3720 for non-ERL dependent MC/S support are not limited to the following:
- Add additional connections on the fly with active+inactive IO (non-leading login)
- Remove connections on the fly with active+inactive IO (explict logout)
- Remove connections on the fly on a different connection with active+inactive IO (different CID explict logout)
- Restart session+connections during single connection failure (session reinstatement)
- Multiple connection sessions to the same and different network portals (iSCSI trunking)
See also
- LinuxIO
- SCSI: Persistent Reservations (PRs), Asymmetric Logical Unit Assignment (ALUA), Error Recovery Level (ERL)
- Fabric modules: FCoE, Fibre Channel, iSCSI, iSER, SRP and vHost
- Management: targetcli
- KVM (with some MC/S performance data)
External links
- RFC 3720: Internet Small Computer Systems Interface (iSCSI)
