Highlighted
Absent Member.
Absent Member.

Re: Timesync and/or XNTPD time one hour behind console!

We have about 65 servers of which 5 are SLES10SP2, the remainder being NW65SP8. They are structured according to physical location and for 2 layers of redundancy.

At our main site we have 4 of the SLES boxes. The other SLES box is at another hub site connected via high speed link and services a certain client who has about 23 NW65SP8 servers spoking from that hub.

Two of the main site's SLES boxes act as the references of the NTP setup - they sync with 3 Internet sources (Unis) and peer with each other. They seem to function correctly and haven't had any issues so far. We had these in for a few weeks prior to migrating to xntpd and switching to these as references. Other devices on our network sync with these just fine.

The other 3 SLES boxes act as primaries and sync with the first two SLES boxes and peer with each other. Again, they seem to function correctly and haven't shown any issues so far.

Of the 3 primaries, one is used by secondary clients at our main site, one is used by secondary clients at various remote sites, the other is used by the large client with 23 secondary NW65SP8 boxes. All clients have "prefer" for the preferred server but also have an entry for the other two primaries for redundancy.

I have tried reducing a consumer's server list to just one but still have the one hour behind issue.

The SLES boxes do not show the issue and seem to be solid.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Timesync and/or XNTPD time one hour behind console!

alexstuart wrote:

>
> We have about 65 servers of which 5 are SLES10SP2, the remainder being
> NW65SP8. They are structured according to physical location and for 2
> layers of redundancy.
>
> At our main site we have 4 of the SLES boxes. The other SLES box is at
> another hub site connected via high speed link and services a certain
> client who has about 23 NW65SP8 servers spoking from that hub.
>
> Two of the main site's SLES boxes act as the references of the NTP
> setup - they sync with 3 Internet sources (Unis) and peer with each
> other. They seem to function correctly and haven't had any issues so
> far. We had these in for a few weeks prior to migrating to xntpd and
> switching to these as references. Other devices on our network sync
> with these just fine.
>
> The other 3 SLES boxes act as primaries and sync with the first two
> SLES boxes and peer with each other. Again, they seem to function
> correctly and haven't shown any issues so far.
>
> Of the 3 primaries, one is used by secondary clients at our main site,
> one is used by secondary clients at various remote sites, the other is
> used by the large client with 23 secondary NW65SP8 boxes. All clients
> have "prefer" for the preferred server but also have an entry for the
> other two primaries for redundancy.
>
> I have tried reducing a consumer's server list to just one but still
> have the one hour behind issue.
>
> The SLES boxes do not show the issue and seem to be solid.




--

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Timesync and/or XNTPD time one hour behind console!

Are the PC/Servers that lose the hour in the same location or spread
around your network?

If they are in one or two location then you need to just look at that
segment. I'd try reducing the trouble shooting by linmiting the setup
to no-redunency for now. So all server in the one location will look
to one server in that location for time. Then, that server would look
outbound for time. Then monitor for the hour drop.




--

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Timesync and/or XNTPD time one hour behind console!

It doesn't seem to matter which segment they're on.

The plot has since thickened - DST has just ended over here and two servers have since been rebooted (abended) WITHOUT the issue.

I have also double checked the DST settings in Monitor --> Server parameters --> Time and they look correct, as do the entries in autoexec.ncf
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.