HP StorageWorks 2/16V HP StorageWorks Fabric OS 5.X Procedures User Guide (AA- - Page 182

Table 35 Enforcing hardware zoning, Switch, HP

Page 182 highlights

Table 35 Enforcing hardware zoning Fabric type Methodology Best practice HP StorageWorks 1-GB switches Enables hardware-enforced zoning only on domain, port zones; WWN or mixed zones are not hardware-enforced. Any domain, port zone that overlaps a mixed or WWN zone is not hardware-enforced. Use domain, port identifiers (PIDs). Do not identify a zone member by its WWN. An overlap occurs when a member specified by WWN is connected to a port in a domain, port zone. The domain, port zone loses its hardware enforcement even though a review of the zone configuration does not indicate it. 4/8 SAN Switch, 4/16 SAN Switch, HP StorageWorks 2-GB switches, SAN Switch 4/32, Core Switch 2/64, SAN Director 2/128, and 4/256 SAN Director Mixed switches Enable hardware-enforced zoning on domain, port zones, and WWN zones. Overlap of similar zone types does not result in the loss of hardware enforcement. Overlap with other zone type results in the loss of hardware enforcement. Use either WWN or domain, port identifiers. As in the HP StorageWorks 1 GB switches, connecting a device specified by WWN into a port specified in a domain, port zone results in loss of the hardware enforcement in both zones. Enable hardware-enforced zoning according to each switch type. Use the portZoneShow command to find the zone type to which a device is attached. Use domain, port identifiers. You can use WWN identifiers if you place disk and tape targets on HP StorageWorks 2-GB switches, Core Switch 2/64, and SAN Director 2/128, and do not use domain, port identifiers. Figure 6 shows a fabric with four non-overlap ping hardware-enforced zones. 182 Administering advanced zoning

  • 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

182
Administering advanced zoning
Figure 6
shows a fabric with four non-overlap ping hardware-enforced zones.
Table 35
Enforcing hardware zoning
Fabric type
Methodology
Best practice
HP StorageWorks
1-GB switches
Enables hardware-enforced zoning
only on domain, port zones; WWN
or mixed zones are not
hardware-enforced. Any domain,
port zone that overlaps a mixed or
WWN zone is not
hardware-enforced.
An overlap occurs when a member
specified by WWN is connected to a
port in a domain, port zone. The
domain, port zone loses its hardware
enforcement even though a review of
the zone configuration does not
indicate it.
Use domain, port identifiers
(PIDs). Do not identify a zone
member by its WWN.
4/8 SAN Switch,
4/16 SAN
Switch, HP
StorageWorks
2-GB switches,
SAN Switch
4/32, Core
Switch 2/64,
SAN Director
2/128, and
4/256 SAN
Director
Enable hardware-enforced zoning on
domain, port zones, and WWN
zones. Overlap of similar zone types
does not result in the loss of
hardware enforcement. Overlap with
other zone type results in the loss of
hardware enforcement.
As in the HP StorageWorks 1 GB
switches, connecting a device
specified by WWN into a port
specified in a domain, port zone
results in loss of the hardware
enforcement in both zones.
Use either WWN or domain,
port identifiers.
Mixed switches
Enable hardware-enforced zoning
according to each switch type. Use
the
portZoneShow
command to
find the zone type to which a device
is attached.
Use domain, port identifiers.
You can use WWN identifiers if
you place disk and tape targets
on HP StorageWorks 2-GB
switches, Core Switch 2/64, and
SAN Director 2/128, and do
not use domain, port identifiers.