20021003 UMASS fos latency

HI Frank, 

In the earlier versions of the LDM..pre 5.2, if the upstream sites do not
report stats, none of the sites below get stats sent in..

If you have downloaded the newest version of the LDM (5.2) we have
implemented a new stats regime that eliminates this problem.

Please see :

http://www.unidata.ucar.edu/cgi-bin/mfs/06/announce/rtstats-description.html

and

http://www.unidata.ucar.edu/staff/chiz/latency/rtstats/rtstats_info.html

for some details. Keep in mind you need LDM 5.2 for rtstats to run..

I will look deeper into your issue, but please let me know if this problem
is persisting, or if it was an artifact of your network being down for
some time..

Thank you,

-Jeff
____________________________                  _____________________
Jeff Weber                                    address@hidden
Unidata Support                               PH:303-497-8676 
COMET Case Study Library                      FX:303-497-8690
University Corp for Atmospheric Research      3300 Mitchell Ln
http://www.unidata.ucar.edu/staff/jweber      Boulder,Co 80307-3000
________________________________________      ______________________

On Thu, 3 Oct 2002, Unidata Support wrote:

> 
> ------- Forwarded Message
> 
> >To: Unidata Support <address@hidden>
> >From: "Frank Colby" <address@hidden>
> >Subject: fos latency
> >Organization: UMass Lowell
> >Keywords: 200210031631.g93GVT117472
> 
> Dear Support,
> 
> We are currently having data trouble here-- cropped up after a planned
> power outage over the weekend.  We can get data, but there are tons of
> reclass messages in the log, and we are getting only about 10-20% of
> what we normally receive, suggesting high latencies.  Our network person
> is going to investigate, but I thought I would look on the fos topology
> page to see what it showed, and not only are we not on the page, but
> both of our upstream providers, brockport and rutgers, are also
> missing.  They aren't reporting any trouble, so I was wondering why they
> don't show up on the topology?
> 
> Frank
> 
> PS  If there are any obvious places to look for network problems like
> this, please let me know.  I'm not sure how creative our network folks
> are.  I can't run traceroute from our node, as the network people have
> disabled it, or the port it works from.
> 
> 
> 
> 
> ------- End of Forwarded Message
> 
>