| Author |
Connecting Silkworm 3850 to 4100 (Cascade)
|
|
| SteveRoss 2006-01-16, 8:47 pm |
| 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
| |
| Faeandar 2006-01-16, 8:47 pm |
| On 16 Jan 2006 16:21:09 -0800, "SteveRoss" <coldaddy@gmail.com> 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" <coldaddy@gmail.com> a écrit dans le message de news:
1137457269.343440.13430@g49g2000cwa.googlegroups.com...
>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" <coldaddy@gmail.com> a écrit dans le message de news:
1137457269.343440.13430@g49g2000cwa.googlegroups.com...
>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
| |
| jlreate 2006-01-18, 7:47 am |
| DD wrote:
>
> "SteveRoss" <coldaddy@gmail.com> a icrit dans le message de news:
> 1137457269.343440.13430@g49g2000cwa.googlegroups.com...
>
> 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 are:
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
--
| |
| SteveRoss 2006-01-18, 5:48 pm |
| Thanks for the reply.
| |
| SteveRoss 2006-01-18, 5:48 pm |
| Thanks for this information.
| |
| SteveRoss 2006-01-18, 5:48 pm |
| 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
| |
| jlreate 2006-01-19, 2:47 am |
| SteveRoss wrote:
> 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
Of course, I apologise for forgetting to mention that one.
The Domain IDs in the fabric have to be all unique. Every switch in
other words that you intend to place inside your fabric should have a
unique different domain id.
--
| |
| SteveRoss 2006-01-20, 2:47 am |
| Thanks again.
| |
| Stuart 2006-01-21, 2:46 am |
| 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" <coldaddy@gmail.com> 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
|
|
|
|