[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Support #GNI-177943]: Re: tigge config @ cma

YangXin,

In testing, we've clearly demonstrated that there is some sort of packet shaping
or throttling between UCAR and CMA on port 388.  When we move the LDM to another
high numbered port ( > 1024) instead of the default port 388, data transfers
improve by a factor of 10-20.

Initially, we'd like to make a few adjustments on ultrazone and tigge-ldm.cma
to see if theory scales to moving large amounts of data.  We'll be contacting
individuals directly for approval to run services on new ports, change the 
ldmd.conf and stop and restart the LDM.

mike

> Hi, Mike,
> 
> Our networking people run a traceroute test within the same DMZ of our LDM 
> Server and got the following results:
> 
> $ traceroute ncardata.ucar.edu
> traceroute to huron.scd.ucar.edu (128.117.64.208), 30 hops max, 46 byte 
> packets
> 1  210.73.54.1 (210.73.54.1)  0.668 ms  0.573 ms  0.568 ms
> 2  192.168.51.61 (192.168.51.61)  1.023 ms  1.009 ms  1.077 ms
> 3  8.201 (159.226.254.53)  0.698 ms  0.636 ms  0.641 ms
> 4  8.198 (159.226.254.106)  0.686 ms  0.659 ms  0.648 ms
> 5  159.226.1.134 (159.226.1.134)  32.350 ms  32.643 ms  32.337 ms
> 6  192.31.99.165 (192.31.99.165)  224.641 ms  234.621 ms  234.529 ms
> 7  192.31.99.146 (192.31.99.146)  239.783 ms  225.532 ms  229.967 ms
> 8  denv-chic-36.layer3.nlr.net (216.24.186.5)  249.089 ms  249.630 ms  
> 249.190 ms
> 9  192.43.217.137 (192.43.217.137)  248.294 ms  248.344 ms  248.384 ms
> 10  192.43.217.114 (192.43.217.114)  249.244 ms  257.935 ms  249.120 ms
> 11  mlra.ucar.edu (128.117.243.75)  249.406 ms  249.418 ms  249.476 ms
> 12  huron.scd.ucar.edu (128.117.64.208)  249.669 ms  249.433 ms  249.300 ms
> 
> $ traceroute tigge-ldm.ecmwf.int
> traceroute to tigge-ldm.ecmwf.int (193.61.196.74), 30 hops max, 46 byte 
> packets
> 1  210.73.54.1 (210.73.54.1)  0.715 ms  0.581 ms  0.566 ms
> 2  192.168.51.61 (192.168.51.61)  1.036 ms  20.367 ms  27.796 ms
> 3  8.200 (159.226.254.181)  0.641 ms  0.640 ms  0.631 ms
> 4  8.198 (159.226.254.102)  0.663 ms  0.666 ms  0.616 ms
> 5  159.226.1.134 (159.226.1.134)  32.360 ms  32.302 ms  32.280 ms
> 6  192.31.99.165 (192.31.99.165)  227.300 ms  227.092 ms  234.544 ms
> 7  192.31.99.134 (192.31.99.134)  224.751 ms  236.299 ms  225.241 ms
> 8  so-3-0-0.0.rtr.wash.net.internet2.edu (64.57.28.13)  252.093 ms  241.349 
> ms  241.361 ms
> 9  ge-1-0-0.418.rtr.chic.net.internet2.edu (64.57.28.10)  246.555 ms  246.540 
> ms  249.047 ms
> 10  198.32.11.51 (198.32.11.51)  246.662 ms  246.639 ms  246.659 ms
> 11  so-7-0-0.rt1.ams.nl.geant2.net (62.40.112.133)  333.610 ms  333.445 ms  
> 333.564 ms
> 12  so-4-0-0.rt1.lon.uk.geant2.net (62.40.112.138)  341.633 ms  341.558 ms  
> 341.542 ms
> 13  po2-0-0.gn2-gw1.ja.net (62.40.124.198)  341.546 ms  341.566 ms  341.510 ms
> 14  po1-1.lond-scr3.ja.net (146.97.35.97)  341.462 ms  341.472 ms  341.553 ms
> 15  so-0-1-0.read-sbr1.ja.net (146.97.33.141)  343.002 ms  343.013 ms  
> 342.888 ms
> 16  TVN-TVN2.site.ja.net (146.97.42.166)  343.089 ms  342.986 ms  343.172 ms
> 17  * * *
> 18  * * *
> 19  * * *
> 20  * * *
> 21  * * *
> 22  * * *
> 23  * * *
> 24  * * *
> 25  * * *
> 26  * * *
> 27  * * *
> 28  * * *
> 29  * * *
> 30  * * *
> 
> 
> Thanks,
> 
> Regards,
> 
> YangXin,
> Mar 27.
> 
> 
> -------------------------------------------------------------
> From: Unidata IDD TIGGE Support
> Date: 2007-03-24 02:17:30
> To: address@hidden
> Cc: address@hidden; address@hidden; address@hidden; address@hidden; 
> address@hidden; address@hidden; address@hidden; address@hidden; 
> address@hidden; address@hidden; address@hidden; address@hidden; address@hidden
> Subject: [TIGGE #YSF-211129]: TCP tuning for TIGGE tuning
> 
> >Hi YangXin,
> >
> >Your networking people may have to run the test to see meaningful results.  
> >It's likely that
> >network security is blocking certain packets that are needed and used for 
> >traceroute.
> >
> >mike
> >
> >> Hi, Mike,
> >>
> >> I appologize for the late of my reply. I have just take some time to do a 
> >> study of the network,
> >> sorry for my limited knowledge on networking.
> >>
> >> When doing the "traceroute tigge-ldm.ecmwf.int" I get the following output 
> >> which confused me a little:
> >>
> >> [root@tgn01 /root]# traceroute tigge-ldm.ecmwf.int
> >> traceroute to tigge-ldm.ecmwf.int (193.61.196.74), 30 hops max, 46 byte 
> >> packets
> >> 1  * * *
> >> 2  * * *
> >> 3  * * *
> >> 4  * * *
> >> 5  * * *
> >> 6  * * *
> >> 7  * * *
> >> 8  * * *
> >> 9  * * *
> >> 10  * * *
> >> 11  * * *
> >> 12  * * *
> >> 13  * * *
> >> 14  * * *
> >> 15  * * *
> >> 16  * * *
> >> 17  * * *
> >> 18  * * *
> >> 19  * * *
> >> 20  * * *
> >> 21  * * *
> >> 22  * * *
> >> 23  * * *
> >> 24  * * *
> >> 25  * * *
> >> 26  * * *
> >> 27  * * *
> >> 28  * * *
> >> 29  * * *
> >> 30  * * *
> >>
> >> For the same test to NCAR LDM Server, the case is similar:
> >>
> >> [root@tgn01 /root]# traceroute  tigge-ldm.ecmwf.int
> >> traceroute to tigge-ldm.ecmwf.int (193.61.196.74), 30 hops max, 46 byte 
> >> packets
> >> 1  * * *
> >> 2  * * *
> >> 3  * * *
> >> 4  * * *
> >> 5  * * *
> >> 6  * * *
> >> 7  * * *
> >> 8  * * *
> >> 9  * * *
> >> 10  * * *
> >> 11  * * *
> >> 12  * * *
> >> 13  * * *
> >> 14  * * *
> >> 15  * * *
> >> 16  * * *
> >> 17  * * *
> >> 18  * * *
> >> 19  * * *
> >> 20  * * *
> >> 21  * * *
> >> 22  * * *
> >> 23  * * *
> >> 24  * * *
> >> 25  * * *
> >> 26  * * *
> >> 27  * * *
> >> 28  * * *
> >> 29  * * *
> >> 30  * * *
> >>
> >> May I do the traceroute with some specific options?
> >>
> >> Thanks,
> >>
> >> YangXin,
> >> Mar 24.
> >
> >
> >Ticket Details
> >===================
> >Ticket ID: YSF-211129
> >Department: Support IDD TIGGE
> >Priority: Critical
> >Status: Closed
> >
> 
> 


Ticket Details
===================
Ticket ID: GNI-177943
Department: Support IDD TIGGE
Priority: Normal
Status: Closed