[c-nsp] Cat 3750 StackMaster Selection considerations

[Michel Grossenbacher]

Thanks guys for your answers.
What Peter wrote is actually what I was thinking about, having a sane
numbering is more important than knowing which switch is the master. I dont
see any benefit in selecting a Stack Master manually in our environment
since we have the same feature sets on every switch. Complex was probably
the wrong word for it, but having to care about that the stack master is
booted within the 20sec time frame for the election and otherwise have to
reboot the "new" stack master is nothing I really want to care about.
Thank you again

best regards

Michel

2008/10/1 Peter Rathlev <peter at rathlev.dk>

> On Wed, 2008-10-01 at 21:30 +0200, Jeffrey Denton wrote:
> > On Wed, Oct 1, 2008 at 5:44 PM, <pashtuk at gmail.com> wrote:
> > > At the moment I dont see much benefit in setting a Stack Master, only
> > > added complexity.
> > > Am I missing something?
> >
> > It's not complex.  The only annoying part is having to reload the
> > switches that are renumbered.  As to why, the big reason is
> > troubleshooting 6 months or more down the line.  Gi1/0/1 does to the
> > first port on the patch panel, etc.  Instead of later trying to figure
> > out which one is the master, what order the switches are numbered for
> > each stack, and where a certain port is physically located on the
> > stack.
>
> Explicitely selecting a master and having sane numbering isn't always
> the same. We always try to make sure that switch 1 is the top most,
> switch 2 just below et cetera, but we don't care which switch is the
> master. We just let the stack decide. Haven't had any problems with that
> yet. :-)
>
> Regards,
> Peter
>
>
>