| Title: | DEC TCP/IP Services for OpenVMS | 
| Notice: | Note 2-SSB Kits, 3-FT Kits, 4-Patch Info, 7-QAR System | 
| Moderator: | ucxaxp.ucx.lkg.dec.com::TIBBERT | 
| Created: | Thu Nov 17 1994 | 
| Last Modified: | Fri Jun 06 1997 | 
| Last Successful Update: | Fri Jun 06 1997 | 
| Number of topics: | 5568 | 
| Total number of notes: | 21492 | 
    Hi,
    
    	I most certainly need help with NTP. I have never set this up and
    the documentation is .....
    
    	My customer would like to setup the following:
    
    		Set node Batman as a local-master
    		Node Fred would be a backup time server
    		Robin and all other nodes are simple clients
    
    	The customer does not have access to a network time provider.
    
    	What should the configuration file look like on each of these
    nodes?
    
    	Also, assuming the above configuration, if Batman goes down then
    Fred takes over as the time server. What happens when Batman becomes
    available again? Will Batman first synchronize with Fred or will all
    node re-sync with Batman. If Batman does not first sync with Fred,
    there could be a forward or backward step in time which could affect
    certain processes in the plant.
    
    	Any help would be appreciated,
    
    Mike
                              
| T.R | Title | User | Personal Name | Date | Lines | 
|---|---|---|---|---|---|
| 5179.1 | Not sure if it's the correct way, but it works... | CSC32::H_SO | Reboot twice 'n call me in the mornin' | Wed Feb 26 1997 15:03 | 61 | 
|     Hope this helps...
    
    We setup NTP with the following:
    
    Primary server STITR has ip address of 16.66.80.220
    Seconary server SHELBY has ip address of 16.66.80.67
    Client ROCKIE has ip address of 16.66.80.13
    
    
    1) Primary server:
    Setup STITR in the local net with local-master stratum of 10
    by editing SYS$SPECIFIC:[UCX$NTP]UCX$NTP.CONF to include:
    
    ;following sets stratum number to corresponding value.
    local-master 10
    
    server 16.66.80.220
    peer 16.66.80.13
    peer 16.66.80.67
    
    
    2) Secondary server:
    Setup SHELBY in the local net with local-master stratum of 20
    by editing SYS$SPECIFIC:[UCX$NTP]UCX$NTP.CONF to include:
    
    ;following sets stratum number to corresponding value.
    local-master 20
    
    server 16.66.80.220
    peer 16.66.80.13
    peer 16.66.80.67
    
    
    3) Client:
    Setup ROCKIE in the local net with local-master stratum of 32
    by editing SYS$SPECIFIC:[UCX$NTP]UCX$NTP.CONF to include:
    
    ;following sets stratum number to corresponding value.
    local-master 32
    
    server 16.66.80.220
    peer 16.66.80.67
    peer 16.66.80.13
    
    
    
    So in this example, if the host ROCKIE loses the primary server STITR,
    it should aquire SHEBLY as the new sync source, as indicated by the
    following in SYS$SPECIFIC:[UCX$NTP]UCX$NTPD.LOG:
    
    * selected new sync source 16.66.80.67, now at stratum 21
     11:22:16.75    -0.008819 seconds, trip 0.1997, aperture 0.0188, hold 4
    
    And once ROCKIE re-aquires the primary server, it should use
    STITR as the new sync source, as indicated by the following in
    UCX$NTPD.LOG:
    
    * selected new sync source 16.66.80.220, now at stratum 11
     19:37:29.38    -0.122397 seconds, trip 0.2000, aperture 0.1224, hold 4
    
    
 | |||||