geert.nijs at gmail
May 16, 2012, 7:25 AM
Post #2 of 2
(497 views)
Permalink
|
Had the same message here.
This is because a remote station whats to "peer" with this station, but the
source ip is not included in local "ntp peer xxx" statements.
So the local switch does not allow the remote system to "peer".
Check if the remote system is using "ntp source Lo0" or something like that
( a fixed ip)
Do a "debug ntp packet" to see what is the source ip that generates this
messaged.
regerds,
Geert
CCIE#13729
2011/6/24 Jeff Kell <jeff-kell [at] utc>
> Updated to SXJ, now a new rash of messages:
>
> > Jun 23 21:37:41.814 EDT: NTP Core (NOTICE): ntp_receive: dropping
> > message: AM_NEWPASS, passive association disabled..
> > Jun 23 21:44:23.716 EDT: NTP Core (NOTICE): ntp_receive: dropping
> > message: AM_NEWPASS, passive association disabled..
> > Jun 23 21:46:00.720 EDT: NTP Core (NOTICE): ntp_receive: dropping
> > message: AM_NEWPASS, passive association disabled..
> > Jun 23 21:53:09.086 EDT: NTP Core (NOTICE): ntp_receive: dropping
> > message: AM_NEWPASS, passive association disabled..
> > Jun 23 21:54:38.415 EDT: NTP Core (NOTICE): ntp_receive: dropping
> > message: AM_NEWPASS, passive association disabled..
>
> Googling that turns up results, but the suggestions/explanations seem to
> point in all sorts of different directions.
>
> Clarification pointer from anyone that has crossed this bridge already?
>
> Thanks,
>
> Jeff
>
> _______________________________________________
> cisco-nsp mailing list cisco-nsp [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
|
