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

20030422: IDD realtime stats and host request(s)

>From: Unidata Support <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200303292224.h2TMOMB2002251 IDD LDM rtstats

Hi Robert,

re: LDM upgrade

>wxmcidas, psnldm, and uldbldm are all now running the latest ldm and are
>running rstats. Let me know if you aren't getting stats.

The real time statistics that we are receiving show that
wxmcidas is still running ldm-6.0.2.  Perhaps you did not change
the runtime link in ~ldm on wxmcidas?

Also, we are seeing that you are requesting HDS and UNIWISC data by IP
address on psnldm.nsbf (the IPs are 140.172.240.190 and 128.118.28.12,
respectively).  We are also seeing wxmcidas requesting HDS and NNEXRAD
data from 192.149.107.23.  Could you change these requests to use the
fully qualified hostname of the upstream feeder?  It will allow the
statistics display software to be able to calculate differential
latencies (latencies between this machine and its immediate upstream
host).  This will do nothing harmful to your receipt of data since
LDM-6 does not accumulate data requests to upstream hosts into single
rpc.ldmds.

We also see that uldbldm.nsbf is requesting data only from psnldm.  If
uldbldm is used for internal purposes only (at least as far as the
LDM/IDD is concerned), we would appreciate you commenting out the
rtstats reporting line in ~ldm/ldmd.conf on uldbldm.  If, on the other
hand, uldbldm is/will be used to relay data to down stream machines at
another physical location, then you should continue to report stats
from uldbldm.  We want the real time stats to reflect those machines
that are directly participating in the IDD.  This includes primary
ingest nodes and relay machines at a site.  It does not include
secondary machines within a department _unless_ those secondary
machines are in a different physical location than the primary ingest
node.

Thanks in advance for all of your help...

Tom