[cisco-voip] Time on CCMs and phones..
Mike Lay (milay)
milay at cisco.com
Wed Sep 20 15:10:38 EDT 2006
XNTP will only be on CallManager. Also there was a cutoff & it may not
be in earlier versions of 4.0. Here is a URL for configuring time sync
for CCM. Please note this doc needs to be updates, we do not like to see
Microsoft Time used for CCM time sync. This document covers the install
as well.:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_configurat
ion_example09186a008009470f.shtml
Mike
-----Original Message-----
From: Tim Reimers [mailto:tim.reimers at asheville.k12.nc.us]
Sent: Wednesday, September 20, 2006 1:46 PM
To: Mike Lay (milay)
Cc: Cisco Voip
Subject: RE: [cisco-voip] Time on CCMs and phones..
also, is that the same for Unity?
I don't find Xntp on my Unity install--
so if it is Cisco's opinion that Xntp be used on Unity as well, how do I
find it to install?
-----Original Message-----
From: Mike Lay (milay) [mailto:milay at cisco.com]
Sent: Wednesday, September 20, 2006 11:55 AM
To: Simon, Bill; Tim Reimers
Cc: Cisco Voip
Subject: RE: [cisco-voip] Time on CCMs and phones..
You may have XNTP already install on your servers, installed as part of
any 3.3.3 or greater CCM install. Please ensure that you do not have
more than on time client running on any given server at one time. At
Cisco we prefer XNTP for a CCM implementation, by default the Pub is the
master & the Subs point to the Pub for time.
Mike
-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Simon, Bill
Sent: Wednesday, September 20, 2006 10:47 AM
To: Tim Reimers
Cc: Cisco Voip
Subject: Re: [cisco-voip] Time on CCMs and phones..
We've found that the NTPD service (Cisco NTP) that comes with
CallManager is right-on and very reliable. We use that instead of the
Windows time service. That would be my recommendation.
Tim Reimers wrote:
> hi everyone-
>
> I'm having trouble with drifting time on phones-
>
> My setup -
> acsccm1 and acsccm2 (publisher/subscriber on 4.01) acsunity (Unity
> 4.x)
>
> Supposedly, acsccm1 and acsccm2 get their time from acsunity acsunity
> gets its time from ntp.bellsouth.net That's the same timeserver my
> main data network uses.
>
> What's weird is that all three 'sets' of servers vary in their time -
> ACSCCM1 and CCM2 usually are not far apart- 15 seconds at most.
> But Unity this AM was more than 10 minutes different from the two CCMs
> And all the VOIP servers were at least 12 minutes different from my
> data timeservers.
>
> No firewalls are blocking timeserver ports- a freeware 'get the time'
> utility can use ntp.bellsouth.net and successfully get the time and
> display it - on all three servers.
>
> No timezone differences (that would result in whole hours being
> different anyhow, not just minute differences)
>
>
> Why are these servers not keeping time with each other, when both are
> looking to ACSUNITY, at the very least, and Unity is looking at the
> same public timeserver that my main DCs are for my data network?
>
>
> Here's some w32TM output from the various servers.
> _*From ACSCCM1 - you can see that it's NTP server is acsunity*_**
> C:\>w32tm -source -v
> W32Time: BEGIN:InitAdjIncr
> W32Time: Adj 156254 , Incr 156250 fAdjust 0
> W32Time: 156254 Adj!=Incr 156250
> W32Time: END:Line 2503
> W32Time: BEGIN:TsUpTheThread
> W32Time: END Line 1407
> W32Time: TimeMMInit()
> W32Time: Kernel timer : using default maximum resolution
> W32Time: MaximumTime = 156250
> W32Time: CurrentTime = 9766
> W32Time: Timer calibrated, looped 1 times
> W32Time: BEGIN:InitTmCfg
> W32Time: END:Line 807
> W32Time: BEGIN:InitTmCli
> W32Time: END:Line 2596
> W32Time: BEGIN:InitTmData
> W32Time: END:Line 2618
> W32Time: AvoidTimeSyncOnWan 0
> W32Time: ntpserver - acsunity
> W32Time: BEGIN:CMOSSynchSet
> W32Time: Setting adjustment 156254 - Bool 0
> W32Time: BEGIN:SetTSTimeRes
> W32Time: END:Line 1295
> W32Time: END:Line 864
> W32Time: BEGIN:InitializeDC
> W32Time: BEGIN:GetRole
> W32Time: Role is 'workstation'
> W32Time: END Line 672
> W32Time: END:Line 704
>
>
>
>
>
> _*w32TM output from ACSUNITY - shows ntp.bellsouth.net*_**
> C:\Documents and Settings\Administrator>w32tm -v -source
> W32Time: BEGIN:InitAdjIncr
> W32Time: Adj 156250 , Incr 156250 fAdjust 0
> W32Time: END:Line 2503
> W32Time: BEGIN:TsUpTheThread
> W32Time: END Line 1407
> W32Time: TimeMMInit()
> W32Time: Kernel timer : using default maximum resolution
> W32Time: MaximumTime = 156250
> W32Time: CurrentTime = 9766
> W32Time: Timer calibrated, looped 1 times
> W32Time: BEGIN:InitTmCfg
> W32Time: END:Line 807
> W32Time: BEGIN:InitTmCli
> W32Time: END:Line 2596
> W32Time: BEGIN:InitTmData
> W32Time: END:Line 2618
> W32Time: AvoidTimeSyncOnWan 0
> W32Time: ntpserver - ntp.bellsouth.net
> W32Time: BEGIN:CMOSSynchSet
> W32Time: Setting adjustment 156250 - Bool 0
> W32Time: BEGIN:SetTSTimeRes
> W32Time: END:Line 1295
> W32Time: END:Line 864
> W32Time: BEGIN:InitializeDC
> W32Time: BEGIN:GetRole
> W32Time: Role is 'PDC'
> W32Time: END Line 672
> W32Time: BEGIN:FetchParentDomainName
> W32Time: NetLogonGetTimeServiceParentDomain() returned 54b with
ptr 0
> W32Time: END:Line 782
> W32Time: END:Line 704
> W32Time: Server: Binding to 1 NIC.
> W32Time: bind failed: 0x80072740
> W32Time: Logging event 0xC0000031. 15 min until this event is allowed
> again.
> W32Time: 0xC0000031 reported to System Log in Event Viewer
> W32Time: BEGIN:FinishCleanup
> W32Time: BEGIN:TsUpTheThread
> W32Time: END Line 1407
> W32Time: BEGIN:UnInitializeDC
> W32Time: Ptrs 0 - 0
> W32Time: END:Line 727
> W32Time: Time service stopped.
> W32Time: END:Line 407
>
>
>
>
>
> ----------------------------------------------------------------------
> --
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
--
Bill Simon - bills at tns.its.psu.edu - (814) 865-2270
http://tns.its.psu.edu/ _______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
More information about the cisco-voip
mailing list