HP A7533A - Brocade 4Gb SAN Switch Base, Administrator'S Manual

Page: 271 / 576

Fabric OS 6.2 administrator guide 269
Port Identification by Port Area ID
The relationship between the port number and area ID depends upon the PID format used in the fabric.
When Core PID format is in effect, the area ID for port 0 is 0, for port 1 is 1, and so forth.
For 32-port blades (HP StorageWorks 4/256 SAN Director 16 Port 4Gb blade, HP StorageWorks SAN
Director 32 Port 8Gb FC blade), the numbering is contiguous up to port 15; from port 16, the numbering is
still contiguous, but starts with 128. For example, port 15 in slot 1 has a port number and area ID of 15;
port 16 has a port number and area ID of 128; port 17 has a port number and area ID of 129.
For 48-port blades (HP StorageWorkds 4/256 SAN Director 48 Port 4Gb blade, HP StorageWorks SAN
Director 48 Port 8Gb FC blade), the numbering is the same as for 32-port blades for the first 32 ports on
the blade. For ports 32 through 47, area IDs are not unique and port index should be used instead of area
ID.
If you perform a port swap operation, the port number and area ID no longer match. On 48-port blades,
port swapping is supported only on ports 0–15.
To determine the area ID of a particular port, enter the
switchShow
command. This command displays
all ports on the current (logical) switch and their corresponding area IDs.
Port identification by index
With the introduction of 48-port blades, indexing was introduced. Unique area IDs are possible for 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, 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 is actually the area assigned to that port.
IMPORTANT: The port area schema does not apply to the HP StorageWorks DC04 SAN Director Switch
enterprise-class platform.
If the PID format is changed from Extended-edge to Core, 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 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. Using
portSwap
on a pair of ports will exchange those ports’ area_ID and index values.
NOTE: The
portSwap
command is not supported for ports above 256.
Table 68 shows the area ID and index mapping for core PID assignment for the HP StorageWorks 4/256
SAN Director and the HP StorageWorks DC SAN Backbone Director enterprise-class platform. There are
up to 255 areas and 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.
This table provides the area_ID/index assignment for the maximum number of ports used by the HP
StorageWorks 4/256 SAN Director 48 Port 4Gb blade and HP StorageWorks SAN Director 48 Port 8Gb
FC 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 68 Default index/area_ID core PID assignment with no port swap
Port
on
blade
Slot
1Idx/are
a
Slot
2Idx/are
a
Slot
3Idx/are
a
Slot
4Idx/are
a
Slot
7Idx/are
a
Slot
8Idx/are
a
Slot
9Idx/are
a
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