Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Baystack 350-24T - So slow it kills the network

Status
Not open for further replies.

tharryman

IS-IT--Management
Sep 18, 2002
3
US
Baystack 350-24T switch with fiber module
Hardware RevD
FirmWare 1.48
Software 4.2.0.12

Reset to Default Settings, then add switch IP address.

Whenever we hook this up to the network, it slows down traffic to the point that the network is unusable.

Any help greatly appreciated!!
 
Any chance that the setting for the fiber module on the 350 end does not match the settings at the other end?

if one side is Half Duplex while the other side is Full Duplex, throughput is lousy. Best is both sides Full Duplex, but they MUST match.

(where DOES the fiber module go, if it is not the connection to the main network I am all wet) I tried to remain child-like, all I acheived was childish.
 
Thank you for your response, but....

The fiber module is not in use at all - only the 24 10/100 RJ45 ports.

Any other ideas? I'd hate to have to get rid of this switch!
 
How do you 'hook this up to the network'? via copper? what device is the other end? how long is the copper run? I tried to remain child-like, all I acheived was childish.
 
When it is hooked up, all UTP copper cat 5e, no runs more than 3m in length.

When the switch is changed out for simple unmanaged $150 switch, everything runs fine. Put in Baystack - easier to use snail mail.

For testing, only two ports in use to two workstations. Still slower than same setup with other switch, but not nearly as slow as when it is hooked up to the network.

Because when switch is changed out, performance increases roughly 20x (sez our test programs), I am going on assumption that is network level of TCP/IP stack, not physical.

Thanks again for your response! I eagerly await someone's revelation on how to fix this!
 
I am guessing the 350 has difficulty auto negotiating with the other switch, the one you won't mention.

Have you tried forcing the Crossover port to 10 Full at each end? (if the other switch is unmanaged, you may have to try 100/half but it will not be as perky, but it will be faster than a mismatch.

Are there any errors on the crossover port in the 350?

Does the Un-named switch have any diagnostics? does it show errors? I tried to remain child-like, all I acheived was childish.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top