Most likely the switch is dropping packets because of periodic over subscription of the ports. Dropping TCP traffic has a huge impact on application performance and TCP performance test results.
I suggest enabling flow control on your network and see if the performance improves. This means all switches and NICs. The NICs most likely have flowcontrol enabled by default, but this version of PowerConnect 62xx firmware has flowcontrol disabled by default. Here are the commands to enable flowcontrol on the 62xx.
console> enable
console# configure
console (config)# flowcontrol
Please let us know the results of your tests with flow control enabled.
That worked!!! I'm now getting tcp throughput of 900 Mb/s between nodes with 10 pairs of nodes communicating simultaneously. Thanks! Why doesn't flow control come enabled by default?
bh1633
909 Posts
0
August 27th, 2009 13:00
Please post the output of "show running-config"
cpp6f
6 Posts
0
September 2nd, 2009 16:00
Sorry for the delay, but I had trouble connecting to the switch through the console port (bad cable!!!). Here is the output of show running-config
bh1633
909 Posts
0
September 3rd, 2009 08:00
Most likely the switch is dropping packets because of periodic over subscription of the ports. Dropping TCP traffic has a huge impact on application performance and TCP performance test results.
I suggest enabling flow control on your network and see if the performance improves. This means all switches and NICs. The NICs most likely have flowcontrol enabled by default, but this version of PowerConnect 62xx firmware has flowcontrol disabled by default. Here are the commands to enable flowcontrol on the 62xx.
console> enable
console# configure
console (config)# flowcontrol
Please let us know the results of your tests with flow control enabled.
cpp6f
6 Posts
0
September 3rd, 2009 14:00
That worked!!! I'm now getting tcp throughput of 900 Mb/s between nodes with 10 pairs of nodes communicating simultaneously. Thanks! Why doesn't flow control come enabled by default?