MiZN
asked on
Cisco 877W different time in log and sh clock
My clock/ntp setup is
clock initialize nvram
clock timezone MSK 4
clock save interval 8
...
! ip nat inside source static udp 192.168.1.63 123 interface Dialer0 123
...
access-list 10 permit 192.43.244.18
...
access-list 100 remark Auto generated by SDM for NTP (123) time.nist.gov
access-list 100 permit udp host 192.43.244.18 eq ntp host 192.168.1.1 eq ntp
...
access-list 101 remark Auto generated by SDM for NTP (123) time.nist.gov
access-list 101 permit udp host 192.43.244.18 eq ntp any eq ntp
...
access-list 101 remark NTP server
access-list 101 permit udp any any eq ntp
...
kron policy-list TIME
cli ntp server 192.43.244.18 prefer source Dialer0
!
kron occurrence TIME in 0:5 oneshot
policy-list TIME
!
kron occurrence TIME in 5:0 recurring
policy-list TIME
!
...
ntp access-group peer 10
ntp server 192.43.244.18 prefer source Dialer0
Moscow time is UTC/GMT +4 now and winter time is abolished in that year.
Winter time is MSK, summer time is MSD (it is MSD now).
Now in logs (deb ntp all) I see time by 4 hours less than at sh clo and sh ntp as d.
What is the reason of difference, and how to set these times equal?
Example:
Oct 4 18:24:34.051: NTP message sent to 192.43.244.18, from interface 'Dialer0' (91.79.169.31).
Oct 4 18:24:34.295: NTP message received from 192.43.244.18 on interface 'Dialer0' (91.79.169.31).
Oct 4 18:24:34.295: NTP Core(DEBUG): ntp_receive: message received
Oct 4 18:24:34.295: NTP Core(DEBUG): ntp_receive: peer is 0x83F5AAE0, next action is 1.
Oct 4 18:24:34.295: NTP Core(DEBUG): receive: packet given to process_packet
Router#sh clo
22:25:49.579 MSD Tue Oct 4 2011
Router#
Oct 4 18:27:07.049: NTP message sent to 87.108.20.70, from interface 'Dialer0' (91.79.169.31).
Oct 4 18:27:07.097: NTP message received from 87.108.20.70 on interface 'Dialer0' (91.79.169.31).
Oct 4 18:27:07.097: NTP Core(DEBUG): ntp_receive: message received
Oct 4 18:27:07.097: NTP Core(NOTICE): ntp_receive: dropping message: restricted..
clock initialize nvram
clock timezone MSK 4
clock save interval 8
...
! ip nat inside source static udp 192.168.1.63 123 interface Dialer0 123
...
access-list 10 permit 192.43.244.18
...
access-list 100 remark Auto generated by SDM for NTP (123) time.nist.gov
access-list 100 permit udp host 192.43.244.18 eq ntp host 192.168.1.1 eq ntp
...
access-list 101 remark Auto generated by SDM for NTP (123) time.nist.gov
access-list 101 permit udp host 192.43.244.18 eq ntp any eq ntp
...
access-list 101 remark NTP server
access-list 101 permit udp any any eq ntp
...
kron policy-list TIME
cli ntp server 192.43.244.18 prefer source Dialer0
!
kron occurrence TIME in 0:5 oneshot
policy-list TIME
!
kron occurrence TIME in 5:0 recurring
policy-list TIME
!
...
ntp access-group peer 10
ntp server 192.43.244.18 prefer source Dialer0
Moscow time is UTC/GMT +4 now and winter time is abolished in that year.
Winter time is MSK, summer time is MSD (it is MSD now).
Now in logs (deb ntp all) I see time by 4 hours less than at sh clo and sh ntp as d.
What is the reason of difference, and how to set these times equal?
Example:
Oct 4 18:24:34.051: NTP message sent to 192.43.244.18, from interface 'Dialer0' (91.79.169.31).
Oct 4 18:24:34.295: NTP message received from 192.43.244.18 on interface 'Dialer0' (91.79.169.31).
Oct 4 18:24:34.295: NTP Core(DEBUG): ntp_receive: message received
Oct 4 18:24:34.295: NTP Core(DEBUG): ntp_receive: peer is 0x83F5AAE0, next action is 1.
Oct 4 18:24:34.295: NTP Core(DEBUG): receive: packet given to process_packet
Router#sh clo
22:25:49.579 MSD Tue Oct 4 2011
Router#
Oct 4 18:27:07.049: NTP message sent to 87.108.20.70, from interface 'Dialer0' (91.79.169.31).
Oct 4 18:27:07.097: NTP message received from 87.108.20.70 on interface 'Dialer0' (91.79.169.31).
Oct 4 18:27:07.097: NTP Core(DEBUG): ntp_receive: message received
Oct 4 18:27:07.097: NTP Core(NOTICE): ntp_receive: dropping message: restricted..
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Routers
A router is a networking device that forwards data packets between computer networks. Routers perform the "traffic directing" functions on the Internet. The most familiar type of routers are home and small office cable or DSL routers that simply pass data, such as web pages, email, IM, and videos between computers and the Internet. More sophisticated routers, such as enterprise routers, connect large business or ISP networks up to the powerful core routers that forward data at high speed along the optical fiber lines of the Internet backbone. Though routers are typically dedicated hardware devices, use of software-based routers has grown increasingly common.
49K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
