D-Link DSN-6410 User Manual for DSN-6410 - Page 107

MPIO and MC/S.

Get D-Link DSN-6410 PDF manuals and user guides View all D-Link DSN-6410 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 107 highlights

Figure 5.8.2 Difference: MC/S is implemented on iSCSI level, while MPIO is implemented on the higher level. Hence, all MPIO infrastructures are shared among all SCSI transports, including Fiber Channel, SAS, etc. MPIO is the most common usage across all OS vendors. The primary difference between these two is which level the redundancy is maintained. MPIO creates multiple iSCSI sessions with the target storage. Load balance and failover occurs between the multiple sessions. MC/S creates multiple connections within a single iSCSI session to manage load balance and failover. Notice that iSCSI connections and sessions are different than TCP/IP connections and sessions. The above figures describe the difference between MPIO and MC/S. There are some considerations when user chooses MC/S or MPIO for multipathing. 1. If user uses hardware iSCSI off-load HBA, then MPIO is the only one choice. 2. If user needs to specify different load balance policies for different LUNs, then MPIO should be used. 3. If user installs anyone of Windows XP, Windows Vista or Windows 7, MC/S is the only option since Microsoft MPIO is supported Windows Server editions only. 4. MC/S can provide higher throughput than MPIO in Windows system, but it consumes more CPU resources than MPIO. 107

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
107
Figure 5.8.2
Difference:
MC/S is implemented on iSCSI level, while MPIO is implemented on the higher level.
Hence, all MPIO infrastructures are shared among all SCSI transports, including Fiber
Channel, SAS, etc. MPIO is the most common usage across all OS vendors. The primary
difference between these two is which level the redundancy is maintained.
MPIO creates
multiple iSCSI sessions with the target storage. Load balance and failover occurs between
the multiple sessions.
MC/S creates multiple connections within a single iSCSI session to
manage load balance and failover. Notice that iSCSI connections and sessions are different
than TCP/IP connections and sessions. The above figures describe the difference between
MPIO and MC/S.
There are some considerations when user chooses MC/S or MPIO for multipathing.
1.
If user uses hardware iSCSI off-load HBA, then MPIO is the only one choice.
2.
If user needs to specify different load balance policies for different LUNs, then MPIO
should be used.
3.
If user installs anyone of Windows XP, Windows Vista or Windows 7, MC/S is the only
option since Microsoft MPIO is supported Windows Server editions only.
4.
MC/S can provide higher throughput than MPIO in Windows system, but it consumes
more CPU resources than MPIO.