Bad Performance with 3ware 9550SXU-4LP

[zernik]

Hi Sh-J,

indeed, in the tests.log there is an entry for that:

eth1    Link encap:Ethernet  HWaddr 00:30:48:8A:59:E1  
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:116038240 errors:0 dropped:95 overruns:0 frame:0
          TX packets:160030293 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3660420155 (3.4 GiB)  TX bytes:985991496 (940.3 MiB)

95 droped packages. Is this high? What is the issue? How can I fix it?

Thanks

[zernik]

Here is the post again, bold was displayed in white color:

eth1 Link encap:Ethernet HWaddr 00:30:48:8A:59:E1
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:116038240 errors:0 dropped:95 overruns:0 frame:0
TX packets:160030293 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3660420155 (3.4 GiB) TX bytes:985991496 (940.3 MiB)

[zernik]

Hi Ben,

appreciate your help. I access the NAS via SMB. NFS is off.

All pings were successfull. Some of them are longer than 1ms:

Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64

What else could I do?

Thanks
Paul

[SeanLeyne]

What else could I do?

Find the source of the packet slowdown.

I would suggest the following order of attack (working out from the DSS Server):

- Connect a client directly to the DSS server (you may need a cross-over network cable) using the port that the DSS is currently connected to the network, try all the ports that are available on the DSS

- Change the switch ports that the DSS server is connected to

- Review each of the devices between the clients and the DSS server, change the switch ports used for LAN connectivity.

- Change the switch ports that the test client is connected to

In between each step you want to test connectivity.

Sean

P.S. Change only one thing/connection at a time otherwise you will not be able pinpoint the source of the problem.

[To-M]

Yepper - Just like old school "Change only one thing/connection at a time, otherwise you will not be able pinpoint the source of the problem." Thanks Sean!!

You had it in Bold [B] - i took care of it.