
Fabric OS 5.3.0 administrator guide 205
By index
With the introduction of 48-port blades, the Index was introduced. Unique area IDs are possible up to 255
areas, but beyond that there needed to be some way to ensure uniqueness.
A number of fabric-wide databases supported by Fabric OS (including ZoneDB, Secure FOS DDC policies,
the ACL DDC, and Admin Domain) allow a port to be designated by the use of a “D,P” (Domain, Port)
notation. While the “P” component appears to be the port number, in up to 255 ports it was actually the
area
assigned to that port.
If the PID format is changed from Core to Extended-edge or vice-versa, the “P” value for ports 0-127 also
changes. If two ports are changed using the portSwap command, their respective areas and “P” values are
exchanged.
For ports that are numbered above 255, the “P” value is actually a logical index. The existing
index-to-area_ID mapping for the first 256 ports in a switch is kept, and add values equal to the physical
port number for the new FC4-48 ports.
The first 256 ports continue to have an index value equal to the area_ID assigned to the port. If a switch is
using Core PID format, and no port swapping has been done, the port Index value for all ports is the same
as the physical port numbers. Changing the PID format will change the index values as well as the area_ID
values of the first 128 ports, and using portswap on a pair of ports will exchange those ports’ area_ID and
index values. Portswap is not supported for ports above 256.
Table 52
and
Table 53
show the area ID and index mapping for core and extended-edge PID assignment.
Note that up to 255 areas, the area_ID mapping to the index is one-to-one. Beyond this, the index is
similar but not exact, and in some instances the area ID is shared among multiple ports.
These tables provide the area_ID/Index assignment for the maximum number of ports (used by the FC4-48
blade). If your blade does not have the maximum number of ports, use the lower sections of the table to
determine the area_ID and index.
Table 52
Default index/area_ID Core PID assignment with no port swap
Port on
blade
Slot
1Idx/Area
Slot
2Idx/Area
Slot
3Idx/Area
Slot
4Idx/Area
Slot
7Idx/Area
Slot
8Idx/Area
Slot
9Idx/Area
Slot
10Idx/Area
47
271/135
287/151
303/167
319/183
335/199
351/215
367/231
383/247
46
270/134
286/150
302/166
318/182
334/198
350/214
366/230
382/246
45
269/133
285/149
301/165
317/181
333/197
349/213
365/229
381/245
44
268/132
284/148
300/164
316/180
332/196
348/212
364/228
380/244
43
267/131
283/147
299/163
315/179
331/195
347/211
363/227
379/243
42
266/130
282/146
298/162
314/178
330/194
346/210
362/226
378/242
41
265/129
281/145
297/161
313/177
329/193
345/209
361/225
377/241
40
264/128
280/144
296/160
312/176
328/192
344/208
360/224
376/240
39
263/143
279/159
295/175
311/191
327/207
343/223
359/239
375/255
38
262/142
278/158
294/174
310/190
326/206
342/222
358/238
374/254
37
261/141
277/157
293/173
309/189
325/205
341/221
357/237
373/253
36
260/140
276/156
292/172
308/188
324/204
340/220
356/236
372/252
35
259/139
275/155
291/171
307/187
323/203
339/219
355/235
371/251
34
258/138
274/154
290/170
306/186
322/202
338/218
354/234
370/250
33
257/137
273/153
289/169
305/185
321/201
337/217
353/233
369/249
32
256/136
272/152
288/168
304/184
320/200
336/216
352/232
368/248
31
143/143
159/159
175/175
191/191
207/207
223/223
239/239
255/255
Summary of Contents for AA979A - StorageWorks SAN Switch 2/8V
Page 1: ...HP StorageWorks Fabric OS 5 3 x administrator guide Part number 5697 0244 November 2009 ...
Page 16: ...16 ...
Page 20: ...18 ...
Page 24: ...24 Introducing Fabric OS CLI procedures ...
Page 116: ...118 Maintaining configurations ...
Page 170: ...172 Managing administrative domains ...
Page 200: ...202 Installing and maintaining firmware ...
Page 222: ...224 Routing traffic ...
Page 274: ...286 Administering FICON fabrics ...
Page 294: ...306 Working with diagnostic features ...
Page 350: ...362 Administering Extended Fabrics ...
Page 438: ...440 Configuring the PID format ...
Page 444: ...446 Configuring McData Open Fabric mode ...
Page 450: ...452 Understanding legacy password behaviour ...