Multiple Connections per Session

The Linux SCSI Target Wiki

(Difference between revisions)
Jump to: navigation, search
m
m
 
(49 intermediate revisions not shown)
Line 1: Line 1:
-
'''MC/S''' (multiple iSCSI connections per iSCSI session) means creating multiple communication paths in a single session.
+
'''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.
-
== Overview ==
+
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.
-
 
+
-
MC/S means creating multiple communication paths across [[TCP]]/[[SCTP]] or iSER & RCaP connections. Session-wide command (CmdSN defined) ordering is preserved per [http://tools.ietf.org/html/rfc3270 RFC-3720] 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 ==
-
* [[Core-iscsi Interopt]]: supported, stable
+
* [[Core-iSCSI]]: supported, stable
-
* [[Linux-iscsi Interopt]]: not supported
+
* [[Open-iSCSI]]: not supported
-
* [[Open-iscsi Interopt]]: not supported
+
== Standards compliance ==
== Standards compliance ==
-
The requirements as defined by [http://tools.ietf.org/html/rfc3270 RFC-3720] for non [[ErrorRecoveryLevel|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 20: Line 17:
* Restart session+connections during single connection failure (session reinstatement)
* Restart session+connections during single connection failure (session reinstatement)
* Multiple connection sessions to the same and different network portals (iSCSI trunking)
* Multiple connection sessions to the same and different network portals (iSCSI trunking)
 +
 +
== 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 ==
 +
* {{RFC|3720|Internet Small Computer Systems Interface (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

Standards compliance

The requirements as defined by RFC 3720 for non-ERL dependent MC/S support are not limited to the following:

See also

External links

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Google AdSense