Sorry for delay in response, I was off yesterday. Yes, it's a bottleneck. But now, it's a Gig bottleneck, as opposed to a 100Mb bottleneck :P I didn't design the infrastructure, I've inherited it. We're in the process now of redesigning it, to try to ease the bottlenecks we have. The Cisco 3560 is the first step. We're planning on moving the servers onto this switch, so that traffic would come in through the HP, go to the 3560, go directly to the server in question, then come back through to the workstation. I'm hoping to see a huge easing of bottleneck, and hopefully a gain in performance, though I don't know that we're moving a whole lot of data back and forth to begin with. I'm going to be doing some bandwidth analysis on the port connecting the Cisco and HP this week. Joe Heaton
________________________________ From: Eric E Eskam [mailto:[EMAIL PROTECTED] Sent: Monday, March 03, 2008 2:43 PM To: NT System Admin Issues Subject: RE: Gig ports - copper or fiber? "Joe Heaton" <[EMAIL PROTECTED]> wrote on 02/29/2008 07:09:02 PM: > The connection is between an HP 4108gl chassis, which > all our users are plugged into, and a Cisco 3560 layer 3 > switch, which is doing the routing between the VLANs on the HP. > So all traffic outside the subnet the servers are on, comes in > the HP, goes over to the Cisco, then comes back to the HP to > hit the servers. Then does the reverse to get back to the > workstations... So all your server/workstation traffic is being shuffled - twice - across one gigabit port? Isn't that the classic definition of a bottleneck? Eric Eskam =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= The contents of this message are mine personally and do not reflect any position of the U.S. Government "The human mind treats a new idea the same way the body treats a strange protein; it rejects it." - P. B. Medawar ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
