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

Features that Impact, Protocol Intermixing, Hardware-Enforced Zoning

Page 132 highlights

Planning Considerations for Fibre Channel Topologies 3 • When employing inband (Fibre Channel) director or switch management, the open-systems management server (OSMS) is associated with the FCP protocol, and the FICON management server (FMS) is associated with the FICON protocol. Management server differences tend to complicate security and control issues. NOTE: The Intrepid 10000 Director and Sphereon 4300 and 4500 Fabric Switches do not support out-of-band management through FMS. Features that Impact Protocol Intermixing Each server provides facilities to change zoning information (FCP protocol) or the logical port address-based connectivity configuration (FICON protocol), but neither provides sufficient functionality for both protocols. McDATA supports the following features that impact how a director or switch behaves when deployed in an intermixed environment: • Hardware-enforced zoning. • SANtegrity Binding (including fabric and switch binding). • FICON cascading. Hardware-Enforced Zoning Hardware-enforced zoning (hard zoning) allows a user to program director or switch route tables that enable hardware logic to route Fibre Channel frames. This process prevents traffic between source and destination devices not in the same zone. Hard zoning provides the open-systems environment with the same protection that PDCM arrays provide in the FICON environment. In environments that include discovery-oriented devices (FCP) and definition-oriented devices (FICON), system administrators must keep device definitions and zoning definitions synchronized. Hard zoning enforces zoning information at the director or switch level and ensures the information takes precedence over access definitions configured at the device level. This provides a security element that is useful for mixed environments using both definition and discovery. For additional information, refer to Zoning. 3-46 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-46
McDATA Products in a SAN Environment - Planning Manual
Planning Considerations for Fibre Channel Topologies
When employing inband (Fibre Channel) director or switch
management, the open-systems management server (OSMS) is
associated with the FCP protocol, and the FICON management
server (FMS) is associated with the FICON protocol. Management
server differences tend to complicate security and control issues.
NOTE:
The Intrepid 10000 Director and Sphereon 4300 and 4500 Fabric
Switches do not support out-of-band management through FMS.
Each server provides facilities to change zoning information
(FCP protocol) or the logical port address-based connectivity
configuration (FICON protocol), but neither provides sufficient
functionality for both protocols.
Features that Impact
Protocol Intermixing
McDATA supports the following features that impact how a director
or switch behaves when deployed in an intermixed environment:
Hardware-enforced zoning.
SANtegrity Binding (including fabric and switch binding).
FICON cascading.
Hardware-Enforced Zoning
Hardware-enforced zoning (hard zoning) allows a user to program
director or switch route tables that enable hardware logic to route
Fibre Channel frames. This process prevents traffic between source
and destination devices not in the same zone. Hard zoning provides
the open-systems environment with the same protection that PDCM
arrays provide in the FICON environment.
In environments that include discovery-oriented devices (FCP) and
definition-oriented devices (FICON), system administrators must
keep device definitions and zoning definitions synchronized. Hard
zoning enforces zoning information at the director or switch level
and ensures the information takes precedence over access definitions
configured at the device level. This provides a security element that is
useful for mixed environments using both definition and discovery.
For additional information, refer to
Zoning
.