Multiple Connections per Session

The Linux SCSI Target Wiki

(Difference between revisions)
Jump to: navigation, search
m (Standards compliance)
m (Standards compliance)
Line 13: Line 13:
== Standards compliance ==
== Standards compliance ==
-
The requirements as defined by [http://tools.ietf.org/html/rfc3270 RFC-3720] for non [[ERL]] dependent MC/S support are not limited to the following:
+
The requirements as defined by [http://tools.ietf.org/html/rfc3270 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)
* Add additional connections on the fly with active+inactive IO (non-leading login)

Revision as of 07:39, 20 November 2010

MC/S (multiple iSCSI connections per iSCSI session) means using multiple communication paths in a single session ("I_T Nexus"). Architectural session command ordering is preserved across those communication paths.

Overview

MC/S means creating multiple communication paths across TCP/SCTP or iSER & RCaP connections. Session-wide command (CmdSN defined) ordering is preserved per 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

Standards compliance

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

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Google AdSense