[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
cirrus.al.noaa.gov--Re: 19990422: any alternatives to feed nsbf? (fwd)
- Subject: cirrus.al.noaa.gov--Re: 19990422: any alternatives to feed nsbf? (fwd)
- Date: Fri, 23 Apr 1999 09:04:35 -0600 (MDT)
===============================================================================
Robb Kambic Unidata Program Center
Software Engineer III Univ. Corp for Atmospheric Research
address@hidden WWW: http://www.unidata.ucar.edu/
===============================================================================
---------- Forwarded message ----------
Date: Thu, 22 Apr 1999 18:17:24 +0000 (GMT)
From: weather <address@hidden>
To: address@hidden, address@hidden
Subject: cirrus.al.noaa.gov--Re: 19990422: any alternatives to feed nsbf?
Robb,
The ping -s and traceroutes to Colostate are a little shaky.
The traceroute to cirrus.al.noaa.gov is great, a good routing
because they are on the NSN as well. Would it be possible to
feed from them (I assume they are getting everything plus FSL2)
and keep aurora as a backup? I think if we could get a constant
reliable feed that we would be free to feed someone. I am getting
fairly comfortable with the ldm and Unix in general. We would
certainly like to participate as much as possible.
traceroute to cirrus.al.noaa.gov (140.172.240.73), 30 hops max, 40 byte packets
1 nsi-nsbfnm-gw.nsbf.nasa.gov (198.120.3.1) 2.310 ms 2.092 ms 2.282 ms
2 s-JPL-NSBFNM.NSN.NASA.GOV (128.161.167.1) 35.670 ms 33.873 ms 33.681 ms
3 s-NCAR1.NSN.NASA.GOV (128.161.97.2) 82.810 ms 76.565 ms 80.313 ms
4 s-sec.nsn.nasa.gov (128.161.150.2) 105.782 ms 116.077 ms 101.723 ms
5 brdwy-rtr.boulder.noaa.gov (140.172.6.253) 125.253 ms 121.415 ms 100.640
ms
6 2a121-asn1-bb.boulder.noaa.gov (140.172.6.52) 132.313 ms 112.375 ms
149.920 ms
7 cirrus.al.noaa.gov (140.172.240.73) 122.264 ms * 126.809 ms
/usr/local/ldm/logs% ping -s cirrus.al.noaa.gov
PING cirrus.al.noaa.gov: 56 data bytes
64 bytes from cirrus.al.noaa.gov (140.172.240.73): icmp_seq=0. time=96. ms
64 bytes from cirrus.al.noaa.gov (140.172.240.73): icmp_seq=1. time=115. ms
64 bytes from cirrus.al.noaa.gov (140.172.240.73): icmp_seq=2. time=113. ms
64 bytes from cirrus.al.noaa.gov (140.172.240.73): icmp_seq=3. time=97. ms
64 bytes from cirrus.al.noaa.gov (140.172.240.73): icmp_seq=4. time=120. ms
64 bytes from cirrus.al.noaa.gov (140.172.240.73): icmp_seq=5. time=131. ms
64 bytes from cirrus.al.noaa.gov (140.172.240.73): icmp_seq=6. time=123. ms
64 bytes from cirrus.al.noaa.gov (140.172.240.73): icmp_seq=7. time=140. ms
64 bytes from cirrus.al.noaa.gov (140.172.240.73): icmp_seq=8. time=138. ms
64 bytes from cirrus.al.noaa.gov (140.172.240.73): icmp_seq=9. time=113. ms
64 bytes from cirrus.al.noaa.gov (140.172.240.73): icmp_seq=10. time=122. ms
64 bytes from cirrus.al.noaa.gov (140.172.240.73): icmp_seq=11. time=135. ms
^C
----cirrus.al.noaa.gov PING Statistics----
12 packets transmitted, 12 packets received, 0% packet loss
round-trip (ms) min/avg/max = 96/120/140