switch PID format的问题(part 2)

6.3.6.2. Core PID On Switches with Fabric OS 4.2 (or Higher)

The SilkWorm 3850 and 3250 have the Core PID format ON by default. Fabric OS 4.2 or greater only supports PID Formats 1 and 2. If these switches are introduced to a fabric that has switches running Fabric OS 2.x or 3.x with the default Core PID format setting of 0, the SilkWorm 3850 and 3250 will segment. When introducing these switches to the fabric, the Core PID formats on the existing switches must be set to 1, as this setting is a fabric wide parameter.

6.3.7. (Optional) Extended Edge PID Format Setting

Note: Displaying and Configuring Extended Edge PID format is available in Fabric OS 2.6.2, 3.1.2 and 4.2 and higher.

This section provides some detail on how to validating the PID Format setting. The best way to display the configuration of the PID format is to use configshow. The current setting is shown by the fabric.ops.mode.pidFormat variable. Depending on the switch type, several screens of output may need to be scrolled through. Partial output, showing the setting is shown below.

fabric.ops.mode.pidFormat:1

In this case the PID Format is set to 1. This means the switch is set to the Core PID setting. Other commands to display the PID setting are portshow and portswapshow.

Warning: Configure may be tempting to use for displaying the PID format. However, in order to see the PID Format setting, the switch must be disabled.

Please note that the switch port number and area ID are not the same. The switch port number is the physical port on the switch. The area number is a logical number that represents the logical port and is the second byte of the PID. The switch port number may consist of physical slot and port numbers or just the switch port number on non-bladed Brocade switch platforms.

To display the PID, use switchshow. It will display both the Area ID and the Port Number on bladed switches. Portshow displays the PID address for individual ports on all switch types. Other commands that display PID address include nsallshow, nsshow, portswapshow

To set the PID format, use the configurecommand. The method of doing this is equivalent to what was shown in section

6.3.6. Set Domain ID and Core PID Format in the Same Session (On Non-Fabric OS 4.x Switches) on page 6-7. Please refer to this section for details.

Note: As of Fabric OS 2.6.2, 3.1.2 and 4.2, support for a PID format 2 available. This setting is an alternative to the Core PID format (PID format 1).

PID format 2 was created for hosts which use persistent binding from having to reboot or involve the execution of commands on the host to recognize devices utilizing new PIDs. This new PID format setting is referred to as Extended Edge PID.

Note: No format setting is required when introducing a SilkWorm 24000, 3250, and/or 3850 to a fabric with a SilkWorm 12000 and/or 3900.

Warning: Be aware that a PID format setting is a fabric wide parameter. All switches in a fabric MUST have the same value or the fabric will segment.

The PID is the 24-bit address assigned to fabric attached hosts and storage. It contains three bytes: the first byte is the Domain Number; the second byte is the Area and the third byte the ALPA. Different PID Format values toggle Brocades addressing scheme in the second byte. Table 6-4 provides a summary of the current available PID formats.

Table 6-4 Available PID Formats

PID Format Name	PID Format Value	Area ID Calculated Value and Range	Affected Switch Model	What it is / What it does	Example/Notes
Native PID Format	0	0x10 + port number Range: 10-1f	SilkWorm 2000 and 3000 series	Sets the first nibble of PID Area byte to be 1. Applies to switches of up to 16 ports	db1a00 (SW 2250) Device on port 10 of a 16 port switch. Only applies on Fabric OS 2.x and 3.x.
Core Switch PID Format	1	port number Range: 00-ff	All	Sets the first nibble of PID to start at 0. Applies to switches of up to 256 ports	141a00 (SW 3900) Device on port 26 of a 32 port switch
Extended Edge PID Format (Newly added to Fabric OS 2.6.2, 3.1.2 and 4.2)	2	0x10 + port number Range: 10-00 (with wrap)	All	Sets the first nibble of PID Area byte to start at 1 and wraps to 0, with 7 as the next to last number. Applies to switches of up to 256 ports	3f5a00 (SW 24000) Device on port 10 on slot 6. On SilkWorm 24000, area_ID runs from 16 - 127, 0 - 15. For port counts of 16 or less, Native PID Format is equivalent to Extended Edge

The SilkWorm 2000 series and 3200/3800 use Core PID format 0 as default. Core PID Format 1 was introduced in the SilkWorm 3900 and the 12000 director. Core PID Format 1 has been extended to the SilkWorm 24000, 3250 and 3850. Your existing fabric may have one of the following three configurations.

1.    The fabric consists of SilkWorm 2000 series (Fabric OS 2.x) and/or SilkWorm 3200/3800 (Fabric OS 3.x).

2.    The fabric consists of SilkWorm 2000 series (Fabric OS 2.x) and/or 3800 (Fabric OS 3.x) and at least one SilkWorm 3900 or SilkWorm 12000 (Fabric OS 4.x) is present.

3. The fabric consists of a SilkWorm 12000 and/or 3900 (Fabric OS 4.x) only. The Core PID format of fabric configurations 2 and 3 are already set to format 1, therefore no action is required when adding a SilkWorm 24000, 3250 and/or 3850. However, fabric configuration 1 requires the Core PID format be set to 1 or 2 when adding a switch running Fabric OS 4.2 or later. It is highly recommended to use Core PID format 1 to be compatible with

newer switches. The following example illustrates a rare special case when you should consider upgrading switches in fabric configuration 1 to Core PID format 2.Condition 1: Host binds storage by Port ID (PID) (solaris, AIX, HPUX hosts)Condition 2: Host config.file update and System reboot is not permissible.Condition 3: You are not planning to change the Domain ID of the existing switch.Condition 4: You are not planning to move the physical storage port from its current location.

Note: If you must upgrade to Core PID format 2 on all switches in fabric configuration 1 to avoid host reboot, they must first be upgraded to the latest available Fabric OS (Fabric OS 2.6.2/3.1.2). Prior versions of Fabric OS do not offer setting of Core PID Format 2. The switch that you would like to add to this existing fabric must also be set to Core PID format

2. All switches in the fabric must have a uniform format type.

Example: Core PID Setting

To illustrate the use of the Extended Edge PID setting, consider the following scenario:

A SilkWorm switch running Fabric OS 4.1 or greater needs to be integrated into an existing fabric that contains SilkWorm switches running Fabric OS 2.x or 3.x, all of which have the default Native PID format (PID 0) configured. Hosts on these fabrics use the PID for persistent binding. Because of the difference in Core PID format, the Brocade switches running Fabric OS 4.1 or greater will not be able to join the existing fabric unless the Core PID format on the exiting fabric switches is upgraded to a compatible PID format of the newer switch (default Core PID Format is 1). Setting the Core PID on existing switches is a disruptive event as it requires the switch to be disabled and rebooted. In this case if the Core PID format is set to 1, as is required, the area field of 24-bit Port ID of all pre-configured devices is changed. The hosts that are binding the storage port by Port ID require the Config.file to be updated to reflect the new storage port ID, and the system must be rebooted. All hosts must be rebooted also, and perhaps certain OS settings may need to be changed as well, in order to rediscover the SAN attached storage.

With the Extended Edge PID Format (PID format 2) set on all switches (old and new), the PID address of the pre-configured devices will be the same. Thus, there is no change to the config.file and the host does need to be rebooted.

While not discussed in the example, the SilkWorm 3850/3250 (Fabric OS 4.2 or greater) is factory installed with Core PID on (PID 1). These switches also support the Extended Edge PID Format.

Warning: In all cases where the PID format is changed, all switches in the fabric must be rebooted or disabled and then re-enabled.