Connecting Silkworm 3850 to 4100 (Cascade)

I will be attempting (for the first time) to connect a new 4100 to an
existing 3850 to extend the fabric. My understanding is that the
switches will recognize each other and configure the ports they are
connected on as E type automatically, forming an ISL. Are there any
gotchas I should be aware of? I have tried to find a step-by-step
guide but have been unsucessful.

Thanks in advance for any assistance.

Steve

On 16 Jan 2006 16:21:09 -0800, "SteveRoss" wrote:

I will be attempting (for the first time) to connect a new 4100 to an
existing 3850 to extend the fabric. My understanding is that the
switches will recognize each other and configure the ports they are
connected on as E type automatically, forming an ISL. Are there any
gotchas I should be aware of? I have tried to find a step-by-step
guide but have been unsucessful.

Thanks in advance for any assistance.

Steve


I have very little experience with Brocade but the most obvious thing
to me would be to bring the switch up standalone (not fabric attached)
and verify it's running the same version of OS and firmware.

~F

"SteveRoss" a écrit dans le message de news:
...
I will be attempting (for the first time) to connect a new 4100 to an
existing 3850 to extend the fabric. My understanding is that the
switches will recognize each other and configure the ports they are
connected on as E type automatically, forming an ISL. Are there any
gotchas I should be aware of? I have tried to find a step-by-step
guide but have been unsucessful.

Thanks in advance for any assistance.

Steve


i already have problems interconnecting two brocade switches.
the soluce was in the "core PID switch format" parameter, was set to 0 on
older switch and 1 on the newer one.
setting 1 on both side solved the problem.
to change this parameter = switchdisable / configure / fabric parameters

take care about domain ID too, must be different.

good luck.

DD

"SteveRoss" a écrit dans le message de news:
...
I will be attempting (for the first time) to connect a new 4100 to an
existing 3850 to extend the fabric. My understanding is that the
switches will recognize each other and configure the ports they are
connected on as E type automatically, forming an ISL. Are there any
gotchas I should be aware of? I have tried to find a step-by-step
guide but have been unsucessful.

Thanks in advance for any assistance.

Steve


i already have problems interconnecting two brocade switches.
the soluce was in the "core PID switch format" parameter, was set to 0 on
older switch and 1 on the newer one.
setting 1 on both side solved the problem.
to change this parameter = switchdisable / configure / fabric parameters

take care about domain ID too, must be different.

good luck.

DD

DD wrote:


"SteveRoss" a icrit dans le message de news:
...
I will be attempting (for the first time) to connect a new 4100 to
an existing 3850 to extend the fabric. My understanding is that the
switches will recognize each other and configure the ports they are
connected on as E type automatically, forming an ISL. Are there any
gotchas I should be aware of? I have tried to find a step-by-step
guide but have been unsucessful.

Thanks in advance for any assistance.

Steve


i already have problems interconnecting two brocade switches.
the soluce was in the "core PID switch format" parameter, was set to
0 on older switch and 1 on the newer one.
setting 1 on both side solved the problem.
to change this parameter = switchdisable / configure / fabric
parameters

take care about domain ID too, must be different.

good luck.

DD

When you interconnect Brocade switches the most important things to
consider a

1) Fabric O/S versions: check the support "matrix" which fabric os
version can talk to which one reliably

2) Core/PID: If any of your switches is running the core pid value set
to zero, you are advised to harmonise all of them to one. BE AWARE of
the fact that depending on the operating system that you are using it
can be that by changing the port id setting the LUNs will re-appear
with different names (most notably HPUX and AIX do port based mapping
and thus changing the corepid will affect the hard device list and make
them appear as different devices)

3) Ensure that the new switch to be used does not have any zone
settings inside it. The zone settings will be propagated across the
switches.

4) In any case of problems, the switches will appear as fragmented
fabrics, luckily not interfering with the existing switch.

Good Luck,
DL

--

Thanks for the reply.

Thanks for this information.

Very good information. Thanks for taking the time to reply. Others
have mentioned domain ID considerations as well. What are your
thoughts about that?

Thanks,
Steve

Thanks again.

as long as the new switch you are plugging in has no conflicting zones
with the old - you will be good.

On 16 Jan 2006 16:21:09 -0800, "SteveRoss" wrote:

I will be attempting (for the first time) to connect a new 4100 to an
existing 3850 to extend the fabric. My understanding is that the
switches will recognize each other and configure the ports they are
connected on as E type automatically, forming an ISL. Are there any
gotchas I should be aware of? I have tried to find a step-by-step
guide but have been unsucessful.

Thanks in advance for any assistance.

Steve