Re: [conduit] Large CONDUIT latencies to UW-Madison idd.aos.wisc.edu starting the last day or two.

  • To: "Patrick L. Francis" <wxprofessor@xxxxxxxxx>
  • Subject: Re: [conduit] Large CONDUIT latencies to UW-Madison idd.aos.wisc.edu starting the last day or two.
  • From: Carissa Klemmer - NOAA Federal <carissa.l.klemmer@xxxxxxxx>
  • Date: Mon, 22 Feb 2016 09:49:20 -0500
Karen,

There was definitely something going on outside of NCEPs servers. We heard
from a couple of folks from Colorado to Oregon having issues that moved
their services to a new location and rates went back to normal. Since you
are in Ok it may have been further reaching into the mid-west than we
heard. Are you still having issues? We are trying to gauge from our users
now to see if something is still lingering out there.


Carissa Klemmer
NCEP Central Operations
Dataflow Team Lead
301-683-3835

On Mon, Feb 22, 2016 at 8:52 AM, Patrick L. Francis <wxprofessor@xxxxxxxxx>
wrote:

>
>
> All,
>
> Something bigger than just CONDUIT users occurred on the 19th. We had
> numerous users of other servers complain of similar drops in transfer
> rates. A few of them were also able to move downloads to a new location
> where speeds were normal. We believe that this issue was outside of NCEP
> due to that reasoning. Having said that though, is anyone still seeing
> abnormal rates?
>
>
>
>
>
> Hi Carissa J
>
>
>
> From our Amazon location in VA, everything is fine as it was on Fridayâ
> From our colo facility, packet loss is still shown via 140.90.111.36, which
> is the hop from gigapop to ncep.. here is an MTR showing the packet loss:
>
>
>
> http://drmalachi.org/files/ncep/he-ncep.2016.02.22.jpg
>
>
>
> Notice that since our colo is directly on the Hurricane Electric backbone,
> there are only a few hops to get to the ncep server, and pings only jump
> once they reach gigapop.
>
>
>
> Here is a screen cap of current download speeds for 0.25deg gfs from the
> ncep server to our colo:
>
>
>
> http://drmalachi.org/files/ncep/he-ncep.wget.2016.02.22.jpg
>
>
>
> In order to ensure proper delivery, we have setup a push / pull from our
> amazon box to the colo, but most people probably wonât have that
> flexibility.. The issue appears to potentially be related to
> packetfiltering and / or redirection / funneling via certain routes, but
> thatâs just a guess J
>
>
>
> Happy Monday J
>
>
>
> Cheers,
>
>
>
> --patrick
>
>
>
>
>
>
>
>
>
> -------------------------------------------------------
>
> Patrick L. Francis
>
> Vice President of Research & Development
>
>
>
> Aeris Weather
>
>
>
> http://aerisweather.com/
>
> http://modelweather.com/
>
>
>
> http://facebook.com/wxprofessor/
>
>
>
> --------------------------------------------------------
>