Tuesday, July 04, 2006

Time Synchronization across enterprize with Windows 2003 SNTP

Configure windows as master time source.

The Windows 2003 time service is configured with w32tm, a command line tool included with the standard Windows installation.
The following three steps set up and activate time synchronization with an Internet time source:
1. w32tm /config /syncfromflags:manual /manualpeerlist:Peerlist
PeerList is a comma-separated list of DNS names or IP addresses of the desired Internet time sources.
2. w32tm /config /reliable:YES
This command configures the Windows time service to announce itself as a reliable time source so other computers can synchronize to it.
3. w32tm /config /update
This command notifies the time service of the changes to the configuration, causing the changes to take effect.

Below are the commands run for this configuration to set up time synchronization to an Internet time source:
1. w32tm /config /syncfromflags:manual /manualpeerlist:time.nist.gov,swisstime.ethz.ch
2. w32tm /config /reliable:YES
3. w32tm /config /update


NTP Configuration on Solaris 9

To configure time services on Solaris, perform the following three steps:
1. Copy the template file provided to ntp.conf:
cp /etc/inet/ntp.client ./ntp.conf

2. Modify ntp.conf to include the time server that will be used by this client.
Minimal required entries in ntp.conf include the time servers that the client should synchronize with and the location of the drift file, which is used to record information regarding the accuracy of the local clock.
eg of /etc/inet/ntp.conf

server patryk.keekar.com
server marc.keekar.com
driftfile /etc/ntp.drift

3. The ntpd daemon must be restarted in order for configuration changes to take effect.
/etc/init.d/xntpd stop
/etc/init.d/xntpd start

NTP Configuration on Linux

To configure time services on the Linux clients, perform the following two steps:
1. Modify ntp.conf to include the time servers that will be used by this client.
Minimal required entries in ntp.conf include the time servers that the client should synchronize with.
/etc/ntp.conf
# Permit all access over the loopback interface. This could
# be tightened as well, but to do so would effect some of
# the administrative functions.
restrict 127.0.0.1
server patryk.keekar.com
server marc.keekar.com

2. For the configuration changes to take effect, restart the ntpd daemon:
/etc/init.d/ntpd restart

Cisco CallManager server

Complete these steps in order to configure the Cisco CallManager server to automatically synchronize, and stay synchronized, with a Time server.

Note: You cannot use NTP to synchronize between two Cisco CallManagers. The NTP that is installed in Cisco CallManager is a client NTP service and only synchronizes to an NTP server.

1 file(s) copied.(NTP Operations Guide) in the C:\WINNT\..\xntp directory...
  1. Complete these steps in order to verify that the NetworkTimeProtocol service is configured to launch automatically upon start-up:
    1. Right-click on My Computer and select Manage.

    2. Expand the Services and Applications section.

    3. Select Services.

    4. Double-click on the Network Time Protocol service.

    5. Ensure that Start-up Type is set to Automatic.

  2. Configure the C:\WINNT\system32\drivers\etc\ntp.conf file.

    This file contains the list of Time Servers that Cisco CallManager becomes synchronized with. You can configure Cisco CallManager to point to specific Time Servers, or you can configure it to receive NTP broadcasts on the local LAN segment from the router (as long as the router is configured to do so).

    • Sample ntp.conf file that uses static Time Servers:

      • server patryk.keekar.com

      • server marc.keekar.com

      • driftfile %windir%\ntp.drift

    • Sample ntp.conf file that uses an NTP broadcast router:

      • broadcastclient

      • driftfile %windir%\ntp.drift

  3. Go to the Services Control Panel and stop/start the NetworkTimeProtocol service. Allow several minutes for the update to take place.

If the NetworkTimeProtocol Service does not run on the Cisco CallManager

Note: This procedure only applies to Cisco CallManager.

Complete these steps in order to install the NetworkTimeProtocol service:

Open a command prompt and change to this directory:

C:\>cd C:\Program Files\Cisco\Xntp


Run install.bat:

C:\Program Files\Cisco\Xntp>install.bat

Installing Configuration Files

1 file(s) copied.

Installing Executables

1 file(s) copied.

1 file(s) copied.

1 file(s) copied.

1 file(s) copied.

The NTP service is already installed

Remove it first if you need to re-install a new version

.

The NTP Service is now installed.


Please modify the NTP.CONF file in C:\WINNT appropriately.

.

See readme.txt for more information.

.

After modifying the configuration file, use the services control panel

to make NTP autostart and either reboot or manually start it.

When the system restarts, the NTP service will be running.

For more information on NTP Operations please see the NTPOG.Wri

C:\Program Files\Cisco\Xntp>


Synchronize Time Manually with the Time Server Using NTP

Note: This procedure only applies to Cisco CallManager.

Complete these steps in order to synchronize time manually with the Time Server using NTP.

Stop the NetworkTimeProtocol service in the Services Control Panel.
Synchronize the clock by using this commands from a command prompt:
In order to synchronize with a remote Time server:

ntpdate marc.keeker.com

Restart the NetworkTimeProtocol service in the Services Control Panel.


Configuring CISCO Multilayer Switch for Time Server
Configuration example for Catlyst 6500 series

--------------------------Start --------------------------
!--- Enable service timestamps datetime!
service timestamps debug datetime msec localtime
service timestamps log datetime msec localtime
!
!
!
!--- Hostnames for the MSFCs.
hostname MSFC15 alt hostname MSFC16
!
!
!
!Both MSFCs are in the PST timezone
clock timezone PST -8
!
!--- Both MSFCs will adjust the clock for Daylight Saving Time.
clock summer-time PDT recurring
!
!--- If connectivity to the NTP server is lost, the calendar is used.
!as an authoritative time source
clock calendar-valid
!
no ip finger
ip domain-name corp.com
ip name-server 172.16.55.120
ip name-server 171.16.60.120
!
!
!--- Each MSFC uses the IP address of the loopback0 interface as
!--- the source IP for NTP packets.

ntp source Loopback0
!
!--- The MSFCs will update the hardware calendar with the NTP time.
ntp update-calendar
!
!--- Both MSFCs are getting the time from 10.100.100.1.
ntp server patryk.keekar.com
!
end
--------------------------END --------------------------

Cisco 1000 Series Router

SNTP generally is supported on those platforms that do not provide support for NTP, such as the Cisco 1000 series, 1600 series, and 1700 series platforms. SNTP is disabled by default. In order to enable SNTP, use one or both of the following commands in global configuration mode:

Configures SNTP to request NTP packets from an NTP server.

Router(config)# sntp server patryk.keekar.com [version number]

Configures SNTP to accept NTP packets from any NTP broadcast server.

Router(config)# sntp broadcast client

Enter the sntp server command once for each NTP server. The NTP servers must be configured to respond to the SNTP messages from the router.

If you enter both the sntp server command and the sntp broadcast client command, the router will accept time from a broadcast server but prefer time from a configured server, assuming that the strata are equal. To display information about SNTP, use the show sntp EXEC command.


Router which support NTP
outer# conf t
Router# ntp server marc.keekar.com
Router# ntp server patryk.keekar.com
Router# clock timezone IST +5.30



1 comment:

Anonymous said...

Good one but in end seems that u r in hurry not formatted and crafted well.

Owl
Night watcher