Rob,
In my case, the site I am currently using, 198.60.73.8 ntp-nist.ldsbc.net may not be the best available, since they are currently down.
I need to change and pick a site that has better up time.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Monday, August 15, 2016 9:46 AM
To: Midrange Systems Technical Discussion
Subject: RE: TCP9110 30 DIAGNOSTIC The maximum threshold for SNTP Client errors has been reached.
Well, I thought they were Windows servers but
Remote system . . . . . . . . . '10.10.1.1'
+ for more values '10.17.1.1'
These .1.1 servers (at least in our setup) seem to indicate Cisco routers.
So, you could have NTP setup on your routers and use those as both a client and a server. The router could be an NTP client to NIST and be an NTP server for the rest of your organization.
I think it's discourgaged to have every device you own going straight to NIST. Why overload it? If you can't communicate to your router you sure ain't going to be able to go to NIST anyway.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 08/15/2016 09:21 AM
Subject: RE: TCP9110 30 DIAGNOSTIC The maximum threshold for SNTP
Client errors has been reached.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Rob,
What is your SNTP Attributes set to for remote server.
Change SNTP Attributes (CHGNTPA)
Type choices, press Enter.
Remote system . . . . . . . . . '198.60.73.8'
+ for more values
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob
Berendt
Sent: Monday, August 15, 2016 8:43 AM
To: Midrange Systems Technical Discussion
Subject: Re: TCP9110 30 DIAGNOSTIC The maximum threshold for SNTP Client
errors has been reached.
In our domain we have various Windows servers which also run NTP back to
NIST. We point our IBM i lpars to these servers. You can have a number
of these servers listed there.
How, if those Windows servers are having issues connecting to NIST (or
wherever) I'm not aware of it but, the time on my IBM i, and my Windows
client, seem to be in sync with
http://www.timeanddate.com
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 08/15/2016 08:36 AM
Subject: TCP9110 30 DIAGNOSTIC The maximum threshold for SNTP
Client errors has been reached.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
TCP9110 30 DIAGNOSTIC The maximum threshold for SNTP Client errors has
been reached.
Connecting to host 198.60.73.8 using port 123.
I've had about 30 of these starting 08/10/16 22:08:01, repeating about
every 3 to 4 hours.
When I check the NIST Internet Time Servers site
http://tf.nist.gov/tf-cgi/servers.cgi
I do see that 198.60.73.8 is "not available" at times.
Is there a better recommended site to use Change SNTP Attributes
(CHGNTPA)?
Remote system . . . . . . . . . '198.60.73.8'
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx<mailto:psteinmetz@xxxxxxxxxx>
http://www.pencor.com/
midrange.com
