From: Rich Glazier (rglazier2002@yahoo.com)
Date: Mon Jan 26 2004 - 12:19:35 EST
I zeroed out all the netstat counters and nfsstat
counters, and then did my vdump | vrestore between the
two nodes (from Mars to Jupiter). It's the only
network traffic on Jupiter. I have an AdvFS
filesystem from Mars nfs mounted on Jupiter (standard-
udp, no rsize or wsize settings). I then vdump |
vrestore the nfs mounted filesystem on Jupiter to a
local AdvFS filesystem on Jupiter. Maybe my
fragmentation is the AdvFS to NFS to AdvFS pipe. I'm
just trying to tune this dump to get it as fast as
possible. Maybe it's as fast as it can be. The
storage is a 0+1 lun using 10k drives on a dual
controller MSA1000. Here is the output from the
systems. Again, it's the "fragments recieved" on the
'netstat -p ip' output that I'm curious about.
Thanks for the help.
Mars ---> Jupiter
mars# hwmgr get att -cat network -a name -a model -a
MTU_size -a media_speed -a full_duplex
87:
name = ee1
model = Intel 82559
MTU_size = 1500
media_speed = 100
full_duplex = 1
jupiter# hwmgr get att -cat network -a name -a model
-a MTU_size -a media_speed -a full_duplex
59:
name = ee0
model = Intel 82559
MTU_size = 1500
media_speed = 100
full_duplex = 1
jupiter# df -k
Filesystem 1024-blocks Used Available
Capacity Mounted on
root_domain#root 7643312 135482 7501592
2% /
/proc 0 0 0
100% /proc
usr_domain#usr 8267016 2771399 5448176
34% /usr
var_domain#var 50849968 148455 50693488
1% /var
DR#prod 142255568 37082281 65829944
37% /prod
DR#prod2 142255568 39150561 65829944
38% /prod2
172.16.0.1:/prod 68157440 35634948 32312536
53% /prod_on_mars
jupiter# time vdump -0f - /prod_on_mars | vrestore -xf
- -D /prod
.
.
.
real 2h6m37.96s
user 2m31.45s
sys 17m49.28s
jupiter# netstat -p ip
ip: Last Zeroed: Fri Jan 23
16:19:41 2004
27229952 total packets received
0 bad header checksums
0 with size smaller than minimum
0 with data size < data length
0 with header length < data size
0 with data length < header length
25121406 fragments received
0 fragments dropped (duplicate or out of
space)
1 fragment dropped after timeout
0 packets forwarded
0 packets not forwardable
0 packets denied access
0 redirects sent
0 packets with unknown or unsupported protocol
3033828 packets consumed here
3104604 total packets generated here
0 lost packets due to resource problems
925282 total packets reassembled ok
0 output packets fragmented ok
0 output fragments created
0 packets with special flags set
jupiter# netstat -p tcp
tcp: Last Zeroed: Fri Jan 23
16:20:46 2004
623233 packets sent
240192 data packets (4506006 bytes)
0 data packets (0 bytes) retransmitted
248738 ack-only packets (4141 delayed)
0 URG only packets
0 window probe packets
0 window update packets
134303 control packets
540130 packets received
131663 acks (for 790586 bytes)
120114 duplicate acks
0 acks for unsent data
242625 packets (123022 bytes) received
in-sequence
40766 completely duplicate packets (0
bytes)
0 packets with some duplicate data (0
bytes duped)
2491 out-of-order packets (0 bytes)
0 packets (0 bytes) of data after
window
0 window probes
4 window update packets
0 packets received after close
0 discarded for bad checksums
0 discarded for bad header offset
fields
0 discarded because packet was too
short
122663 connection requests
2492 connection accepts
122299 connections established (including
accepts)
134339 connections closed (including 116370
drops)
2856 embryonic connections dropped
251470 segments updated rtt (of 370696
attempts)
5712 retransmit timeouts
0 connections dropped by rexmit
timeout
0 persist timeouts
3117 keepalive timeouts
63 keepalive probes sent
2856 connections dropped by keepalive
jupiter# netstat -p udp
udp: Last Zeroed: Fri Jan 23
16:20:41 2004
2482715 packets sent
2486560 packets received
0 incomplete headers
0 bad data length fields
0 bad checksums
0 full sockets
4263 for no port (4263 broadcasts, 0
multicasts)
0 input packets missed pcb cache
jupiter# nfsstat -c
Client rpc:
tcp: calls badxids badverfs timeouts
newcreds
0 0 0 0
0
creates connects badconns inputs
avails interrupts
0 0 0 0
0 0
udp: calls badxids badverfs timeouts
newcreds retrans
5326646 19 0 853
0 853
badcalls timers waits
0 1283 0
Client nfs:
calls retrans badcalls nclget
nclsleep ndestroys ncleans
5326646 0 0 5326646
0 0 5326646
Client nfs V2: (0 out of 5326646 calls)
null getattr setattr root
lookup readlink read
0 0% 0 0% 0 0% 0 0% 0
0% 0 0% 0 0%
wrcache write create remove
rename link symlink
0 0% 0 0% 0 0% 0 0% 0
0% 0 0% 0 0%
mkdir rmdir readdir statfs
0 0% 0 0% 0 0% 0 0%
Client nfs V3: (5326646 out of 5326646 calls)
null getattr setattr lookup
access readlink read
0 0% 683K 12% 0 0% 1785K 33% 614K
11% 141 0% 2152K 40%
write create mkdir symlink
mknod remove rmdir
0 0% 0 0% 0 0% 0 0% 0
0% 0 0% 0 0%
rename link readdir readdir+
fsstat fsinfo pathconf
0 0% 0 0% 39480 0% 54097 1% 36
0% 5 0% 31 0%
commit
0 0%
--- Rich Glazier <rglazier2002@yahoo.com> wrote:
> None of the Tru64 networking books really break down
> netstat output, which is what I'm looking for. Can
> anyone tell me why I see very few "fragments
> recieved"
> versus "packets recieved" on all of my server's but
> this one? The packets recieved and fragments
> recieved
> are almost equal on Jupiter. Does this have to do
> with MTU size perhaps? All the servers on my
> network
> are set up the same (as far as I can tell). I'm
> just
> looking for guidance as to what's an acceptable
> value
> (if any) for "fragments recieved". Thanks.
>
>
> jupiter# netstat -p ip
> ip:
> 29541100 total packets received
> 0 bad header checksums
> 0 with size smaller than minimum
> 0 with data size < data length
> 0 with header length < data size
> 0 with data length < header length
> 27625393 fragments received
> 0 fragments dropped (duplicate or out of
> space)
> 1 fragment dropped after timeout
> 0 packets forwarded
> 0 packets not forwardable
> 0 packets denied access
> 0 redirects sent
> 0 packets with unknown or unsupported
> protocol
> 2922818 packets consumed here
> 2924202 total packets generated here
> 4656 lost packets due to resource problems
> 4656 host unreachable
> 1007111 total packets reassembled ok
> 0 output packets fragmented ok
> 0 output fragments created
> 0 packets with special flags set
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free web site building tool.
> Try it!
> http://webhosting.yahoo.com/ps/sb/
>
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:49 EDT