Pete Lumbis wrote:
It sounds like NTP may be stuck in broadcast mode for some reason. I'd
suggest either calling TAC or issuing no ntp to completely disable the
service then reconfigure the ntp server commands.
Resetting the ntp process by issuing no ntp and then reapplying the
ntp server
Hi,
On Thu, Jul 04, 2013 at 04:17:55PM +0700, Victor Sudakov wrote:
However, when I apply the following command to the interface:
interface GigabitEthernet0/0
ntp multicast ttl 1
the routers again begins sending multicast NTP packets with ttl=28.
What gives?
Don't do this, then
If
Gert Doering wrote:
However, when I apply the following command to the interface:
interface GigabitEthernet0/0
ntp multicast ttl 1
the routers again begins sending multicast NTP packets with ttl=28.
What gives?
Don't do this, then
If you really care, open a TAC case, get
Colleagues,
Why is a CISCO3945 router sending multicast NTP packets with ttl=31 (!)
while I have never configured it to do so? debug ntp packets reveals:
NTP message sent to 224.0.1.1, from interface 'NULL' (0.0.0.0).
NTP: ntpio_send_ipv4 called with bcast address and NULL interface
In fact,
This must be some NTP v4 novelty?
All right, how do I revert to the old behaviour, or at least limit the
ttl of those multicast packets sent from the 'NULL' interface?
ntp multicast ttl 1 on the interface does not seem to have any
effect. Configuring a broadcast destination on an interface does
Aaron wrote:
Have you set your ntp source interface by any chance?
No.
In fact, now I have removed all NTP configuration except 2 ntp servers,
but the multicast packets are still being sent:
orlov#
orlov#sh running-config | i ntp
ntp server 10.14.129.71
ntp server 10.14.140.125
orlov#
NTP
| Phone: 914-460-4039
-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of
Victor Sudakov
Sent: Tuesday, July 02, 2013 12:31 PM
To: Aaron; cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] NTP message sent to 224.0.1.1, from interface 'NULL
To: Aaron; cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] NTP message sent to 224.0.1.1, from interface
'NULL' (0.0.0.0).
Aaron wrote:
Have you set your ntp source interface by any chance?
No.
In fact, now I have removed all NTP configuration except 2 ntp servers
, NY 10577
OTA Management LLC | Phone: 914-460-4039
From: Aaron [mailto:dudep...@gmail.com]
Sent: Tuesday, July 02, 2013 12:41 PM
To: Matthew Huff
Cc: Victor Sudakov; cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] NTP message sent to 224.0.1.1, from interface 'NULL'
(0.0.0.0).
Hmm.
What
Have you set your ntp source interface by any chance?
It has been awhile since I've been on IOS.
It shouldn't have a big impact to your ntp clients unless you have an odd
setup with your ntp configuration or architechture.
I have my core set up to peer with each other directly (slaved off of a
It sounds like NTP may be stuck in broadcast mode for some reason. I'd
suggest either calling TAC or issuing no ntp to completely disable the
service then reconfigure the ntp server commands.
-Pete
On Tue, Jul 2, 2013 at 12:30 PM, Victor Sudakov v...@mpeks.tomsk.su wrote:
Aaron wrote:
Have
NTP broadcast sends the messages using multicast, to 224.0.1.1. See
RFC5905.
Phil
On 7/2/13 6:09 AM, Victor Sudakov v...@mpeks.tomsk.su wrote:
Colleagues,
Why is a CISCO3945 router sending multicast NTP packets with ttl=31 (!)
while I have never configured it to do so? debug ntp packets
12 matches
Mail list logo
