Paul,
Was the machine having other traffic while you pinged? There was a
e1000g LSO issue on snv_111b. But Ultra 27 equips with ICH10 on-board
NIC which doesn't support LSO.
I think the very first thing is to identify the long latency is on the
transmission side, receiving side or both. If there is another
accessible machine, to achieve this, you can enable wireshark or snoop
on both machines, ping one system, record the departure and arrival
timestamps of both the request and the echo packets. And please paste
the problematic samples to us.
Another suggestion is to disable the pause frame by running "dladm
set-linkprop e1000g0 -p flowctrl=no".
Thanks,
Miles
Paul Hinker wrote:
About 3-4 weeks ago I suddenly started seeing high latency on the e1000g
interface of my Ultra 27.
ping -s yahoo.com
PING yahoo.com: 56 data bytes
64 bytes from ir1.fp.vip.re1.yahoo.com (69.147.125.65): icmp_seq=0. time=74.611
ms
64 bytes from ir1.fp.vip.re1.yahoo.com (69.147.125.65): icmp_seq=1.
time=5052.370 ms
64 bytes from ir1.fp.vip.re1.yahoo.com (69.147.125.65): icmp_seq=2.
time=4052.442 ms
64 bytes from ir1.fp.vip.re1.yahoo.com (69.147.125.65): icmp_seq=3.
time=3052.408 ms
64 bytes from ir1.fp.vip.re1.yahoo.com (69.147.125.65): icmp_seq=4.
time=2052.412 ms
64 bytes from ir1.fp.vip.re1.yahoo.com (69.147.125.65): icmp_seq=5.
time=1052.437 ms
64 bytes from ir1.fp.vip.re1.yahoo.com (69.147.125.65): icmp_seq=6. time=68.882
ms
64 bytes from ir1.fp.vip.re1.yahoo.com (69.147.125.65): icmp_seq=7. time=68.949
ms
64 bytes from ir1.fp.vip.re1.yahoo.com (69.147.125.65): icmp_seq=8. time=71.530
ms
64 bytes from ir1.fp.vip.re1.yahoo.com (69.147.125.65): icmp_seq=9. time=71.510
ms
64 bytes from ir1.fp.vip.re1.yahoo.com (69.147.125.65): icmp_seq=10. time=69.161
I don't believe this is a problem with my ISP or home network since I have a
number of other
machines (laptop, Mac, PS3) that use the same network and do not exhibit this
behavior.
The routine table looks fine to me:
$ netstat -rn
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ---------- ---------
default 192.168.1.1 UG 1 27009
192.168.1.0 192.168.1.130 U 1 1848 e1000g0
127.0.0.1 127.0.0.1 UH 1 34 lo0
Routing Table: IPv6
Destination/Mask Gateway Flags Ref Use If
--------------------------- --------------------------- ----- --- ------- -----
fe80::/10 fe80::221:28ff:fe26:337f U 1 0 e1000g0
::1 ::1 UH 1 10 lo0
$ dladm show-ether
LINK PTYPE STATE AUTO SPEED-DUPLEX PAUSE
e1000g0 current up yes 100M-f bi
vboxnet0 current unknown no 0M none
$ dladm show-linkprop e1000g0
LINK PROPERTY PERM VALUE DEFAULT POSSIBLE
e1000g0 speed r- 100 100 --
e1000g0 autopush -w -- -- --
e1000g0 zone rw -- -- --
e1000g0 duplex r- full full half,full
e1000g0 state r- up up up,down
e1000g0 adv_autoneg_cap rw 1 1 1,0
e1000g0 mtu rw 1500 1500 --
e1000g0 flowctrl rw bi bi no,tx,rx,bi
e1000g0 adv_1000fdx_cap r- 1 1 1,0
e1000g0 en_1000fdx_cap rw 1 1 1,0
e1000g0 adv_1000hdx_cap r- 0 1 1,0
e1000g0 en_1000hdx_cap r- 0 1 1,0
e1000g0 adv_100fdx_cap r- 1 1 1,0
e1000g0 en_100fdx_cap rw 1 1 1,0
e1000g0 adv_100hdx_cap r- 1 1 1,0
e1000g0 en_100hdx_cap rw 1 1 1,0
e1000g0 adv_10fdx_cap r- 1 1 1,0
e1000g0 en_10fdx_cap rw 1 1 1,0
e1000g0 adv_10hdx_cap r- 1 1 1,0
e1000g0 en_10hdx_cap rw 1 1 1,0
e1000g0 maxbw rw -- -- --
e1000g0 cpus rw -- -- --
e1000g0 priority rw high high low,medium,high
e1000g0 tagmode rw vlanonly vlanonly normal,vlanonly
I'm running 2009.06 snv_111b X86
$ cat /etc/release
OpenSolaris 2009.06 snv_111b X86
Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 07 May 2009
Around that same time I had an 'Update All' from the package manager but I'm
not convinced the two are related since I believe the high latency had shown up
first (which prompted the update).
Any clues would be much appreciated.
Paul
_______________________________________________
networking-discuss mailing list
[email protected]
