[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensolaris-networking-discuss
Subject:    [networking-discuss] (warning) packet length greater than MTU in
From:       Roman Naumenko <roman () frontline ! ca>
Date:       2009-11-20 11:44:42
Message-ID: 853288066.461258746312066.JavaMail.Twebapp () sf-app1
[Download RAW message or body]

copy to networking discuss (from storage)

I have a problem on storage server related to network.

This is on OpenSolaris 121b, on the other side is Windows file server accessing it \
through iscsi. When a user is hammering storage server by copying files back and \
forth, other users connected to Windows file server are experiencing slowness.

root@torgenzsan.local:/export/home/roman/zfs/iscsi_watch# dladm show-ether
LINK PTYPE STATE AUTO SPEED-DUPLEX PAUSE
e1000g0 current up yes 1G-f bi
e1000g1 current up yes 1G-f bi
e1000g2 current up yes 1G-f bi

dladm show-link
LINK CLASS MTU STATE OVER
e1000g0 phys 1500 up --
e1000g1 phys 1500 up --
e1000g2 phys 1500 up --

ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 10.24.1.101 netmask ffffff00 broadcast 10.24.1.255
ether 0:15:17:87:c9:bc
e1000g1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 10.24.254.101 netmask ffffff00 broadcast 10.24.254.255
ether 0:15:17:87:c9:bd
e1000g2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
inet 10.21.3.101 netmask ffff0000 broadcast 10.21.255.255
ether 0:11:a:54:6e:66

snoop -r -o 20112009.cap -d e1000g0

29135 (warning) packet length greater than MTU in buffer offset 0: length=8320
29136 (warning) packet length greater than MTU in buffer offset 8320: length=8320
29137 (warning) packet length greater than MTU in buffer offset 16640: length=8320
29138 (warning) packet length greater than MTU in buffer offset 24960: length=8320
29139 (warning) packet length greater than MTU in buffer offset 33280: length=8320
29141 (warning) packet length greater than MTU in buffer offset 41688: length=8320
29142 (warning) packet length greater than MTU in buffer offset 50008: length=8320
29160 (warning) packet length greater than MTU in buffer offset 0: length=8320
29163 (warning) packet length greater than MTU in buffer offset 8496: length=8320
29180 (warning) packet length greater than MTU in buffer offset 18304: length=8320
29181 (warning) packet length greater than MTU in buffer offset 26624: length=8320
29182 (warning) packet length greater than MTU in buffer offset 34944: length=8320
29183 (warning) packet length greater than MTU in buffer offset 43264: length=8320
29184 (warning) packet length greater than MTU in buffer offset 51584: length=8320

And so on...

In Wireshark packets sizes go up to 56741 (49927,41687,33495,16697,9382)
Among bigger packages mostly 8294 seen.

What I'm thinking about is that Intel Intel I/OAT engine can help screwing things up \
- e1000g0 is Intel one. (I remember there was a command to check BIOS setting).

If anybody is willing to take a look on trace file, please let me know at roman at \
frontline dot ca

--
Roman
-- 
This message posted from opensolaris.org
_______________________________________________
networking-discuss mailing list
networking-discuss@opensolaris.org


[prev in list] [next in list] [prev in thread] [next in thread]