[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20040903:LDM time requirements
- Subject: 20040903:LDM time requirements
- Date: Fri, 3 Sep 2004 14:37:23 -0600 (MDT)
Hi Tim,
Here is the URL that describes what you desire:
http://my.unidata.ucar.edu/content/software/ldm/ldm-6.1.0/basics/platform.html
It specifies :
"Have a monotonic clock accurate to within one second."
..of course to the milli-second is preferred :)
This document also links to ntp.org for further guidance.
Busy tracking Frances..she is undergoing some changes currently!
Have a fun and safe weekend,
Jeff
---------------------------------------------------------------------
Jeff Weber address@hidden :
Unidata Program Center PH:303-497-8676 :
University Corp for Atmospheric Research 3300 Mitchell Ln :
http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000 :
---------------------------------------------------------------------
On Fri, 3 Sep 2004, Unidata Support wrote:
>
> ------- Forwarded Message
>
> >To: address@hidden
> >cc: Chris D Gilbert <address@hidden>
> >From: "Tim D Crum" <address@hidden>
> >Subject: [Fwd: Re: [Fwd: AWIPS NTP Issues]]
> >Organization: US DOC/NOAA/NWS/NEXRAD OSF
> >Keywords: 200409032013.i83KDXvq003891
>
>
> --------------3DB242A8EEAD7F25F689683E
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> Please help us out and reply to Chris' question below about the timing
> requirement.
>
> Thank you.
>
>
> Tim
>
>
> -------- Original Message --------
> Subject: Re: [Fwd: AWIPS NTP Issues]
> Date: Fri, 03 Sep 2004 15:01:29 -0500
> From: "Chris D Gilbert" <address@hidden>
> Organization: US DoC/NOAA/NWS/NEXRAD OSF
> To: Jami Casamento <address@hidden>,Tim D Crum
> <address@hidden>
> CC: Steven D Smith <address@hidden>,William J
> Armstrong <address@hidden>
> References: <address@hidden>
>
> Jami & Tim,
>
> We know KICT has a problem with NTP due to Build 6 Beta Testing. It is
> the only one with build 6 loaded. The RPG router IOS was upgraded in
> build 6, and MAY have a NTP problem. We are checking with Cisco on
> this...
>
> However, that still doesn't explain why KLCH, KRGX, and KDAX are having
> problems. Build 5.0 NTP has been working good for all the other
> sites... When we find the time (no pun intended), I guess we will have
> to call each one of these sites to further investigate the problem. We
> will try to do what we can, and let you know...
>
> One more question - If LDM is so time sensitive... What is the Unidata
> LDM Time requirement for Archive II? We will try to keep an accurate
> clock on the BDDS, but no one has documented the LDM requirement?
> Anyone have a Unidata document explaining this?
>
> Thanks,
> Chris
>
>
>
>
>
> Jami Casamento wrote:
>
> > Chris,
> >
> > Can we make sure the BDDS Servers are configured to accept the NTP
> > broadcast? Does the ROC have remote access to the BDDS Servers?
> >
> > Thanks,
> > -Jami
> >
> > ----------------------------------------------------------------
> >
> Subject:
> Re: AWIPS NTP Issues
> From:
> Diane Deitz <address@hidden>
> Date:
> Fri, 03 Sep 2004 09:37:26 -0400
> To:
> Jami Casamento <address@hidden>
> >
> To:
> Jami Casamento <address@hidden>
> CC:
> "Jackson, Tom" <address@hidden>, Phil Cragg
> <address@hidden>, Warren Blanchard <address@hidden>
> >
> > Jami,
> > I checked the times at the four AWIPS sites where the radars are and
> > they are all correct. Why don't you try restarting ntp on the BDDS
> > servers - perhaps the daemon is not even running.
> >
> > Jami Casamento wrote:
> >
> >
> >> TJ & Diane,
> >>
> >> Would it be possible to check the time servers at the following
> >> sites for accuracy:
> >>
> >> KICT
> >> KLCH
> >> KRGX
> >> KDAX
> >>
> >> We are noticing some incorrect times on our BDDS Servers that are
> >> configured to listen for the NTP broadcast.
> >>
> >> Thanks,
> >> -Jami
> >>
> >> "Jackson, Tom" wrote:
> >>
> >>
> >> > We use the application server at each site as the NTP time source
> >> > for that site. The site application server I believe is updated
> >> > once daily, and the master AWIPS time source I believe is updated
> >> > once weekly from either Boulder or the Naval Observatory.
> >> >
> >> > TJ
> >> >
> >> > -----Original Message-----
> >> > From: Diane Deitz [mailto:address@hidden]
> >> > Sent: Monday, August 30, 2004 11:43 AM
> >> > To: Phil Cragg
> >> > Cc: Jami Casamento; Ted Ulinski; address@hidden; Jackson,
> >> > Tom
> >> > Subject: Re: AWIPS NTP Issues
> >> >
> >> > As I understand it, at least on the ORPG end, it takes the time off
> >> > the
> >> > AWIPS application server via the ntp broadcast by adding the AWIPS
> >> > subnet to
> >> > their frame relay hub router configuration.
> >> >
> >> > TJ/John - can you 'boys' add anything?
> >> >
> >> > Phil Cragg wrote:
> >> >
> >> >
> >> >> Diane,
> >> >>
> >> >> An issue involving NTP has come up. We were told that you could
> >> >> steer us
> >> >> in the right direction.
> >> >>
> >> >> Currently we are working on the NEXRAD Level II, Archive Data
> >> >> Project.
> >> >> We have 4 BDDS servers at various WFO sites that are not being
> >> >> updated
> >> >> with the correct times using NTP. This is causing latency issues
> >> >> with
> >> >> the Level II data being sent via LDM from the WFO site BDDS
> >> >> servers to
> >> >> the Regional Headquarters. Any information you could provide us
> >> >> on
> >> >> how NTP is currently configured on the AWIPS LAN would be greatly
> >> >> appreciated. With your help, I am sure we will be able to
> >> >> resolve our
> >> >> problem.
> >> >>
> >> >> The sites in which the BDDS servers are currently being affected:
> >> >>
> >> >> KICT
> >> >> KLCH
> >> >> KRGX
> >> >> KDAX
> >> >>
> >> >> Thank you,
> >> >> Phil
> >> >>
>
> --------------3DB242A8EEAD7F25F689683E
> Content-Type: text/html; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
> <html>
> <body text="#000000" bgcolor="#FFFFFF">
> Please help us out and reply to Chris' question below about the timing
> requirement.
> <p>Thank you.
> <br>
> <p>Tim
> <br>
> <p>-------- Original Message --------
> <table BORDER=0 CELLSPACING=0 CELLPADDING=0 >
> <tr>
> <th ALIGN=RIGHT VALIGN=BASELINE NOWRAP>Subject: </th>
>
> <td>Re: [Fwd: AWIPS NTP Issues]</td>
> </tr>
>
> <tr>
> <th ALIGN=RIGHT VALIGN=BASELINE NOWRAP>Date: </th>
>
> <td>Fri, 03 Sep 2004 15:01:29 -0500</td>
> </tr>
>
> <tr>
> <th ALIGN=RIGHT VALIGN=BASELINE NOWRAP>From: </th>
>
> <td>"Chris D Gilbert" <address@hidden></td>
> </tr>
>
> <tr>
> <th ALIGN=RIGHT VALIGN=BASELINE NOWRAP>Organization: </th>
>
> <td>US DoC/NOAA/NWS/NEXRAD OSF</td>
> </tr>
>
> <tr>
> <th ALIGN=RIGHT VALIGN=BASELINE NOWRAP>To: </th>
>
> <td>Jami Casamento <address@hidden>,Tim D Crum <address@hidden></td>
> </tr>
>
> <tr>
> <th ALIGN=RIGHT VALIGN=BASELINE NOWRAP>CC: </th>
>
> <td>Steven D Smith <address@hidden>,William J Armstrong
> <address@hidden></td>
> </tr>
>
> <tr>
> <th ALIGN=RIGHT VALIGN=BASELINE NOWRAP>References: </th>
>
> <td><address@hidden></td>
> </tr>
> </table>
>
> <p>Jami & Tim,
> <p>We know KICT has a problem with NTP due to Build 6 Beta Testing. It
> is the only one with build 6 loaded. The RPG router IOS was upgraded in
> build 6, and <b>MAY </b>have a NTP problem. We are checking with Cisco
> on this...
> <p>However, that still doesn't explain why KLCH, KRGX, and KDAX are having
> problems. Build 5.0 NTP has been working good for all the other
> sites...
> When we find the time (no pun intended), I guess we will have to call each
> one of these sites to further investigate the problem. We will try to do
> what we can, and let you know...
> <p>One more question - If LDM is so time sensitive... What is the Unidata
> LDM Time requirement for Archive II? We will try to keep an accurate
> clock on the BDDS, but no one has documented the LDM requirement?
> Anyone have a Unidata document explaining this?
> <p>Thanks,
> <br>Chris
> <br>
> <br>
> <br>
> <br>
> <p>Jami Casamento wrote:
> <blockquote cite="address@hidden" type="cite">
> <pre wrap="">Chris,
>
> Can we make sure the BDDS Servers are configured to accept the NTP
> broadcast? Does the ROC have remote access to the BDDS Servers?
>
> Thanks,
> -Jami
> </pre>
>
> <hr size="4" width="90%">
> <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" class="header-part1"
> >
> <caption><tbody>
> <br></tbody></caption>
>
> <tr>
> <td>
> <div class="headerdisplayname" style="display: inline;">Subject: </div>
> Re: AWIPS NTP Issues</td>
> </tr>
>
> <tr>
> <td>
> <div class="headerdisplayname" style="display: inline;">From: </div>
> Diane Deitz <a href="mailto:address@hidden"
> class="moz-txt-link-rfc2396E"><address@hidden></a></td>
> </tr>
>
> <tr>
> <td>
> <div class="headerdisplayname" style="display: inline;">Date: </div>
> Fri, 03 Sep 2004 09:37:26 -0400</td>
> </tr>
>
> <tr>
> <td>
> <div class="headerdisplayname" style="display: inline;">To: </div>
> Jami Casamento <a href="mailto:address@hidden"
> class="moz-txt-link-rfc2396E"><address@hidden></a></td>
> </tr>
> </table>
>
> <table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="100%" class="header-part2"
> >
> <caption><tbody>
> <br></tbody></caption>
>
> <tr>
> <td>
> <div class="headerdisplayname" style="display: inline;">To: </div>
> Jami Casamento <a href="mailto:address@hidden"
> class="moz-txt-link-rfc2396E"><address@hidden></a></td>
> </tr>
>
> <tr>
> <td>
> <div class="headerdisplayname" style="display: inline;">CC: </div>
> "Jackson, Tom" <a href="mailto:address@hidden"
> class="moz-txt-link-rfc2396E"><address@hidden></a>,
> Phil Cragg
> <a href="mailto:address@hidden"
> class="moz-txt-link-rfc2396E"><address@hidden></a>,
> Warren Blanchard
> <a href="mailto:address@hidden"
> class="moz-txt-link-rfc2396E"><address@hidden></a></td>
> </tr>
> </table>
>
> <pre wrap="">Jami,
> I checked the times at the four AWIPS sites where the radars are and
> they are all correct. Why don't you try restarting ntp on the BDDS
> servers - perhaps the daemon is not even running.
>
> Jami Casamento wrote:
>
> </pre>
>
> <blockquote type="cite">
> <pre wrap="">TJ & Diane,
>
> Would it be possible to check the time servers at the following sites for
> accuracy:
>
> KICT
> KLCH
> KRGX
> KDAX
>
> We are noticing some incorrect times on our BDDS Servers that are configured
> to listen for the NTP broadcast.
>
> Thanks,
> -Jami
>
> "Jackson, Tom" wrote:
>
> </pre>
>
> <blockquote type="cite">
> <pre wrap="">We use the application server at each site as the NTP time
> source for that site. The site application server I believe is updated once
> daily, and the master AWIPS time source I believe is updated once weekly from
> either Boulder or the Naval Observatory.
>
> TJ
>
> -----Original Message-----
> From: Diane Deitz [<a href="mailto:address@hidden"
> class="moz-txt-link-freetext">mailto:address@hidden</a>]
> Sent: Monday, August 30, 2004 11:43 AM
> To: Phil Cragg
> Cc: Jami Casamento; Ted Ulinski; <a href="mailto:address@hidden"
> class="moz-txt-link-abbreviated">address@hidden</a>; Jackson, Tom
> Subject: Re: AWIPS NTP Issues
>
> As I understand it, at least on the ORPG end, it takes the time off the
> AWIPS application server via the ntp broadcast by adding the AWIPS subnet to
> their frame relay hub router configuration.
>
> TJ/John - can you 'boys' add anything?
>
> Phil Cragg wrote:
>
> </pre>
>
> <blockquote type="cite">
> <pre wrap="">Diane,
>
> An issue involving NTP has come up. We were told that you could steer us
> in the right direction.
>
> Currently we are working on the NEXRAD Level II, Archive Data Project.
> We have 4 BDDS servers at various WFO sites that are not being updated
> with the correct times using NTP. This is causing latency issues with
> the Level II data being sent via LDM from the WFO site BDDS servers to
> the Regional Headquarters. Any information you could provide us on
> how NTP is currently configured on the AWIPS LAN would be greatly
> appreciated. With your help, I am sure we will be able to resolve our
> problem.
>
> The sites in which the BDDS servers are currently being affected:
>
> KICT
> KLCH
> KRGX
> KDAX
>
> Thank you,
> Phil
> </pre>
> </blockquote>
> </blockquote>
> </blockquote>
>
> <pre wrap=""><!---->
> </pre>
> </blockquote>
>
> </body>
> </html>
>
> --------------3DB242A8EEAD7F25F689683E--
>
> --
> NOTE: All email exchanges with Unidata User Support are recorded in the
> Unidata inquiry tracking system and then made publicly available
> through the web. If you do not want to have your interactions made
> available in this way, you must let us know in each email you send to us.
>
> ------- End of Forwarded Message
>