Comment Re:As a non-developer, this is what I see (Score 1) 216
A switch is a switch. What? So you'd be perfectly fine with using a 3com switch at your corporate headquarters for your company with 120+ employees and 100+ servers?
Performance and feature set were known at the time of purpose. No, just like the subject that was originally being discussed, the switch was put in place a long time ago and never swapped out, even though performance and work arounds had to constantly be put in place for it. (In this case, it was daisy-chaining additional switches, including, and I don't know why it wasn't moved into place as the core switch, a 6506.
The switch was chosen for a reason. And that reason was no longer valid. It was, again, going back to the crux of the article, more of a hindrance than a helper at that point. But rather than fix the problem, people kept slapping on band-aids.
If it gets the job done, then what are you complaining about? Because when I went into that company, it WASN'T getting the job done.
How will a NewFangledSuperSwitch make things better? Uh, by not having tons of collisions, dropped packets, slowness and causing loss of production?
How much will it cost? The recommendation (which they followed) cost around $15,000 to add an additional sup II and a couple GB cards to the 6506.
How long will it be until you recommend NewerRangledSuperDuperSwitch? That all depends on how long it takes before the company runs out of space on the 6506, and also takes into consideration EOL and EOS requirements from Cisco. So...for the time being, they're good (and happy now) for the next several years.