Confirmation on possable PID issue.

[Dave Thomson]

Hello

If i add a new switch to an existing Fabric with a differnent PID no - existing PID 0 , new PID 1 - will it cause the fabric to segment and disconnect servers from storage units ?

Thanks

[Uwe Zessin]

The new switch will not join the existing fabric.

[Dave Thomson]

Thanks Ewu, but would it cause the existing fabric to disconnect current servers from storage.

I connected a switch to my fabric - different PID. I only expected it to not join to the fabric. But i had servers disconnecting from the storage devices. Device ID's have been set accordingly.

Would the differnt PID do this, or might i have another issue. I cannot retest it with a new PID. New switches are PID1,2 Current fabric is PID 0. I have to first change the current fabric to 1, this will take 3 weeks.

Thanks

[Uwe Zessin · Accepted solution]

Just to make sure:
we are talking about the "Core-PID" setting, right?

I have never tried it out myself, but from reading the documentation, value 2 should be compatible with value 0. It makes sure that the area byte wraps around on switches with many ports.

[Jim Paulsen]

a switch with a pid of 0 won't communicate with a switch with a PID of 1. The PID 1 will segment itself. I went thru this same issue about 18months ago when we were adding directors to our fabric and had Brocade 2800 switches in our fabric. First had to go to a PID of 2 (kind of an interop). Brocade has a script on their website that will change the PID format on multiple switches at once to ease the downtime.

[Dave Thomson]

Thanks.

We are replacing 2 Brocade 2800's with new switchs. It makes more sence to change the current PID on the remaing switches to 1 instead of 0 so we dont have this issue again.

Regards