Change PID Format Storageworks 2/16 Switch

[Pau_2]

Hello,

We Have Two Switches Storageworks 2/16 (they only have PIDformat in 0 or 1 mode) in a EVA 5000, the PIDformat have value 0.
We will connect Two new Brocade (in cascade cascade) with PIDformat in 1 (it only have PID in 1 or 2 mode).
If we change the PIDFormat to 1..
affect the change in the servers that it has connected in the switchs?
Would it lose the Zones configuration of the storageworks Swithces or others configurations?

With Test Merge (with Borcade Manager) have this results:


--- Merge Check Results ---
HP01SW merge checked against BR01SW

--- DomainIDTest
Merge Check Successful

--- TOVTest
Merge Check Successful

--- BufferBufferCreditTest
Merge Check Successful

--- DisableDeviceProbe Test
Merge Check Successful

--- RoutePriorityPerFrame Test
Merge Check Successful

--- SeqLevelSwitching Test
Merge Check Successful

--- SuppressClassF Test
Merge Check Successful

--- LongDistanceTest
Merge Check Successful

--- InteropMode Test
Merge Check Successful

--- DataFieldSizeTest
Merge Check Successful

--- VCEncodingTest
Merge Check Successful

--- VC Priority Test
Merge Check Successful

--- PIDTest
PID format is incompatible:
fabric HP01SW pidFormat: 0
fabric BR01SW pidFormat: 1
Failed Merge Check

--- MgmtServerPlatformTest
Merge Check Successful

--- ZoningTest
WARNING: Zoning Configuration from HP01SW will be applied to BR01SW
FC traffic to some devices may become disrupted
Merge Check Successful

--- SecurityTest
Neither fabric has security enabled
Merge Check Successful

--- FM Configuration and Data Test
Merge Check Successful

[CA1309061]

Hi Pau!

At first, what OS included in your zone cfg? Do you have HP-UX servers?

[Pau_2]

We have two DL580 and two DL360 with W2000 Adv. Srv. and one Sun 280R with Solaris 8.

[CA1309061]

One of the important thing is firmware of SAN switch. There is 3 PID format:
- native PID switch PID address mode 0
- core PID switch PID address mode 1
- extended edge PID switch PID address mode 2
In Fabric OS release v4.2.0 and later, Native PID format is not supported; the default format is the Core
PID format. In Fabric OS v3.1.2 and later, Core PID format is the default configuration. In Fabric OS v2.0.0 and later, Native PID format is the default configuration.
Without dual-fabrics, stopping traffic is highly recommended. You must schedule downtime for the SAN to change the PID format. If HP-UX systems don't present on your enviroment, changing PID format no affect zone cfg or server configuration because they automatically bind by new PID.

Step-by-Step configuration
1. Ensure that all switches in the fabric are running Fabric OS versions that support the addressing
mode. It is recommended that you use v2.6.2+ for 1Gb/s series switches, v3.1.2+ for
2Gb/s switches2. Telnet into one of the switches in the fabric.
3. Disable the switch by entering the switchdisable command.
4. Enter the configure command (the configure prompts display sequentially).
5. Enter â yâ after the â Fabric parametersâ prompt.
6. Enter â 1â at the â Core Switch PID Formatâ prompt.
7. Complete the remaining prompts or press Ctrl-d to accept the remaining settings without
completing all the prompts.
8. Repeat steps 2 through 7 for the remaining switches in the fabric.
9. Reenable the switch by entering the switchenable command.
Example
10. After all switches are updated to use the new PID format and reenabled, verify that the fabric has
fully reconverged (each switch â seesâ the other switches).
11. Enter cfgenable on one of the switches in the fabric to update zoning to
use the new PID form.
This does not change the definition of zones in the fabric, but merely causes the lowest level tables
in the zoning database to be updated with the new PID format setting. It is only necessary to do this
once per fabric; the zoning update automatically propagates to all switches.

[Uwe Zessin]

Last time I checked, changing the PID format requires a switch reboot. The modification will cause a change in fibre channel addresses which affects HP-UX and IBM AIX, which use the address as part of their hardware path.