scottman29
asked on
speed issues with 3560 switches
I have a series of trunked 3560 switches. When I patch into one of the switches and try to connect through it to one of my servers, the connection is slow. For example, trying to pull down files off a share, the speed crawls.
The 3560's are not configured to route. They trunk back to a 3550, which is configured to route back to our core.
What is interesting is that when I connect a netgear switch to one of the 3560's as an access port, anything connecting to that switch works fine.
So it seems to be some kind of trunking issue, but I can't seem to put my finger on it.
Any insight would be helpful.
The 3560's are not configured to route. They trunk back to a 3550, which is configured to route back to our core.
What is interesting is that when I connect a netgear switch to one of the 3560's as an access port, anything connecting to that switch works fine.
So it seems to be some kind of trunking issue, but I can't seem to put my finger on it.
Any insight would be helpful.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ken,
This was it. On the 3560, the ports were 1/2 duplex, and on the 3550, they were full. On the 3560, I set the mdix auto, and then on the 3550 I hardcoded the speed to 100 and the duplex to 1/2. Do you know why this happens? If I had a 3560 to 3560 trunk would the auto negotiate work properly? Or does it typically not work in general?
This was it. On the 3560, the ports were 1/2 duplex, and on the 3550, they were full. On the 3560, I set the mdix auto, and then on the 3550 I hardcoded the speed to 100 and the duplex to 1/2. Do you know why this happens? If I had a 3560 to 3560 trunk would the auto negotiate work properly? Or does it typically not work in general?
Glad you found the problem. With autonegotiation turned on here is how it works.
If both ports are set to auto it will try to autonegotiate. On some older switches this doesn't always work so well. Even cisco to cisco. blows your mind. Any way if one port is hard-coded and the other is auto OR if it can't figure out how to auto set the duplex the default settings get used which are 100/half.
So typically what you need to do is run auto on both sides. If auto is not giving the right settings on both sides, then you want to hard code both sides. You want to hard code them to 100 Full though. You won't get the collisions with full duplex like you get with half. Do this to both sides and you should be good to go.
If both ports are set to auto it will try to autonegotiate. On some older switches this doesn't always work so well. Even cisco to cisco. blows your mind. Any way if one port is hard-coded and the other is auto OR if it can't figure out how to auto set the duplex the default settings get used which are 100/half.
So typically what you need to do is run auto on both sides. If auto is not giving the right settings on both sides, then you want to hard code both sides. You want to hard code them to 100 Full though. You won't get the collisions with full duplex like you get with half. Do this to both sides and you should be good to go.
ASKER
I think part of the problem was that the 3560 is an older 3560 and is 1/2 duplex. Go figure it's working now. Thanks for your help!
ASKER