From: Michael Stout (michaelgstout@hotmail.com)
Date: Fri Jul 28 2006 - 08:38:41 ART
i ran into a spanningtree issue when we connected a stacked switch to a
vendow who used nono cisco switches. The loop was caused by creating a
svi interface for th euplink. We added the vlan to each switch and
installed redundent links from sw1 and sw2 up to the provider.
This caused a spanningtree loop that i was unable to reproduce using
cisco switches.
On another occasion, i was unable to create an etherchannel across
switches. Meaning i could not create portchannel over gig 1/0/14 and gig
2/0/14. Thats not realy a big deal.
I think they make very fast LAN routers. I think it would be interesting
to put a heavy load on a 3750 stack and compare the throughput to a 4000
a 4500 and a 6500. It would be an interesting test.
--------------------------------------------------------------------
From: "Jeffrey Fry" <Jeff@FryGuy.Net>
Reply-To: "Jeffrey Fry" <Jeff@FryGuy.Net>
To: "Mark Lasarko" <mlasarko@co.ba.md.us>, <caccamucca@gmail.com>
CC: <ccielab@groupstudy.com>
Subject: RE: To Stack or Not to Stack
Date: Wed, 26 Jul 2006 23:19:47 -0400
I have been using the Cisco 3750 in a stack for quite a while and
have
not had any issues with them. We use them in a max-stack
configuration
of 5, with StackMaster priority being Switch 1, 3 and 5. We then
also
etherchannel/trunk Switch 1, 3, and 5 back to our core 6509 switches.
When we need to do an upgrade, we upgrade each switch one-by-one and
then reboot that switch number via reboot slot command. Each switch
has
its own copy of the IOS loaded in flash and is able to use that to
boot.
What I like about using them in a stack is that it gives me the
benefit
of a chassis type switch and yet the resiliency of having individual
switches for uptime.
Keep in mind a few things with how we use them... They are typically
Layer 2 devices only, our end-user application is written very well,
thus network utilization is at a minimun, also we have one stack that
has been up for over 2 years with no problems. (And that stack does
do
Layer 3 routing!)
Just my experience...
Jeff
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
Mark Lasarko
Sent: Wednesday, July 26, 2006 8:13 AM
To: caccamucca@gmail.com
Cc: ccielab@groupstudy.com
Subject: Re: To Stack or Not to Stack
Advice: Not to stack,
Reasoning: Limited to 32-Gbps on the stack, with management via a
single
(master) switch. This "master" is responsible for loading IOS across
the
stack along with global configuration control, maintenance of
switching
and routing tables, and acceptance of new switches to the stack. I
see
multiple potential single points of failure here, along with a
performance hit the more you stack. HTH, ~M
>>> "Cacca Mucca" <caccamucca@gmail.com> 07/26/06 6:41 AM >>>
Hi,
I have a question for the group.
My new boss is convinced that stacking the 3750s in the closet is the
way to go where as I feel slaving them off the main closet switch is
better.
I'm flushed with IP addresses so, single management IP address is not
appealing to me. If I need to span more than 2 ports, slaved scenario
works better.
I can upgrade the IOS and reboot one switch at a time.
I've heard nightmare stories about stacked 3750s in a hung state and
not
passing traffic.
Pros about stacking is you can daisy chain them, back of the 3750s,
using the provide cables. Single management IP for the stack.
What is everyone else doing and what works for you?
_______________________________________________________________________
Subscription information may be found at:
http://www.groupstudy.com/list/CCIELab.html
_______________________________________________________________________
Subscription information may be found at:
http://www.groupstudy.com/list/CCIELab.html
_______________________________________________________________________
Subscription information may be found at:
http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Tue Aug 01 2006 - 07:13:48 ART