From: P729 (p729@cox.net)
Date: Fri Nov 28 2003 - 16:07:48 GMT-3
You are correct. As soon as the Gigastack grows beyond two switches it
essentially becomes a shared half-duplex medium, albeit with
"point-to-point" capability (think of it as an Ethernet bus with the ARP
tables pre-populated). Beware of the shared characteristic if you are
considering running QoS-sensitive traffic across the stack, as it's not
advisable.
Regards,
Mas Kato
https://ecardfile.com/id/mkato
----- Original Message -----
From: "Kenneth Wygand" <KWygand@customonline.com>
To: "Jason Buszta" <groupstudy@buszta.com>; "Kelly, Russell G"
<Russell_Kelly@eu1.bp.com>
Cc: <ccielab@groupstudy.com>
Sent: Friday, November 28, 2003 10:07 AM
Subject: RE: Gigastacks & Clustering
> Jason,
>
> Thanks and I agree with you. However, each Gigastack module has 2 ports,
so only a single gigastack module is required for each switch, even if
running in a complete redundant loop topology.
>
> Someone please correct me if I am wrong?
>
> Thanks,
> Ken
>
> -----Original Message-----
> From: Jason Buszta [mailto:groupstudy@buszta.com]
> Sent: Fri 11/28/2003 12:35 PM
> To: Kelly, Russell G
> Cc: Kenneth Wygand; ccielab@groupstudy.com
> Subject: RE: Gigastacks & Clustering
>
>
>
>
>
> I also believe that if you connect two switches to a single gigastack
> module the GBIC-Gigastack will run them both in half-duplex. You should
> spend the extra money and on the switch that completes the loop put dual
> GBIC-Gigastacks in it.
>
>
>
>
>
> On Fri, 28 Nov 2003, Kelly, Russell G wrote:
>
> > -----Original Message-----
> > From: Kenneth Wygand [mailto:KWygand@customonline.com]
> > Sent: 28 November 2003 16:14
> > To: ccielab@groupstudy.com
> > Subject: Gigastacks & Clustering
> >
> >
> > Hello and hope everyone had a great Thanksgiving...
> >
> > I am going to be "gigastacking" several switches together but I can't
> > find too much configuration information on Cisco.com for doing this.
> > All I found was a document that said to configure the gigastack
> > interface as a trunk.
> >
> > If more than one vlan exists across the stack then yes, the gig
> > interface needs to be configured as a trunk.
> >
> > I've also looked into switch "clustering". Are "clustering" and
> > "gigastacking" mutually exclusive?
> >
> > Yes they are mutually exclusive. Gigastacking is just uplinking
> > switches, whilst clustering is a convenient way of a single point of
> > management for a whole load of switches.
> >
> > Do you have to cluster if you gigastack switches? -No.
> >
> > I know a switch cluster is a single managed unit across all switches,
> > but I really want to manage each switch individually but to leverage the
> > gigastacking capability. Is this possible? - Yes this is possible just
> > assign each switch an IP (with the clustering too). I have done this to
> > allow HP Openview to monitor each switch individually. A few issues
> > around TACACS+ access to a switch that is not the cluster commander but
> > each switch can be managed/monitored separately
> >
> >
> > Does anyone have any more information on this and/or any documents you
> > can point me to in order to clarify these differences?
> >
> > Thanks in advance,
> > Ken
> >
> > _______________________________________________________________________
> > Please help support GroupStudy by purchasing your study materials from:
> > http://shop.groupstudy.com
> >
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
> > _______________________________________________________________________
> > Please help support GroupStudy by purchasing your study materials from:
> > http://shop.groupstudy.com
> >
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Fri Dec 12 2003 - 12:29:19 GMT-3