Network Timing Protocol

NTP
Installation and Configuration on
DMN Vision
Cisco CSS
Sun Netra T1 AC-200
Brighton 2, MMV Relays and Client PCs
Client

By:
System Verification Test Laboratory
HNS-SVT
xxxxxxx-0001
Revision
January 17, 2002

11717 Exploration Lane, Germantown, MD 20876

Tel: (301) 428.5500 Fax: (301) 428.1868/2830

HNS Proprietary II
1

Copyright 2002 Hughes Network Systems, a Hughes Electronics Corporation company

All rights reserved. This publication and its contents are proprietary to Hughes Network Systems, a
Hughes Electronics Corporation company. No part of this publication may be reproduced in any form
or by any means without the written permission of Hughes Network Systems, 11717 Exploration
Lane, Germantown, Maryland 20876.
Hughes Network Systems has made every effort to ensure the correctness and completeness of the
material in this document. Hughes Network Systems shall not be liable for errors contained herein.
The information in this document is subject to change without notice. Hughes Network Systems
makes no warranty of any kind with regard to this material, including, but not limited to, the implied
warranties of merchantability and fitness for a particular purpose.

Trademarks
All trademarks, marks, names, or product names referenced in this publication are the property of
their respective owners, and Hughes Network Systems neither endorses nor otherwise sponsors
any such products or services referred to herein.

Contents
CONTENTS .................................................................................................................................................................3
TABLE OF FIGURES ................................................................................................................................................4
REVISION HISTORY ................................................................................................................................................5
ABOUT THIS DOCUMENT......................................................................................................................................6
CHAPTER 1.................................................................................................................................................................7
DMN VISION .............................................................................................................................................................7
NTP Protocol ........................................................................................................................................................7
CHAPTER 2...............................................................................................................................................................12
IPGW CONFIGURATION ...........................................................................................................................................12
CHAPTER 3...............................................................................................................................................................14
RELAY (BRIGHTON 2 OR MMV) CONFIGURATION ...................................................................................................14
CHAPTER 4...............................................................................................................................................................19
CAC SERVER CONFIGURATION................................................................................................................................19
CHAPTER 5...............................................................................................................................................................20
CISCO CONTENT SERVICES SWITCH 11051-AC .......................................................................................................20
Enabling NTP .....................................................................................................................................................20
Enabling logging.................................................................................................................................................20
Interfacing with the MGMT LAN ........................................................................................................................21
Showing the Log..................................................................................................................................................22
Configuring Date, Time and Timezone in CSS ...................................................................................................22
CHAPTER 6...............................................................................................................................................................24
SUN NETRA T1 AC-200 CONFIGURATION ................................................................................................................24
CHAPTER 7...............................................................................................................................................................29
NTPTIME .............................................................................................................................................................29
SAMPLE NETWORK CHART...............................................................................................................................35
NOTES .......................................................................................................................................................................36

Table of Figures
Figure 1 HP-UX man xntpd command ......................................................................................................... 7
Figure 2 IPGW Configuration..................................................................................................................... 12
Figure 3 Adding Multicast address to IPGW.............................................................................................. 13
Figure 4 Relay's IP Multicast Profile .......................................................................................................... 14
Figure 5 Adding Multicast Address to Relay.............................................................................................. 15
Figure 6 Sniffer Matrix at the Remote LAN........................................................................................... 18
Figure 7 NTP multicast address (224.0.1.1) configuration in CAC server................................................. 19
Figure 8 NTPTime URL ............................................................................................................................. 29
Figure 9 NTPTime icon in Control Panel ................................................................................................... 30
Figure 10 NTPTime Servers tab ................................................................................................................. 31
Figure 11 NTPTime Settings tab ................................................................................................................ 31
Figure 12 NTPTIme Log Files tab.............................................................................................................. 32
Figure 13 NTPTime Retry tab .................................................................................................................... 32
Figure 14 NTPTime Advanced tab ............................................................................................................. 33
Figure 15 NTPTime Sample Sniffer Capture.......................................................................................... 34
Figure 16 Sample Network Layout............................................................................................................. 35

Revision History
Date
January 17, 2002
January 18, 2002

Name
Juan Zavala
Juan Zavala

Joe Szekeres
Rohit Tripathi

February 8, 2002

Juan Zavala

Description
First release for comments
Add reference to TIMEZONE file for Netra
Add Copyright notice and logos
Add Revision History
Add Sniffer Matrix picture from Remote LAN
Proofreading, suggested changing some graphics
to a higher resolution
Suggested changing some graphics to a higher
resolution and to document NTP multicast address
in CAC server
Insert Chapters and more document formatting
Add About this document section
Add references on NTPTime
Incorporate feedback from John Border

About this document

Scope and Audience
This document provides configuration instructions to set up the Network Timing Protocol in
several devices in the DMR/MMV Network Operations Center (NOC):

HP-UX NMS computer running as the NTP server.

Cisco Content Services Switch (CSS).
Sun Solaris running Parent Traffic Server web caching software.
DRM2 and MMV relays
Client PCs at the remote sites.
Other NTP client devices with networking connectivity to the NMS at the NOC side.

Time synchronization is important because it assures that all devices running web cache
applications keep accurate measurements of web objects freshness. Without NTP running on
the network there is not guarantee that an object just cached can be detected as such by
another device with different time, consequently, there will unnecessary traffic generated in the
network going back and forth to retrieve web content from origin servers.
The intended audience for this document is Network Engineers from the Business and Software
Engineering Groups.

Organization
This document is organized in Chapters as follows:
-

Chapter 1- DMN Vision

Chapter 2 - IPGW Configuration)
Chapter 3 - Relay (Brighton 2 and MMV) Configuration
Chapter 4 - CAC Server Configuration
Chapter 5 - Cisco Content Services Switch 11051-AC
Chapter 6 - Sun Netra T1 AC-200 Configuration
Chapter 7 - NTPTime
Sample Network Chart

Chapter 1
DMN Vision
NTP Protocol
This section defines the steps required to configure the NMS platform to support XNTP, a
requirement for caching and other features of the VSATs. Note that this functionality is provided
by the HP-UX operating system and is not part of the NMS release. However, to aid in the
configuration of NTP, a template configuration file has been provided in the NMS release.
1. There are two versions of XNTPD available on HP-UX. To determine which is installed on
your machine, type: man xntpd
If, under SYNOPSIS, the first argument is "-ab", you have a version of XNTPD that does not
support the Time To Live (TTL) argument.
If the first argument is "-abdm", you have a version of XNTPD that does support the Time To
Live (TTL) argument.
Example: man xntpd

Figure 1 HP-UX man xntpd command

2. Log in as the system administrator (root).

3. Change directory to the dmnvision default directory.
type: cd /user/dmn/dmnvision/default
4. Copy the ntp.conf template to /etc
type: cp ntp.conf /etc/ntp.conf
5. Edit the /etc/ntp.conf file
a) locate the line with the following format:
broadcast 224.0.1.1 key 0 ttl 255 # [ key n ] [ version n ]
b) if your version of XNTPD does not support the TTL, then delete 'ttl 255' from the line above
in the file.
c) if the multicast address you plan to use for broadcasting the network time is not 224.0.1.1,
modify that portion of the line above to match your configuration.
d) make sure that the CAC and an IPGW are configured to send keys for and forward the
multicast address, respectively.
6) To configure XNTPD to start at system boot time, perform the following:
a) Change directory to /etc/rc.config.d
b) type: cp oracle xntpd
c) Edit xntpd and make the contents to match the following:
#!/sbin/sh
#
# xntpd environment variable settings
#
XNTPD=1
d) Reboot the system and verify that all processes start up correctly. (Starting Time
Synchronization must display OK during the HP booting process).

# Sample XNTP Configuration File

#
# Use "peer", "server" and "broadcast " statements to specify various time
# servers to be used and/or time services to be provided.
# Peer: The peer statement specifies that the given host is to be polled
#
in "symmetric active" mode. The syntax is :
#
peer addr [ key # ] [ version # ] [ minpoll interval_in_sec ] [ prefer ]
#
# peer 128.116.64.3 key 2001 version 2
#
# Server: The server statement causes polling to be done in client mode rather
#
than symmetric active. It is an alternative to the peer command
#
above. Which you use depends on what you want to achieve.
#
The syntax is:
#
server addr [ key # ] [ version # ] [ minpoll interval_in_sec ] [ prefer ]
#
# server 128.8.10.1 key 2000 minpoll 6
prefer
#
# Broadcast: The broadcast statement tells it to start broadcasting time
#
out one of its interfaces. Syntax is:
#
broadcast addr [ key # ] [ version # ] [ minpoll interval_in_sec ]
#
broadcast 224.0.1.1 key 0 version 3
#
# broadcastclient: It tells the daemon whether it should attempt to sync
#
to broadcasts or not. Defaults to `no'.
#
#broadcastclient yes # or no
#
# broadcastdelay: It configures in a default round-trip delay to use for
#
broadcast time (in seconds). The defaults is 0.008 second.
##
#broadcastdelay 0.008
#
# Precision: The default is -6. Unless there is a good reason to do so, this
#
value should not be changed from the default value.
#
# precision -6
#
# Drift file: Put this in a directory which the daemon can write to. No
#
symbolic links allowed, either.
#
driftfile /etc/ntp.drift
#
# authenticate: It configures us into strict authentication mode (or not).
#
The default is no.
#
#authenticate yes
# or no.
#
# authdelay: It is the time (in seconds) it takes to do an NTP encryption on this host.
#
#AUTHDELAY
9

#
# trustedkey: The keys defined here are used when authenticate is on.
#
We only trust (and sync to) peers who know and use these keys.
#
#trustedkey 1 3 4 8
##
# keys: It specifies the file which holds the authentication keys.
#
#keys /etc/ntp.keys
#
# controlkey: It indicates which key is to be used for validating
#
mode 6 write variables commands. If this isn't defined, no
#
mode 6 write variables commands can be done on the xntpd.
#
#controlkey 65534
#
# restrict: This option places restrictions on one or more systems.
#
This is implemented as a sorted address-and-mask list, with
#
each entry including a set of flags which define what a host
#
matching the entry *can't* do.
#
The syntax is :
#
restrict address [ mask numeric mask ] [ flag ]
#
#
The flags are:
#
#
ignore
- ignore all traffic from host
#
noserve - don't give host any time (but let him make queries?)
#
notrust - give the host time, and let it make queries, but don't
#
sync to it.
#
noquery - host can have time, but can not make queries
#
nomodify - allow the host to make queries except those which are
#
actually run-time configuration commands.
#
ntpport - Makes matches for this entry only if the source
#
port is 123.
#
#The matching machines can be served time, but they will be restricted to
#make non-modifying queries
#
#restrict 129.140.0.0 mask 255.255.0.0 notrust nomodify
#
#Ignore all packets from host 15.1.15.1
#
# restrict 15.1.15.1 ignore
#
# Restric 35.1.1.0 to query only
#
#restrict 35.1.1.0 mask 255.255.255.0 noserve nomodify
#
# take time from the 128.116.64.3, but don't let it query
#
#restrict 128.116.64.3 noquery
#
# statdir : Indicates the full path of the directory where statistics files
10

#
should be created:
#
statsdir /var/tmp/ntp
#
# statistics : Enables writing of statistics records: loopstats/peerstats.
#
#statistics loopstats
#statistics peerstats
#
# filegen : Configures the ways to generate the statistic file set. It
#
provides a mean for handling files that are continously growing
#
during the lifetime of a server.
#
#
The syntax is :
#
filegen statsname [ file filename ] [ type typename ]
#
[ link/nolink ] [ enable/disable ]
#
filegen loopstats file loopstat type week link
filegen peerstats file loopstat type week link
#
# Local clock : Allows the server to synchronize to its own clock.
#
server 127.127.1.0 minpoll 6 prefer
#fudge 127.127.1.0 time1 1
#
# Spectracom Netclock/2 clocks : synchronize to netclock/2 which receives WWVB.
#
# server 127.127.4.1
# End of File

Sample ntp.drift file.

# cd /etc
# ls -l ntp.drift
-rw-r--r-- 1 root
# more ntp.drift
13.00000

root

9 Jan 17 13:02 ntp.drift

Verifying xntp is running.

# ps -ef |grep ntp
root 1039 1 0 15:02:30 ?
#

0:13 /usr/sbin/xntpd

Change the permissions mode on the /var/tmp/ntp subdirectory

# cd /var/tmp
# chmod 777 ntp
# ls l ntp*
# drwxrwxrwx 2 bin

bin

24 May 26 1999 ntp

11

Chapter 2
IPGW Configuration

Figure 2 IPGW Configuration

12

Figure 3 Adding Multicast address to IPGW

13

Chapter 3
Relay (Brighton 2 or MMV) Configuration

Figure 4 Relay's IP Multicast Profile

14

Figure 5 Adding Multicast Address to Relay

VxWorks Console Configuration and Troubleshooting Commands

- To setup the time and date go to the shell and execute:
-> lkup "ntp"
sntpt_enable_multicast
0x0015f998 text
sntpt_system_time_store
0x00160028 text
sntpt_system_shutdown
0x0015f918 text
sntp_localtime_r
0x0015ff08 text
sntp_get_local_time
0x0015fea8 text
sntpt_task_init_done
0x0015f888 text
sntpt_task_init
0x0015f7f8 text
sntp_set_config
0x0015fe88 text
sntpt_show
0x0015fcc8 text
sntpt_set_date
0x00160228 text
sntp_get_config
0x0015fe68 text
sntpt_system_init
0x0015f798 text
cfm_set_sntp_config
0x001285f8 text
sntpt_system_time_restore 0x00160088 text
cfm_get_sntp_config
0x001285c8 text
nntp_accept_file_descriptor 0x0189b208 data
sntpt_set_time
0x00160138 text
sntp_gmtime_r
0x0015ff48 text
value = 0 = 0x0

(SB)

-> date
GM Time:
THU JAN 17 22:20:04 2002
Local Time: THU JAN 17 17:20:04 2002
value = 0 = 0x0
-> sntpt_set_date 01,17,2002
------------------------------------------------------set_clock
------------------------------------------------------tv_sec
: 1011306035
15

tv_nsec
: 0
------------------------------------------------------GM Time:
THU JAN 17 22:20:35 2002
Local Time: THU JAN 17 17:20:35 2002
value = 0 = 0x0
-> sntpt_set_time 22,25,00
<-Must be GMT
------------------------------------------------------set_clock
------------------------------------------------------tv_sec
: 1011306300
tv_nsec
: 0
------------------------------------------------------GM Time:
THU JAN 17 22:25:00 2002
Local Time: THU JAN 17 17:25:00 2002
value = 0 = 0x0
->
-> sntpt_show
--------------------------------------------------------------SNTP Task:
--------------------------------------------------------------Startup:
System Init
Completed : YES
Task Init
Completed : YES
Task Init Done
Completed : YES
System Shutdown
Completed : NO
Handlers:
Mcast Queue Handler Calls
: 698
New Parms Handler Calls
: 0
Configuration:
Multicast Address for SNTP
: 224.0.1.1
Timezone Index
: 11
DST Calc. Enable
: 0
Statistics:
Successful Clock Update Count : 698
Failed Clock Update Count
: 0
--------------------------------------------------------------value = 0 = 0x0
->
-> aam_show
aam info
--------------------------------------------------------state
dpcmac
ethmac
key
------------------ -------- ------------ ---------------ADDR_RESERVED (4) 03000000 030000000000 0000000000000000
ADDR_RESERVED (4) 8A482501 8A4825010000 0000000000000000
ADDR_UNICAST
(8) 88482502 884825020000 D5EDA78A4F9DA8D9
ADDR_CLOSED
(5) 00000000 01005E020203 0000000000000000
ADDR_ACTIVE
(2) 0D14FF00 01005E000104 55CF8400703F4179
ADDR_ACTIVE
(2) 1914FF00 01005E000101 55CF8400703F4179
ADDR_ACTIVE
(2) 0918FF00 01005E010301 783020F42AF02D8C
ADDR_ACTIVE
(2) 1914FF00 01005E000106 55CF8400703F4179
ADDR_CLOSED
(5) 00000000 01005E020202 0000000000000000
16

slh info
-----------------------------dpcmac
total
out of seq
-------- ---------- ---------03000000
4131
0
8A482501
903
0
88482502
12731
428
0D14FF00
0
0
1914FF00
20382
707
0918FF00
74
0
value = 0 = 0x0
-> aam_show
aam info
--------------------------------------------------------state
dpcmac
ethmac
key
------------------ -------- ------------ ---------------ADDR_RESERVED (4) 03000000 030000000000 0000000000000000
ADDR_RESERVED (4) 8A482501 8A4825010000 0000000000000000
ADDR_UNICAST
(8) 88482502 884825020000 D5EDA78A4F9DA8D9
ADDR_CLOSED
(5) 00000000 01005E020203 0000000000000000
ADDR_ACTIVE
(2) 0D14FF00 01005E000104 55CF8400703F4179
ADDR_ACTIVE
(2) 1914FF00 01005E000101 55CF8400703F4179
ADDR_ACTIVE
(2) 0918FF00 01005E010301 783020F42AF02D8C
ADDR_ACTIVE
(2) 1914FF00 01005E000106 55CF8400703F4179
ADDR_CLOSED
(5) 00000000 01005E020202 0000000000000000
slh info
-----------------------------dpcmac
total
out of seq
-------- ---------- ---------03000000
4133
0
8A482501
903
0
88482502
12742
428
0D14FF00
0
0
1914FF00
20393
707
0918FF00
74
0
value = 0 = 0x0
->
-> aam_debug=1
aam_debug = 0x3dcc80: value = 1 = 0x1
CAC Msg type: P
IP Dest = 10.2.9.36
IP Dest = 224.0.1.6
IP Dest = 10.2.9.36
IP Dest = 224.0.1.6
IP Dest = 10.2.9.36
IP Dest = 224.0.1.6
IP Dest = 10.2.9.36
IP Dest = 224.0.1.6
IP Dest = 224.0.1.1
IP Dest = 224.0.1.1
IP Dest = 224.0.1.6
17

IP Dest = 10.2.9.36
CAC Msg type: P
IP Dest = 10.2.9.36
IP Dest = 224.0.1.6
IP Dest = 10.2.9.36
IP Dest = 224.0.1.6
IP Dest = 10.2.9.36
IP Dest = 224.0.1.6
IP Dest = 10.2.9.36
IP Dest = 224.0.1.6
IP Dest = 10.2.9.36
CAC Msg type: E
IP Dest = 224.0.1.6
IP Dest = 10.2.9.36
CAC Msg type: P
aam_debug=0
->

Figure 6 Sniffer Matrix at the Remote LAN

18

Chapter 4
CAC Server Configuration

Figure 7 NTP multicast address (224.0.1.1) configuration in CAC server

Enter the NTP MAC address 01005e000101 into the same element id that holds the SDL MAC address

19

Chapter 5
Cisco Content Services Switch 11051-AC
In this chapter IP addresses are shown as a sample only, you must verify your IP scheme and
enter the correct IP addresses for your configuration.

Enabling NTP
Add the following lines to the CSS configuration:
CSS11050# config t
CSS11050(config)# sntp server 192.168.11.190 version 3
CSS11050(config)# sntp poll-interval 30
CSS11050(config)# exit
CSS11050# wr mem
CSS11050# sho run
!*************************** GLOBAL ***************************
sntp server 192.168.11.190 version 3
sntp poll-interval 30
..
..
..

Enabling logging
Add the following lines to the CSS configuration:
CSS11050# config t
CSS11050(config)# logging buffer 64000
CSS11050(config)# logging commands enable
CSS11050(config)# logging subsystem all level debug-7
CSS11050(config)# exit
CSS11050# wr mem
CSS11050# sho run
logging buffer 64000
logging commands enable
logging subsystem syssoft level debug-7
logging subsystem buffer level debug-7
logging subsystem flowmgr level debug-7
logging subsystem radius level debug-7
logging subsystem wcc level debug-7
logging subsystem ipv4 level debug-7
20

logging subsystem chassis level debug-7

logging subsystem vlanmgr level debug-7
logging subsystem netman level debug-7
logging subsystem app level debug-7
logging subsystem rip level debug-7
logging subsystem ospf level debug-7
logging subsystem sntp level debug-7
logging subsystem vrrp level debug-7
logging subsystem redundancy level debug-7
logging subsystem csdpeer level debug-7
logging subsystem portmapper level debug-7
logging subsystem circuit level debug-7
logging subsystem security level debug-7
logging subsystem fac level debug-7
logging subsystem vpm level debug-7
logging subsystem publish level debug-7
logging subsystem acl level debug-7
logging subsystem keepalive level debug-7
logging subsystem urql level debug-7
logging subsystem nql level debug-7
logging subsystem dql level debug-7
logging subsystem pcm level debug-7
logging subsystem proximity level debug-7
logging subsystem hfg level debug-7
logging subsystem replicate level debug-7
logging subsystem boomerang level debug-7

Interfacing with the MGMT LAN

As shown in the sample network diagram at the end of this document, to access the Time
Server (NMS) it is required to defined a port in the CSS that will get connected to the minihub
where the NMS is attached to.
A straight through cable is needed if the cable goes from the CSS to the upload port on the
minihub; otherwise; a cross-over cable is required if the cable goes from the CSS to any port on
the minihub.
As a sample, the following lines show a VLAN4 configured in the CSS to connect to the minihub
where the NMS is attached to:
!************************* INTERFACE *************************
interface e2
phy 100Mbits-FD
description "To B2 Linksys Hub - Port 15" <-In this sample this is the minihub hosting the MGMT LAN
bridge vlan 4
!************************** CIRCUIT **************************
circuit VLAN4
ip address 192.168.11.172 255.255.255.0

21

The CSS will received the multicast stream from the NMS on IP address 224.0.1.1 and forward
it to other VLANs (VLAN2 in the sample network layout). From here the CSS and Sun Netras
can synchronized its clocks and the IPGateway will forward this multicast traffic to the remote
relays.

Showing the Log

CSS11050# sho log
Displaying Log events.
Press any key to abort...
JAN 17 14:16:01 5/1 32923 NETMAN-6: CLMcmd: sho log,svtcss@139.85.161.143
JAN 17 14:16:06 5/1 32924 SNTP-7: Sending SNTP packet to 192.168.11.190 , port 123
JAN 17 14:16:07 5/1 32925 SNTP-7: Received SNTP packet from 192.168.11.190
JAN 17 14:16:07 5/1 32926 SNTP-6: Setting time to <01/17/2002 14:16:07>

Configuring Date, Time and Timezone in CSS

From Cisco documentation:
Mode Command and Syntax Description
General Commands: SuperUser, User, and all modes
clock timezone name hour hours {before-UTC|after-UTC} {minute minutes {beforeUTC|after-UTC}
The timezone keyword sets the timezone to offset the Universal Time Coordinated (UTC) time
from an SNTP server. This command is available in SuperUser mode.
The name variable is the name of the timezone. Enter a name with a maximum of 32
characters and no spaces.
The hour hours keyword and option set the hours offset for the timezone. For the hours
value, enter a number from 0 to 12. If the before-UTC or after-UTC option is omitted,
the offset is set to a positive number.
The before-UTC option sets the offset as a negative number. For example, if the hour
offset is 12, the before-UTC option sets it to -12.
The after-UTC option sets the offset as a positive number. This is the default offset.
The minute minutes option and variable set the minutes offset for the timezone. For
minute value, enter a number from 0 to 59. If the before-UTC or after-UTC option is
omitted, the offset is set to a positive number.
To reset the timezone information to 00:00:0, enter:
no clock timezone

End of Cisco documentation

Sample:
22

CSS11050# clock ?
date
Modify the system clock date
time
Modify the system clock time
timezone
Modify the timeZone information
CSS11050# clock date
Enter date [01-01-2000]:01-17-2002
CSS11050# clock time
Enter time [14:17:54]:14:17:56
CSS11050# clock timezone ?
<Text>
Enter timezone name (Len: 1-31)
CSS11050# clock timezone EST ?
hour
Configure hours from UTC
CSS11050# clock timezone EST hour 5 before-UTC
CSS11050# sho clock
Date: 01-17-2002
Time: 14:37:08
TimeZone: EST: -05:+00:+00
CSS11050#
(Installed software as of on CSS is ap0501005)

23

Chapter 6
Sun Netra T1 AC-200 Configuration
In this chapter IP addresses are shown as a sample only, you must verify your IP scheme and
enter the correct IP addresses for your configuration.
During the Sun Netra factory setup, the correspondent Locale is selected as shown below:
Netra 200
LOM event: +21h33m42s host power on
Netra T1 200 (UltraSPARC-IIe 500MHz), No Keyboard
OpenBoot 4.0, 1024 MB memory installed, Serial #16675624.
Ethernet address 8:0:20:fe:73:28, Host ID: 80fe7328.
Initializing Memory Boot device: disk File and args:
SunOS Release 5.8 Version Generic_108528-06 64-bit
Copyright 1983-2000 Sun Microsystems, Inc. All rights reserved.
Hostname: unknown
Configuring /dev and /devices
6/26/2001 17:45:30 GMT LOM time reference
Configuring the /dev directory (compatibility devices)
ufs fsck: sanity check: /dev/rdsk/c1t0d0s3 okay
S99testslice: Removing partition c1t0d0s3...
The system is coming up. Please wait.
Select a Language
0. English
1. French
2. German
3. Italian
4. Spanish
5. Swedish
Please make a choice (0 - 5), or press h or ? for help: 0
Select a Locale
0. English (C - 7-bit ASCII)
1. Albania (ISO8859-2)
2. Australia (ISO8859-1)
3. Belgium-Flemish (ISO8859-1)
4. Belgium-Flemish (ISO8859-15 - Euro)
5. Bosnia (ISO8859-2)
6. Brazil (ISO8859-1)
7. Bulgaria (ISO8859-5)
8. Canada-English (ISO8859-1)
9. Catalan, Spain (ISO8859-1)
24

10. Catalan, Spain (ISO8859-15 - Euro)

11. Croatia (ISO8859-2)
12. Czech Republic (ISO8859-2)
13. Denmark (ISO8859-1)
14. Denmark (ISO8859-15 - Euro)
15. Egypt (ISO8859-8)
16. Estonia (ISO8859-15)
17. Finland (ISO8859-1)
18. Finland (ISO8859-15 - Euro)
Press Return to show more choices.
Please make a choice (0 - 51), or press h or ? for help:

Select a Locale
19. Great Britain (ISO8859-1)
20. Great Britain (ISO8859-15 - Euro)
21. Greece (ISO8859-7)
22. Hungary (ISO8859-2)
23. Iceland (ISO8859-1)
24. Ireland (ISO8859-1)
25. Ireland (ISO8859-15 - Euro)
26. Israel (ISO8859-6)
27. Latvia (ISO8859-13)
28. Lithuania (ISO8859-13)
29. Macedonia (ISO8859-5)
30. Netherlands (ISO8859-1)
31. Netherlands (ISO8859-15 - Euro)
32. New Zealand (ISO8859-1)
33. Norway (ISO8859-1 - Bokmal)
34. Norway (ISO8859-1 - Nynorsk)
35. Poland (ISO8859-2)
36. Poland (UTF-8)
37. Portugal (ISO8859-1)
Press Return to show more choices.
Please make a choice (0 - 51), or press h or ? for help:

Select a Locale
38. Portugal (ISO8859-15 - Euro)
39. Romania (ISO8859-2)
40. Russia (ANSI 1251)
41. Russia (ISO8859-5)
42. Russia (KOI8-R)
43. Russia (UTF-8)
44. Serbia (ISO8859-5)
45. Slovakia (ISO8859-2)
46. Slovenia (ISO8859-2)
47. Thai
48. Turkey (ISO8859-9)
25

49. U.S.A. (en_US.ISO8859-1)

50. U.S.A. (en_US.ISO8859-15)
51. Go Back to Previous Screen
Press Return to show more choices.
Please make a choice (0 - 51), or press h or ? for help: 49

That selection updates the TIMEZONE file located at:

/etc/TIMEZONE
where TIMEZONE is a symbolic link pointing to:
/etc/default/init
# more init
# @(#)init.dfl 1.5 99/05/26
#
# This file is /etc/default/init. /etc/TIMEZONE is a symlink to this file.
# This file looks like a shell script, but it is not. To maintain
# compatibility with old versions of /etc/TIMEZONE, some shell constructs
# (i.e., export commands) are allowed in this file, but are ignored.
#
# Lines of this file should be of the form VAR=value, where VAR is one of
# TZ, LANG, CMASK, or any of the LC_* environment variables.
#
TZ=US/Eastern
CMASK=022
LC_COLLATE=en_US.ISO8859-1
LC_CTYPE=en_US.ISO8859-1
LC_MESSAGES=C
LC_MONETARY=en_US.ISO8859-1
LC_NUMERIC=en_US.ISO8859-1
LC_TIME=en_US.ISO8859-1
The file above configures the TIMEZONE for US English and Unites States Eastern Time
Test your Suns current time and timezone:
# date
Fri Jan 18 10:15:59 EST 2002

<-note the EST string in the output of the date command

Now that your Sun has the correct Timezone, configure NTP in it to listen for your NMS NTP Server.
# cd /etc/inet
# cp ntp.client ntp.conf
# vi ntp.conf
#@(#)ntp.client
1.2
#
#/etc/inet/ntp.client
#

96/11/06 SMI

26

# An example file that could be copied over to /etc/inet/ntp.conf; it

# provides a configuration for a host that passively waits for a server
# to provide NTP packets on the ntp multicast net.
#
#multicastclient 224.0.1.1
<-Comment this line out
server 192.168.11.190
<- add this line then save. 192.168.11.190 is the NMS ip address
#
Note:
- if the only clock reference reaching the Sun machine comes from the NMS then you can keep
the line multicastclient 224.0.1.1 and do not use the server 192.168.11.190 line.
- if more than one clock source can reach the Sun machine on either of its Ethernet ports then
you must point to the server 192.168.11.190 as shown in the sample above.

Then run:
# /etc/init.d/xntpd start

(to start the deamon, stop to stop it)

Verify the deamon is running:

# ps -ef |grep ntp
root 708 1 0 Jan 16 ?

0:01 /usr/lib/inet/xntpd

Confirm NTP works:

-

Set the date and time close to the NMSs one:

# date 0117145802
Thu Jan 17 14:58:00 EST 2002
192.168.11.190 -> 224.0.1.1

NTP broadcast (Thu Jan 17 15:58:30 2002)

Run snoop
# snoop v d eri1 |grep NTP
NTP:
NTP:
NTP:
NTP:
NTP:
NTP:
NTP:
NTP:
NTP:

----- Network Time Protocol ----Leap = 0x3 (alarm condition (clock unsynchronized))
Version = 3
Mode = 3 (client)
Stratum = 0 (unspecified)
Poll = 6
Precision = 239 seconds
Synchronizing distance = 0x0000.0000 (0.000000)
27

NTP:
NTP:
NTP:
NTP:
NTP:
NTP:
UDP:

Synchronizing dispersion = 0x0001.0061 (1.001480)

Reference clock =
Reference time = 0x00000000.00000000 (Thu Feb 7 01:28:16 2036)
Originate time = 0xbff1be23.a4a1b000 (Thu Jan 17 16:18:27 2002)
Receive time = 0xbff1be23.a55a2000 (Thu Jan 17 16:18:27 2002)
Transmit time = 0xbff1be63.a50d2000 (Thu Jan 17 16:19:31 2002)
Destination port = 123 (NTP)

NTP:
NTP:
NTP:
NTP:
NTP:
NTP:
NTP:
NTP:
NTP:
NTP:
NTP:
NTP:
NTP:
NTP:
UDP:

----- Network Time Protocol ----Leap = 0x0 (OK)

Version = 3
Mode = 3 (client)
Stratum = 2 (secondary reference)
Poll = 6
Precision = 239 seconds
Synchronizing distance = 0x0000.0048 (0.001099)
Synchronizing dispersion = 0x0001.4b87 (1.295029)
Reference clock = 192.168.11.190 (192.168.11.190)
Reference time = 0xbff1bf23.a5d54000 (Thu Jan 17 16:22:43 2002)
Originate time = 0xbff1bf23.a60b5000 (Thu Jan 17 16:22:43 2002)
Receive time = 0xbff1bf23.a5d54000 (Thu Jan 17 16:22:43 2002)
Transmit time = 0xbff1bf63.a3539000 (Thu Jan 17 16:23:47 2002)
Destination port = 123 (NTP)

28

Chapter 7
NTPTime
To synchronize client PCs there are many free utilities on the Internet. As a sample, this chapter
presents NTPTime, a freeware that can be downloaded from
http://home.att.net/~Tom.Horsley/ntptime.html
Note: HNS does not support this utility, it is presented in this chapter as an illustration only on
how to synchronize client PCs with a Time Server

Figure 8 NTPTime URL

The URL presents detailed installation instructions on this utility.
Once installed for example in a PC running Windows 98, NTPTime creates an icon in Control
Panel as shown below.

29

Figure 9 NTPTime icon in Control Panel

By double clicking on its icon, NTPTime displays its configuration dialog boxes show as an
illustration in the following pictures.

30

Figure 10 NTPTime Servers tab

Figure 11 NTPTime Settings tab

31

Figure 12 NTPTIme Log Files tab

Figure 13 NTPTime Retry tab

32

Figure 14 NTPTime Advanced tab

NTPTime Sample Log File

As a result of configuring it, NTPTime logs its events in a plain text file as shown below:
2002/02/11 15:05:23
2002/02/11 15:05:23
2002/02/11 15:05:23
192.168.11.190
2002/02/11 15:05:26
2002/02/11 15:05:26
2002/02/11 15:06:04
2002/02/11 15:06:12
2002/02/11 15:06:12
2002/02/11 15:06:12
192.168.11.190
2002/02/11 15:06:13
2002/02/11 15:06:13

UTC [-567353/-131275889]: Starting up NTP service version 4.1

UTC [-567353/-131275889]:
Primary server: 192.168.11.190
UTC [-567353/-131275889]: Requesting time from server:
UTC
UTC
UTC
UTC
UTC
UTC

[-567353/-131275889]:
[-567353/-131275889]:
[-567353/-131443057]:
[-567353/-131443057]:
[-567353/-131443057]:
[-567353/-131443057]:

clock adjustment: 2.519 seconds

round trip delay: -0.000 seconds
NTP shutdown request
Starting up NTP service version 4.1
Primary server: 192.168.11.190
Requesting time from server:

UTC [-567353/-131443057]: clock adjustment: 0.189 seconds

UTC [-567353/-131443057]:
round trip delay: 0.050 seconds

The following picture shows a Sniffer capture showing the NTP traffic between a client PC
and a NTP server.

33

Figure 15 NTPTime Sample Sniffer Capture

HNS Proprietary II
34

Sample Network Chart

Figure 16 Sample Network Layout

35

Notes

HNS Proprietary II
36