Multiple Connections per Session
The Linux SCSI Target Wiki
(Difference between revisions)
m |
|||
Line 1: | Line 1: | ||
- | MC/S is an acronymn for Multiple iSCSI Connections per iSCSI Session | + | '''MC/S''' is an acronymn for Multiple iSCSI Connections per iSCSI Session. |
- | == | + | == Overview == |
- | [[ | + | MC/S means creating multiple communication paths across [[TCP]]/[[SCTP]] or [[iSER]] & [[RCaP]] connections + RFC-3720 defined session-wide CmdSN ordering 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 == | |
- | [[ | + | * [[Core-iscsi Interopt]]: supported, stable |
+ | * [[Linux-iscsi Interopt]]: not supported | ||
+ | * [[Open-iscsi Interopt]]: not supported | ||
- | The | + | 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) |
Revision as of 02:31, 15 November 2010
MC/S is an acronymn for Multiple iSCSI Connections per iSCSI Session.
Overview
MC/S means creating multiple communication paths across TCP/SCTP or iSER & RCaP connections + RFC-3720 defined session-wide CmdSN ordering 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
- Core-iscsi Interopt: supported, stable
- Linux-iscsi Interopt: not supported
- Open-iscsi Interopt: not supported
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)