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

[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