Why use windows as your networks ntp server ?
Why not setup you Solaris system(smc01) as the ntp server and sync all your servers off it ?

Not sure about Veritas Cluster, But with Sun Cluster, there is ntp.cluster template file you use for ntp and we use ntp.conf.cluster , not ntp.conf

In the ntp.conf.cluster you setup your nodes as peers to sync off each other using the private interconnects and set the ntp server to your time server on your network.

This is what we use on our Sun Cluster:

Code:

server my.ntp.server
#
# One of the "peers" should be "preferred" over the others.
#
peer clusternode1-priv prefer
peer clusternode2-priv

#
# Drift file (optional)
#
driftfile /var/ntp/ntp.drift

#
# Stats (optional)
#
filegen peerstats file peerstats type day enable
filegen loopstats file loopstats type day enable
filegen clockstats file clockstats type day enable

Code:

# ntpq -p
     remote           refid      st t when poll reach   delay   offset    disp
==============================================================================
*my.ntp.server yarrina.connect  3 u   74 1024  377     1.13   -0.392    1.94
 clusternode1-pr 0.0.0.0         16 -    - 1024    0     0.00    0.000 16000.0
+clusternode2-pr my.ntp.server  4 u  298 1024  376     0.43   -0.270   16.14
#

my.ntp.server is a Stratum 3 server, it syncs its time from our Internet providers Stratum 2 servers. Its ntp.conf looks like this:

Code:

server ntp.mel.connect.com.au
server ntp.syd.connect.com.au

broadcast 224.0.1.1 ttl 4
broadcastdelay  0.5

driftfile /etc/inet/ntp.drift

Code:

# ntpq -p
     remote           refid      st t when poll reach   delay   offset    disp
==============================================================================
 NTP.MCAST.NET   0.0.0.0         16 -    -   64    0     0.00    0.000 16000.0
*yarrina.connect ntp.sydney.nmi.  2 u   49  128  377     3.02    0.429    0.44
+warrane.connect ntp.melbourne.n  2 u   68  128  377    19.01    0.851    0.66
#

Strata NTP servers are arranged in a hierarchy of levels, called strata. A stratum-1 server is more accurate than a stratum-2 server. There are 15 strata, but only first three are usually used.

Stratum 1 is the highest hierarchical level and those servers are directly attached to highly accurate reference sources such as atomic clocks. This is backbone of NTP and regular servers should not interface with backbone directly, but using NTP servers on lower stratums.

Stratum 2 servers tend to operate out of academic institutions and large corporations. Those can be used by "regular" Internet-connected servers but any sizable organization usually has its own "local" NTP server(s) that interfaces with Stratum 2 servers.

Below Stratum 2 you will find local NTP server that most organizations on the Internet now have. Most organization use free xntp daemon, but some prefer using appliances. Appliances often provide alternative synchronization case of lost internet connectivity using GPS.