Installing timesync on a linux server, 2 installing timesync on a linux server – HP NonStop G-Series User Manual

Page 22

Advertising
background image

HP NonStop Time Synchronization User’s Guide

Page 22 of 81

-> add process $ZZKRN.#TimeSync, &
cpu 1, &
name $TIME, &
program $SYSTEM.SYSTEM.TIMESYNC, &
hometerm $ZHOME, &
autorestart 5, &
startmode APPLICATION

4. If you plan to run the OSS version of TimeSync, copy the OSSPAX file from the product

subvolume to an OSS directory, adding a .pax extension, and use the pax utility to
extract the file contents. For example, from an OSS shell prompt, do the following
(assuming you used IPSetup to place the TimeSync files in $DSMSCM.ZTIMES):

[root tmp]# cp –p /G/dsmscm/ztimes/osspax /var/tmp/osspax.pax

[root tmp]# pax –rf /var/tmp/osspax.pax

The pax file contents will be extracted to the product installation directory
/usr/tandem/timesync. You can then configure and run TimeSync from that location.

5. Obtain and install a license key for the product by sending an email request to

[email protected]. In the request, include the system number, system type,
node name, number of processors, and OS version for each system on which TimeSync
will run. In return you will receive a license file for each system containing the license
key for that system. This file must be placed in $SYSTEM.SYSTEM, and must be named
TIMESLIC regardless of whether you are running the Guardian or OSS version of
TimeSync. Once a valid license key has been installed, TimeSync will be able to run on
that system.

6. Edit the TimeSync configuration file (TSCONF in Guardian or timesync.conf in OSS) and

create a custom configuration for the system as described in

Configuring TimeSync

.

7. If you will be running TimeSync with client mode enabled (i.e. TimeSync will be

updating the local system time), you should disable time synchronization in products
such as NSX and ASAP to avoid potential erratic changes to system time.

8. In order for the TimeCom CI to communicate with TimeSync, a loop-back route

(address 127.0.0.1) must be configured for the TCP/IP process that TimeSync will use
for communication.

3.2 Installing TimeSync on a Linux Server

TimeSync is packaged on a CD as an independent product. For Linux, two different
installation methods are available: RPM (RedHat Package Manager) and tar archive file.
The advantage of using the RPM-based installer is that RPM tracks and manages all
packages installed on your system, which makes it easy to check what has been installed,
upgrade to newer versions, and uninstall products. However, RPM also gives you less

Advertising
This manual is related to the following products: