HP StorageWorks 2/24 FW 07.00.00/HAFM SW 08.06.00 McDATA Products in a SAN Env - Page 136

Con PDCM arrays, Con zoning, Con Allow/Prohibit Matrix - Active

Page 136 highlights

Planning Considerations for Fibre Channel Topologies 3 6. Configure PDCM arrays - For each director or switch managed by the FICON management style, define the allow and prohibit settings for FICON device connectivity. Use the Element Manager application's Configure Allow/Prohibit Matrix - Active dialog box. Port connectivity assignment (step 4) should be reflected in PDCM arrays for FICON connectivity management. The baseline configuration for each fabric element must prohibit communication between FICON and FCP devices. - Because PDCM arrays affect port connections at the hardware level, it is imperative to establish a range of port addresses for FCP use and another range for FICON use. FCP-assigned ports should be configured to allow communication with each other and prohibit communication with FICON-assigned ports, and vice versa. - At the Configure Allow/Prohibit Matrix - Active dialog box, assigning port names to logical port addresses is another practice that should be followed. For example, the port name for all FCP devices could begin with FCP or OS to indicate the associated port addresses attach to open-systems devices. This information emphasizes which ports are FCP ports and which are FICON ports and gives a user the ability to better manage the connectivity matrix. - Caution should be exercised when using a PDCM array to prohibit E_Port connectivity. For additional information, refer to PDCM Arrays. 7. Configure zoning - Well-behaved intermix environments require the creation of separate zones for FCP and FICON devices. Group all FICON devices into one zone, then group FCP devices into multiple zones in traditional fashion to facilitate typical opensystems communication. - Be aware that FICON devices do not use the Fibre Channel name server, therefore name server-based zoning does not affect FICON connectivity. However, the name server does affect distribution of registered state change notification (RSCN) service requests to FICON devices. If a FICON device is not in the same zone as other devices, state changes are not properly communicated. 3-50 McDATA Products in a SAN Environment - Planning Manual

  • 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
  • 319
  • 320
  • 321
  • 322

3
3-50
McDATA Products in a SAN Environment - Planning Manual
Planning Considerations for Fibre Channel Topologies
6.
Configure PDCM arrays -
For each director or switch managed
by the FICON management style, define the allow and prohibit
settings for FICON device connectivity. Use the Element Manager
application’s
Configure Allow/Prohibit Matrix - Active
dialog box.
Port connectivity assignment (
step 4
) should be reflected in
PDCM arrays for FICON connectivity management. The baseline
configuration for each fabric element must prohibit
communication between FICON and FCP devices.
Because PDCM arrays affect port connections at the hardware
level, it is imperative to establish a range of port addresses for
FCP use and another range for FICON use. FCP-assigned
ports should be configured to allow communication with each
other and prohibit communication with FICON-assigned
ports, and vice versa.
At the
Configure Allow/Prohibit Matrix - Active
dialog box,
assigning port names to logical port addresses is another
practice that should be followed. For example, the port name
for all FCP devices could begin with FCP or OS to indicate the
associated port addresses attach to open-systems devices. This
information emphasizes which ports are FCP ports and which
are FICON ports and gives a user the ability to better manage
the connectivity matrix.
Caution should be exercised when using a PDCM array to
prohibit E_Port connectivity. For additional information, refer
to
PDCM Arrays
.
7.
Configure zoning -
Well-behaved intermix environments require
the creation of separate zones for FCP and FICON devices.
Group
all FICON devices into one zone, then group FCP devices into
multiple zones in traditional fashion to facilitate typical open-
systems communication.
Be aware that FICON devices do not use the Fibre Channel
name server, therefore name server-based zoning does not
affect FICON connectivity. However, the name server does
affect distribution of registered state change notification
(RSCN) service requests to FICON devices. If a FICON device
is not in the same zone as other devices, state changes are not
properly communicated.