TMI Jonathan. I didn't need that scenario to think about on a Friday, Yuck!
________________________________ From: Jonathan Link [mailto:[EMAIL PROTECTED] Sent: Friday, February 01, 2008 11:51 AM To: NT System Admin Issues Subject: Re: Switch Purchase Question... Brings new meaning to the phrase knowledge dump. On Feb 1, 2008 11:20 AM, Martin Blackstone <[EMAIL PROTECTED]> wrote: Then you should have no trouble gaining some of that knowledge while you are there. From: Tim Vander Kooi [mailto:[EMAIL PROTECTED] Sent: Friday, February 01, 2008 8:13 AM To: NT System Admin Issues Subject: RE: Switch Purchase Question... Don stores it all a lil farther south than his head Tom. From: Tom Strader [mailto:[EMAIL PROTECTED] Sent: Friday, February 01, 2008 9:51 AM To: NT System Admin Issues Subject: RE: Switch Purchase Question... Not everybody has a BIGHEAD like you Don to store all that information. ________________________________ From: Don Ely [mailto:[EMAIL PROTECTED] Sent: Friday, February 01, 2008 10:43 AM To: NT System Admin Issues Subject: Re: Switch Purchase Question... GUI's are for the unskilled... On Feb 1, 2008 6:50 AM, Andy Shook <[EMAIL PROTECTED]> wrote: I'm surprised that no one has mentioned Dell in these discussions. I've used Dell switches in stacked and single deployments and have enjoyed great success with all the managed products. When I was running the IT department for that law firm (from Hell), I had a Cisco core and Dell in all my access-layer closets and all branch offices and it was a rock solid setup. My only beef with Dell is that the CLI is just different enough from Cisco to piss you off. Example, you can't just type 'sh run' you have to type "show running-config". However, the web mgmt applet was easy-peasy to use. Shook http://www.linkedin.com/in/andyshook -----Original Message----- From: kenw [mailto:[EMAIL PROTECTED] Sent: Friday, February 01, 2008 9:41 AM To: NT System Admin Issues Subject: RE: Switch Purchase Question... I use HP nearly all the time now. While Cisco gear is good, unless you're doing a fairly large implementation, the time it can take to get them configured right can be expensive. I had a situation a while ago, due to Cisco's default configuration for bridge discovery, that caused a lot of hassle. An XP box behind another switch had defaulted to bridge mode, the Cisco saw it, panicked, and disconnected the port, causing a whole section of the network to "go dark". Took a few times to figure out what was happening. My complaint is that neither Cisco nor Microsoft had any documented recognition of the issue, nor any recommendation on how to deal with it, and the support wasn't much help. A caution on the HPs, though: they've brought out some new, low-cost, semi-managed switches that I've put where I can't do anything else. They're still pretty green, don't cluster, and are generally feature-poor. There's an undocumented "feature" wherein if you use ports 1 and 2 for a trunk, and there's a power cycle, they will reset to factory defaults. Also, I'm seeing a lot of compatibility issues with low cost gigabit PC NICs, wherein they don't negotiate speed/duplex/etc. properly, and users with gigabit cards start running at 100MB with truly crappy performance. They seem to be happy with Intel NICs, FWIW. HP's bringing new firmware out for them fairly often. /kenw ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
