[c-nsp] Catalyst 3750 stacks with many members

[Mike Louis]

split the stacks into smaller groups

________________________________________
From: cisco-nsp-bounces at puck.nether.net [cisco-nsp-bounces at puck.nether.net] On Behalf Of Dale Shaw [dale.shaw+cisco-nsp at gmail.com]
Sent: Friday, November 14, 2008 1:19 PM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] Catalyst 3750 stacks with many members

Hi all,

We have a few large (>6 member) cat3750 stacks in our environment,
most in L2 edge/access roles, and most providing PoE to cisco IP
phones.

Does anyone have any tips as to how to make large stacks more
reliable? We're seeing really high CPU and have found you need to be
really careful doing anything that has the potential to swamp the CPU
-- the other day I crashed a stack master by clearing the CDP
neighbour table (a bit silly in hindsight, given the number of CDP
table entries [phones], but I was troubleshooting a stale neighbour
problem).

Does changing to the 'VLANs' SDM template for switch stacks in this
role make any difference? These stacks don't do any routing, or
traffic ACLs.

We've tried 12.2(40)SE, 12.2(44)SE2 and 12.2(44)SE3. Our biggest stack
is 7 members. You're supposed to be able to stack 9 of these things
(and I don't recall reading about any caveats), so it's a bit
concerning. Disabling certain functionality (e.g. CDP) to stabilise is
one thing, but long term it would be nice if it 'just worked'.

cheers,
Dale
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Note: This message and any attachments is intended solely for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, legally privileged, confidential, and/or exempt from disclosure.  If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited.  If you have received this communication in error, please notify the original sender immediately by telephone or return email and destroy or delete this message along with any attachments immediately.