HP 316095-B21 FW 08.01.00 McDATA EFCM Basic User Manual (620-000240-000, Novem - Page 94

Domain 1, Port 1, Using Port Numbers

Page 94 highlights

Understanding Zoning 4 such as servers or storage devices. Although the device may also have a node WWN, this WWN is not used for zoning identification. NOTE: Nicknames can be assigned to the WWN using the Element Manager. This functionality is not available in EFCM Basic. The advantage of identifying a zone member as the WWN of the attached device is that the identification will not change if fiber cable connections to ports are rearranged. This is especially important if you are using spare ports. You can simply move the fiber cable to a spare port from a failed port and still maintain the zoning configuration. The disadvantage of identifying a zone member by the WWN is that removal and replacement of a device HBA or Fibre Channel interface (thereby changing the device WWN) disrupts zone operation and may incorrectly include or exclude a device from a zone. Using Port Numbers To identify a zone member by port number, use the domain identification number of the managed product and the port number on that managed product. For example: Domain 1, Port 1 NOTE: Port numbers cannot be used for zone members if the Interoperability mode for the switch or director is set to Open Fabric 1.0 mode. Port numbers can be 0 through n, with n representing the number of ports on the managed product minus one. When you define a zone member by a port number, any device attached through that port is included in the zone. A port number that you assign as a zone member is automatically prefixed with the domain identification number of the managed product. The advantage of identifying a zone member by port number is that if the HBA on an attached device fails, you don't have to identify the member with the WWN of the replacement HBA. A disadvantage of port zoning is that someone may rearrange cable connections to ports (because of port failures or other reasons) and inadvertently allow devices to communicate that should not have access to each other. 4-8 EFCM Basic User 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

4
4-8
EFCM Basic User Manual
Understanding Zoning
such as servers or storage devices. Although the device may also
have a
node
WWN, this WWN is not used for zoning identification.
NOTE:
Nicknames can be assigned to the WWN using the Element Manager.
This functionality is not available in EFCM Basic.
The advantage of identifying a zone member as the WWN of the
attached device is that the identification will not change if fiber cable
connections to ports are rearranged. This is especially important if
you are using spare ports. You can simply move the fiber cable to a
spare port from a failed port and still maintain the zoning
configuration.
The disadvantage of identifying a zone member by the WWN is that
removal and replacement of a device HBA or Fibre Channel interface
(thereby changing the device WWN) disrupts zone operation and
may incorrectly include or exclude a device from a zone.
Using Port Numbers
To identify a zone member by port number, use the domain
identification number of the managed product and the port number
on that managed product. For example:
Domain 1, Port 1
NOTE:
Port numbers cannot be used for zone members if the Interoperability
mode for the switch or director is set to Open Fabric 1.0 mode.
Port numbers can be 0 through
n
, with
n
representing the number of
ports on the managed product minus one. When you define a zone
member by a port number, any device attached through that port is
included in the zone. A port number that you assign as a zone
member is automatically prefixed with the domain identification
number of the managed product.
The advantage of identifying a zone member by port number is that if
the HBA on an attached device fails, you don’t have to identify the
member with the WWN of the replacement HBA.
A disadvantage of port zoning is that someone may rearrange cable
connections to ports (because of port failures or other reasons) and
inadvertently allow devices to communicate that should not have
access to each other.