Being very new to networking it was allways going to be a giant leap into our own network and servers! but here is my problem if anyone has some time to help me ;)

We have a 100Mbps line with ip's routed down it into a 3com 4226t switch. Unfortunatly were getting a lot (and i do mean a lot) of errors between the switch and servers resulting in very slow transfer speeds of files.

I assume this is something to do with Traffic Management, but have no idea how to set it up. So far i have managed to restrict speeds to under 3Kbytes/sec at times and maximum by playing around i have achived is 440KBytes/sec.

Anyone out there know how i would go about setting up the switch to operate correctly? Do i need to assign different classifiers and profiles to different ports?

Thank You in advance all,

Neil Bowen

What types of errors are you seeing? Can you post the statistics you're seeing at the switch port and on the server nic?

One thing to check may be the duplex settings. Some switches and nics have trouble negotiating duplex settings. If you're going straight from the switch into a server you'll want to set both sides at full-duplex. If you're going into a hub you'll want to set both sides at half-duplex.

Richard

Switch to Servers , and Switch to Router are all set to 100FD and fully supported. We get the same errors in all modes though...

##########################################
Server 1 statistics...

eth0 Link encap:Ethernet HWaddr 00:10:DC:C6:58:C9
inet addr:217.151.96.105 Bcast:217.151.96.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1379627 errors:0 dropped:0 overruns:0 frame:0
TX packets:31638 errors:870552 dropped:0 overruns:0 carrier:1735337
collisions:0 txqueuelen:100
RX bytes:387573359 (369.6 Mb) TX bytes:29366473 (28.0 Mb)
Interrupt:11 Base address:0x5000

##########################################
Switch port 2 statistics...
Port: 2 Label: RMON Port ..

--------------------------------------------------------------------------------

Receive Statistics Transmit Statistics
Unicast Packets: 7437 Unicast Packets: 89414709
Non Unicast Packets: 199 Non Unicast Packets: 1629542
Octets: 9822888 Octets: 2841334767
Fragments: 1 Collisions: 0

--------------------------------------------------------------------------------

Errors
Undersized: 0 Oversized: 0
CRC Errors: 10 Jabbers: 0

--------------------------------------------------------------------------------

Packet Size Analysis
64 Octets: 79109724 65-127 Octets: 10040436
128-255 Octets: 200299 256-511 Octets: 940289
512-1023 Octets: 177046 1024-1518 Octets: 584093

--------------------------------------------------------------------------------

I think the problem must be in the switch, just no idea what ;/

The fact that it is not showing collisions (the normal indication of a duplex mismatch) is a good thing.

I usually suspect cables when I see that many carrier errors (basically I presume it to be some sort of cross-noise problem). It could also be the sign of a bad NIC on the server, or a bad port on the switch.

Switch configuration settings probably will not be of much help.

What kind of network card do you have in your server? Perhaps it could be a network driver problem.

Richard

well crc errors there that means you probably have some bad cables.

also try setting the speed and duplex to auto on both switches and servers.

Are you using solid or stranded core cables?

We are using solid core cables, it apears that it is something to do with the switch though ;/

Have a technician going round to configure it tomorrow. IF that fails then its cable testing.