UNSOLVED

phollenback

updated

23 years ago

0

10073

May 14th, 2004 18:00

Info needed for redundant connection of 3348s and 3324s

I have two 3348s in a rack and two 3324s in a office. Currently one of the 3348s is connected via fiber to one of the 3324s. None of the switches are stacked - the two switches on each end are just connected over a regular 100mbit port.

Now I want to improve my redundancy and reliability. It seems I should do this by adding another fiber and cross-connecting the switches on each end by stacking them. I assume that's better than cross-connecting each end over the 100mbit or gigabit copper ports as it will give more bandwidth.

Here's what the current setup looks like:

rack office
3348--------------3324
| fiber |
|100bT |100bT
| |
3348 3324

And here's what I'm thinking of doing:

rack office
3348--------------3324
| fiber |
|stack |stack
| |
3348--------------3348
fiber

Questions:

1. Is it best from a redundancy perspective to connect the systems on each end via stacking or via the gigabit copper?
2. Will spanning tree work in this setup to prevent loops?
3. Will this setup allow all systems to continue communicating if any one of the links fail?

Your thoughts appreciated.
P.
  • Clark kent

    23 Posts

    178

    0

    Posted May 17th, 2004 12:00

    Hello,

    I don't have much knowledge but from my experiences here is what I would answer:

    1. Is it best from a redundancy perspective to connect the systems on each end via stacking or via the gigabit copper? The stacking module is not meant for redundancy, it's only to be able to manage both switch through one interface with one unique IP.
    2. Will spanning tree work in this setup to prevent loops? Yes it will stop forwarding traffic through one of the fiber links if both are active.
    3. Will this setup allow all systems to continue communicating if any one of the links fail?Yes for the fiber links the traffic will move from one link to the other if the active one failed. Regarding the stacking link I would answer yes but you should try it first and both switch in stacking should be fully configured also in standalone mode in order that if the stacking failed they use the standalone configuration.

     If the stacking solution doesn't satisfy you go for the copper solution but don't forget to set up correctly the bridge priority in order to decide which link will not forward traffic.

    Let me know of your experiences.

    E. 

  • GregM_1

    2 Intern

    •

    112 Posts

    178

    0

    Posted May 17th, 2004 13:00

    To answer your questions:

    1) I would use stacking, this is important if you want to divide the fiber link between the two units.

    2) Spanning Tree will work, but you will not have a loop. Since you have both ends 'stacked' with the stacking module, they both appear as one virtual switch. Once both sides are stacked, the two fiber links should be created in a Port Channel using Link Aggregation (yes, it can span across the stack). Then the two fiber runs will appear as one virtual link, thus no loops.

    3) Yes and No. You can lose a fiber link and be fine, but if the stack link fails (cable or stack module) the entire stack will be down.


    My thoughts are you can go either way. We never get cases of bad stacks, but it could be considered a point of failure in this case. If you go with giga copper between the units instead of stacking, then you will not have a fiber LAG, but two separate links. You will have one big loop, but you can configure Spanning Tree to block one of the fiber ports. In this case you could pull one link and all units would still function.

    Message Edited by DELL-GregM on 05-17-2004 09:49 AM

  • 178

    0

    Posted May 17th, 2004 17:00

    So if I understand correctly, one advantage of stacking is to aggregrate the two fiber links into one pipe? I'll have to consider that.

    If I go with stacking, will the fiber link continue to function if one of the fibers goes down? I.e., will the fiber link be both redundant and load-balanced?

    It seems stacking will be more convenient and a better use of resources. However, I am concerned about the failure mode of a broken stack. If that makes everything stop working, then that's a problem. Can you elaborate on that failure possibility any more? If a stack is broken, do the fibers continue to work as separate connections?
  • GregM_1

    2 Intern

    •

    112 Posts

    178

    0

    Posted May 18th, 2004 12:00

    Yes, if the units are stacked you can aggregate the two fiber links to act as one pipe. Keep in mind you can aggregate on a single switch as well, but when stacking the switches you can span an aggregated link across stack units.

    Yes, if you have a stack with a fiber LAG, the LAG is redundant and does load balance. You can pull either fiber cable and data will continue to pass.

    No, if the stack is broken, both fibers will be down. The nature of the stack allows you to break it for up to two minutes (to replace a switch, or add one to the stack). After that time, all members will reboot in an attempt to restore the stack. The root switch will then keep polling for the other members, but no data will pass until the stack is fixed. The switches recognize they are in a stack by detecting the stacking module.