ā03-11-2010 09:52 AM - edited ā03-15-2019 09:44 PM
I have a Cisco 2821 10.1.1.1 as a VGW and router in the network sitting behind a Cisco ASA5505(10.1.1.2)
Was running 12.4-3g prior to upgrading.
The ASA , switches, another router/vgw at anthoer site, Cisco WLC and Cisco UCM server and customer Domain controller are all set to get their NTP from the this VGW.
10.1.1.1 is acting as the NTP server for the network. and when you do a show ntp status it shows syncd.
________________
Router1#sh ntp stat
Clock is synchronized, stratum 2, reference is 132.163.4.101
nominal freq is 250.0000 Hz, actual freq is 249.9936 Hz, precision is 2**24
reference time is CF43A732.243889C1 (11:30:26.141 CST Thu Mar 11 2010)
clock offset is -0.0007 msec, root delay is 0.03 msec
root dispersion is 0.08 msec, peer dispersion is 0.01 msec
loopfilter state is 'CTRL' (Normal Controlled Loop), drift is 0.000025278 s/s
system poll interval is 512, last update was 1035 sec ago.
Router1#sho clo
11:47:47.971 CST Thu Mar 11 2010
_______________________________
The ASA, WLC and other router seem to be synching to this gateway.
In the WLC it says synced with time server
the other router says sync stratum 3
In the UCM server is says ntp rechable but customer is reporting time is off on the phones.
Also customers DC is getting this error when trying to sync
((computer didnt resynch because no time data was available.))
when doing a debug on NTP i get this
""windows server""
000854: Mar 11 15:53:32.539: NTP message received from x.x.x.x on interface 'GigabitEther
net0/0.10' (x.x.x.x).
000855: Mar 11 15:53:32.539: NTP Core(DEBUG): ntp_receive: message received
000856: Mar 11 15:53:32.539: NTP Core(DEBUG): ntp_receive: peer is 0x463670A0, next action is 1.
000857: Mar 11 15:53:32.539: NTP Core(NOTICE): ntp_receive: dropping message: unsynch.
---------------------
----------------
call manager
000858: Mar 11 15:53:40.731: NTP message received from x.x.x.x on interface 'GigabitEthern
et0/0.9' (x.x.x.x).
000859: Mar 11 15:53:40.731: NTP Core(DEBUG): ntp_receive: message received
000860: Mar 11 15:53:40.731: NTP Core(DEBUG): ntp_receive: peer is 0x00000000, next action is 3.
000861: Mar 11 15:53:40.731: NTP Core(DEBUG): ntp_receive: doing fast answer to client.
000862: Mar 11 15:53:40.731: NTP message sent to x.x,x,x, from interface 'GigabitEthernet0
/0.9' (x.x.x.x).
When you point the customers DC to a public time server it stays sync'd with no issues and same thing with the UCM server.
Any thoughts would be greatly appreciated.
Upgraded to c2800nm-spservicesk9-mz.124-24.T2.bin
from
c2800nm-spservicesk9-mz.124-3g.bin
Solved! Go to Solution.
ā03-11-2010 11:46 AM
Hi greg,
It looks like you may be hitting one or more of these Bugs;
CSCsy31597
Synchronization fails between NTPv4 and Linux
CSCtf03971
NTP stratum not displayed correctly in 'show ntp status' output
CSCsy13363
NTP v4 is slow to synchronize
Cheers!
Rob
ā03-11-2010 12:05 PM
Hey Greg,
None of the three show a 'Fixed-In" version
CSCsy31597 Bug Details
Synchronization fails between NTPv4 and Linux
Symptom:
NTP fails to synchronize between 1800 router and Linux
Conditions:
It was observed after upgrading past 12.4(15)T throttle where we use NTPv4
Workaround:
Downgrade to 12.4(15)T train with NTPv3
Status
Open
Severity
3 - moderate
Last Modified
In Last 7 Days
Product
Cisco IOS software
Technology
1st Found-In
12.4(23.13)T1
CSCtf03971 Bug Details
NTP stratum not displayed correctly in 'show ntp status' output
Symptom:
'show ntp status' shows different local system stratum then actual local stratum.
Conditions:
Issue experienced when NTP client configured to also be a Master. Client syncs to itself first, then will sync to its configured servers, but 'show ntp status' will show a local stratum of the previous sync (to itself) and not of the current sync (to the external NTP) server.
Workaround:
None.
Status
Open
Severity
4 - minor
Last Modified
In Last 2 weeks
Product
Cisco IOS software
Technology
IP Application Services
1st Found-In
12.4(24)T2
CSCsy13363 Bug Details
NTP v4 is slow to synchronize
Symptom:
A router may take as long as 15 minutes to synchronize its clock to an NTP server.
Conditions:
The router is running IOS 12.4(20)T or above.
Workaround:
Configure the "iburst" and "burst" options, for example:
ntp server 10.0.47.1 burst iburst
with this configured, NTP should synchronize in under 2 minutes.
Further Problem Description:
This performance regression was introduced in IOS 12.4(20)T, which
implemented NTP v4.
Status
Open
Severity
6 - enhancement
Last Modified
In Last 2 weeks
Product
Cisco IOS software
Technology
IP Application Services
1st Found-In
12.4(22)T
Hope this helps!
Rob
ā03-11-2010 11:46 AM
Hi greg,
It looks like you may be hitting one or more of these Bugs;
CSCsy31597
Synchronization fails between NTPv4 and Linux
CSCtf03971
NTP stratum not displayed correctly in 'show ntp status' output
CSCsy13363
NTP v4 is slow to synchronize
Cheers!
Rob
ā03-11-2010 11:54 AM
Rob do you know where this is fixed in.
thanks
ā03-11-2010 12:05 PM
Hey Greg,
None of the three show a 'Fixed-In" version
CSCsy31597 Bug Details
Synchronization fails between NTPv4 and Linux
Symptom:
NTP fails to synchronize between 1800 router and Linux
Conditions:
It was observed after upgrading past 12.4(15)T throttle where we use NTPv4
Workaround:
Downgrade to 12.4(15)T train with NTPv3
Status
Open
Severity
3 - moderate
Last Modified
In Last 7 Days
Product
Cisco IOS software
Technology
1st Found-In
12.4(23.13)T1
CSCtf03971 Bug Details
NTP stratum not displayed correctly in 'show ntp status' output
Symptom:
'show ntp status' shows different local system stratum then actual local stratum.
Conditions:
Issue experienced when NTP client configured to also be a Master. Client syncs to itself first, then will sync to its configured servers, but 'show ntp status' will show a local stratum of the previous sync (to itself) and not of the current sync (to the external NTP) server.
Workaround:
None.
Status
Open
Severity
4 - minor
Last Modified
In Last 2 weeks
Product
Cisco IOS software
Technology
IP Application Services
1st Found-In
12.4(24)T2
CSCsy13363 Bug Details
NTP v4 is slow to synchronize
Symptom:
A router may take as long as 15 minutes to synchronize its clock to an NTP server.
Conditions:
The router is running IOS 12.4(20)T or above.
Workaround:
Configure the "iburst" and "burst" options, for example:
ntp server 10.0.47.1 burst iburst
with this configured, NTP should synchronize in under 2 minutes.
Further Problem Description:
This performance regression was introduced in IOS 12.4(20)T, which
implemented NTP v4.
Status
Open
Severity
6 - enhancement
Last Modified
In Last 2 weeks
Product
Cisco IOS software
Technology
IP Application Services
1st Found-In
12.4(22)T
Hope this helps!
Rob
ā03-12-2010 01:14 PM
Rob thanks great info
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: