HP-UX Reference (11i v1 00/12) - 1M System Administration Commands N-Z (vol 4)

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

561

562

563

564

565

566

567

568

569

570

__________________________________________________________________________________________________________________________________________________________________________________________________

STANDARD Printed by: Nora Chuang [nchuang] STANDARD

/build/1111/BRICK/man1m/naaagt.1m

________________________________________________________________

___ ___

xntpd(1M) xntpd(1M)

prevented by specifying disabled. The default is enabled.

link/nolink

It is convenient to be able to access the current element of a ﬁle generation set by a ﬁxed name. This

feature is enabled by specifying link and disabled using nolink. The default is link.Iflink is

speciﬁed, a hard link from the current ﬁle set element to a ﬁle without sufﬁx is created. When there is

already a ﬁle with this name and the number of links of this ﬁle is one, it is renamed appending a dot,

the letter C, and the pid of the xntpd server process. When the number of links is greater than one,

the ﬁle is unlinked. This allows the current ﬁle to be accessed by a constant name.

REFERENCE CLOCK DRIVERS

Individual clocks can be activated by conﬁguration ﬁle commands, speciﬁcally the server and fudge

commands described in the xntpdc(1M) manual page. The following discussion presents information on how

to select and conﬁgure the device drivers in a running UNIX system.

Radio and modem clocks by convention have addresses in the form 127.127.t.u , where t is the clock

type and u is a unit number in the range 0-3 used to distinguish multiple instances of clocks of the same

type. Most of these clocks require support in the form of a serial port or special bus peripheral. The particu-

lar device is normally speciﬁed by adding a soft link

/dev/deviceu to the particular hardware device

involved, where

u correspond to the unit number above.

Following is a list showing the type and title of each driver currently implemented. The compile-time

identiﬁer for each is shown in parentheses.

The following four clock drivers are supported by HP.

Type 1 Local Clock Driver (LOCAL_CLOCK)

Type 4 Spectracom 8170 and Netclock/2 WWVB Receivers (WWVB)

Type 26 Hewlett Packard 58503A GPS Receiver (HPGPS)

Type 29 Trimble Palisade GPS Receiver (PALISADE)

The clock drivers mentioned below are not supported by HP. They may work, but have not been tested.

They are provided as is, for the convenience of the diverse users.

Type 2 Trak 8820 GPS Receiver (TRAK)

Type 3 PSTI/Traconex 1020 WWV/WWVH Receiver (PST)

Type 5 TrueTime GPS/GOES/OMEGA Receivers (TRUETIME)

Type 8 Generic Reference Driver (PARSE)

Type 10 Austron 2200A/2201AGPS Receivers (AS2201)

Type 11 * TrueTime OMEGA Receiver

Type 15 * TrueTime TM-TMD GPS Receiver

Type 16 Bancomm GPS/IRIG Receiver (HP only) (BANC)

Type 17 Datum Precision Time System (DATUM)

Type 18 NIST Modem Time Service (ACTS)

Type 20 Generic NMEA GPS Receiver (NMEA)

Type 23 PTB Modem Time Service (PTBACTS)

Type 24 USNO Modem Time Service (USNO)

Type25*TrueTimegeneric.

All TrueTime receivers are now supported by one driver, type 5. Types 11, 15 and 25 will be retained only

for a limited time and may be reassigned in future.

DEBUGGING HINTS FOR REFERENCE CLOCK DRIVERS

The ntpq and xntpdc utility programs can be used to debug reference clocks, either on the server itself

or from another machine elsewhere in the network. The server is compiled, installed and started using the

command-line switches described in the xntpdc(1M) manual page.

The ﬁrst thing to look for are error messages on the system log. If none occur, the daemon has started,

opened the devices speciﬁed and waiting for peers and radios to come up.

The next step is to be sure the RS232 messages, if used, are getting to and from the clock. The most reli-

able way to do this is with an RS232 tester and to look for data ﬂashes as the driver polls the clock and/or

as data arrive from the clock. Our experience is that many of the problems occurring during installation are

due to problems such as miswired connectors or improperly conﬁgured device links at this stage.

If RS232 messages are getting to and from the clock, variables can be inspected using the ntpq

command

(see ntpq(1M)). First, use the

pe and as commands to display billboards showing the peer conﬁguration

and association IDs for all peers, including the radio clock peers. The assigned clock address should appear

Section 1M−−1068 − 5 − HP-UX Release 11i: December 2000

___