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

No Zone Synchronization, Append IPS Zones, No Zone, Synchronization, Append IPS, Zones

Page 161 highlights

Implementing SAN Internetworking Solutions 4 A No Zone Synchronization policy is typically not suitable for larger SAN routing environments where many devices must be visible to numerous fabrics. Append IPS Zones When the zone policy is set to Append IPS Zones, Internet protocol storage (IPS) zone set information from the router is appended to the active zone set for every router-attached fabric in the mSAN. In addition, all devices in the IPS zone set are added to the SNS of each fabric, even if the fabric does not have an active zone set. This policy is the default setting when an R_Port is configured. The Append IPS Zones policy is recommended and provides a balance between ease of use and retention of primary zoning control by Fibre Channel SAN management applications. Cross-fabric devices are zoned together (IPS zone set) through the SANvergence Manager application, and the zone is appended to the active zone set for each fabric (zoned through a SAN management application). Any subsequent changes made to the IPS zone set are propagated to the fabrics. NOTE: When using a SAN router with E/OSi Version 4.5 (or earlier), an active zone set must exist for each fabric prior to performing an Append IPS Zones operation. When using E/OSi Version 4.6 (or later), active zone sets are created automatically when the router zone is appended. The Append IPS Zones policy automatically creates common router zones in each attached fabric. In large environments where many devices must be visible to numerous fabrics, this policy is much easier than creating router zones manually (using the No Zone Synchronization policy). The IPS zone set appended to the active zone set of the fabric must not be modified using a Fibre Channel SAN management application. Changes made to the appended IPS zone set are immediately overwritten with the information previously configured at the SANvergence Manager application. Implementing SAN Internetworking Solutions 4-17

  • 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

4
Implementing SAN Internetworking Solutions
4-17
Implementing SAN Internetworking Solutions
A
No Zone Synchronization
policy is typically not suitable for larger
SAN routing environments where many devices must be visible to
numerous fabrics.
Append IPS Zones
When the zone policy is set to
Append IPS Zones
, Internet protocol
storage (IPS) zone set information from the router is appended to the
active zone set for every router-attached fabric in the mSAN. In
addition, all devices in the IPS zone set are added to the SNS of each
fabric, even if the fabric does not have an active zone set. This policy
is the default setting when an R_Port is configured.
The
Append IPS Zones
policy is recommended and provides a
balance between ease of use and retention of primary zoning control
by Fibre Channel SAN management applications. Cross-fabric
devices are zoned together (IPS zone set) through the SANvergence
Manager application, and the zone is appended to the active zone set
for each fabric (zoned through a SAN management application). Any
subsequent changes made to the IPS zone set are propagated to the
fabrics.
NOTE:
When using a SAN router with E/OSi Version 4.5 (or earlier), an
active zone set must exist for each fabric prior to performing an
Append IPS
Zones
operation. When using E/OSi Version 4.6 (or later), active zone sets
are created automatically when the router zone is appended.
The
Append IPS Zones
policy automatically creates common router
zones in each attached fabric. In large environments where many
devices must be visible to numerous fabrics, this policy is much
easier than creating router zones manually (using the
No Zone
Synchronization
policy).
The IPS zone set appended to the active zone set of the fabric must
not be modified using a Fibre Channel SAN management
application. Changes made to the appended IPS zone set are
immediately overwritten with the information previously configured
at the SANvergence Manager application.