HP StorageWorks 2/140 FW 08.01.00 McDATA Products in a SAN Environment Plannin - Page 115

Read/write mixture, Type of data access, SAN Management Applications, Configuring Zones

Page 115 highlights

Planning Considerations for Fibre Channel Topologies 3 I/O Requirements • Software limits, including the maximum number of fabric elements managed by the SAN management application and the maximum number of zones and zone members. For additional information, refer to SAN Management Applications and Configuring Zones. McDATA directors and fabric switches are designed with nonblocking architecture; therefore any two switch ports can communicate at the full Fibre Channel bandwidth of 1.0625, 2.1250, 4.2500, or 10.2000 Gbps without impact to other switch ports. Because most SAN-attached devices are not capable of generating I/O traffic at the full bandwidth, there is little potential for congestion between two devices attached through a single director or switch. However, when multiple directors or switches are connected through a fabric ISL that multiplexes traffic from several devices, significant potential for congestion arises. To minimize congestion, factors such as application I/O profiles, ISL oversubscription, and device locality must be included in the fabric design. Application I/O Profiles Understanding application I/O characteristics is essential to SAN, fabric, and ISL design. Factors that may affect application I/O include: • Read/write mixture - Although application I/O is typically a mixture of read and write operations, some applications are very biased. For example, video server applications are almost 100% read intensive, while real-time video editing applications are mostly write intensive. Read operations typically take less time than write operations, therefore storage devices for a read-intensive application usually wait for data transfer. As a consequence, read-intensive applications typically require high bandwidth to the device. • Type of data access - When an application requires data, access to that data is random or sequential. For example, e-mail server activity is random access, while seismic data processing for the oil and gas industry is sequential access. Sequential data access typically takes less time than random data access, therefore sequential-access applications usually wait for data transfer. As a consequence, sequential-access applications typically require high bandwidth to the device. Planning Considerations for Fibre Channel Topologies 3-31

  • 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
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318

3
Planning Considerations for Fibre Channel Topologies
3-31
Planning Considerations for Fibre Channel Topologies
Software limits, including the maximum number of fabric
elements managed by the SAN management application and the
maximum number of zones and zone members. For additional
information, refer to
SAN Management Applications
and
Configuring Zones
.
I/O Requirements
McDATA directors and fabric switches are designed with non-
blocking architecture; therefore any two switch ports can
communicate at the full Fibre Channel bandwidth of 1.0625, 2.1250,
4.2500, or 10.2000 Gbps without impact to other switch ports. Because
most SAN-attached devices are not capable of generating I/O traffic
at the full bandwidth, there is little potential for congestion between
two devices attached through a single director or switch.
However, when multiple directors or switches are connected through
a fabric ISL that multiplexes traffic from several devices, significant
potential for congestion arises. To minimize congestion, factors such
as application I/O profiles, ISL oversubscription, and device locality
must be included in the fabric design.
Application I/O Profiles
Understanding application I/O characteristics is essential to SAN,
fabric, and ISL design. Factors that may affect application I/O
include:
Read/write mixture -
Although application I/O is typically a
mixture of read and write operations, some applications are very
biased. For example, video server applications are almost 100%
read intensive, while real-time video editing applications are
mostly write intensive. Read operations typically take less time
than write operations, therefore storage devices for a
read-intensive application usually wait for data transfer. As a
consequence, read-intensive applications typically require high
bandwidth to the device.
Type of data access -
When an application requires data, access to
that data is random or sequential. For example, e-mail server
activity is random access, while seismic data processing for the oil
and gas industry is sequential access. Sequential data access
typically takes less time than random data access, therefore
sequential-access applications usually wait for data transfer. As a
consequence, sequential-access applications typically require
high bandwidth to the device.